paradox and PRT3

Ivica Cevis ●

Hi Martin, did you connect correctly PRT3 with RS232 module RX, TX and ground?- Attached is an example how to do it on DSC and Visnet. Wiring should be same.

Files:

Reply URL

1

Martin ●

hmm, i have RX and TX switched. look here: https://www.pdf-archive.com/2017/06/02/prt3-ei02/preview/page/1/

rest is same.

look at the Figure at page2, LEDS RX&TX on the right side do not flash. Leds in Panel bus flashes.

On page1 in the table are described settings, which should be done. Has anybody any tutorial what to do?

btw, nice picture. should be in Zipato manual or KB.

Reply URL

2

Pablo ●

Hi Martin,

Have a look in here: https://community.zipato.com/topic/paradox-alarm-and-zipatile

In case you find no answer to your question, write back here.

Regarding RXTX they should blink when there is any communitation on the Paradox system. Try activating any sensor of the alarm. Then they should blink. If not, check the wiring.

For Paradox config, my recommendation is you use "Babyware" soft from Paradox itself. But I believe there are other ways.

Reply URL

1

Martin ●

hey, thank you, the answer is in this post from you: https://community.zipato.com/topic/paradox-alarm-and-zipatile#comment-33539

i have to make that settings on PRT3.

one more question, were you able to connect PRT3 to computer via USB and then use hyperterminal?

Reply URL

1

Pablo ●

Yes! After configuring PRT3 you can do that and see on the computer that codes are received when any sensor is triggered. I managed to do that yes.

URL

1

Martin ●

Pablo, I configured the PRT3, hopefully correctly. TX on the right side do flash on events.

One thing on zipabox has changed, now I see in new device wizard, after selecting Paradox, the SN Tile. Before, it was not there. Now when I click on it, i see "Inclusion process started", but it never ends. You had same problem, how did you solve it?

URL

1

Pablo ●

Yes I had. But before anything else, try this:

When you start the discovery process, try tripping any of your alarm sensors. This will cause the PRT3 send the overall status of the Paradox alarms' zones.

Give us your feedback when tried!

URL

1

Martin ●

no success. i' see starting inclusion process screen with turning circle, but with no countdown.

i connected to PRT3 via USB and computer, and when tripping a zone, i get only a zone message, like G001N007A001/G000N007A001.

the PRT3 is configured:

[001] 12****** - i have 2 sections

[002] 12345678 - 8 zones

[014] 1234*6**

[015] 1******

[016] 12*4****

[027] 055 - here i'm not sure; 055=all events, but this section goes from 027 to 058

i will check the cable, now

URL

1

Pablo ●

Hello Martin,

you have to make the PRT3 sends all the information on the zones. For that make [016]/4 = ON (Home Automation). Then connect again to the computer and check if all the zones report back when any zone is triggered.

Also do you have already this situation on the picture? And when tryint to add the Alarm, de you click on the ZT... line?

If you have done same 2 things and still no countdown, you are on the same situation I am since 9 months. In that case, how long is the USB cable from PRT3 up to Zipatile?

URL

1

Martin ●

i have [016]/4 = ON, see settings above

which picture do you mean? when adding I click on the SN line. i looks:

Paradox

SN11111

Paradox IP

i have zipabox and RS232 module. so I go over serial cable, which is 40-50cm long.

