We have been using an Ingersoll Rand INSIGHTqcx to track torque values in Tulip for the past year for our production line with little to no issues. We are adding more stations and need to add a second controller device since more torque tools are required and we have maxed out our tool licenses on the first controller.
The issue is, despite configuring the second torque controller exactly the same as the first, I keep receiving an “internal server error [500]” when I attempt to enable the tool in the app. I need to get this communicating with Tulip ASAP since we are looking to get these new stations up an running in the next 2 weeks.
Here is some information on the setup of the new Ingersoll Rand INSIGHTqcx device that is not communicating:
INSIGHTqcx Port IP:10.0.5.2 connected to network switch
Tool Port: 4551
Set to External-MES
Edge IO is connected to wifi and configured with Torque OP standard open protocol: 10.0.5.2:4551
Edge IO connected to network switch at the LAN port. Assigned 10.0.5.1.
The app I’m using to test calls the edge IO directly using the “Run Device Function”, “Torque Tool Open Protocol” trigger to enable the device on a button push. This is when I receive the internal server error.
I have tried changing the controller’s port IP, the tool port number, and many other things to get this to work, but no luck. I need some help to figure out what I’m missing here an why the same setup isn’t working as the first controller.
Thank you!