Table of Contents
Advertisement
Notifications
3.5 Notifications
Notifications are frames sent asynchronously by devices that are otherwise slaves.
The notifications are received by a device closest to the host and then sent to the
host. If the host is not available, the receiving device stores the notification and
waits until the host questions it. At this point, the device informs the host that it has
a notification. It is then the task of the host to issue a command to read the
respective notification.
Before a device can issue a notification, the notification must first be enabled.
Special frames are used to this end, depending on the notification type. If an end
device is not able to send a notification due to radio propagation or other kinds of
communication problems, it will store the date/ time when the notification took
place. As soon as the communication is re-established, the device tries to send the
notification again.
Note:
To avoid collisions, the device waits a random time (up to 10 seconds) before
sending the notification frame.
The following notifications are currently implemented for the A733 device:
Note:
The A733GSM/GPRS RTU currently does not support notifications when used in
GSM operation mode.
3.6 Returned errors list
Following are error messages you might get.
3.6.1 Command line interpreter
1 — nonexistent command
2 — command line buffer overflow (input line too long)
3 — internal error
4 — reserved
5 — missing or false parameters in command
6 — operation not implemented
7 — remote operation not allowed
8 — Invalid IMEI checksum number
9 — command not supported in this configuration
3.6.2 Device descriptors and storage handler
10 — device not found (attempt to perform a command on a nonexistent device)
11 — device already exists
12 — reserved
54
•
NOPC—Notification On Port Change (see "PORT" on page 40);
•
NOTR—Notification On Threshold Reached (see "ANLG" on page 32).
Advertisement
Table of Contents
