|
I'm fiddling with
a Loksound 5 decoder, with DecoderPro. I've run in to an issue while doing
so that leaves the decoder bricked, ?requiring a factory reset to
get out of it.
Specifically the decoder is a Loksound 5 21 pin, bootcode 5.0.5 and Firmware 5.1.85, Type 63, according to DecoderPro, ? The sound project is for a UK Dapol Class 68 locomotive, project by "LegomanBiffo", which in the Loksound 4 version is the Dapol factory sound project. ?I have a version on a Loksound 4 which works decently well. ?I purchased a new L5 decoder with the "upgraded" project on it - which appears to be a quick conversion from the L4 version as in the Info pane it still says Loksound 4 in the Loco Name field. It sounds the same and has basically the same function key setup. ? The symptom is that something I get DP to do to the decoder causes it to behave as though Drive Hold is turned on, permanently. ?Right now, I have not discovered exactly what this is, but I'm zeroing in on something in the Function Map pane. ?I have a custom CV setup for this loco, and I can run all the changes into it from other tabs, and the loco still works. ?If I then start to make changes on the function map pane, things start to go wrong. ? I've gone back to the project's original set of function map entries, which go to row 31. On row 33, I added F22 as Brake 1, and the loco still worked. I then added row 34, F23, Brake 2, ditto - and I also went to Advanced and set some paremeters for Brake 1 and Brake 2, and the brakes worked as I expected. ?But the loco was too loud, so I then set row 40 to F28, Volume/Mute,and toggled it. ?Bricked - as far as movement is concerned. ?Light controls on functions OK, sound triggered functions OK, just no action from the loco. ? Could the issue be F28, or Volume/Mute? ? (I noted, and this may or may not be a red herring, that ?(according to the L5 manual) Volume/Mute is 128 in Control CV O, while Drive Hold is 128 in Control CV N; is it possible that somewhere the wrong CV is being changed, not that doing so should leave the decoder permanently in Drive Hold, if indeed that is happening). So I reset it again, checked that the loco would run, went back to my intended function map, erased actions on the F28 row and rewrote the entire decoder in POM mode. Bricked again. ?Reset on program track, erased the entire row with F28, and it still bricks - indeed, it actually bricked while writing the function map pane. ? Could the issue be row 40? No, my intended function map setup goes to row 38 only. ? So the question is whether this is a Loksound 5 feature/bug, a Decoderpro function map issue, ?a sound project issue, or possibly even a Mick issue. Just to complete the picture, I'm doing this from DecoderPro connected to a Digitrax DCS240 Command station via a LocobufferUSB, using the DCS240 program track outputs (which is sometimes another story) or POM mode. ?I have DP programming settings setup with Allow Caching... and When Possible.... both unchecked. As an aside, I also note that L5 no longer has Notch Up/Notch down functions - anyone miss that? ? ?I do appreciate the F-key brake functions, at last. Soundtraxx have had that functionality since 2005. Mick ______________________________________________________________________ Mick Moignard Specialising in DCC Sound p: +44 7774 652504 e: mick@... skype: mickmoignard Notes and Domino: ?Rapid app development, , hi-code, low code, no code, noSQL. What else do you need? ? |
