05-25-2012 08:04 AM - edited 05-25-2012 08:06 AM
Seems that decreasing the 'wait' in the loop helps.
Would there be any benefit to making this into a subvi to run in a larger loop?
05-25-2012 08:07 AM
Hi Ralph,
- your loop timing determines the sampling speed. You cannot detect pulses with lower switch time than your sampling time. Fundamental data aquisition knowledge...
- you can put that into a subVI. That doesn't change the behaviour, but makes the (main VI) block diagram nicer
05-25-2012 09:01 AM
In use as a subvi, one wouldn't want a while loop, would you?
If not, how do you handle the shift registers... Make them inputs and outputs of the subvi and run them through the main loop?
05-25-2012 09:11 AM - edited 05-25-2012 09:12 AM
05-25-2012 10:19 AM
Oh neat.
I'm a hack so all help is appreciated.
05-25-2012 10:38 AM
Hmm.
Made it into a sub, trying to run two separate instances and they're behaving oddly. Just running away and no distinct control. Do I need to add error in and out to 'sequence' the subvis?
05-25-2012 11:20 AM
05-25-2012 12:25 PM
I took all three courses five years ago and knew everything pretty well then, it's been a couple of years.
If I don't ask, how will I know?
05-25-2012 12:37 PM
OK, I set the Execution properties for the sub vi to Reentrant with preallocate for each clone and the functionality seems to be there.
Glad I had this conversation, because I have some VI's with multiple calls of the same vi that are very, very large and I had been using the error handler to sequence the subvi's. This was causing some major slowness in the operation. As a result of this conversation, I believe I can go fix things that have been bothering me for years.
The classes didn't really cover reentrancy. This is all new to me. Thanks.