Problem Initializing Watlow F4T LabVIEW Driver (Ethernet)

[sanjib321]

We have environmental chamber from Associated Environment Systems with Watlow F4T Controller. Watlow has a LabVIEW driver (version 6.0.109). Following is the information on the LabVIEW Environment

LabVIEW Version 2015.

NI-488.2 Version 17.6.0

NI-VISA Version 17.5.0

Watlow F4T has an ethernet output and I can access it when I enter the IP address in the browser but when I run a simple initialization step it gives me Initialization Failed stating Error connecting to GPIB driver with NI-488.2 driver may not be installed as one of the possible reason.  Screenshot attached.

I contacted Watlow and they do not understand why it show error relating to GPIB driver since Standard Watbus does not use GPIB for communications. And I also verified I have NI-488.2 version 17.6.0 is compatible with LabVIEW 2015. So, I do not understand why it is showing error in Initialization since I can verify the communication between PC and F4T by entering IP address in the browser but I get this error with LabVIEW.

[Kyle97330]

It's probably a problem with the constant you have in the VISA field.  Unless that's an alias you set up in NI-MAX, you can't just stick a bare IP address in there.

Try using this guide to set up a connection through MAX first, and then choose that connection from the drop-down.

If that doesn't help, it would also help if you could post the actual VI generating the error, not just a screenshot of it being called.

[sanjib321]

Kyle97330 thank you for your response. I will follow the guide and post an update.

[MrJackHamilton]

Ping the Watlow from the CMD line, see if it responses.

Additionally, is your firewall up?... If so, it will block any TCP/IP calls. [So will Malware protection applications]

Try:

1 Take the firewall down completely, for all domains.

2. Ping the unit.

3. Try the VI again...

Regards

Jack

[sanjib321]

 MrJackHamilton

Thank you for your suggestion.

The Watlow controller is part of Environmental Chamber from Associated Environment Systems and looks like there is another interface board between the controller and ethernet port in the chamber. I am in contact with Associated Environment to figure out if I can access F4T controller via the ethernet port. 

[sanjib321 · Accepted solution]

I had Watlow F4T Controller installed in Environmental Chamber from Associated Environmental Systems and I was able to access F4T controller when I used the service port. Regular Ethernet port is for AESXchange program from the Associated Environmental Systems.

After connecting to Service Port and typing in IP address to Watlow F4T Initialization function I confirmed the device was detected and now at least it is working as expected.