Scope: what the EA9 evidence supports
Use the C-more EA9 as an operator interface first: interact with the PLC, then let the PLC or dedicated devices handle jobs outside core HMI scope. In the evidence, an EA9-T12CL is paired with a P2000 and a P2-8AD4DA-2 multichannel AD/DA card; the same environment is described as supporting PID control loops. Satisfaction is generally high for ease of screen building and point-and-drop tag work, but three constraints drive selection: XY pair plotting, historical data handling, and carrier-dependent SMS/email delivery.
| Need | Evidence-backed status | Design action |
|---|---|---|
| Non-time X/Y pairs | An EA9-T12CL user could not find an Excel-like X/Y plot for unevenly spaced, non-time pairs such as vertical-LVDT vs horizontal-LVDT, load cell vs LVDT, or GPS latitude vs longitude. | Do not assume scatter plotting exists. Prove it in the exact EA9 software revision before committing; otherwise buffer pairs in the P2000 and use a plotting path that explicitly supports X/Y pairs. |
| History navigation | Trend objects are called archaic; moving to previous days is a chore; a DatePicker is requested. | Keep short operational trends on the HMI; put long-term review where date selection and export are native. |
| SD card retention | No FIFO overwrite is confirmed; old SD data may require manual wiping. | Design retention outside the panel or verify current EA9 firmware/software adds rotation before relying on unattended logging. |
| SMS/email to AT&T | C-more uses Unicode in Subject and Message Body for international languages; AT&T is described as expecting ASCII in the subject and handling Unicode poorly. | Leave the subject blank so the first body line becomes the subject in most cases; verify through AuthSMTP with a mail client and the target handset. |
Decision path for X/Y pair display
The risk is architectural: multichannel acquisition and PID imply engineering data relationships, while the reported EA9 trend path is time-oriented. If the required view is channel-versus-channel rather than channel-versus-time, treat it as a hard requirement, not a nice-to-have. Examples from the field case are LVDT vertical versus horizontal position and GPS longitude versus latitude for a mobile plot.
- Write the requirement as pairs: sample ID, X value, Y value, units, range, and whether X is monotonic. If X is latitude/longitude, state map scaling separately from raw pair plotting.
- In the EA9 project, test whether the available object accepts two arbitrary tags for X and Y and does not force time on an axis. If it cannot, stop and do not emulate scatter with trends.
- Move acquisition and pair formation to the P2000: scale channels, time-stamp or sequence samples, and keep a bounded pair buffer so the HMI only displays what the controller has validated.
- Select the display layer by proof: EA9 native object only if the demo passes; otherwise use a purpose-built plotting device/software for review while keeping field control independent of Windows interruptions if that separation is a project requirement.
Logging, alarms, recipes: keep the boundary explicit
The satisfied-use pattern is clear: the HMI interacts with the PLC; datalogging, true web hosting, recipe database behavior, and alarm database behavior are not automatically expected from the panel. The counterpoint is also clear: datalogging, recipes, and alarms are HMI-suited functions, and the EA9 is described as close to reducing SCADA scope if date navigation and SD FIFO overwrite existed. Until those are proven in your version, partition functions: real-time operator actions and current trends on EA9; durable history, fleet exports, and database behavior on PLC storage, external storage, or SCADA.
Email-to-text failure isolation
For the AT&T text case, isolate by layer before changing the panel program. C-more sends Unicode in Subject and Message Body; AuthSMTP is not identified as the failure point; the suspected break is when the message reaches AT&T, which expects ASCII in the subject. Leave the subject blank so, in most cases, the first line of the email becomes the subject. Verify by connecting a mail client to the AuthSMTP server to confirm the C-more message is intact, then test the same message to the AT&T destination and one non-AT&T destination if available.
Physical and runtime fit checks
Account for the EA9 bezel: the area outside the active screen is described as large, so the cutout and enclosure can be bigger than the nominal screen suggests. Confirm the panel cutout from the exact EA9-T12CL mechanical drawing before fabrication. Preserve the stated runtime goal: office development in Windows is acceptable, but field control should remain substantially separate from Windows interruptions. Before acceptance, run a bench proof for the four failure modes above: required plot type, previous-day trend recall, SD card full behavior, and Unicode/ASCII SMS delivery.
FAQ
Can an EA9-T12CL plot latitude versus longitude directly?
The evidence reports no found path for non-time, unevenly spaced X/Y pairs on an EA9-T12CL with a P2000. Prove a two-tag X/Y object in your exact software revision; otherwise form pairs in the P2000 and use a display layer that natively supports scatter plots.
Why does C-more email fail only as an AT&T text?
The evidence points to Unicode in the C-more Subject and Message Body while AT&T expects ASCII in the subject. Leave the subject blank so the first body line often becomes the subject, then verify through AuthSMTP and the target handset.
How do I stop EA9 SD logs from needing manual wipes?
No FIFO overwrite is confirmed in the evidence, so do not design for unattended indefinite logging unless your current EA9 version proves rotation. Use bounded PLC-side retention or external storage and test card-full behavior during acceptance.