Account Code Setting; Protocol And Format Setting; Re-Dialing Pause Setting - jablotron MAESTRO JA-65 Installation Manual

•
The pulse formats are not capable to report zero and numbers above 15. For this reason events in zone 16 or in a subsystem are
reported to the Monitoring Station as events in zone 10. This means that from the point of view of the monitoring station zone 10
also covers zone 16 and the subsystem if used. This problem does not exist in the CID protocol.

16.2. Account code setting

This sequence is used for the alarm system identification by a Monitoring Station. The sequence structure is as follows:
02 x x x x
When using only three-digit codes (formats 3/1 and 3/2) enter a zero in the first position. The communicator will then ignore it (example
- 0123)
Note: Changing of the account code erases the internal communicator's memory of non reported events and sends a
„Reset" reporting code (051) to the Monitoring Station. If pulse formats are used, zero is transmitted as A
Factory setting: 0000

12.3 Protocol and Format setting

This sequence is used to select the communication protocol and format. Its structure is as follows:
03 x y
x Name Hand-shake
0 Ademco Slow
(Silent Knight)
1
Ademco Fast
2
Telemax
3 Franklin
4 Radionics 2300
5 Radionics 1400
6
DTMF 2300
7
Sur Guard*
8 Ademco express* Dual tone
9 Contact ID* Dual tone
*
fixed format, "y" is
Notes:
1/ Some Monitoring Station receivers do not support all formats.
2/ Logic of the format marking - 4/2 means, that an account code has
4 digits and an event report code has 2 digits.
Changing of a format erases the internal communicator's memory of non reported events and sends a „Reset" reporting code (051) to the
Monitoring Station.
Factory setting: 90 (Contact ID)

16.4. Re-dialing pause setting

When activated, the communicator tries to communicate with the Monitoring Station (alternates between the main and
back up phone number if no handshake is received). After 8 attempts it stops and tries again after a pause programmed
in this section. All non sent events will be queued and transmitted together after establishing a connection.
0 4 x
x – time multiplied by 10 minutes (from 1 to 9, example 3 = 30 minutes)
Factory setting: 1 = 10 min.
Alarm system JA-65 MAESTRO
xxxx – account code ( x are numbers from 0 to 9 or hexadecimals).
x - protocol (0 – 9, see table bellow)
y - format (0 - 3 see table on right
Protocols
Data Kiss off
1400Hz 1900Hz 1400Hz 10bps
1400Hz 1900Hz 1400Hz 14bps
2100Hz 1650Hz 2100Hz 10bps
2300Hz 1800Hz 2300Hz 20bps
2300Hz 1800Hz 2300Hz 40bps
1400Hz 1900Hz 1400Hz 40bps
2300Hz DTMF 2300Hz DTMF
2300Hz DTMF 2300Hz DTMF
DTMF 1400Hz DTMF
DTMF 1400Hz DTMF
arbitrary (0 is recommended)
)
y format
0
1
Speed format
2
Next
table
3
Next
xxxx = account number
table
R = major event code (only first digit counts)
Next
rc = detailed event code (two digits)
table
n = source identification (generated automatically)
Next
Sur Guard protocol has structure: xxxx E rc, where
table
E is a group identifier (generated automatically)
Next
E
table
1 Fire
Next
2 Panic
table
3 Alarm
Next
4 Arming
table
5 Disarming
4/3
6 Failure
4ID/2
8 Report
CID
9 Restore
A Test
- 21 -
Formats
reports
Major events only
3/1
All events
3/2
4/1/1 Major events with autom.
source identification
All events
4/2
Event Note
General
Incl. Partial
Mains failure, RF jamming etc..
Enter/Exit service mode ...
End of alarm, panic ...
24 hour test
sequence: 02
h
sequence: 03
structure
xxx R
xxx rc
xxxx Rn
xxxx rc
sequence: 04
MFM51202