<p><font size="3"> </font></p><p><font size="3"> </font></p> <p><font size="3">This is culled from GSM to try and answer some common questions on DCC programmers and installing decoders. Many thanks to the members who’s post are edited together here. Zerogee, PaulSHolt, Ian, DTSteam, Zman, Graham, Chas, Nick & Dunnyrail.</font></p><font size="3">
</font> <font size="3"><font color="#0000ff">This week I bought a SPROG II decoder programmer, after reading good reports of them from several members on this forum and elsewhere. I bought it in preference to a Massoth or LGB programming module because I use a Mac rather than a PC, and the SPROG (with the free Decoder Pro software) is Mac-compatible. It was a little bit of a struggle to set up properly for the first time - nothing to do with the SPROG itself, but finding and installing all the necessary little bits of software to make it run on the Mac - but with the help of a computer-guru friend yesterday (moral: always have someone on-call who actually knows what they are doing...), it's now all installed and running nicely, and I can start learning my way around the system.
</font></font><p><font size="3"> </font></p><font size="3">(Note it’s all there on the JMRI website but read the installation section carefully)
<font color="#0000ff">The question is this: with the SPROG/DecoderPro setup, is it OK to program a decoder OUT of the loco - ie: simply connect the decoder's power leads to the SPROG output, so that I can set up the relevant CVs before I install the chip in the loco - or does it need to be connected to a motor etc? I am assuming you CAN do this, because I guess that is how a dealer can pre-program bits of the chip before supplying it, but I wanted to double-check with you chaps before I simply connect it up and the Magic Smoke gets out of the decoder (as everyone knows, once the Magic Smoke escapes from a piece of electronic equipment, it stops working...).
</font></font><p><font size="3"> </font></p><font size="3">On Massoth and LGB you have to have the chip connected to the motor - to provide a "load"
</font><font size="3">You can program the chip but it will say error if you try to read anything without a load. Better to install it so you can test it straight away and get confirmation that it has worked. Shops that have to program it usually have it hooked up to a decoder tester, which includes a motor, so they can test it before despatch.
</font><p><font size="3"> </font></p><font size="3">The load is required to allow the decoder to send an acknowledgement signal back to the programmer, otherwise you'll get something like "unable to read decoder" error even though you might have sucessfully programmed the CV change.
</font><font size="3">For a load you can simply use an old spare motor. Doesn't have to be a motor, any load with a few ohms resistance will do, but a motor is best as you get to see something happening. And you can then use to SPROG in command station mode to try driving the motor too.
</font><p><font size="3"> </font></p> <p><em><font size="3"><font color="#0000ff">A couple of follow-up questions connected with the SPROG and programming stuff: as I've mentioned in earlier posts, I've got a couple of Massoth LS sound decoders to install in locos which already have factory-fitted LGB decoders - the intention was to splice the LS decoder into the track power feeds and use its sound functions only (in effect, just use it like a cheaper version of an LGB aftermarket sound module), leaving the driving and lighting functions to the original factory-fitted decoder. This was partly for simplicity's sake, but also with the thought of not disturbing the loco's original wiring too much, in case I want to remove the LS again at a later date and return the loco to as-built configuration. Now, will I have any problems with this? Will the fact that the driver stage of the LS is not connected to a motor cause any difficulty, either in programming or in function? Will the SPROG get confused by the fact that there are two decoders present, both on the same address?
Would it, in fact, be better to simply remove the factory-fitted decoder and replace everything with the LS after all?
</font></font></em></p>
<font size="3">No this will work fine as the Massoth chip will take commands as you program the LGB chip, (motor<u> only provides a load for reading back CV's not programming them</u>)
The LGB onboard chips have a better power buffer too, for dirty track, Massoth sell theirs as a separate item which costs you more. If you piggyback it on the power inputs you will get the best of both decoders and if the LGB one ever dies you still have a spare decoder onboard to wire in
Neil's stuff for Klien Arosa and my Ge4/4 both use exactly this setup with both decoders onboard.
</font><p><font size="3"> </font></p><p><font size="3"> </font></p><font size="3"><font color="#0000ff">Will the SPROG get confused by the fact that there are two decoders present, both on the same address?
</font></font>
<font size="3">Nope
</font><p><font size="3"> </font></p><font size="3">SPROG comfortably works with G scale decoders with it's supplied power unit, and everything else especially current hungry sound decoders without a booster circuit. Andrew Crossland at SPROG is very helpful at problem solving.
I have Sprog and recently got a ESU lokprogrammer too and both work well although I would choose the SPROG for other manufacturers decoders due to the slightly better interfaces. The ESU unit is invaluable for their sound decoders though if you want to be able to download or change sounds, I only need to buy another 9 decoders and it's paid for itself </font>
<font color="#0000ff" size="3">I</font><font color="#0000ff"><p><font size="3"> </font></p><font size="3">reckon that the lower voltage is more likely to Trip before frying a chip if I make a botch of it.
</font></font>
<font size="3">Beauty of the programmers like the SPROG, ESU etc is that as they only supply a low voltage and current, if you install the chip and then read it back the programmer will tell you if you've connected it up wrong as it will show an error. The programmer is a safe way to check it out before trying it on the track. The ESU and SPROG both allow you to actually test the functions in command station mode.
<strong>Reference the ESU Decoder tester
</strong></font><font size="3">Looks to be a handy little bit of kit - I assume it'll work with any decoder, not just ESU? Does it have any major advantages over simply rigging up a testbed with any old motor as a load?
</font>
<font size="3">Works with any decoder the advantage is it tests the function outputs too not just the motor is working, but as long as you don't damage the decoders leads or board in any way the chip is still guaranteed once installed. Personally I've only had one duff decoder and as I tested it with the SPROG before putting the loco back together it was as easy to test it onboard as on a special tester as you still have to connect it all up.
</font><p><font size="3"> </font></p>