Hi,

I'm trying to get a Re 3/3 (36332) to talk DCC. I've found that the equivalent Trix model (22390) is DCC-ready and I was wondering if its decoder (242332) could be swapped in place of the Marklin one.

I've also found two alternatives to the proprietary decoders, something small enough to fit the orthogonal position of this decoder. As far as I understand the sound is produced by the board, relying on the SUSI data from the decoder. So:
- Zimo MX634C. It explicitly lists SUSI as feature and enabling it by default.
- ESU LokPilot v4.0 M4 MKL (64618). The only one of the LokPilot versions that mentions SUSI.

Both are cheaper than Trix and keep alive capacitors can be added to them. So a priori I'd take one of these two.

But what is your experience, what would you recommend? Trix, Zimo or ESU? Anything else I should keep an eye on when selecting a replacement decoder?

Thanks!

.costin

Edited by user 21 August 2018 09:57:26(UTC)  | Reason: Not specified

Ok, it looks like Marklin's mLD/3 (60972) would also be compatible, but I can't find the physical size of the decoder in the manual or anywhere on the web... Can anybody tell me the length to see if it would fit the width of the loco?

And it can also be connected to a keep alive (60974). So yes, keeping with the manufacturer might be an option after all :)

Cheers,

.costin

The manual drawing is completely wrong for 36332. The decoder sits orthogonal to the loco, not along it as in anything else I have. I'll take a picture of it when I get back home. To get an idea of what I mean please take a look at page 24 of the Trix model. In any case, a sound decoder wouldn't fit the width of the loco. The current one is ~20mm long and couldn't be any longer than this.

Sorry, no experience with this, barely found out that this even exists. Lots of things to learn about in this hobby :)

Thanks a lot for the detailed info on the ESU decoders, it's good to know there is potential from others as well. But from what you are saying it sounds like I'd better give Marklin a try first. Will let you know in any case.

Cheers,

.costin

I have used quite a few Maerklin mLD decoders for DCC, and as far as I know they are designed to retrofit any Maerklin loco with a 21 pin board.
Your photo of the 36332 shows a 21 pin connection.
Why not phone your local Maerklin dealer and ask about the size and fitting, because that is where you will buy it anyway?

Kimball

Size of mLD3 decoder is 23 x 15.5 mm, Lokpilot V4 is 21.5 x 15.5 , Zimo MX634D 20.5 x 15.5 (from catalog)

regards

Hello costing,

do I understand you correctly: you already bought the Märklin art #36332? Now you want to run your new Re 3/3 with DCC instead of mfx? Your question is: how does Re 3/3 (36332) from Maerklin run under DCC?

I doubt it that your Märklin Re 3/3 will do it, whereas the Trix Re 3/3 can do it and mfx as well. This might be a serious complain to Maerklin worthwhile. Because both articles (Trix as well as Maerklin) are quite new. First offered in 2015. I did not made a full investigation, but on the Maerklin homepage Re 3/3 is listed only doing the mfx format. On the Trix homepage Re 3/3 is listed doing mfx and DCC!

I had a look in both manuals. Indeed, the Trix manual writes from a multi protocol operational decoder, the Maerklin ones does not! Also the decoder at Märklin has another spare parts # (242 202) than the decoder in the Trix loco (spar part # 242 408).

I would write to Maerklin asking if this is correct: same models but two different types of decoders. If YES, then request them to change your Märklin decoder against a multi protocol decoder for free. It is a misleading for the customers. Märklin is always very proud about its offered multi-protocol decoders and controllers, like the CS 3. Then it is inappropriate to give the same model one time a single-protocol decoder and the other time a multi-protocol decoder. If your Märklin Re 3/3 would have the Trix decoder on board, it would be very easy changing your Re 3/3 locos to the DCC track format for running.

Regards

TEEWolf

It's Ee3/3, Re3/3 does not exist

Sorry, yes, it's Ee 3/3, not Re 3/3.

I have received earlier today the mLD/3 (60972) and since 5 hours I'm struggling to configure it.

So, what works
- DCC :)
- motor and auto tuning
- light mapping to travel direction
- aux1 disables one of the rear white lights
- aux2 disabled the other of the rear white lights
- both aux1 and aux2 at the same time turn the one rear light red

But I couldn't figure out how to enable driving sounds and to map the sound functions. I don't see anything about how to map conditions to susi functions. Any suggestions for CV values?

As for asking Marklin for help... my mails went unanswered, not a bit of help. Too bad the machines are so nicely done, the level of documentation and support is terrible :(

Cheers,

.costin

I know, it's a bit confusing still. As mentioned above the sound is not coming from the decoder but from the motherboard (the original one seems to be a mLD).

This page also mentions using LokPilot for the 36332 model:



And then there is the fact that no sound decoder on the market is small enough to fit the space there, Marklin included. So back to square one, how to actually configure it to pass susi commands to the motherboard?

Cheers,

.costin

I think the missing step is the decoder programming USB dongle. I've checked out mDecoderTool and it has the option to add SUSI_F* as actions to the received F* calls. I have no idea how this translates into CV settings, the manual is really cryptic in general and particularly void of information in this area. Anyway, I'll let you know in a couple of days if this works.

And in the mean time I got a message from Marklin saying that the mLD/3 is the right upgrade part for this loco. Hurray, it seems I'm on the right track!

Until then another question: how do you figure out which motor type to choose? The options are (CV 52):
1. Softdrive Sine
2. Without feedback control
3. High efficiency propulsion C90
4. Bell armature
5. Direct current DC soft (default)
6. Direct current DC hard
7. Direct current DC 1 Gauge

The default value worked the best, I was more curious in what this advertisement actually translates into:


Settings 3 and 4 had funny behaviour even after the auto calibration, for a long throttle range it barely moves, then it's faster, then slower again to finally accelerate decently at full throttle.

A search by the motor part no (E239326) didn't bring any clarity in the picture.

Not a big deal, it works ok as is, just trying to build a knowledge base :)

Thanks a lot for your answers so far,

.costin