Chapter 1 Debugging on the LAN

Check the installed device. If the debugging fails

1. Add a controller to the software. The serial number of the controller must be correct

2. Communication mode Select "Small LAN"

3. In the "General Console" -> "Real-time monitoring" of the controller, if the communication fails, go down to check (keep "real-time monitoring")

4. Go to the controller and check whether the light is on or blinking on the controller

5. After obtaining the indicator status, ensure that the CPU is blinking normally and the Err indicator is off before connecting the green and orange indicators near the network cable:

If the green light is not on, check whether the line between the controller and the switch is connected properly (line problem);

If the orange light does not blink, then check the line (this part is complex, involving hardware lines and systems) If the orange is blinking, then check the computer, first turn off the firewall (in XP system, to turn off the windows firewall (run: firewall.cpl)) - mainly for system problems, if it doesn't work, try another computer.

Note: To turn on Windows Firewall, click Start, point to Settings, then click Control Panel, Network and Internet Connections, and then Windows Firewall.

After the above operations, we should be able to basically judge the problem.

Chapter 2 Cross-network Segment 

Debugging The key to cross-network segment debugging is the testing of ip addresses and related gateways. Key use command

ping -t 192.168.168.51

(where 192.168.168.51 is the IP address set by the controller and will be changed in actual use) If normal communication returns, In general, the local area network will not exceed 2ms, and the wide area network will not exceed 30ms; If the time is longer than 50ms, there may be a network problem (such as a network virus).

If you can't ping the controller, try ping another device or computer (in the same network segment as the controller).

If you can ping another device, Then check whether the ip gateway of the controller is set correctly (this requires the help of the network management)

After ping the controller, the software still cannot communicate, first check whether there is "enable TCPIP" in "Extension function", if there is a tick, remove the tick... Then check whether the controller IP and port Settings are correct. If not, special analysis is required.

Chapter 3 If dynamic domain names are used for Internet access control, obtain the actual IP address of the domain name

Ping -t wg3721.kmip.net

Return: Reply from 121.35.236.233: bytes=32 time<1ms TTL=64

NOTE The IP address bound to the domain name is 121.35.236.233.

If the IP address bound to the domain name is inconsistent with the WAN IP address obtained by your router during Internet access, Note that dynamic domain name resolution has problems. (This is another deal)

Chapter 4 Solutions to special problems, also professional methods

A.Prepare (five things) Laptop Two network cables , small HUB with four ports 12V power supply (for powering the controller) A.NET access controller (without IP address)

B. First in the company, debug everything is normal,

C. then go to the site, connect the five things, test everything is normal, and then go to the next test. (If the built-in does not work properly, you need to check the AC power supply)

D. And then do one by one debugging (change the same equipment, test it, so that you can find the problem)

Add the onsite controller to the management software

1. First use your own laptop to replace the field computer.

If communication is feasible, check the field computer system

2. Use the network cable delivered with the computer to replace the network cable between the computer and the switch.

If the communication is feasible, the network cable is faulty.

3.Then use the built-in HUB to change the on-site switch

If the communication is feasible. The onsite switching may have special configurations, which require the customer's network management system to handle.

4 If the communication between the controller and the switch network cable is feasible, the network cable is faulty.

5. Use the built-in.12V power supply to power the onsite access controller.

If the communication is feasible, the onsite power supply of the controller is faulty or the installation position is incorrect.

6.Then use the built-in.NET door controller to replace the on-site access controller.

If the communication is feasible, the on-site controller has problems. If not, check again starting with item C.