dani/CommandStation-EX
1
0
Fork 0
mirror of https://github.com/DCC-EX/CommandStation-EX.git synced 2024-11-27 01:56:14 +01:00
Code Releases Activity

Update ThrottleAssists.md

Browse Source 
Fixing formatting
This commit is contained in:
Fred 2023-03-03 21:35:13 -05:00 committed by GitHub
parent 0f5b8adb6b
commit 79eaaa85fa
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 34 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
Release_Notes/ThrottleAssists.md
View File

@ -14,15 +14,15 @@ The conventional turnout definition commands and the ```<H>``` responses do not
e.g. response ```<jT 1 17 22 19>``` e.g. response ```<jT 1 17 22 19>```
```<JT 17>`` requests info on turnout 17. ```<JT 17>`` requests info on turnout 17.
e.g. response ```<jT 17 T "Coal yard exit">``` or ```<jT 17 C "Coal yard exit">``` e.g. response ```<jT 17 T "Coal yard exit">``` or ```<jT 17 C "Coal yard exit">``
(T=thrown, C=closed) (T=thrown, C=closed)
or ```<jT 17 C "">``` indicating turnout description not given. or ```<jT 17 C "">``` indicating turnout description not given.
or ```<jT 17 X>``` indicating turnout unknown (or possibly hidden.) or ```<jT 17 X>``` indicating turnout unknown (or possibly hidden.)
Note: It is still the throttles responsibility to monitor the status broadcasts. Note: It is still the throttles responsibility to monitor the status broadcasts.
(TBD I'm thinking that the existing broadcast is messy and needs cleaning up) (TBD I'm thinking that the existing broadcast is messy and needs cleaning up)
However, I'm not keen on dynamically created/deleted turnouts so I have no intention of providing a command that indicates the turnout list has been updated since the throttle started. However, I'm not keen on dynamically created/deleted turnouts so I have no intention of providing a command that indicates the turnout list has been updated since the throttle started.
Also note that turnouts marked in EXRAIL with the HIDDEN keyword instead of a "description" will NOT show up in these commands. Also note that turnouts marked in EXRAIL with the HIDDEN keyword instead of a "description" will NOT show up in these commands.
Automations/Routes Automations/Routes
@ -39,11 +39,15 @@ Note: It is still the throttles responsibility to monitor the status broadcasts.
or ```<jA 13 A "description">``` for an automation. or ```<jA 13 A "description">``` for an automation.
or ```<jA 13 X>``` for id not found or ```<jA 13 X>``` for id not found
Whats the difference: What's the difference?
A Route is just a call to an EXRAIL ROUTE, traditionally to set some turnouts or signals but can be used to perform any kind of EXRAIL function... but its not expecting to know the loco. -----------------------
Thus a route can be triggered by sending in for example ```</START 13>```.
A *Route* is just a call to an **EXRAIL ROUTE**, traditionally to set some turnouts or signals but can be used to perform any kind of EXRAIL function... but its not expecting to know the loco.
Thus, a route can be triggered by sending in for example ```</START 13>```.
An *Automation* is a handoff of the last accessed loco id to an EXRAIL AUTOMATION which would typically drive the loco away.
An Automation is a handoff of the last accessed loco id to an EXRAIL AUTOMATION which would typically drive the loco away.
Thus an Automation expects a start command with a cab id Thus an Automation expects a start command with a cab id
e.g. ```</START 13 3>``` e.g. ```</START 13 3>```