Skip to content

Connecting the hardware

This guide covers wiring a Paradox EVO panel (EVO48 or EVO192) to Protequ and getting the first data flowing. Follow it in order.

How Protequ reaches it

Protequ talks to the EVO panel over the network, not over a direct cable. The panel needs a network endpoint:

  • A Paradox IP150+ Ethernet module plugged onto the panel's serial bus. This is the normal way.
  • A serial-to-Ethernet converter on the panel's serial port, if no IP150+ is fitted.

Either way Protequ opens one TCP connection to that endpoint on port 10000 and stays connected. Traffic is encrypted end to end.

To open the session Protequ needs two separate secrets:

  • the module password — the password of the IP150+ (or converter). It unlocks the network link.
  • the PC password — a 4-digit code programmed inside the panel. It authorises the login once the link is open.

These are two different passwords. Having one without the other will not connect.

Before you start

Have these ready before you touch Protequ:

  • The IP150+ (or converter) powered, on the same network Protequ can reach, with a known, stable IP address. Give it a fixed address or a DHCP reservation so it does not change later.
  • The module password of the IP150+. The factory default is paradox. Change it on site and use the value you set.
  • The PC password of the panel — the 4-digit code programmed in the panel for PC/software access. The panel does not allow 0000. If you do not know it, read it (or set it) in the panel programming before continuing.
  • The panel model (EVO48 or EVO192) so you pick the right one in Protequ.

On the equipment

  1. Fit the IP150+ module onto the panel's serial bus (or connect the serial-to-Ethernet converter to the panel's serial port) and power it.
  2. Plug the module into the site network with an Ethernet cable. Confirm it gets an IP address and is reachable.
  3. Set the module's own password to a value you record. The factory default is paradox; do not leave it at the default on a live site.
  4. In the panel programming, set or note the PC password — the 4-digit code used for software/PC access. Do not use 0000.
  5. Leave the module's TCP port at 10000 unless your network forces a different one. If you change it, record the new number.

In Protequ

Open the adapter's configuration page and fill in these fields:

Value on the equipment Protequ field Notes
IP150+ / converter IP address or hostname IP address Required
TCP port Port Default 10000
IP150+ / converter password Password Required; factory default paradox
Panel PC password PC password Required; 4 digits; not 0000
Reply wait time Response timeout Seconds; default 20, raise on slow links

Pick the panel type that matches the hardware (EVO48 or EVO192). Save the configuration.

Confirm it works

This adapter can read the panel layout for you. Once the configuration is saved and the adapter connects:

  1. Run discovery from the adapter. Protequ reads the panel and builds the device tree — partitions, zones, keypads, expanders, doors, readers and outputs — from what the panel actually holds.
  2. Check that the discovered partitions and zones match the site. If they do, the connection and both passwords are correct.
  3. Trigger a real change on site — open a zone, or arm/disarm a partition from a keypad — and confirm the matching event shows up in Protequ.

If discovery returns the panel layout and live events arrive, the panel is connected.

If it does not connect

  • No connection at all. Check the module is powered, on the network, and reachable at the IP address you entered. Confirm nothing blocks TCP port 10000 between Protequ and the module.
  • Connects then drops, or never authorises. One of the passwords is wrong. The module password and the PC password are checked separately — verify each against the equipment. Remember the module default is paradox only until someone changes it.
  • Login refused. The PC password does not match the one programmed in the panel. Re-read it in the panel programming and enter exactly those 4 digits.
  • Connection works but nothing appears. Confirm you selected the correct panel model and ran discovery. On a slow or busy link, raise the response timeout above 20 seconds.
  • Address keeps changing. If the module uses DHCP without a reservation its IP can move. Give it a fixed address and update the IP address field to match.