MrCourtney

Thanks for the post. That worked for me!

Anyone here have experience with HIKvision's in-camera line detection? I have two of my bazillion cameras watching the front. One is pointed from the front of the house to the street and the other looks back toward the front door. Both are for general security and protect my wife's car which she parks in the driveway. Both cameras are Hikvision DS-2CD2032-I 3MP Bullets. Need some help please: I got a lot of palm trees around my house. They all make humongous shadows on the driveway during the day. Big ones that move a lot. To keep BI from triggering into insanity I have the minimum object size cranked way up. I'm not comfortable with that. The DS-2CD2032-I has intrusion detection settings internal to the camera. I want to use the line crossing detection in the Events section. Will this trigger BI? If not, how would it show? Sorry, I'm lost on this and any help from someone doing it would be appreciated.

eed some advice for a bricked HUACAM HCV712. When I first started putting in my camera system I bought Huacam because they were cheap. I believe they are Grandstream knockoffs. You get what you pay for and all but two have been replaced with HIKvision. The last two should be here in a couple of weeks. Meanwhile one has gotten itself bricked. Not the most important security camera but I'd still like to have it working. Symptoms: I can not access the camera with a browser or the Huacan IP search or config program. An IP Search program does not show the camera. It's getting POE because the camera is warm but I have no way to access it. Before I take it apart - does anyone know if there's a reset button inside? Any tricks to finding what IP it's on, if that's possible. Thanks for the help.

The latest Blue Iris update has introduced a problem in my Win 7 system: The CPU utilization reports 0% constantly. BI support says they've had a couple of reports of this but not enough to chase it down. Several hours before the update, I installed the Windows Update security fixes and we've had some discussion on whether that might have contributed. Both the update and fixes were installed on 3/12/15. Again the CPU reporting problem showed on the same date. Anyone else having this problem? I'll pass on to BI support. Thanks.