REQUEST A QUOTE  -  STREAMLINED BACKSHOP INSTALLATIONS AND REPAIRS  -  MORE INFO 

ESU LokSound - LokPilot 5 Multi-Protocol and DCC Decoders - Decoded

Last Updated 240317

ESU offers two distinct versions of nearly every model decoder in their product line; multi-protocol decoders and pure NMRA DCC decoders.

To oversimplify the matter, multi-protocol decoders offer features consistent with the European market whereas the pure DCC decoders offer features consistent with the North American market.  Multi-protocol decoders will work with nearly any digital command station.  Pure DCC decoders will only work with NMRA DCC compliant command stations.  To oversimplify the matter further, a communication protocol is like a language.  Multi-protocol decoder speak DCC, Marklin Motorola, Selectrix, and Marklin M4; think of this as English, German, French and Italian.  Pure DCC decoders speak NMRA-compliant DCC; think of this as English only.

In every case, the two models are physically identical; they are literally the same hardware.  In every case, the two models use the exact same sound file; they are literally the same recordings.  The difference between the two resides in the firmware.  While both versions offer all of the great features that make the ESU decoder a great value and powerful decoder platform, there a couple of key differences that require explication. 

I should note also that many of the Multi-Protocol versions also include an ESU 50321 "Sugar Cube"-style Speaker 11x15mm 8 ohm 1 watt w/ Sound Chamber.  Information about which models include the speaker can be found in the ADDITION DETAILS tab in the product description.

I have analyzed the product manuals and CVs as they are presented in the LokProgrammer software and identified the key differences which affect (but not necessarily limited to) the following CVs:

The following CVs are also affected but they are generally used to configure the features associated with non-DCC protocols.

I do not wish to ignore the questions or needs of any of my clients, but please note I am writing this page for the benefit of pure DCC users.  I do not typically use the non-DCC functionality so I don't have any tangible experience with it. 

So, what's different?  I used the LokProgrammer software to do a side-by-side comparison of sound file S0501 when configured for a  LokSound 5 DCC sound decoder and a LokSound 5 Multi-Protocol sound decoder.  Here are the differences I can identify.  Note that in my analysis, the DCC file is always the left half of the image and Multi-Protocol is always the right half of the image.  I have also made references to the applicable section of the current product manual so you can explore this information on your own.

 

Pure DCC users will care most about the differences between speed tables and the differences and real effect between acceleration and deceleration settings.

The speed table is the easiest to cover.  The bottom line is pure DCC models offer the ability to select and configure a NMRA compliant 3-point speed table; CV6 is omitted in multi-protocol decoders so they do not support this functionality.  It's important to note that the full 28-point speed table is identical in both versions.  It is configured the same way and the results are identical, all other setting being equal.

This difference is really only an issue if you are speed matching locos for a consist and using the 3-point speed table.  It's not really an issue if you are speed matching using the 28-point speed table.

From the manual, 10.2 VMin, VMax, Speed Curve and 10.2.1 3-point speed table are defined as follows.


The difference between acceleration and deceleration settings is the crux of the matter and what users need to understand. 

Before reading further, note that this difference is only an issue when speed matching or consisting a loco having pure DCC decoder with a loco having Multi-Protocol decoder.

This detail doesn't really matter if you are speed matching locos having the same model or version of decoder.  This detail doesn't really matter if the loco will never be run in a consist.

The point to make here is that the scale of CV3 and CV4 in terms of real time and influence on behavior is different between the two models.  The values programmed in CV3 and CV4 affect the rate or time period it take a model to increase or decrease speed when the user changes the desired speed of the engine with their throttle.  Reviewing the range of these CVs, a pure DCC decoder can be programmed to take as long as 228.48 seconds to to transition between speed steps where as the Multi-Protocol decoder has a maximum setting of only 63.75 seconds or a ratio of 3.584:1.  This difference in the ratio makes it hard to make the two models play well together.

The difference between the scales has a direct affect on how 10.6 Brake functions and 10.7 Load simulation respond in operation of the model on the layout.

From the manual, 10.6 Brake functions and 10.7 Load simulation are defined as follows.

Using the examples provided, here is the math that highlights the effect of the different scales in terms of real time the different values have on these advanced features.

Since it is desirable to have the Acceleration and Deceleration time be reasonably identical for speed matching locomotives, it is not possible to have the 10.6 Brake functions and 10.7 Load simulation perform the same between the two decoder types.

So there it is, that's the real difference.  To say it again, this difference between the two types only matter if the loco is to be consisted and or speed matched with another model AND that the two models have decoders that aren't from the same version.