EX-Rail parsers

[dcyoung-dev]

Description

When a parser receives an EXRail response
I want to parse the response into usable elements
so that I can perform other tasks with the information

Design

EX-Rail responses are not documented

Notes

N/A

[FrightRisk]

The features that need adding to WebThrottle are:

• Turnout control with a separate screen (swipe left?)
• Routes
• Automation
• DriveAway
• Built-in decoder diagnostics (D ACK Commands)
• Button to Read the Loco ID on the programming track
• Button to set the loco ID on the programming track
• Walk-Through screen for WiFi Config (reset, fill in SSID, etc. and send the AT commands)
• Accessory address converter (enter linear or 2 part address and calculate the other)
• Can we mirror controls where a phone throttle and WebThrottle change the same loco?
• Multiple loco control with roster images and loco specific function keys.
• WiFi option to connect and use WiThrottle or (and?) <DCC++> Commands

The list got long as I started going through the mental list. The priorities are turnouts and ex-rail. We can make sure we have issues for each of the features we need to get to later. I've asked Chris and others to contribute to the features and their implementation, so you can have a clear direction to make coding simpler.

We can look to JMRI and Engine Driver for ideas on implementation.

[dcyoung-dev]

Thanks @FrightRisk, I'm really looking for some documentation on the EX-Rail responses (data coming from the command station)
With this information I can build a parser to convert the responses to usable data.

[dcyoung-dev]

https://dcc-ex.com/throttles/tech-reference.html#automations-routes

[dcyoung-dev]

https://dcc-ex.com/automation/EX-RAIL-summary.html#command-summary