Hello, I’m new to forums so please just let me know if I’m not doing this right, Thx.
I have 1 Loksound XL V3.5 and 2 LokpilotXL V3.0 boards that I am installing in an A-B-A set.
I’m not sure if I should use them all under the same address thereby calling up all three with a single address or if I should have a different address for each board and consist them @ the throttle?
Also can anyone say when the mars lights on either end should be operational and when 1 or both is on/off? These are in EMD F7’s and currently the seperate headlight is wired on “0” key for front headlight
Primarily,I’m needing info on how to make the rear A unit run in the same direction as the front one when I have them all together and I’d like to be able to “switch ends” at times if possable.
Also, my mars light connection has 4 wires, 2 for each grain of wheat bulb (I think).
Can someone help me with seting up the wiring to those? Does it go with one bulb on Aux 1 and one on AUX 2, then set up Aux 1 to be on steady while flashing Aux 2?
I don’t have this specific decoder set, nor any Mars lights, so I’ll stay away from that part.
I would give all units separate addresses unless they are hard-coupled together with permanent drawbars rather than couplers. I enjoy the simple exercise of bringing engines together and consisting them, and then breaking the consist at the end of the run and sending them off to other jobs. Separate addresses let you use them all independently. (Even B units can be operated from “hostelers’ cabs” for use in engine service areas when the A units aren’t around.)
Your DCC system instructions should tell you how to create consists and put engines in “backwards.” It’s not done the same way for every system, although the results should be the same.
There was an MR article a few months back about “advanced consisting” and how to set the engines up so that the lights behave the way you want them to. It involves setting up certain CVs in the decoder to do this.
You can speed match even if they have the same addresses - having the same address doesn;t mean they have to have the same settings for start, mid, and top, or the same values in a speed table.
How to proceed for the OP depends on the intended use. If the units will be mixed and matched, then definitely individual addresses are what is wanted. If they will always be operated as a set, like they had drawbars, then by all means use the same address.
I’m aware that each decoder can be programed independently, but when they all have the same address then only one at a time can be on the track when your are adjusting the speed settings. It’s just easier when they each have their own address…at least for me.
I guess I should have worded it more carefully. I didn’t mean to indicate that common addresses COULDN’T be speed matched separately, just that separate addresses is easier.
I have an A-B-A set of P1K C-liners. I used NCE DA-SR decoders, but some of the basics should apply.
I use them in the set at all times. I set them all to the same address (28). I chose to put 28A as the leader, 28B runs the same direction, and 28C is the rear A unit. On 28C I set CV29 to 7. This reverses the direction, no analog operation, and 2-digit address. If it needed a 4-digit address I would have set CV29 to 35. I blew up the LED headlight in 28C, so it trails 99% of the time. If I fix it, some function remapping will get the headlights working the way I want.
If you break them up and use them with other power, separate addresses would be the way to go. Not sure what system is in use. Lenz seems to prefer advanced consisting with CV19. The consist address is 2-digit. For CV19, forward running engines would use the 2-digit consist address, 1-127. To have it run backwards in the consist, add 128 to the consist address. For example, consist address 28-rear engine would have CV19=146.
The Mars light should have its own function. Probably should set it to one that isn’t in use for sound. Mars light would be in use running on clear track, especially over grade crossings, very noticeable to motorists. When meeting other trains, etc, Mars light would be off, headlight dim.
as phoebe vet says it is easier to speed match with different addresses, but once you have them matched you can then change the addresses to all the same if you wish. one down side with all the same address is that when you put the lights on, every unit will put it’s lights on!, better to consist different addresses as some systems can then sort the lights to what they should be when you switch them on rather than all of them. i suppose with some function remapping it may be possible to only make the lights at the ends work with all decoders on the same address, or perhaps even just disconnect the lights you don’t want to come on so you don’t have to worry about remapping or different addresses.
I find it much easier to use the same address for cab units, and I use the lowest unit number, then switch the direction of the trailing unit. That way I don’t have to write down or remember arbitrary consist numbers. It’s also easy to tell the direction the set will move by simply rembering the lowest numbered unit (selected) will move in the direction selected. If lighting is simple, as in my case, the light follows the direction, so the light of the unit moving “forward” is lit automatically.
I’m using LokSound in PCM FA and Genesis F3 and F7 units.
Getting ready to start on my Sharks and Erie Builts.
If you have the LokProgrammer, the function mapping screen lets you select if the funtion is active in forward, reverse, or both. Very intuative, and the solution for your Mars light issue.
I don’t have a LokPilot yet. Please keep us posted on how they interop with the 3.5 sound units. I’d like to pull expensive sound from B units, but keep them powered.
That was another next step of mine,but wasn’t sure if the 3.0 ver was the equivalent of the motor control side of the 3.5.
First off there will be a big difference in start up and running between the sound equipped loco and the non sound locos. You will have to experiment and add momentum in CV3 of the lokpilot locos to match the start up of the loksound decoder. It can be done,I have a Loksound in an SD9 and run it with a TCS decoder in the mate loco. CV29 will determine which direction you want the loco to run. If you want to have the rear loco run in reverse just add 1 to the value in CV29.
Setting them up with the same address will work great. Consisting them also will work. If you take them to another layout than you will have to break the consist and remake it at the other layout.
The headlight will be hooked to the white and blue wires. The mars light can be hooked to the yellow and blue wire. You will have to remap the yellow light function to another button for independent control. It would probably be best to map it to F3 due to the horn and bell functions being used in the loksound decoder.
WOW! Thanks for all of the great replys and all the help from this friendly group!
Working through the night on this project, the priorities have changed. The lighting is now a secondary concern to the biggest issue…getting the boards to react to the changes entered in to the CV’s.
I’m using the loksoundXL and lokpilot boards with a digitrax 402R duplex radio/infared throttle.
#1 Although I can get CV253 to accept a “good” value, I see no change in performance on the track. The loco starts immediately when set at at value 1 or value 255 ???. (I don’t yet understand how/when to set the “bit” in the CV).
#2 in "special functions, step 15 in the user manual, it notes that in order to make loksound and lokpilots start out in unison, lokpilot needs to know when soud is on or off. I understand that fully. What I’m now having probs with is that sound on/off has to be set on F1 (B?) . I can’t learn how to access B on the digitrax throttle. The digitrax book seems to indicate that A, B & C are researved for some future development use. Currently, F1 is programmed from digitrax for the Bell.
Thanks in advance for all your help.
(I tried the forums on the ESu website but I can’t get through the German language!
I have the 2 locos starting up together now by putting a start delay on the locpilot loco so it will wait to move till the locsound loco spins up.
I had to enable "sound on/off in the lokpilot board to achive this as per the instrutions. By default sound on/off is assigned to F1. All is great,but now the bell which is programmed on F1 on the digitrax throttle has to be ringing all the time on loco #1 in order for loco #2 to see “sound on”… thus enabling the required start delay
Is there a way to change the "default F1 sound on/off to a different key?
I’m still very confused in understanding the procedures between "enabling a specific function (say to AUX 1) and assigning that function to a specific F key.
In this case, need to enable sound on/off (set CV 148 & 151 to 4), but how to get t off key F1 and move it to F12??
I can not get sound on/off working at all on the Loksound loco
Instead of using F1 for start delay why not add momentum to CV3 in the Lokpilot? Remapping CVs are in the instructions for your decoders. Loksound has a lot of info on those tiny pages. You may want to download the instructions to your computer and print them out larger off of their web site.
ANother useful option is to download DecoderPro and just set it up using the Loconet SImulator, it will run standalone that way and be fully functional except it won;t, obviously, read or write any CVs to your actual decoder. You can then open the programming tool and select the appropriate ESU decoder, and make the changes via the check boxes on the various pages. There is another page which lists all the CVs, and whichever ones you have changed by making the checks will be highlighted in red. Program those in in your usual manner and you will have the decoder operating as selected in DecoderPro.
I have some factory 21 pin LokSound units that have the “mute” on F1 like European units.
The “normal” assignment for North America is F8.
I remap all of mine to be silent untilI I press the function button (opposite of default), which also plays a short startup sequence. I have posted the CV mods for this several times here. I also remap that function to F6, so at least the button is the same as my BLI products, even though the sequence is not.
Interestingly, the Euro standard is silent by default, while American is sound on by default.
The LokProgrammer clearly illustrates function assignments in graphical “radio button” style, including any associated sound “slots”. Not sure how to remap with straight CV programming. I must be spoiled.
If I have time I might be able to read the CV settings of a factory sound on F1 unit, then make my function map change for the sound to be on F8 in the GUI, then read back what CVs changed. Might be a few days…
Afterthought…I wonder if “sound on/off” and “mute” are different…
I’ve now d/loaded & installed Decoder Pro…looks like I’ll need several hours of reading before I can understand that. IE: how to assign sound on-off to function key F12 in F, R & stopped and how to remove sound on-off from function key F1.
Can anyone help me understand more easily the procedure to enable or turn on a function and how to assign/remove that function from an F key?
I’m thinking mute & sound off-on are different. mut is currently on F8 and sound on/off is currently on F1, but I’m not sure. What I need to leard to do is to remap an F function key