Both decoders have an automatic recognition protocol, the difference is the ESU has an open protocol and this means you can change the loco number and all other available CV's.
The "railcom plus" system is an invention by Lenz.

We had a query on this forum, having a mixture of Märklin mfx & fx locos and use them as a consist under the same number.
Because the Märklin MFX loco numbers are rigid you cannot, for instance use the same loco number for another loco, although possible with a Command station, you can program 2 mfx locos as an consist.

I would imagine, having a few locos in your possession, it wouldn't be much of an issue, unless you don't have a CS1 or CS 2 and only possess a MS1, you need 2 loco numbers to form a consist.

Märklin & ESU automatic recognition system is virtually the same, except with the ESU decoders you can activate or de-activate the automatic recognition system, which would allow you, after programming, to change it from e.g. mfx to fx and hence programming 2 locos with the same number to form a consist with a MS1 and maybe MS2.

To have these type of options, is in my opinion, a great step forward an other option is also available, because you have an open protocol you can change the loco nummer to your own taste & requirement, if needed.

To be honest I have stayed away from buying Locos with mfx decoders because of the associated infringements.

I have aired my opinion about mfx decoders in the past, why would anybody bother buying a mfx loco and I had an opinion replied to me, this is what he prefers, coming home from a stressful day and doesn't have to figure out which loco is which, which is understandable and point taken and one could say this is the end of a discussion.

The point I like to make is to make members aware there are more options than one available with automatic recognition systems.

Including this member preference, it is a pity, Märklin chooses to use a closed protocol without giving enthusiasts of the wider modeltrain spectrum, the opportunity to do what they may prefer, to be able to change a.) a loco number, b.) turn off the mfx protocol.

Some people would say, you just have to live with it and if you don't like it, this is your personal choice but don't force your opinion onto others.

I hope it wouldn't be interpreted as such, my information I have on hand would be taken on board by these who would like to have a more flexible or usable system.

regards.,
John

Nev,

I see and thanks for the clarification

So I assume the Lenz railcom plus uses a different protocol to identify a loco and the ESU M4 uses the same principal as the mfx.

Now the ESU loksound V4 decoder, activating the railcom plus and downloaded a BR 01 sound file (I've downloaded it for the BR 23 which in turn doesn't show up as a BR 01 on your lockprogrammer), the moment you put it on the track with an ESU Command station, it tells you this loco (BR 01 is already occupied) and you can't use the same loco number) it confused me a bit and it offers you under railcom plus system, to enter a new loco number, hence assuming it was the number which dictated the automatic recognition.

So I had to re-think, first of all, how do they know its a BR 01 from a sound file, when I've dedicated the sound file, the number and name to a BR 23.

I again assume, acknowledging the sound file of a BR 01, different from an Marklin mfx protocol, it could be any BR 01 loco and the moment you change the loco number the sound file is or can be duplicated as an mfx loco so to speak many times over, although it will always tell you, this loco is already designated to an identification tag, it asks you change the loco number, either to use the railcom plus numbering system which they come up with the number 1000 or you ignore this and enter your own number into it.

What I had to do, rename the BR 01 to a BR 23 and than got rid of the BR 23 which was already registered in the system but without the railcom plus automatic recognition protocol.

Looking at it from the surface it may look complicated but I wasn't aware of the railcom plus addition to the decoders, plus all my loco had been registered prior to the discovery.

Having so many locos, a.)from different Railway Authorities, b.) three different types of locos, 1.) electric, 2 Diesel and 3.) Steam it was crucial to put them in such an order to find them easely.
Another hurdle I had to come to grips with was the dedicated number system to the marklin protocol regarding long addresses, which is another story.

a question I have about the numbering order, although you have over 10000 loco addresses putting them closer together instead of spreading them over the whole 10000 addresses available will the ESU command station slow down ? could it be compared similar to when defragmenting your computer files instead of having them splattered all over the hard disk.

regards.,

John

Edited by user 03 August 2011 04:28:00(UTC)  | Reason: Not specified

The MAC address is used to automatically assign an mfx address to the loco. Commands will be send to the mfx address, not the MAC address.

Theoretically mfx decoders shall ignore all MM commands if they detected any mfx commands (for their own address or other addresses) on the track. This does not work with the new Trix mfx decoders.