List view
- No due date•0/1 issues closed
The brake system is necessary for obvious reasons. It seems simple, but the brakes of the train are complex, so they require efficient and concise code. The brake system in ZephyrCab should be written based on Al Krug's "Railway Air Brakes" paper, originally hosted on his site (alkrug.vcn.com). That site has since been taken down, but a copy of the paper can be found at http://hm.evilgeniustech.com/alkrug.vcn.com/rrfacts/brakes.htm
No due date•2/3 issues closedSince the bundle standard is so rapidly expanding, some kind of version information in each JSON object is necessary. ZephyrCab should be able to accept/reject/suggest edits to a bundle based on its creation date, and which objects it has/doesn't have.
No due dateWhile the output force is fairly realistically modeled already, the internal electrical systems are not effectively simulated. We need to have the option for automatic/manual transition, and have the motors function accordingly. This will probably require some additional work with the number returned by the Virginia Tech motive force equation, and far more electrical engineering theories involved in the simulation than there are currently.
No due dateSince most users will not know how to write JSON, an automated tool needs to exist for setting up bundles.json . Users should be able to look at a centralized list of appropriate locomotives, view the raw JSON if they so choose, and have the program generate a bundles.json file that binds the appropriate prototypes to their corresponding JMRI roster entries. The program ought to be able to connect to JMRI and fetch the roster so it's easy to bind an entry.
No due date