Layout Feedback

• accepted
  Build our own active-high block detector

  2026-08-25 · Off-the-shelf detectors pull low for occupied, so a broken wire under the layout reads as a clear block. A home-designed board with an active-high output makes that fault read as occupied instead.

• accepted
  The block detectors' Input A is left unpowered, against the datasheet

  2026-08-24 · Powering an LM-iD.1's Input A, as every datasheet says to, makes its output idle at 5V into 3.3V expander inputs. It's deliberately left unpowered on Westgate Hollow.

• accepted
  MQTT for hardware, WebSocket for operators

  2026-08-24 · Sensors and point feedback talk to the orchestrator over MQTT under a binding contract. Operator devices, including the handheld throttle, use the orchestrator's WebSocket control plane.

• accepted
  Points are commanded by one device and read back by another

  2026-08-24 · Cobalt iP point motors take DCC commands but can't report their position, so position comes from their S2 contacts on a feedback node. That catches hand-thrown points, but creates two mappings nothing cross-checks.

• accepted
  Sensor nodes publish only the sensors that are actually wired

  2026-08-23 · An unwired expander input reads as "clear", so publishing the whole pin table would tell the orchestrator a block is empty using a wire that doesn't exist. Nodes publish an allow-list instead.

• accepted
  Sensors must keep talking, and silence is treated differently from lying

  2026-08-16 · Every sensor re-sends its reading at least every 30 seconds. A silent sensor degrades only its own blocks, while a garbled message Safe-Stops the layout.

Nothing logged yet.