multiIO / Supported devices / Mettler Toledo
Mettler Toledo IND terminals
Eight IND terminals across five format cores. Standard Continuous is byte-identical in every manual that prints it, and the Level 0 SICS response is the same field everywhere, so most of this suite is one verified parser serving many terminals.
8
Models
5
Output formats
22
Catalogue entries
⚠ Every Mettler Toledo terminal leaves the factory assigned to Demand output — a site-built print template rather than a wire format — so no catalogued format is their factory default. See the note on defaults below.
Models and the formats they offer
| Model | Output formats | Default baud |
|---|---|---|
| IND131 | Continuous · Continuous-Extended · SICS | 9600 |
| IND246 | Continuous · Continuous-Extended · SICS | 9600 |
| IND331 | Continuous · Continuous-Extended · SICS | 9600 |
| IND360 | SICS · SICS SIX1 | 9600 |
| IND400 | Continuous · SICS | 9600 |
| IND560 | Continuous · SICS | 9600 |
| IND700 | Continuous · SICS · SICS Level 2 | 9600 |
| IND780 | Continuous · Continuous-Extended · SICS · SICS Level 2 | 9600 |
The formats
Each one is a separate parser, because which format a site chose is not reliably detectable from the stream — you pick what the box's own menu is set to. Example frames below are produced by that format's own encoder and read back through its own parser.
Continuous
Standard Continuous Output
The fixed, binary, free-running telegram an MT terminal streams when a port's connection assignment is set to Continuous Output — roughly twenty times a second above 4800 baud. STX, three status words, a six-digit displayed weight, a six-digit tare, CR, and an optional checksum.
The weight field carries no decimal point: its position has to be recovered from a status word. And a terminal only ever transmits one displayed value plus its tare, so gross, net and tare are derived rather than read — which means getting the status word wrong does not produce a wrong-looking number, it produces a plausible one.
Example frame — IND131, a stable 12.34 kg gross reading
<STX>,1···1234···000<CR>
02 2C 31 20 20 20 31 32 33 34 20 20 20 30 30 30 0D
17 bytes · decodes back to 12.34 kg
Verified against: IND560 71209394 R01 Appendix D Table D-3 · IND246 64084453 R05 Appendix E.3 Table E-1 · IND780 64057242 R15 Appendix D Table D-6
Continuous-Extended
Continuous — Extended Output
The 24-byte extension of the standard telegram, adding a node address and a fourth status byte. Unlike the standard frame its weight field carries its own sign and decimal point, so nothing has to be recovered from a status word.
The status bytes are where the IND246 and IND780 genuinely differ — the IND780 adds units, a weight-range field and application bits the IND246 manual marks unused. We keep the two tables separate rather than merging them into a superset, because a merged table decodes values a given terminal cannot emit and quietly misreports the ones it can.
Example frame — IND131, a stable 12.34 kg gross reading
<01>1"!······12.34····0.00<CR>
01 31 22 21 20 20 20 20 20 20 31 32 2E 33 34 20 20 20 20 30 2E 30 30 0D
24 bytes · decodes back to 12.34 kg
Verified against: IND246 64084453 R05 Appendix E.3.3 Table E-5 · IND780 64057242 R15 Appendix D Table D-10
SICS
MT-SICS Level 0
The standard S, SI and SIR command and response — send stable weight, send immediately, send immediately and repeat. A status character and a ten-character right-justified weight field with its unit.
That field is ten characters wide, not eleven. An earlier revision of this parser used eleven, which is off by one and would not have matched a real terminal — caught by reading a rendered page rather than trusting text extraction, which miscounts the spaces fixed-width frames depend on. Overload and underload collapse the telegram to a status character with no weight field at all.
Example frame — IND131, a stable 12.34 kg gross reading
S·S······12.34·kg<CR><LF>
53 20 53 20 20 20 20 20 20 31 32 2E 33 34 20 6B 67 0D 0A
19 bytes · decodes back to 12.34 kg
Verified against: IND246 64084453 R05 Appendix E.6.3.1 · IND560 71209394 R01 Appendix D · IND780 64057242 R15 Appendix D.7
SICS Level 2
MT-SICS Level 2 — SX, SXI, SXIR
The combined record: gross, net and tare in one response, each a ten-character field with its own tag and unit. Offered by the IND780 and IND700.
⚠ This is a response, never a stream. The combined record is only ever emitted when a host sends SX, SXI or SXIR, and none of the terminal's free-running continuous modes carry gross and net and tare together. The gateway's input side is receive-only today, so a real deployment needs the port primed externally until that changes. The IND246 and IND560 do not implement it at all — both manuals cap their SICS appendix at Levels 0 and 1.
Example frame — IND700, a stable 12.34 kg gross reading
SX·S·G······12.34·kg···N······12.34·kg···T·······0.00·kg<CR><LF>
53 58 20 53 20 47 20 20 20 20 20 20 31 32 2E 33 34 20 6B 67 20 20 20 4E 20 20 20 20 20 20 31 32 2E 33 34 20 6B 67 20 20 20 54 20 20 20 20 20 20 20 30 2E 30 30 20 6B 67 0D 0A
58 bytes · decodes back to 12.34 kg
Verified against: IND780 64057242 R15 Appendix D.7.10 · IND700 30753872 C §5.3.5.8
SICS SIX1
MT-SICS SIX1
One line carrying gross, net, tare, the unit and a row of status flags — which is what earns it an entry of its own. On the IND360 it is the only format that reports all three weights at once.
Several of its documented fields are fixed constants on this terminal, so we parse them for framing and deliberately do not report them: publishing a constant as telemetry invites a consumer to depend on it. Note that on the IND360 this command is served over TCP/IP rather than a serial port — the bytes are identical, which is the whole point of keeping the transport away from the parser.
Example frame — IND360, a stable 12.34 kg gross reading
SIX1·S·0·N·N·R·0·0·0·1·N·12.34·12.34·0.00·kg<CR><LF>
53 49 58 31 20 53 20 30 20 4E 20 4E 20 52 20 30 20 30 20 30 20 31 20 4E 20 31 32 2E 33 34 20 31 32 2E 33 34 20 30 2E 30 30 20 6B 67 0D 0A
46 bytes · decodes back to 12.34 kg
Verified against: IND360 30654701 L Appendix C.3, with the worked example at C.3.4
Is your indicator here?
If it is, it works out of the box — pick the model and the format its menu is set to, and readings publish over MQTT, Modbus TCP, OPC UA, REST and six more transports at once. If it is not, describe the line's fields in the console and multiIO decodes it anyway, or send us the manual's serial chapter: that is how most of this catalogue got here.