TestSys is a bench copy of ARMAC's electronics at the developer's home in Rowe Street, Melbourne, used to develop and test code without touching the system at Fairhaven.

Last checked: 7 November 2026.


TestSys

What it is

  • Three Arduino UNO R4 WiFi boards (AR1, AR2, AR3) running exactly the same code as Fairhaven.
  • Two Gravity RS-485 boards and short wires for the RS-485 and backup links, as on the real cable but without the 10 m run.
  • LEDs in place of relays, lit when AR3 energises each output.
  • A test button for AR3, as in Module 4.
  • No temperature probes, so outside a test the dashboard shows 0 °C and "all temperature sensors failed".
  • A separate Raspberry Pi at Rowe Street runs a test copy of Home Assistant and Mosquitto.

How the code knows it is on TestSys

A permanent wire strap to GND: AR1 pin A3 and AR3 pin D11 (see Arduino pin allocations). AR2 doesn't need to know. On TestSys:

BoardDifference
AR1Connects to the Rowe Street MQTT broker; connection self-restart after 3 minutes instead of 15 (2 minutes after start-up); a forced comms path ends after 3 minutes instead of 30; A0 has no battery divider, so AR1 sends AR3 no battery reading (AR3 then uses recirculation). The USB command BATSET <volts> sets a test value, and BATSET alone clears it
AR3No LCD; latch-relay pins drive LEDs that hold the pump state; battery reported as a fixed 12.8 V; fallback stages 1 minute instead of 5, fallback entry 10 s instead of 60, recovery 20 s instead of 2 minutes; connection self-restart after 3 minutes

The same compiled program runs on both, so there is nothing to change when loading the Fairhaven boards.

Testing at Fairhaven

TestSys can also be taken to Fairhaven and connected to the Rowe Street Home Assistant: AR1 recognises TestSys and connects to the Rowe Street broker, which is reachable from Fairhaven through the Fritzbox and Tailscale routing.

Logging

During tests the three boards' serial output is logged together on a laptop, with timestamps, for review afterwards. The logs show each message checked, every path change, restarts, and the Autonomous decisions as they happen.

Long tests

TestResult
16 hours on RS-485, message checking counting onlyNo bad messages either way, no restarts
Rejection switched on (FRAME_REJECT = 1): buttons, test button, forced backupEvery command went through once; only scrambled backup messages were rejected
7 hours forced onto the backup linkUnder 1% of AR3's messages rejected, about 5% lost, none bad from AR1; no restarts
16 hours on AUTO, rejection onNo errors, no restarts

<< Appendices | | Test scenarios >>      |Table of Contents>


Page last modified on November 22, 2026, at 01:57 AM