Nothing beats hardware detection for switches separately as their own block. But as Tony said, it will add up moneywise. And in terms of wire. An alternative is to have the block sensors in JMRI, but without the hardware. In that case you need the logic (possibly in Logix) to calculate the expected occupancy taking into account train speeds (either measured or, more simple, expected), train direction, timing and neighbouring block occupancy. Less precision, a lot less money, less effort if you don't count creating the logic, which isn't entirely trivial.
On Tue, 12 May 2020 at 11:08, SteveM <steve@...> wrote:
Hi everyone,
With the aim of achieving layout automation either via warrants or dispatcher (rather than purely coding) when designing and laying out the track should turnouts be isolated blocks or can? they part of an exiting block. If a turnout is an isolated block then I suppose it would need it's own occupancy sensor rather if part of an existing block and able to be assigned the same sensor for the rest of the block. ? I think I must be the slowest modeller at achieving some form of automation, trying to bring all the elements together and taking one slow step after another.? It appears with jmri you can achieve the same or similar results via different routes and it seems experience often dictates which route you take,? oh for some experience
