Read these pages carefully:
?
and
?
You also need a text editor, ideally one which does a decent job with XML.? I use “Notepad++” on Windows.?
?
Then start looking at the decoder files.?
You can construct locally held decoder files in the “preferences” area where settings are stored, typically on a Windows machine that’s in:
C:\users\[yourname]\JMRI\[systemconnection]\decoders
?
The main files are in the “program” area, under xml/decoders
?
Zimo files are moderately complex.? There’s a large “zimo” sub-folder of components used in the files, and then a number of files which reflect the decoder versions.
?
Suggest as a starting point, pickup the v39 file for the MX640-660 decoders, putting a copy in your locally held area, renaming it to cover the MX690-699 decoders, and opening it for editing.???
Remove most of the decoders in your copy of the file, and try to create something for one of the MX690-series. ?(I’d do it almost a line or element at a time, to keep errors to a minimum).
There’s a tool inside JMRI to “validate XML” which will spot many syntax errors in XML (and you can correct them!).?
Then load this file into JMRI (recompile decoder index, which can take ages, will report errors on the system console if you’ve made a mistake).??? IF it works, you’ll have the new file in your
decoder list.???
?
From there start making changes, such as getting the right number of function outputs.?
?
?
Next, look at various CV’s in decoder files, and investigate the zimo sub-component files. ?This gets a bit more complex, but that’s perhaps lesson-2.?
?
?
I recommend you get someone to go over your changes and make comments before they are submitted to JMRI as a change request.?
?
-
Nigel
?
?
?
I would like to learn how to make the changes. ?How do I get started.
Michael Carney
