MOBOTIX Release Notes

Important Information

• This version replaces the previously released MX-V9.1.1.7.
• These release notes apply to both the firmware and the app package.
• This firmware is provided as Beta software and may still contain issues.
• Update packages can be installed directly on the S1A-D camera.
• After updating the software, please double-check your configuration to ensure proper operation. Old configurations may no longer work under certain circumstances.

Feedback to MOBOTIX about the S1A-D camera

• Please use only the dedicated email address S1AD-Beta@mobotix.com. Note that feedback submitted through other channels will not be forwarded to the development team.
• The provided issue reporting template must be used. Missing essential information may hinder analysis and resolution.

New Features

• Support for the new camera model S1A-D.
• New dialog "Argus" in Admin Menu → Maintenance. The tool provides an overview of MOBOTIX IoT cameras on the local network. It is intended for small installations of up to ~50 cameras. For larger installations, please continue using MxManagementCenter.
• New dialog "Health Check" in Admin Menu → System Information. Previously only available via MxManagementCenter, you can now directly check the current system status on the camera. A simple traffic light system indicates when issues are detected in certain functional areas.
• Reworked "Exposure Settings" dialog. The camera modules on M1 and M2 are displayed in separate sections. For Day/Night modules, the "Night" profile can apply a different set of exposure settings for night use. The custom exposure windows have been redesigned and can now be enabled/disabled individually as tiles. The dialog has moved to the Admin area and is now available under Admin Menu → Hardware Configuration. Admin rights are required; please check your group policies.
• Improved MxActivitySensorONE app with a new model optimized for dual operation. Note: existing configurations are not compatible and the app must be fully reconfigured.
• Updated MxMessage structure of the MxActivitySensorONE app to MxActivitySensorONE.profile_summary.<YourProfileName>.<eventType>.<ClassName>. Note: existing message event configurations are no longer valid and must be adjusted.
  • e.g. MxActivitySensorONE.scene_summary.loitering.total → MxActivitySensorONE.profile_summary.loitering_profile.loitering.Total
  • e.g. MxActivitySensorONE.scene_summary.motionAI.total → MxActivitySensorONE.profile_summary.motion_profile.motionAI.Total
• New default message events for the MxActivitySensorONE app:
  • MotionAI_Person (MxActivitySensorONE.profile_summary.motion_profile.motionAI.Person)
  • MotionAI_Vehicle (MxActivitySensorONE.profile_summary.motion_profile.motionAI.Vehicle)
• New entry "Training Image" on the "Download Support Information" page. This feature allows you to provide a live image from your camera that can be used to further improve and train our AI models. By contributing real-world camera images, you actively help increase detection accuracy and optimize the future performance of MOBOTIX solutions.
• In Admin Menu → Ethernet Interface, IPv6 operation has been extended with the options SLAAC and DHCPv6.

Improvements and Bug Fixes

• Custom exposure windows are visualized correctly again.
• Image quality with WDR has been improved; in certain scenes the overall impression was brightened.

Restrictions and Known Issues

• The microphone is not functional in this release. An updated sensor cable is required.
• Smart Data Configuration does not automatically detect any source for the MxActivitySensorONE app.
• The S1A-D camera image currently differs from the M1A-S image.
• Buffered archiving may fail at night due to corrupted sequences (likely caused by high data rates from image noise).
• ONVIF recording playback skips entire MKV segments.
• The 3 m sensor cable is not supported by the S1A-D and may cause distorted colors in the live image.
• MxActivitySensorONE can cause image freeze and is not yet 100% stable.
• MxActivitySensorONE: changing profile names requires reconfiguring the message event.
• Online help pages for the new features are currently missing.