LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

hardware trigger causes shift register failure

I got an interesting problem. I've got a case statement that contains the AI Start.VI out before a while loop that contains AI Read.VI and some processing. The case statement with the AISTART.VI, depending on the case, will either start immediately, or start upon reception of an analog trigger. I've also got a couple waveform graphs inside the loop that update every loop iteration with different running averages. These averages are kept in shift registers that are initialized from outside the loop before the first iteration. When the case is set to immediately aquire, these graphs update beautifully. If the case is set to wait for the trigger, the trigger begins the acquisition nicely, but these graphs that are connect
ed to shift registers never get data! Other graphs not dependent on shift registers still update every iteration. Any ideas on what in the world is up here? Thanks in advance for any help!

-JOE
0 Kudos
Message 1 of 5
(3,025 Views)
Just a guess here.

Create an indicator for the shift registers. There may be data in them that is confussing the graph.

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 2 of 5
(3,025 Views)
G'Day Joe,

Please post up your VI - your problem sounds interesting...

cheers,
Christopher

Christopher G. Relf
Certified LabVIEW Developer

Christopher.Relf@mBox.com.au
Int'l Voicemail & Fax: +61 2 8080 8132
Aust Voicemail & Fax: (02) 8080 8132

---
EULA
1) This is a private email, and although the views expressed within it may not be purely my own, unless specifically referenced I do not suggest they are necessarily associated with anyone else including, but not limited to, my employer(s).
2) This email has NOT been scanned for virii - attached file(s), if any, are provided as is. By copying, detaching and/or opening attached files, you agree to indemnify the sender of such responsibility.
3) Because
e-mail can be altered electronically, the integrity of this communication cannot be guaranteed.




Copyright © 2004-2024 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 4.0 License.
0 Kudos
Message 3 of 5
(3,025 Views)
sorry, I tried to upload the VI, but it's 30 megs and it seems the internet is putting up a fuss about it. The best I can do is offer a more detailed explanation.
-JOE
0 Kudos
Message 4 of 5
(3,025 Views)
Joe,
Strip down your VI into a simpler example that shows the behavior. Have just AI start, read and clear, with structures and one graph. This VI shouldn't have more than few megs. Test this VI, and if it reproduces the behavior, post it on the web. Run the VI in the highlighted execution mode or put a probe on the shift register, and see if there are values being written to it in each iteration.

Zvezdana S.
0 Kudos
Message 5 of 5
(3,025 Views)