LabVIEW exe cannot find power supply - Development code has no problem

[Daddy-O]

I have created a VI (LV 2019) to automatically detect the resource name of a specific model of power supply. It is the very first thing that happens in a larger, more complex test routine. I have had no problems running it on my development machine. I created a exe build and deployed it to another computer. I expect the "VISA resource Teledyne PS" indicator to return a value like "ASRL:INSTR" what I get is "GPIB::INTFC" I have no idea how that would appear based on my little VI.

MAX does not see the power supply at all and Windows Device Manager shows it as this.

Also the target machine has been updates to new drivers. I think they should be good. See this below.

I have attached the VI if someone could look it over for me please.

Thanks in advance, Chris

[Gregory]

It looks like you're connecting to the USB port on the instrument.

Have you installed the USB driver for this instrument? https://www.gwinstek.com/en-global/products/detail/GPP-Series

[Daddy-O]

I am installing that driver on the target machine. I will keep that link for other things as well. Whenever I went to the Teledyne site there was no power supply support. I am using the USB output from the PS but device manager and MAX see it as as a serial port. I will give this a try..

[Gregory]

Yes USB instruments often show up as a virtual COM port, and sometimes require a USB driver.

[Daddy-O]

The driver made the computer see it, and had to add in this string constant to look for the correct stuff. Power supply still does not come one, but one small step in the right direction. Thanks for help.

[Gregory]

"Power supply still does not come one, but one small step in the right direction. Thanks for help."
Can you explain this a little? Your LabVIEW program is not controlling the power supply as expected?
How do you get your executable onto the target machine? Do you create an installer and let LabVIEW automatically include any dependencies it needs?

[Daddy-O]

I had built this VI to write to a file required by the power supply called OP.log in C:\My Documents. It turns out that this machine did not have the my documents folder. I added the folder and everything is working fine now. Thanks for all the input!

[Gregory]

Great, glad you were successful!