Trix BR 89 Decoder
The Trix BR89 uses a dedicated 66839 1600 Milliamp Decoder for 21-Pin Connector, only four functions for 35Eu (60Eu RRP). Is there an alternate from Zimo/Lenz etc? Are manufacturers using dedicated interfaces to avoid user choice?

When I seen this 21 pole connecter come out I thought that would be it's purpose. It is expensive too at about 30 euros (tax free as I'm in Ozz). It has actually put me off a few locos due to the cost. Why pay 30 euros for a standard decoder when for an extra 60 to 70 you can get a sound one? :?:

Tim, I'd stick with the ESU LokPilot v2.0 or v3.0 that I emailled you about. Unsurprising that ESU offer compatible decoders as I understand that their DCC console 'EcOS' has the same parentage as the Marklin equivalent. Steph

Steph, Thats true, but the EcOS doesn't have MFX protocol yet even though ESU built the Marklin central station! I would personally go for the v3.0 but that is a personal choice. John

I'm just a bit bemused as to what all those pins are for...seems a backward step to me to put such a huge plug/socket arrangement on a decoder... I can only see the point if you need lots of external functions, certainly not for sound, which can be completely addressed using SUSI... assuming sound can be completely catered for with the SUSI interface (four connections) and the standard NEM eight pin connector fully addresses lights plus one extra function, just how many pins do you need in total? I'd suggest there's a limit to additional functions you'd be able to use, OK you can have a smoke generator, raise and lower pantographs, maybe an auxiliary lighting circuit for the cab or maybe a warning light, couplers, but what else? I can't envisage any situation where you'd need more than four extra functions (excluding directional lights) so what do Maerklin/ESU use those extra pins for? I can see only 15. Track 2 Motor 2 SUSI/Sound 4 lights 2 Return 1 4 functions 4

Thanks for the info Frank... that kind of makes more sense now, though I'm not sure how you'd use three synchronisation inputs. It still looks over complicated to me, although I concede it seems to help make the system more flexible and futureproof; it'll be interesting to see if presenting clocks and databuses on the interface leads to the development of "daughter" modules for mfx decoders. It's also kind of ironic that putting all that effort into designing such a comprehensive interface will be of limited value if it isn't truly an open standard to allow other manufacturers to exploit its features... let's hope ESU and Maerklin steer a sensible path through this issue. Has NMRA taken this up as a standard?

If the capacitor is the interference suppression capacitor for normal DC operation, you don't need it for DCC - in fact you're better off removing it altogether as it can cuse problems ith DCC operation (a capacito act as a short circuit to high frequency signals)

Either it's not for DC interference suppression or it's needed for the 21 pin interface. It's not needed for NEM 651/652 decoders. I guess it could be something to do with the lighting, but can't really see why it would be needed. I do not have the model so without further details I cannot throw any more light on its use. Where is it connected? is it across the motor brushes? What type of motor is it? is it a can motor with permanent magnets or a coreless? With either of these, I have had no problems with removing everything from the brushes (chokes, resistors and capacitors) and soldering the decoder orange and grey wires directly to the contacts for the brush holders, and the red and black wires direectly to the pickups, with a variety of decoders (Lenz, Zimo, ESU), and also where 8 and 6 pin sockets are provided. On Guetzold models with an 8 pin socket, the capacitor is usually soldered onto the jumper, so by removing the jumper to insert a decoder, you also remove the interference suppression capacitor.