GV FAE Knowledge

Article ID: GV33-10-11-15
Released Date: 11/15/2010


Applied to
GV-NVR

Problem
A customer, the Keelung State Hospital, located at the northern part of Taiwan, reported that 5 of the GV-NVR Systems were in a cycle of disconnecting and reconnecting to the designated IP devices.

Problem Verification
We checked our customer’s computer on site and found that the system time delayed at a range of 30 seconds to 1 minute 30 seconds per hour, and this time delayed was added back to the system at an hourly basis. When the time was added back to the system, the IP devices were disconnected and reconnected to the GV-NVR System.

Initially, we attempted to verify the functioning of the GV-NVR System by creating a simple application program and connected it with the IP devices. The disconnecting and reconnecting issue recurred. Hence we excluded the possibility of the GV-NVR System malfunctioning. We, then, went for the further verification as below:

In-house verification:

• Since the GV-NVR System reconnects to IP devices if it does not detect streaming for over 40 seconds, we suspected that the adding back of system time interfered with the GV-NVR’s time-out rule. Therefore, we created a similar environment by using a Gigabyte EP45-UD3P motherboard, the system time delay and the GV-NVR System reconnection problems also occurred.
• We updated the BIOS of the Gigabyte EP45-UD3P motherboard and the reconnection problem did not occur again in our testing lab.

Keelung State Hospital verification:

• We updated the customer’s BIOS of the Gigabyte X58A-UD3R motherboard, and disabled the Turbo Boost function which may increase CPU load, create an unstable motherboard and system. The connection problem did not happen again.

Conclusion
After the careful verification, we concluded that the cause of the connection problem lies in the particular type of the motherboard (Gigabyte X58A-UD3R) in the customer’s pc.

Result
The customer was satisfied with our immediate help.