1. Communications basics (read this first)
  2. Not Receiving Events from the door controller(s)
  3. Database mis-match
  4. Comms Analysis - Establish which door controllers are responding
    1. What to do if doors do not respond (No Ans)
    2. What to do if you get data errors
      1. Test one door locally to the protocol convertor
Comms Analysis returns
No Ans
  1. Total network failure - no door controllers are responding. Follow these steps in order.
    1. Check the Protocol Convertor
    2. Check the serial cable connections to the PC
      • Check that you are using COM1 port on the PC
        • Many PC's come without a Serial port (COM port). In this case it is necessary to use the USB port on your PC. To do this you will require a USB to Serial converter. With this device you can create a 'virtual' COM1. Often the default with these devices is not COM1 and and will need to be manually configured.
    3. Use the network test utility to check the door controller closest to the PC
      • disconnect remainder of network whilst you do this
      • if this fails to get a response from the door controller continue to next step
    4. Test each failing door controller locally to the protocol convertor

          1. Partial network failure - some controllers are NOT responding
            1. beyond a point in the network (ie. past door 3 for example)
              1. It is likely that there is a break in the network, check your cabling... or
              2. Test each failing door controller locally to the protocol convertor
            2. randomly across the network
              1. Test each failing door controller locally to the protocol convertor
          Check the Protocol convertor
          1. Are the protocol convertor DIP switches set correctly?
          2. Power LED should be lit on the protocol converter (code 40010013 or 40010014).
          3. Does the Tx LED flash when you send data. Data is sent every poll (roughly every 2-10 seconds on most systems). If it does, this means that data is getting onto the RS485 network from the PC
          4. Does the Rx LED flash when you receive data. Data is received every poll (roughly every 2-10 seconds on most systems). If it does, this means that a controller is responding.

            If the Rx light is permanently on either
            1. The dip switches are switched ON in the protocol converter
            2. Or there is a voltage present on the receive Rx+. This could be coming from
              • a controller
              • or a short circuit.
            3. If a controller is always sending data (obviously in error) then it may be causing the fault
            4. Finally the protocol converter may be at fault, but that is less likely
          Test one door controller locally to the protocol convertor
          1. Connect one door controller directly into the protocol convertor
            1. remove the door controller from its current location
            2. connect it to the protocol convertor on a short cable
              • network connections only
            3. connect 12V to the power terminals of the door controller
            4. use the network test utility to check the door controller
          2. If the previous step fails
            1. You have a fault in the protocol convertor, the door controller, the serial cable, or the PC COM1 port.
            2. If you have another door controller, you can repeat the test, working on the principle that you are unlikely to have many of the same component faulty.

          © Door Entry Direct Ltd