Getting started with Torque Tool Ethernet Driver

[LP_12507955]

As per the original post.

Hi,

I have the similar problem as NM_12850686. Could you please share the port issue solution?

Here is my setup:

Cleco Controller mPro200 - Open Protocol - Port 9002 - Activated

Cleco Controller mPro200 - TorqueNet- Port 12345 - Activated

Cleco Controller mPro200 id : 192.168.50.20

 

KepServerEx - Channel:TorqueToolEthernet - Device:Cleco (Open Protocol - 192.168.50.20 - Port: 9002)

Both the controller and the port can be ping successfully from the PC.

However, none of the tags receives information from Cleco. Could you please look into this?

Thank you,
LP

[pshashipreetham]

Hi @LP_12507955 

My Observations are 

Network connectivity is not the issue

• Your Test-NetConnection result shows port 9002 is reachable.

• Device IP is correct.

• Controller port is activated, and protocol is set to Open Protocol.
  
  

No MID 001 Communication happening

From your Kepware logs and screenshots:

• Kepware is not receiving responses from Cleco (timeouts or blank reads).

• Likely causes:

  • Incorrect MID polling config

  • Missing handshake

  • Wrong Job selection, or missing Start request MID

  • Cleco not configured to auto-transmit data

Solutions May be:

1. Controller-Side Validation

• On the Cleco mPro200, go to:

  • Menu > Protocol Settings > Open Protocol > Advanced

  • Ensure MID 001, 005, 006, 0062, 0064 are activated for replies

  • Set Primary Trace MID = 0064 or the expected MID your system should respond with

  • Enable Auto-send MID 0064 on job completion

Also check:

• "Controller Auto Start Job" is enabled

• Job ID is pre-assigned or ready to be started from OPC (Kepware)

Why this matters: If the controller is waiting for a MID 003 (Job Select) or MID 001 handshake, and it's not received, it won't push out MID 0064 (tightening results).

2. Kepware Device Settings

From your screenshot:

• Job Select Method: Try setting it to None initially for testing

• Start MID: Enable “Send MID 003” to select Job

• Enable Auto-send MID 0064 (result transmission from Cleco to Kepware)

Also:

• Increase Timeout from 5000 ms to 10000 ms for slow reply testing

• Ensure Device Read Mode is set to either On Demand or Cyclic (not “None”)

3. Trigger Initial MID

Kepware won’t automatically initiate MID 001 unless the driver does so or tags are manually activated.

To verify:

1. Go to Quick Client

2. Right-click any writable command tag (like MID_003_JobNumber) and write a valid job number

3. Then write 1 to the Send_Job tag (or equivalent) to send MID 003

4. Observe if Cleco replies with MID 006 or MID 0064

If this works, the issue is that the controller needs an explicit MID trigger to start sending.

Use UaExpert to Compare

If the MES is not reading but UaExpert is:

• Use UaExpert to create a monitored item on tag like Torque or ResultID

• Perform a real tightening operation on Cleco

• See if MID 0064 values populate

If UaExpert sees values but Kepware does not:

• Likely a job trigger/start MID missing from Kepware

• Or MES needs to send command MID to initiate data

5. Firmware or Protocol Mismatch

Check:

• Cleco firmware matches the Open Protocol version expected by Kepware

• If Cleco uses a custom MID map, the default OPC tag structure in Kepware may not match

Use Cleco’s documentation to verify which MIDs are enabled and what data formats are used.

Thanks,

[NM_12850686]

Things I learned - you can't read tool_enable only write it. 

You need to add every tool in kepserver.

They will have the same IP address as the controller but the port that is mapped to them in the controller.

You will need to address the tool  as toolname.tagname  when controlling remotely. I used ignition and OPC

Easiest thing to get working is reading the CommChanelId - should match the toolgrp in the cleco controller.

Also you can send TimeSync and read back time.

If you get those working through quick client, you're good. 

I found Cleco MPRO  was best controlled via app numbers.  I am using no MIDs directly. 

I am sending enables, app numbers, and reading back LTRs. All those are available in the tag library when you add a new tag. 

I mostly got tripped up on needing to use app numbers and on needing to use the tag library in KepServer.  When I tried to use MIDs to start communication for example, that was built into kepserver. If you let the tool do the work, it is easier.