OmniPod UST400, User Manual

Page: 150 / 202

135
Understanding PDM and Pod Function 12 12 Understanding PDM and Pod Function
Timing of alarms and notifications originating in the Pod
If the Pod is sounding an alarm, the PDM also sounds an alarm as soon as it is
aware of the alarm. However, there may be a delay before the PDM sounds an
alarm that originates in the Pod.
• If the PDM and Pod are in range of each other and:
• you use the PDM, the PDM checks the Pod's status. If the PDM finds that
the Pod is sounding an alarm, the PDM sounds an alarm as soon as the
status check is complete.
• you do not use the PDM, the PDM's alarm is delayed until it wakes
itself up to perform a status check, which could mean a delay of up to 30
minutes.
• If the PDM is out of range, the PDM does not sound a Pod-originated alarm
even if the Pod is sounding an alarm.
Therefore, if you hear a Pod alarm, bring your PDM in range of your Pod and turn
on your PDM. This triggers a status check which results in a message explaining
the alarm.
As with alarms, if a notification originates in your Pod, there may be a delay of up
to 30 minutes before an in-range PDM begins to beep.
When the PDM cannot communicate with the Pod
When you turn on your PDM, it attempts to establish communication with the
active Pod. Usually, communication occurs quickly. Occasionally,
communication takes longer, and the PDM screen's header bar displays the
communication icon during the delay:
The PDM cannot communicate with the Pod when:
• A USB cable is plugged into the PDM's USB port.
• The PDM and Pod are separated by more than 1.5 meters (5 feet).
• The PDM's batteries are dead.
• There is too much outside interference (see "Omnipod® System Notice
Concerning Interference" on page 163).
For instructions on handling communication problems, see "Pod
Communication Failures" on page 102.