1
Introduction
What is the Push Notification Series?
The push notification series was designed for customers requiring contact closure
input monitoring via push notification rather than a query based method. This
means your application is free to process other tasks while listening for input
status change. This opens the door to many new and exciting applications such as
email/text message notification, data logging, security monitoring, and much
more. These controllers can be configured to send information to a specific
server via internet connection when their input status changes, or alternatively
they can broadcast their input status change across all devices a local area network
so many applications can be informed of the recent closure.
What can this device be used for?
The possibilities are endless. Just think, a closure generated by someone walking
through a door could trigger a notification on 5 managers’ Android devices
informing them a customer has entered the building. A notification could be sent
to a small local server such as the WiNet which can in turn send an email
notification when the float switch on a reservoir has been tripped by excess water.
Several types of devices can be connected to the Push Notification Series
product’s inputs such as motion detectors, push buttons, switches, relay outputs,
float switches, virtually any device that generates a dry contact closure. The Push
Notification series offers controllers with 1, 2, 4, and 8 contact closure inputs.
We believe this product is the missing link in so many applications. When
combined with our current products such as the WiNet and Fusion series your
imagination really is the limit to what can be done.
How do Push Notification series products work?
PN series products send a packet via TCP or UDP sockets when the status of
their inputs change. They can be configured to send this packet when the input is
open/closed, opened, or closed. Setup of the socket and a breakdown of the
packet will be covered later in this guide.
Chapter
1
