but was wondering if others have come up with a fix for decoder files and would like to share? what do you mean ?

John

I guess this is something that would help more with LokSound decoders instead of LokPilot decoders, but not entirely. With the LokSound files, you download them from ESU and load the sound and operating portions of the file into the decoder. These files are generic files specific to a particular prototype, but not a particular brand or model of model railroad loko. In many instances these files are used without any, or very minor changes. But for some, the file needs work. ESU states in the LokPilot and LokSound instructions that aux 4 needs to be on continuously in a sinus drive loko to power the sinus drive circuit. As I learned with VT 8.05 #39080, that is not always correct. Once I realized their statement is not always true, it was easy to deduce the rest of the aux functions. Many sound files do not exist at ESU's site, ET91 and RBe 2/4 in my case. These files can be created with sound bits that too are downloaded from ESU's site. My thought process: In those cases with unusual lokos or non-existant files, if you have already worked out a solution, why not share?

In a broader sense, Tom's suggestion of a data base listing aux functions for various models would be helpful to most, but if you are creating unique LokSound files, or like the ease LokProgrammer provides for programming a decoder, then ultimately those files would be the easiest and quickest way to share that information.

If ESU's mobile decoders are what you use and you do not have a LokProgrammer, then you are working under a significant handicap. The simplicity it provides for custom programs makes the first time you try it near epiphany in the experience. With LokProgrammer, you know what program you have installed. No wondering "Did I add up all the numbers right? Is it not working because my program is wrong or my assumptions for what I needed in that program are wrong?" With LokProgrammer I could deduce what was wrong with the program in the VT 8.05 because I could directly corelate the loko's performance with a graph showing the program installed. You can't get that from a number that is a sumation of several functions.