LMSFan72

2mm tower LEDs and drill out the high intensity light to fit them. Straightforward I’d think

@ColinB I totally agree that if you want all functions to work you need the right decoder. The only decoders that will do that are the ESU v5 - either Lokpilot or Loksound. However it’s not simply the case of the functions being logic level - actually the same pins on the ESU that the HM7000 has functions on operate the same way - pin 4 (AUX4) and pin 13 (AUX3) are logic level on both. That logic v full output on 6 function decoders is the issue we commonly come across on 21-pin decoders. This one is different: The Accurascale 37 requires 15 functions for everything to operate as designed. The 21-pin socket doesn’t have enough pins for 15 functions. It uses the 2 SUSI pins on the decoder (pins 5 and 6 I think) to “talk” to the circuits built into the loco PCB that has those functions built on it. Only an ESU chip can talk to the board that way. A Zimo cannot. That is why Accurascale specifically have the dip switch settings designated for “ESU” and for “non-ESU”. You’ll notice that the language never refers to NMRA standard or the number of functions. I originally thought that was just their terminology and somewhat “woolly” but it is actually very precise!

Coming back to the issue here. The Accurascale 37 is fitted with a PCB designed in conjunction with ESU. I believe it uses the SUSI pins on the decoder to talk to the PCB to use additional functions. It’s not really anything to do with the 2-logic functions in the HM7000 which would also be logic on the Loksound v5. It’s simply that the 37 is specifically designed for an ESU decoder.

Coming back to the issue here. The Accurascale 37 is fitted with a PCB designed in conjunction with ESU. I believe it uses the SUSI pins on the decoder to talk to the PCB to use additional functions. It’s not really anything to do with the 2-logic functions in the HM7000 which would also be logic on the Loksound v5. It’s simply that the 37 is specifically designed for an ESU decoder.

Looks like an ESU Loksound V4 to me

The HM7000 has only the 6 functions. I believe these are on the “standard” pins for a 21-MTC decoder. Accurascale have connected only the marker lights, tail lights and instrument panel lights to the first 6 functions. Now, they use the dip switches under the decoder to then make or break connections to other light connections for non-ESU decoders (ESU have 14 outputs which can control each light separately) but clearly they will not be able to operate everything. I have asked Accurascale if they can publish the detail of what each switch does but I would suggest that the engine room lights would be one of the least used so I suspect that is definitely one you’ll never be able to operate. I’ll update when I get any more detail.

I suspect it’s the difference in available functions. I’ll try and find some time to compare the pin functions to what Accurascale used. Have you tried the different dip switch settings too - I haven’t looked at those for non-ESU sound decoders but I’ll give that a go too…

I had a similar issue with the A4 on a Next18. It all looked like it loaded but then had the error. Loaded other profiles and they worked but not that one. I found that when I re-updated the firmware (even though it said it was up to date) and then tried again it then loaded it. Strange

Agreed, it's definitely a peculiarity to the MXULFA. Using a DCC EX++ on JMRI I have no issues reading CVs and running the chip. The only thing missing is a profile for these decoders in JMRI!

Agreed, it's definitely a peculiarity to the MXULFA. Using a DCC EX++ on JMRI I have no issues reading CVs and running the chip. The only thing missing is a profile for these decoders in JMRI!

Well, I got the Next18 version delivered yesterday. I put it into the socket on my decoder tester and tried to drive it (with my Zimo MXULFA). The Zimo firstly tries to identify the address and decoder so reads CVs before it will enter drive mode...but all it did was pulse the motor and fail to read anything...hmmm! Might have to try it with another programmer and JMRI!

With the zimo decoder you have a high end very flexible decoder. The sound project loaded is likely to have many customised features which may or may not be in your documentation. Depending how you got it you may start with the seller to help you. Now, it’s very easy to get confused between function keys and function outputs. The function outputs are the physical connections on the decoder. The function keys are what you map the outputs to in order to control them on your command station. Sometimes outputs are referred to as FO or as AUX. For example FO2 may be referred to as AUX2 in documentation and vice versa. F2 is your command station key. With a zimo you can completely map any output to any key so, for example, F5 might control FO2/AUX2. This is set up with CV values. Zimo also has even more sophisticated mapping called “Swiss mapping”. This means you can have other parameters control function outputs differently - for example a combination of command station keys and direction may control a function output differently. I would suggest you get a copy of the full zimo small decoder manual and look at the sections on functions, lighting and Swiss mapping.

Well, mine seems to exhibit all the same problems: wheels scraping, twisted track and upside down whistle. Haven't run the loco yet... I'll be seeing what Hornby say!

No, but the connections for it are behind the bulkhead (think cab light). The back of the bulkhead is pretty open so if the wires coil round they poke through - which is what I think is happening.

I think the wires will be pushing through the back of the cab just as a consequence of how the body has been put on. As far as I am aware there are no wire connections actually inside the cab, so, it's simply them finding their own space. Should be a removal of the body, check the wires are pulled back behiind the bulkhead and put it back on.