I have Lenz set 100 to run my layout. Reading about how to speed match my locos for MU ops the suggestion of using Decoder Pro keeps coming up. Speed matching my locos using the DCC system is very time consuming.
So here is what I understand about Decoder Pro: DP is a program I download onto a PC that has an interface to connect it to the layout.
I have an old laptop (Windows 7). is it preferred to connect to the layout or a separate programing track?
What do I need for the interface connection?
Do you use the PC to run the layout or just for programming?
I also understand that DP stores CV settings rather than having to use the DCC system to read back settings.
Am I missing anything? I appreciate any info that gives me a better understanding of DP and just why I need to have it. I know speed matching locos currently gets frustrating.
http://jmri.sourceforge.net/help/en/html/apps/DecoderPro/
Mark.
¡ uʍop ǝpısdn sı ǝɹnʇɐuƃıs ʎɯ 'dlǝɥ
For your specific Lenz system ....
http://jmri.sourceforge.net/help/en/html/hardware/XPressNet/index.shtml
basementdwellerI have an old laptop (Windows 7). is it preferred to connect to the layout or a separate programing track?
I'm not familiar with Lenz, but normally the computer connects to the command station and the command station connects to the track. If your command station has connections to both the railroad as well as the programming track, then normally those connections remain.
If you want to do speed matching, you will use programming on the main, not the programming track.
Basementdweller,
You can use the WIN7 Laptop, depending on your Lenz DCC system, with JMRI, to program via programming track, program via main line, run trains on mainline from computer throttle, control turnouts, control signals, and more.
If you can, I recommend USB, as it will be faster, and will absolutely connect to your laptop. Older serial models may not...
And, always unplug it when not in use! (Otherwise, any power surge that gets through your computer will go into your layout. Opposite direction works also. Power surge that makes it to layout does damage. Layout to computer does just as much damage. And yes, spoken from (a not good) experience!)
Ricky W.
HO scale Proto-freelancer.
My Railroad rules:
1: It's my railroad, my rules.
2: It's for having fun and enjoyment.
3: Any objections, consult above rules.
Thanks for replies, I don't intend to run the layout from the PC as I want the walk around Lenz throttles. That is why I am thinking programming only, but programming on the main makes sense.
I see about using USB on PC.
To be honest this is all clear as mud.
What Lenz products are you using? I use xpressnet compatible products with RocRail and JMRI, and can probably help, but I need to know what hardware you have.
Julian
Modeling Pre-WP merger UP (1974-81)
There's really only two options - LI-USB and the LI-USB-Ethernet.
Once you connect the computer to the interface and plug the interface into the Expressnet, load up JMRI and away you go. See the other thread on using phones - once you have JMRI up you can use an Android or iPhone as a throttle too - handheld and wireless walkaround.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
basementdweller I also understand that DP stores CV settings rather than having to use the DCC system to read back settings.
This isn't quite right, and there's a two-part explanation.
First part:
DP has a bunch of decoder definitions. They all have default CV values in them, but those are the CV values that the definition's author used when they wrote that particular definition. They may not be the CV values in YOUR decoder, or not even the factory defaults for that decoder. Think of them as a very good starting point.
Second part:
You use one of the decoder definitions mentioned above as a template to create a roster entry in DP for each of your locos. That roster entry is where DP stores the CV values *for that loco*.
But if you don't read the loco's CV's, that roster entry will have the values from the decoder definition file, which again are not necessarily what's in your loco.
Bottom line:
Your roster entry will have CV values stored in it, but unless you actually read the decoder and save the roster entry, those stored values may not be what's really in your decoder.
That's why the first thing I do when setting up a new loco is "Read all sheets" (a sheet is what they call each section of the roster entry, such as one sheet for the speed table, another for lighting effects, etc) and then save the roster entry. That way I get a baseline of what's in MY decoder.
I hope that helps some. It's actually easier to do it than to explain it.
fieryturbo What Lenz products are you using? I use xpressnet compatible products with RocRail and JMRI, and can probably help, but I need to know what hardware you have.
i have the Lenz set 100. That is it.
I have no luck trying to speed match locos and so that is why I am thinking DP.
StevertYour roster entry will have CV values stored in it, but unless you actually read the decoder and save the roster entry, those stored values may not be what's really in your decoder.
That's a very important point. You want JMRI's roster to acquire the customized readings you have entered previously, in most cases, rather than to write the default values that JMRI has for the decoder in you loco.
Read before you write.
It also applies if you have a tendency to use your full-featured system throttle to make CV changes without updating the loco's roster file in JMRI. The solution is the same, read before you write IF you want to keep what's in the loco when it goes on the programming track. However, you may want to revert to the stored roster file, in which case you write first.
Mike Lehman
Urbana, IL
JMRI is not going to magically speed match locos. There are some scripts people have written to do it mostly automatically, but it requires additional hardware for block detection as well, or else the use of things like the Bachrus speedometer.
Stick with decoders that support CV2-6-5 for a simple 3 step speed matching and you cna get them more than close enough without a lot of work. Maybe you are trying too hard. There's no need for the locos to be in 100% perfect lockstep using 28 step speed tables (this is where JMRI can help, programming 28 CVs one by one with the htrottle is much hard than just dragging the curve in JMRI and then saving it to the decoder), as long as they are reasonably close they will work fine when coupled together, especially when pulling a train. I've never done any 28 step speed curves in any of my locos in 13+ years of DCC.
The key to remember is that if one on default settings starts faster than another, you cannot slow down the faster one to match, only speed up the slower one. And one that goes faster than another at full speed - you cannot speed up the slower one, only slow down the faster one.