Displays the number of seconds until the current interval ends.

The current time on device's internal clock (local time).

The length of time this device has been continuously powered up.

Indicates the meter's connection status with the Gen5 network:

• No Radio. Status not available. This can be caused by:
  • The device has restarted and displays this status briefly while the it reboots.
  • The network firmware on this device is not properly configured and the device is in failure state.
• Radio Off. Network access disabled.
  The device is in "Opt Out" status: the meter's 900Mhz radio transmission is disabled.
• No Neighbors. Initialized.
  The device's network stack is running and has begun the neighbor discovery activity.
• Have Neighbors. Network found.
  The device has found a peer neighbor that is connected and can act as a relay.
• Network Registered. Connected.
  The device can successfully communicate on the network.

The status of the Home Area Network

• Disabled. The meter is not connected to the homeowner's Wi-Fi Access Point.
• Joining. The meter is attempting to connect to the homeowner's Wi-Fi Access Point.
• Joined. The meter is connected to the homeowner's Wi-Fi Access Point.
• No Network. If the homeowner verifies that their Wi-Fi is working correctly, this status can occur if the Wi-Fi router is too far away. Ask the homeowner to move the router closer to meter.
• Join General Failure. The meter tried and failed to connect to the homeowner's Wi-Fi Access Point. This could be the result of any of the following problems:
  • The user entered the wrong SSID and/or password for the Wi-Fi router. Verify the SSID and password and retry.
  • The Wi-Fi router is still too far from the meter to establish a reliable connection. Move the Wi-Fi router closer to the meter or add a Wi-Fi range extender.
  • The Wi-Fi router might be more than 10 years old. Replace the Wi-Fi router with a newer router.
  • The Wi-Fi router may have IGMP proxying turned off. It should be turned on and have the Wi-Fi router restarted. This should allow the meter and Wi-Fi router to start communicating.

Displays the line frequency at the moment this page was opened.

The total length of time the device has relied on its battery for power (rather than the service line). Shown in days, hours, and minutes.

The total number of times this device has experienced a power outage.

Gives an indication of the remaining life of the battery.

If the device is unregistered, the device will attempt to register in this length of time. Shown in hours, minutes, and seconds.

A time span during which the device randomly generates a countdown timer until it tries to register again. This is to reduce network traffic.

Tamper Count fields. Meter tampering can be an attempt to invoke malicious communications or steal electricity from the utility company by interfering with the correct functioning of the meter.

Gen5 Riva meters have multiple ways of detecting meter tampering. The following fields display the number of times that the meter has detected individual type of tampers.

To clear these counts, see the Tamper options under Device Management > Device Operations.

The meter's accelerometer detects motion. A motion flag is set that allows the meter to determine upon power up whether motion was detected just before losing power. If power is not lost after motion is detected, the meter waits 10 seconds, then resets the motion flag and the removal event is not logged.

The meter's accelerometer detects the potential attempt to roll back energy accumulation by installing the meter in the upside-down position.

When 40 Wh or more are detected in the reverse direction, this tamper is counted.

The number of times the secure login process has failed.

The processor on the Hall effect sensor detects that the magnetic field is atypical. This is an attempt to induce offsets that impact meter accuracy.

The terminal block cover switch detects when the cover is removed. The switch has a processor with battery backup that makes note of the removal even if the meter is powered down.

Arc Detection Count fields. These six fields allow you to monitor arc conditions. This provides users with early awareness so that corrective actions can be taken.

Note that if the meter is not configured to detect arcing, the fields display zeros.

For more information, refer to the Gen5 Riva Singlephase Electricity Meter Technical Reference Guide, "Detecting Arcing."

The number of arcs detected. This count accumulates over the life of the meter.

Note: The meter can only detect one arc per second.

The number of blocks (60 seconds, configurable) where the number of detected arcs is at or above the threshold (20, configurable). This count accumulates over the life of the meter.

The number of times the arc detection algorithm has triggered due to the number of arcs detected in a block exceeding the configured arc detect block threshold. This count is reset to zero when arc detection enters the clearing state.

The number of seconds that contained at least one arc during the previous block. This count is reset at the end of each block.

The number of contiguous blocks where the arc detect block threshold has been exceeded. This count is reset with a clear block and when the triggered state is acknowledged by the head-end.

The current number of contiguous blocks where no arcs (configurable) have been detected. This count is reset to zero when a block exceeds the configured arc threshold.

These four fields display the number of times demand value has been reset, the date and time of the most recent reset, and how much time has elapsed since the most recent reset.

The number of events that this device has logged since it was most recently configured.

The number of energy profile intervals that this meter has recorded since it was most recently configured.

The number of voltage profile intervals that this meter has recorded since it was most recently configured.

This message displays on the meter's LDC panel and is meant to communicate information to the customer. Is is populated by the Pre-Pay Message API.