MOBOTIX T25M Network Camera Firmware 4.4.1.56 Download

Posted at November 21, 2024 by PCI-DB Team

MOBOTIX T25M Network Camera Firmware 4.4.1.56 Description

Notes on Release MX-V4.4.1.56:

The only difference between the current release 4.4.1.56 and its predecessor release 4.4.1.55 is a bugfix for door stations, which did not execute specific functions after updating to release 4.4.1.55

Highlights:

- Improved colors in Lowlight situations < 1 Lux for cameras with 5MP and 6MP color image sensors.
- Hardware support for the MxDigitzer to integrate analog cameras with S15D/M cameras, including all MOBOTIX features.
- Brings extended features for cameras with thermal sensors with TR technology.
- Includes numerous other improvements.

Enhancements and Improvements

Improved Image Quality in Lowlight Situations (< 1 Lux)
This release brings perceptibly better colors for all 5MP and 6MP cameras with color image sensors in Lowlight situations below one Lux.

Hardware Support of MxDigitizer

This release supports the new MxDigitizer, which provides for easy integration of analog cameras into a MOBOTIX system. The analog cameras are attached to a MOBOTIX S15D/S15M via the MOBOTIX MxDigitizer just like a regular sensor module. Besides delivering digitized images from an analog video source, you can use all other MOBOTIX features, such as MxActivitySensor, event storage on the camera and the well-known event logic. Open the Admin Menu > Hardware Configuration > Image Sensor Configuration dialog to activate an MxDigitizer as a sensor module attached to an S15D or S15M.
- S15D
For an S15D, make a choice on where you want to show the analog camera (right or left image), then select the external port (Cam1 or Cam2) to which you attached the MxDigitizer.
- S15M
You can show either the integrated image sensor or the MxDigitizer attached to Cam1 or Cam2.

Make sure to select MxDigitizer as sensor type for the video input you are using.

Enhancements for Thermal Cameras

- Reference windows
When using a MOBOTIX thermal camera M15/S15 with TR technology (TR = thermal radiometry), you can now compare the temperature in the measurement window with the average temperature of a reference window and then use the result to trigger an event. The reference window should then point to an image area that has a constant temperature (such as a black radiator set to 55 °C/131 °F). Compared to using absolute temperature measurements, the reference method provides a much better accuracy (50 mK) if you want to trigger events based on specific temperature values, especially in scenarios where temperatures change often and the values vary in a wide range. To use this new mode, open the Setup Menu > Image Control > Event Overview > Environment Events dialog and activate the Reference Temperature measurement mode. Activating this mode will show additional options for defining a reference window.

- Temperature Measurement Window With Level Meter
On thermal cameras M15/S15 with TR technology (thermal radiometry), you can set a temperature that triggers an alarm when the measured temperature exceeds or drops below the value. The new level meter can be shown in the live image to see the difference between the specified trigger value and the temperature of the measurement window. To see the level meter for TR profiles, open the Setup Menu > Image Control > Event Overview > Environment Events dialog and activate the Level Meter option.

Other Improvements

- SIP client settings for remote controlling also available for door station cameras
In the Admin Menu > Audio and VoIP Telephony > SIP Client Settings dialog in Expert Configuration mode, the Remote Control Settings are now also available on door stations. This is where you can define the signal output functions that are triggered when pressing the DTMF keys 1 to 3.

- API command "event.jpg" for downloading an MXG clip
After executing the API command <IP address>/control/event.jpg?output=mxg to download an MXG clip of the latest event, the camera now stores the file named sequence-<sequence number>.mxg. Every stored clip now has a unique name with the correct file name extension, which facilitates further processing of these files.

Bugfixes

- Door stations after updating to release MX-V4.4.1.55:
On door stations with several attached MxBus modules and activated MxMessageSystem, some functions (such as ringing the doorbell and opening the door) sometimes did not work reliably any more after updating the software to release 4.4.1.55.
- Messages of the MxMessageSystem in MxBus modules
The maximum number of messages that could be used in the Admin Menu > MxMessageSystem > Message Configuration of MxBus Modules dialog for one module was lower than the specified number of 32 per module. When defining more messages, the corresponding MxBus module reported an error and the module neither sent nor evaluated these messages. It is now possible to use up to 32 messages per MxBus module.
- Door station – Keypad bell button after rebooting the camera
After rebooting a door station, the first use of the Keypad bell button did not trigger a call to the intercom at the other end. After that, the bell button worked as expected.
- MX-DoorMaster LED
After opening the door using the MX-DoorMaster key, the blue LED sometimes did not stop flashing.
- 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.
- Behavioral detection – "U-Turn" alarm type
When using MxAnalytics and events of the Behavioral Detection type, the U-Turn alarm type continued to produce false alarms.
- MxAnalytics Heatmap Reports with IE 11
When exporting an MxAnalytics heatmap report using Internet Explorer 11, the export sometimes failed.
- Polygon window of MxActivitySensor
After defining an Activity Sensor window as polygon, the AS sensor values in a displayed graph did not show.
- Image switching and FTP profiles on Day/Night cameras with low trigger value
On Day/Night cameras with low trigger values (<= 1 Lux), the cameras continued to show images and transfer FTP images from the color sensor instead of the black&white sensor even though the illumination dropped below the specified value. 
- Full image recording and network message
When sending event information using a transfer profile (network message (IP Notify), E-Mail, FTP) as a reaction to an event with active full image recording, the attached information (e.g., the $(FPR.ENO) variable) sometimes did not show data from the current event, but from the preceding one.
- 802.1x authentication
When using an 802.1x server with the EAP-MD5 method for authenticating network devices, the authentication sometimes failed.

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