[SOLVED] Alarm will not clear on mdetect

[arad85]

Hi

I have installed ZM from the 1.25.0 VM link on the main web page. I am using a Foscam 8910 and everything "works" - I can get video, I can control the camera etc... I can even get events working - sort of.

I have defined the active region to be the whole of the camera, and the settings for the alarm :

Units: Percent
Alarm colour: 255/0/0
Alarm check: Blobs
Min/Max pixel threshold: 40/0
Filter width/height: 5/5
Zone area: greyed
Min/Max alarmed area: 16/0
Min/max filtered area: 12/0
Min/max blob area: 10/0
Min/Max blobs: 1/0
Overload frame ignore count: 0

If I restart zm, everything is fine - the system sits in an idle state until an alarm is triggered. The problem comes then - the alarm never stops even after the event has moved from the cameras frame. If I disable alarms, recording stops, but as soon as I enable them again (on the camera window) an alarm is triggered. Looking at the images, they all have a score of 50 and if I click on the statistics link it says: "There are no statistics recorded for this event/frame". If I reboot and manually force an alarm, the system recoreds, but even when I cancel the alarm, the system still thinks it is in an alarm state.

I have enabled debugging and captured the debug images. Unfortunately, as a new user, I can't post them, but they are mostly black with a few twinkling small areas - way under the min size. Any idea what is causing this?

[arad85]

As an update, it seems that 50 is being added to all scores after an event is detected.

Taking logs at +5 and grepping the log files I get:

Code: Select all

$ grep "Zone is" *log*
zm_debug.log.02742:06/16/13 13:47:34.177787 zma_m1[2742].DB3-zm_monitor.cpp/2768 [Zone is alarmed, zone score = 38]
zm_debug.log.02742:06/16/13 13:47:34.422059 zma_m1[2742].DB3-zm_monitor.cpp/2768 [Zone is alarmed, zone score = 36]
zm_debug.log.02742:06/16/13 13:47:34.621280 zma_m1[2742].DB3-zm_monitor.cpp/2768 [Zone is alarmed, zone score = 34]
zm_debug.log.02742:06/16/13 13:47:34.848943 zma_m1[2742].DB3-zm_monitor.cpp/2768 [Zone is alarmed, zone score = 31]

Whilst the frame view (click on the frame count link in the camera window) for the same time period shows:

Code: Select all

1	Normal	13:47:31	0.00	0
2	Normal	13:47:32	0.31	0
3	Normal	13:47:32	0.51	0
4	Normal	13:47:32	0.77	0
5	Normal	13:47:32	0.93	0
6	Normal	13:47:32	1.19	0
7	Normal	13:47:33	1.45	0
8	Normal	13:47:33	1.62	0
9	Normal	13:47:33	1.88	0
10	Normal	13:47:33	2.04	0
11	Alarm 	13:47:34	2.31	38
12	Alarm 	13:47:34	2.55	86
13	Alarm 	13:47:34	2.74	84
14	Alarm 	13:47:34	2.99	81
15	Alarm 	13:47:34	3.17	50
16	Alarm 	13:47:35	3.42	50
17	Alarm 	13:47:35	3.67	50
18	Alarm 	13:47:35	3.86	50
19	Alarm 	13:47:35	4.12	50
20	Alarm 	13:47:36	4.37	50
21	Alarm 	13:47:36	4.63	50
22	Alarm 	13:47:36	4.90	50
23	Alarm 	13:47:36	5.13	50
24	Alarm 	13:47:37	5.41	50
25	Alarm 	13:47:37	5.57	50

You can see that the alarm fires, the first score si correct, the following 3 scores are the alarm score +50 and then all subsequent frames are +50.

[arad85]

I had the camera linked to itself in Linked Monitors on the first page of the camera definition.

Deleting the whole monitor and starting from scratch was the simplest way I could find of removing the link.

[bb99]

Control left click should've worked also

[arad85]

For some reason, sometimes the link would show, but most times it wouldn't. Perhaps I screwed something up, but even with it unselected and it not showing, I was still getting alarms linked. Deleting and recreating only took 5 minutes (it was only a question of setting the camera and very simple zone parameters up).