Hamburger

Pretty sure this is a LokPilot Standard. 02714-14649_LokPilot_Standard_ESUKG_ESULLC_US_Blisterkarton_Betriebsanleitung__Auflage-2_eBook.pdf02714-14649_LokPilot_Standard_ESUKG_ESULLC_US_Blisterkarton_Betriebsanleitung__Auflage-2_eBook.pdf

With a few exceptions, locomotives with 2 and often even 4 cylinders have 4 chuffs per revolution and with 3 cylinders they have 6. Decoders such as TTS produce a "fake" number of chuffs due to their primitive technology. Fewer chuffs than the original are preferably played at higher speeds because the sound sampling of the chuffs is simply poorly done. When the models run at higher speeds, the sounds usually sound very choppy. In fact, model railroaders often ignore reality because they just want to hear a nice "puff-puff" and that's it." There are exceptions, such as the A4 sound project by Locomansounds or European projects by D&H, but such things are rare. More sophisticated decoders than TTS have the ability to individually adjust the number of chuffs.

It sounds like you're blaming the ECoS for being incompatible. In fact it is the Zimo decoder that cannot handle Railcom-PLUS.

The video is soo boring: far too high revs for the speed . What do you want to show us? Don't understand the video.

Since this is not an ordinary German D&H project, but Locoman's, I took a look at Locoman's website, and voilà: technical information->CV list->CV353 at speed step 2. And I'm very sure it's 2/28. For me it's an iterative process, which means switching between CV 353 and 354 again and again, 3 or 4 times. I usually test with speed step 2, 6, 10, maybe 12, at most 14. At higher speeds you can't see it clearly anyway. I use PoM to set it up and it usually takes 5 - 10 minutes. The last step is to adjust CV 362 to limit the chuff rate at very high speeds. By the way: a real locomotive can only maintain such a low speed for a brief moment as is achieved (on a scale) with the D%H decoder at speed step 1. At least you won't hear any chuffs on the real thing, so it seems reasonable to me that no sound can be heard on the model. Just switch on F5 and it sounds realistic for me

Do you have this? https://shorturl.at/oDUY7 Also (mostly 😉 ) valid for V5

Hi Lester, I can see 3 ways to achieve this, but only under certain circumstances. 1. As Dave mentioned, delay the moving off. If you have full access to the sound section (unlocked project) then you can insert a delay in the motor sound slot. 2. As it is a shuttle, the direction of travel should change at every stop. So you can do experiments with CV111 (gearbox backlash delay). Then the motor will run up to 4.18 seconds (CV111 = 255) with internal speed step 1 (of 255), so try if CV2 = 1 hinders the DMU from moving. Maybe it works, maybe not. Maybe you have to finetune the speed curve for the lower speed steps a bit. 3. If you are able to rewire the interior lighting: Resistor for LEDs must be between U+ and LED Anodes (+). Cathodes must be permanently connected to GND (-). The lights will then always be on. Then you can use negative logic by "stealing" the voltage between resistor and LED by connecting the output exactly there. Means output on = lights off. And no, this will not overload the output because the current is limited by the resistor. The stop time for the shuttle then should not exceed about 2 minutes. You can then program the output to switch on 6.14 seconds after stop (this will "steal" the voltage and switch the lights off). Then set the automatic function timeout of the output to 104.45 seconds. Timeout = output off = lights on. If you have programmed a shuttle wait time of about 115 to 120 seconds this will give you a delay between lights on and moving off.

This is a LokSound 4.0 from 2015.

Almost anything is possible with an ESU LokSound 5 decoder, but of course it depends on what exactly you want to do. Please describe in more detail what you are planning.

Did you also change CV2? This has a big impact on chuff sync. For example, if CV2 = 1, you should start with CV57=200 and CV58 = 50. And before that (but after setting CV2) you need to do the CV54/F1 procedure, see instructions.

Depending on the locomotive manufacturer it is probably an ESU multi-protocol decoder. In this case there is no CV6. (And CV1 is a typo I think, should be CV2)

Simply increase the value of CV5 on the ESU decoder (if not already set to maximum value 255) and/or decrease the value of CV5 on the 2-8-2.

Manual for V4, but 95% is also correct for V5.

The learning curve can be steep. A little trick for the future: it may help if the LoPro shows you all the respective CVs: Go to "Tools -> Program settings -> General settings" and tick the box "Show CV numbers", then close the program and open again. Now it should show you the respective CV# for each function setting. Nomenclature: [CVxxx.y] means "only bit y of CVxxx is used for this setting" (mainly on-off-functions) [CVxxx.y:z] means only bits z to y are used for this setting (example CV262.4:0 means bits 0 to 4 are used (gives you single-bit-values from 1 to 16, if all bits are on and added this gives you value 31)) [CVxxx.y (CV32=0)] means that CV31 has to be set to 16 and CV32 to 0 before programming the "main" CV. If CV31 needs to have a value other than 16, this will be specified separately). Hard to understand at the beginning and maybe useless for a beginner but after some time you will appreciate this. Good luck!

😄 Didn't know you have a LoPro.