M4 Configuration Range; M4, The Mfx® Compatible Protocol By Esu - Esu LokPilot V4.0 Instruction Manual

Programming

8.1.1. M4 configuration range

LokPilot XL V4.0
The NMRA CV concept as described above has some disadvan-
tages: On the one hand dealing with „collection CVs" such as CV
29 with its binary format is complicated while on the other hand
you can only enter one value (!). How could one possibly store
locomotive names with this method?
Furthermore, it is not possible for the command station to find
out, which CVs a decoder supports. The NMRA has simply „for-
gotten" to define a mechanism for providing feedback from the
decoder to the command station regarding the supported CVs.
With the introduction of the mfx® system the user does not have
to deal with CVs, values and the binary system. The command
station should rather request the decoder to provide this kind of
information and then enable the user to enter any values in an
easy way on the graphic interface.
For instance, you do not have to enter the value 15 in CV 3 on an
mfx® capable command station but rather set the acceleration
time to 10 seconds. Thanks to M4 you do not have to remember
that CV 3 contains the value for the acceleration time and that the
value 15 is equivalent to about 10 seconds. This kind of complex
technology is hidden in the mfx® command station.
Therefore the mfx® system does not cater for a direct method
of influencing the memory spaces, the so-called mfx® configura-
tion area of the decoder. Generally, M4 only permits access via the
command station.
This method has only one drawback. How can the owners of other
command stations that are not mfx® capable access the configu-
ration area? This is facilitated by means of a register concept that is
somewhat similar to the NMRA DCC CVs. Unfortunately this does
not provide access to all characteristics of the M4 decoder. Fur-
thermore mfx® was not developed further as intended originally
and basically remains at the status of 2004.
Since ESU "educated" the Central Station® 60212 with the "Re-
LokPilot V4.0 M4
loaded" Update and taught it to support DCC and when Märk-
lin® followed with the current Central Station 2, the situation has
been somewhat eased: All current mfx® command stations also
support DCC and can program DCC decoders. Since all LokPilot
V4.0 decoders support DCC you now have the choice on how you
wish to program your decoder:
• The Central Station® 60212 Reloaded and the Central Station 2
offer a graphic programming option for M4 decoders. However,
it only recognises the "old" ESU LokPilot V3.5 decoders and their
possibilities as well as the similar and hardly changed Märklin de-
coders. The LokPilot V4.0 M4 respectively the LokPilot XL V4.0
can be programmed via this menu without any problems. Unfor-
tunately some options are not available because the command
station "does not know them".
• You may access all options via DCC programming. If you own an
ESU ECoS we recommend this kind of programming. This com-
mand station also provides a suitable profile for this decoder.
8.1.2. M4, the mfx® compatible protocol by ESU
Since the mfx® data protocol was introduced, it has been pro-
tected by Märklin® as a trade mark. This is why ESU decided in
January 2009 to use the name "M4" for all their decoders. M4 is
technically 100% compatible with mfx®.
All ESU decoders and command stations which are M4 compatible
can be easily combined with the corresponding Märklin®-mfx®
products. We would like to apologise for this inevitable change of
names due to reasons of trademark.
29