Paradox security Burgular alarm
Content languageEnglish
Description
Usage This template brings you a few default Commands to control your Security system with Loxone. You'll be able to:
- get Area and Zone status ("On change" updated by central panel of Security system) - send command to Arm, Partialy Arm or Disarm your system - get critical alerts about Power shutdown or Battery fail
HW From Loxone we need Loxone RS232 Extension for serial communication. Paradox provide Integration module called PRT3.
SW On Loxone side you use Loxone Config with this template which can be imported directly as Sensors and Actors. Paradox security control panel and Integration module are programed by Babyware. Please ask certified partner to extend control panel Digiplex EVO by Integration module PRT3 and set the communication in program.
Template It contains basic commands to start with on Residental building - 20 zones, 1 Area, Critical alerts, Arming and confirmation/fail respond on commands. All commands are easily extendable with attached documents. If you need more specific situations to catch, feel free to add any Sensors in the same syntax like mine. You can add Access system, if used or extend with more Areas, when your system is divided into more independent sections (like Guest house, Garage, another office, ...)
Important things to do before use of this template:
1. You have to set user code for Actors, where you have to Arm or Disarm your Security system. This is like a normal situation where a user enters code that authorizes an action. Simply Find&Replace dummy code "9999" by given code. 2. You have to ensure that Zones are under Area 1. If more than Area 1 is allowed, you need to get Zone assigment list from certified partner to correctly update template. It's easy, Area starts by letter A and is followed by 3 digits like A001. Only 8 areas are avaliabe in this Security system.
Inputs and outputs · 92
| Name | Type | Command | Unit |
|---|---|---|---|
| Zone 001 OFF | Comm | G000N001A001\r | |
| Zone 002 OFF | Comm | G000N002A001\r | |
| Zone 003 OFF | Comm | G000N003A001\r | |
| Zone 004 OFF | Comm | G000N004A001\r | |
| Zone 005 OFF | Comm | G000N005A001\r | |
| Zone 006 OFF | Comm | G000N006A001\r | |
| Zone 007 OFF | Comm | G000N007A001\r | |
| Zone 008 OFF | Comm | G000N008A001\r | |
| Zone 009 OFF | Comm | G000N009A001\r | |
| Zone 010 OFF | Comm | G000N010A001\r | |
| Zone 011 OFF | Comm | G000N011A001\r | |
| Zone 012 OFF | Comm | G000N012A001\r | |
| Zone 013 OFF | Comm | G000N013A001\r | |
| Zone 014 OFF | Comm | G000N014A001\r | |
| Zone 015 OFF | Comm | G000N015A001\r | |
| Zone 016 OFF | Comm | G000N016A001\r | |
| Zone 017 OFF | Comm | G000N017A001\r | |
| Zone 018 OFF | Comm | G000N018A001\r | |
| Zone 019 OFF | Comm | G000N019A001\r | |
| Zone 020 OFF | Comm | G000N020A001\r | |
| Zone 001 ON | Comm | G001N001A001\r | |
| Zone 002 ON | Comm | G001N002A001\r | |
| Zone 003 ON | Comm | G001N003A001\r | |
| Zone 004 ON | Comm | G001N004A001\r | |
| Zone 005 ON | Comm | G001N005A001\r | |
| Zone 006 ON | Comm | G001N006A001\r | |
| Zone 007 ON | Comm | G001N007A001\r | |
| Zone 008 ON | Comm | G001N008A001\r | |
| Zone 009 ON | Comm | G001N009A001\r | |
| Zone 010 ON | Comm | G001N010A001\r | |
| Zone 011 ON | Comm | G001N011A001\r | |
| Zone 012 ON | Comm | G001N012A001\r | |
| Zone 013 ON | Comm | G001N013A001\r | |
| Zone 014 ON | Comm | G001N014A001\r | |
| Zone 015 ON | Comm | G001N015A001\r | |
| Zone 016 ON | Comm | G001N016A001\r | |
| Zone 017 ON | Comm | G001N017A001\r | |
| Zone 018 ON | Comm | G001N018A001\r | |
| Zone 019 ON | Comm | G001N019A001\r | |
| Zone 020 ON | Comm | G001N020A001\r | |
| A1 ARM fail | Comm | AA001&fail\r | |
| A1 DISARM ok | Comm | AD001&ok\r | |
| A1 ARM ok | Comm | AA001&ok\r | |
| A1 partial ARM | Comm | G012N004A001\r | |
| User Code entered | Comm | G005N\#\#\#A000\r | |
| A1 OFF by master | Comm | G013N\#\#\#A001\r | |
| A1 ON by master | Comm | G009N\#\#\#A001\r | |
| A1 ARM Force | Comm | G064N001A001\r | |
| A1 DISARM fail | Comm | AD001&fail\r | |
| A1 ON by user | Comm | G010N\#\#\#A001\r | |
| A1 OFF by user | Comm | G014N\#\#\#A001\r | |
| A1 ARM Normal | Comm | G064N000A001\r | |
| A1 ARM Stay | Comm | G064N002A001\r | |
| A1 ARM Instant | Comm | G064N003A001\r | |
| A1 ALARM till OFF | Comm | G064N004A001\r | |
| A1 ALARM silent | Comm | G064N005A001\r | |
| A1 ALARM | Comm | G064N006A001\r | |
| A1 ALARM FIRE | Comm | G064N007A001\r | |
| DELAY exit | Comm | G065N001A001\r | |
| DELAY entry | Comm | G065N002A001\r | |
| OFF after event by master | Comm | G016N\#\#\#A001\r | |
| OFF after event by user | Comm | G017N\#\#\#A001\r | |
| CANCEL alarm by master | Comm | G019N\#\#\#A001\r | |
| CANCEL alarm by user | Comm | G020N\#\#\#A001\r | |
| AC fail | Comm | G036N001\r | |
| BATT fail | Comm | G036N002\r | |
| AC restore | Comm | G037N001\r | |
| BATT restore | Comm | G037N002\r | |
| A1 status query | Comm | RA001\r | |
| A1_ARM_Force | Comm | AA001F9999\r | |
| A1_ARM_STAY | Comm | AA001S9999\r | |
| A1_DISARM | Comm | AD0019999\r | |
| Z001 | Comm | RZ001\n\r | |
| Z002 | Comm | RZ002\n\r | |
| Z003 | Comm | RZ003\n\r | |
| Z004 | Comm | RZ004\n\r | |
| Z005 | Comm | RZ005\n\r | |
| Z006 | Comm | RZ006\n\r | |
| Z007 | Comm | RZ007\n\r | |
| Z008 | Comm | RZ008\n\r | |
| Z009 | Comm | RZ009\n\r | |
| Z010 | Comm | RZ010\n\r | |
| Z011 | Comm | RZ011\n\r | |
| Z012 | Comm | RZ012\n\r | |
| Z013 | Comm | RZ013\n\r | |
| Z014 | Comm | RZ014\n\r | |
| Z015 | Comm | RZ015\n\r | |
| Z016 | Comm | RZ016\n\r | |
| Z017 | Comm | RZ017\n\r | |
| Z018 | Comm | RZ018\n\r | |
| Z019 | Comm | RZ019\n\r | |
| Z020 | Comm | RZ020\n\r |
FAQ
No questions have been answered yet.
Questions and answers
Area status
OpenDobry den, prosim o radu jak vycitat stav sekce? prez jaky blok? nemate prism nejaky screen funkcnich bloku? ovladani sekci mi funguje ale nevim jak zobrazit zda je sekce zastrezena nebo ne. Dekuji za odpoved
1 reply
Dobrý den,
využít můžete například: 1. digitální senzory jednotlivých stavů, které jsou v šabloně a chodí při jednotlivých akcích. 2. nebo si v senzorech vytvoříte analogový vstup např. "A1 stav", rozeznání příkazu: "RA001\1", který vrací číselnou hodnotu stavu oblasti. Cyklicky se pak dotazujte zasláním příkazu z Aktorů "EZS A1 dotaz" a Paradox bude vracet vždy aktuální stav oblasti.
Obojí můžete vyhodnotit v bloku status (a použít lehce pro vizualizaci). Následně pro zajištění jednoho správného stavu do značek lze použít blok radiobutton vázaný na číselnou interpretaci vyhodnoceného stavu.
V druhém scénáři se vám budou hodit hodnoty a jejich stavy dle návodu Paradox: 68 = Vypnuto 65 = Zapnuto 70 = Zapnuto Force 83 = Zapnuto Stay 73 = Zapnuto Stay bez zpoždění
Výstup dle hodnoty stavu do Radiobuttonu je čistě na vás, pokud potřebujete dále používat Značky k návazné logice. Přiveďte výstup "Val" z bloku Status do vstupu "Sel" na Radiobuttonu. Zajistíte tak vždy správný a jediný platný stav do značek, které si vytvoříte (např. EZS zapnuta, EZS vypnuta, EZS Stay,...)
Getting status from paradox
OpenHello,
When monitoring traffic from RS232 I see that command recognition is matching the sensors, but in Live view I see that its not getting information through (for example to the status block) - also when using actuators, i see data going through and data back also but actuator itself does not return the value from the actuator.
Do you have an example what should be addressed to get it working?
BR, Andres
1 reply
Hello Andres,
I'm not sure where the trouble is. By saying "when monitoring traffic from RS232" you mean RS232 BUS or monitor in Loxone Config? If you see it in monitor tab in Loxone Config, this template should work. All sensors sould be checked as digital. In this you get impulse when syntax is detected. Then I suggest to use 2-switch block for detector status. Put ZONE XY ON to Son and ZONE XY OFF to Soff. You can use Marker with O output so you get status for another logic. Like this you manage status of every detector from Paradox alarm.
Try this, or reach me via mail with detailed description or log from your Config.
Regards, Robert
Hallo
OpenI am using a Paradox EVO192 in combination with a PRT3 module, which is connected via RS232 to my Loxone system.
I have already applied the recommended settings from the forum (e.g., Serial 9600, ASCII mode, etc.), but I do not see any data in the RS232 monitor within the Loxone Config when I arm or disarm the alarm system.
My setup:
EVO192 + PRT3, connected via 4-wire bus (working)
PRT3 DIP switches: set to ASCII mode
Serial interface: 9600 baud
Loxone RS232 Extension: configured to the same baud rate
PRT3 connected to Loxone via a 9-pin null modem cable
Problem: No data is being transmitted via the RS232 interface — not even status changes or events such as "arming" or "disarming".
I kindly request technical assistance on the following:
Are there additional settings required on the EVO192 or the PRT3 (e.g., event reporting or user permissions)?
Do I need to send specific ASCII commands in order to receive status updates?
Is there a working sample configuration available for Loxone?
1 reply
Hi,
looks like my previous post didn’t go through, so here’s a quick recap.
Have you configured any messages or options in the PRT3 settings in Babyware? You need to enable it to send status messages to the serial port — not just alarm events for the monitoring station, but also things like zones opening/closing when the system isn’t armed.
Sometimes the port stays silent for no obvious reason, almost as if the RS232 on the Loxone side isn’t recognized. The easiest check is to connect it to your PC with a terminal program and see if data comes through. You can even try sending a command to the PRT3 yourself. Once the port “wakes up,” it usually keeps working fine.
Hope that helps — let us know if you still have issues.
Robert
PIR a osvětlení
OpenDobrý den, potřeboval bych čidly z EZS rozsvicen noční osvětlení. Dá se stejným způsobem jako vyčítání stavu zón vyčítat i stav jednotlivých PIR?
Moc děkuji za radu
1 reply
Dobrý den, situace je pro tento případ totožná s magnety. Při správném nastavení každá zóna tiskne svůj stav i při nezakódovaném stavu EZS. Jen počítejte drobnou prodlevu. Ne tak velkou jako u Jablotronu, kde to může být až 7s. Nicméně pro noční světlo to bude zřejmě OK. Má zkušenost je převážně 1-2s.
Jinak lze použít upravený modul bez tiskového modulu - jmenuje se BUS2SER. Je o něco levnější a jinak totožný na implementaci.
Log in to rate, comment or ask a question. Log in
Ratings and comments
No ratings or comments yet.
Log in to rate, comment or ask a question. Log in