DS-2CD2387G2H-LISU/SL detection issues

[DBUK]

Hi all, looking for any potential solution to get one of my cameras detecting motion & intrusion, everything is setup correctly as far as i can see, the camera is a DS-2CD2387G2H-LISU/SL, all detection zones are set, linkage set, but it regularly does not see our car enter the driveway, or people, its intermittent, sometimes it does, then doesn't, it seems to be worse at night.

I have motion currently set on this camera at 100%, intrusion at 100%.

All cameras on H265+
Exposure 1/100
HDR Off
Noise reduction 50
Variable bit rate
video quality medium
20 FPS

Tried adjusting the Min/Max boxes, changed the perimeter to see if this helps.

Camera is set on smart so its black and white until motion is detected, then colour.

24/7 recording.

Checked all settings to ensure all notifications are set correctly.

I have also turned on VCA on the hik-connect app, walked under the camera, intermittent whether it detects or not, 80% it gets people, 10% it gets our car, the red perimeter line does not always change to red to show detection, but the next day it might work correctly.

Camera is about 3m high. no obstructions, clear view down our driveway, angled as its on the side of our house, driveway runs front to back.

Could this be a software/firmware issue as everything i have tried does not seem to make much difference.

Thanks


NVR: DS-7604NXI-K1/4P Acusense

[D1] Front-Cam01	DS-2CD2387G3-LIS2UY/SL	V5.8.10 build 250605	--	The version is already the latest.	--
[D2] Rear-Cam02	DS-2CD2347G1-LU	V5.6.821 build 230831	--	The version is already the latest.	--
[D3] Driveway-Cam03	DS-2CD2387G2H-LISU/SL	V5.7.19 build 241207

 

[fullboogie]

I'm convinced there's a batch of those cameras that are bad. I upgraded to a 2387G2 for my front door and I had the exact same problems as you. I reset it multiple times, reloaded firmware, fiddled with the detection settings and nothing worked. Very intermittent detection. I threw it away and put up another camera and it works flawlessly like my other 7.

 

[DBUK]

I'm convinced there's a batch of those cameras that are bad. I upgraded to a 2387G2 for my front door and I had the exact same problems as you. I reset it multiple times, reloaded firmware, fiddled with the detection settings and nothing worked. Very intermittent detection. I threw it away and put up another camera and it works flawlessly like my other 7.

Yep I've the done the same, reloaded the firmware about 5 times, changed the settings 100s of times, and nothing seems to work, driving me crazy, but good to know others have experienced this. The G3 has been spot on which I changed a week prior to the G2. I've considered putting an older firmware version on to see if that does anything.

I think I will be going down the same route as you and throwing it in the bin, unless there is something I am missing or any advice from others who have fixed the issue somehow.

Thanks for replying

 

[alfaclvi]

Those issues exist for many years. The "new" v5.7.19 instead of fixing, just made things worse with Dual VCA problem. I am sure you also have exactly the same problems with me, since we have the NXI-K, on which they never managed to fix issues. The easy solution was to go EOL earlier. Just using this with many many tricks. Yes Detection for close to camera targets is a serious problem. Huge "objects" like Human walking out of their entrance and under the cameras, are not detected at all. Possibly wrong calibrated under camera detection distances from factory. The target must loiter even if loitering is set to 0. Left to right movement detection usually is ok. On the other hand very small targets like birds or cats are always detected at distances of 12 to 20 meters. Recognition requires Detection. The very strange thing about those missing detections on Smart Events, is that the same target is simple Motion detected but usually not recognized. Try raising the installation height a few centimeters, try higher more than ten cm and check again. Try different angles. There is really no solution. I am on v5.7.15 and the only "good" thing is the dual vca. Nothing else.

 

[Yorkie]

I have the 4mp version of this camera and found the Intrusion Detection was a bit hit-and-miss, I have it linked through a relay so that a security light comes on when I arrive on the bike and half the time it wouldn't do anything......... I have deactivated the Intrusion Detection a few months ago and instead have been using Region Entrance Detection - it's not 100% accurate, but it's better.

 

[DBUK]

Those issues exist for many years. The "new" v5.7.19 instead of fixing, just made things worse with Dual VCA problem. I am sure you also have exactly the same problems with me, since we have the NXI-K, on which they never managed to fix issues. The easy solution was to go EOL earlier. Just using this with many many tricks. Yes Detection for close to camera targets is a serious problem. Huge "objects" like Human walking out of their entrance and under the cameras, are not detected at all. Possibly wrong calibrated under camera detection distances from factory. The target must loiter even if loitering is set to 0. Left to right movement detection usually is ok. On the other hand very small targets like birds or cats are always detected at distances of 12 to 20 meters. Recognition requires Detection. The very strange thing about those missing detections on Smart Events, is that the same target is simple Motion detected but usually not recognized. Try raising the installation height a few centimeters, try higher more than ten cm and check again. Try different angles. There is really no solution. I am on v5.7.15 and the only "good" thing is the dual vca. Nothing else.

Thanks for replying, very annoying. Repositioning is not an option due to install method, but ive tried all angles to try and improve the detection. Example, today i reversed down the drive, car not detected, then walked down the driveway, i was detected, some days the car is detected, but 9 times out of ten its not.

 

