From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Case Structure Based on Changing Input Controls

You will most likely run into issues with your VISA Write. You are trying to run them in parallel but they are all communicating with the same device. You should send the commands out serially. Use the Error Out of the VISA Write as the Error In to the next one. This will ensure the writes happen in serial. Otherwise you will get a conflict or garbled messages.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
Message 11 of 14
(339 Views)

Aaah, I see now why it was sometimes jittery and it wasn't working properly. Like that?

0 Kudos
Message 12 of 14
(330 Views)

I would consider creating a subVI for your data write. The subVI would take the VISA resource, the location value (the value that indicates which motor), the motor values and the error in. It would output the VISA resource and teh error out. Your block diagram would look cleaner and if you needed to make a change to the communications you would only need to do it in one place rather than update 4 copies of the code. You should also consider renaming your controls and indicators to meaningful names. String 3 is not very descriptive.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
Message 13 of 14
(321 Views)

I see. I'll go about that once everything is set up and works. Thanks for all the good advice Mark. I'll come back if there's other things.

0 Kudos
Message 14 of 14
(312 Views)