Quantcast
Channel: Instrument Control (GPIB, Serial, VISA, IVI) topics
Viewing all articles
Browse latest Browse all 5566

Chroma 63600 Series doesn't work after migrating to new PC

$
0
0

Hello all,

 

after exchanging a PC in a working measurement setup from a Win7 to a Win11 machine, LabView 2012 is unable to Communicate with a Chroma 63600 device (Electronic Load Rack). I am using LabView 2012 Version 12.0 (32 Bit).

Chroma loads are connected to the PC via an ethernet switch. Other devices like scope, AC-Source, Power Meter and a Mux are working properly and can be controlled by LabView as expected. All devices, including chroma loads can be pinged without any issues.

LabView is trying to connect to Chroma 63600 Series device with dll-file drivers. Updating those to a newer version also did not help but instead produced the error seen in the "entryPointError" attachment. Also, the new drivers are claimed to be compatible only with LabView version 2014 and later.

Attached a comparison of the two VI's which are used for communication between "oldDrivers" and "newDrivers".

 

All file paths and LabView VI's have exactly the same on both new and old PC.

Another weird observation is that NI MAX V15 is unable to detect any devices connected to the Win11 machine, including devices that are connected via USB. Rolling back NI MAX to V5.5 show same, no device can be detected even though LabView is able to communicate with all devices except chroma loads. 

 

Chroma loads port/IP address has following format:

TCPI0::XXX.YYY.W.ZZZ::2101::SOCKET

 

Is there any known issue with LabView 2012 and Win 11 regarding the above topic?

Is there any workaround to achieve communication with chroma loads and LabView 2012 without the need of additional dll files?

 

Regards


Viewing all articles
Browse latest Browse all 5566

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>