Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Locked
Re: Function mapping on ESU V4
#esu-decoders
¿ªÔÆÌåÓýStefan and Michael? Read the documentation [RTFM? ;-)], Unfortunately the ESU decoder manuals are not a great help with the function map. They just present a bewildering array of Function Map CVs (640 for V4, more than 1,000 for 5). A good resource is Phil Dunlop's excellent unofficial LokProgrammer manual, found in the Files area of the LokSound group. it is very easy to do, I have done it a number of times for my own small roster and for friends. Here's an expanded version of this: 1) You must use New Loco->Read Type from Decoder and use the model it picks. 2) You should use Direct Mode to read these decoders (despite misinformation to the contrary peddled by some OEMs). Some DCC systems will fail to read some CVs in Paged Mode or may return incorrect values. 3) You must read the Decoder Default CVs. Reading the full decoder is essential, particularly with ESU decoders where there are no "standard defaults". Each sound project has its own "factory defaults". All ESU sound decoders are manufactured effectively blank. When a Sound project is loaded to the decoder (using LokProgrammer software) part of the procedure is to write a new set of "factory defaults". Because of a known (but as yet unresolved) race condition with certain decoder settings variables in JMRI code: i) Use "Read Full Sheet" on the CVs pane instead of "Read All Sheets". It is less likely to cause errors when reading a decoder with lots of CVs. Once finished, some may be missed (displayed in red). Use "Read Changes on Sheet" as many times as needed until no red items remain. (Hint: Click on the Status column in the CVs pane until you see a down arrow. All the Red items will then be at the top.) ii) After you make changes on a programming sheet, don't use Write/Read changes on that programming sheet. Instead, switch to the CVs pane and use Write/Read changes on (the CVs) sheet. The result is the same but it will never trigger the race condition. You'll also see a number of messages in the JMRI System Log like this: "ERROR - Variable=xxxxxx; Busy goes false with state IDLE" Ignore these as they don't indicate a real error, we'll fix the problem in a later JMRI release. 4) Save the roster entry once you have successfully read all CVs Programming the Function Map - Read the information about the Function Map on the README pane of the Roster Entry. - Ignore the line numbers of the Function Map. They are just there for convenience and bear absolutely no relationship to F keys on your throttle. - You read the Function Map by reading across a line (ignoring the line numbers). So your decoder will most likely have a line that reads: "F0,Forward Headlight[1]". There will also most likely have a line that reads: "F0,Reverse Rearlight[1]". These lines may be on any line and not even in that order. The line order doesn't matter in the slightest, nor the lime numbers. - To change an F key assignment, you simply find the line that mentions what you want and change the Conditions (first box) in the line. So if you want to change the Rearlight to F5, you'd Change the Conditions box to read F5 (uncheck F0 and Reverse). If you accidentally left F0 checked (the box would read F0,F5 Rearlight) you'd have to have both F0 and F5 on for the Rearlight to work. - When you remap you will almost certainly end up with the F keys out of order as you read down the page. That doesn't matter in the slightest, nor do any blank lines. (You can reorder the lines by selecting the radio button in the first column of any line and using the Up or Down buttons to move that line. But that's only necessary if you want to be obsessive, it makes no difference to the decoder and you'll have a lot more CVs to write when you do a Write Changes.). Dave in Australia |
to navigate to use esc to dismiss