The electronic mail notification service allows controller-based projects to report alarms or events. The automation controller monitors the system and can automatically create an electronic mail message alert with data, alarms, and/or events. Mail recipients can be either local or remote.
-
Based on predefined events or conditions, messages are created using the MSTR function block.
-
The email message is constructed from predefined headers plus variables and text (a maximum of 238 bytes). This message is sent directly from the automation system to the local email server.
-
Mail headers contain common predefined items—recipient list, sender name, and subject. These items can be updated by an authorized administrator.
The Simple Mail Transfer Protocol (SMTP) provides two mechanisms for the transmission of email messages:
-
direct connection
-
relay system
|
Mechanism
|
Condition
|
Result
|
|
Direct connection
|
Sender and receiver are connected to the same transport service.
|
Email messages are sent to host.
|
|
Relay system
|
Sender and receiver are NOT connected to the same transport service.
|
Email messages are relayed from one server to another server.
To relay messages, the SMTP server must be supplied with the address of the:
-
destination host
-
destination mailbox
|
The Quantum Ethernet module includes an SMTP client. When the module receives a specific request from the project, it sends an email message to the mail server.
Operating Modes and Sending Requests
Because the project sends the email request, a controller cannot send an email message either while in the stopped mode or while downloading a project. As soon as the controller is in RUN mode, the function block sends a request during the first project scan.
Diagnostic counters are reset to 0 after either a power-up, a project download, or a reconfiguration of the mail service.