[DBUK]

I have the 4mp version of this camera and found the Intrusion Detection was a bit hit-and-miss, I have it linked through a relay so that a security light comes on when I arrive on the bike and half the time it wouldn't do anything......... I have deactivated the Intrusion Detection a few months ago and instead have been using Region Entrance Detection - it's not 100% accurate, but it's better.

Even basic motion detection does not seem to notice our cars moving down the drive, intrusion seems to be as you say hit and miss, hopefully a future firmware wil rectify the issue, but i will most likely change the camera before that.

 

[DBUK]

If anyone else has any suggestions, or advice on how to rectify this please let me know.

 

[fullboogie]

Replace the camera.

 

[JB1970]

I've not had issues with these cameras with regard to detection, but don't I dispute that some people have...

Is the camera correctly orientated for its view (if you stand in the centre of the field of view you should appear upright)? I see many cameras installed (incorrectly IMHO) partially rotated, so that a door or object at one side of the image appears level. Please post a screenshot of the camera view.

When setting up a camera for line crossing/intrusion detection I'd always:

• Configure the event from the NVR, if the camera is managed by an NVR. If additional options relating to the event setup are unavailable in the NVR interface (min/max on older firmwares, target validity etc), those parameters (and only those parameters) can be adjusted in the camera later.
• Start with detection set at the defaults. Sensitivity at 50 and no minimum/maximum set. Those minimum/maximum parameters can be set later to filter out false alerts.
• Minimum/maximum when set, need to be adjusted for the camera perspective. The minimum being slightly smaller than an object at the furthest point at which the trigger can take place, and the maximum slightly larger than an object at the nearest point to the camera at which a trigger could take place.
• Line crossing is more effective for targets moving across the line right/left, left/right, rather than toward or away from the camera.
• Both line crossing and intrusion detection will work better when not positioned to the edges of the view (target fully in view before crossing the line/entering the intrusion area)
• Personally I wouldn't be bothering with minimum/maximum parameters if I was using AcuSense filtering for both Human and Vehicle on a single detection area. Your minimum needs to be narrower/shorter than a Human and your maximum wider than a wider/taller than a vehicle while also taking into account the minimum/maximum sizes at the point of trigger. I'd rather set up a separate zone for Human and Vehicle with separate minimum/maximum parameters for each OR use separate event types for each (intrusion for one, line crossing for the other). The ability to set separate minimum/maximum target sizes per detection area may/may not be available depending on where the event is being configured from.

If all else fails remove the camera, factory default it, re-install the firmware immediately after activation. Then set the camera up standalone without the NVR to prove detection works.

 

[DBUK]

I've not had issues with these cameras with regard to detection, but don't I dispute that some people have...

Is the camera correctly orientated for its view (if you stand in the centre of the field of view you should appear upright)? I see many cameras installed (incorrectly IMHO) partially rotated, so that a door or object at one side of the image appears level. Please post a screenshot of the camera view.

When setting up a camera for line crossing/intrusion detection I'd always:

• Configure the event from the NVR, if the camera is managed by an NVR. If additional options relating to the event setup are unavailable in the NVR interface (min/max on older firmwares, target validity etc), those parameters (and only those parameters) can be adjusted in the camera later.
• Start with detection set at the defaults. Sensitivity at 50 and no minimum/maximum set. Those minimum/maximum parameters can be set later to filter out false alerts.
• Minimum/maximum when set, need to be adjusted for the camera perspective. The minimum being slightly smaller than an object at the furthest point at which the trigger can take place, and the maximum slightly larger than an object at the nearest point to the camera at which a trigger could take place.
• Line crossing is more effective for targets moving across the line right/left, left/right, rather than toward or away from the camera.
• Both line crossing and intrusion detection will work better when not positioned to the edges of the view (target fully in view before crossing the line/entering the intrusion area)
• Personally I wouldn't be bothering with minimum/maximum parameters if I was using AcuSense filtering for both Human and Vehicle on a single detection area. Your minimum needs to be narrower/shorter than a Human and your maximum wider than a wider/taller than a vehicle while also taking into account the minimum/maximum sizes at the point of trigger. I'd rather set up a separate zone for Human and Vehicle with separate minimum/maximum parameters for each OR use separate event types for each (intrusion for one, line crossing for the other). The ability to set separate minimum/maximum target sizes per detection area may/may not be available depending on where the event is being configured from.

If all else fails remove the camera, factory default it, re-install the firmware immediately after activation. Then set the camera up standalone without the NVR to prove detection works.

Thanks for the above, ive not actually tried setting a detection zone for each specific target, ive got it currently set with the area drawn, min/max set, just one rule and both vehicle and human ticked, i will give that a go and see if there is any improvement.

The camera is orientated correctly, it would drive me nuts any other way, the camera is positioned on the side of the house around 1m from the front, 3m high, angled facing the driveway which is around 12m long, garage at the end, (rear of house), id post pics but it captures part of next doors drive which they may not want posting online, but id say its a very standard position and strange that the camera is ignoring practically everything (intermittently), the previous camera was in the same position for 4 years (DS-2CD2383G0-1) and didnt miss anything, which was set for both intrusion and motion, no acusense.