LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VISA device error in NI MAX and cannot connect to the hardware

Solved!
Go to solution

I was trying to connect with my HVDC power supply from Delta Elktronika. It shows it cannot initialize the hardware. This issue exist also with some other hardware as well.

 

1. Checked NI MAX

       -NI max couldn't connect to the hardware. every parameters are checked and are correct in NI MAX

        

RepMat_0-1731924725589.png

 

2.tried to setup a new device

     - couldn't open a visa session

RepMat_1-1731924809576.png

 

3.Checked the visa.dll in system32 folder

   -the file can be seen in the folder.

4. system restarted

    - Ni Max couldn't recognize the hardware.

What would be the possible solution?

0 Kudos
Message 1 of 5
(102 Views)

There defintely is some sort of disconnect!

 

In MAX it shows TCPIP::192.168.0.3::8462::SOCKET but you try to connect to TCPIP::192.168.0.3::INSTR.

 

That is not the same!

 

The first is a TCP-IP socket connection to a custom port number 8462. Have you checked the network settings of your Delta Power Supply to enable this interface and what possible communication mode it is in? Is your device connected to the ethernet interface with subnet address 192.168.0.x on your computer?

 

You need to make sure to set the Delta Power Supplies for the programming source for voltage, current and/or power to 'eth' via the front menu or the web interface.

 

The second address only will work if the Delta Power Supply confirms to VXI-11 and/or HiSlip. It will then attempt to connect to the default port number 111 for VXI-11 to query for the actually used service ports or to 4880 for HiSlip. As far as I can see, the Delta Power Supplies only support a socket connection and not VXI-11 or HiSlip.

Rolf Kalbermatter
My Blog
0 Kudos
Message 2 of 5
(64 Views)

sorry dont get confused.

first one is the driver already configured and the second one is when i tried to add a new device.

 

yes,the programming source was changed to ethernet. i was also able to ping the ip address

RepMat_0-1731940404369.png

 

PingSucceeded          : True
PingReplyDetails (RTT) : 1 ms
TcpTestSucceeded       : False

 

seems like specific port not accepting any connection

 

but still NI MAX didnt recognize the Delta power supply

 

0 Kudos
Message 3 of 5
(55 Views)

ping only confirms that the device has a working IP socket which has ICMP replies enabled. This is on IP network level and below your TCP/IP network layer.

 

The device may only answer on its default port 8462 if it is specifically set to listen on the ethernet port for remote connections, which I explained how to do:

 

You need to make sure to set the Delta Power Supplies for the programming source for voltage, current and/or power to 'eth' via the front menu or the web interface.

Also your device may use a different default port number for TCP/IP remote programming. I only checked the SM15K programming manual where it states that it uses 8462.

 

If you start the NI Max Wizard to add a new device and enter a TCP/IP address but specify the device to be a TCP/IP Instr resource, NI Max assumes that the device properly implements either VXI-11 or HiSlip and will start to query the according service enumeration ports as specified by those standards.

 

Without VXI-11 or HiSlip there is no way for NI-Max to detect the device. If Delta even implements some auto-detection mechanism, it seems to be their own proprietary one and NI-Max can't go and try to support all the different possible proprietary auto-detection services. It supports VXI-11 and HiSlip and that is THE industry standard in Test & Measurement.

 

You will need to select in the NI Max Add Device Wizard to connect to a TCP/IP Socket resource. This tells NI-Max that there is really no standard way to try to enumerate the available resources on the device and all it will do is try to connect to that port and if that succeeds it will claim success. Maybe it will also try to send an *IDN? query but it can't interpret a failure to receive a valid answer as a real failure. Most devices, except many Test & Measurement devices, but even there not all, will not understand this query command at all and just give you a stare blank, or roll on their back and play dead, when receiving that command.

 

Of course there is also a possibility that your network cabling is bad (happens much more often than you would think and it can show intermittent problems like low level things like ping working and other things not). Or your network setup is not quite right. Or your Delta device got damaged or the firmware corrupted somehow.

Rolf Kalbermatter
My Blog
Message 4 of 5
(38 Views)
Solution
Accepted by topic author RepMat

updated to new firmware solved the problem

0 Kudos
Message 5 of 5
(22 Views)