LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Query Instrument in NI MAX but not using LabVIEW Drivers

Hello,

 

In NI MAX, I can query (*IDN?) and a Magna XR Series power supply and read the right response.  I have downloaded the most recent LabVIEW drivers for this power supply, but I am unable to to get the Initialize.vi to work.  

 

I am communicating the instrument via TCPIP.  The error is occurring when inputting in the property node "IO Port" as highlighted below.  The output error also confirms that it's the fourth argument.

 

Has anyone had this issue before with an instrument driver?  Does anyone have any tips on how to resolve this?

 

 

 

_natalie__2-1731681159679.png

 

 

_natalie__1-1731681079595.png

 

 

0 Kudos
Message 1 of 10
(252 Views)

Run the code in Highlight and Retain values-mode. I'm not so sure you enter that case.

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

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 2 of 10
(246 Views)

Yes, I most definitely am entering that case, Case 6.

0 Kudos
Message 3 of 10
(243 Views)

@Yamaeda wrote:

Run the code in Highlight and Retain values-mode. I'm not so sure you enter that case.


Also, that coercion dots indicates that you are typecasting the line feed constant to the wrong datatype.  SHOW the lable on the integer.  Are you sure the device expects LF and not CR?


"Should be" isn't "Is" -Jay
0 Kudos
Message 4 of 10
(241 Views)

It was U32 when it should have been U8.  I have fixed that, but it did not resolve my problem.

0 Kudos
Message 5 of 10
(238 Views)

@_natalie_ wrote:

It was U32 when it should have been U8.  I have fixed that, but it did not resolve my problem.


OK, now try running VI Annalyzer.   It is difficult debugging a picture but, I don't like the looks of some of your constants! They have strange borders.  This COULD be a clue that there are objects hidden underneath them (VIA tests for hidden objects and unwired constants)  you also have an unwired boolean constant so, run the VIA and see if my eyeballs and 8-Ball are working today.


"Should be" isn't "Is" -Jay
0 Kudos
Message 6 of 10
(213 Views)

Oh, sorry.  Those loose constants and what not were added when I was trying to figure out what wrong with the driver.  This has been happening even with a "fresh" download of the drive.  I'll attach it.

 

I don't think I have access to the VI Analyzer...

0 Kudos
Message 7 of 10
(209 Views)

VIA has shipped with all versions of LabVIEW for over a decade.  It's under the Tools menu.

 

But,  it's good to know my eyes are working!  There really were hidden objects under those funny looking constants.  8-Ball count ++


"Should be" isn't "Is" -Jay
0 Kudos
Message 8 of 10
(200 Views)

What happens if you just delete the 4th element of that property node, leaving the 1st three and not setting it?

 

I've been using VISA over TCP/IP for quite a while and I have never set that property while using my own code (though it may have been set by drivers in some cases without me noticing...).  It's not entirely clear to me what the difference is between the "normal" setting and that setting.

0 Kudos
Message 9 of 10
(174 Views)

No error occurs there, but one will occur at the Visa Write.

0 Kudos
Message 10 of 10
(145 Views)