so, support was not able to help you for over 9months? :( what did they say?

URL

1

Martin ●

picture before starting inclusion process

/7wFW98d3p4AAAAABJRU5ErkJggg==

URL

1

Pablo ●

I forgot the image but it is the same as yours. Now you have to click on the line in the middle when doing the inclusion.

I had the same situation as you with a 2,5m cable to a Zipatile (USB). No countdown. Then I opened a ticket (March/April) and they recognised a bug. After several trials and months waiting, I have the countdown. But nothing is found (I see the messages if I connect my computer to that same cable). 2 weeks ago Support suggested me to Installation a USB switch with power adapter to strenghen the signal. Havent done it yet.

And that is the situation currently. My guess is integration via USB, at least with Zipatile doesn't work. But I have to do that suggestion

URL

1

Martin ●

that's not good. you are saying, that when you trigger an event in a zone, you get status of all zones?

now, I notices something else. U tried to send UL/AL/ZL commands to PRT3 from computer, but nothing happened, i got no answer, RX diod was off. Life the module was in printer mode and not in home automation mode. Then i pressed the one button on the PRT3 board and since then i get answer and the RX diod flashes. But the answers are a bit strange:

"UL00&fail

UL001Rimas

UL002Gintaras Stepona

UL003Tinkuotojai

AL001NAMAS

AL002Area 2

AL003Area 3

AL004Area 4

AL005&fail

AL004Area 4

ZL001Garazas JD

ZL002Koridorius JD

ZL0033 kambarys JD

ZL004Miegamasis JD"

I don't know where are the texts comming. Only "Garaz" is correct.

Do you get any answer using this command?

URL

1

Pablo ●

Hello Martin, not my case... I am stuck where I told you. Anyhow, I will do a test with the Wiznet... because I see no other success stories with the USB option.

URL

1

Martin ●

so, i found something. I was able to listen to communication between paradox and zipabox /OjJ5mxPkjMbliial51N9tSFYVCPF7AACgFAEAAJQiAACAUgQAAFCKAAAAShEAAEApAgAAKEUAAAClCAAAoBQBAACUIgAAgFIEAABQigAAAEoRAABAKQIAAChFAAAApQgAAKAUAQAAlCIAAIBSBAAAUIoAAABKEQAAQCkCAAAoRQAAAKUIAACgFAEAAJT6TzvIXqPH7kYxAAAAAElFTkSuQmCC lower panel are commands , upper answers. latest command is mine, which worked. command should be RA001<CR>. Zipabox sends <CR>RA001<CR>. 0D=<CR>. Mine answer is correct, zipabox gets RA008&fail the whole log is: 000004: 000005: RA001 000006: 000007: 05D0&faiRA002RA003RA004RA005 000008: RA002RA003RA004RA005 000009: RA002RA003RA004RA005 000010: RA002RA003RA004RA005 000011: RA002RA003RA004RA005 000012: RA002RA003RA004RA005 000013: RA002RA003RA004RA005 000014: RA002RA003RA004RA005 000015: l 000016: RA001DOONOOO 000017: 000018: 05D0&fail 000019: RA002DOOOOOO 000020: 000021: 001l 000022: 000023: RA006 000024: 000025: 001N&fail 000026: RA006&fail 000027: 000028: RA007 000029: 000030: 001N&fail 000031: RA007&fail 000032: 000033: RA008 000034: 000035: 001N&fail 000036: RA008&fail empty line and new line is <CR>. Here you cannot see, but every command from zipabox starts with <CR> according to APR3PRT3_ASCII-EP00.pdf, <CR> should be on end

URL

1

Martin ●

once again, with enter:

000004:

000005: RA001

000006:

000007: 05D0&faiRA002RA003RA004RA005

000008: RA002RA003RA004RA005

000009: RA002RA003RA004RA005

000010: RA002RA003RA004RA005

000011: RA002RA003RA004RA005

000012: RA002RA003RA004RA005

000013: RA002RA003RA004RA005

000014: RA002RA003RA004RA005

000015: l

000016: RA001DOONOOO

000017:

000018: 05D0&fail

000019: RA002DOOOOOO

000020:

000021: 001l

000022:

000023: RA006

000024:

000025: 001N&fail

000026: RA006&fail

000027:

000028: RA007

000029:

000030: 001N&fail

000031: RA007&fail

000032:

000033: RA008

000034:

000035: 001N&fail

000036: RA008&fail

URL

1

Željko Cerovski ●

Martin, I am curious about your problem and would like to examine it as close as I can remotely, so I was wondering if you are available for skype chat on Sunday?

Zeljko

Reply URL

1

Martin ●

Hello Zeljko,

thank you, I opened a ticked 8944 to this problem. I will post the result here for Pablo and others

Martin

URL

1

Pablo ●

Any news, Martin?

URL

1

Martin ●

Pablo, sorry for late answer.

yesterday, i had luck and was able to connect both systems. First problem was, that i had no devices under Paradox. This was solved by Zeljko. Then Zipabox was still not able to find any zones. The logic is, that Zipabox sends ZL00i commands and reads the answer for the list of Zones. Zones must be named! (Zone 001 is wrong)

Yesterday I found out, that I had switched two wires :(

Now, Zipato had discovered correctly all zones and every zone need to be triggered, otherwise you cannot finish inclusion process. Here comes my problem with PRT3, which returns list of zones of previous owner, which doesn't make sense. When I trigger a zone, PRT3 acts correctly, only the list is bad. So, i'm not able to trigger every zone, as I don't have so many. I will contact Paradox and ask them for help.

But, here comes one question. I was able to trigger motion sensor zones, door sensor, tamper, but i have no idea what to do with glass break sensor, how to trigger it :) if this should be last issue, i will break some glasses under the sensor :))

URL

1

Martin ●

if anybody should buy an older PRT3, use Label broadcast to copy zone names (from EVO manual)

/ALVl3cFa5KiTAAAAAElFTkSuQmCC

URL

