The MI has a built-in Modbus / TCP server that provides measurement data for connected clients. Clients can connect and read the Modbus registers by using function code 3. Each active MI app updates its registers that depend on app type. The following tables list the registers.
The following table lists the Modbus registers of a Refractometer app. The register address n is the appslot number.
Name | Address | Type | Function |
---|---|---|---|
Status | n032 | 32-BYTE STRING | Refractometer status message |
Conc | n050 | FLOAT | Final concentration value |
Temp | n052 | FLOAT | Process temperature |
Calc | n054 | FLOAT | Calculated concentration value |
nD | n056 | FLOAT | Calculated refractive index value |
S/N | n098 | 32-BYTE STRING | Refractometer serial number |
Ext wash | 1n000 | 4-BYTE INT | External wash request input |
The external wash request includes a state machine to prevent continuous wash triggering that would wear out the sensor, so there must be a resetting value (zero) between each wash triggering values (ones).
The following table lists the Modbus registers of a Recipe app. The register address n is the appslot number.
Name | Address | Type | Function |
---|---|---|---|
Status | n032 | 32-BYTE STRING | Refractometer status message |
Conc | n050 | FLOAT | Final concentration value |
Temp | n052 | FLOAT | Process temperature |
Calc | n054 | FLOAT | Calculated concentration value |
nD | n056 | FLOAT | Calculated refractive index value |
S/N | n098 | 32-BYTE STRING | Refractometer serial number |
Ext wash | 1n200 | 4-BYTE INT | Recipe identification number input |
Avoid overloading the MI with very frequent Modbus requests. The shortest recommended interval between Modbus requests is 100 ms. |