Paxton Net2 plus control unit - Manual (Page 7)

Page 7
7 - Fire alarm integration - Net2 Professional software must be used.
Q A voltage free normally closed contact from the fire alarm system should be wired across an ACU input
Q (Contact/PSU/Tamper/Exit). The doors that are required to open from that trigger are set up in the software for
Q that ACU under the Fire Alarm Tab.
Q NOTE: The doors are relocked from the PC software - resetting the Fire panel will have no effect on the system.
Q The Net2 Server MUST be running at all times for this method to work.
Q Fail open locks are required on fire doors. Break glasses should be installed to drop power to the lock manually.
8 - RS485 data line cable layout. (Net2 classic and Net2 plus)
Q The data line must be wired in a daisy chain. End of Line (120ohm) resistors must be fitted/switched across
Q both pairs at each end of the line.
Q Repeaters must be used over 1000 metres and can be used to create a branch from the daisy chain. Cat5 or
Q Belden 8723 (4 Core Twisted pair) must be used for the data line. The cable screen must be connected
Q throughout for reliable communication. Cat5 must have spare cores terminated in lieu of screen cable.
9 - Timesheet - Why Time & Attendance must have dedicated readers for logging in/out.
Q In the vast majority of applications using the same reader for access and T&A is not practical. Traffic through the
Q access points causes long, unmanageable T&A reports. It is therefore NOT possible to set this up in the software.
Q Proximity or Cardlock readers set up as Clocking in or Clocking out readers have no effect on Relay 1 and will not
Q appear in Access levels. Relay 2 will switch for half a second to allow confirmation by fitting an LED or sounder.
10 - TCP/IP communication over a WAN.
Q We need to establish two-way communications between a PC on site A and the TCP/IP interface on Site B.
Q The paths that the PC and the TCP/IP interface will use are different, but they each need to know the IP address
Q they are trying to locate on the other site as well as the gateway IP address that will route their requests from
Q their own LAN to the other LAN.
Q - TCP/IP Interface set up (Site B).
Q You need to set the IP address for the TCP/IP interface that will define it within it's own LAN. (e.g. 10.10.0.25).
Q You need to set the gateway IP address of the local 'router', in the TCP/IP interface. This is so that the router will
Q know that any reply from this interface needs to be sent back to the other LAN.
Q NOTE: All the information required to get back to the sending PC on site A is done automatically by the network
Q hardware; the 'site A' PC includes its own IP address in the outgoing message.
Q - PC Set up (Site A).
Q Most LAN addressing is set up such that different groups are reserved for specific remote sites. It is then just a
Q case of setting up the IP address of the TCP/IP interface on site B (10.10.0.25) in the PCs' Net2 Server
Q Configuration Utility; all the outward routing is done automatically by their network hardware.
Q Port '9999' must be allowed through any firewall software.
TCP/IP and RS485 LED indication
The Net2 plus performs two functions. It is an access control unit and also a TCP/IP RS485 converter. Information
can pass across the PCB between the TCP/IP and RS485 data port but is not relevant to this ACU.
- Server Connected LED (Steady Green)
This LED shows that the TCP/IP interface is active and receiving data from the Net2 PC server. This includes all
data for other ACU's that may be linked via the RS485 data port.
- Rx and Tx LED's
These LED's show the activity for this ACU only. This is same indication as seen on a Net2 classic ACU.
It is not dependant on the source (TCP/IP or RS485). The Rx LED will flash for all data being received and the Tx
LED will only flash when this unit responds to its own address.
Here is the list of topics about this product that receive the most technical support enquiries.
We list them here to help you speed up the installation and trouble shooting process.