My Motion Sensor Triggers

Mikentosh2017

Getting the hang of it
Aug 5, 2017
116
15
Monterey County, USA
I’m not sure my trigger settings are correct for my single camera. Can someone peruse my 2 photos to see if I checked the correct boxes?
 

Attachments

  • BD550D29-3C6F-4730-9815-63B31A06CEF4.jpeg
    BD550D29-3C6F-4730-9815-63B31A06CEF4.jpeg
    3.1 MB · Views: 47
  • 66D6F468-8AA8-4D6F-8D1D-7C175A3360C7.jpeg
    66D6F468-8AA8-4D6F-8D1D-7C175A3360C7.jpeg
    3.6 MB · Views: 46
Uncheck the high definition box.

The yellow zones have to be much larger. The two around the car will almost never work, especially at night.

Change algorithm to simple at night. Edge Vector will miss a lot of the time at night with B/W images.

That field of view will be problematic trying to trigger for someone going to the driver side door.

These are not tripwires like in the camera GUI. Suggest a block of yellow for the area you want to trigger.

2 seconds is along time. Consider 1 second.

I would lower the contrast - I run most of mine at the min.

Make sure the FPS and iframes in the camera GUI match.
 
Also you might want to resolve which date/time display you want but not both, especially since they differ by 2 months and 2 hours, +/-.
I use the cam's overlay, direct to disk recording and NetTime time server to insure the cam's overlay is accurate.

When you log into the cam's webGUI to get the time/date pointed to the NetTime server I'd remove that "Amcrest" logo and "IPC" if it were me..
 
  • Like
Reactions: looney2ns
Uncheck the high definition box.

The yellow zones have to be much larger. The two around the car will almost never work, especially at night.

Change algorithm to simple at night. Edge Vector will miss a lot of the time at night with B/W images.

That field of view will be problematic trying to trigger for someone going to the driver side door.

These are not tripwires like in the camera GUI. Suggest a block of yellow for the area you want to trigger.

2 seconds is along time. Consider 1 second.

I would lower the contrast - I run most of mine at the min.

Make sure the FPS and iframes in the camera GUI match.
 

Attachments

  • 072B1648-37FF-4861-A567-2FB1E1DE0C2A.jpeg
    072B1648-37FF-4861-A567-2FB1E1DE0C2A.jpeg
    5.4 MB · Views: 13
  • D326B5D0-800A-4C65-821F-3D2A5758D680.jpeg
    D326B5D0-800A-4C65-821F-3D2A5758D680.jpeg
    6.8 MB · Views: 12
  • 2C2F074A-F73C-4CC1-AAE0-56FE598DF0F8.jpeg
    2C2F074A-F73C-4CC1-AAE0-56FE598DF0F8.jpeg
    6.2 MB · Views: 13
  • 5352EC43-57DE-488B-A211-F858E4F2B363.jpeg
    5352EC43-57DE-488B-A211-F858E4F2B363.jpeg
    3.2 MB · Views: 12
Also you might want to resolve which date/time display you want but not both, especially since they differ by 2 months and 2 hours, +/-.
I use the cam's overlay, direct to disk recording and NetTime time server to insure the cam's overlay is accurate.

When you log into the cam's webGUI to get the time/date pointed to the NetTime server I'd remove that "Amcrest" logo and "IPC" if it were me..
I found where I can sync the time with the PC. Is that what you meant?

I couldn’t find “NetTime”. I didn’t see where I can change the name.