Model Railroading > JMRI Programming Time Question

For those who use JMRI and maintain an active roster, what is your approach to downloading and storing CV values.  I have some new locomotives that I would like to download and save the factory settings prior to adjusting things.  My issue is the process can take a very long time, and while I could do other activities in that time, I feel like I have to babysit it to make sure it doesn't time out.  I'm running a Digitrax PR4 connected to a Windows computer via USB.  The PR4 is also hooked to Loconet and my DCS100, so I use the programming track leads off the DCS100.  The decoders I typically read are Loksound and Tsunamis, but the Loksounds take the longest.  Is there a faster setup for this process?  I remember moving from a PR3 to PR4 and being surprised by the speed increase.

Thanks,
Sean
West Grove, PA

Yes, it can take a long time to "Read All Sheets" on something like a ESU Loksound decoder. I have a NCE system that I use with JMRI, but have not had any time out issues. I just let it go and do some model work on the work bench. I usually set the address, momentum, and do a CV54=0 on ESU decoders to self program the BEMF before doing the read and then save to roster.

Ted Curphey
Ontario, OR

I second Ted's response.  the only decoders that take a long time are  ESU.  I tell fellow club members "if you click read all sheets on ESU, then go to dinner and come back later"
We've somewhat solved the issue by installing the ESU Lok programmer on the same computer/test track with a switch routing them to the track.  The ESU guys at the club don't seem to have a long duration problem when using the Lok programmer.  

Mike Stewart
Oakley, CA

I, too, recommend using the Lok Programmer for this.  Then when importing to the roster in JMRI, I don't do the "Read all sheets", instead I just get the basics down to cover throttle settings.

gnguy Wrote:
-------------------------------------------------------
> I second Ted's response.  the only decoders that
> take a long time are  ESU.  I tell fellow club
> members "if you click read all sheets on ESU, then
> go to dinner and come back later"
> We've somewhat solved the issue by installing the
> ESU Lok programmer on the same computer/test track
> with a switch routing them to the track.  The ESU
> guys at the club don't seem to have a long
> duration problem when using the Lok
> programmer.  
>
> Mike Stewart
> Oakley, CA

Agree with others, JRMI/Sprog for me, WOW, Tsunami can take awhile, but I also use the ESU programmer and ESU decoders take seconds to code. If you're using different types of decoders, makes sense to use different options. Many people try and standardize on one manufacturer decoder. It saves a lot of time and effort overall. 

Mike ONeill
Okahumpka, FL

Can't you reset the decoder back to factory defaults by setting CV8 to what the manufacturer specifies if the programming goes wrong?