Not able to connect to Ingersoll Rand Torque tool

Developer
,
1

Anyone was able to connect to Ingersoll Rand Torque tool ? We are trying to connect to the QCX torque tool and keep on getting following message. We are trying to connect it via standard open protocol but we didn’t have any luck so far. Any hints?

Nov 07 21:16:32 EIO-01-271D5F67 cell[4545]: 21:16:32.285Z ERROR torque-op: Client connection error: connect EHOSTUNREACH 10.0.5.5:4545. This likely means you have the wrong controller IP address (10.0.5.5) or port (4545), or your device is not properly configured for Open Protocol. Please check your torque controller and refer to the controller’s manual. (hwid=c971a0bff944)

2

Hi Sandeep,

Could you please share more details about the configurations applied and how the 2 devices are connected? Is the torque tool controller connected to the Tulip Edge LAN port or via some other connection?

EHOSTUNREACH generally means a networking issue, but it may be due to a configuration conflict.

Thank you,
Damiana Gonzales

3

Hi Damiana,

Tulip and torque tool is connected through Edge IO. Torque tool is connected to LAN port on Edge IO and Edge IO displaying ip address as 10.0.5.1 in downstream.

  1. I’ve given controller an 10.0.5.5 ip address . Also, enabled PF-OP protocol on 4545 port.
  2. I’ve enabled ip aliasing mentioned on following post and tried that ip address in Tulip.

https://irtoolhelp.ingersollrand.com/hc/en-us/article_attachments/4406924689811

Both the methods were not able to communicate to the tool.

In the Tulip LAN settings, it shows ‘connected’ though.

I tried both torque-op driver and ingersoll-rand-qx drivers. I’m not sure which one to use.

4

Hi @sandeep.ingale,

Thank you for this information. The Torque-OP is the correct driver to use here.
If possible, could you please test the same, but with a network switch between the Torque controller and the Edge IO device?

Thank you,
Damiana Gonzales

5

We tried network switch and it didn’t work.

6

Hi Sandeep,

I’m sorry this has been tricky! Another thing we talked about trying is connecting the torque controller on the WAN side of the connection.

If that still doesn’t work, let me know and I will make a support ticket for you with our support team, as they will be able to debug this at a deeper level.

7

I’ve a working session scheduled with Tulip and Ingersoll Rand. I will write down the notes and share with the community so that other will be benefited.

2 Likes