Open
Description
As a test I connected twice to a CommandStation-EX, one serial and one (wired) network using Traintastic. (My open source project for model railway control.)
When you control an engine, the other client(s) are notified, see log below:
2025-03-28 09:48:48.853718 dccex_network D2001: TX: <t 1 1 0 1>
2025-03-28 09:48:48.863162 dccex_serial D2002: RX: <l 1 0 128 0>
2025-03-28 09:48:48.873023 dccex_network D2002: RX: <l 1 0 128 0>
2025-03-28 09:48:48.882254 dccex_network D2002: RX: <T 1 0 1>
2025-03-28 09:48:53.338391 dccex_network D2001: TX: <F 1 0 1>
2025-03-28 09:48:53.347916 dccex_serial D2002: RX: <l 1 0 128 1>
2025-03-28 09:48:53.354009 dccex_network D2002: RX: <l 1 0 128 1>
2025-03-28 09:48:57.118718 dccex_serial D2001: TX: <F 1 0 0>
2025-03-28 09:48:57.124332 dccex_serial D2002: RX: <l 1 0 128 0>
2025-03-28 09:48:57.218955 dccex_network D2002: RX: <l 1 0 128 0>
2025-03-28 09:49:01.476529 dccex_serial D2001: TX: <t 1 1 0 0>
2025-03-28 09:49:01.482218 dccex_serial D2002: RX: <l 1 0 0 0>
2025-03-28 09:49:01.482347 dccex_serial D2002: RX: <T 1 0 0>
2025-03-28 09:49:01.518029 dccex_network D2002: RX: <l 1 0 0 0>
This works very well.
But when it comes to controlling DCC accessory there is no way to know if someone controls an accessory, see log below:
2025-03-28 09:49:46.192580 dccex_serial D2001: TX: <a 1 0>
2025-03-28 09:49:49.371773 dccex_serial D2001: TX: <a 1 1>
2025-03-28 09:49:52.851653 dccex_network D2001: TX: <a 1 0>
2025-03-28 09:49:53.677656 dccex_network D2001: TX: <a 1 1>
It would be really helpful if the other clients are notified, similar to the <l ....> response for engine control.
This makes it possible for clients to control accessory, another client (e.g. Traintastic) can then visualize the state of those accessories, e.g. turnout positions.
Metadata
Metadata
Assignees
Labels
No labels