0 Members and 1 Guest are viewing this topic.
Here is another data point. Windows 10, Locobuffer-USB, DCS 50, JMRI 5.0. I used Direct Byte mode. I opened the CVs tab and Read Full Sheet. Most CVs were read successfully. Those that had errors were in red, so I read those individually. I did the same procedure with a Raspberry Pi with equal success. One loco was an N scale Paragon 3 (SW 7) and the other an N scale Paragon 4 (SD70ACe). I think that you did this, but do not select Rolling Thunder option from Ident. That has few CVs.Rodney
Thanks guys,I’m using JMRI version 4.26+R381c8dfc32, Windows 10, Locobuffer USB and a Digitrax DCS50 Zephyr on Kato Unitrack.I keep getting no acknowledgment from the locomotive. On address 03 the engine runs ok although pick up is sketchy. Seems like it’s only picking up on one truck. When I get time I’ll open it up and make sure everything is making connection. Seems odd since the trucks are hardwired.
Jim, did you ever get your addressing issue resolved? I've had good luck with the P4's, but I use BLI "address changer" on a dedicated track to set the address, and program everything else on the main, even when running by the seat of my pants. No JMRI here.(BTW when it first came out, I thought the "address changer" was a needless gimmick, but once I saw it in use, I was sold).Otto
Just wanted to update and thank everyone who replied with suggestions. I replaced the Paragon 4 with a Loksound Nano and an ISE Powerkeeper. It programmed flawlessly and is now an outstanding runner.