On the Zimo, usually selecting ¡°nearest similar model¡± will be fine.? Only problem arises if those three CVs do something important
for your use of the decoder. Otherwise it won¡¯t be a problem.
Keeping up with every new Zimo release (decoder hardware and new decoder firmware releases covering every piece of hardware) is a challenge.?
?
If you want to create a new Zimo file, please do so. But do it carefully, look at the modular nature of the other Zimo files, and try very hard to make the
new definition for the MX616 fit in with everything else.? I¡¯d expect its possible to do it with a small edit to an existing file to slide the MX616 alongside an existing similar device.??
?
?
Other people¡¯s answers cover the ESU and the MRC decoder.?
I just Purchased two new decoders, One a Zimo MX616N and a ESU Lokpilot FX Nano 8 Pin. Neither of these will self identify under JMRI.
The Zimo will identify many different decoders but not the MX616N, If I select one that I think is closest to it and read all CV's It will read almost all, but will leave three CV's?unread.?That questions my choice of decoder. Do I need to create a new definition
file?
On the Lokpilot I see the F1 Light Flash, when it is being read,?but then I get a no locomotive present. Reading the documentation just confuses me more.
Can anyone give me some insight?how to programing these decoders.
I am using JMRI Test ver 15-1
Also I have a MRC 1833 Sound Decoder that I was trying to create a Decoder definition file. I am?using JEdit. I used a MRC 1927 File to begin with as it had most of the cv's that I needed. It will let me make changes to the file but will not let me save it.