1

Ignacio Gonzalez ●

Hello, I am stuck trying to connect serial module (zipabox1) with PTR3 and evo192 paradox system. I can not get to the countdown in the initiation process. I believe I have the wiring correct. PTR3 configuration is ASCII, 9600, home automation and serila port enabled. Any help or idea you can suggest would be greatly appreciated.I open a ticket with Zipato but not help was provided.

URL

1

Željko Cerovski ●

Hello, If you send me your Zipabox serial number to zcerovski@3plus.hr, I would like to check what is going on, although I am pretty convinced you don't actually have the wires correct

URL

1

Vlad Popovici ●

Hello,

guys, please be so kind and point me in the right direction.

I am stuck in the same point, on Starting device inclusion process...

My box is ZipaBox2 with 1.3.65 firmware.

My cable is 1m long, is shielded and have magnets on it, I tested it and works flawless in any other setup. (see picture)

I tested the PRT3 with Putty (and the same cable) and I get correct status and it replies correctly on commands (Zone status, Zone labet etc).

Also I enabled only one zone (see picture) so I can trigger it easly (is a magnetic sensor).

The area is named "A1" and all zones i renamed them to start with the area name. Ex. my zone is "A1 LIV-MAG"

However I am unable to get past the "Starting device inclusion process...".

Any help is greatly appreciated.

Thank you.

Best regards,Vlad

Files:

Reply URL

1

Željko Cerovski ●

Hi Vlad,

I would like to investigate your issue of you send me your Zipabox serial number at zcerovski@3plus.he

Zeljko

Reply URL

1

Vlad Popovici ●

Thank you Zeljko but there is a problem with the email:

<zcerovski@3plus.he>:No mx record found for domain=3plus.he

Thank you Zeljko but there is a problem with the email:

<zcerovski@3plus.he>:No mx record found for domain=3plus.he

URL

1

Vlad Popovici ●

My email is wraymogg@yahoo.com, if you are so kind to write me an email, I will reply.

URL

2

Vlad Popovici ●

Hello everybody,

first of all a big thanks to Zeljko, he solved my problem very fast, so now everything is working.

I saw some posts that nobody confirmed the Paradox is working on USB, so I CAN CONFIRM IT IS WORKING. For everyone that is still trying or have questions about this, I will post a couple of tips that helped me make it work.

- First of all, you need a PRT3 for your Paradox EVOs. In case some wonders, all the EVOs are OK, I have an EVOHD and it is working fine. Also it works on the CBUS in the same time with other cards. For example I have on the same bus an IP150, and HD77 and the PRT3.

- When you set your PRT3 (I recommend BabyWare since is very easy) you only need to set Serial port enabled, ON:Home Automation, Baud rate setting to 9600 and Home Automation on Ascii Protocol. You can ignore everything else. Almost all of the other options are for reporting only, when you set the Home Automation, everything is done by specific queries, so nothing else matters. For example, Areas ans Zones, you can set them whatever, but on discovery will find all of them anyway.

- Another thing I didn't tested but others said is a must, is to set the name of the Area and the name of the Zones. Do not leave them with their default name.

- The USB cable should be as short as possible and a good quality one (shielded).

- If you get stuck on Starting device inclusion process, then ask for help here or open a ticket, it seems it is something that only devs can fix. After that the timer starts and after a couple of seconds it finds the alarm and a screen pops asking you to trigger every zone. After that you are all set.

- VERY IMPORTANT You need to go to Users and change the security pin to the master code on your alarm. The default one is 0000. Also the set part of the alarm (arm, disarm, stay) are in the Virtual network, where you should see the name of your partition (area). There you should go and check the QUICK ARM. Otherwise you cannot trigger the actions by rules.

- If you don't know already, to arm/disarm/stay by Google Assistant you need to Add new device, Virtual devices, Virtual sensor. Make 3 of them for every action you want (arm, disarm,stay). Then go where they are installed (Virtual network) and open them until you get to STATE, then click the cogwheel and copy the URL. Then go to the IFTTT, set the Google Assistant on IF, and WebHooks on THEN. On URL paste when you copied previously and don't forget to add the 1 after value=. On Method is POST and on Content Type is text/plain. On the ZipaBox rules side you put a WHEN with a sensor filled with your virtual sensor (Arm for example) and the condition is ACTIVE. Then you put an Action with your partition inside with the action ARMAWAY, for example, then put a WAIT 1 second, then a SET with your virtual sensor inside and set INACTIVE to false.

- This is ALL. The system is very sensible so you can brick it on every step you do, just reboot it and refresh the webpage. I did at least 20 reboots until I got it to work, but now it works.

Good luck!