Signal Monitoring and Alerts
Overview
Alerts let you check when signal conditions become active and recover. You can configure multiple conditions per signal. Distinguish the Monitor setting for the value list, the setting that enables alerts, and triggers that start/stop log saving.
| Purpose | Settings / screen to use |
|---|---|
| Check the latest value | Values / Monitor in Display Settings |
| Check activation/recovery of value conditions | Alert in Signal Setting, Alert History |
| Use a condition to start/stop log recording | Start/Stop Signal Trigger in Trigger Window |
| Find occurrences in a saved log | Signal Analysis in Analyze Window |
Configuring Alert Conditions
- Stop monitoring and open Edit for the target signal in Signal Catalog.
- Select the Alert tab. For a derived signal, also use Alert in its editing screen.
- Add a condition with + Add and set its name.
- To also use a condition that supports real-time monitoring while monitoring, select “Monitor + Analysis” as its use. “Analysis only” applies to analysis of recorded logs. State transition is analysis-only.
- Turn on “Enable this condition.”
- Select the required condition from the options available for the signal type.
- Configure the supported thresholds, recovery conditions, notification delay, and notification sound if needed. State transition has no duration or recovery conditions.
- Check the condition summary and enabled state, then confirm with OK.
- For Monitor + Analysis conditions, start monitoring with the intended Set and check Values and Alert History. For analysis-only conditions, analyze a log in Signal Analysis and check the results.
Alert Tab Reference
Figure 1 shows condition CH1 RPM High monitoring Simulated_RPM_demo in FanDemo. Its use is Monitor + Analysis and the condition is on. Upper limit under Range limits is 2200 rpm, Recovery margin is 100 rpm, and Notify is Immediately.
Figure 1. Upper-limit condition for actual rotational speed.
| Item | Description |
|---|---|
| Condition list / Alert conditions | Check registered conditions and the enabled count. Select a condition to edit. |
| Condition name | Set a name to distinguish multiple conditions. |
| Monitor + Analysis / Analysis only | Specify whether the condition is used in real-time monitoring as well, or only in analysis. |
| Enable this condition | Enable or disable the selected condition. |
| Range limits | Use lower/upper-limit conditions. Enable the required side. The upper-limit condition becomes true at or above the configured value. |
| Equals / Does not equal | Test whether values match or differ. |
| Is one of / Is none of | Test whether a value matches any specified state or none of them. |
| Text matches / Text does not match | Test whether strings match or differ. |
| Invalid BCD | Detect values invalid as BCD. |
| State transition | An analysis-only event detecting the instant of a state transition. Not used for monitoring notifications; no duration or recovery conditions are configured. |
| No reception | Test whether the target signal has not been received for the specified time. |
| Condition details | Check the target value, comparison method, and condition summary. |
| Recovery margin | A margin to prevent repeated activation/recovery near a threshold. |
| Notify | Specify Immediately or After duration. |
| Sound / Preview | Configure a notification sound and check it with Preview. |
| + Add / Delete / Undo | Add/delete conditions or undo edits. |
Available conditions and fields depend on the signal type. Do not confuse numeric physical values, Logical states, and strings; check the comparison target in Condition details. For derived signals, the item that checks for missing input updates is shown as No result update.
Upper-Limit Example
The condition in Figure 1 becomes true when actual rotational speed reaches 2200 rpm or higher. With Recovery margin set to 100 rpm, recovery occurs when the value falls below 2100 rpm. Notify is Immediately, so activation is reported immediately.
For After duration, set how long the condition must remain true before notification. Choose according to whether you need to detect momentary changes or only abnormalities lasting a specified time.
Alert History Reference
Click Alert History at the upper right of Signal Window.
Figure 2 shows history from actual monitoring with the condition in Figure 1 enabled. Timestamp and Start Value record activation; Recovery Time and Recovery Value record recovery.
Figure 2. Alert History recording activation and recovery.
State in Figure 2 is Recovered. Condition CH1 RPM High for Simulated_RPM_demo became active at +000:00:01.264.351 with 2200 rpm, and recovered at +000:00:31.480.286 with 2092 rpm.
| Item | Description |
|---|---|
| State | Check the alert activation/recovery state. |
| Signal / Rule | Check the target signal and condition. |
| Timestamp / Start Value | Check activation time and the value at that time. |
| Recovery Time / Recovery Value | Check recovery time and the value at that time. Scroll horizontally to see later columns. |
| Signal Type / Rule Type / Condition | Check signal/condition types and the evaluation condition. Figure 2 shows Native, Monitoring, and >= 2200. |
| Export CSV | Export history to CSV. This has a different purpose from signal analysis CSV files and communication logs. |
| Open in Signal Analysis | Examine the selected history in Signal Analysis when available. |
| Clear | Clear recovered history entries. Active alerts remain. |
| Close | Close the history screen. |
Stop monitoring and select the same history row to enable Open in Signal Analysis as shown in Figure 3.
Figure 3. Controls for opening selected history in Signal Analysis.
To examine a history occurrence in analysis, stop monitoring and analysis, then double-click the history row or select it and click “Open in Signal Analysis.” Data at the activation time must still be in the target channel's monitoring buffer. For derived signals, channels required for inputs are included too.
For checking detection rows, waveforms, and Values after opening, see Checking Alert Occurrences.
Alerts Versus Signal Trigger
Enabling an alert alone does not make it a condition for starting or stopping log recording. To control log saving using a signal condition, configure the target signal, threshold, comparison direction, and other settings in Start Signal Trigger/Stop Signal Trigger in Trigger Window. Also check the trigger mode and Save Log File.
Restrictions apply to signals selectable for Signal Trigger; derived signals cannot be selected. Check availability and the reason shown in the selection screen. Also see the existing trigger features.
Saving and Reusing Conditions
After editing conditions, use Save in the Catalog to save them to MPXSIG. To retain history, use Export CSV in Alert History. Saving conditions and saving recorded history are separate operations.
For saved-log analysis, result output, and use in transmission settings, see the respective instructions.