After cutting a trace you should use a DVM on Ohms and check that the trace is actually open. I have been caught several years ago with a trace that looked cut by the eye, but really was not. The DVM is a better check.
you are absolutely correct its really tough trying to cut the traces, i did use a meter and checked that the traces were in fact cut.
Still having issues with jmri reading cvs with dcc++ arduino and pololu motor shield . All wiring is correct per several other posts on this forum. I even switched to the esp32 version of dccpp and have the same problem. jmri does not acknowledge the decoder or read cvs. Anyone having similar problems. jmri gives 308 error no response from loco.
Hello all, Hi dompondaco, I have just setup my dcc++ BaseStation with an Uno/ArduinoMotorShield (both genuine). The first problem was a faulty MotorShield, which gave me some more grey hairs ... With a new Shield it starts working fine on both - "ControlerMaster" and also JMRI. I could read and write my decoders on the programming track with both environments. But with some decoders, specially from Minitrix and DoehlerHaass, I could not read the CVs an get that 308-Error. Fortunatly I found a solution here in another thread: http://www.trainboard.com/highball/index.php?threads/dcc-issues-with-d-h-10c-resolved.106064/ Patching the original file "PacketRegister.cpp" in the BaseStation code solved that issue for me, now everthing works fine. Reading all CVs of a loco in one step with JMRI is really great! Maybe this helps for you as well Kind regards from germany peter ps: if running on GNU/Linux I have a diff-file ready for easy patching and can send it, just 2.5 kB ...
This is really a JMRI issue and not a DCC++ issue. Page 9 explains how to set up turnouts in JMRI. http://www.quaker-valley.com/ctc/JMRI Panel Tutorial1.pdf
How does he get 17 functions from an accessory decoder? How do you enter it in JMRI and do you know how to do it in DCC++ which uses the 2 part address scheme? Normally, in a 2 part address, you have the 9 bit address, then a 2 bit subaddress and then a direction or enable bit that makes it "closed" or "thrown". So 1 address can only have 4 outputs with 2 outputs each. And these can act as a mobile decoder OR a stationary decoder. So you can program it like a loco too, right? I have a few and just haven't soldered them up yet.
