Interface arduino with old burglar alarm

Other Hardware General Electronics
1

As title suggest, i'd like to start this new project. as you can see by the photo, it's a closed system.
My goal is to find a way to turn on and off this alarm at a distance with an iot program (cayenne,etc) and monitor the alarm state (on,off).

At the moment i'm quite lost. I thought I had something going with the internal siren pins, (in using the dc output as an arduino high signal, from then I could disable internal and external siren with an npn transistor). Unfortunately I discovered that it was outputting an AC 60v. Also, there's no way I could capture the remote control 433.92mhz signal (encrypted?).

Currently the only idea I have is soldering some outputs from the leds to acknoledge the alarm status and hacking the remote control itself making it wired for internet control.

I'd love to receive some hints, tks

I have no electronics diagrams apart from the original instructions

2

Update: I've been doing some research on the main chip, PIC 16F84
I've connected negative to VSS, according to this image SamacSys PCB Symbol Preview

So I've been looping around and checking the system states and I discovered that

it seems that when the siren sounds, pin 23 goes to 5v, and when it goes off we have 0v
Also the state of the alarm is on at pin 25 high and off at pin 25 low

This is cool, it means that I can disable with a relay the internal and add an external siren (currently we don't have one). But I still don't know how to disarm and re-arm apart from the remote.

3

joerack:
But I still don't know how to disarm and re-arm apart from the remote.

Well, you have to figure out what signals the remote receiver (the board at the top) sends to the PIC.

4

you mean, intercepting and grabbing the remote codes with a RF receiver, or checking what lanes on the cirucuit connect when a signal is sent?

5

Hi.

Paul__B's message couldn't be more accurate and clear.

Paul__B:
figure out what signals the remote receiver (the board at the top) sends to the PIC

So, that's not to try to receive the signals again (where would that get you ?), as you already mentioned you aren't able to do so.
Instead, find out what receiver module that is, and what it outputs to the alarm's controller.

Do not plan on putting your Arduino or any other electronics near the receiver module.
Those voids on the PCB are there for a reason.

6

thanks for the tips.

I plan on installin my arduino on top of the alarm, which is almost 10cm away fron the whole pcb board.

can I take the 5v source from VDD/VSS of the PIC (would a diode be necessary to protect the pic?)

7

MAS3:
Those voids on the PCB are there for a reason.

Now you come to mention it, the daughterboard looks like a complete receiver with a SAW resonator, but on the main PCB just below it appears to be another transmitter unit. I am wondering what that is; it is unlikely to be a superregenerative RF unit and I cannot see why it would be a proximity detector.

joerack:
can I take the 5v source from VDD/VSS of the PIC (would a diode be necessary to protect the pic?)

No, you take it from the 5 V regulator itself. A diode will not do anything.

8

Or .... you could throw the board away and buy a more modern control board which has the interfaces present and is maintainable . ( if your old board fails you’ll have to start over).

9

but on the main PCB just below it appears to be another transmitter unit. I am wondering what that is; it is unlikely to be a superregenerative RF unit and I cannot see why it would be a proximity detector

I suppose it's this all wireless alarm unit:

The markings on the PCB tells me so.
It'll have to communicate with sensors and other peripherals through a wireless connection.

10

I've managed to capture the Rf frequency with arduino and 3.5 jack of gate:

https://i.imgur.com/NngxsAB.png (2 presses)

Alarm: ( 3 presses)

3200×1080 256 KB

3200×1080 248 KB

3200×1080 262 KB

There's a big difference between the signal lengh of my gate and alarm. Do you think it's reliable? (I'll do the calculations)

11

Yes this is the alarm, it's called GT casa alarm 2200

12

I've had some more progress using another library called rfremot

at least this time I have something printed at (of which I can't make out much from )

This is the garage gate output:

[.] Ready
[01] S=24(24), SYN: 11634 - T1=12 (331), T2=12 (637), T3=0 (0), T4=0 (0), T?=0 (0) {637|1} - 11634
[02] S=24(24), SYN: 11636 - T1=12 (330), T2=12 (637), T3=0 (0), T4=0 (0), T?=0 (0) {637|1} - 11635
[03] S=24(24), SYN: 11634 - T1=12 (331), T2=12 (636), T3=0 (0), T4=0 (0), T?=0 (0) {636|1} - 11634
[04] S=24(24), SYN: 11634 - T1=12 (332), T2=12 (636), T3=0 (0), T4=0 (0), T?=0 (0) {636|1} - 11634
[05] S=24(24), SYN: 11636 - T1=12 (332), T2=12 (636), T3=0 (0), T4=0 (0), T?=0 (0) {636|1} - 11634
[06] S=24(24), SYN: 11634 - T1=12 (332), T2=12 (636), T3=0 (0), T4=0 (0), T?=0 (0) {636|1} - 712
[07] S=24(24), SYN: 11636 - T1=12 (332), T2=12 (636), T3=0 (0), T4=0 (0), T?=0 (0) {636|1} - 2272
[08] S=24(24), SYN: 11634 - T1=12 (332), T2=12 (636), T3=0 (0), T4=0 (0), T?=0 (0) {636|1} - 3442
[09] S=24(24), SYN: 11636 - T1=12 (331), T2=12 (637), T3=0 (0), T4=0 (0), T?=0 (0) {637|1} - 4353
[10] S=24(24), SYN: 11636 - T1=12 (332), T2=12 (636), T3=0 (0), T4=0 (0), T?=0 (0) {636|1} - 5081
[11] S=24(24), SYN: 11636 - T1=12 (331), T2=12 (637), T3=0 (0), T4=0 (0), T?=0 (0) {637|1} - 5677
[12] S=24(24), SYN: 11632 - T1=12 (331), T2=12 (637), T3=0 (0), T4=0 (0), T?=0 (0) {637|1} - 712
[13] S=24(24), SYN: 11634 - T1=12 (331), T2=12 (637), T3=0 (0), T4=0 (0), T?=0 (0) {637|1} - 1552
[14] S=24(24), SYN: 11634 - T1=12 (331), T2=12 (636), T3=0 (0), T4=0 (0), T?=0 (0) {636|1} - 2272
[15] S=24(24), SYN: 11634 - T1=12 (332), T2=12 (636), T3=0 (0), T4=0 (0), T?=0 (0) {636|1} - 2896
[16] S=24(24), SYN: 11636 - T1=12 (331), T2=12 (636), T3=0 (0), T4=0 (0), T?=0 (0) {636|1} - 3442
[17] S=24(24), SYN: 11632 - T1=12 (332), T2=12 (636), T3=0 (0), T4=0 (0), T?=0 (0) {636|1} - 69
[18] S=24(24), SYN: 11636 - T1=12 (332), T2=12 (636), T3=0 (0), T4=0 (0), T?=0 (0) {636|1} - 712
[19] S=24(24), SYN: 11632 - T1=12 (332), T2=12 (636), T3=0 (0), T4=0 (0), T?=0 (0) {636|1} - 1286
[20] S=24(24), SYN: 11636 - T1=12 (333), T2=12 (635), T3=0 (0), T4=0 (0), T?=0 (0) {635|1} - 1804
[21] S=24(24), SYN: 11638 - T1=12 (332), T2=12 (636), T3=0 (0), T4=0 (0), T?=0 (0) {636|1} - 2272
[22] S=24(24), SYN: 11636 - T1=12 (333), T2=12 (635), T3=0 (0), T4=0 (0), T?=0 (0) {635|1} - 2698
[23] S=24(24), SYN: 11634 - T1=12 (331), T2=12 (637), T3=0 (0), T4=0 (0), T?=0 (0) {637|1} - 237
[24] S=24(24), SYN: 11634 - T1=12 (331), T2=12 (637), T3=0 (0), T4=0 (0), T?=0 (0) {637|1} - 712
06:53:23.707 -> [*] Bits: 12 - SP: 331, LP: 636 (?, 1:?) - SYN: 712 (?, 1:?)
[*] A2: 637, A3: 0, A4: 0, AX: 0
06:53:23.740 -> 
06:53:23.740 -> ~SsLsLsLsLsLsLsLsLsLsLlSlS~
06:53:23.808 -> ~SsLsLsLsLsLsLsLsLsLsLlSlS~

and this is the alarm remote control output

[01] S=126(122), SYN: 17058 - T1=63 (501), T2=59 (1003), T3=0 (0), T4=0 (0), T?=4 (938) {970|2} - 17058
[02] S=126(116), SYN: 4662 - T1=63 (486), T2=53 (1026), T3=0 (0), T4=0 (0), T?=10 (932) {979|2} - 10860
[03] S=126(112), SYN: 17058 - T1=63 (495), T2=49 (1024), T3=0 (0), T4=0 (0), T?=14 (928) {976|2} - 12926
[04] S=126(107), SYN: 17064 - T1=63 (496), T2=44 (1035), T3=0 (0), T4=0 (0), T?=19 (924) {979|2} - 13960
[05] S=126(116), SYN: 17066 - T1=63 (496), T2=53 (1014), T3=0 (0), T4=0 (0), T?=10 (933) {973|2} - 1474
[06] S=126(126), SYN: 17078 - T1=63 (509), T2=63 (1019), T3=0 (0), T4=0 (0), T?=0 (0) {1019|1} - 4075
[07] S=126(124), SYN: 17090 - T1=63 (512), T2=61 (1024), T3=0 (0), T4=0 (0), T?=2 (884) {954|2} - 5934
[08] S=126(124), SYN: 17082 - T1=63 (513), T2=61 (1026), T3=0 (0), T4=0 (0), T?=2 (890) {958|2} - 7327
[09] S=126(121), SYN: 17088 - T1=63 (509), T2=58 (1018), T3=0 (0), T4=0 (0), T?=5 (1053) {1035|2} - 1130
[10] S=126(125), SYN: 17094 - T1=63 (512), T2=62 (1024), T3=0 (0), T4=0 (0), T?=1 (896) {960|2} - 2726
[11] S=126(119), SYN: 17096 - T1=63 (509), T2=56 (1019), T3=0 (0), T4=0 (0), T?=7 (1036) {1027|2} - 4033
[12] S=126(124), SYN: 17084 - T1=63 (512), T2=61 (1024), T3=0 (0), T4=0 (0), T?=2 (890) {957|2} - 5120
[13] S=126(121), SYN: 17082 - T1=63 (507), T2=58 (1014), T3=0 (0), T4=0 (0), T?=5 (1097) {1055|2} - 999
[14] S=126(122), SYN: 17088 - T1=63 (514), T2=59 (1029), T3=0 (0), T4=0 (0), T?=4 (890) {959|2} - 2148
[15] S=126(124), SYN: 17088 - T1=63 (511), T2=61 (1022), T3=0 (0), T4=0 (0), T?=2 (998) {1010|2} - 3144
[16] S=126(124), SYN: 17086 - T1=63 (512), T2=61 (1025), T3=0 (0), T4=0 (0), T?=2 (892) {958|2} - 4016
[17] S=126(124), SYN: 17086 - T1=63 (512), T2=61 (1025), T3=0 (0), T4=0 (0), T?=2 (894) {959|2} - 929
[18] S=126(121), SYN: 17090 - T1=63 (514), T2=58 (1029), T3=0 (0), T4=0 (0), T?=5 (929) {979|2} - 1827
[19] S=126(125), SYN: 8268 - T1=63 (510), T2=62 (1021), T3=0 (0), T4=0 (0), T?=1 (896) {958|2} - 2166
[20] S=126(125), SYN: 12518 - T1=63 (510), T2=62 (1021), T3=0 (0), T4=0 (0), T?=1 (896) {958|2} - 2684
[21] S=129(42), SYN: 10982 - T1=23 (408), T2=19 (1039), T3=0 (0), T4=0 (0), T?=87 (741) {890|2} - 3079
[22] S=134(115), SYN: 31698 - T1=58 (493), T2=48 (986), T3=9 (1090), T4=0 (0), T?=19 (635) {903|3} - 1401
[23] S=126(126), SYN: 29922 - T1=63 (509), T2=63 (1019), T3=0 (0), T4=0 (0), T?=0 (0) {1019|1} - 2641
[24] S=126(123), SYN: 17084 - T1=63 (513), T2=60 (1027), T3=0 (0), T4=0 (0), T?=3 (886) {956|2} - 512
06:49:01.070 -> [*] Bits: 63 - SP: 502, LP: 974 (?, 1:?) - SYN: 512 (?, 1:?)
06:49:01.104 -> [*] A2: 1027, A3: 0, A4: 0, AX: 886


06:52:00.084 -> ~?s????s?????~
06:52:00.118 -> ~???S???????~
06:52:00.421 -> ~#
06:52:01.164 -> ~#
06:52:01.434 -> ~?l???????~
06:52:01.468 -> ~??~
06:52:01.506 -> ~??????s??????l???~
06:52:01.506 -> ~?~
06:52:01.540 -> ~??l??????S~

Which would confirm the lengh of the signal is of 12 (gate) and 64 (alarm)

Unfortunately instead of decoding the signal I get a lot of gibberish