For LokSound decoders, Decoder Pro function map pane is blank until you read the decoder. Every LokSound project has the capability of being completely unique. There is no set or standard function mapping. It would take thousands of unique definitions to cover all the possibilities and that isn't practical for anyone to spend their time programming. So until you read the decoder, you have no function map pane with any valid information.? If your project is showing different function mapping than the ESU bulletin for that project, then either the bulletin is wrong (I have personally never encountered this) or you have not gotten a thorough read of your decoder or the project did not write fully from LokProgrammer or some other problem. But DP having the wrong functions is not the culprit. It only reads what is there.
Was there another project on that decoder before you loaded 73825? Maybe the function mapping from a previous project did not get overwritten in LokProgrammer.
Have you checked the bulletin against the function mapping in LokProgrammer?
I will be interested to follow this thread to its conclusion.
On Tue, Aug 28, 2018, 12:11 PM Richard Knight <enginman@...> wrote:
Hopefully Dave can answer this. I loaded sound file #73825 into lok sound select direct. Also printed out function sheet from lok website. Read the decoder. Function map does not match the functions from the website. I think the D.P.function map was created before the drive hold feature went into affect ??? Thanks, Rick.
