multiIO / Supported devices / OHAUS
OHAUS indicators
The Defender range plus the 7000-series T72XW and the CE35, across six format cores — including both an OHAUS-native ASCII string and a Mettler-emulating binary telegram, selectable on the same box.
6
Models
6
Output formats
18
Catalogue entries
⚠ Like Mettler Toledo, every OHAUS terminal here leaves the factory assigned to Demand output, so no catalogued format is their factory default. OHAUS also marks defaults in bold rather than in words, which text extraction drops entirely — every default and every absence of one was confirmed by rendering the page.
Models and the formats they offer
| Model | Output formats | Default baud |
|---|---|---|
| CE35 | Default ★ | 9600 |
| Defender 2500 | MT-Continuous · OH-Continuous · SICS | 9600 |
| Defender 3000 | MT-Continuous · OH-Continuous · SICS | 9600 |
| Defender 5000 | 3835 · MT-Continuous · OH-Continuous · SICS · SICS Level 2 | 9600 |
| Defender 6000 | MT-Continuous · OH-Continuous · SICS | 9600 |
| T72XW | MT-Continuous · OH-Continuous · SICS | 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.
MT-Continuous
MT-Continuous
The fixed binary telegram these indicators stream with a port set to MT-Continuous — STX, three status bytes, a six-digit displayed weight, a six-digit tare, CR and an optional checksum.
This is the same Standard Continuous Output the Mettler terminals emit, but the OHAUS status byte carrying the unit code has its own table — which is exactly why this is a separate parser rather than a reuse of the Mettler one. As there, one displayed value plus tare means gross, net and tare are derived rather than read.
Example frame — Defender 2500, 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: Defender 5000 30430958 F Appendix A · Defender 2500 30809939 A §10.1 · 7000-series and T72XW 30131338 D Appendix C
OH-Continuous
OH-Continuous — the OHAUS native string
The fixed-width ASCII string these indicators stream with a port set to OH-Continuous: a right-justified weight, a unit field, a stability character and a two-character type field.
Unlike the MT telegram this carries a single labelled value — net or gross, not both — so only the field the stream actually reports is populated, and nothing is derived. The unit field goes all spaces if unit display is switched off in the print-content menu, which is a valid frame rather than a broken one.
Example frame — Defender 2500, a stable 12.34 kg gross reading
······12.34····kg····G<CR><LF>
20 20 20 20 20 20 31 32 2E 33 34 20 20 20 20 6B 67 20 20 20 20 47 0D 0A
24 bytes · decodes back to 12.34 kg
Verified against: Defender 5000 30430958 F §5.5 · Defender 2500 30809939 A §10.4
SICS
MT-SICS Level 0
The S, SI and SIR command and response, documented for the Defender indicators in their own MT-SICS appendix. MT-SICS is a cross-vendor standard, so the wire format matches the Mettler Toledo Level 0 telegram exactly.
Implemented as a self-contained OHAUS parser with no dependency on the Mettler assembly. That duplication is deliberate — a driver suite is a shipping boundary, so one family must never reference another.
Example frame — Defender 2500, 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: Defender 5000 30430958 Appendix B · Defender 2500 30809939 §10.2
SICS Level 2
MT-SICS Level 2 — SX, SXI, SXIR
The combined gross, net and tare record, documented for the Defender 5000 in its MT-SICS appendix.
Same receive-only caveat as the Mettler Level 2 entry: the combined record is only ever emitted in response to a host command, so as a reader it needs something to poll it. Its primary use here is the serial-output emulation, where the gateway is the one answering.
Example frame — Defender 5000, 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: Defender 5000 30430958 Appendix B
3835
3835 — polled command and response
Not a free-running stream but a polled format: a host sends single-letter commands terminated by CR and gets a weight telegram, a status reply, or a documented error reply for anything unrecognised. Only the Defender 5000 manual documents it, so it ships for that model only.
Over-capacity and under-capacity fill the weight field with a repeated fill character rather than sending a number, so those frames carry a status and no value. We implement both faces — decoding the telegram as a reader, and answering the poll set as an emulated indicator.
Example frame — Defender 5000, a stable 12.34 kg gross reading
<LF>·12.340kg<CR>00<ETX>
0A 20 31 32 2E 33 34 30 6B 67 0D 30 30 03
14 bytes · decodes back to 12.34 kg
Verified against: Defender 5000 30430958 F Appendix C
Default
CE35 — the Scout print format
OHAUS' standard fixed-width continuous ASCII format as the CE35 emits it, documented as the New Scout Print Format: a right-justified weight, unit, stability character and mode field.
Overload and underload are not covered by OHAUS' published examples, so the tokens used follow OHAUS' own on-screen abbreviation convention for those conditions — flagged here because it is the one place in this family where a shape was inferred from the vendor's display rather than read from a serial table.
Example frame — CE35, a stable 12.34 kg gross reading
······12.34····kg·····<CR><LF>
20 20 20 20 20 20 31 32 2E 33 34 20 20 20 20 6B 67 20 20 20 20 20 0D 0A
24 bytes · decodes back to 12.34 kg
Verified against: OHAUS New Scout print format documentation
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.