P2 Knowledge

Knowledge Base Table

Issue	Popular Solution(s)

Relay B does not trigger in the event of a fire.	Check that Relay B mode is set to Fire. To test the functionality of this open the Fire input monitoring circuit (circuit is Fire Status On when open, Fire Status Off when closed).

No Comms to P2.net Controller.	Check Firewall settings (Port numbers 10010 - 10030 on UDP and TCP/IP should be open for Doors Express).
	If a direct connection is being made check that the cable is a crossover cable and not a straight through cable.
	Check for duplicate IP addresses on the network. Ping the IP address assigned to see if there is a response. If there is a response disconnect the P2.net from the network and try to ping again. If you can still ping then there is a duplicate IP address on the system.

No comms to P2 Controller (Red Data LED solid).	Check that all RS48 5 A and B connections are correct. A goes to A and B goes to B.
	Check that the RS485 network cable is correctly earthed and screened. Any inducted voltage from other cables will be enough to illuminate the Data LED.
	If the earthing and connections are correct it is possible that a spike caused by high voltage transients or lightning damage has damaged the network chip. If this is the case, the controller will need replacing.

The reader does not respond to any credential.	Check that the X and Y connections are terminated correctly.

Delay in lock release following a valid transaction.	Check that no delay has been programmed in to the lock release.
	Check that the locking devices are adequately suppressed. Back EMF issues can damage relays.

The card is working ok but the door is not releasing.	Check to see if the relay controlling the door is changing state - if not then it is likely a faulty relay.
	Check to see if voltage is being applied or removed at the lock - if it is then there is a fault with the lock.

The door is constantly unlocked.	Check to see if a Time Zone is in effect on that door.
	Check to see if the door has been latched open manually via the PC.
	Check the voltages at the lock. Is the lock fail safe or fail secure?

Door controller freezes or locks up.	Check earthling, cabling and for adequate lock suppression (Back EMF).
	Check current load on PSU.

Doors Express has not installed correctly (P2 Server has not installed and started automatically).	Ensure that you are installing under the full administrator account.
	Disable User Account Control in Vista or 7.
	Run a repair using "Add or Remove Programs" in XP or "Programs and Features" in Vista or 7.

Client software does not connect to the Server software.	Check to see if the Client is using the right IP address to communicate to the Server (Server Settings link).
	Check Firewall settings (Port numbers 10010 - 10030 on UDP and TCP/IP should be open for Doors Express).
	If the IP address of the Server PC has changed whilst Doors Express has been running, and the connector is set to Auto-detect IP address then either restart all components of Doors Express or reboot the machine.
	If the Server is on a different PC to the Client, check if the Server IP address has changed and enter the new one if so (Server Settings link). Consider fixing the IP address of the Server PC if this happens regularly.

Invalid card event is reported but the card details (access level and enabled status) appear to be correct.	Check to see if the card has gone dormant (Use the Dormant Card Filter to see if it has or open the record directly).
	The controller may not have the correct information about that card. Update the hardware with "Enabled Cards Only".

Time Zones do not fucntion correctly in Doors Express.	Update the software to the latest build (available here)

SQL 2005 Express will not install on a Windows XP SP3 machine.	XP SP3 may have had MSXML6.0 installed prior to SQL and it is a newer version than the one that SQL 2005 is trying to use. SQL will not install under those circumstances. Run the Microsoft fix tool on the software CD then run the software installation again.