This Article Applies From:
DeMeter |
Introduction
The present articles explains the minimum requirements to connect a tightening device to DeMeter using Open Protocol.
You will also find a list of devices whose results have already been successfully retrieved in DeMeter using Open Protocol.
1 - Suggested readings before diving-in
You may benefit from reading the following articles before going any further:
2 - Open Protocol compatibility requirements
2.1 - Overview
Open Protocol is an open source protocol whose purpose is to allow different Tightening Devices brand to connect and work together.
DeMeter uses Open Protocol to connect then retrieve Tightening results. In that particular setup, DeMeter is the Client, i.e. it will connect to the target tightening device who acts as a server.
However, a minimum number of MIDs must be available for DeMeter to be able to retrieve the tightening results.
The next sections will list the MIDs being necessary to ensure:
- DeMeter connects to the target device.
- DeMeter retrieves tightening numerical results (real time and off-line).
- DeMeter retrieves tightening curves.
Note: DeMeter can not retrieve tightening results via Open Protocol from Multi-spindle devices.
2.2 - Connection and communication MIDs requirements
The target asset must be compatible with the following MIDs handling Open Protocol connections - note that DeMeter will always try to connect with the higher MID revision, then work its way down if the target device reject the mid revision.
| MID Number | Supported MID Revisions | MID Purpose |
| 0001 | Revision 6 and below | Message to start Open Protocol communication with the target asset. |
| 0002 | Revision 6 and below | Message sent by the asset in response to MID 0001. |
| 0003 | N/A | Message from to disable communication. |
| 0004 | N/A | Negative acknowledge of a previous MID. |
| 0005 | N/A | Positive acknowledge of a previous MID. |
2.3 - Requirements to retrieve Numerical Results via Open Protocol
DeMeter can retrieve real-time results and also older results from the controllers. Both behaviors require the target asset to support 2 different sets of specific MIDs.
2.3.1 - Numerical results retrieval
| MID Number | Supported MID Revisions | MID Purpose |
| 0060 | N/A | Subscribe to Real Time tightening results. |
| 0061 | Revision 6 and below | Send numerical tightening results alongside identifiers. Results include the identifiers: - If controller implements Revision 1, 2, or 3 of the MID, a single identifier will be retrieved. - If controller implements Revision 4 or higher of the MID, up to 4 identifiers can be retrieved via the MID. |
| 0062 | N/A | Acknowledge last tightening result data. |
| 0063 | N/A | Unsubscribe to last tightening result data. |
Note: to use Pivotware's Action Selection step, third party controllers must implement MID 0061 Revision 4 at the very least to retrieve all necessary Identifiers.
2.3.2 - Off-line results retrieval
The MIDs listed below allow DeMeter to retrieve tightening results acquired while connection between the target asset and DeMeter was down.
If the target asset does not support these MIDs, DeMeter will still be able to retrieve tightenings numerical results in real time, but any communication drop will result in traceability loss.
| MID Number | Supported MID Revisions | MID Purpose |
| 0064 | N/A | Upload request of a specific result number. |
| 0065 | Revision 6 and below | Upload of a specific result number. |
2.4 - Requirements to retrieve Curves via Open Protocol
The MIDs listed below allow DeMeter to retrieve curves associated to tightening results.
If the target asset does not support these MIDs, DeMeter will still be able to retrieve tightening numerical results in real time, but no curves will be associated to the results.
Note: Open Protocol curves have 500 points.
| MID Number | Supported MID Revisions | MID Purpose |
| 0008 | Revision 1 | Subscribe to a specific application data message. |
| 0900 | Revision 1 | Trace curve data message. |
| 0009 | Revision 1 | Unsubscribe to application data message. |
3 - Third party tightening devices having successfully been connected to DeMeter
The following is a list of tightening system that have been successfully connected to DeMeter.
Note: depending on the firmware revision and licensing policy of the manufacturer, there could be issue / restrictions when trying to connect to the listed device.
Desoutter is only responsible for the DeMeter side of communications.
Desoutter is not in any way responsible for the list of supported MIDs and their revisions for the listed controllers.
DeMeter does not support Multi Spindle devices over Open Protocol.
| Manufacturer - Controller model | Firmware version | Numerical Results | Curves | Offline data | Comments |
| Atlas Copco PF4000 | World 14 (Minimum) | Yes | Yes | Yes for Numerical Results No for Curves | |
| Atlas Copco PF6000 | 3.1.14.98 (Minimum) | Yes | Yes (*) | Yes | (*) A specific Atlas Copco license is required. |
| Stanley | Yes | Yes | |||
| ESTIC | GA 1370 | Yes | No | Only works with early releases of the controller firmware. | |
| SCS FIM-EVO | 3.1.13.3 | Yes | No | Used alongside Digital Wrench Freedoom 4s |