The specs mention "mfx, MM1, MM2 und DCC", but no mfx+.

Total 12 new items in fall 2015 is now online today.

See Fall 2015 database in English >LINK<

Well I see three distinct groups of decoders in that line-up

60975, 60976, 60977 in one group.

60978, 60979, in a second group.

60985, 60986, 60987 in a third group.

But there is no explanation as to what their functions are.

Then there is 60972 and 60982 with no sound.

60973 seems to be altogether new.

Kimball

I've added some explanation from the Marklin website linked in the first post above.

I´m not really sure if mfx+ decoder will keep on as generation 3.

These decoders are specifically for Retro-fit. Marklin have always retained the mFX+ decoder as a factory fit only and they will simply continue this policy. It is unlikely they will use different hardware and will just change the firmware.

My understanding is that the ESU automatic motor calibration feature works extremely well. All that is needed afterward is to set up the speed curves.

It won't matter. It is important to understand that mfx+ is all about storing the information in the locomotive itself. mfx+ is not some special protocol, it is "just" a set of features and/or configuration values on top of the original mfx.

This means that no matter what control device you use with the Central Station, mfx+ will still work. This is a major difference from other systems that keeps the information in the controlling unit (e.g. Z21 is "just" a command relay box, the simulation (fuel consumption etc.) takes place in the controlling iPad only). If several controllers are used, they will have different ideas on the levels of fuel.

IMHO mfx+ is a more flexible system since more controllers can be in play. This means that no matter what controller you use, the locomotive will still run out of fuel when it is empty.

As with anything else there are pros and cons - and it is a matter of personal taste. I am sure some will disagree with me.

- With the Z21 (and others) you do not need a special decoder, which is powerful in itself, but the information is stored in only one controller and cannot be shared. Fine, if you only use one controller.

- With mfx+ the information is stored in the locomotive. Any controller for the Central Station will automatically work with it. Great if you use mutiple controllers. A special decoder (or at least firmware) is needed. Potentially expensive should Märklin ever make it possible to retrofit locomotives. My guess would be that all current mLD or mSD can be mfx+-ified with a software update. This would of course make upgrading existing decoders free.

Yep. Søren wrote it is just a matter of taste.

RailCom has a patent on using loco feedback to determine loco position.
mfx+ has a patent to simulate loco resources in the decoder.


Would it be great to have cab control with Delta decoders, 6090 and 60901 decoders? Yep, great for the consumers.
But there is no money in it for Märklin.

But as Tom (HO) said, there is no money in that for Marklin. The cost of the app is not going to be a serious revenue stream for them the way mfx+ fitted locos are. The only reason to charge for an app is it makes it not worth any other company trying to use it on their system, and Marklin get some traceability on where they are selling.

I could envisage the current Marklin app being upgraded to handle the mfx+ functionality with a cab view - and they would probably charge twice the price for it, justified by the development effort.

Goofy, an app is nice but with it's own problems too.

First off, we need a physical interface between the wi-fi and the track. This interface would at most be a complex circuit or at least a small computer that would require upgrades anyway.

At a recent train meet, we had a guy with a Z21. He had fun until his iPad drained. I switched his track to my CS2 while he charged up his iPad.
Another problem was his iPad went to sleep while we were studying the Marklin Magazine centerfold (Lufthansa train). A collision was imminent and in the rush to wake up his pad, he entered the wrong password and the trains collided.

There were a lot of other issues, mainly getting other people's ithingy to connect. It was not an issue for a simple connect and play but it was an issue to have another idevice to have authorization to make roster edits.

Half of the issues we had to deal with were not Z21 related.

I used the Main Station iPad app frequently but if I allow my iPad it to go to sleep, I can quickly run to the CS2 to change something or stop everything. No such luck on the Z21. I would at least have an e-stop on the Z21...

If Marklin would go all the way and only provide an app and rely on someone else to provide the wifi-track interface, then if there are problems, everyone is pointing fingers at everyone else...not a one piece solution at all.

