12-23-2015 04:50 AM
I am using the Rotronic HC2-ic102 probe. The correct driver for the probe is installed and the probe works on another computer system using the same Labview code. When I use the HC2 probe on my computer system i get the following error,
Could it be that the computer system I am using has two seperate drives a C: Drive and a 😧 Drive. Labview 2012 is installed on the 😧 Drive. I have tried running the Labview code on both drives but I still get the same error. The labview code is a single Vi saved in a folder with the DLL supplied by rotronic. Does anyone have an ideas why I am getting this error?
12-23-2015 05:34 AM
The error description says 'TIMEOUT_ERROR' - which is the error thrown by the .NET library - it sounds like the library is not receiving a response from the device so it is timing out. How is it connected? Is it on a different port (e.g. COM2 instead of COM1 if it's serial)? How is the port specified?
Can you show us your code?
12-23-2015 05:58 AM
How is it connected?
The probe is connected through a USB port, Here is a screenshot of the Rotronic USB port connection.
Is it on a different port (e.g. COM2 instead of COM1 if it's serial)? How is the port specified?
The port is specified as a USB port located at Port 4.
Can you show us your code?
Here is a screenshot of the code below.
12-23-2015 06:13 AM - edited 12-23-2015 06:13 AM
The screenshot you posted was too small to view the text.
The error occurs at 'readdata' because that's probably the first time the code actually tries to communicate with the device and it gets no response.
One of the configuration settings (e.g. port, port address, device address etc.) is wrong.
Does the manufacturer have a utility that allows you to read the device? Does that work?
12-23-2015 06:34 AM
Here is the screenshot of the port again,
Does the manufacturer have a utility that allows you to read the device? Does that work?
Yes the manufacturer has their own licensed software which can read information from the device.
12-23-2015 06:40 AM - edited 12-23-2015 06:40 AM
@coalminer2109 wrote:
Does the manufacturer have a utility that allows you to read the device? Does that work?
Yes the manufacturer has their own licensed software which can read information from the device.
And what does it say it is using for the Port / Port Address when you use their software to read the data from the device?
According to the screenshot, you have at least 4 "Port 4"s according to that USB View software so "Port 4" isn't enough information to uniquely describe the 'location' of the device.
I suggest you contact the manufacturer or read the documentation and find out how to determine the correct configuration.
12-23-2015 06:45 AM
12-23-2015 06:56 AM
It is a USB device. It is only shown in device manager as a USB port it doesn't have a COM Port assigned to it.
12-29-2015 07:17 AM
Hello,
Which port and port adress are you specifying in your VI?
Also, why is there a coercion dot for the wire into your first Invoke Node?
Regards,
Christopher
02-10-2021 05:31 AM
Hi! Has this been solved by any chance? I am using the same HC2-IC102 probe, with the same USB connection and I am getting the same exact error, as if the driver were corrupted. Did you figure out where the error was and how to solve it? Thanks!