So knowing what I now do about the IoTT channel progress, how would it affect the South Downs railway?
Firstly: if I started from scratch, the South Downs railway might be a lot different.Â
- The EX-CSB1 + Red hat looks like it would make a fine command station; the added Power shield boards would make good boosters. So the Digitrax command station and boosters would not be needed.
- The DCC critters look like they would make good replacements for the Digitrax PM42 modules. The FET switched output, rather than relay switched output, would lead to silent operation.Â
- The Yellow Hat modules would be credible alternatives for control panels. However they'd need additional code to add an ALM for interlocking with Traincontroller
- The Blue Hat signal controllers might be suitable, but the need to drive available N scale model signal leads is a possible complication
However, replacing working electronics on the existing railway isn't that simple. What will I actually do?
Well, the "Brown hat" plus LocoNet interface and IoTT stick makes an excellent gateway for 3rd party communications. It will replace a locobuffer; it will allow smart phone throttles to be used; and it will provide a MQTT broker gateway. Ihave assembled Brown hats ready to go, together with a Raspberry pi with installed MQTT broker.
Replacing the PM42 with LocoNet critters is a possible change. However the physical assembly of my railway electronics might mean they don't fit.Â
Any new control panels will use a Yellow Hat, with MQTT communications.Â
Train detection is as yet an unsolved problem. I have 10 Digitrax BDL168 boards and it isn't clear that replacing them would be wise. Occasionally I get "stuck on" detectors (typically on the short detection sections at the "stop sensor" at the end of a block). A technology that avoided that would be good. I'm unconvinced about "train side" sensing for N scale: I don't see how it would fit even if the communication were build into the decoder and miniaturised.Â
Watch this space!