Function Mapping: Assign Buttons, AUX Outputs & Sound
Decide which button controls the headlights, tail lights, cab lighting, shunting mode, digital coupler or sound. This guide explains conventional DCC mapping, advanced mapping, operating conditions, output assignments and a safe testing strategy.
What does function mapping mean on a model railway decoder?
Function mapping determines which button on the digital command station activates which decoder function. F1 may, for example, switch AUX1, F2 may control the red tail lights and F3 may simultaneously activate shunting mode, white lights at both ends and a reduced acceleration delay.
Three separate levels must be distinguished: function button, logical function and physical output. One button may trigger several functions. An output may react only in a particular direction or while the vehicle is stationary. A sound function may not use a physical AUX output at all.
Conventional DCC mapping uses defined CVs and bit masks. Modern decoders frequently provide advanced mapping with considerably more function buttons, operating conditions, outputs and logical combinations. Extensive projects are therefore easier to create using manufacturer-specific software.
Before the first mapping attempt
Software cannot replace the correct electrical output assignment
Function mapping does not change the wiring. A load must be connected to the correct amplified output or a suitable vehicle circuit board. Logic-level, SUSI, servo and loudspeaker connections must not be treated like normal AUX outputs.
Manufacturers offering extensive function mapping
The terminology and mapping tables differ considerably. Always use the instructions for the exact decoder family installed in the vehicle.
Understand conventional and advanced function mapping
NMRA DCC mapping
The conventional method uses CV 33 to CV 46, among others. Bit values determine which outputs respond to F0 and subsequent function buttons.
Advanced mapping
Modern decoders manage assignments in larger tables. Buttons, outputs, direction and operating conditions are stored together as a mapping row.
Logical functions
Shunting mode, momentum override, sound fading and volume do not necessarily use a physical output but can still be assigned freely to function buttons.
Multiple actions
One button can trigger several actions. A shunting function may reduce the speed, disable momentum and activate white lights at both ends.
Operating conditions
Depending on the decoder, direction, stationary operation, movement, logical combinations or other active functions may be used as conditions.
Sound mapping
Sound slots are assigned to function buttons and sometimes to driving situations. A sound button, physical AUX output and logical function may all be assigned separately.
Select the trigger
Choose a function button, direction or operating state.
Set the condition
Select forward, reverse, stationary or another logical requirement.
Assign the action
Activate an AUX output, sound slot, shunting mode or decoder function.
Test the result
Check every direction and function combination individually.
| Mapping element | Example | Important check |
|---|---|---|
| Function button | F0, F1, F2 or F20 | Does the command station support the required function button? |
| Physical output | Front light, AUX1 or AUX5 | Is the load actually connected to that output? |
| Logical function | Shunting mode or momentum override | Is another important function being overwritten? |
| Sound slot | Horn, whistle or coupler sound | Does the slot match the loaded sound project? |
| Direction condition | Forward only | Test the function in both directions. |
| Timed function | Coupler sequence or pulse | Do not activate the load for longer than permitted. |
Which mapping strategy suits the required function?
The assistant suggests a sensible structure for common vehicle functions. It does not replace the decoder instructions, but helps separate the button, operating condition and action logically.
Begin with a simple assignment. Add direction, dimming, sound or further operating conditions only after the output switches reliably. This makes it easier to identify which change caused a fault.
Existing mapping rows in factory-digitised vehicles should not be deleted without checking them. They may control internal lighting boards, sound sequences or special switching logic.
Mapping Assistant
Select the function and decoder family.
Use a separate output for each cab, assign an individual function button and add direction and stationary conditions.
Configure function mapping in ten steps
Identify the decoder and firmware
Record the product number, decoder family, interface and firmware version. Mapping tables may differ between decoder generations.
Save the complete project
Save the decoder file using a programmer or read all relevant CVs. It must remain possible to restore the original configuration.
Identify the outputs
Clearly identify the front light, rear light, AUX1 to AUXn, logic-level outputs and vehicle-specific circuit-board connections.
Create the required button list
Create a table containing the button, function, output and operating condition. This reveals duplicate assignments early.
Test a simple basic assignment
Initially connect only one button to one action. Test the output at low brightness or without additional effects.
Add direction conditions
Test forward and reverse separately. Headlights, tail lights and cab lighting frequently require different conditions.
Add logical functions
Add shunting mode, momentum override or sound fading only after the physical output assignment works reliably.
Configure dimming and effects
Configure the brightness, flashing pattern or timed function separately. Do not change the mapping and output effect at the same time.
Test every combination
Test stationary operation, movement, both directions, analogue operation, braking sections and several simultaneously active functions.
Document the completed assignment
Update the locomotive card and digital command station with the function symbols, button assignments and saved decoder project.
Practical mapping examples for locomotives and coaches
| Function | Possible button | Action | Condition |
|---|---|---|---|
| Headlights | F0 | Front or rear lighting output | Direction-dependent |
| Tail lights at cab 1 | F1 | Red AUX output | Relevant end of the vehicle only |
| Tail lights at cab 2 | F2 | Second red AUX output | Independent of the other tail light |
| Shunting mode | F3 | Shunting speed, momentum override and white lights at both ends | Both directions |
| Cab lighting 1 | F5 | Dimmed AUX output | Stationary with cab 1 active |
| Cab lighting 2 | F6 | Second dimmed AUX output | Stationary with cab 2 active |
| High beam | F7 | Second brightness level or separate output | Only with the headlights switched on |
| Digital coupler | F8 | Time-limited AUX output and coupler sequence | Stationary or in shunting mode only |
What should be considered for different gauges?
| Gauge | Typical decoders | Mapping priority |
|---|---|---|
| Z gauge | Nano and micro decoders | Few outputs, minimal dimensions and simple lighting assignments |
| N gauge | Next18, NEM 651 and Fx micro | Control cars, multiple units and compact interior lighting |
| TT gauge | PluX12, Next18 and function decoders | Separate tail lights and vehicle-specific circuit boards |
| H0 gauge | NEM 652, 21MTC, PluX22 and Fx | Numerous lighting arrangements, sound, couplers and shunting functions |
| H0e / H0m | Micro and wired decoders | Compact lighting with restricted installation space |
| Gauge 0 | High-output and large sound decoders | Cab, engine-room, coupler and servo functions |
| Gauges 1 / G | XL and large-scale decoders | Smoke, pantographs, servos, lighting and sound sequences |
Why does a function respond incorrectly or not at all?
The button does not activate a function
Check whether the command station transmits the button, whether a mapping row exists and whether the output works electrically.
The function works only in reverse
A direction condition has probably been set incorrectly. Forward and reverse must be tested separately.
Two functions operate together
Several mapping rows may use the same button, or the vehicle circuit board may connect the loads electrically.
The sound button plays the wrong sound
The button and sound slot may be connected incorrectly, or the loaded sound project may use a different slot assignment.
The cab lighting remains on while moving
A stationary condition may be missing or implemented differently by the decoder family.
Shunting mode does not affect the lighting
Shunting speed and lighting are separate actions. Both must be assigned to the same button or a suitable logical condition.
The mapping disappeared after a reset
The factory reset replaced the saved assignment. Reload the saved decoder project or rebuild the mapping.
Higher function buttons do not respond
The command station, handheld controller or selected protocol may not support the complete function range.
The programmer uses different AUX names
Decoder terminology and vehicle circuit-board labels may differ. Check the pin assignment as well.
Programmers and decoders with flexible function mapping
Compare the number and type of outputs, supported function buttons, interface, digital protocol, installation dimensions and permitted load.
Programming and testing devices
ESU 53451 LokProgrammer
Graphical assignment of buttons, outputs, operating conditions and sound slots.
View product
PIKO 56415 SmartProgrammer
Programming system for SmartDecoder XP functions and sound projects.
View product
Märklin 60971 Decoder Programmer
PC programmer for Märklin mLD3 and mSD3 decoder projects.
View product
Uhlenbrock 71000 DigiTest
Decoder testing, output diagnostics and programming on the workbench.
View product
ZIMO MXULFA
CV programming, updates and sound management for ZIMO decoders.
View productFunction decoders for different gauges
ESU 59210 LokPilot 5 Fx
Multi-protocol function decoder with an eight-pin interface.
View product
ESU 59212 LokPilot 5 Fx
PluX22 function decoder for extensive lighting and auxiliary functions.
View product
ESU 59229 LokPilot 5 Fx DCC
DCC function decoder for control cars and function vehicles.
View product
ESU 59110 LokPilot 5 Fx micro
Compact multi-protocol function decoder for small vehicles.
View product
ESU 59128 LokPilot 5 Fx micro
Next18 function decoder for control cars and compact multiple units.
View product
PIKO 56517 SmartDecoder XP F
Function decoder for complex lighting and coach functions.
View product
PIKO 56518 SmartDecoder XP F
Next18 function decoder with amplified and logic-level outputs.
View product
Uhlenbrock 76800 Function Decoder
Six outputs with dimming, flashing and timed functions.
View product
Uhlenbrock 73700 Mini Function Decoder
Compact decoder with six outputs and mapping up to F44.
View product
Kühn 81820 F062 Function Decoder
Low-profile decoder for direction-dependent lighting and coach functions.
View productLocomotive decoders for H0 gauge
ESU 59610 LokPilot 5
Multi-protocol decoder with extensive function assignment.
View product
ESU 59612 LokPilot 5 DCC
PluX22 locomotive decoder for extensive lighting and special functions.
View product
ESU 59619 LokPilot 5
21MTC multi-protocol decoder for modern vehicle circuit boards.
View product
PIKO 56500 SmartDecoder XP 5.1
PluX22 multi-protocol decoder with advanced functions.
View product
PIKO 56503 SmartDecoder XP 5.1
Eight-pin decoder for DCC, Motorola and mfx-oriented systems.
View product
Uhlenbrock 74125 ID2
NEM 652 locomotive decoder with modern digital and mapping functions.
View productDecoders for TT, N, Z, H0e and H0m
ESU 59818 LokPilot 5 micro
Next18 micro decoder for small locomotives and railcars.
View product
ESU 59816 LokPilot 5 micro
Compact six-pin decoder for N and TT vehicles.
View product
PIKO 46401 SmartDecoder 4.1
PluX12 multi-protocol decoder for suitably prepared TT locomotives.
View product
ZIMO MX618N18
Compact decoder with function outputs and additional logic-level connections.
View product
Lenz 10310-02 Silver mini
Wired decoder for small vehicles and compact digital conversions.
View productDecoders for Gauges 0, 1 and G
ESU 59315 LokPilot 5 L
High-output decoder for large vehicles and numerous auxiliary functions.
View product
ESU 58513 LokSound 5 XL
Large-scale sound decoder for extensive function and sound sequences.
View product
PIKO 36505 SmartDecoder XP 5.1 S
Unprogrammed large-scale sound decoder for individual projects.
View product
PIKO 36540 PSD XP 5.1 S
Large-scale sound decoder for class 199 and V 100 locomotives.
View productRelated guides about function decoders
FAQ about function mapping on model railway decoders
What is function mapping?
Function mapping connects function buttons and operating conditions to physical outputs, sound slots or logical decoder functions.
Which CVs are used for conventional DCC mapping?
Conventional NMRA mapping frequently uses CV 33 to CV 46. The exact meaning depends on the decoder and the supported function range.
What is advanced function mapping?
Advanced mapping provides considerably more function buttons, outputs, operating conditions and multiple assignments than the conventional CV scheme.
Can one button activate several functions?
Yes. A shunting button may, for example, activate shunting speed, the momentum override and white lights at both ends.
Can one output be assigned to several buttons?
Many advanced mapping systems support this. The operating conditions must be selected so that contradictory states do not occur.
How is a sound function reassigned?
The required function button is connected to the appropriate sound slot in the loaded project. Slot numbers differ between sound projects.
Why does a higher function button not work?
The handheld controller, command station, decoder or digital protocol may not support the required function range.
How can cab lighting be switched off automatically?
Add a stationary or speed condition to the output if the decoder supports this logic.
What is the difference between AUX and a sound slot?
AUX normally describes a physical output. A sound slot is an internal audio file or sound function and does not necessarily use an electrical output.
Can mapping be programmed on the main track?
Many DCC decoders support Programming on Main. Complex assignments are normally easier to manage using a manufacturer-specific programmer.
Why did the mapping disappear after a reset?
A factory reset restores the saved default output configuration. Custom assignments must be reloaded from a saved project or programmed again.
How can completed mapping be saved?
Save the decoder project and create a locomotive card listing the function buttons, outputs, operating conditions and decoder product number.
Good mapping makes complex functions easy to operate
Further decoder guides, interface comparisons and buying guides are available in the central model railway guide.