A station is one module (boxes); lite districts adopted; code documentation link
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Docs review and the district simulators plan
- Home, Node-Lite, DCC-EX, LocoNet Adapter, Architecture, RocNet on the Mesh, Module and
Layout Files: brought up to date (GCA101 stage 2, lite servers and failover, turnouts
on DCC-EX, sensors as RocNet, the module editor, O6 answered); two broken anchors and
the Node-Lite button table fixed.
- New page District Simulators and Train Tracking: the plan, steps 1 to 5 built.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Module and Layout Files drawn from SpDrS60 tiles; Screenshots page
- Module and Layout Files: the old top views replaced by the example modules as the
module editor draws them (Adorf, a 2E96 line module, the district border pair);
schema version 3 draws from tiles, no geometry; signal aspects by their Ril 301 names
(the colours kept for version 2); the web view shows signals as their tiles, and the
simulator does not yet show Hp 2 / Vr 2.
- Screenshots: Hive-Rail running on the bench layout: the web view with trains and the
station information boards of Adorf and Bdorf, Cdorf's passing loop, the module editor,
the dispatcher screen and a node dashboard.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signals: new pages Signal Faces and Choosing and Placing Signals; sensors as RocNet
- Signal Faces: every DB LED signal Hive-Rail draws, each aspect pictured, as faces and
panel tiles, with the Viessmann models and the one-red option.
- Choosing and Placing Signals: which signal goes where and what it shows, as SpDrS60
panels (two animated), Ks, shunting, the common mistakes, which Viessmann models to buy,
wiring them with MobaLedLib, and the sources (Ril 301, EBO §14, Wikipedia, Viessmann,
MobaLedLib).
- Architecture §2.2: RocNet for what a RocNet tool should understand, JSON for Hive-Rail's
own state; RocNet on the Mesh §9: nodes report their detectors as RocNet sensor reports.
- Home and Module and Layout Files link and use the new signal tiles.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Module and layout files: schema version 3, modules drawn from SpDrS60 tiles in the module editor; grid, tiles, file, what is derived, DB/FREMO names
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Module files: passing loops (passing_loops) next to stations
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Dispatcher sets the fast clock and shows loco districts; web view clocks
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Module files: signals, section-by-section routes and transfer block feed (3.11)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Module files: buildings with lights and level crossings (3.10)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Module and layout files: implemented checks, library, district files from several owners, publishing and locking
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Serial LocoNet interface, Intellibox I stage 2 and the node file as TOML
LocoNet adapter: the serial interface (--loconet-serial) with the settings
for the Intellibox I's RS232 port, a LocoBuffer-USB and the Intellibox II;
the status now matches the slot owners; stage 2 uses the Intellibox I
(65000) with its config file and first bench steps; L-Q4 answered, L-Q3
partly; new L-Q8 (the Intellibox's own controls on LocoNet) and L-Q9 (its
fast clock). The release byte was given as B5 slot 03, which is FREE: COMMON
is 13, and the code's bug is noted.
Module and layout files: the node file is implemented as a TOML config file
(--config). DCC-EX adapter: node ids MacBook, RaspberryPi and Windows, and
the config file. Home and FRED pages: status and defaults.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Module and layout files design, DCC-EX loco driving, takeover on the beam restore
- New design page: module, node and layout files; blocks with rail cuts,
sensors by running direction, geometry, a module editor later; top-view
SVGs of an example module, a standard 2E96 double-track module and a
district border on double track.
- DCC-EX Adapter §3.1: driving locos from the register.
- Takeover: the receiving node switches the transfer block when the beam at
its entrance is restored (the last car has passed) and the source edge
block is clear, instead of after a fixed delay; transfer blocks are cut in
both rails; on double track each district hosts the transfer block for its
incoming track.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>