Troubleshooting
Working around the C-More EA9 alarm banner covering buttons
Short answer
No. The C-More EA9 alarm message banner has no position setting: it is fixed at the bottom of the screen, and while an alarm is active it overlays every screen in the project. Reduce the banner height, move page-change buttons above the banner band on every screen, and verify each one with a live alarm showing.
On this page
No — the C-More EA9 alarm message banner cannot be moved to the top of the screen. AutomationDirect's FAQ on exactly this question states the banner position cannot be changed: the banner resides at the bottom, and it is an overlay that appears on every screen in the project while an alarm is active, not only the screen where the alarm was configured. Any page-change button in the bottom band of any screen is therefore covered during every active alarm. The fix that works today is layout, not configuration: shrink the banner, move the navigation buttons above the banner band on every screen, and prove each button with a live alarm on the panel.
The documented behavior you are working against #
- Position is fixed. The vendor FAQ answer is direct: the alarm message banner position cannot be changed, and the banner resides at the bottom of the screen. No documented EA9 setting, menu or parameter moves it.
- The banner is project-wide. It is not an object you placed on one screen; it belongs to the alarm system and displays on any screen while an alarm is active. Clearing the bottom band on the screen that drew the complaint is not enough — the band exists on all of them.
- Size is the one adjustment. The banner height is adjustable, and shrinking it is the standard interim move; the field case shows its ceiling — the page-change button stayed half covered.
Why a smaller banner is only first aid #
Reducing the banner height cuts the overlap but leaves the fault in place. In the reported case, production complained that the banner covered the page-change buttons; after the banner was made smaller, half the button was still under it. Half a touch target is not a working button — an operator reacting to an alarm presses fast, and presses land where the banner is. Treat shrinking as step one of the fix, never the whole fix: the standard is zero overlap between the banner band and anything the operator must press.
Build the keep-out band and move the buttons #
- In the alarm configuration, reduce the banner height to the smallest value that stays readable at arm's length under the plant's lighting.
- Turn that height into a keep-out band: on every screen, nothing the operator must press may sit inside the band, and leave a small gap above it.
- Move each page-change, alarm-acknowledge and alarm-history button so its bottom edge clears the band with that gap.
- When the moved rows collide with the objects above them, do not push the buttons back down; recover the height by sizing HMI touch buttons in a dense button matrix instead of shrinking hit areas.
On capacitive panels the move pays twice: targets jammed against the bottom bezel are a known source of missed presses on their own, the pattern explained in why capacitive touch buttons miss presses near screen edges.
Worked example: the keep-out band in pixels #
Illustrative numbers, not an EA9 specification — read your own banner height out of the alarm configuration and redo the arithmetic with it.
Take an 800 × 480 project, a banner reduced to 40 px, and a row of 40 px page-change buttons whose bottom edge sits at y = 460.
- Band: 480 − 40 = 440, so the banner occupies y = 440 to 480.
- Overlap: the buttons span y = 420 to 460, so 460 − 440 = 20 px of each button is covered — 20 / 40 = 50%, exactly the half-covered state the field workaround ended at.
- Target: put the bottom edge at 440 − 12 = 428, a 12 px gap above the band; the row then spans y = 388 to 428.
- Move: the whole row shifts 460 − 428 = 32 px up, and nothing above y = 440 is banner territory.
Decision from the numbers: with a 40 px banner on an 800 × 480 project, any object whose bottom edge is below y = 440 moves up until it sits at y = 428 or higher, on every screen.
Getting messages at the top of the screen #
The banner is the wrong tool for that requirement — it has exactly one position. Put an alarm list object at the top of the screen instead: you place it, size it, and feed it from the alarm configuration you already have. On the CM5 series the vendor's guidance states the pattern outright — stop displaying the banner and use an alarm list object — and the EA9 programs the same alarm objects, so the decision does not depend on the series. Top-of-screen messages come from your own alarm list, and the fixed banner becomes harmless once nothing pressable sits in its band. If the only requirement is buttons that stay usable during alarms, keep the banner and move the buttons: that is the smaller change.
Verify with a live alarm on every screen #
- Force or simulate one alarm and leave it active while you walk through every screen in the project.
- On each screen, press every page-change button with the banner showing; a pass is a first-press navigation, every time.
- Include the screens an operator needs during a fault — alarm acknowledgement, alarm history, the machine screen — not only the main menu.
- A button that still fails with no banner on screen has a different fault; one documented pattern is Goto Display buttons locked out by HMI global connections.
Treat any navigation that only works when no alarm is active as a design fault: alarm conditions are exactly when the operator must change screens.
Decision by case #
| Case | Decision |
|---|---|
| Banner covers part of a page-change button | Move the button above the band; shrinking alone already failed in the field |
| Production wants messages at the top | Alarm list object at the top; the banner stays at the bottom |
| Multi-screen project | Same keep-out band on every screen; the banner overlays all of them |
| Moved buttons crowd the rows above | Resize the targets; never push them back into the band |
Questions asked
Does the same bottom-only banner limit apply to the C-More CM5 series?
Yes. A 2025 vendor community answer for the CM5 gives the same result: there is no way to move the alarm banner from the bottom, and the suggested pattern is to stop displaying it and use an alarm list object instead. Treat the fixed bottom position as a series-wide design, and spend the effort on layout.
Is a button that is only half covered by the banner still usable?
No. Coverage does not scale into usability: a press aimed at the visible half still clips the banner edge, and an operator reacting to a fault presses fast. The field case kept the production complaint at exactly half coverage. Treat any part of a navigation target inside the banner band as a defect and move the button.
Can the banner be hidden on individual screens where it is in the way?
No per-screen hide is documented for the EA9 banner. The documented behaviors are a fixed bottom position and display on every screen while alarms are active. The workable alternative is global rather than per-screen: give the message job to an alarm list object you place yourself, and keep every pressable object out of the bottom band.
Where do I ask for a top-position banner option?
Through the vendor's support and community channels. The original relocation request was forwarded to the C-more Product Manager in the vendor's own answer to this question, which is where the fixed-position FAQ also lives. File the request and check release notes when you upgrade, but design today's layout for the banner you have.