01-29-2015 10:20 AM - edited 01-29-2015 10:21 AM
hi Dhouston
please check the files attached...
Regards
RENN
01-29-2015 03:27 PM
RENN, I used most of your code along with mine. The indicator changes extremely fast now. It moved so fast I thought it wasn't working at all. It seems that the indicator changes one iota, then immediately goes back to the maximum value. I did a Probe watch and I see that the Scale.Maximum property is incrementing and decrementing like I would expect. I have attached a snippet showing the area of concern, as well as the vi itself.
There are data acquisition icons in this vi, so I have doubts the vi will actually run, but it is present for all to see.
Sherm,
I was in the process of trying your idea right before RENN came back with the second example. I'll be keeping yours around for future reference.
02-27-2015 08:39 AM - edited 02-27-2015 09:04 AM
Dhouston, please consider using subVIs in your program.
For example, just look at your own code, you are setting the 'position' and 'Motor Not Active' values around 12 times. you can see, the same functionality is used 12 times. It takes 12 times more coding and the code is difficult to maintain. just think about a place where you doing this only once!.
To help you with this, i am attaching another version.
Regards
RENN