Description of events from new GSM-devices
Current descriptions of events for new GSM-devices can be viewed in the templates for the Security Center 5.5.1131:
- Template of "C-Nord GSM" SC 5.5
- Template of "Си-Норд GSM+EPAF" SC 5.5
Below we describe in more detail the event codes for which questions most often arise.
Fault / Recovery of the backup battery of the wireless alarm.
Event E754 is generated when the communication channel is restarted at the site by the audit system. When restarting the device as a result of work audit system an event is generated about the reason for restarting R754.
The event with the E350 code is generated by the device at the moment when it was unable to establish a GPRS connection. As the section number in this event, the SIM number that was active at that moment is given.
The event with the R350 code is generated by the device at the moment when it restores the GPRS connection. But this event is generated only if the connection is restored on the same SIM for which an event with the code E350 was generated.
In other words, if the device has lost GPRS communication on SIM1, it generates an event with E350 code and switches to the backup channel. If the backup channel is GPRS on SIM2 and the device is connected via GPRS to SIM2, the event with code R350 will not be generated, since the device did not have GPRS problems on SIM2. The event with the code R350 will be generated only at the moment when the device reconnects over GPRS to SIM1.
As a section number in the event with the R350 code, the SIM number that was active at the time the connection was restored is transmitted, and the number of the loop or user number is the number of erroneous attempts to establish a GPRS connection on this SIM that were made.
The event with the ZZWE code is generated by the CML event source to which the devices are connected. The event registers the fact that the device has connected via IP channel and has passed the authorization procedure.
The event with the ZZWF code is generated by the CML event source if the connection to the device via the IP channel is lost, and at least 120 seconds have passed since the connection was lost. The event with ZZWF code is generated only for those devices for which an event with ZZWE code was previously generated.
A pause of 120 seconds is needed in order not to generate events about connecting / disconnecting devices in a situation when the GPRS connection is interrupted for a short time, for example, when the GPRS session is forcibly closed by the telecom operator.
Long loss of communication can be controlled with help of the processor Control chain of events.
The event is formed at the beginning of the entry delay (in the previous templates, the description was: "Probable alarm" or "Prealarm").
You can configure the Control chain of events processor so that after this event, if there is no other event for some time from the object, an alarm is generated. This allows you to avoid the situation when the intruder during the delay has time to disable the device or disable the communication channels.
This event can be sent when the device is working on a radio channel. For radio transmission, event codes are converted to EPAF format(it has two-digit codes and has its own description). If the device cannot convert the code, then code 99 is sent to the console.
Today, not all new codes from the device can be converted to EPAF, since The format is already used to the maximum and there are no free codes. In the next versions of devices we will try to redesign the format conversion and the template in the SC, so that a larger number of codes have a correspondence and description.
If the central station cannot receive the EPAF format, or there is a non-correctly specified EPAF property (checkbox in the settings of the templates in the SC), instead of code 99, a KD code may be received (Fault of zone 72). Other events on the radio may also have an incorrect description. We recommend to check the correctness of setting the EPAF property.