topic Re: Use of MID 0008 with Torque tool ethernet driver in Kepware

Use of MID 0008 with Torque tool ethernet driver

PK_9967706 — Wed, 08 May 2024 14:52:41 GMT

Hello,

I am trying to configure Atlas Copco Micro Torque MTF 6000 in Kepware and as per device documentation the MIDs for this device are used differeltly than that of full Atlas Copco Open Protocol. e.g.

My question here is, how should I use the MID 008 to read the last torue value, I know that in device settings there is an option to enable the use of generic subscibe which enables MID 008, but what will be the tag address then for torque value? or it will be same "LTR_TORQUE_VALUE".

(FYI I am a Thingworx developer & have a limited orientation towards industrial protocols & their working)

Re: Use of MID 0008 with Torque tool ethernet driver

cmorehead — Thu, 09 May 2024 17:19:36 GMT

@PK_9967706,

All you need to do is enable the parameter listed in the following knowledge base article:

https://www.ptc.com/en/support/article/CS417352

The tag address "LTR_TORQUE_VALUE" would be the same.

Thanks,

*Chris

Re: Use of MID 0008 with Torque tool ethernet driver

cmorehead — Wed, 10 Jul 2024 19:48:57 GMT

Take away resolution from submitted case:

"For clarification on the MTF6000 MIDs you requested, we cannot directly consider the LTR tag addresses.
We need to configure MID1202.
If you look on page 16 in the "Atlas-Copco-MT-Focus-6000-Open-Protocol.pdf" document and check the parameters under this - 2.4.12 Notes on mid 1202 Operation result object data.
You can see the different tags that you need to create related to torque and other parameters."

Re: Use of MID 0008 with Torque tool ethernet driver

adrake — Mon, 09 Feb 2026 20:32:24 GMT

Relating to this case, I have configured the necessary 1202 tags for an Atlas Copco MT Focus 6000, but still with 'Out of Service' Tags. Interestingly, all of the New Data tags show 'good value' but as 0. Communication is the only block that successfully works. When I enable the CS417352 article to force to MID 0008, the kepware logs still claim it is trying to read from MID 0060, and 1202 tags still show bad quality.