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

[MaxBFCCL]

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

[santo_13]

Does Chroma confirm that their driver dlls work with Win11?

[MaxBFCCL]

We have contacted Chroma for an answer in regards to the dll driver.

In the mean time we have managed to establish communication with the devices with the attached code snippet.

While the device give out answers a time out error occurs every time as seen in the "Readout" attachment.

Is there a fix to get rid of this error?

[Melo_Yu]

Hi MaxBFCCL:

I met the same issue as you. My PC is win10 64bit and I install 2 version of Labview in my PC.

2018 Labview 32bit & 2021 Labview 64bit.

When I use LV2018 to remote control Chroma63630, it doesn't work. 

But when I use LV2021, it works.

Worth to mention that, there are 2 version of 63630 labview vi in Chroma's website. 32bit & 64bit.

I try these versions, only LV2021(64bit)+Chroma vi(64bit) works.

I called Chroma Technical support and their feedback is use NI-MAX spy(NI-Max I/O Trace) to monitor I/O trace.

Once 64bit works well, the NI -MAX spy could capture correct VISA information.

I am still waitting for their FAE's feedback.

Any update, I will notice you. Tks!

Thanks!

[Melo_Yu]

problem solved！

Copy chr63600_32.dll to C:\Program Files(x86)\IVI\Foundation\IVI\Bin.

Then it works. Remote control successfully.

[TaoHT]

Hi man,

Can you share the Chr63600_32.dll? I cannot find it in internet

[carlos_camargo]

located in zip file

https://www.chromaate.com/en/data_center/63600_series_dc_electronic_load