ADESCO MQ03-4I 설치 및 구성 매뉴얼 - 페이지 7

{카테고리_이름} ADESCO MQ03-4I에 대한 설치 및 구성 매뉴얼을 온라인으로 검색하거나 PDF를 다운로드하세요. ADESCO MQ03-4I 11 페이지. Global sim universal communicators

페이지 인쇄

dialer are reported using the Site Number that is programmed into the alarm panel itself. Therefore, ensure that you have conﬁgured the same

Site Number on both the communicator and the alarm panel.

Conﬁguring diﬀerent Site Numbers for diﬀerent partitions

When the system is split into multiple partitions, you can provide diﬀerent Site Number for each partition. In this way you can conﬁgure a single

communicator to report events from diﬀerent sites independently.

You can specify up to 4 additional Site Numbers in the SiteNo1 – SiteNo4 ﬁelds in the Alarm Settings section on the administrative web site and

administrative mobile application. If an event from partition 1 is received it will be reported with SiteNo1. If SiteNo1 is not speciﬁed, then the

event is reported with the generic SiteNo. If an event from a partition is outside the range 1-4 then again the generic SiteNo is used.

Note! The events from the dialer and from the serial port of the alarm panel contain extended data about the partition. Besides that, you can still

split the system in partitions even if the panel is connected only to the digital inputs of the communicator. For example, you can specify that

input 1 will generate alarm event from partition 1 and input 2 will generate alarm event from partition 2. (See "Messages from digital inputs"

section). In this way you can again get event reports from diﬀerent independent Site Numbers.

Note! The general events that are speciﬁc to the communicator itself will be reported only for one of the Site Numbers! Such general events for

example are the Connection Lost event, Jamming Detected, Periodic Test.

Reporting to Central Monitoring Station

Besides sending the events to the client site and the client mobile application, the device can report also to Central Monitoring Station. For easy

integration with most of the monitoring software, events can be redirected using diﬀerent popular hardware receivers' protocols such as

SurGard MLR2, Visonic, KP RCI3300 etc. To enable redirecting data to a Central Monitoring Station, go to Alarm Setting page of the device in the

administrative web site or in the administrative mobile application and check the "Report to CMS" checkbox.

Choose the transport protocol from the "Receiver protocol" list, e.g. SurGard MLR2.

The format of the messages that is used by default is Ademco Contact ID.

Conﬁguring the messages generated by the MQ03 communicators itself

Configuring periodic test messages

You can conﬁgure the GPRS communicator to send test messages periodically over a speciﬁed time interval. This can be done ONLY from the

administrative web site.

If the Test Intl. ﬁeld is left blank, no test messages will be emitted by the GPRS communicator.

Note! It is very important to distinguish between periodic tests and the so called heartbeats that are used to monitor the connection between

the device and the server. The device sends heartbeats to the server in very short intervals in order to maintain a constant connection with the

server and to enable the server to detect when the device is disconnected and to send an alarm message. Generally, it might be from several

seconds to several minutes. These heartbeats ARE NOT forwarded as events to the monitoring center. An alarm event is sent only when the

server detects that a device is disconnected.

On the other hand, the periodic test message is sent to the monitoring center and is usually set at intervals of a few hours. Its purpose is to

prevent the occurrence of events of the type 'No Event for Long Time' in the monitoring software.

Most of the traﬃc generated by the communicator is due to the keep-alive heartbeats. That's why you CANNOT conﬁgure the heartbeats

interval by yourself. It is part of you service agreement. If you want to change the heartbeats interval, please contact your account manager.

You can only conﬁgure the interval of the test messages that are sent to the monitoring software.

Programming messages from the digital inputs

You can conﬁgure the messages that will be reported when the state of a digital input is changed. This can be done from both the administrative

web site and administrative mobile application from the Input pins section on the Alarm Settings page.

Generally, the digital inputs are activated with GND. Please refer to the hardware speciﬁcation of your device.

You can conﬁgure the message that will be sent when the input level is high (GND not applied) from the "Raising/ON" field of each input. You can

conﬁgure the message that will be sent when the input level is low (GND applied) from the "Falling/OFF" ﬁeld of each input. Messages are

entered using the Contact ID format. From the administrative web site click 'Edit' button for each ﬁeld you want to edit. From the

administrative mobile application click the ﬁeld itself. A dialog will open and you should specify the event code, the partition and the zone/user

components of the Contact ID message.

If a ﬁeld is left blank, this digital input will not report events.

Low battery and Mains power outage messages

This message can be conﬁgured ONLY from the administrative web site.

The device monitors the power supply voltage and can report a message in case of missing mains power supply or low battery. You can conﬁgure

the message code, as well as how long the voltage has to be below a set threshold before generating the alarm event. Detecting the mains

power outage relies on the fact that when mains power is available, the voltage will be above 13.2V to be able to charge the battery. This

threshold can also be conﬁgured.

Connection Lost message

This message can be conﬁgured ONLY from the administrative web site from the Connection Alarm section of the Alarm Settings page. The

device maintains a constant connection to the server via GPRS and periodically sends keep-alive heartbeats to notify the server that it is working

properly and that the connection is alive. If the server does not receive data from the device, it will report an alarm message about the

disconnected device.

Most of the traﬃc generated by the communicator is due to the keep-alive heartbeats. That's why you CANNOT conﬁgure the heartbeats

interval by yourself. It is part of you service agreement. If you want to change the heartbeats interval, please contact your account manager.

Communication Channel messages

This message can be conﬁgured ONLY from the administrative web site from the Channel Change section of the Alarm Settings page. If you are

using ADESCO SIM cards (provided by ADESCO) you can beneﬁt of using the network of multiple operators with a single SIM card. If the network

GSM/GPRS Communicator MQ03 Installer Manual Version 1.1

page 7 of 11