Hi there all, I'm currently running JMRI 4.16 and I'm trying to program a UB 74120. This isn't known to JMRI, so while I can use it on Address 3 with ops, I can't change anything. Keep getting 308s when programming, but the default settings are otherwise not so very bad. Is support for newer UBs in the pipeline? I saw a thread somewhere which seemed to imply 'at some point'... And is there some hack I can use in the meantime to get control of it and at least change the address? For those not familiar with it, it's an intellidrive 2 motor only decoder, follows on from the 76425 which is known to JMRI, but I tried that model in Add New and it didn't work. This didn't surprise me much. For that matter, is there any kind of generic decoder definition you can use with an unsupported decoder, just to get a few basic things set, especially the address?
Hmm just had a look at the XML for decoder definition. This is beyond my skill to mess around with. I guess I'll just have to wait! Unless someone has a tool for creating these which simplifies the process a bit? Don't say 'text editor'
Have you tried the simple programmer in JMRI. Down side is you'll have to do a few calculations your self on some CVs. You should get the calculators online, but watch out which support Railcom in CV29 (for your Uhlenbrock decoder). If you get same error when using other decoders, a spot of trouble shooting.
Not sure how to access this. Every dialogue I've seen starts by trying to recognise the decoder, which it can't. Which of the JMRI apps has this, and where under the menu structure does it lurk? However, all I want to do at this stage is change the address so this would be fine. Thanks!
Another D'oh! TM moment. Found it, DecoderPro/Actions. Shows what happens when you Read The Fine Manual. Thanks for the tip Pieter, will give this a go.
OK tried it, no dice. I get nothing but 308s for any read or write. But the thing works fine on the ops track with address 3. Well, at least nothing broke but I can't do anything with this one at the moment other than use the defaults. This seems a bit weird. I would have thought I should be able to at least read some values using the Simple interface? Especially since it runs on ops... Luckily I only have one of these, the others are supported NCEs and Zimos. Guess I'll work on them instead. Might raise an issue for this decoder and see what happens.
308 means no communication with loco. Various reasons why it might happen: 1) Using the programming track (service track doesn't program.) 2) All the cuts & jumper wire done on your motor shield as per instructions. 3) wire connections/ soldering 4) Your boards sitting evenly on each other? 5) Picked the correct command station in JMRI General settings? (should be 5 radio buttons to check in a row) There are other posts here that cover some of the other 308 problems. Look also for an earlier post on tweaking the read/ write sequence of DCC++ to get better compatibility with programming a wider set of decoders.
