Operation and Maintenance

You can perform maintaining operations in the menu to ensure a smooth and convenient usage of the client.

Click in the upper-right corner, and then click File/System/Tool to perform the following operations.

• Open Log File — You can open a log file saved in your local PC or log files of the client.
• Import/Export Configuration File — You can import configuration files from local PC to the client if needed, and vice versa.
• Auto Backup — Select day and time to backup configuration files and data in database, or restore the backed up data.
• Batch Time Sync — Synchronize selected devices' time with your PC time.
• Message Queue — After configuring email linkage, the triggered event(s) will be displayed here. Select an event and cancel sending the an email to the receiver.

A. Custom Wiegand Rule Descriptions

Take Wiegand 44 as an example, the setting values in the Custom Wiegand tab are as follows:

(Odd Parity, Even Parity, Site Code and OEM fields are not set in this example.)

• Wiegand Data — Wiegand Data = Valid Data + Parity Data.
• Total Length — Wiegand data length.
• Transportation Rule — 4 bytes. Display the combination types of valid data. The example displays the combination of Card ID and Manufacturer Code. The valid data can be single rule, or combination of multiple rules.
• Parity Mode — Valid parity for Wiegand data. You can select either odd parity or even parity.
• Odd Parity Start Bit, and Length — If you select Odd Parity, these items are available. If the odd parity start bit is 1, and the length is 12, then the system will start odd parity calculation from bit 1. It will calculate 12 bits. The result will be in bit 0. (Bit 0 is the first bit.)
• Even Parity Start Bit, and Length — If you select Even Parity, these items are available. If the even parity start bit is 12, and the length is 12, then the system will start even parity calculation from bit 12. It will calculate 12 bits. The result will be in the last bit.
• XOR Parity Start Bit, Length per Group, and Total Length — If you select XOR Parity, these items are available. Depending on the table displayed above, the start bit is 0, the length per group is 4, and the total length is 40. It means that the system will calculate from bit 0, calculate every 4 bit, and calculate 40 bits in total (10 groups in total). The result will be in the last 4 bits. (The result length is the same as the length per group.)
• Card ID Start Bit, Length, and Decimal Digit — If you use the transformation rule, these items are available. Depending on the table displayed above, the card ID start bit is 0, the length is 32, and the decimal digit is 10. It represents that from bit 0, there are 32 bits represent the card ID. (The length here is calculated by bit.) And the decimal digit length is 10 bits.
• Site Code Start Bit, Length, and Decimal Digit — If you use the transformation rule, these items are available. For detailed information, see the explanation of the card ID.
• OEM Start Bit, Length, and Decimal Digit — If you use the transformation rule, these items are available. For detailed information, see the explanation of the card ID.
• Manufacturer Code Start Bit, Length, and Decimal Digit — If you use the transformation rule, these items are available. Depending on the table displayed above, the manufacturer code start bit is 32, length is 8, and decimal digit is 3. It represents that from bit 32, there are 8 bits are manufacturer code. (The length here is calculated by bit.) And the decimal length is 3.

B. Troubleshooting

Here are some common symptoms when operating the client software. We provide the possible causes and corresponding solutions to solve the problems.

B.1 Failed to get the live view of a certain device

Problem

Failed to get the live view of a certain device.

Possible Reasons

• Unstable network or the network performance is not good enough.
• The device is offline.
• Too many accesses to the remote device cause the load of the device too high.
• The current user has no permission for live view.
• The version of the client software is below the needed version.

Solutions

• Check network status and disable other not in use process on your PC.
• Check the device network status.
• Restart the device or disable other remote access to the device.
• Log in with the admin user and try again.
• Download the client software of the latest version.

B.2 Local recording and remote recording are confused

Problem

Local recording and remote recording are confused.

Solutions

• The local recording in this manual refers to the recording which stores the video files on the HDDs, SD/SDHC cards of the local device.
• The remote recording refers to the recording action commanded by the client on the remote device side.

B.3 Failed to download the video files or the downloading speed is too slow

Problem

Failed to download the video files or the downloading speed is too slow.

Possible Reasons

• Unstable network or the network performance is not good enough.
• The NIC type is not compatible.
• Too many accesses to the remote device.
• The current user has no permission for playback.
• The version of the client software is below the required version.

Solutions

• Check network status and disable other not in use process on your PC.
• Directly connect the PC running the client to device to check the compatibility of the NIC card.
• Restart the device or disable other remote access to the device.
• Log in with the admin user and try again.
• Download the client software of the latest version.

C. FAQ (Frequently Asked Questions)

Here are some frequently asked questions when operating the client software. We provide the corresponding answers to help the users to solve the problems.

C.1 During live view, why an error message with error code 91 prompts?

Answer

For live view of multiple windows, the channel may not support sub stream. You should disable the function of Auto-change Stream Type in System Configuration → Image, and select the appropriate steam type for live view.

C.2 During live view, why the image is blurred or not fluent?

Answer

Check the driver of video card. We highly recommend you update the driver of video card to the latest version.

C.3 Why the memory leaked and the client crashed after running for a while?

Answer

In the installation directory of the client software, open the Setup.xml file with Notepad and modify the value of EnableNetandJoystickCheck to false. Restart the client, and if the problem is still not solved, contact our technique support.

C.4 During live view, when getting stream via the Stream Media Server, why an error message with error code 17 prompts?

Answer

Check the port mapping of Stream Media Server, especially RTSP port.

C.5 How to get better performance of live view and playback when network bandwidth is low?

Answer

This function should be supported by the device. You can perform the following operations to realize live view in low bandwidth:

• Firstly, after adding the encoding devices to the client, you need to set the camera's streaming protocol.
  • Enter Device Management → Group.
  • Select the camera in the Encoding Channel list and click .
  • In the Edit Camera window, set the Protocol Type (for live view) and Playback Protocol Type (for playback) as Adaptive UDP.
  • Click OK to save the settings.
• Then you need to disable the Auto-change Stream Type function.
  • Enter System Configuration → Image.
  • Disable the switch of Auto-change Stream Type function.
• Select stream type for live view.
  • Enter Main View module.
  • In the device list on the left, move the cursor to the camera name and click → Stream.
  • For network camera, set the stream type as Third Stream. For DVRs or NVRs, set the stream type as Virtual Stream.
  • Start live view.

D. Error Code

NVMS V3

HCNetSDK.dll

Playctrl.dll

SMS