I had one thought, could this be related to the firmware version contained in the LokSound Select decoders themselves, not being at a level high enough, or the reverse, that the firmware level is to new and JMRI is having an issue reading the decoder?
On August 4, 2019 at 1:57 PM James Koretsky <jameskoretsky@...> wrote:
Hi All,
I am having some issues with JMRI for the first time while I have been programming a Loksound Select decoder as part of using the Read type from decoder function. I am trying to standardize a process for some people to program their locomotives, and if they all do the same thing it might make them programming their own units simpler and not have to get me involved.
I am using a DCS52 (With USB Interface), a Lenovo Tablet running WIndows 10 Build 1803, JMRI Test Version 4.17.2+Re9dde08, and a Digirax for the System Manuifacturer, DCS52 USB Interface as the System Connection, the Serial Port is COM3, Command Station Type is DCS52 USB interface as standalone programmer, L as the Connection Prefix and LocoNet as the Connection Name.
Anyway, as part of the standard programming features for a new locomotive, I use the Read type from decoder button on the Create New Loco window, to keep things standard.
We had programmed some 15 units without sound, and all was going well. I knew there were limitations with some Soundtraxx Sound decoders due to the power requirements needed on to power up the decoder on the Programming track. Most of these locomotives are N Scale and there's very few N Scale units owned by members with Soundtraxx so wasn't worried about the setup for that, then I went to program our first Scaletrains N Scale unit with Factory Sound from ESU, a select I believe in N Scale, and ran into the problem.
It gets through reading CV8 and CV7, and then goes on to reading Set SI and Set PI before it comes up with Stopping due to error: No Acknowledge from Locomotive (308).
I added a Soundtraxx Programming booster, thinking that there wasn't enough power on the programming track to power the decoder, which by the way, I have never seen before on a LokSound Select not be able to have the cv values be read from the programming track before, but then again, I always use the LokProgrammer.
I am getting the same error with the programming track booster, as I was getting before adding the programming booster. This is happening on 3 different locomotives, one from Scale Trains, One from Kato and One from Rapido (HO Scale), all have Loksound Decoders. I myself use the LokProgrammer to program my LokSound decoders, and I don't want a different setup for Loksound units, as we're trying to build a roster of all lococomotives.The LokProgrammer reads the decoders without issue.
Non Sound decoders function just fine, as they should, I have ruled out the porgramming track wiring, as well as the USB connection to the Command station, as we've tried different cables, etc...
Using a throttle in JMRI, and setting the Command Station type to DCS52 (Zephyr Express), I am able to run locomotives on the track outputs of the DCS52, without any issue. So JMRI is communicating just fine with the DCS52 and all 3 Locomotives that I can't read the decoder value using the programming track function just fine with the throttle, in DCS52 (Zephyr Express) mode, but still get the same issue when trying to program..
So what is the issue here, is this an issue with the DCS52, or some other issue, and why can I read the decoders CV values with the LokProgrammer and not JMRI.
What am I missing here? Anyon
Regards
James
