MOBOTIX v25 Network Camera Firmware 4.4.2.34 Download

Posted at November 2, 2024 by PCI-DB Team

MOBOTIX v25 Network Camera Firmware 4.4.2.34 Description

Enhancements and Improvements

Integration into Genetec Security Center

Starting with Security Center Release 5.6, Genetec supports and certifies MOBOTIX cameras with a firmware that implements the Genetec protocol. This is valid for all cameras of the x14/24 and x15/25 series starting with camera software MX-V4.4.2.34.

The following functions are supported by the Genetec system:
- RTSP Streaming
- MxPEG Codec
- M-JPEG Codec
- Virtual PTZ Functions
- Camera Multicast
- Events triggered MOBOTIX Video Motion Detection, microphone und signal input
- All other MOBOTIX events (as customized Genetec events)
- Digital signal inputs/outputs
- Audio IN/OUT

To set the Genetec-specific options (RTSP and Multicast), the Admin Menu > Camera Administration section has the new Integration Protocols dialog.

MxActivitySensor 2.0

This release contains an enhancement to the well-known MxActivitySensor. Using simple configuration steps for MxActivitySensor 2.0, you can make sure that only movements of persons or objects of specific sizes will trigger an event – regardless of their current position within the scene captured by the camera (using "three-dimensional perspective compensation"). Similar to video motion windows, you can draw rectangles in the image to specify the object size (for persons, for example) once near the camera and once farther away from the camera. Using these rectangles as reference objects, the video system determines whether or not the object size in conjunction with its current position actually match the size of the reference object. If the object in the example is smaller than a person standing at that position in the room, the camera does not trigger an event.

To activate MxActivitySensor 2.0, activate the corresponding option in the Setup Menu > Event Control > Event Overview > Image Analysis Events dialog in the MxActivitySensor 2.0 Settings section. When activating the Perspective Compensation option, you will see additional options for the minimum object sizes near the camera and farther way from the camera. For scenes with less depth, you can only set the Minimum Object Size to avoid events triggered by objects that are too small, such as animals, for example.

Remarks on activating MxActivitySensor 2.0:

- Applies to all MxActivitySensor profiles, i.e., it cannot be switched on or off for individual profiles.
- Using this option may reduce the maximum frame rate of the camera.

Hardware Support of MxMultiSense

The new software release MX-V4.4.2.34 is required if you want to connect the new MxMultiSense module to a camera. The MxMultiSense is an MxBus module with integrated environmental sensors for recognizing movements (PIR sensor), changes in illumination, temperature or noise level (sound sensor).

The MxMultiSense has the same body as an external image sensor module of a MOBOTIX camera and it is also installed in a wall or ceiling. The module uses a two-wire MxBus connection to a MOBOTIX device (camera, door station, MxDisplay). For communication with the attached MOBOTIX device, the module uses the MxMessageSystem. The module thus sends messages if one of the trigger values that can be set specifically for each sensor are reached. Upon receiving one of these messages, the camera can trigger events, which in turn trigger the actions defined in action profiles.

To activate an attached MxMultiSense module, open the Admin Menu > Hardware Configuration > Manage MxBus Modules dialog. The configuration of the MxMessageSystem messages for this module is accomplished by clicking on the MxMessageSystem Configuration button in the Service Functions section of the same dialog. For more information on the module, please see the product documentation (Quick Install) and the online help of the camera.

Other Improvements

Extended functionality of the MX-GPS-Box (via MxMessageSystem)
From software release MX-V4.4.2.34, you can use the integrated illumination and temperature sensors of an MX-GPS-Box to send MxMessages. The messages are sent if one of the specified values is reached; upon receiving the message, the camera will use it to execute the actions defined in the corresponding action profile. The configuration of the MxMessageSystem messages for each module is accomplished by clicking on the MxMessageSystem Configuration button in the Service Functions section of the Admin Menu > Hardware Configuration > Manage MxBus Modules dialog. Please refer to the camera's online help if you would like more information on this topic.

MxActivitySensor enhancements

For dark images with a high level of image noise, you can adjust the behavior of MxActivitySensor to reduce the number of false alarms. In the Setup Menu > Event Control > Event Overview > Image Analysis Events dialog, General MxActivitySensor Settings section, simply activate the Activate Image Noise Improvement option.

MxAnalytics enhancements

The behavior of MxAnalytics on cameras installed at higher positions (6 to 7 m/20 to 23 ft) and small detection areas has been improved.

Thermal TR measurement windows with additional information

The temperature measurement areas and the level meter of the Thermal TR event profiles of a Thermal TR camera (M15/S15) can now be displayed for each profile. To accomplish this, the two options Show Measurement Area and Show Thermal Radiometry Level Meter have been moved from the global settings to the profile-specific section of the Thermal Radiometry event type.

