X42 Monitoring
XMC-Fire — Fire Tank Monitoring HMI
User Manual
Installation · Commissioning · Configuration · Fault Finding
Audience: field technicians · x42monitoring.com
DOCUMENT STATUS: FRAMEWORK — DRAFT ONLY. Not for issue. All amber-highlighted placeholder items must be completed with hardware specifications and site-specific details before this manual is issued to technicians. Remove this banner before publishing.
Read this manual before installing or operating the device. Keep it with the equipment.
Contents
- Document control
- About this manual
- 1 Overview
- 2 Installation
- 3 First power-on and startup
- 4 Main screen guide (Home Multi)
- 5 Status indicators
- 6 Settings menu guide
- 7 Inputs and outputs
- 8 Alarms
- 9 Communications
- 10 Trending
- 11 Fault finding
- 12 Specifications quick reference
- Appendix A Error code table
- Appendix B Modbus register map summary
- Appendix C MQTT payload reference
- Appendix D Factory default restoration
- Legal notices
- Support and contact
Document control
| Field | Detail |
|---|---|
| Document title | XMC-Fire User Manual |
| Document number | [PLACEHOLDER] — doc number |
| Revision | [PLACEHOLDER] — e.g. Rev A |
| Issue date | [PLACEHOLDER] |
| Applies to firmware | [PLACEHOLDER] — version / range |
| Applies to hardware | [PLACEHOLDER] — model / variant codes |
| Prepared by | [PLACEHOLDER] |
| Approved by | [PLACEHOLDER] |
| Manufacturer | Kangaroo Kick Tech Pty Ltd trading as X42 Monitoring, ABN 66 679 196 073, Queensland, Australia |
Revision history
| Rev | Date | Description | Author |
|---|---|---|---|
| A | [PLACEHOLDER] | First issue | [PLACEHOLDER] |
About this manual
This manual covers installation, commissioning, configuration, and fault finding for the XMC-Fire HMI device. Steps are written for technicians who are familiar with industrial instrumentation and networking but who may not have worked with this device before.
Intended users
Installation, commissioning and servicing must be carried out only by a competent person: a technician with training, qualifications or experience in industrial instrumentation, low-voltage wiring and, where the device is connected to a fire protection system, the applicable fire protection service requirements.
Intended use
The XMC-Fire is intended for monitoring and signalling of water level in fire tanks and similar industrial storage vessels, and for transmitting that data to building management, SCADA and cloud systems. Any other use is outside the intended use of the product.
Safety notices used in this manual
Safety messages in this manual use the following signal words. Read and obey every safety message.
| Signal word | Meaning |
|---|---|
| DANGER | Hazardous situation that, if not avoided, will result in death or serious injury. |
| WARNING | Hazardous situation that, if not avoided, could result in death or serious injury. |
| CAUTION | Hazardous situation that, if not avoided, could result in minor or moderate injury. |
| NOTICE | Practice not related to personal injury: risk of equipment damage, data loss or process upset. |
| NOTE | Additional information that helps avoid a common mistake or improves the result. |
Related documents and standards
- XMD remote display user manual — [PLACEHOLDER] — document number
- XMC-Fire hardware datasheet — [PLACEHOLDER]
- Sensor manufacturer instructions — [PLACEHOLDER]
- AS 1851 Routine service of fire protection systems and equipment — service and record-keeping obligations for the tank the device monitors
- IEC/IEEE 82079-1 Preparation of information for use — structure and content of this manual
1 Overview
1.1 What the XMC-Fire does
The XMC-Fire is designed for monitoring fire tank water reserves for commercial and high-rise buildings, as a one-stop solution for buildings to meet the monitoring and service requirements of the fire protection codes.
It monitors up to two 4–20 mA current loop level sensors, displays live values on its built-in touchscreen, and sends data to a third-party cloud platform via WiFi and MQTT. Data can be shared with BMS and SCADA systems through the Modbus TCP protocol, through auxiliary signalling analogue outputs (0–10 V), and through voltage-free relay outputs driven by configurable alarm thresholds.
The XMC-Fire connects to XMD rugged remote display units, or can act as a high-end auxiliary display itself. Local trending of level readings over 50 days assists service, maintenance and troubleshooting.
1.2 Key features at a glance
- Touchscreen HMI with live sensor display and trend graphs
- 2 × 4–20 mA analogue sensor inputs (configurable as hydrostatic or radar)
- 2 × digital inputs
- 6 × relay outputs and 2 × analogue outputs
- WiFi connectivity with MQTT data publishing
- Modbus TCP (read-only, over WiFi) and Modbus RTU (RS-485)
- Remote display link — drives up to 4 external displays, or acts as a remote display itself (single or dual channel)
- FRAM non-volatile storage for configuration and trend history
- Status LED visible at distance
1.3 Device identification
| Item | Where to find it / format |
|---|---|
| Device name | Set on the Interface screen; used in the MQTT topic path |
| Client ID |
X42_XMC_{Unit ID} — shown on the About screen |
2 Installation
2.1 Mechanical
2.2 Wiring
Power supply
Analogue inputs (Loop 1 and Loop 2)
Signal type: 4–20 mA current loop.
Sensor range check: the device flags a sensor fault if the loop current falls outside 3.7 mA – 20.3 mA. See Section 11.
Digital inputs
Relay outputs (RL1 – RL6)
Analogue outputs (AO1, AO2)
RS-485 (Modbus RTU)
Used for the remote display link. See Section 9.4.
Grounding and shielding
3 First power-on and startup
3.1 Startup sequence
- Apply power. The splash screen appears for a few seconds.
- The device transitions to the Main Screen (Home Multi).
- The Status LED shows GREEN solid when all is healthy. If it is ORANGE or RED on first startup, refer to Section 5.
3.2 Factory / test mode
A new or factory-reset device starts in factory mode (flag PARAM_FLAG_FACTORY_MODE_OFF = 0). Normal operation begins once the flag is set.
3.3 Setting the admin password (first login)
PARAM_FLAG_CREDS_SET is saved3.4 WiFi commissioning
3.5 Setting the clock
The device synchronises time automatically via NTP (pool.ntp.org) once WiFi is connected. No manual time entry is required.
4 Main screen guide (Home Multi)
4.1 Pages
The main screen has up to three swipeable pages. The active page is selected automatically based on which sensors are enabled, but can be swiped manually.
| Page | View | Shown when |
|---|---|---|
| Page 0 | Dual view — both sensors side by side with individual trend graphs | Both sensors enabled |
| Page 1 | Sensor 1 large view — full screen with trend graph | Only Sensor 1 enabled |
| Page 2 | Sensor 2 large view — full screen with trend graph | Only Sensor 2 enabled |
4.2 Value displays
Each sensor panel shows:
- Live value in engineering units, with the label set in Sensor Configuration
- Minimum and maximum indicators
- A status indicator if the sensor is in fault
4.3 Trend graph
The graph scrolls as new samples arrive (one sample every 12 hours). The horizontal axis represents time, oldest on the left. History is loaded from memory when the screen is first shown. To clear the trend history, go to Settings > Device Configuration.
4.4 Info bar (top of screen)
Updated approximately every 10 display frames.
| Indicator | Meaning |
|---|---|
| WiFi signal bars | No bars = disconnected or not configured; 1 bar = very weak (below −100 dBm); 2 bars = weak (−100 to −80 dBm); 3 bars = fair (−80 to −60 dBm); 4 bars = good (−60 to −40 dBm); 5 bars = strong (−40 dBm and above) |
| IP address | Assigned by DHCP. Used for Modbus TCP access. |
| Board temperature | Ambient temperature inside the enclosure. Shows “--.-” if outside −20 to 100 °C. |
| TCP indicator | Lit when a Modbus TCP client is connected. |
| Remote count | Number of remote displays currently linked. Shows “R” when this device is acting as a remote display. |
| Relay status | Two short text fields showing the state of the configured relay outputs. |
4.5 System status indicators
| Indicator | Condition |
|---|---|
| SYS | System-level fault — software fault or hardware reset required |
| LOW SUPPLY | Supply voltage below threshold |
| CRITICAL | Brownout — outputs have been de-energised to protect data |
| ALARM | One or more alarm thresholds active |
| AUTO DIM | Display auto-dimming is active |
5 Status indicators
5.1 Status LED
The LED on the front panel reflects the current health of the device.
| LED state | Meaning |
|---|---|
| GREEN solid | Normal — no active faults or warnings |
| GREEN fast flash | Information event active (non-urgent) |
| ORANGE solid | Warning active (communications, power threshold) |
| ORANGE slow flash | Warning is clearing / recovering |
| RED solid | Fault active (sensor out of range, power brownout, FRAM error) |
| RED slow flash | Fault is clearing / recovering |
5.2 Screen indicators
The Home Multi screen also shows system status icons. See Section 4.
5.3 What to do when the LED is not green
Check the Commissioning screen for live readings and relay states. If faults persist, refer to Section 11 (Fault Finding) and Appendix A (Error Code Table).
6 Settings menu guide
6.0 Accessing settings
From the Main Screen, press the Settings button. If an admin password has been set, you are prompted for it first.
6.1 Device configuration
Display auto-on (LDR)
| Setting | Description |
|---|---|
| Enable | On / Off |
| ON threshold | LDR reading above which the display turns on |
| OFF hysteresis | LDR reading must fall this far below the ON threshold before the display turns off |
| Brightness | LCD backlight level |
Display forced on (digital input / fire alarm input)
| Setting | Description |
|---|---|
| Enable | On / Off |
| Min on-time | Seconds the display stays on after the input clears, to avoid rapid on/off flickering |
Trend history
- Clear Sensor 1 trend — wipes stored trend data for Channel 1
- Clear Sensor 2 trend — wipes stored trend data for Channel 2
6.2 Sensor configuration
Applies separately to Sensor 1 and Sensor 2.
| Setting | Description |
|---|---|
| Enable | On / Off |
| Name | Up to 10 characters, shown on the main screen |
| Sensor type | Hydrostatic — pressure-based level sensor; Radar — distance / time-of-flight sensor |
| Full-scale range | Maximum measurable distance or depth (mm) |
| Full level | Distance or depth at 100 % fill (mm) |
| Empty level | Distance or depth at 0 % fill (mm) |
| Install height | Height of sensor above vessel bottom (mm). Required for radar sensors. Must be greater than the Full level value. |
| Offset (software trim) | Added to the raw reading after scaling, in engineering units |
| Gain (software trim) | Multiplier applied to the raw reading |
6.3 Alarm settings
Up to 6 independent alarm thresholds are available.
| Setting | Description |
|---|---|
| Name | Up to 10 characters |
| Source | Which sensor or data point drives this alarm |
| Activate at | Threshold to turn the alarm ON |
| Deactivate at | Threshold to turn the alarm OFF (hysteresis) |
| Min active time | Alarm stays on for at least this many seconds, preventing rapid cycling |
| Output | Which relay this alarm drives |
| Override | Auto — alarm controls the relay normally; Force On — relay held on regardless of process value; Force Off — relay held off regardless of process value |
6.4 Interface (WiFi, MQTT, Modbus TCP)
WiFi
| Setting | Description |
|---|---|
| SSID | Network name, up to 20 characters |
| Password | Network password, up to 20 characters |
MQTT
| Setting | Description |
|---|---|
| Broker | Hostname or IP address of the MQTT broker, up to 32 characters |
| Port | Default 1883 (plain) or 8883 (TLS) |
| TLS | On / Off |
| Clean session | On / Off |
| QoS | 0, 1 or 2 |
| Keepalive | Keepalive interval in seconds |
| Client ID | Override the auto-generated ID (optional, up to 32 characters) |
| Username | MQTT broker username, up to 32 characters |
| Password | MQTT broker password, up to 32 characters |
Modbus TCP
| Setting | Description |
|---|---|
| Slave address | This device’s address on the Modbus network (1–247) |
| Port | TCP port to listen on (default 502) |
| IP address | This device’s IP address |
6.5 Security (admin password)
Enter the new password twice to confirm. Once set, this password is required to enter Settings.
CREDENTIALMINIMUMLENGTH characters6.6 Remote display (Modbus RTU mode)
| Mode | Behaviour |
|---|---|
| Master — Send to remote displays | This device polls up to 4 remote display units and sends them values from its configured data slots. |
| Slave — Single display | This device acts as a remote display, receiving one channel from a master device. |
| Slave — Dual display | This device acts as a remote display, receiving two channels. |
| Slave address | This device’s address when operating as a slave (1–247) |
Remote device configuration (Master mode only, up to 4 devices)
| Setting | Description |
|---|---|
| Address | Slave address of the remote display (1–247) |
| Enable | On / Off |
| Slots 1–7 | Each slot can read or write one Modbus register |
| Function code | 3 = Read Holding, 4 = Read Input, 6 = Write Register |
| Register | Starting register address |
| Count / value | Register count (reads) or write value |
6.7 Commissioning
For use during installation and fault finding. Not for normal operation.
Live readings
- 24 V supply rail voltage
- Loop 1 raw current (mA) — useful for verifying sensor wiring
- Loop 2 raw current (mA)
Relay override controls
Each of the 6 relays can be set to Auto (controlled by alarm logic), Force On (energised regardless of process value) or Force Off (de-energised regardless of process value).
Suspend actions
Pauses Modbus master polling and MQTT publishing while enabled. Use when making wiring changes that would otherwise cause spurious alarms.
Display test
Sends a test pattern to all connected remote displays. Use to verify the RS-485 wiring to remote display units.
6.8 About
Read-only device information:
- Device name — as configured on the Interface screen
- Firmware version
- MAC address
- Unit ID (serial)
7 Inputs and outputs
7.1 Analogue inputs
Two 4–20 mA current loop inputs (Loop 1, Loop 2). Each input is independently configurable — see Section 6.2.
Fault detection
The device monitors each loop current continuously. A fault is logged and the LED turns RED if the current falls outside:
- Low limit: 3.7 mA (below 4 mA — open circuit or sensor failure)
- High limit: 20.3 mA (above 20 mA — short circuit or sensor overrange)
7.2 Digital inputs
Two digital inputs (DIG_INPUT_1, DIG_INPUT_2).
One use case is Display Force-On: digital input 1 can be configured to force the touchscreen on when asserted, for example from a fire alarm panel. See Section 6.1.
7.3 Relay outputs
Six relay outputs (RL1 – RL6). Each relay is driven by one of the 6 configurable alarm thresholds. Relays can also be forced manually from the Commissioning screen.
7.4 Analogue outputs
Two analogue outputs (AO1, AO2).
8 Alarms
The device provides 6 independent alarm channels. Each alarm monitors a selected data point and activates a relay when the threshold conditions are met.
8.1 Normal (high) alarm
- Activate threshold < Deactivate threshold
- Alarm ON when the value rises above the Activate threshold
- Alarm OFF when the value falls below the Deactivate threshold
8.2 Inverted (low) alarm
- Activate threshold > Deactivate threshold (set Activate lower)
- Alarm ON when the value falls below the Activate threshold
- Alarm OFF when the value rises above the Deactivate threshold
8.3 Minimum active time
Prevents the relay from de-energising immediately after the process value crosses the Deactivate threshold. Useful for pump protection and for avoiding rapid cycling.
8.4 Relay override
See Section 6.7 for manual force control via the Commissioning screen.
9 Communications
9.1 WiFi
The device connects to a standard 2.4 GHz WiFi access point. Configure the SSID and password in Settings > Interface. The IP address is assigned by DHCP and displayed in the Info Bar.
WiFi is required for MQTT data publishing, Modbus TCP access, and NTP time synchronisation.
WiFi can be disabled via the PARAM_FLAG_WIFI_DISABLE flag, set during manufacture for units without the WiFi option. No WiFi errors are reported when disabled.
9.2 MQTT
The device publishes sensor data to an MQTT broker at the interval set in the Posting_sec parameter (default 60 seconds).
Publishing is suppressed when the device is not connected to WiFi or the broker, is in a brownout or safe state, or has actions suspended from the Commissioning screen. For payload details see Appendix C.
| Item | Value |
|---|---|
| Topic | {device_name}/{MAC_no_colons}/ |
| Example | FireX42/AABBCCDDEEFF/ |
| Settings | Section 6.4 |
| Status | Info Bar WiFi signal bars and LED colour |
9.3 Modbus TCP
The device operates as a Modbus TCP slave (server). External SCADA or PLC systems can read register values over the WiFi network. Default port 502, configurable in Settings > Interface. For the register map see Appendix B.
9.4 Modbus RTU (remote display link, RS-485)
The RS-485 port supports three operating modes, selected in Settings > Remote Display. A reboot is required when changing mode.
| Mode | Behaviour |
|---|---|
| Master — Send to remote displays | Polls up to 4 remote display units. Each remote unit has an independent slave address and up to 7 register slots that can be read or written on each poll cycle. |
| Slave — Single display | The device acts as a remote display, showing the value received from a master device on the main screen. Swipe is locked to Page 1 (Sensor 1 large view). A comms loss alarm is raised if no update is received for 30 seconds. |
| Slave — Dual display | As above, but the device receives two channels. Swipe is locked to Page 0 (dual view). |
10 Trending
The device stores a long-term trend history for both sensor inputs. One sample is recorded every 12 hours.
The trend graph on the main screen displays this history. The oldest samples scroll off the left as new ones are added. Trend data survives power cycles, stored in FRAM non-volatile memory.
To clear the trend history: Settings > Device Configuration > Clear Sensor 1 trend / Clear Sensor 2 trend.
11 Fault finding
11.1 LED is ORANGE — warning
- WiFi connected? Check the SSID and password in Settings > Interface.
- MQTT connected? Check the broker address and port.
- Modbus RTU comms: check RS-485 wiring and slave addresses.
- Supply voltage: is the 24 V supply within specification?
11.2 LED is RED — fault
- Sensor loop current: go to the Commissioning screen. Loop 1 and Loop 2 raw readings should be between 4 mA and 20 mA. If outside this range, check sensor wiring and sensor health.
- Supply voltage: a brownout (below the critical threshold) de-energises all outputs. Check the supply.
- FRAM error: configuration storage fault.
11.3 Main screen shows “--.-” for temperature
The board temperature sensor is reading outside −20 to 100 °C. Check the enclosure environment and ambient conditions.
11.4 Remote display count shows “R”
The device is in Slave mode and is acting as a remote display. If this is not intended, change the mode in Settings > Remote Display.
11.5 No trend history visible
- The trend may have been cleared. History builds up at 12-hour intervals.
- Alternatively, the device clock was not set (no NTP sync) and samples are being stored with epoch timestamp 0.
11.6 Device not responding to Modbus TCP
- Check WiFi is connected and the IP address is shown in the Info Bar.
- Confirm the SCADA system is using the correct IP and port (default 502).
- Modbus TCP is read-only; confirm the SCADA is not issuing write commands.
11.7 Display not turning on automatically
- Check Settings > Device Configuration: auto-on must be enabled.
- Check the LDR threshold setting against the actual ambient light level.
- Check that a forced-on digital input is not being confused with LDR control.
12 Specifications quick reference
| Parameter | Value |
|---|---|
| Supply voltage | [PLACEHOLDER] — V dc, range |
| Analogue input range | 4–20 mA |
| Sensor fault thresholds | Low 3.7 mA / High 20.3 mA |
| Digital input voltage | [PLACEHOLDER] — V, active level |
| Relay contacts | [PLACEHOLDER] — rating, type |
| Analogue outputs | [PLACEHOLDER] — signal type, range |
| RS-485 | [PLACEHOLDER] — baud rates, default |
| WiFi standard | 2.4 GHz, [PLACEHOLDER] — protocol |
| Operating temperature | [PLACEHOLDER] — range °C |
| Enclosure | [PLACEHOLDER] — IP rating, material |
| Dimensions | [PLACEHOLDER] — mm |
Appendix A Error code table
| Code | Name | Severity | Description / typical cause |
|---|---|---|---|
| 0x01 | POWER_BROWNOUT |
Fault | Supply voltage critically low. All outputs de-energised. Check supply and cabling. |
| 0x02 | SENSOR1_RANGE |
Fault | Loop 1 current outside 3.7–20.3 mA. Check sensor, loop wiring, power. |
| 0x03 | SENSOR2_RANGE |
Fault | Loop 2 current outside 3.7–20.3 mA. |
| 0x04 | FRAM_CORRUPT |
Fault | NV configuration data integrity failure. See Appendix D. |
| 0x05 | FRAM_IO |
Fault | Communication failure with NV storage device. Hardware fault. |
| 0x10 | WIFI_DOWN |
Warning | WiFi disconnected. Check SSID, password, access point. |
| 0x11 | MQTT_DOWN |
Warning | MQTT broker unreachable or rejected. Check broker address, port, credentials. |
| 0x12 | MODBUS_TCP |
Warning | Modbus TCP transport error. |
| 0x13 | MODBUS_RTU_SLAVE1 |
Warning | Remote display 1 not responding. Check RS-485 wiring and address. |
| 0x14 | MODBUS_RTU_SLAVE2 |
Warning | Remote display 2 not responding. |
| 0x15 | MODBUS_RTU_SLAVE3 |
Warning | Remote display 3 not responding. |
| 0x16 | MODBUS_RTU_SLAVE4 |
Warning | Remote display 4 not responding. |
| 0x17 | POWER_LOW_SUPPLY |
Warning | Supply voltage below low threshold. Outputs still active. Check supply. |
| 0x18 | MB_DISPLAY_CH1 |
Warning | Slave mode: no update received on channel 1 for more than 30 s. Check master. |
| 0x19 | MB_DISPLAY_CH2 |
Warning | Slave mode: no update on channel 2. |
Appendix B Modbus register map summary
Access via Modbus TCP (port 502 default) or Modbus RTU RS-485. The slave address is configured in Settings > Interface.
B.1 Scaling
Float and 32-bit values are scaled to fit a 16-bit register.
| Value | Scaling | Example |
|---|---|---|
| Sensor values (AI_EXT_1/2) | register = engineering value × 100 | 12.34 m = 1234 |
| Analogue outputs (AO1/2) | register = output value × 100 | — |
| Loop current (IR5 / IR6) | register = µA | 12000 = 12.000 mA |
| Thermistor (IR2) | register = °C × 100 | 23.50 °C = 2350 |
| 24 V supply (IR3) | register = volts × 100 | 24.10 V = 2410 |
B.2 Input registers — FC4 Read Input Registers (read-only)
| Reg | Name | Scale | Description |
|---|---|---|---|
| IR0 | Sensor 1 (AI Ext 1) | ×100 | External analogue input 1, engineering units |
| IR1 | Sensor 2 (AI Ext 2) | ×100 | External analogue input 2, engineering units |
| IR2 | Board temperature | ×100 | Internal thermistor (°C) |
| IR3 | 24 V supply rail | ×100 | Supply voltage (V) |
| IR4 | LDR light level | ×1 | Raw light sensor reading (display auto-dim) |
| IR5 | Loop 1 current | µA | Sensor 1 raw loop current (fault range 3700–20300) |
| IR6 | Loop 2 current | µA | Sensor 2 raw loop current |
| IR7 | Analogue output 1 | ×100 | AO1 current output value |
| IR8 | Analogue output 2 | ×100 | AO2 current output value |
| IR9 | System state | ×1 | 0 = Operational, 1 = Degraded, 2 = Safe, 3 = Shutdown, 4 = Fault |
| IR10 | Remote value 1 | ×100 | Modbus remote input 1 (slave mode: received from master) |
| IR11 | Remote value 2 | ×100 | Modbus remote input 2 (slave mode: received from master) |
B.3 Input bit registers — FC2 Read Discrete Inputs (read-only)
| Reg | Bit | Name | Description |
|---|---|---|---|
| IB0 | 0 | Digital input 1 | State of digital input 1 (0 = off, 1 = on) |
| IB0 | 1 | Digital input 2 | State of digital input 2 (0 = off, 1 = on) |
B.4 Coil registers — FC1 Read Coils / FC5 Write Single Coil
Coil register 0: WRITE — relay force commands from SCADA. Coil register 1: READ — relay actual state read-back.
| Reg | Bit | Name | Access | Description |
|---|---|---|---|---|
| CR0 | 0–5 | Relay 1–6 | R/W | Write 1 to force relay ON, 0 to force OFF |
| CR1 | 0–5 | Relay 1–6 | R | Actual relay state (reflects alarm and force logic) |
B.5 Holding registers — FC3 Read / FC6 Write Single Register
These registers allow a SCADA system to update alarm thresholds remotely. Changes are saved to non-volatile memory automatically.
| Reg | Alarm | Access | Description |
|---|---|---|---|
| HR0 | Alarm 1 (RL1) | R/W | Activate threshold (alarm turns ON above this) |
| HR1 | Alarm 1 (RL1) | R/W | Deactivate threshold (alarm turns OFF below this) |
| HR2 | Alarm 3 (RL3) | R/W | Activate threshold |
| HR3 | Alarm 3 (RL3) | R/W | Deactivate threshold |
| HR4 | Alarm 4 (RL4) | R/W | Activate threshold |
| HR5 | Alarm 4 (RL4) | R/W | Deactivate threshold |
| HR6 | Alarm 6 (RL6) | R/W | Activate threshold |
| HR7 | Alarm 6 (RL6) | R/W | Deactivate threshold |
| HR8 | AO1 setpoint | R/W | Analogue output 1 forced value (×100) |
| HR9 | AO2 setpoint | R/W | Analogue output 2 forced value (×100) |
B.6 RTU slave mode — display receive registers
When operating as a remote display (Slave Single or Slave Dual mode), the device listens on the RS-485 bus for write commands from the master.
| Reg | Name | Description |
|---|---|---|
| HR0 | Display channel 1 | Written by master — shown as Sensor 1 on the main screen |
| HR1 | Display channel 2 | Written by master — shown as Sensor 2 on the main screen (Slave Dual mode only) |
Values are sign-extended 16-bit integers. The master should scale values ×100 before writing, matching the sensor display format.
Appendix C MQTT payload reference
C.1 Payload format (JSON)
| Item | Value |
|---|---|
| Topic | {device_name}/{MAC_no_colons}/ |
| QoS | As configured (0, 1 or 2) |
| Retain | Off |
| Interval |
Posting_sec (default 60 s, suspended if not operational) |
| Subscribe topic (inbound settings) | {device_name}/{MAC_no_colons}/Settings/# |
C.2 SEC field — sensor error bitmask
| Value | Meaning |
|---|---|
| Bit 0 | Sensor 1 out of range |
| Bit 1 | Sensor 2 out of range |
| 0 | No sensor errors |
Appendix D Factory default restoration
Considerations to cover when this section is written:
- Restoration erases all site configuration — WiFi, MQTT, alarms, sensor calibration.
- Record all settings before proceeding.
- May require physical access to the device (button sequence or menu option).
-
PARAM_FLAG_FACTORY_MODE_OFF_BITis cleared — the device returns to factory / test mode and must be recommissioned.
Legal notices
Copyright
X42 Monitoring™. No part of this technical manual may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of X42 Monitoring™.
Disclaimer
Warranty and liability
Regulatory information
Disposal
Support and contact
Need help with your XMC-Fire?
Technical advice and resources, including manuals, user instructions and datasheets, are available from x42monitoring.com.
For direct product support email support@x42monitoring.com or call 1300 421 069.
X42 Monitoring is powered by Kangaroo Kick Tech Pty Ltd.
Document status: FRAMEWORK — all amber-highlighted placeholder items require completion with hardware specifications and site-specific details before issue to technicians.
