Recent content by doodles

Thanks for the replies guys. Yup, it seems the RJ45 plugs I had laying around were rated for both stranded and solid so I just went with it and it seems to be holding fine (for now). That's not a bad idea if going for a keystone jack approach, but it seems to be holding with a stranded rated...

Hi guys, I'm having to replace a water damaged rj45 poe connector on a hiki camera and was wondering how best to proceed. I've seen @fenderman @nayr and @alastairstevenson help a lot with discovering pinout, but is there a consensus on which style end it would best to terminate with...

Looks like the TP link and V7 are the strongest contenders. But V7 MPEGS24-1N is now priced at $399.00, are you sure it was the 24 port model listed at $122? Also, how are the noise levels on the fan? The TL-SG1016PE is now listed at $119.00 which isn't bad, but how has it held up? Fan whine...

It was never enabled in BI to begin with, hmm. I use bicommand, and there was an issue with it and my global schedule as a result of a registry conflict. Perhaps it's the same issue here and I just need a clean install, which is bizarre as I've already deleted the cam (although used the same name).

It's not selected in any profiles, only the normal "Motion sensor" (first check box) is selected. Thanks again

Latest 4.4.2. Yes all zones are cleared, I already deleted and reconfigured the cam from scratch to further ensure that. But, I didn't think to check cam's OEM UI. While motion detection is not enabled, this "linkage" setting is enabled: I'll try disabling and see what happens, thanks guys.

I think we're describing the same thing, this is my current config and it's still activating: How it's still getting triggered and recording, I have no idea. Thoughts?

You mean if there are 0 green marked zones? Yes, even without green marked zones it's triggering. I thought you need to mark the areas of interest in order for anything to trigger?

Thanks for the suggestion, but it didn't seem to help. I still get tons of false alerts for passing cars outside the green mask. I've clear the mask entirely and re-drew, even deleted the entire cam and re-did all configs for it. But it's just constant alerts of cars outside the masked area...

Thanks for the reply. It's always a possibility, but I've never had this many false positives when there are virtually no clouds/shadows present. Will keep fiddling with it I suppose. Thanks, I see what you're saying but I was viewing those clips when the exact profile that triggered it...

I used it be in version 4.0.X.X had everything configured, updated a few weeks ago to 4.4.X.X. Motion capture operating normally in marked areas (green brush) in 4.0, but now after a few weeks with 4.4 I'm convinced either I've configured it horribly wrong or it's bugging on me. First I started...

Thanks. Guess that explains it as I do use BICommand. Odd my other cams weren't affected though as they are configured similarly.

Didn't want to reconfigure, but it was the only option. I even tried import the .reg of that single cam, and restoring it caused the same issue. Suppose something got corrupted. Doesn't look like there are slightly old iterations of BI available, just some legacy versions. Anyhow...

I just tried importing and old known working backup (.reg) and it still is stuck on profile 3. Really scratching my head at this, should I just reinstall or am I missing something?

So, I just updated to version 4.4 and one of my cams is refusing to follow global schedule, and is stuck on one profile (#3). See the title here: I checked the per camera settings and override global schedule is not checked. Even when I do check it to see if I can get it to change, it refuses...