Whoa. I really had no plans of posting these screen shots since the discussion is the D&H decoder. Then I saw the sophistication of the program ESU created for the Brawa V100, which is a part of this discussion. I thought some here would find it interesting.

The front headlamps are under three function or SUSI outputs. I haven't dug deep enough into the program to see where the actual switch is located. Those three functions are Aux 3, 4 and 5. Conversely, the rear headlamps are under three different functions, Aux 6, 9 and 10. See the top two lines of the first screenshot. So as I suspected, there are a lot of aux outputs (6) to generate the triple headlamps just so the special headlamp arrangements in the shunting functions buttons (F8, 9,10 and 11) will work as needed. In the conditions column for F0 they have added "not F9 not F10". This is how they turn off those white headlamps they do not want lit when shunting mode F9 and F10 are selected. They needed the "and X not Y" equation though because you do need F0 selected before you can select any of the shunting light functions (f8 through F11) see * paragraph 4 below. This "and not" equation is how they turn off the unwanted white headlamps for those two shunting modes. If you did not turn them off with the "and not" equation, then you would just have three white headlamp lit at that end when it is the direction of travel no matter what shunting function you selected.

The taillamps at the rear of the loko, line 5, "Physical output rear lights (1)" are activated when F3 is pressed and not F8 nor F9 nor F10 nor F11. So they go out when any of the four shunting light functions (F8 through F11) are selected. So the taillamps do not automatically light when F0 is activated, you must press F3 to turn on taillamps. They are direction dependent. Note (f) and (r), the direction component in the "conditions" column.

Lines 11, 12 and 13 of the first screenshot are the physical outputs when a shunting mode function button is selected. To get all the possible permutations, they used an aux output for each of the three white lamps at each end (repeat info from paragraph 1) and then build the light formation needed for that country's shunting mode by building it one lamp at a time until all the lamps that are needed to get that formation are activated. * The conditions line for these shunting modes is read "F0 and Fx". So you will not get the shunting function to activate unless you also active F0, the headlamp function button. * Except for the shunting function under F11. Note they use the direction component (f) and (r), but they have not used an "F0 and F11" equation in the "condition" column there. It is simply F11.

They also operate the coupling sound, see "sound" column, when functions F4 or F5 are pressed to operate the telex, aux 7 and aux 8 in the "physical outputs" column. And you get a fan sound when F6 is pressed to active the cooling fan, Aux1(1). I did not do a screen shot of the function output aux1(1), but I did notice the function is speed dependent and the fan will run faster as the speed increases. I did not check to see if the "coupler waltz" feature is activated when the telex couplers are operated, but as this is a feature the ESU V4 decoders support, I would bet it is there.

There is an incredible amount of stuff going on in this program. I have merely scratched the surface. I wonder if the D&H decoder has this level of sophistication? I would guess so since the circuit board for the connections to the physical outputs is probably the same and it's just who's 21MTC decoder is plugged into it. But they do not necessarily have to create all the shunting light functions. They may just offer the simple triple headlamp at both ends. I am sure many of those who write computer code can see and explain much more than I can. I might be able to understand it, but I could never write something so sophisticated. This has been an incredible learning experience that will surely help me with my own decoder programs. I imagine I will reference it frequently for now on.






For an explanation of how LokProgrammer works, see this: https://www.marklin-user...1-LokProgrammer-software

Oh yeah, It is a program written for an MFX compatible V4M4 decoder, see just under the "help" pull down at the top left of the screenshot. But, it lists more than 16 functions in the "Conditions" column. I have never seen this before in a LokProgrammer file written for an M4 compatible decoder. I know MFX only supports 16 functions, so I guess those at 17 and up, which are not available in MFX, get ignored.

Edited by user 11 July 2015 14:10:39(UTC)  | Reason: I keep discovering more and more!