The LokProgrammer is insanely fast to read and write CVs to the decoder. It also allows you to modify or load the sound project.
It does have a few useful features outside of speed. It will allow the firmware in the decoder to be updated, and you can set the defaults. If the decoder resets by accident or on purpose, you don't lose things like the address you set and other CVs.
Another advantage: The software will work without the hardware, so you can make changes and get a list of CVs to change, either manually or using DecoderPro.
How are you interfacing JMRI to your current Digitrax command station?
If you're using a PR4, when used in stand-alone programming mode the PR4 is pretty quick compared to a command station. As long as you're not downloading new sound projects to the ESU decoders, it'll do just fine.
My PR4 will read all CV's on a LokSound in about 15-20 minutes. Not as fast as the LokProgrammer, but how often do you need to read all the CV's? I do it once on a new loco, and that's it...
I would also caution against having any sort of a "combination" track because of the potential for back-feeding current into something and letting the magic smoke out. But if you insist on setting one up with a rotary switch, please use a "non-shorting" (break before make) switch.
ArtoI have room for another third track which I can make single line point to point or around the layout.
Yes you can do this but you will need to remember to remove any other loco on the track prior to doing any programming. If you don't, you will end up programming all those locos along with the intended victim. And anyone who tells you that this hasn't happen to them or to someone they know is probably not telling the truth.
Much better to have a spur within view that you can isolate.
ArtoESU doesn't *require* a "special connection" with JMRI. BUT, ESU does make a special interface called LokProgrammer.
Ahh that's different. It is faster.
If rotary switches are off between positons it should work. I believe they are, but I am no Randy Rinker.
Henry
COB Potomac & Northern
Shenandoah Valley
ArtoExisting layout is DCC 2-track mainline, Digitrax, separate boosters for each maineline. JMRI used as interface. I have room for another third track which I can make single line point to point or around the layout. I want to use this third track for programming.
Are you anticipating that this third track would be completely separate from the other two or connected through crossovers or some other track? If completely isolated, I don't see any issue. If not completely isolated, you want to make sure you don't ever bridge the boundary while the new track is set to program. Not only would you run the risk of programming everything on the other track(s), but you would also risk frying the output circuits of your boosters and or programmers.
If the sections are connected, but you have a significant length of rail between them, you can setup an isolated section of track that is only powered when the track is set to run. It would require the use of a 4 pole switch instead of 2 poles. I can give you more information on it if you want to go that way.
BigDaddy I don't use JMRI, yet, so maybe I should keep my mouth shut, but that wouldn't be me. There are good reasons to have a programming track. I've never read that ESU needs a "special connection". Reading ESU decoders often require multiple reads with JMRI.
I don't use JMRI, yet, so maybe I should keep my mouth shut, but that wouldn't be me.
There are good reasons to have a programming track.
I've never read that ESU needs a "special connection". Reading ESU decoders often require multiple reads with JMRI.
Let me rephrase that
ESU doesn't *require* a "special connection" with JMRI.
BUT, ESU does make a special interface called LokProgrammer. I guess it's primarily used for creating/programming your own sounds onto the decoder.
However, it also greatly speeds up the amount of time it takes to read/write (make any changes) to LokSound decoders. It has it's own software interface that allows it to read and write the much larger number of CV that Loksound have. Using JMRI can take many times longer (as in hours) on LokSound decoders. With LokProgrammer its a mater of seconds. But all the setups I've seen use a separate programming track for LokSound/LokProgrammer.
I'm not sure how to word the Subject Title & therefore also having difficulty doing a search. Looking for information on whether or not this is a good/bad idea and best way to do it..........................
Existing layout is DCC 2-track mainline, Digitrax, separate boosters for each maineline. JMRI used as interface.
I have room for another third track which I can make single line point to point or around the layout.
I want to use this third track for programming. However ESU Loksound decoders seem to require a separate connection to the computer to speed up read/write time to their decoder.
So, what I'm looking to do, is for instance, have a point to point maineline track that could be used for interurban, but also be used as a programming track for both Digitrax, and for the special connection for ESU decoders.
I'm pretty sure I can accomplish this with, say, a simple 3-way rotary switch for Mainline using Digitrax, and for programming both Digitax and ESU.
Anything in particular I should watch out for or be aware of? Articles or videos on this subject?