MOBOTIX Q25M Network Camera Firmware 4.4.0.31-r1 Download

Posted at November 27, 2024 by PCI-DB Team

MOBOTIX Q25M Network Camera Firmware 4.4.0.31-r1 Description

Notes on Release MX-V4.4.0.31.r1:

The only difference between the current release 4.4.0.31.r1 and the predecessor release 4.4.0.31 is the added audio support of v25 models.

Event Logging for MxManagementCenter

Starting with this software release, the camera will log all events internally. This is used by MxManagementCenter (MxMC) to create a Histogram within the Playback view (available in MxMC 1.2 and higher).

Notes:

- The Event Logging option can be enabled or disabled in the Admin Menu > Storage on External File Server / Flash Device dialog. This feature is enabled by factory default.
- The event information in the log is stored on the SD card in the camera itself. To use this feature, however, the SD card needs to be formatted using a camera with software release 4.3.4.x or higher. If this is not the case, the activated event logging will generate error messages in the live image and in the system messages after rebooting. Make sure to reformat the SD card in order to use this feature.
- Note that the event logging feature works independently of the storage target used (SD card, SD card with MxFFS archiving, file server with folder structure).

New Web User Interface "MxWeb"

In addition to the current user interface in the web browser, you can activate the new MxWeb user interface. MxWeb allows accessing the camera's live image and the camera recordings. The new interface allows using the MxPEG codec for live images and recordings without requiring an additional plugin or a specific browser. MxWeb runs on all current versions of the commonly used web browsers (Firefox, Google Chrome, Edge, Safari) and – most importantly – it can be used on smartphones and tablets!

Notes on Activating and Using MxWeb:

- To activate MxWeb, the Admin Menu > Network Setup > Web Server dialog contains the new section MxWeb Settings. Using these parameters, you can activate and customize the MxWeb user interface.
- MxWeb is disabled by factory default.
- After activating MxWeb and rebooting the camera, you can start MxWeb by entering <IP address>:8080 (or the corresponding port) in the browser address bar.
- To set MxWeb as the default start page for the camera, open the Admin Menu > Language and Start Page dialog.
- When using Internet Explorer 11, make sure to deactivate the "compatibility mode".

Extended Thermal Features

- Thermal Image Overlay
On cameras with both a thermal and an optical image sensor, you can now opt to show the thermal image as an overlay image above the regular optical image. This allows to show "hotspots" of the thermal image on top of the regular image, for example. To activate the overlay image, you can click on the Camera Selection quick control above the live image and select Thermal Overlay as a value. To customize the corresponding parameters, you can open the Setup Menu > Image Control > Thermal Sensor Settings dialog and modify the settings in the Thermal Overlay section. Please refer to the camera's online help if you would like more information on the Thermal Sensor Settings topic.

- Expanded Thermal-TR features
For the calibrated Thermal-TR sensors for temperature measurement, you can now manually adjust the temperature compensation. This provides the means to adjust the temperature measurement to the environmental conditions of the current scene and to achieve more precise values. To configure this, the Setup Menu > Image Control > Thermal Sensor Settings dialog contains the Manual Temperature Adjustment parameter.

Once you have activated this option, three new parameters appear: Object Emissivity, Atmospheric Transmission and Environmental Temperature.

- MxActivitySensor settings for thermal images
Especially for thermal images, the MxActivitySensor feature has been extended by a new Difference Threshold of Thermal Sensor parameter. This option can be activated in the Setup Menu > Event Control > Event Overview > Image Analysis Events dialog. By increasing the threshold value for this option, you can lower the sensitivity of MxActivitySensor for thermal images in order to avoid false alarms.

Other Improvements

- Setting the lens carrier type for D15 cameras
This release supports the use of the new Panorama lens carriers for D15 camera bodies. For this purpose, the Admin Menu > Hardware Configuration > Image Sensor Confguration dialog has the new Lens Carrier Type option. Once you have selected the proper value (Double Lens Carrier PAN/180), you need to store the settings, reboot the camera and reset the image settings to the factory defaults (e.g., by using the Manage Settings > Load Image Factory Defaults). In the process, you should also reset all views. Next, you can activate the OnScreen Control to properly configure the Panorama dual image of a D15 Panorama camera and to store the settings.

- MxActivitySensor visualization
When using MxActivitySensor events, you can now also show the position of a recognized movement in the image. This option can be activated in the Setup Menu > Event Control > Event Overview > Image Analysis Events dialog by activating the Show Live Position Indicator option.

- New alarm type for Behavioral Detection
For events of the Behavioral Detection type, you can now select the Restricted Area alarm type. This parameter allows settings a rectangular area in the camera image, which triggers an alarm if an object enters the area. This option can be configured in the Setup Menu > Event Control > Event Overview > Image Analysis Events dialog.

- MxPEG sensitivity
In the Setup Menu > Image Control > JPEG Settings dialog, the new MxPEG High Sensitivity Mode will prompt the camera to better detect small image changes in special situations. This will prevent "tile artifacts" from appearing in the image. Using this option may reduce the frame rate. This feature is disabled by factory default.

