Matching a Loksound 5 and a LokPilot 5

[reinhardtjh]

Seems to me it might have been a firmware bug in the LokPilot.  Do you have a LokProgrammer to update the firmware?  If so, make sure you're running V5.0.17 of the LokProgrammer software.  Do NOT download and run V5.1.0. It has a bug which will mess up the speed table CV on any DCC version of a LS 5 decoder.

Or maybe it's this? @RBrodzinsky mentioned this behavior on the LokSound email group:

Just finished this large batch of installs of LokSound 5 Micro DCC and LokPilot 5 Micro DCC decoders into a large set of Intermountain N-scale F units.  As I was auto tuning them and speed matching, I noticed a difference in behavior between the two decoders and starting delay.

First: after timing the startup delay in the sound file and setting the value for that delay in the LokPilots, starting from a dead halt (throttle=0) works just perfectly.  This is the way it should.

But, if one reverses the direction of the locos WHILE THEY ARE MOVING (I know, not supposed to do this, not prototypical, but not uncommon among modelers), the LokPilots and the LokSounds decelerate to 0 at the same (set) rate, but the LokSounds immediately ramp back up in the other direction, while the LokPilots delay moving for the length of time in the startiup delay.

Honestly, I'm not really sure which behavior I would prefer, just caught me by surprise that the decoders behave differently.

[RBrodzinsky]

John,

I think that bug has been fixed in the latest firmware, I didn’t encounter it in my most recent installations.

/>


While not shown in the edited video, I did back and forth movement by changing direction with throttle set, and everything worked as it should.

But that stresses the fact to make sure the firmware is up to date.

[delamaize]

Well, crap, I'm using JMRI. So I guess I need to figure out how to update the firmware.....
Of course, I should probably check it first..... stay tuned.....

EDIT: Looks like my firmware on the lokpilot is 5.2.105

[ Guests cannot view attachments ]

I'm working though an idea right now. Basicly copying all the motive related CVs from the A unit to the B unit. We will see what that does. Who knows might just fix the issue!!

[RBrodzinsky]

Nope, won't fix the issue at all.   You have VERY OLD (for the LP 5) firmware.  The only way to upgrade it is with a LokProgrammer (current version is 5.3.128)

[delamaize]

Nope, won't fix the issue at all.   You have VERY OLD (for the LP 5) firmware.  The only way to upgrade it is with a LokProgrammer (current version is 5.3.128)

Well, Crap. I may have to invest in a LokProgrammer, and a new computer to run the software.
Meanwhile, I did finally get all the data and CV's from both Locos downloaded into JMRI, and I found a lot of differences, and discrepancies. Little things, like the value for momentum was different, Vmin and Vmax were a little different, along with a few other things. I ended up just writing the important, pertinent CV values from the A unit, to the B unit.....

....and the problem is partially fixed. From a stop, Both forward and reverse, the 2 units are matched, and the B unit delays perfectly with the A unit when throttle is applied. But, like others have experienced with changing direction, while moving, or throttle applied, it doesn't delay....

So, progress is being made. I gotta get this figured it out sometime, I got parts coming to do my NCL F3 ABA set.

[reinhardtjh]

Well, Crap. I may have to invest in a LokProgrammer, and a new computer to run the software.

If you're planning on having a number of ESU decoders - LokSound or LokPilot, it's really a nice way to go.  Unfortunately, a component supply problem related to COVID is delaying a new run/shipment of LokProgrammers.

Sadly it's simply a Covid related component issue. They are coming but part lead times are unexpectedly long right now. We are also looking at other component sources, but they are limited. We want them released more than anyone.

If you join the ESU group on Groups.IO you can ask if there is a member near you able to program your units.  https://groups.io/g/Loksound

Or ask here.  I'm in Saginaw, Texas, near Fort Worth.  But I don't think you're near me.

[delamaize]

If you're planning on having a number of ESU decoders - LokSound or LokPilot, it's really a nice way to go.  Unfortunately, a component supply problem related to COVID is delaying a new run/shipment of LokProgrammers.

If you join the ESU group on Groups.IO you can ask if there is a member near you able to program your units.  https://groups.io/g/Loksound

Or ask here.  I'm in Saginaw, Texas, near Fort Worth.  But I don't think you're near me.

Thank you, I will join the group. I appreciate the offer, and you're right, I live in washington state. I use to be a die hard lenz guy, until the local shop that carried them closed up, after the owner retired. After that I used mostly TCS and Digitrax decoders. I am really digging sound decoders, and I really like the quality of sound that comes out of the Loksound decoders, not to mention how customizable they are. The lokpilot decoders are really nice also....

[reinhardtjh]

The lokpilot decoders are really nice also....

The cool thing is that the LokPilot decoders are usually cheaper than the TCS these days and generally have better motor control.  Digitrax decoders are still cheaper though for the generic wired types.  But you do have to make sure you don't get the LokPilot nanos or Standards if you want to match them with LokSound units.