Case Statements or While Loop

[BadAzzS10]

Hi guys,

I need some advice on what is the best approach.

I am modifying a current Labview program (the same VI just renamed) to take advantage of two readings from a Force Gauge. My requirements are:

1. Take the first dip in the force gauge. This will be the first reading and it's distance.
2. Find the next rise in force
3. Take the next dip and place this as the second reading along where the distance occurs.

I have four fields: 1st Peak Force, 1st Distance, 2nd Peak Force, 2nd Distance.

Do I use multiple case statements, a while loop, or something else?

I've enclosed my VI. I know, there are a lot of local references in here , but I've got a short time frame and I'll have to rewrite this later.

[BadAzzS10]

By the way, it's #23 in the case structure.

[altenbach]

Could you reduce the problem to a simple VI with an array of typical test data?

(btw, all these "read local variable-modify-write to the same local variable" constructs should be done with shift registers instead of locals of hidden controls/indicators. If you keep the data in a shift register, you don't need to involve the front panel. This is not text based programming 😉 Overall, the code is very hard to read. There is also something wrong with your state enum, because it gets coerced to a simple number. Most likely you are mixing different enums. You should have made it a type def. )

[elset191]

Sounds like you might want to look into the peak finding vi's.  Search the examples for "peak"

[altenbach]

---

@altenbach wrote:

Most likely you are mixing different enums. You should have made it a type def. )

---

In case "10", the two enums with selection "User Input (Start Button)" have an extra item "Read Gauge (R.T.C.)", replace those with the more common enum and things will look much better. Make it a type def to keep things manageable.

[BadAzzS10]

Thank you so much! That would have taken me hours to find out.

[tbob]

You can reduce the complexity of your timestamp code:

[BadAzzS10]

tbob, won't I still need the date/time vi wired into the format date/time string?

[TCPlomp]

---

@BadAzzS10 wrote:

tbob, won't I still need the date/time vi wired into the format date/time string?

---

No, that's an implicit input, it per default uses the current timestamp, you can always use another moment in time.

If you are looking for information of a typedef, see this video.

Ton

[BadAzzS10]

I don't think the Peak Reading VI will work. I need to read the force of the gauge and at what distance it was taken at. I don't think that the Peak Finding VI will do that (although my knowledge level is very low with labview).