LiveView
The LiveView page provides real-time monitoring and is accessible via the "Setup menu" ➡️ "Setup". Alternatively, it can be accessed from the Ext software menu.
The Ext software menu includes options such as Live, Setup, Software management, Operation schedule, and Control log.
The LiveView interface displays detected fire and smoke events, showing zones with their respective percentages. For fire detection, specific zones (e.g., Zone1, Zone3, Zone44) are highlighted with their detection percentages and RGB color values. For smoke detection, zones (e.g., Zone1, Zone3) are shown with their grayscale values.
Example data shown:
- Fire: Zone1 4.54% (R: 231 G: 154 B: 77), Zone3 66.41% (R: 243 G: 196 B: 85), Zone44 14.08% (R: 243 G: 176 B: 91)
- Smoke: Zone1 19.02% (Grayscale: 58), Zone3 1.62% (Grayscale: 58)
Preferences
Application preferences can be configured on the "Configuration" and "Detection areas" pages of the application WebUI.
Configuration Settings
| Setting | Unit | Min | Default | Max | Description |
|---|---|---|---|---|---|
| Capture quality | Enum | 0 | 0 | max<=255 | List of capture modes (resolution and FPS) provided by camera. Used for thumbnail generation. Frames will be resized for AI model inference. Actual FPS can be lower. |
| LiveView framerate | FPS | 1 | 3 | 15 | LiveView page MJPEG stream FPS, does not affect inference speed. |
| Object detection on firmware | bool | False | True | True | Object detection using CV engine is always operating inside of the camera. By setting False (disabling function), more resources from CV engine will be available to be used by the extension software. Notice: When object detection is disabled, functions that use the object detection installed in the camera (such as some image quality automatic control functions and APIrivacy Guard) will be also disabled. |
Detection areas
This section allows for the configuration of detection zones.
Manipulating zone contours
- ?Add contour: Click and add vertices to the configuration frame. Complete the contour by clicking the first point. Zones can be added consecutively. A maximum of 8 zones and 16 vertices per zone are supported.
- ↩️Select contour: Click an existing contour; its line style will change to a dash.
- Clear: Delete the selected contour.
- All clear: Delete all contours.
Settings per zone
| Settings | Unit | Min | Default | Max | Description |
|---|---|---|---|---|---|
| Zone color | color | - | - | - | Zone colors are constant. |
| Enabled | bool | False | True | True | Only enabled zones will be processed. |
| Zone name | text | 1 char | Full Zone N | 20 chars | Used in alarms data and live view cards. Must contain only latin letters, digits, underscores, and spaces. |
| Fire alarm threshold | % | 0.01 | 0.5 | 100.0 | Threshold for fire detection, expressed as a percentage of a zone size. |
| Smoke alarm threshold | % | 0.01 | 0.5 | 100.0 | Threshold for smoke detection, expressed as a percentage of a zone size. |
| Fire alarm warm-up timer | ms | 0 | 5000 | 3600000 | Time interval before a fire alarm event is triggered after the first detection. |
| Smoke alarm warm-up timer | ms | 0 | 5000 | 3600000 | Time interval before a smoke alarm event is triggered after the first detection. |
| Fire alarm cooldown timer | ms | 0 | 30000 | 3600000 | Time to wait before initiating a new fire alarm. |
| Smoke alarm cooldown timer | ms | 0 | 30000 | 3600000 | Time to wait before initiating a new smoke alarm. |
| Fire alarm ID | Enum | 171 | 171 | 174 | Camera internal Alarm ID assigned for fire detection events. |
| Send fire test alarm | - | - | - | - | Used for alarm checks and demonstration purposes. |
| Smoke alarm ID | Enum | 171 | 172 | 174 | Camera internal Alarm ID assigned for smoke detection events. |
| Send smoke test alarm | - | - | - | - | Used for alarm checks and demonstration purposes. |
Additional notes
- In the event of simultaneous fire and smoke detection, the application will prioritize the fire event and send both events. However, due to camera cooldown limitations, only the fire alarm may be triggered.
- The application will reload if the camera's rotation setting is changed. Consequently, the LiveView page should also be reloaded.
- Enabled zones without contours are considered full-frame zones.
- The default zone serves as a fallback option when no zones have been enabled in the internal configuration.
License
License management can be accessed on the "License" WebUI page.
| Device blob | /54fhdcg4nGOsHdaz5HaVCz9YD31bQS8CHitQcCy6xU= |
| Status | Valid Expiry date: 31.10.2024 |
| License |
System linkage for VMS
Genetec Security Center with i-PRO Active Guard
i-PRO Active Guard server configuration:
- Edit the configuration file C:\MultiAl\Backup\3rdpartyApp.config on the PC where the Active Guard server is installed.
Key configuration parameters in the file include:
application_name_1 = "Noema Fire and Smoke Detection iPRO App"event_name_1 = "Fire detection"event_name_2 = "Smoke detection"- For Genetec systems, configure custom event IDs:
genetec_custom_event_id_1 = 12000andgenetec_custom_event_id_2 = 12001. Ensure any leading semicolons (;) are removed from these lines.
Integration Steps:
- Register cameras on the i-PRO Active Guard configuration web interface.
- Restart the i-PRO Active Guard Service.
- In the Genetec configuration tool:
- Create "Custom Event" entries, ensuring their values match the Active Guard server configuration (e.g., "Fire detection" with value 12000, "Smoke detection" with value 12001).
- (Optional) Create "Alarm" definitions and configure "Event-to-action" rules.
Visuals in the original document show screenshots of the file explorer, camera registration interface, Genetec config tool for custom events, and event-to-action configuration.
Milestone XProtect with i-PRO Active Guard
With i-PRO Active Guard server, alarm name, snapshot, and event detail information are displayed on the XProtect Alarm manager.
XProtect configuration:
- Create "Analytics Event" entries in the XProtect Management client. The event names must match the configured event names (e.g., "Fire detection", "Smoke detection").
- Create "Alarm definition" entries in the XProtect Management client, linking them to the appropriate analytics events.
Visuals in the original document show screenshots of the XProtect Management client for creating Analytics Events and Alarm Definitions.
Milestone XProtect without i-PRO Active Guard (with i-PRO Maximizer plug-in)
The i-PRO Maximizer plug-in allows for simple integration without an additional PC for the Active Guard server. In this setup, only the alarm name is shown on the XProtect Alarm manager.
Integration Steps:
- Run "Update alarm sending on all cameras" from [Rules and Events] – [i-PRO Extended Actions] in the Milestone XProtect Management Client.
- Verify that HTTP alarm notification is configured on the camera side under [Alarm] – [Notification] – [Notification] – [HTTP alarm notification] - [Address 1].
- Create "Custom Event Mapping" entries, mapping hexadecimal alarm IDs to tag names (e.g., "AB" for "Fire detection", "AC" for "Smoke detection").
- Create "Alarm definitions", selecting "i-PRO Maximizer Events" and "i-PRO Custom Event" for the triggering event.
Visuals in the original document show screenshots of the Milestone XProtect Management Client configuration, camera HTTP notification settings, and custom event mapping.
Video Insight with i-PRO Active Guard
No specific configuration is required for the Active Guard plug-in within Video Insight. The configured event name will appear in the "Extension app. event filter."
Visuals show a "Refine filters" dialog with "Fire Detection" and "Smoke Detection" options.
(Optional) Rule configuration on Video Insight:
By configuring the event name as "Category" within "Enhanced System Input", various Actions can be utilized.
Visuals show the "Enhanced System Input" configuration screen where "Category" can be set to "Fire Detection".
NVR/WV-ASM300 Configuration
Camera Configuration
Configure the NVR's IP address as the destination for notifications under [Alarm] – [Notification] – [Notification] – [TCP alarm notification] - [Destination of notifications].
Visuals show the NVR configuration interface with TCP alarm notification settings.
NVR Configuration
Extension software alarms must be configured on the NVR.
To notify WV-ASM300, configure its IP address via [Network] – [TCP alarm notification].
Visuals show the NVR configuration for extension software alarms, including a list of event names and their corresponding Message IDs (e.g., "Fire detection" with Message ID 176 / B0).
WV-ASM300 Configuration
Configure settings under [Setting] – [AI camera] – [Alarm name setting].
Ensure that the Name and Message ID are matched with the configured numbers.
