LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

read and save settings from instruments

The command in the initialize vi (:SYST:PRES;) ---> *RST without changing display state...

I have edited the subVI with VISA open & close to replace 8133 initialize and close VIs.

double checked the SCPI command for delay, but still not working....duty cycle is working though...

0 Kudos
Message 31 of 38
(1,913 Views)

cannot figure out what's holding back for 'delay' parameter(?)

It looks exactly the same format as for 'duty cycle' but only duty cycle works...

Can anyone tell me what's would be the culprit? (tabbing order, syntax?)

thanks,

0 Kudos
Message 32 of 38
(1,886 Views)
What have you done to try and debug the problem? I'm assuming it is the read instrument settings that is giving you a problem. Right click on the VI and select SubVI Node Setup. Select Show Panel, Close Afterwards, and Suspend. Now, when you run this state, that subVI will pop-up and you will have to click the run button before it executes. Before you do that, place a probe on the VISA Read where you are getting the value. Run the subVI and see what it says. You can also execute the instrument command in MAX to see what the actual string returned is.
Message 33 of 38
(1,882 Views)
created indicators for both delay & duty cycle...they seems to work fine (reading correct values) for different GPIB addresses...
 
0 Kudos
Message 34 of 38
(1,874 Views)
Do you mean it is now working? If not, would you like to share the actual strings you're getting? You didn't save the readings with the subVI. You can easily do that, just go to the Operate menu and select 'Make Current Values Default'. Save the subVI afterward.
Message 35 of 38
(1,872 Views)
The interesting thing is that I can see the value reading from indicators, but not from the 'pulse setting' cluster for delay..
0 Kudos
Message 36 of 38
(1,867 Views)
Of course not. The returned string is '+3.00000E-10', you convert that to a dbl but then your numeric indicator is set to only 2 digits of precision. When you program the delay, you are programming the value in picoseconds. That's the meaning of the 'PS' suffix. Determine if there is a query to return the delay setting in ps or multiply the numeric result before you write it to the cluster.
Message 37 of 38
(1,865 Views)

thank you!

 

0 Kudos
Message 38 of 38
(1,860 Views)