Common Message Types From All Agents

Each agent sends data in the form of messages. As discussed in Working with Itron-Developed Agents, the message content and destination vary by the agent. There are several message types, however, that are common among all agents.

These common messages typically send information indicating that configuration changes occurred within an agent. Unlike other messages, these configuration change messages aren't sent to an app and aren't made known to customers through a user interface.

Rather, these messages are internal only, sent to the CMS where CMS maintains the source of truth for each agent's current configuration. The messages can help confirm if and when a configuration upgrade (or discrepancy) occurred, or if any upgrades failed. As a utility customer, you won't have access to CMS or these messages. However, if Itron personnel should help install or troubleshoot your DI system, they may access the common messages in CMS for assistance with their efforts.

The following table describes the messaging details of common messages that any agent may send.

For information about the unique messages each agent may send, see Itron-Developed Agents.

Message	Size	Frequency	Content
Agent Log Message	150 bytes	Error logs once per day, per service point	event/alarm level, message, message ID. Error logs event not alarm. 150 to HES Debug logs event not alarm
Agent Start-up Report	108 bytes	Only at agent start up	Contains the agent version, meter firmware version, AppServ version, a list of the agent's enabled feature IDs, a list of the agent's disabled feature IDs, the agent's declared CPU, flash, and memory usages (from the policy file), and longitude.
Diagnostic Configuration Message	199 bytes	On-demand, only when the command is sent
Agent-Specific Diagnostic Message	Depends on the command	On-demand, only when the command is sent
Configuration Notification With Feature ID	48 bytes	Each service point sends one message a day	Each message contains the Feature ID of the feature that experienced a configuration change, the new configuration ID, the new feature version, the old configuration ID, the old feature version, length, and status.
Configuration Notification	75 bytes		Each message contains the Feature ID of the feature that experienced a configuration change, the new configuration ID, the new feature version, the old configuration ID, the old feature version, length, and status.
Configuration Notification V2	42 bytes	Each service point sends one message a day	Each message contains the Feature ID of the feature that experienced a configuration change, the new configuration ID, the new feature version, the old configuration ID, the old feature version, length, and status.