开云体育

G'day, I've just added a 74120 to my collection of decoders without checking to see if it was supported first--oops!
Since it isn't, is there support for it in the pipeline, and in the meantime, is there some way I can get control of it to at least change the address?
I can run it on ops using address 3 but can't change anything, I just get 308 errors. The defaults aren't so bad but the default address will not do.
Adding decoder support seems to be fairly involved, but I could possibly have a swing at it myself if someone can point me to how this is done.
I have all the docs with the decoder of course, but no real idea how JMRI stores this info. Could I perhaps use the existing 76425 definition as a starting point?
Thank you!
Charles

I just had a look at the definitions shipped and the docs for updating them. This is beyond my skill with XML to mess around with.
I don't suppose that a tool exists to simplify this process a bit? Other than a text editor of course...

Hi Charles,
On the Uhlenbrock website, it says:?The 74120 Decoder replaces the existing Decoder 76425 with NEM 652 plug.
That one happens to be in JMRI, and IntelliDrive2 I added for other models last Spring.

If you can send me the CV tables for this decoder (by Private message, use the button below on the groups.io web interface), I will check if I can work something out for you next month.

Egbert