The Event Manager belongs to the full C-more touch-panel family. Software version 3.22.0.0 is the C-more Micro line, so the menu you are hunting for does not exist in it. Use Alarm Control Setup for alarms on the Micro, and treat any need for email, pop-ups or logging as a panel-family change.
You are looking for a menu that does not exist in your software. A project reporting version 3.22.0.0 is on the C-more Micro software line, and the Micro family ships without the Event Manager. That feature belongs to the full C-more touch panels, so no menu search, software update or project setting will surface it. The closest Micro feature is Alarm Control Setup, which covers alarm handling on the panel only. This article gives the checks that confirm the family split, then the fix for each outcome.
Why the menu is missing
The Event Manager is documented for the full C-more touch panels, where it ties events, alarms among them, to actions: send an email, show a pop-up notification, write to a log, change screen, follow a schedule, and choose the power-up screen. The Micro panels are the small end of the line, and they run their own software with its own version history. Version 3.22.0.0 is a Micro version; the full-family configuration software reached version 6.0 with more alarm and recipe features. The feature follows the panel family, so reading full-panel documentation against a Micro project sends you hunting for a menu the Micro software never had.
What each symptom points to
- The Event Manager command appears nowhere in the menus. The project targets the Micro family. The version number 3.22.0.0 identifies the Micro software.
- The pages that mention the Event Manager list email, pop-ups and logging. Those pages describe the full touch panels. They are correct for that family and describe a different product line.
- You found Alarm Control Setup and took it for a renamed Event Manager. It is the Micro alarm feature. It presents alarms on the panel; it sends no email, raises no pop-up notification and writes no log.
- An example project shows event actions yours will not show. The example targets a full panel. Your Micro project has no such actions to configure.
- The panel runs fine otherwise. Nothing is broken. The family split costs you features, and the panel keeps doing the job it was built for.
Checks that settle it
- Open Panel Manager, the screen where you set the PLC type, and read the panel model the project targets. A Micro model confirms the split in one look.
- Read the version your software reports. 3.22.0.0 is a Micro version, and the full-family tool is a separate program.
- Open the page that sent you looking for the Event Manager and check which panel series it names. Full touch panels only.
The fix when alarms are all the Micro has to do
If the job needs the operator to see and clear alarms at the panel, Alarm Control Setup is the whole fix. Define the alarm conditions the panel watches and how they present, then test one alarm end to end before configuring the rest: trip the condition, confirm the indication appears, clear the condition, confirm it goes away.
If email is the single missing action and the panel must stay, move that one action to the controller. PLC email alerts from a Boolean event covers driving the message from the PLC side. The Micro keeps the local alarm display, and the technician still gets the message.
The fix when the job needs event actions
Write down the actions the job actually needs, then check them against what each family offers:
| Action the job needs | Micro family | Full touch-panel family |
|---|---|---|
| Alarm shown on the panel | Alarm Control Setup | Event Manager |
| Email on an event | Not offered | Event Manager action |
| Pop-up notification | Not offered | Event Manager action |
| Logging to a file | Not offered | Event Manager action |
| Change screen on a condition | Not offered | Event Manager action |
Any row that reads "not offered" and sits on your list is the decision: the project has to move to a full-family panel. Record the actions, confirm the candidate panel documents the Event Manager with those exact actions, and plan the work as a project rebuild until a documented conversion path shows otherwise. Two examples of what the move buys you: an event manager action that saves a screenshot to USB, and an alarm shown as a pop-up message box.
When you pick the replacement panel, plan its alarm text for the floor; the worked example below sizes the letters. Keep the product categories straight while you buy, because a signage screen is not an HMI: shop-floor signage plays its own shows from a memory card or USB stick, so it is a notice board for the area, not a stand-in for the panel that watches the machine.
Example: a filler line at 8 ft that wants email and a pop-up
Inputs:
- The project reports version 3.22.0.0, from the case that raised the question, so the panel is a Micro panel.
- Maintenance wants two event actions when a filler fault bit turns on: an email to the technician and a pop-up on the panel. Both are Event Manager actions on the full family.
- The operator stands about 8 ft from the panel during a run.
Rule: count the wanted actions the current family can host, and size the pop-up text from the viewing distance.
Actions: the Micro hosts zero of the two. 2 wanted minus 0 hosted leaves 2 uncovered.
Text size: the FHWA planning figure is 30 ft of viewing distance per inch of letter height, and 20 ft per inch is the safer choice for fast reading, which an alarm pop-up is. At 20 ft per inch, the pop-up needs 8 ft divided by 20 ft per inch, which is 0.4 in capitals. Line spacing is 1.7 times the capital height, so 1.7 x 0.4 in = 0.68 in, and two message lines need 2 x 0.68 in = 1.36 in of height before any frame or buttons.
Decision: 2 uncovered actions clears a threshold of zero, so plan the panel change now. Until the full panel is in, the controller can send the email, which closes one of the two gaps, and Alarm Control Setup keeps the fault visible at the machine.
The decision
Recommendation: keep the Micro panel and configure Alarm Control Setup when alarm display at the machine is all the job needs, and move the email duty to the PLC if email is the one missing piece. The moment your list includes a pop-up notification, logging or a screen change on a condition, stop searching the Micro software and plan the move to a full-family touch panel; the family change is the only fix for those actions.
Questions
Is the Event Manager hidden somewhere in C-more Micro software 3.22.0.0?
No. A project reporting version 3.22.0.0 is on the Micro software line, and the Event Manager is a feature of the full C-more touch panels. There is no menu, tab or setting that reveals it, because the Micro family ships without it. The closest Micro feature is Alarm Control Setup, which handles alarm presentation without the email, pop-up or logging actions.
Can I keep the Micro panel and still get email alerts?
Yes, from the controller side. Keep Alarm Control Setup for the alarm the operator sees on the panel, and let the PLC send the email when the fault bit turns on, if your controller supports email. That closes one gap. The panel still raises no pop-up or log entry through an event system, so write down what stays uncovered before you accept the arrangement.
How do I confirm which panel family my project targets?
Open Panel Manager, the same screen where the PLC type is set, and read the panel model the project is built for. The reported software version also separates the lines: 3.22.0.0 is a Micro version, while the full-family configuration software has continued past version 6.0. If the page that sent you searching names the full touch panels, it describes that family, not your project.
How large should the alarm pop-up text be on the replacement panel?
Size it from the viewing distance. The FHWA planning figure is 30 ft per inch of letter height, and 20 ft per inch is the safer choice for text an operator must read fast. At 8 ft that gives 0.4 in capitals with line spacing of 1.7 times the capital height, about 0.68 in. Measure the farthest operator position you need to cover, then round up.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.