In this article, we will try to give you some pointers as to how to interpret "missing readings" alarms.

An example alarm email:

In this email, a single Juggle Plant is being referred to. The "small print" describes how one of the devices in this plant is not sending data.

If you receive an alarm like this, it is worth taking a look at the plant on Juggle, especially the "Plot & Report" tab. This will allow you to spot if the problem is real for this meter.

In the screenshot below, the meter in question has been found on the "tree" on the left hand side and a couple of parameters that should have been read from the meter have been ticked. The view is showing the last week, with no data displayed for this meter.

Understanding why this has happened depends on the type of system, however in this case, the Plant is being monitored using a single Juggle data logger. Looking more widely at the Plant information in Juggle, it's clear that the data logger is working and has an Internet connection.

So, in this example, we would recommend that an engineer examines the RS485 (modbus) connection between the device itself (a meter in this case) and the data logger.

Possible explanations in this case may be: - The meter is powered off or faulty - There is a problem with the RS485 (serial) connection between the meter and the data logging equipment. This may be a broken cable, or a problem with a termination.

Further examples will be added to this Wiki article to support other scenarios.