555059
6
Zoom out
Zoom in
Previous page
1/13
Next page
The JA-82Y GSM communicator installers manual 6/6 MDL51108
Event CID CODE
Factory default
settings
uu
Alarm after powering up the system 1140/3140 reported 00
Instant loop alarm 1130/3130 reported 01
Delayed loop alarm 1134/3134 reported 02
Fire alarm 1110/3110 reported 03
Panic alarm 1120/3120 reported 04
Tamper alarm 1144/3144 reported 05
Number of permitted incorrect code-
entries exceeded
1461/3461 reported 06
Device fault 1330/3330 reported 07
Complete setting 3401 reported 08
Complete unsetting 1401 reported 09
Codeless setting 3408 reported 12
Partial setting A 3402 reported 13
Detector communication failure 1350/3350 reported 14
Control panel power supply dropout 1301 reported 15
Control panel power supply restored 3301 reported 16
Detector power supply dropout 1384/3384 reported 17
Communicator failure 1330 Not reported 18
Communicator OK 3330 Not reported 19
Control panel battery failure 1302 reported 20
Control panel battery OK 3302 reported 21
Alarm 24h 1130 reported 23
Receiver jamming 1355 reported 24
Setting A – split system 3402 reported 26
Setting B – split system 3402 reported 27
Unsetting A – split system 1402 reported 28
Unsetting B – split system 1402 reported 29
Setting C – split system 3402 reported 30
Unsetting C – split system 1402 reported 31
Partial setting AB 3402 reported 33
Power supply ON 3301 Not reported 64
Switching to service /
maintenance mode
1306 reported 65
Exiting service / maintenance mode 3306 reported 66
End of alarm indication * Not reported 67
Reporting to ARC1 * reported 68
No reporting to ARC1 * reported 69
Reporting to ARC2 * reported 70
No reporting to ARC2 * reported 71
Alarm cancelled by user 1406 reported 78
Control panel reset 1305 Not reported 79
All tampers calm 3137 reported 80
All faults removed 3300 Not reported 81
System power supply OK * Not reported 82
The communicator has no connection 1356 reported 83
Communicator connection restored 3356 reported 84
Master code reset to 1234 1305 Not reported 85
Master code changed * Not reported 86
Power supply failure exceeding
30 minutes
1301 reported 89
Unconfirmed alarm 1138 reported 90
Service request 1393 reported 91
PgX output ON 1661 Not reported 92
PgX output OFF 3661 Not reported 93
PgY output ON 1662 Not reported 94
PgY output OFF 3362 Not reported 95
Blocking after an alarm
(Engineer reset)
1500 reported 96
Unblocking after an alarm 3500 reported 97
Low SIM card credit balance * Not reported 50
SMS transmission from a line
(e.g. from JA-84P)
- Not reported 51
ARC communication failure 1354 reported 52
ARC communication restored 3354 reported 53
tab. 3 ARC event table
Source Name
701 Control panel
731 Communicator
741 Keypad
001 - 050 Device 1 – Device 50
500 Master code
599 Service code
501 - 550 Code 1 – code 50
tab. 4 Source number table
The report to the ARC consists of:
Premises number, event code, section, source number.
Section: 01 is set for all reports
Split system for setting and unsetting: 02 = A, 03 = B
Unsplit system for partial setting: 01=ABC, 02 = A, 03 = AB
Notes:
Events to ARC are reported with the identification of the section
7.5. ARC communication checking – periodic or fixed
This sequence is used to define whether the regular transmission takes place at a
given time according to 07 p hhmm, or periodically according to 07 p hhmm
settings.
06 p x
where:
p 1=ARC1, 2=ARC2
x 0= with a period according to 07 p hhmm
1= at the set time according to 07 p hhmm
Factory default setting: With a period after the last report
7.6. ARC communication checking period
This sequence programs how often the communication check is performed:
07 p hhmm
where:
p 1 = ARC1, 2 = ARC2
hh hours
mm minutes
Notes:
Checking reports are not sent in service mode.
Jablotron IP protocol allows very frequent checking of ARC communication
(even every 5 minutes in practice).
When 00:00 is set, communication check is not performed.
Factory default setting: 23:59 (hours:mins)
7.7. Enable ARC reporting (ARC2 backs up ARC1)
This sequence allows reporting to ARCs to be switched on/off and also enables
ARC2 to backup ARC1:
08 p x
where:
p 1=ARC1, 2=ARC2
x 0=off, 1=on, 2=ARC2 backs up ARC1 (2 can only be entered for
ARC2)
Note: if ARC2 backs up ARC1 then it will only receive reports if it is not possible to
deliver them to ARC1. Each event is first reported to ARC1 (both main and backup
number / URL address) and if the transmission fails, the event is reported to ARC2.
A report containing “Communication fault to ARC1” is then sent to ARC2 together
with the first report to ARC2
Factory default setting: Transmissions to both ARCs are off
7.8. Recording ARC reporting in the control panel memory
This sequence enables the recording of every report successfully communicated to
ARCs in the control panel’s internal memory:
001 0 disabled
001 1 enabled
Note: it is recommended not to record reports sent to ARCs via reliable protocols
(IP CID and SMS CID) but to enable the indication of ARC communication faults
(see 7.9). This saves a significant amount of control panel memory. The system
initially assumes that every report is successfully delivered to ARCs, but if a report
is not successfully delivered within 110 seconds of transmission, then a
communication fault will be indicated and recorded.
Factory default setting: disabled
7.9. Indicate an unsuccessful ARC communication fault
Enables the indication and recording of a communication fault if a report is not
successfully delivered to an ARC within 110 seconds of its transmission:
002 0 communication faults not indicated
002 1 communication faults indicated
Notes:
The communicator continues trying to send information to an ARC even after a
communication fault has been indicated (after the data has been delivered,
communication fault indication stops)
for communication-checking reports the delivery time limit (confirmation from
the ARC) is 300 minutes. But if any other report is sent to the ARC it must be
confirmed within 110 seconds (otherwise a communication fault will be
indicated).
Factory default setting: communication faults not indicated
6


Need help? Post your question in this forum.

Forumrules


Report abuse

Libble takes abuse of its services very seriously. We're committed to dealing with such abuse according to the laws in your country of residence. When you submit a report, we'll investigate it and take the appropriate action. We'll get back to you only if we require additional details or have more information to share.

Product:

For example, Anti-Semitic content, racist content, or material that could result in a violent physical act.

For example, a credit card number, a personal identification number, or an unlisted home address. Note that email addresses and full names are not considered private information.

Forumrules

To achieve meaningful questions, we apply the following rules:

Register

Register getting emails for Jablotron JA-82Y at:


You will receive an email to register for one or both of the options.


Get your user manual by e-mail

Enter your email address to receive the manual of Jablotron JA-82Y in the language / languages: English as an attachment in your email.

The manual is 0,22 mb in size.

 

You will receive the manual in your email within minutes. If you have not received an email, then probably have entered the wrong email address or your mailbox is too full. In addition, it may be that your ISP may have a maximum size for emails to receive.

Others manual(s) of Jablotron JA-82Y

Jablotron JA-82Y User Manual - English - 8 pages

Jablotron JA-82Y User Manual - Dutch - 14 pages


The manual is sent by email. Check your email

If you have not received an email with the manual within fifteen minutes, it may be that you have a entered a wrong email address or that your ISP has set a maximum size to receive email that is smaller than the size of the manual.

The email address you have provided is not correct.

Please check the email address and correct it.

Your question is posted on this page

Would you like to receive an email when new answers and questions are posted? Please enter your email address.



Info