Edit. Going back on topic. The new wave of decoders is 21 pin so we can have more lights and functions. This is the main reason for the new decoders.
As more people want to have more functions, the 8pin decoder is not going to cut it anymore. It is getting very easy to add the extra lights and functions.
I do see that the CS2 will be going through an update to allow access to more than the current 16 functions.

The challenge Marklin has is to do this while not making too much of a change to the current well designed display that we currently enjoy. Most users at first will not care to have the ability to have access to 17+ functions and will NOT like a smaller display that shows a lot of blank area for the few that have many functions.

I like the idea of the new decoders but currently am more comfortable with ESU decoders...but I use the odd mSD when Marklin has the odd sound file that is better than ESU. I will wait and see how far Marklin goes with this.

Some European dealers are still charging €100 for the M decoders that are soon to be superceded.
I guess the new decoders will be no different in price, so why buy now?

regards
Kimball

That was totally unnecessary to use locomotive model to equal as app!
Märklin also use mfx standard decoder.
So don´t use locomotives as bad excuse!

Sigh!

Glad he's not my accountant ...

Perhaps the reason is that someone else owns the patent to railcom, and Marklin don't want to pay for it to use it on DCC.

FACT :

Marklin and ESU are not friends at all, but fierce competitors in the digital equipment field !

WHY :

ESU totally ripped off Marklin who paid them to develop the CS1, and Marklin systems, including MFX, whilst ESU also developed the Ecos alongside and the old boffins at Marklin made the agreement so loose, that huge omissions in that agreement allowed ESU to "do there own thing" in parallel IE; the Ecos and after much angst and a new agreement, M4 (mfx) [thank goodness for that ]

RESULT :

An embarrassing underdone CS1 that was totally Usurped by the Ecos, in that it did not have S88, or booster connections, or a turntable page just to mention two (edit three) deficiencies.
Fortunate/unfortunate result for CS1 owners, ESU's "Central Station Reloaded" which us CS1 owners had to pay more money for when that was already developed, but at least we got a new Switched Mode Power Supply and a stylus for our money, the firmware, M had already paid for and was already operating in the Ecos, but we paid for it again


RAILCOM, developed by ESU and Lenz, and owned exclusively by them, and could be licensed, but Marklin would not do that on principal ! IMHO
I have seen it work and it is good

WHAT THE NEW M DECODERS BRING (IMHO) is; more functions and programming possibilities (and a better programming tool than the earlier one)

MFX+ has, and will always be, exclusive to New Factory Locos, so don't expect it to be available on the M retrofit decoders
I do have five or six MFX+ Loks and at this stage, and two more on order (Kl 41 37929 and 18.5 39030 ) but I don't have a CS2 on order as yet but I do think MFX+ is fun and I will include it's full functional ability into my new layout, but IMHO I think it could become just a tedious distraction after awhile

One more thing, I only own Marklin Locos (99.9% Digital and 95% MFX )

Hi Shane,
I have a MFX+ loco (37167) and I use it quite happily with old CS1 and MS1.
I am unable to use the cab control features, but that at the moment does not appeal to me.
I did not have to disable anything.
And even with a CS2, you are not obliged to use or activate cab control.

regards
Kimball

Computer software detects where a loco is located on the layout because it keeps a record of where the locomotive was. If I stop the program/CS2 and then move a locomotive to another section or swap the location of two the program will be pointless.

railcom doesn't have that problem as long as you have the needed hardware.

I'd also love to see Marklin including railcom support.

Goofy, you can buy an ESU Loksound decoder V4, and put it in a Trix lok but to use Railcom you will need an Ecos

I´m sure Märklins new generation decoder 3 will put in the Märklin/Trix locomotive as standard when you buy ready sound locomotive.
So you can choise mfx or DCC protocol by disable.
If you have CSx with the wi-fi you can simulate cabinet for both 2 and 3 rail.

That was fast delivery!

Nothing about additional options to implement automatic brake control? Still only done via a DC signal from a power source other than your controller?

It seems the new (forthcoming) mDT can be used like the current mDT: with USB flash memory and CS2.
If the decoder is in the loco, use the CS2 to make the changes.