Hi!
It works OK. You only get 16 functions per loco where other controllers support 29 functions per loco. It seems that American sound locos often come with 29 functions ex works.
In general I don't like the user interface of the CS2: complicated, counter-intuitive, slow.
The CS2 does not support RailCom or RailCom+.

I don't have severe issues with DCC decoders from different manufacturers.
I prefer DCC. I switched off mfx and try to avoid MM when buying locos.

The biggest problem with European rolling stock are Märklin couplers colliding with the buffers on non-MäTrix rolling stock. Not an issue with American rolling stock that does not have buffers.

I run both fx, mfx, mfx+ and DCC with my CS2. ( I have both 2 and 3 rail C track).
Yes currently there is a limit of 16 functions but most DCC decoders can be programed to get your most important functions up front.
If there is demand, I am sure that there can be a way to alter the CS2 programming to access more functions.

I have a Rapido VIA Canadian and it works well on the CS2. It was easy to consist the loks and I have an A-B-A lash up, all powered although I had to wait to get the powered B chassis. With all metal wheels and 14 cars, I will need the 3 loks on my hills.

DCC programming is more clunky that the slick programming that we have for fx and mfx. However it does work.
I would recommend that when you do serious programming (like a new decoder), that you set the CS2 to only be DCC or MM in the control setting until you get familiar with it.
I have had multi decoders go funny when trying to set the preferred "language". i.e. Set my CS2 to MM only when programming a new multi-decoder to m or m4 or mfx. DCC tends to take precedence because unlike mfx, it is not bidirectional communication.

I have been maintaining my NA clubs loks so I am exposed to a lot of different dcc decoders. Our club loves the ESU decoders but some diehards prefer the Digitrax because they are used to it. ESU has so many options that it is hard to keep track.

Getting NA rolling stock to run on C track or Trix C track is another thing. Rapido products are very close to scale...that means that curves have to be large. I had to spend about an hour per car to nip and tuck away piping that interfered with the swivel range of the truck. As it is, I could only have a minimum radius of 20.25 " (R3). The loks were short enough to not need much work.
Second is this. The C track is designed for larger flanges so that means that the NA cars will wiggle on the switches. You can build up the flange rests if the only wheels going on the rail is only short flanges that NA loves.

Thanks for brining this topic up... I would like to hear other chime in about their CS2 and DCC experiences. I am stuck with my CS2 and so far I am still happy that I made a good decision. This predicament also forces me to find solutions rather than complain and that is not a bad thing.

IMHO, for what it is worth, If you are looking for a Controller for DCC, or more particularly are not concerned with MFX+ then go for the ECOS

I will probably succumb to the weird ways of the CS2, for my layout, as I am a Marklin MFX fan and I am intrigued by MFX+.
That said I have my trusty CS1-R to fall back on which is really an Ecos with Marklin logo's on it

I run all my loks on DCC using a CS2. I have installed lokpilot V4 decoders in all of them. After I convet them from analoge to digital I use a sprog V3 with JRMI to program and test the engines and all the data is stored in my laptop it is so easy to use. Why would I use anything else ?

Edited by user 22 February 2015 18:45:57(UTC)  | Reason: Not specified

Awesome, thanks Søren and others! Will take another look at the ESU. The appeal of the Marklin stuff is it seems to be more consumer friendly so far.

We know you think so, you already said so. Luckily "user friendly" is a matter of personal opinion and preference, I for one, thinks that CV programming using the CS2 is easy as pie.

Sorry to disappoint you, but yes I am comparing the two. I guess you missed the spot where I wrote "cheap". The ESU mobile control (the new one, the old one is not available anymore) costs around 260 euro. That is a lot of money for a handheld. I may have other needs than you. We are usually five to six people operating on a system. With the Mobile Station 2 I can have sockets around the layout and plug it in where needed. The MS2 is usually available for around 55 euro. Way cheaper than the ESU controller.


The MS2 and other controllers are not irellevant if you do not have an Iphone or Android. I have a Windows device, which does not have the option for an app at the moment. It is also my experience that the mobile apps can suddenly disconnect, which leaves me without control of the train. That is not an option for me.

I've never thought that my mobile phone is a good idea as a controller for my trains. What happens if the phone rings, or I get a text message? Much better in my book to have a device which is dedicated to the purpose!

I know that the current trend is to do everything on one's phone, but really, I don't think it's so practical.

I like my MS2, it does a great job of controlling my trains, and it has zero chance of starting to buzz, ring, ding, notify, or anything else while I'm enjoying my trains!

Hi Matt,


I wrote that the ESU mobile controller costs to much for me - and it does. I was looking for a digital system with a cheap mobile controller. When I made my decision I compared them with regards to the features and the cost. I think that is fair thing to do, since they are both mobile controllers and supposed to solve the same problems. My opinion is that the wireless deal with the ECoSControl Radio is not worth the additional cost - especially when I need more than one of them.

Yes, the ECoSControl Radio is a wireless controller, but I honestly do not see any differences that justifies paying between 150 - 200 euro more for it.

I think I can do more with the Mobile Station 2. With the Mobile Station 2 I also get a nifty little controller that I can use without the Central Station 2 for quick setups, testing purposes and the like. That also matters to me. In my research I did not find any information about being able to use the ECoSControl Radio, on its own, without the ECoS.

At the end of the day it is a matter of personal taste.

Hello Søren,


We have differences of needs and/or opinions. I am not questioning that. I prefer a wireless device. I just wanted them to understand that there is a technical difference between the two besides the price. Your post left the impression that one just simply cost more than the other. You can not justify the difference in cost based on your needs. Perhaps their needs are different and they can justify the cost difference. If something doesn't fit your needs, then at times, it does not matter how cheap it is.



Completely agree. We usually buy what we want and/or need.