Nick,

?

Check in device manager when you plug it in. Some devices make multiple entries so they might be used multiple ways. If it creates a COM device (windows) then you have lots of options for how to deal with it. If not, then you have a bit more work with what library or driver you might need to make the connection.

?

-Ken Cameron, Member JMRI Dev Team

?

?

Ted,

?

It’s possible the LokProgrammer software is not 100% accurate. I now realize that inclusion of “Delay starting if drive sound is enabled (bit 2 of CV124)” makes no sense (but also does no harm) since the LokPilot can’t make use of it. That starting delay is tied into the prime mover startup sound sequence which depends on the sound project. The LokPilot has no way of knowing what sound project is in a LokSound 5 that might be consisted to it.

?

The same thing shows up for LokPilot 5.

?

I have JMRI 5.10 and find that “Prime Mover Startup Delay if Virtual Drive Sound Enabled “ shows up under “Advanced>Miscellaneous’ in the LokPilot 5 programmer. The associated value of CV252 is adjusted using the slider. CV252 is in the ‘CV’ sheet. Unfortunately, no separate DecoderPro programmer for LokPilot 5 Basic.

?

Mark Granville

A question for those having issues with the NCE Light-It.

?

Are you all using NCE command stations or have people been seeing the same issue but use other vendor command stations?

?

I suspect other vendors might prioritize the choice and spacing of the signal accessory packets differently from how NCE is doing it. I’m curious to see if that makes any difference or not to the problem. This might shed more light on what the problem might really be and then some work around might be figured out. It’s a long shot, but I figure worth asking.

?

The other question is if people had found some minimum number of Light-It decoders are needed before this become a problem? Or has this issue been seen when only a couple of Light-It’s are in use?

?

-Ken Cameron, Member JMRI Dev Team

?

?

Ted. Some more info.

?

I opened my LokProgrammer software and created a new LokPilot 5 Basic project. I can only assume this will give accurate information. Under ‘Decoder>Driving characteristics>Starting delay’ it lists two check boxes:

Delay starting if drive sound is enabled (bit 2 of CV124);

Delay starting if virtual drive sound is enabled: Time to wait before start (CV252). CV252=1 gives 0.07s. CV252=10 gives 0.66s. CV252=50 gives 3.28s. So, I think a value of 50 should match the default value of CV167=13 in the LokSound 5.

?

I think ESU is saying that starting delay is available in the LP 5 Basic.

?

As mentioned before, you should be able to program CV252 with DecoderPro using the single CV programmer.

?

Mark Granville

My bad. Found it on page 72 of the LokPilot 5 manual: “But only when the sound is switched on. You can set the start-up delay of the LokPilot 5 decoder in CV 252 in steps of 65ms.” Interesting that the units are 0.063 sec instead of 0.25 sec.

?

You can access CV252 using the JMRI single CV programmer.

?

I still cannot find it in the LokPilot 5 Basic instructions which say “A list of all decoder parameters can be found in the de?tailed manual for the LokPilot 5 Basic, which can be down?loaded from our website www.esu.eu in the ?Downloads? area.” I can’t find that detailed manual anywhere. Anyone know where it can be found?

?

Mark Granville

?

Ted, Definitely better asked in the LokSound group. All my locos have LokSound. None have LokPilot so I don’t have direct experience. The on-line manuals for LokPilot 5 and LokPilot Basic are not helpful. I can’t find a mention of starting delay in either one. But my understanding is that the starting delay feature was put into later firmware versions of LokPilot V4 and the LokPilot 5/DCC. You might try CV167. That seems to be the usual one used to set starting delay time (units of 0.25 sec) in the LokSounds.

?

Mark Granville

If the startup delay doesn’t work in your LokPilot 5 Basic, then you need to kill the delay in your LokSound 5. Try setting SoundCV13=0 (CV167=0).

?

Mark Granville