A question on your question

Yannis do you have a Lok Programmer?  If yes you can programme almost all of the Aux functions to do anything you want and use any colour wire you want.  You can also programme any Function key on your throttle you like to operate Aux 1.   The hard part is working out a consistent set of Function buttons across your loco fleet.

I also believe that you can perform this Function mapping by using Decoder Pro on JMRI.  I have a Lokprogrammer so I haven’t tried the Decoder Pro option myself.

IMHO using an 8 pin connector on a V5 Loksound  is wasting the investment in the Decoder.  I have just fitted V5s to two locos using the V5 Direct board with its 18 pin “Next18” socket.  A better option maybe to use the MTC21 versions with one of Nixtrain’s Decoder Buddies.

I hope this helps

Thanks Peter

I do not have a lok-programmer but i might get one if they release a linux version of the software. I am using the Z21 which is very user friendly in programming decoders in general.

I do have a V4 loksound (8-pin) in a Kato GP35 but since it did not have a mars light i did not bother with extra lighting functions.

Why do you mention that 21-pin or Next18 etc... are better investments? I will be using these decoders in F units, the A units will have headlight + mars light (and possibly cab lights if it makes sense and it is not just a gimmick), the B units no lighting at all. With an 8pin version i think i ll be able to have those 2 extra lighting functions right?

If i opt for the 21-pin version i ll be using this as well:

http://www.esu.eu/en/products/accessories/adapterplatinen/21mtc-adapter-board-3/

If i am missing something feel free to advise accordingly.

Don’t need the programmer for CV changes

Number of Pins

Prior to sound decoders, 8 pins was generally enough for most locos.  In no particular order they were allocated as follows:

1. Motor - Grey

2. Motor + Orange

3. Right Rail Red

4. Left Rail Black

5. Light Common + Blue

6. Head Light  White

7. Rear Light Yellow

8.  Aux 1  Green

The ESU Loksound 5  has an additional 9 pins available (not all of these can be used for lighting functions)

If the existing loco only has an 8 pin socket then yes you can wire the additional lighting functions direct to the decoder.  However, the advent of various motherboards with either a 21 pin or 18 pin socket reduces the birds nest of wiring to an  absolute minimum. 

Three mother board options  are:

a.  ESU 51955 Motherboard. $10.99  with Next 18 socket

b. Nixs Trains Decoder Buddy. $13.95  21 pin socket and a separate plugin board for lighting functions.  This makes separating the loco shell from the chassis a lot easier.

c. TCS Motherboards.  $39.96 21 Pin socket and  Keep Alives already hardwired in place.

The ESU MTC adapter you mention is $12.39 so already more expensive that the ESU mother board.

If you buy the "Direct" version of the Loksound 5 it comes with the Motherboard included.

...thank you both!

Being in Europe, the Loksound 5 versions available for me are 21MTC, Plux22, 8-pin and 6-pin. I don't see a Next-18 version.

Similarly, for adapter boards, i got Plux22 and 21MTC only.

Not having a bird's next is certainly something that i would prefer, so the 21MTC might be tidier.

I don't have a windows pc so I might ask the whoever loads the sounds to sort out lighting functions / mapping for me using their programmer.

Talking about sound projects, if i understood it correctly, some are converted from V4 versions to V5 and some are V5? Has anyone observed any sound-quality differences? I take it for the examples that follow i am better of with S0711 than S0746, and actually 0711 does have a better function mapping to start with.

For example... S0583 (E8 dual 567), S0711 (EMD 16-567BC 2EXH NT, actually recorded from an F7A), appear to be V5.

While S0746 (EMD 16-567B) has a mention that it is converted from V4.

Side note: I take it the full throttle would work fine if in a consist there is a loksound V5 (lead unit) and a lokpilot V4DCC in the trailing unit.

Next18 is available on the micro

The Next18 is supposed to be the future standard interface in N scale, so all the V5 Loksound micros have a Next18 interface. The different variations simply use adapters to provide the 6 pin, 8 pin, cables only etc. options.

You can try running the Lokprogrammer in Wine. Another option is to consult the manual and just set all the CVs old school with your DCC system. It helps if your DCC system can address CVs greater than 512. If it can't you can still do it, because the loksound decoders have a feature to make it possible, allthough it requires three CV write operations for each 'actual' CV update. I did that with a Multimaus for a while.

I have a Loksound V5 on hand but not installed yet. From what I've read in the manual there shouldn't be any issues. I have loaded a sound project into it and hooked it up to a modified ZIMO LS8x12 for testing and found it sounded just like I would expect a V4 to sound like.

Trivia: The non sound Lokpilot decoders support the drive hold feature, but not the run8, coast or independent brake.

Thanks Orvio

I forgot to mention i was looking for HO scale... so the non-micro Loksound (hence the next-18 does not apply here).

I ll try it in wine to see if it works. In the meantime i did find of a new sound project (S0711) that does have a more favorable mapping to start with (AUX1 used as a flashing ditch light which i presume can be easily reprogrammed to a mars light even without a lokprogrammer).

Thank you for the info concerning the lokpilot. If three powered F units are enough to haul my passenger train (full consist of a Super Chief... circa 13 to 15 cars plus the two dummies, 1.5% to 2% inclines), then i wont be needing the lokpilots and i ll use just B units as dummies with speakers.

I must say the 21MTC does sound interesting... and much tidier... and it tempts me to install a cab light (so a 3rd LED).

You do not need a LokProgrammer

Changing the mapping of the function keys does not require a LokProgrammer.  You can also easily use DecoderPro.  The "problem" with replying is that there are so many CVs in an ESU decoder, and there is no "one" standard set of function mapping CVs. Each project can be different, so one needs to know what project is loaded in your decoder prior, and what, if any, other changes have been made, before directing which CVs to change.

There are 72 "rows" of function mapping available, and any row can be set for any function button(s) and any function output(s): sound, physical or logical.  You can do AND and NOT logic, as well (F3 AND F5;  NOT F6; etc) in a single row.  The CVs involved (257-511)  are indexed, with CV31=1 and CV32 between 0 and 4.

Newer versions of DecoderPro can read the settings of the decoder, and then the function mapping will show in clear English. You can then adjust the row that is mapped to F5, changing the physical output. 

European versions

Hi Yannis,

I am in France, do you mean that you can load US sounds on European versions of the loksound 5?

sounds....

Gerard, I have a loksound V4 (bought in Europe) loaded with a sound file (full throttle version) for an EMD567D3. Works great. I think the same applies for a V5, loading the relevant file (I will sound find out )

By the way with respect to my original question, I got the CV values info needed straight from ESU for a specific remapping i had in mind, great customer service i must say. I will have in mind decoder pro and lokprogrammer (via wine) for future uses though. You have all been most helpful (as usual) and steering me towards 21MTC was very welcoming.

Sounds, thanks

Thank you Yannis, I will try it with a loksound 5.

Gerard...

you are more than welcome.

A bientot!