In addition, you can now use the new options Show Thermal Radiometry Level Meter and Show Thermal Radiometry Profile Name in the same section. This will display the current temperature and the profile name in the measurement windows, respectively. The "current" temperature in this context is the temperature value determined according to the selected comparison type and compared to the specified trigger threshold. This will facilitate setting sensible thresholds for triggering events if the temperature rises above or drops below the threshold.

Digest Authentication

Starting with this release, the camera supports Digest authentication for HTTP and HTTPS connections. Open the Admin Menu > Hardware Configuration > Web Server dialog and for the Authentication Method option, select either Auto, Basic or Digest. When using Auto, the camera automatically selects the proper method for the inbound http(s) request (Auto is the default setting).

Bugfixes

Using variables in the CGI path of a network message profile (IP Notify)
Using a variable (e.g., $(ID.FIP)) in a CGI path of a network message profile (IP Notify) only worked properly for profiles of the Text only type. When using one of the types without additional text, the camera did not correctly resolve the variables.

Online help for the "generate_reference_image" function

In the online help, this API function had been written as http://<IP>/control/rcontrol?action=generate_reference_image. This has been corrected to http://<IP>/admin/rcontrol?action=generate_reference_image.

Continuous recording in MxManagementCenter (MxMC)

Cameras added to MxManagementCenter sometimes showed alarms in the MxMC alarm list although the cameras were only recording continuously and had not been set up to generate alarms.

Thermal spotmeter in mirrored images

Using the Thermal Spotmeter event type in mirrored images resulted in faulty temperature values and – consequently – to faulty events.

Using MxActivitySensor on video streams from MxDigitizer

After activating MxActivitySensor for video streams generated by MxDigitizer, very dark scenes sometimes prompted continuous alarms of the sensor.

Thermal overlay with full-image recording

On Thermal cameras, the Thermal Overlay live display mode in combination with full-image recording and viewing Both Sensors sometimes resulted in a thermal part of the image that showed darker colors in the recording than in the Live view.

Known Limitations

Formatting an SD card with active recording in MxFFS archive
After formatting an SD card as primary storage target of the camera (e.g., after exchanging the SD card) in combination with an existing MxFFS archive, the camera will not show the highest event sequence number after rebooting without activated recording, but a 0. After activating recording, the camera shows the correct sequence number in the image.

Directly accessing SD cards with MxControlCenter

SD cards written by MOBOTIX cameras with software version 4.3.4.x or higher cannot be read directly on a computer running MxControlCenter (MxCC). Before you can read the SD cards, you need to delete the partition for storing the event log (64, 128 or 256 MB). This means that the new event logging for the MxManagementCenter histogram is not available any more. For more information, please send a message to your MOBOTIX Support team .

Use in MxEasy

In order to use cameras with this software release in MxEasy, you need to make sure beforehand that the configuration entry TLS_MIN_VERSION=SSL3 described for release MX-V4.4.0.31.r1 has been added to the configuration on these cameras. This applies to cameras that have already been integrated into MxEasy as well as to cameras found on the network using Bonjour (i.e., when starting MxEasy on a computer for the first time). Failing to do this will result in a crash of MxEasy.
As an alternative, you can open the Admin Menu > Network Setup > Web Server dialog and deactivate the HTTPS option on these cameras. After rebooting the cameras, you also need to deactivate the Secure connection (SSL) option in MxEasy for all corresponding cameras.

Translations

Currently, only the English and German translations of the camera's web browser interface are up-to-date.

About Network Camera Firmware:

Updating to a newer firmware version than the one already installed on your network camera can improve the device’s overall performance and stability, resolve various issues, and add support for newly developed features or enhance existing ones.

On the other hand, downgrading the camera’s firmware can recover its functionality in the unlikely event the currently installed version is faulty, or the device’s performance dropped after an upgrade. However, bear in mind that applying an earlier build might not always be possible.

Changing the camera’s firmware must be performed when the new release resolves an issue that your device has encountered or adds a new feature (or enhances an existing one) that could prove useful to you.

As for the installation method, the steps vary depending on the model you own, but basically, you must connect your camera via an Ethernet cable (username and password required), and use the downloadable file in the Firmware Update section to upgrade your device. Make sure you do not interrupt the installation process.

However, make sure you carefully read and understand the installation steps so that you don’t end up with a broken device. This process isn’t intended to be destructive, but still, it’s best to save all configurations before applying a different firmware.

That being said, if you consider that this firmware improves your device in any way, then hit the download button and get the desired version; if not, check our website as often as possible so that you don’t miss the update that will boost your camera’s performance. 

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related MOBOTIX Drivers