Why does a single ◄ press open the System Menu?
On this Matrix controller, pressing ◄ alone opened the System Menu from any screen. The behavior was the same with or without a project loaded. The ► key navigated normally, and a factory reset changed nothing. Formatting the controller from SMLogix cleared the fault. The documented entry is ◄ and ► pressed together at any time while the controller is running, so a single-key trigger means the combination check is returning true when it should not.
The keypress travels through these stages:
- The key contact closes.
- The keypad scan detects it.
- The system firmware reads the key state.
- The combination decoder evaluates the key state.
- The menu dispatcher acts on the result.
The System Menu handler belongs to the system firmware, not the application. It evaluates the key combination before the project sees the key. That is why loading or removing a project has no effect. For ◄ alone to satisfy a two-key condition, one of two things is true:
- Physical/scan layer: the decoder sees ► asserted at the same moment as ◄.
- Storage layer: the condition is evaluated against damaged stored data.
Test the physical layer first, then the storage layer.
Check before moving on: remove the project or run the controller empty and confirm the fault is still present. If it is, the application program is not the cause.
Is the ► contact actually releasing?
A ► contact held closed makes the scan report ► as permanently pressed. Every ◄ press then completes the combination. Possible causes include bezel pressure on the membrane, contamination, or moisture. Rule this out before touching firmware or storage.
| Observation | Points to |
|---|---|
| Display advances or scrolls right with no key touched | ► contact stuck closed |
| One ► press moves exactly one step, with no auto-repeat | ► contact releases correctly |
| Fault disappears when panel fixings are loosened or the unit is removed from the cutout | Mechanical pressure on the keypad |
| Fault identical after power cycle, factory reset, and with or without a project | Stored system data, not the keypad |
| Other single keys also trigger system functions | Wider keypad or scan fault |
Here ► worked normally, and the later fix by formatting confirms the keypad hardware was sound.
Check before moving on:
- Power up and watch the display for several seconds without touching any key. Nothing should move.
- Press ► once. The cursor or screen should advance exactly one step.
- On a panel-mounted unit, relieve the bezel pressure and repeat the ◄ test. If the fault stays, go to storage.
Why doesn't a factory reset clear the fault?
A factory reset is a routine inside the controller's own firmware. It writes default values back into the settings area. It runs on top of the existing storage structure and does not rebuild it. If the damage sits in the storage structure itself, the reset leaves it in place. The damage could be in system configuration data or in a remnant of an earlier project. A format issued from SMLogix erases the controller storage and recreates it from the PC side.
| Operation | Initiated from | Scope | Result on this unit |
|---|---|---|---|
| Factory reset | Controller system firmware | Restores default settings over existing storage | Fault persisted |
| Format | SMLogix over the programming link | Erases and rebuilds controller storage, removing the loaded project | Fault cleared |
Check before moving on: confirm the fault survived a completed factory reset followed by a power cycle. That result tells you to format.
How do you format the Matrix from SMLogix?
The format request travels from the PC running SMLogix, over the programming link, to the controller system firmware, which then writes to storage. Prove the physical link first, then communication, then run the format. A format interrupted by a cable pull or power loss leaves the storage empty and the controller without a program.
- Back up. Save the current project source in SMLogix. Record every setpoint and parameter adjusted from the front panel, because the format erases the controller storage, including the loaded project.
- Connect the physical link. Use the programming interface configured on your unit. Seat the cable at both ends and use a known-good cable.
- Prove communication. Go online in SMLogix and confirm it identifies and reads the controller. Do not continue while the connection drops or retries.
- Run the format. Start the SMLogix format function on the connected controller. Keep power and the link undisturbed until SMLogix reports completion.
- Power cycle the controller.
- Test the keypad before loading the project (next section). This isolates the fix from anything the project brings back.
- Download the project and restore the recorded parameters.
Check before moving on: SMLogix reports that the format completed, and the controller boots to its empty state without errors.
Does the System Menu now open only on ◄+►?
Verify twice: first on the empty controller, then with the project loaded. If the fault returns only after the download, the project transfer is carrying the problem back. In that case, format again, recompile the project in SMLogix, and download the fresh build instead of reusing the old transfer.
- With the controller empty, press ◄ alone from every screen you can reach. The System Menu must not appear.
- Press ► alone. It must move one step with no repeat.
- Press ◄ and ► together. The System Menu must open. Exit it.
- Download the project and restore parameters. Repeat steps 1–3 at every application menu level, since the original fault appeared from any menu.
- Power cycle the controller. Repeat step 1 and step 3 to confirm the corrected behavior persists in storage across a restart.
FAQ
Why does my Matrix controller open the System Menu when I press only the left arrow?
The System Menu decoder is seeing its ◄+► condition as true on ◄ alone. Either the ► contact is held closed, or the stored system data is damaged. If ► navigates normally and the fault survives a factory reset, format the controller from SMLogix.
Why does a factory reset not fix the Matrix System Menu problem?
A factory reset restores default settings on top of the existing storage structure, so damage in that structure survives. A format issued from SMLogix erases and rebuilds the storage, and that cleared the fault on this unit.
Why does the fault appear even with no project loaded on the Matrix?
The System Menu key combination is handled by the system firmware before any application code sees the keypress. A fault that is identical with and without a project points to the keypad or stored system data, not to your program.
Does formatting a Matrix controller in SMLogix erase the project?
Yes. Formatting clears the controller storage, including the loaded project. Save the project source and record any panel-adjusted parameters first, then download and restore them after the format and keypad test.
Why does the right arrow work normally if the key combination is misfiring?
A normally working ► key with one step per press and no auto-repeat shows its contact is releasing. That rules out a stuck ► as the cause and moves the diagnosis to stored system data, which is why a format fixes it.