Description

This article will describe how to troubleshoot the VS13x count inaccurate problem in different scenarios.

Requirement

• VS133 Series: with firmware version 133.1.0.7-r2 and later.
• VS135 Series: with firmware version 135.1.0.7 and later.

In below we will use VS133 to refer to VS133 and VS133-P, use VS135 to refer all models of VS135 series.

Checklist

Step 1: Check Installation Environment

Installation height:

For VS133 and VS135 standard versions, the installation height ranges from 2.5m to 3.5m. For the VS135 high mount version, the mounting height ranges from 3.5m to 6.5m.

Distance from wall:

When the floor is dark or black, or the installation height is higher than 3.4m (for the standard version), it will result in a red image scene.

1. It is recommended to avoid installing device against the wall and ensure the device and the wall as follows: 

2. If the environment is relatively narrow, you can adjust the direction of the VS device to ensure that the y direction is farther away from the wall. (Such as 90° rotating equipment.)

3. If the VS13x screen is still red due to installation restrictions that cannot be further adjusted, try to enable Enhance Detection Mode to improve the inspection rate in the red screen scene.

Step 2: Check Live View Screen Status

Scenario 1:

If the screen has a lot of noisy points, it will cause missing detection when people pass the noisy points. This easy to happen to black carpet.

Solution: Turn on the ToF Noise Filtering function to adjust the screen appropriately.

• Standard Version: When installing in a spacious environment with black carpet, it is recommended to set the strength to 2; when installing in a narrow environment with black carpet, it is recommended to set the strength to 10.
• High Ceiling Mount Version: When installing in a spacious environment with black carpet: it is recommended to set the strength to 18; when installing in a narrow environment with black carpet, it is recommended to set the strength to 9.

Scenario 2:

The picture suddenly becomes very red or too bright when some people are close to the device, which cause the device not count normally.

Solution: Check whether the person has a reflective object, or the reflective strip is too large.

Scenario 3:

The device screen doesn't show the picture and doesn't count properly. As shown below:

Solution: This is because the ToF light is off, the VS13x device does not display images or count. Please configure the ToF Lighting Mode as required:

• Auto: the device will turn off the ToF light when radar detects no person for some times to save the power. This is applicable to VS135 series.
• Always On: always turn on the ToF light
• Schedule: set the specific time period to turn on the ToF light

Scenario 4:

In the detection screen, the corresponding track line is not generated when the person passes the detection line.

Solution: Please check Step 1. If the problem persists, Please refer to Step 3 to collect relevant information and send it to us for further analysis.

Scenario 5:

There is a track line when people passing the detection line in the screen, but VS13x does not count normally.

Solution: Check below settings:

• Whether the actual target height is within the target height range settings.

• When Staff Detection is enabled, if the target will be not counted if he is carrying reflective objects. VS13x currently identifies employees by reflecting light, you can turn off the feature and test again.
• Check whether the U-turn mechanism causes the filtering, and turn off this feature to test again.

• If Input Enable Line Crossing Count externally is enabled, VS13x will only start counting if the external input signals match the Trigger Status.

Scenario 6：

When using the Muti-Device Stitching feature, multiple trace lines appear resulting in multiple counts.

Solution: Check if the Stitching function is adjusted properly.

Drag the live view of node device to adjust the location and angle, and the relative position parameters will change automatically as your operations. Besides, users can also adjust the size of this live view. 

Tips: cut the staff tags or other reflective stripes into pieces and stick them to the ground of overlapping areas, then drag the live view of node devices to make highlight markers in the two live views overlap. This allows equipment splicing configuration without measurement.

Step 3: Collect Information and Send to Milesight

1. Check if the firmware version is the latest version. The latest firmwares can be downloaded here:

VS133: https://www.milesight.com/iot/resources/download-center/#firmware-vs133

VS135: https://www.milesight.com/iot/resources/download-center/#firmware-vs135

2. Send the photos of installation environment and provide below information: 

• Actual installation height of the equipment
• The distance from the wall
• People's height and clothing

3. Use the Validation function to record the video and send it to us for analysis.

4. Export the configuration file of your device and send it to Milesight.

5. If the VS device can connect to the Internet, please connect the device to Milesight DeviceHub: How to connect Milesight Gateway & Router to DeviceHub : IoT Support (milesight-iot.com)

After connected, generate the remote access link and provide the link with account information to Milesight technical support to check the device directly.

Note: please contact Milesight to apply for a DeviceHub account if you do not have it.

----END---