C
ONFIGURATION
C
OMMAND
S
ET
- F
IRMWARE
R
EVISION
2.4.0_
BETA
-
V
ERSION
1.0.0
information to be sent to a buffer. SMS send, for example, stores the SMS in the SMS
outbox. TCP send stores the TCP packets in the TCP buffer (which is sometimes also
called TCP history buffer). That means, if a buffer is used up, the sent action is going to
fail, only. This causes the alarm to be ‚blocked‘ until enough space inside the buffer is
available to store the message. A such ‚blocked‘ alarm attempts to send/enqueue the
information once per second. If this succeeds, the alarm will be deactivated and it can
be activated again.
6.11.4.2 SMS send
Note that, a “blocked” alarm cannot be activated again –even if all its conditions are
evaluated to True. Therefore, it is not possible to send a SMS reporting message each
second. (The first few SMS would be stored in the SMS Outbox until it is used up). Even
though the system tries to send SMS away, the Outbox will be used up faster than it can
be freed by sending. Once the outbox is used up, all alarms which attempt to send SMS
will be ‚blocked‘. They cannot be activated anymore before successfully enqueuing
their SMS to the Outbox.
These results in alarms, which will be launched not each second anymore – just e.g.
each 9 seconds (whenever the system successfully sends an SMS)
6.11.4.3 CSD send
Special care has to be taken when sending data via CSD (data call). It is strongly
recommended to include a state to each alarm to check an established CSD
connection, which attempts to send CSD data.
Unless SMS or TCP send commands, the CSD does not use an Outbox buffer to store
messages. It attempts to send the data directly. Therefore, alarms can be easily
blocked, if there is no CSD connection available.
6.11.4.4 Storing information to non volatile memory
Prevent saving of states or configurations periodically via alarms or very often. The
system is limited to several 100'000 configuration write operations. If the limit (which may
vary slightly from device to device) is exceeded, the device has to be replaced. This
also includes the saving of states of triggers/counters/timers or positions. Special
algorithms are used to increase the number of write operations, when writing history
entries. Therefore this functionality is not restricted as much as the configuration writes
operations (writing records into the history can be done for many years before the
device has to be replaced – its more likely that writing configurations from time to time
exceeds this number faster than writing history entries).
6.12 ISP, GPRS configuration parameters of German service
providers
The following table presents GPRS parameters of selected German service providers
and operators:
T-D1
Vodafone D2
E-Plus
Genion O2
APN
internet.t-mobile.de
volume.vodafone.de
internet.eplus.de
internet
REQoS
1,3,4,3,0,0
1,3,4,3,7,31
1,2,4,3,9,31
1,2,4,3,9,31
MIQoS
1,0,0,0,0,0
1,0,0,0,0,0
1,0,0,0,0,0
1,0,0,0,0,0
USERNAME
(optional)
""(None)
"eplus"
""(None)
PASSWORD
(optional)
""(None)
""(None)
""(None)
Table 65:
Service provider information, valid 16.10.2001
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 269 of 271