0 Members and 2 Guests are viewing this topic.
I've installed an ESU LokSound Micro decoder in a Kato SD40-2. That was fun... not... I've added an LED on the AUX1 (F1) function and programmed it as a Gyralight. So far, so good. Now, I want it to operate with the F0f function - if the headlight is on, the Gyralight is on. If I'm reading the documentation correctly, the sequence I'm following is this: CV31=16, CV32=2, CV330=5 (1 (headlight) + 4 (AUX1)). This should (if I'm reading it correctly) map F1 to the F0f function. No love. I've tried setting CV330=4 to see if F0 would activate the Gyralight (F1), but again, no love. If I press F1, the Gyralight works like a champ. If I press F0, the headlight works like a champ. I just can't get the Gyralight to activate with the headlight (F0). I've tried both Page mode programming and Ops mode. I'm using a Digitrax DCS100 with DB150 boosters. Help. Me. Thanks in advance,Chris
You would make a great teacher.
Hi Peteski.That comment made my day - because in fact teaching is what I do. I'm a [now partly retired] professor at the University of Illinois.https://law.illinois.edu/faculty-research/faculty-profiles/john-d-colombo/John C.
By the way, changing the value for CV266 as indicated will not alter the behavior of F1 - that is, it will still turn on the gyralight independently. To change THAT, you will need to reprogram CV298, which is the physical output control CV for F1 (set it to zero, and it won't turn on anything).Mastering the reprogramming of the function keys for a LokSound Select or V.4 sound decoder is complicated, but there is a logic to it that makes things straightforward once you understand it. First, you have to quit thinking about lighting outputs as "functions". I know that's how we've referred to them for years, and still the way most manufacturers refer to them (e.g., function outputs). But in ESU's world, you have function KEYS (e.g., F0, F1, F2, etc). Instead of thinking of the wires as "function outputs," think of them simply as physical outputs (or in my case, I think of them as "output wires."). ESU calls the output wires the "headlight," the "backup light" and then "Aux 1," "Aux2" etc. A four-function decoder from ESU has the headlight wire (white); the backup light wire (yellow); the Aux1 wire (green) and the Aux2 wire (purple). You can tell a function KEY (e.g., F1) to turn on or turn off any of these outputs when pressed by programming the corresponding physical output CV (e.g., CV266, for F0 Forward). You can also assign sounds to the function keys as well as logic control. For example, you can use the logic functions to set up F2 for "grade crossing" behavior, so that when you blow the horn, the bell comes on and the ditch lights start flashing for a pre-determined amount of time.The flexibility for programming the function KEYS on a LokSound is almost unlimited, but to take advantage of it, you have to sort of re-orient your thinking. For each function key, you need to think "What physical output wire do I want on or off?"; "Do I want to add any logic functions - like, do this only when the engine is stopped, or in reverse, or going forward, or only if another function key is on at the same time?"; and "Do I want any sounds to happen when I press this key?" Once you answer these questions, then you can program the appropriate control CV's to make it happen (the control CV's are all listed in the LokSound manual; I use the V.4 manual, because it is more up to date than the Select manual and the two decoders are identical when it comes to these things).Once you get used to this approach, it kind of all falls into place logically. But it's different from the way most of us are conditioned to think about "functions."John C.
Mastering the reprogramming of the function keys for a LokSound Select or V.4 sound decoder is complicated, but there is a logic to it that makes things straightforward once you understand it. First, you have to quit thinking about lighting outputs as "functions". I know that's how we've referred to them for years, and still the way most manufacturers refer to them (e.g., function outputs). But in ESU's world, you have function KEYS (e.g., F0, F1, F2, etc). Instead of thinking of the wires as "function outputs," think of them simply as physical outputs (or in my case, I think of them as "output wires."). ESU calls the output wires the "headlight," the "backup light" and then "Aux 1," "Aux2" etc. A four-function decoder from ESU has the headlight wire (white); the backup light wire (yellow); the Aux1 wire (green) and the Aux2 wire (purple). You can tell a function KEY (e.g., F1) to turn on or turn off any of these outputs when pressed by programming the corresponding physical output CV (e.g., CV266, for F0 Forward). You can also assign sounds to the function keys as well as logic control. For example, you can use the logic functions to set up F2 for "grade crossing" behavior, so that when you blow the horn, the bell comes on and the ditch lights start flashing for a pre-determined amount of time.
It would be nice if all manufacturers got better at using unambiguous language:'To map function key 1 to the green wire, program CVs as follows..."'The white wire is the headlight by default, but can be mapped to other function keys by following these instructions...'Etc.Same goes for Decoder Pro files.
Author
Topic: Help - ESU LokSound Gyralight and Function Remapping (Read 4225 times)