- LED Security Mode
The Admin Menu > Camera Administration > LED Setup dialog now has a new value Security Mode for the LED Main Switch parameter. When in Security Mode, the green LED (LED 1 on D14/D15 cameras) mainly shows the arming status and live image access while the red LED (LED 2 on D14/D15 cameras) shows the status of the recordings:
Green LED (LED 1 on D14/D15 cameras)
The LED is on permanently if the camera is not armed. If the camera is armed, the LED is off and briefly flashes every 2 seconds. Upon detecting an event, the LED will light up for 3 seconds. If the live image of the camera is accessed, it is on permanently and briefly goes off every 2 seconds.
Red LED (LED 2 on D14/D15 cameras)
This LED is on permanently if the camera is recording. If the MxFFS archive is synchronized, this LED is on permanently and briefly goes off every 2 seconds. If the camera is ready for recording, the LED is off and briefly flashes every 2 seconds.

- SSL settings for MxEasy and more restrictive encryption
For integrating cameras in MxEasy via the HTTPS protocol, this release now allows using the older SSLv3 encryption method supported by MxEasy. This is done by adding the following section to the camera configuration:
SECTION httpd
ENABLE_SSL=1
TLS_MIN_VERSION=SSL3
ENDSECTION httpd

Caution:

If the configuration section SECTION httpd is already present, simply add the highlighted entries to the section.

In order to integrate the camera into more restrictive network environments (e.g., if older, less secure encryption methods are discovered by "vulnerability scans"), you can use the method above to set the most secure TLS V1.1 protocol as the minimum. This is done by adding the TLS_MIN_VERSION=TLS1_1 entry.

- Portmap service
The portmap service (Port 111 TCP and UDP) is now started only when needed, e.g., when accessing an NFS file server.

Bugfixes

- MxPEG ActiveX component did not allow HTTPS connections in IE 8/IE 11 and did not show an event after changing the audio status
When using the ActiveX components contained in release 4.3.4.83, it was not possible to connect to cameras via the HTTPS protocol in IE 8 and IE 11. In the versions prior to release V4.3.4.83, playing back recordings via the ActiveX component sometimes stopped when using HTTPS connections. In addition, when activating/deactivating audio output in the ActiveX component, no event was triggered internally within the component. In order to resolve these issues, this release contains new versions of the ActiveX components (V1.7.8.0 for Windows 32 Bit and V1.8.8.0 for Windows 64 Bit).

- Hemispheric 6MP full images not round and partially clipped
When showing hemispheric full images of a 6MP image sensor, it sometimes happened that the camera did not show the entire full image (full circle), but that parts of the image at the left and the right were black.

- Configuration of the Panorama image of a D15 Panorama
Certain configuration settings of the camera led to a situation where the D15 Panorama did not show a live image after entering the display mode for configuring the dual image.

- "Illumination" event for high Lux values
When configuring events of the Illumination type, it was only possible to set trigger values of up to approx. 1000 Lux. Using higher values did not trigger the event, even if the illumination exceeded the specified value.

- Counting corridors in MxAnalytics
When using counting corridors in MxAnalytics, the camera sometimes counted objects for both directions although the object only had passed a corridor in one direction.

- Heatmap in MxAnalytics reports on 6MP cameras
Heatmaps within MxAnalytics reports were shown with the wrong aspect ratio on 6MP cameras and did not fill the entire image.

- Temperature values displayed on Thermal-TR cameras
On some Thermal-TR cameras, the $(SEN.TTR.CELSIUS) variable showed inaccurate values or showed a max. value of 175°C although the actual temperatures were higher.

- Using RFID transponders for MxMessageSystem messages
With some RFID transponders, the UID of the transponder could not be used for sending messages via the MxMessageSystem; the transponder did not trigger a message.

- Defining access times on a door station using MxDisplay
When defining weekly programs with access times for a door station on an MxDisplay, the MxDisplay sometimes showed different times than the times actually defined on the door station. To correct this behavior, you need to install the current software release on the camera and an MxDisplay release V2.0.0.22 or higher.

- vPTZ and SIP client as remote station of a door station
When using a SIP client (e.g., Grandstream VoIP/SIP phone) as remote station for a door station, it was not possible to deactivate the virtual PTZ (vPTZ) on this camera. This option was active again after every reboot of the camera.

Known Limitations

- MxMessageSystem message in MxBus modules
Currently, the maximum number of messages that can be used per MxBus module in the Admin Menu > MxMessageSystem > Message Configuration of MxBus Modules is limited. Depending on the MxBus module and the type of information in the messages, at max. between 3 and 8 different messages can be defined. If this limit is exceeded for an MxBus module in the afore-mentioned dialog, the MxBus module indicates an error status by the left LED alternately flashing red and blue after setting and storing the dialog values. The superfluous messages defined in the dialog will not be sent or evaluated in this status.

- Behavioral detection – restricted area
When using restricted areas in a distortion-corrected live image or when defining such an area by means of a polygon in the configuration dialog, the borders outside of the restricted areas may produce false alarms.

- Direct access to SD cards from MxControlCenter
SD cards that have been formatted using a software release 4.3.4.x or higher cannot be read directly on a computer running MxControlCenter (MxCC). To be able to do so, you need to delete the additional partition for storing the event log (with sizes of 64, 128 or 256 MB). This means that the event histogram is not available any more in MxManagementCenter.

- 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 above 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