Hi,
yesterday I tested cam #1 (Vivothek IP8332-C) - everything worked correct: with 'modect' ZM is recording an event, when in front of the cam something comes in motion. When the motion stops - the recording stopped.
Today I tested the other cam (Vivothek FD8134V) ... 'modect' ... the recording does start, when motion does happen in front of the cam, but does not stop recording, when the motion stops. I first supposed a problem in the firmware of these cam ... I updated the firmware ... no change.
Then I tested with both cameras ... now both(!) cameras do not stop recording, when the motion in front of the cam stops.
What's wrong?
Thanks for hints (and sorry my English).
Centaurus17
Modect - no stop recording
-
- Posts: 47
- Joined: Fri Sep 06, 2013 7:44 am
- Location: Europe/Austria
Re: Modect - no stop recording
Did you linked the cameras? Try removing the link.
After more than 15 years, no longer using ZM as surveillance system.
Now in the dark side, using a commercial system...
-
- Posts: 47
- Joined: Fri Sep 06, 2013 7:44 am
- Location: Europe/Austria
Re: Modect - no stop recording
Hi Paco,
many thanks - you were some minutes quicker ... I wantet to post an update. After many hours of trial and error I found yesterday evening that there is a dependence to 'linked camera': I (several times) reremoved all cameras and started fresh (mostly with linked cameras) ... at the moment I have no camera 'linked' - and both are working (starting/stopping events) correct. I hope this will hold on when I add 2 additional cameras in some weeks.
Thanks again.
Regards,
Centaurus17
many thanks - you were some minutes quicker ... I wantet to post an update. After many hours of trial and error I found yesterday evening that there is a dependence to 'linked camera': I (several times) reremoved all cameras and started fresh (mostly with linked cameras) ... at the moment I have no camera 'linked' - and both are working (starting/stopping events) correct. I hope this will hold on when I add 2 additional cameras in some weeks.
Thanks again.
Regards,
Centaurus17