LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem !! while using event structure with VISA

I have attached the VI which is saved at version 2015

0 Kudos
Message 11 of 14
(731 Views)

The ST[1] is your Stop command ... If it's supposed to be mirrored as acknowledgement you need to read that when you send the command.

Also, if you set the Booleans to Latch you can remove the Locals.

The point of having the commands end with semicolon is that you (probably) can write them together, so you can start the system by sending UM=5;MO=1;PR=23454; in one fell swoop.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 12 of 14
(726 Views)

It does not only return the ST[1]; many time it also returns BG; as well,

 

So I am confused why it returns commands when I call profiler position first time.

when I press second time it works in a way it should work and return me profiler position.

 

When I call profiler position first time:

 

mi1111_0-1586953479678.png

 

When I call profiler position second time:

mi1111_1-1586953650659.png

 

0 Kudos
Message 13 of 14
(700 Views)

Hi mi,

 


@mi1111 wrote:

It does not only return the ST[1]; many time it also returns BG; as well,

So I am confused why it returns commands when I call profiler position first time.

when I press second time it works in a way it should work and return me profiler position.


Because you (probably) sent those other commands before trying to request the current position?

And because you forgot to implement the communication protocal as described in the manual by not just sending commands, but also reading (all) their responses!?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 14 of 14
(698 Views)