Hi!
DCC programming works well with the MS2. It's just the C sine motor driver board that can lead to problems - with all DCC controllers.
Programming on Main (POM) will probably help to set everything up - except for the address.

Decoder manuals are available from esu.eu.

I don't have the Gottardo.
Probably it needs one AUX to be always on for the C sine motor driver and another AUX to drive the switch-over of the pickup shoes.
Maybe an owner of the 39540 can report the AUX configuration of the original mfx decoder for you.

Hello Oliver,

I hope you enjoy a challenge, but if you are patient and persevere, you will get there.

I can not help you with CV specifics. I bought my LokProgrammer when I bought my first ESU decoder. The only CVs I change on the track is max speed and the two that control time between steam chuffs. But I do have sinus drive and dual slider sets 39080 and 39100.

Until I started researching an answer for you, I would have said the slider changeover relay will require two aux functions, but the program I have for 39100 says otherwise.

The decoder will have four automatic functions that are direction and running or stopped dependent. FS(f) and FF(f) are forward running and stopped. I do not remember which is running or stopped, but that doesn't matter as you will use the same functions in both. FS(r) and FF(r) are the functions for reverse. This is where you configure the slider changeover and activate the sinus drive power function.

For 39080:
FS(f) and FF(f) have aux 2 (Sinus drive power) and aux 3 (front slider) on
FS(r) and FF(r) have aux 2 and aux 4 (rear slider) on
aux 1 is interior lighting

For 39100:
FS(f) and FF(f) have aux 3 (sinus drive power) and aux 4 (front slider) on
FS(r) and FF(r) has aux 3 on
aux 1 is the table lamps
aux 2 is not used

As you can see, M is not consistent, but I expect one of the above configurations will work. I have found that not all sinus motored lokos need an aux output on to power the drive. Apparently in those lokos, they have the circuit board configured to do that without the need of an aux output. A wrong configuration will not damage the decoder, it just won't work as you need it. Edit: chapter 12 of the manual I reference below explains how to configure CVs for functions. I didn't look to close though as the LokProgrammer figures all that out for me. I just tick the boxes for the function I want under the function buttons and automatic functions. This is where LokProgrammer truly shines. I do not have to add up a bunch of bit values and hope I understood them correctly and did my sums properly. If you think you'll typically use ESU decoders, then buy the LokProgrammer now. You will understand once you start reading chapter 12.

There are some other configurations needed to make the sinus drive work. Enable SUSI (CV124 bit 3) and for forward and reverse running trim (CVs 66 and 95), you typically need a value of 128 for both fields. Without a trim setting, some sinus drives will not reach max speed. Turn motor load control off (CV49 bit 0). The sinus drive handles that. You will also most likely need to install a 470uf 25V capacitor. The sinus drive will typically cause an overload in the decoder. It will run, go into overload and coast down, then reset and run. Over and over. Page 26 of the LokSound decoder manual, Edition 4, May 2012, shows where to connect the capacitor. Use the diagram at top right. You do not need the diode, just connect the capacitor to U+ and GND. Observe polarity. Pages 49 and 50 of the manual referenced above also explains it. Note that they say aux4 will be the sinus drive power. This is (usually) correct for a lokomotive,. For your triebwagen, probably not. As you can see in the function maps above, M is consistent with their inconsistency.

The final hurdle is the Sinus drive POM interference. This may be a Catch-22 for you since your only programming option is in the loko and on the track. When the sinus drive is powered, as shown above you will likely have an aux on to power the sinus drive, it then (usually) causes interference with programming commands and the command you transmit to configure the decoder will not be recognized by the decoder. Your only option is to remove the decoder from the loko and program it with an ESU decoder tester (item # 51900) or a 21 pin decoder adapter (item # 51967) and wire connections 20 and 21 so you can connect the adapter to your MS2 and program the decoder.

If none of the two above aux configurations work, then you are stuck with trial and error. Then I would suggest you map the aux functions to four function buttons, one each. Then you can turn on and off aux functions individually and build a table for the configuration you will need. If you are lucky, you may be able to hear the changeover relay click back and forth and determine which function(s) control it. Note that you will likely need two aux functions on- sinus power and slider control, to make the loko run. Your last and best hope is that someone here has the set and an ESU decoder tester. They could install the M decoder in the decoder tester and the LEDs which indicate if a function is on will quickly and accurately reveal the proper configuration. This is what I do when I remove and replace the M decoder.

Good luck,

Link to ESU decoder manuals:
http://www.esu.eu/en/dow...anuals/digital-decoders/

When programmed on the programming track, the decoder has to send an acknowledgement - at this point the C sine driver may interfere.
POM is like radio - controller sends instructions, but does not care if anybody's listening.

Putting the decoder into another loco may help - but 21MTC configuration is not consistent and this could kill decoder or loco board or both if you put the decoder into the wrong loco.

On the Loksound Yahoo list, the guy who has done a lot of work porting the Loksound requirements to JMRI keeps telling people to download the Lokprogrammer software (it is free from the ESU web site) and looking at the function matrix. After you make changes you can evidently print out the changed CVs so you can take them over to the train room and work through what needs changing.

Another possibility would be if you have an Intellibox with a computer connection to load JMRI on the computer and work through the matrix from there. Dave has made great strides in making the JMRI interface for Loksound decoders (and by analogy Lokpilot) look very much like the Lokprogrammer interface.

But the problem is that there are so many possible variations the you do need to look at the matrix to figure out what needs to be changed and then to get it to tell you what CVs need changing.

I'm bumping this thread, as I have purchased this great Gottardo from Oliver some time ago! When testing the railcar today, initially I had some problems changing settings, as the CS2 couldn't read or write CV:s. I couldn't e.g. change the default address "3". However, on the net I found that there could be problems with ESU decoders on CS2, unless one temporary change the CS2 on SETUP > TRACK > GLEISFORMAT FUR LOKS to "DCC" only. After this, I could read and write all CV:s. As I had reset the decoder, I changed all the CV:s according to Olivers instructions above. Now for the reason I'm bumping this thread, for documentation purposes only: The railcar was running, but it was only crawling! Again, on the net, I found out that the reason was the Softdrive Sinus motor! I changed the CV56, "Operating range of load control", to "0".

Now the railcar is working great! Later, I will probably change for a Loksound decoder...