Locate the Mode Command in the Keypad Macro
On the Pixel 2511, start with the keypad macro that processes operator keys. The evidence identifies the F5 action as the existing remote/local mode command, even though this controller has no physical F5 key. Treat F5 as a logical action to reproduce, not as a terminal that can be wired directly.
Do not assume that assigning key:F5 to a DIN in the system menu is sufficient. That mapping was proposed but not confirmed. Inspect the macro to determine how the F5 event changes the operating mode and whether a DIN event can invoke the same path.
Separate the Command from the Indication
| Function | Required signal | Implementation decision |
|---|---|---|
| Change remote/local mode | Momentary command | Make the DIN-operated pushbutton reproduce the logical F5 action handled by the keypad macro. |
| Show the active mode | Current mode state | Drive the lamp from the stored remote/local state, not from the momentary pushbutton contact. |
A non-latching pushbutton generates only a command pulse. Its contact cannot provide persistent indication after release. An illuminated pushbutton can show the current mode only when its lamp is controlled separately by the state maintained in the controller logic.
Configure the External Pushbutton
- Open the Pixel 2511 keypad macro and locate the logic executed by the F5 action.
- Identify the state or logic that the F5 event toggles between remote and local control.
- Configure the selected DIN so its momentary event follows that same command path. If using the system-menu
key:F5assignment, confirm that the keypad macro receives and processes it identically to the original key action. - Connect the illuminated button's lamp to an available indication path driven by the resulting mode state. The evidence does not identify a specific output, address, or polarity, so select these from the actual controller configuration and wiring.
Verify the Result
With the equipment in a safe test condition, press and release the external button once. Confirm that the operating mode changes once and remains selected after the button is released. Press it again and confirm that the mode returns. Then verify that the lamp follows the actual remote/local state rather than lighting only while the button is held.
If the DIN changes state but the mode does not, trace whether the configured input generates the logical F5 event and whether the keypad macro receives that event. If the mode changes more than once per press, inspect the event handling for repeated processing; no debounce timing is provided in the evidence, so determine any required correction from observed input and macro behavior.
FAQ
Can a Pixel 2511 DIN be assigned to key:F5 for remote/local selection?
It is a candidate configuration, but the evidence does not confirm that the assignment alone works. Verify that the DIN-generated key:F5 event reaches the keypad macro and invokes the same mode-change logic.
Does the remote/local selector need a maintained switch?
No maintained contact is required if the keypad macro already toggles a stored mode from the momentary F5 command. Confirm that one press produces exactly one mode change.
How can a momentary illuminated button show the selected mode?
Control the lamp from the controller's current remote/local state, independently of the momentary contact. Wiring the lamp only to the button signal would indicate a press, not the retained operating mode.