Release Notes for MOBOTIX Camera Software

Document Information

Contents

These Release Notes contain a technical description of the most important changes in the software for the MOBOTIX network cameras.

Software Releases—Overview:

Notes:

• Please download the stable customer releases of the software from http://www.mobotix.com in the Support > Download Center > Software Downloads section.
• Please note that some of the described features in the dialogs will only be visible if the More button at the bottom of a dialog has been pressed.
• Please send an email to intl-support@mobotix.com for feedback.

top

Software Release MX-V4.4.2.73 − for MOBOTIX Camera Models D24M, M24M, Q24M, T24M, D14Di, S14, V14D, i25, c25, p25, v25, D25M, M25M, Q25M, T25M, D15Di, M15, M15-Thermal, S15 and V15D with Thermal Sensors and 6MP, 5MP, 3MP and 1MP Image Sensors

Creation Date: 2017-10-09

Publishing Date: 2017-11-14

Enhancements and Improvements

Support of MxBell Push Notifications

This release places special emphasis on door stations that are used together with the MOBOTIX MxBell app for Android and iOS as door station intercom. After adding a door station in MxBell, you can activate the signaling of someone ringing the doorbell using push notifications. If someone presses a doorbell defined in the door station, the door station sends a push notification to MxBell. Opening MxBell (and thus opening an audio connection to the door station) will acknowledge the push notification and will stop the ringing sound at the door station. In addition, MxBell can show the door station's live image and you can open the door.

Bugfixes

• Thermal TR cameras show temperature values above 2,000 °C.
  On rare occasions, Thermal-TR cameras showed temperature values above 2,000 °C.
• Preview Option in faststream CGI
  When calling the /control/faststream.jpg?... CGI with the preview option and an image size (size), the CGI generated images with the wrong scaling factors for some sizes.

Known Limitations

• Login to MxWeb
  Some web browsers (e.g., Edge) will only show the live image after logging in when you manually reload the page. In Internet Explorer 11, the live page will not show even after reloading the page.
• 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 formatted by MOBOTIX cameras with software version 4.3.4.x or higher cannot be read directly on a computer running MxControlCenter (MxCC) in older releases up to and including 2.5.4.2. 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 (support@mobotix.com).
• 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.

top

Software-Release MX-V4.4.2.69 − for MOBOTIX Camera Models D24M, M24M, Q24M, T24M, D14Di, S14, V14D, i25, c25, p25, v25, D25M, M25M, Q25M, T25M, D15Di, M15, M15-Thermal, S15 and V15D with Thermal Sensors and 6MP, 5MP, 3MP and 1MP Image Sensors

Creation Date: 2017-07-20

Publishing Date: 2017-07-31

Enhancements and Improvements

Event Stream Group Right for Integrating Cameras into MxManagementCenter

To integrate a MOBOTIX camera into MxManagementCenter (MxMC), you had to use the access credentials of a user with admin rights on the camera.

This software release provides a better solution: In the Admin Menu > Security > Group Access Control Lists, you can now add a new group with the new Event Stream right. If you are using the credentials of such a user to integrate the camera into MxMC, you can use all features of MxMC (except updating the camera software). In addition, the user cannot make any configuration changes in the browser-based user interface of the camera.

Separating the rights in such a manner has significantly increased the system security, especially where larger installations are concerned.

Enhanced Security Thanks to Special Characters in Passwords

Firmware release MX-V4.4.2.69 allows using special characters to create more complex passwords (Admin Menu > Security > Users and Passwords). This again increases the protection against unwanted camera access. To prevent problems when logging in from different browsers, all printable special characters from the US ASCII character set are allowed:
! " # $ % & ' ( ) * +, −. /:; < = >? @ [ \ ] ^ _ `{ | } ~.

Other Improvements

• Support for FTPS (FTP over TLS)
  When transferring data via FTP profiles, FTP servers can now be used which support the more secure FTPS protocol (FTP via TLS). Once the connection is established, the camera automatically logs the protocol used with the FTP server. TLS 1.0 to TLS 1.2 are supported and the most recent version, TLS 1.2, is the preferred version.
• Improvement to Intrusion Detection
  When attempting to connect an IP address that is blocked by intrusion detection, the error message "404 not found" can now be returned by the camera instead of the standard error message "403 forbidden". For that purpose the following entry must be inserted in the camera configuration file:
  SECTION httpd
ids_http_403_to_404=1
ENDSECTION httpd
• Update of the OpenVPN-Client to version 2.4.3
  This version provides, among other things, improved protection against DoS and memory overflow attacks.
• Extension of the Online Help for SD card Replacement when MxFFS-Archiving is being used
  The camera-internal online help for the dialog Admin Menu > Storage > Storage on External File Server / Flash Device has been supplemented by the section "Exchanging Flash Devices with Activated MxFFS Archiving". The steps and the correct sequence for exchanging the SD card in connection with MxFFS archiving are described in detail. Correct execution is important to prevent subsequent archiving errors.
• Expansion of the File Server Test
  When one presses the Test button in the Admin Menu > Storage > Storage on External File Server / Flash Device dialog, the available memory space on the defined file server is now additionally checked and compared with the set memory size.
  Note:  Currently, in the above dialog, after the Test button is clicked, a success message is also displayed even though an error is shown in the Fileserver Test Log window after checking the storage space.
  
• MxWeb Player now also without Admin Privileges
  The use of the MxWeb player is now also possible by users in a non-admin group with the new right "Event Stream" (see "Event Stream Group Right for Integrating Cameras into MxManagementCenter" above).
• Variables for Indicating the Speed of Movement
  The variables which indicate the current movement speed when a GPS box is connected can now be supplemented with the desired unit rate type:
• $(SEN.GVE) = $(SEN.GVE.MPS): Speed in [m/s]
• $(SEN.GVE.KMH): Speed in [km/h]
• $(SEN.GVE.MPH): Speed in [mile/h]
• $(SEN.GVE.KNOT): Speed in knots]
• Lock of vPTZ actions
  Deactivating vPTZ actions in the Setup > Image Control > vPTZ Settings dialog now also prevents the accidental triggering of vPTZ actions (for example, by pressing the # 2 key) when controlling the camera via VoIP / SIP.
• MxMessageSystem extension for KeypadRFID
  A message with the type function code can now be defined for a connected KeypadRFID module in the Admin menu > MxMessageSystem > Message Configuration for MxBus Modules in the Keypad section. Such a message is sent when a number is entered followed by one of the buttons "Key", "Mail", "Bell" or "OK". As a parameter, the message is then sent with a string consisting of the entered number, followed by one of the following key identifiers/characters:
• K: Key button
• M: Mailbox button
• B: Bell button
• E: ESC button
• O: OK button

Bugfixes

• Use of SD cards 64GB and larger
  In the case of large SD cards (64 GB or more), incorrect CRC errors were sometimes reported in the System Messages after a camera restart.
• Admin dialogs after changing the language
  After setting French or Italian as language in the browser-based user interface, the dialogs Admin Menu > Storage > Storage on External File Server / Flash Device and Admin Menu > Camera Administration -> Time & Date dialog showed some wrong contents.
• Profile for Network Messages and Full Image Recording
  When using profiles for network notifications (IP-Notify) with event images in combination with Full Image Recording, the IP Notify message was not sent if the triggering event of such a profile did not simultaneously trigger recording.
• Image Logo Upload
  Automated uploading of logos via web server URLs did not work properly in some cases.
• Thermal TR cameras with temperature values ​​above 2000° C
  A Thermal TR camera could, in rare cases, display a temperature of more than 2000 ° C.
• Incorrect Triggering of Temperature Events
  Image errors could sometimes lead to incorrect triggering of temperature events on TR-Thermal cameras.
• MxWeb Player
  Certain dates were not accepted when entering a search time in the Player view of MxWeb.
• Faulty Configuration and Camera Restart
  In very rare cases, the internal configuration data of the camera could be faulty and the camera then would not allow a software reboot.
• Online help for Variables $SEN.VM1, $SEN.VM2
  The description of the two variables, $SEN.VM1 and $SEN.VM2, in the camera-internal online help was incorrect.
• Incorrect Logging of VoIP Service
  The System Messages contained log entries for starting and terminating VOIP and SIP services even when the services were not activated.

Known Limitations

• Login using MxWeb
  After entering the login data, the live image of the camera only visible in some web browsers (e.g., Edge) until refreshing the web page. In Internet Explorer 11, the live image does not display at all.
• 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 (support@mobotix.com).
• 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.

top

Software-Release MX-V4.4.2.51.r1 − for MOBOTIX Camera Models D24M, M24M, Q24M, T24M, D14Di, S14, V14D, i25, c25, p25, v25, D25M, M25M, Q25M, T25M, D15Di, M15, M15-Thermal, S15 and V15D with Thermal Sensors and 6MP, 5MP, 3MP and 1MP Image Sensors

Creation Date: 2017-03-14

Publishing Date: 2017-03-24

Enhancements and Improvements

Support of the New MX-Proximity-Box

The MX-Proximity-Box is a compact, weatherproof interface box (IP66) with integrated radar sensor technology that can be attached to all cameras with MxBus interface. This interface box emits radar waves and detects moving objects using the reflections of these radar waves. It is even possible to install the MX-Proximity-Box behind drywalls, glass or plastic covers and up to 100 m/110 yd away from a camera. The box is thus a meaningful addition to the passive infrared sensors (PIR) of a D15, M15 and ExtIO.

One technical finesse is the ability of the MX-Proximity-Box to differentiate between different types of movements before sending a message using the MxMessageSystem. Persons are detectable up to distances of 15 m/50 ft, cars up to 35 m/115 ft. The box can differentiate between approaching objects, leaving objects and general movements. To configure these options, you can define corresponding message names in the Admin Menu > MxMessageSystem > Message Configuration of the MxBus Modules dialog, then use these names to define the corresponding profiles for sending messages if the box recognizes one of the types of movement. For further information, please see the online help topic of the dialog.

Other Improvements

• Improvements of MxActivitySensor 2.0 for optical and thermal image sensors
  For MxActivitySensor 2.0, the Activate Image Noise Improvement option that improves darker images with high image noise is now always active. Consequently, this option has been removed from the Setup Menu > Event Control > Event Overview > Image Analysis Events dialog. In addition, the trigger behavior of MxActivitySensor2.0 has been improved in very dark scenes.
• Image Analysis Events
  By factory default, new image analysis events use the MxActivitySensor instead of the video motion detection (VM).
• Portuguese language
  In the Admin Menu, you can now set the user interface language to pt for Portuguese. This means that there are a total of 10 supported languages: English, German, Chinese, French, Italian, Japanese, Portuguese, Russian, Spanish, and Turkish.

Bugfixes

• Showing M-JPEG streams in third-party software
  When showing a camera live stream in M-JPEG format (using the faststream API) in third-party software (e.g., NETAVIS), the images sometimes showed gray tiles if the bandwidth was too low.
• RTSP server
  When activating the RTSP server in the Admin Menu > Camera Administration > Integration Protocols dialog, the explanatory text for the URL to use in the dialog showed a wrong IP address.
• Genetec integration – T24/T25
  When using T24/T25 door stations, you could not configure the video motion detection (VM) in Genetec Security Center.

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 (support@mobotix.com).
• 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.

top

Software Release MX-V4.4.2.34 − for MOBOTIX Camera Models D24M, M24M, Q24M, T24M, D14Di, S14, V14D, i25, c25, p25, v25, D25M, M25M, Q25M, T25M, D15Di, M15, M15-Thermal, S15 and V15D with Thermal Sensors and 6MP, 5MP, 3MP and 1MP Image Sensors

Creation Date: 2016-12-22

Publishing Date: 2016-12-23

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 (support@mobotix.com).
• 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.

top

Software Release MX-V4.4.1.56 − for MOBOTIX Camera Models D24M, M24M, Q24M, T24M, D14Di, S14, V14D, i25, c25, p25, v25, D25M, M25M, Q25M, T25M, D15Di, M15, M15-Thermal, S15 and V15D with Thermal Sensors and 6MP, 5MP, 3MP and 1MP Image Sensors

Creation Date: 2016-12-07 (V4.4.1.55: 2016-11-11)

Publishing Date: 2016-12-12 (V4.4.1.55: 2016-11-18)

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. For more information, please send a message to your MOBOTIX Support team (support@mobotix.com).
• 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.

top

Software Release MX-V4.4.0.31.r1 − for MOBOTIX Cameras D24M, M24M, Q24M, T24M, D14Di, S14, V14D, i25, c25, p25, v25, D25M, M25M, Q25M, T25M, D15Di, M15, M15-Thermal, S15 and V15D with Thermal Sensors and 6MP, 5MP, 3MP and 1MP Image Sensors

Creation Date: 2016-07-19 (V4.4.0.31: 2016-04-05)

Publishing Date: 2016-07-26 (V4.4.0.31: 2016-04-18)

Enhancements and Improvements

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

For additional information on this topic, see the Additional Information > MxWeb Interface online help page.

Support of the New v25 Camera Model

The software release also runs on the new v25 camera model. The v25 is the new, versatile MOBOTIX dome camera for installation on ceilings for indoor applications. It has a 6MP image sensor and can be ordered as Day or Night variant with lenses from B036 to B237 (103°x77° to 15°x11° angles of view). Starting with software release 4.4.0.31.r1, you can activate audio on this model (microphone and speaker). This is required if you want to use the audio components of the v25 On-Wall Kit with Audio.

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. For detailed information on these parameters and their effects, please read the camera's online help and the corresponding Compact Guide in the www.mobotix.com/other/Support/MX-Media-Library/Compact-Guides section of the MOBOTIX website (available soon).

• 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. If you need more information on this issue, please contact MOBOTIX support (support@mobotix.com).
• 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.

top

Software Release MX-V4.3.4.83 – for MOBOTIX Cameras D24M, M24M, Q24M, T24M, D14Di, S14, V14D, D25M, i25, c25, p25, M25M, Q25M, T25M, D15Di, M15, S15 and V15D with 5MP/6MP Image or Thermal Sensors

Creation Date: 2015-12-01

Publishing Date: 2015-12-08

Enhancements and Improvements

Unified Firmware MX-V4.3.4.83 for all MOBOTIX Cameras with PXA 320 Processor

Supports all D24M, M24M, Q24M, T24M, D14Di, S14, V14D, D25M, M25M, Q25M, T25M, i25, c25, p25, D15Di, M15, M15-Thermal, S15 and V15D camera models. This includes all camera models with PXA 320 processor ("P3") and thermal, 6MP, 5MP, 3MP and 1MP image sensors.

Other Improvements

• Supports the new Thermal Sensor Modules TR, also when combined with an optical 5MP sensor module (cameras S15 with Thermal Sensor Module TR and M15-Thermal TR).
• Supports the Thermal Spotmeter feature, also when combined with an optical 5MP sensor module (cameras S15 with Thermal Sensor Module and M15-Thermal, both with and without TR technology).
• MxAnalytics including behavioral detection event type now also for c25, Q25 and S15M with 5MP image sensors (with hemispherical lens and when mounted to the ceiling).
• Extended recording time including audio of the scenery before the event: The Pre-Alarm Time has been extended from 5 to 15 seconds.

Known Limitations

• Use in MxEasy
  In order to use cameras with this software release in MxEasy, you need to make sure beforehand that the HTTPS option in the Admin Menu > Network Configuration > Web Server dialog has been deactivated 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 deactivate the HTTPS option on the cameras will terminate MxEasy. After deactivating the option and 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.

top

Software Release MX-V4.3.4.66 − for MOBOTIX Camera Models D25, M25, Q25, T25, c25, i25, p25, D15, M15, M15-Thermal, S15 and V15 with 6MP Image Sensors or Thermal Sensors

Creation Date: 2015-09-10

Publishing Date: 2015-09-15

Enhancements and Improvements

Support of All P3 Camera Models With 6MP Image Sensors or Thermal Sensors (Single-Lens and Dual-Lens Models)

This software release supports all camera models with the new, more light-sensitive 6MP image sensor and/or thermal sensors, i.e., the camera models D25, M25, Q25, T25, i25, c25, p25, D15, M15, M15-Thermal, S15 and V15. For these camera models, the maximum image size for each sensor is 3072x2048 pixels (6MP, aspect ratio 3:2).

Note: If you intend to use 5MP image sensors on an M15, D15 or S15 camera that is currently running this software release, you need to downgrade the camera to the newest software release 4.3.2.77 for 5MP cameras.

Extended Features for Cameras with Thermal Sensors

The newest thermal cameras and S15 thermal sensors with TR technology (TR = thermal radiometry) can measure temperature values in the entire image area and can react accordingly. For this, the software now has a new event type, which is specifically used for alerting if temperature changes in the image are detected. Note that an additional event type for thermal cameras has been added, which can be used for thermal modules without TR technology.

Support of Thermal Cameras and S15 Modules with Thermal Radiometry (TR)

In order to support the TR technology, this software release introduces the new Thermal Radiometry event type. Using corresponding event profiles, you can define up to 20 different measurement windows within the image area. You can then set a minimum range and a temperature trigger value. The event will be triggered either when the temperature drops below or when it exceeds the trigger value. In this context, the minimum range specifies the number of pixels in which the temperature values exceeds or drops below the trigger value in order to trigger an event. This new event type is configured in the Environment Events section in the Setup Menu > Event Control > Event Overview dialog.

In order to determine the proper trigger value, you can use the new variables $(SEN.TTR.CELSIUS) and $(SEN.TTR.FAHRENHEIT). If comparison has been set to trigger when the temperature exceeds the specified value, the variable shows the lowest temperature of the hottest pixels within the minimum range in the measurement window. If comparison has been configured to trigger when the temperature drops below the specified value, the variable shows the highest temperature of the coldest pixels within the minimum range in the measurement window. Note that using the level meter to display the trigger value as a graph can also help in finding the proper trigger value.

"Thermal Spotmeter" Event for all Thermal Cameras/Sensors

All cameras with thermal sensors, i.e., including those without thermal radiometry, now allow measuring the temperature in a "spot" of 2x2 pixels in the image center. The cameras can create an alert when dropping below or exceeding the specified trigger value. The new Thermal Spotmeter event type is also configured in the Environment Events section of the Setup Menu > Event Control > Event Overview dialog. To determine the trigger value, you can use the variables $(SEN.TSR.CELSIUS) and $(SEN.TSR.FAHRENHEIT) for the right sensor or $(SEN.TSL.CELSIUS) and $(SEN.TSL.FAHRENHEIT) for the left sensor to display the current temperature value.

For additional information about the two new event types, see the Online Help of the camera.

Other Improvements

• Distortion Correction of Non-Hemispheric Lenses
  Just like before for B036 (L20,103°) and B041 (L22, 90°) lenses, you can now have the camera correct the slight image distortion of the B061 (L32, 60°), B079 (L43, 45°) and B119 (L65, 31°) lenses. This is done by activating the Lens Correction display mode.

  Note: When correcting the distortion of L20/22 lenses, the visible image section has changed slightly compared to the previous software release. In order to get the same image as before the software update, you need to slightly zoom into the image.

• Frame Rate for "Normal" Image Quality
  When compared to the previous software release, this release reaches higher frame rates for Normal image quality. This applies specifically to the image sizes from SVGA (800x600) to MEGA (1280x960).

Bugfixes

• Auto configuration with several door stations
  When running the auto configuration on systems with several attached door stations, not all Keypad/BellRFID modules entered the mode for entering the Super PIN. In this case, the configuration had to be completed using the camera dialogs.
• Display of attached door openers
  When integrating cameras into MxManagementCenter, MxDisplay or the MOBOTIX App, the process sometimes detected a door opener although there weren't any door openers attached.
• MxAnalytics Counting Corridors
  If counting corridors were being used, the positions of the displayed corridors sometimes did not precisely match the defined positions.
• Date and time in MxAnalytics reports
  The selection boxes for creating MxAnalytics reports (heatmaps and counting corridors) did not contain the local camera times, but the local time of the computer (based on its time zone settings) on which the browser had been started. If the camera and the computer were using different time zone settings, the camera returned faulty results. The selection boxes now contain only values that are based on the local camera time.
• Behavioral Detection and Corridors
  When using Behavioral Detection together with an empty corridor list, the camera did not visualize and evaluate the defined corridors, but only the last corridors specified in a list.
• Camera models i25 and c25 with audio package
  On the 6MP camera models i25 and c25 with audio package (i.e., with integrated microphone and speaker), it was not possible to activate the microphone.

Known Limitations

• Door Station Auto Configuration
  After restarting the camera and then running the "Auto Configuration" using a door station's bell button, the automatic configuration does not execute all required configuration steps. If you want to open the door and switch the lights, you need to manually configure the Door Release Actuator and Lights parameters in the Admin Menu > Hardware Configuration > Assign Wires dialog accordingly after running the auto configuration. In addition, you will need to manually create the door station events ("Ring", "Wrong PIN", "Door open", etc) in the Setup Menu > Event Overview dialog.
• Behavioral Detection
  The behavioral detection sometimes produces false events if illumination changes rapidly or on dark image areas (e.g., a dark carpet).
• Exposure windows and vPTZ actions
  When explicitly defining windows for exposure control on a camera and using vPTZ actions so that only very little of the defined exposure windows are visible in the image (<2%), exposure control can fail and sometimes even produces completely white images. This applies especially for the 6MP image sensor with image quality program set to "Fast".
• Use in MxEasy
  In order to use cameras with this software release in MxEasy, you need to make sure beforehand that the HTTPS option in the Admin Menu > Network Configuration > Web Server dialog has been deactivated 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 deactivate the HTTPS option on the cameras will terminate MxEasy. After deactivating the option and 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.

top

Software Release MX-V4.3.4.50 − for MOBOTIX Camera Models D25, M25, Q25, S15M, T25, c25, i25, p25 with 6MP Image Sensor

Creation Date: 2015-07-21

Publishing Date: 2015-07-23

Enhancements and Improvements

Support of All P3 Camera Models with Integrated 6MP Image Sensor

This software release supports all P3 camera models with the new, more light-sensitive 6MP image sensor, i.e., the camera models D25, M25, Q25, S15M, T25, i25, c25, p25 with 6MP image sensor. For these camera models, the maximum image size is 3072x2048 pixels (aspect ratio 3:2). The camera models c25, i25 and p25 are available in an audio variant with integrated microphone and speaker; the regular variants do not have any audio functionality.

Image Analysis Events from MxAnalytics Results (Behavioral Detection)

The image analysis events now feature a new type, the "behavioral analysis". This means that you can use the results from the "MxAnalytics" image analysis toolbox to directly trigger events. The following list briefly presents the most important features and the corresponding settings:

• Supported cameras:
  Behavioral detection is available on the Q25, S15M and c25 with a hemispherical lens (B016/L10) when mounted to the ceiling.
• Detectable Movements:
  Using the behavioral detection, the camera can trigger events when detecting the following types of movement in the image (the so-called "alarm types"):
  • Corridor: Walking through the defined counting corridor.
  • Duration of Stay: Permanent detection of an object in the area/image that stays there longer than the specified time span.
  • Opposite Direction: An object moves against the defined main direction.
  • Turn: An object changes its direction from 45° to 134°.
  • U-Turn: An object changes its direction from 135° to 180°.
  • Speed: An object moves faster than the specified speed.
• Configuration of the behavioral detection:
  To configure the behavioral detection, see the Image Analysis events section of the Setup Menu > Event Control > Event Overview dialog. This section allows adding the new "Behavioral Detection" type. For this purpose, the event profiles now have an additional "behavioral detection" type. When configuring such a profile, you can select one of the "alarm types" listed above and set other parameters as required.

Important: You can also use behavioral detection without having to activate MxAnalytics (in the General MxAnalytics Settings dialog). Note that neither the heatmap nor other elements unused by behavioral detection are displayed and there is no storage of MxAnalytics results on the SD card. In such a case, MxAnalytics automatically works "in the background".

For detailed information on this topic, please see the camera's online help of the dialogs or read the Compact Guide – MxAnalytics, which is available in the Support > MX Media Library > Compact Guides section of the MOBOTIX website.

Enhancements of the MxMessageSystem

The MxMessageSystem area has seen many enhancements; the following list describes the most important ones.

• Calling the remote station upon receiving a message
  Cameras with door station functionality allow placing a call to the configured remote station (MxDisplay, MxApp, MxMC) when receiving a message. Open the Admin Menu > Video Door Station > Bell Behavior and Video Mailbox dialog to configure this feature.
• Messages triggered by RFID events
  The KeypadRFID and BellRFID modules now allow triggering a message when presenting an RFID card. Open the Admin Menu > Hardware Configuration > Manage MxBus Modules dialog to configure this feature.
• Message with parameters
  
  • All messages from the MX-GPS-Box contain the sensor values as parameters (illumination, temperature, ...).
  • Messages from MxBus modules with signal inputs include their current status as parameter, BellRFID modules include their key status in the messages.
• Exchanging messages between cameras
  The distribution of messages between cameras in the current network now uses two different mechanisms that are configured in the Admin Menu > MxMessageSystem > Network Distribution of Messages dialog:
  • Best Effort Broadcast: Allows sending broadcast messages to any number of cameras and their attached modules. Note that this requires synchronized clocks on the cameras (max two seconds difference allowed). Otherwise, message reception is not reliable.
  • Reliable Multicast: Allows sending messages to up to 32 cameras; message reception is reliable even if the cameras do not use synchronized time.
• Definable message range
  You can set a distribution range for the messages generated by MxBus modules. The following settings are available:
  • Global messages are sent via Ethernet to any number of cameras and their attached modules.
  • Local messages are sent from one MxBus module to all other modules on the same MxBus and the attached camera, but not any farther.
  • Internal messages are sent to all other modules on the same MxBus, but are invisible to the attached camera.
  Caution: this range can only be configured for modules. Messages sent by the camera are always global.

For detailed information on this topic, please see the camera's online help of the dialogs or read the Technical Note – MxMessageSystem, which is available in the Support > MX Media Library > Compact Guides section of the MOBOTIX website.

Other Improvements

• Image quality for 5MP and 6MP resolutions
  Compared to the predecessor versions, the image quality for the two largest image sizes 5MP (2592x1944 pixels) and 6MP (3072x2048 pixels) has been improved perceptibly.
• Event-controlled application of image profiles in the live image
  As a reaction to an event, you can now activate image profiles in the triggered actions. For example, when the camera detects an MxActivitySensor event in the displayed thermal image, the camera can switch to the live image of the second (optical) image sensor and store that image. To be able to do so, the action groups in the Action Group Overview dialog have been expanded to include the defined image profiles. If required, you can also activate the selected image profiles for a limited time only.
• Image profiles with improved quality
  When generating an image using an image profile, the quality of that image depends on the selected image quality of the current live image. The additional Best Quality parameter in the Admin Menu > Transfer Profiles > Image Profiles dialog now allows generating images from image profiles with the best possible quality, independent of the current live image.
  CAUTION: Using this parameter may result in a brief reduction of the live frame rate while the camera generates the image from the image profile.
• "Assign Wires" dialog
  In the Admin Menu > Hardware Configuration > Assign Wires dialog, the identifiers of the selectable input types for the signal inputs of the door sensor and the door lock sensor have been revised.
• Focusing aid with audio
  The volume for the audio support of the focusing aid has been increased.

Bugfixes

• MxFFS archive − exchanging an SD card
  If MxFFS archiving had been activated and the SD card was exchanged (e.g., because of a corrupt SD card), the camera sometimes was unable to access the data stored in the archive. This led to a situation where the recording sequences started with sequence 0.
• Signal output of the BellRFID module
  When using a BellRFID signal output together with a timer, a closed signal output sometimes did not open after the specified time, but stayed closed. The signal output only opened after being triggered again.
• Connection to NTP time servers
  After rebooting the camera, it sometimes failed to reconnect to the specified NTP time servers.
• False alarms of Video Motion (VM) windows in darkness
  In very dark scenes and with relatively short exposure times (e.g., 1/30 sec), the camera sometimes continued to produce false VM events.
• Content length using HTTP API call to get a preview image
  The returned value for the content length of the "needlength" parameter of a preview image was sometimes faulty. Example for such a call:
  http://<IP address>/control/faststream.jpg?needlength&stream=full&fps=0&size=320x240&preview
• Audio from MxDisplay to the camera
  When talking to a door station/camera from MxDisplay, the MxDisplay sometimes produced audible cracking noises.
• GPS values for longitude and latitude
  The GPS coordinates returned using the $(SEN.GPS) variable were sometimes faulty.

Known Limitations

• Behavioral Detection
  The behavioral detection sometimes produces false events if illumination changes rapidly or on dark image areas (e.g., a dark carpet).
• Exposure windows and vPTZ actions
  When explicitly defining windows for exposure control on a camera and using vPTZ actions so that only very little of the defined exposure windows are visible in the image (<2%), exposure control can fail and sometimes even produces completely white images. This applies especially for the 6MP image sensor with image quality program set to "Fast".
• Use in MxEasy
  In order to use cameras with this software release in MxEasy, you need to make sure beforehand that the HTTPS option in the Admin Menu > Network Configuration > Web Server dialog has been deactivated 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 deactivate the HTTPS option in the cameras will terminate MxEasy. After deactivating the option and 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.

top

Software Release MX-V4.3.2.77 - for MOBOTIX Cameras D24M, M24M, Q24M, T24M, D14Di, S14, V14D, D25M, M25M, Q25M, T25M, i25, c25, D15Di, M15, M15-Thermal, S15 and V15D

Creation Date: 2015-06-25

Publishing Date: 2015-06-30

Enhancements and Improvements

Support of the New MX-Bus-IO-Module

Thanks to the new MX-Bus-IO-Module, the i25 and c25 camera models can use two signal inputs, two signal outputs (potential-free or 12 V self-powered) and MxBus modules. The module is to be wired fully before it is plugged onto the powered-off camera's mainboard. After finishing the installation and starting the camera, the module is recognized automatically and listed in the Camera Status dialog in the System section.

You can immediately use the signal inputs to define signal event profiles in Setup Menu > Event Overview. Likewise, you can immediately use the signal outputs to define signal output profiles in Admin Menu > Hardware Configuration > Signal Out Profiles. In addition, the signal inputs and outputs are automatically listed in the Admin Menu > Assign Wires dialog so you can use them immediately for door and light features. Input 1 is assigned to the door sensor, Input 2 to the lock sensor, Output 1 is assigned to the door opener and Output 2 to a light switch.

If you want to use one or both signal outputs not as potential-free outputs, but as self-powered 12 V outputs, you set this mode for the desired outputs in the Admin Menu > Hardware Configuration > Manage Hardware Expansions dialog, MxBus/IO Board section.

Improvements for Integrating into MxManagementCenter

This software includes many improvements that facilitate the integration into MxManagementCenter.

Bugfixes

• Playback of Recordings in MxManagementCenter via the Camera
  When playing back recordings in MxManagementCenter via the camera, issues occurred and time searches were not positioned properly, if recordings had been searched for single images or when playing back single images with a specified (fixed) interval.
  In addition, reverse playback of event recordings sometimes did not work properly.

Known Limitations

• Display of windows on D15D-180° models
  After defining windows for exposure control, video motion detection (VM) or MxActivitySensor (AS), the windows appear slightly offset in the "Full Image" display mode. This only applies to the window display – the windows are detecting at the correct positions. The other display modes ("Panorama", "Standard") are showing the windows at the correct positions.
• Exposure windows and vPTZ actions on 5MP and 6MP image sensors
  When explicitly defining windows for exposure control on a camera and using vPTZ actions so that only very little of the defined exposure windows are visible in the image (<2%), exposure control can fail and sometimes even produces completely white images. This applies especially for the 6MP image sensor with image quality program set to "Fast".
• Translations
  Currently, only the English and German translations of the camera's web browser interface are up-to-date.

top

Software Release MX-V4.3.2.72 - for MOBOTIX Cameras D24M, M24M, Q24M, T24M, D14Di, S14, V14D, D25M, M25M, Q25M, T25M, i25, c25, D15Di, M15, M15-Thermal, S15 and V15D

Creation Date: 2015-06-01

Publishing Date: 2015-06-03

Enhancements and Improvements

Support of MOBOTIX MxManagementCenter

This software release supports the new MOBOTIX MxManagementCenter – a completely newly developed video management system for Windows and Macintosh systems. MxManagementCenter is a video management software with a focus on simple and intuitive user interaction. Full screen display of a camera via mouse click, multi-monitor support, a clear representation of events and alarms, the control of door stations as well as the execution of many actions by "drag&drop" are just some examples of the many program functions.

Other Improvements

• "Playback has Priority" Option
  This new parameter in the Setup Menu > General Image Settings dialog replaces the old parameter named Limit Frame Rate When Idle in the same dialog. This option controls the camera behavior when playing back recordings via the camera. This is the case, if you are using MxManagementCenter for browsing the recordings, for example. If activated, it automatically reduces the frame rate of live streams in order to reduce processor load and to guarantee smooth video display when playing back recordings. Depending on the selected value, the recording frame rate will be reduced not at all or only for pre-event images (to 2 frames/s). Please refer to the camera's online help if you would like more information on this topic.

Bugfixes

• Camera audio not available any more
  When often opening the Admin Menu > Speaker and Microphone dialog and making changes, it sometimes happened that you could not hear the sound from the camera microphone. Likewise, the recordings did not contain the audio track.

Known Limitations

• Display of windows on D15D-180° models
  After defining windows for exposure control, video motion detection (VM) or MxActivitySensor (AS), the windows appear slightly offset in the "Full Image" display mode. This only applies to the window display – the windows are detecting at the correct positions. The other display modes ("Panorama", "Standard") are showing the windows at the correct positions.
• Exposure windows and vPTZ actions on 5MP and 6MP image sensors
  When explicitly defining windows for exposure control on a camera and using vPTZ actions so that only very little of the defined exposure windows are visible in the image (<2%), exposure control can fail and sometimes even produces completely white images. This applies especially for the 6MP image sensor with image quality program set to "Fast".
• Translations
  Currently, only the English and German translations of the camera's web browser interface are up-to-date.

top

Software Release MX-V4.3.2.68 - for MOBOTIX Cameras D24M, M24M, Q24M, T24M, D14Di, S14, V14D, D25M, M25M, Q25M, T25M, i25, c25, D15Di, M15, M15-Thermal, S15 and V15D

Creation Date: 2015-04-30

Publishing Date: 2015-05-05

Enhancements and Improvements

Support of All P3 Camera Models With Thermal, 6MP, 5MP, 3MP and 1MP Image Sensors as well as the New C25 Camera Model

This software release supports all P3 camera models with Thermal, 6MP, 5MP, 3MP and 1MP image sensors. On D15Di, M15D, S15D and V15D cameras with 6MP image sensors, the maximum image size is 3072x2048 pixels (aspect ratio 3:2).

The software release also runs on the new hemispheric c25 camera model. The c25 is the smallest and most light-weight hemispheric MOBOTIX camera for installing in ceilings of indoor applications. It has a 5MP image sensor and can be ordered as Day or Night variant with either an L12 lens (180° x 160° angles of view) or an L23 (92° x 68° angles of view).

"MxAnalytics" Image Analysis Tools Available on All x25M and S15M Camera Models

This software release contains the MxAnalytics image analysis tools also for the D25M, M25M, Q25M, T25M, i25, c25 and S15M camera models with all supported lenses. Using these tools, you can detect, display and log objects that are moving in the direction that is specified by freely definable areas, the so-called "counting corridors", just like on Q25M camera models. In addition, you can use the so-called "heatmaps" to detect, analyze, display and evaluate the distribution of objects in the image. The function, configuration and use of MxAnalytics has not changed from release 4.3.2.45 for the Q25M. Note that you need to address the lens-related differences in image areas and the resulting object sizes in the camera images when configuring this feature.

Several KeypadRFID and MX-DoorMaster Modules Allowed in One System

Using this software release, you can use MxBus to connect more than one KeypadRFID and MX-DoorMaster MxBus module to an IP Video Door Station. Make sure to respect the constraints when setting up such a system, e.g., the max. power requirement of all attached MxBus modules. For more information, please see the Technical Note – MxMessageSystem in the Support > MX Media Library > Compact Guides section of the MOBOTIX website. The additional modules attached via MxBus are controlled and configured using the new MxMessageSystem. For example, you can define a special PIN in the MxMessageSystem configuration; entering that PIN at the KeypadRFID will send a specific message. The addressed MX-DoorMaster can react to this message and opens the attached door opener.

Other Improvements

• Improved Audio Using Echo Cancellation by AGC
  The audio quality with activated echo cancellation (default on door station cameras) has been further improved. If echo cancellation has been activated, the camera automatically adds the "Auto Gain Control" (AGC) to help maintain the same volume in the recordings. The AGC adjusts the amplification level based on the set volume, the microphone sensitivity and the ambient noise level. Moreover, the echo is reduced even better.
• Improved white balance
  For both 6MP and 5MP image sensors, an improved automatic white balance has been implemented, which is also the factory default for these sensors, Automatic WB (Extended). The new algorithm is better at correcting the influence of colored light (below 4000K), which means that white or gray surfaces actually appear white or gray even if warm light is used.
• MxFFS archive larger than 4 TBytes
  When setting the maximum size of an MxFFS archive in the browser-based user interface of the camera, the size is not limited to 4 TB any more. In addition, the maximum physical size of the single archive files has been increased from 1 to 2 GB.
• EXIF header with local time
  When adding the jpegcomment_exif_time=cameratime line to the imageimprover section of the camera configuration, the camera will write the local camera time to the EXIF headers of JPEG images instead of the UTC time.
• Limiting the frame rate when idle
  By default, the camera reduces the frame rate if no live stream is requested, i.e., when idling. During these idle times, pre-alarms are now recorded using 2 fps instead of the 1 fps before.

Bugfixes

• SIP calls via Cisco Call Manager 9
  Inbound calls to a camera via a Cisco Call Manager 9 were sometimes not answered by the camera. This happened every time a call to the camera had been canceled before the camera had received any video data.
• Pattern in 5MP black&white image
  When using very short exposure times, the 5MP black&white image sensors sometimes showed stripes in the images.
• Reading MxFFS recordings from Flash media directly in the computer using MxControlCenter
  It was not possible to use a computer with installed MxControlCenter to read Flash storage media (SD cards, USB sticks, SSDs), which had been formatted and used for MxFFS storage using a software release higher than V4.1.10.28 and lower than V4.3.2.45.
• Video Motion windows (VM) on Thermal cameras
  After defining a video motion window (VM) on a Thermal camera and subsequently changing the image size, the window was shifted slightly to the right/left.
• Exposure window weighting for white balance of 5MP image sensors - online help
  For 5MP image sensors, it is only possible to use the exposure windows for white balance control either entirely ("100%") or not at all ("Total"). The online help of the camera has been corrected accordingly.
• Recordings without audio or with high image rates and audio
  In case the camera microphone had been deactivated and audio for recording had been activated, recorded M0000i files sometimes had single frames with faulty header entries. Trying to play back these recordings with MxControlCenter or MxEasy sometimes led to problems. On rare occasions, the same effect appeared in recordings with high image rates (>20 fps) and audio stream (i.e., the microphone had been activated).
• Door station – access using PIN
  After changing the access information on the MxDisplay (e.g., training RFID cards or activating combined access identification), it will take up to three minutes until the PIN/combined access can be used to gain access.
• Door stations with BellRFID module and/or bell buttons
  On door station systems with connected BellRFID module or other bell buttons, the bell buttons sometimes did not work properly after changing the connectors using the Admin Menu > Hardware Configuration > Assign Wires dialog or after updating the door station camera's firmware.

Known Limitations

• Display of windows on D15D-180° models
  After defining windows for exposure control, video motion detection (VM) or MxActivitySensor (AS), the windows appear slightly offset in the "Full Image" display mode. This only applies to the window display – the windows are detecting at the correct positions. The other display modes ("Panorama", "Standard") are showing the windows at the correct positions.
• Exposure windows and vPTZ actions on 5MP and 6MP image sensors
  When explicitly defining windows for exposure control on a camera and using vPTZ actions so that only very little of the defined exposure windows are visible in the image (<2%), exposure control can fail and sometimes even produces completely white images. This applies especially for the 6MP image sensor with image quality program set to "Fast".
• Translations
  Currently, only the English and German translations of the camera's web browser interface are up-to-date.

top

Software Release MX-V4.3.2.53 – only for MOBOTIX D15Di, M15D, M15D-Thermal, S15D and V15D Cameras

Creation Date: 2015-03-13

Publishing Date: 2015-03-17

Enhancements and Improvements

Support of the New Lens Units/Sensor Modules with 6MP Moonlight Technology

This software is the first release to support the new 6MP lens units and sensor modules for the D15Di, M15D, S15D and V15D camera models. The new 6MP image sensor delivers a maximum resolution of 3072x2048 pixels and has a noticeably higher light sensitivity than the 5MP sensor.

Support of MX-Input-Box and MX-Output-Box

As in the predecessor version V4.3.0.15, this version allows attaching MX-Input-Boxes as MxBus modules and integrating them using the MxMessageSystem. In addition, this version also supports the new MX-Output-Box as an MxBus module. This module adds up to eight signal/switching outputs to the camera and is also integrated using the MxMessageSystem.

Other Improvements

• Improvements from V4.3.2.45
  This version contains the same Other Improvements as release V4.3.2.45, which had been released only for Q25M and i25 cameras.
• Improved white balance
  For the 6MP sensors, an improved automatic white balance has been implemented, which is also the factory default for these sensors, Automatic WB (Extended). The new algorithm is better at correcting the influence of colored light (below 4000K), which means that white or gray surfaces actually appear white or gray even if warm light is used.

Bugfixes

• Bugfixes from V4.3.2.45
  This version contains the same Bugfixes as in release V4.3.2.45, which had been released only for Q25M and i25 cameras.
• Day/Night switching
  If the Day/Night switch had been activated in an M15D or S15D, the switching sometimes did not work properly and the camera continued to use the color/black&white sensor that was being used at the time. This happened although the camera should have switched to the other image sensor due to the change in lighting.
• Full Image recording for thermal cameras
  While recording full images on thermal cameras, the camera sometimes only showed one half of the thermal image.
• MxMessageSystem − swapped messages
  When using several MxBus modules on one camera with the MxMessageSystem, the camera sometimes swapped single messages when receiving/sending the messages. This happened after configuring the messages without rebooting the camera afterwards.

Known Limitations

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

top

Software Release MX-V4.3.2.45 – only for MOBOTIX Q25M and i25 Camera Models

Creation Date: 2015-02-23

Publishing Date: 2015-02-26

Enhancements and Improvements

Redesigned "MxAnalytics" Image Analysis Tools Available for Q25M Cameras

This software release contains the redesigned MxAnalytics image analysis tools for Q25M models. Using these tools, you can detect, display and log objects that are moving in the direction that is specified by freely definable areas, the so-called "counting corridors". In addition, you can use the so-called "heatmaps" to detect, analyze, display and evaluate the distribution of objects in the image. The results are stored continuously on the camera's integrated SD card; they can be evaluated, displayed or exported for further analysis later on. To do so, the camera uses "report profiles", which define the type of evaluation, the time range covered by the report and the result file, e.g. "how many objects entered corridor 1 within the last month".

In order to configure the image analysis, the Setup Menu of the camera contains the new MxAnalytics Control section with the following dialogs:

• General MxAnalytics Settings
  Use this dialog to activate and configure the MxAnalytics settings, such as all parameters for object recognition and how to display the results in the camera's live image. In addition, you can define the required counting corridors and set the parameters for the heatmap. Note that you can use all colors available on the MOBOTIX camera to differentiate between the different of object display types.
• MxAnalytics Overview
  Both the counting corridor report profiles and the heatmap report profiles (see next two items) can be evaluated automatically by means of separate results files that are sent as e-mail attachment, via FTP or as a network (IP) message. Note that you can use dynamic text variables in the profiles to set the name of the result file. The overview dialog shows colored dots to indicate if a report profile is being used in action profiles for e-mail, FTP or network messages and if the usage is tied to a scheduled task (Time Task - TT).
• Counting Corridor Report Profiles
  Allows defining the report profiles, which are used to subsequently evaluate the image analysis data for objects passing through the counting corridors.
• Heatmap Report Profiles
  Allows defining the report profiles, which are used to subsequently evaluate the distribution of stay analysis data ("heatmaps").

Support of i25 Cameras with Lens L23

This release also supports the new i25 camera models with L23 lens (angle of view 92 x 68°). With this lens variant, the camera can automatically correct the slight image distortion, provided that you select the corresponding "display mode".

Other Improvements

• MxPEG Codec
  As compared to the predecessor release 4.3.0.15, this release contains a new version of the MxPEG codec, which uses less bandwidth when transferring scenes with reduced illumination.
• Audio quality
  The audio signal recorded by the camera's microphone has been improved in the range between 4 and 5 kHz. This improves the output of the audio signal by applications (e.g., the MOBOTIX App).
• Improved automatic white balance for scenes with artificial light
  This release has an additional setting for optimized white balance that is especially geared to indoor scenarios with artificial lighting. In the Color Settings dialog of the Setup Menu > Image Control section, the new entry Automatic White Balance (Indoor) has been added to the White Balance option for this purpose.

Bugfixes

• ActiveX Plug-in for Internet Explorer
  This software contains the new releases 1.8.6.0 (64 bit) and 1.7.4.0 (32 bit) of the MxPEG ActiveX control, which can be installed on the Windows system directly from the camera's browser user interface.
• Behavior of the exposure program "+6"
  When using the exposure program +6, the camera sometimes generated overexposed images if exposure times had been 1/2 second or longer.
• Events in continuous recording
  Events that occurred during a continuous recording at the same time as the one-minute images E00000.JPG had been included in the event list even though they had been configured to not trigger a recording. This led to single video motion events triggering false alarms on the MOBOTIX App although these events were only to be used in the event logic to trigger recordings.
• Network messages with line breaks
  When using line feeds (%A0) directly after the target address (IP address and port), the camera sent the message without the host header.

Known Limitations

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

top

Software Release MX-V4.3.0.15 - for MOBOTIX Cameras D24M, M24M, Q24M, T24M, D14Di, S14, V14D, D25M, M25M, Q25M, T25M, D15Di, M15, M15-Thermal, S15 and V15D

Creation Date: 2014-11-05

Publishing Date: 2014-11-14

Enhancements and Improvements

Higher Frame Rates, Improved Image Quality and 5MP Resolution for 5MP Cameras

This software release contains a basic redesign and many improvements of the image generation process on all 5MP camera models. This results in noticeably improved image rates and higher image quality. The faster frame rates are most easily noticed when using the M-JPEG and MxPEG codec with a lot of movement in the images. Depending on the image size, image quality, video codec used and the movement in the image, it is possible to reach up to 150% higher frame rates.

In addition, these cameras can now generate images in 5 Megapixel resolution (2592x1944pixels) as compared to QXGA ()2048x1536 pixels) before. This applies to both single and dual images as well as to full image display and display of automatically distortion-corrected images (on Hemispheric camera models).

Support of MxDisplay and Door Station Features

• Integrating Door Stations and Other Cameras into MxDisplay
  This software release is the first official release that allows using one or more MxDisplay units as door intercom for a MOBOTIX door station. After updating other cameras to this release, you can also add these cameras to an MxDisplay unit in order to use it as an integrated video management system for viewing and managing the cameras.
• Auto Configuration for Door Stations
  The camera auto configuration for setting up door stations and the corresponding intercoms now also supports the new MxDisplay. Just like with Grandstream IP video phones, MxDisplay units are automatically detected in the network and configured as intercoms for the bells and/or contact numbers of a door station camera. Once the auto configuration has assigned bells and contact numbers to the MxDisplay units, you can customize the configuration of the individual MxDisplay units afterwards.
• Time-Based Access Control via MxDisplay
  In combination with the firmware versions of the MxBus modules that is part of release V4.3.0.x, this release now allows setting up time-based access control for MOBOTIX door station. Note that defining the individual time ranges for RFID cards and PIN numbers that are already trained is currently only possible using the configuration screens of the MxDisplay.
• Combined Access Identification
  In this release, an MxDisplay can be used to further increase security by setting up a combination of RFID card and PIN for access control.

Note:
For instructions and more information on setting up an MxDisplay unit as intercom for a MOBOTIX door station and on integrating other MOBOTIX cameras, please read the MxDisplay documentation.

Extended Features for MxBus Modules

Integrating and using MxBus modules has been extended by significant new features that are described in the following.

MxMessageSystem

MxBus modules can now send and receive messages independently from other devices. Typically, an MxBus module will send a message as a reaction to a sensor that is triggering. Upon receiving such a message, an MxBus module can trigger an action. For example, if the signal input of an MX-232-IO-Box is triggering (e.g., from a door that is opening), the module can send a message to a camera or to other MxBus modules. Likewise, the same box can trigger a signal output (e.g., to switch on the lights) upon receiving such a message.

Sending and receiving messages in this context is not restricted to one camera (as a "Gateway") and its attached MxBus modules, but can also use the Ethernet network for communication between different MxBus systems, i.e., cameras with attached MxBus modules. Currently, up to 32 MxBus systems can be set up in such a messaging system.

The following steps are required to use MxBus messages:

• Configure the messages to send and to receive in the Admin Menu > MxMessageSystem > Message Configuration for MxBus Modules dialog.
• Define special message events that will be triggered in the camera upon receiving MxBus messages, and which can be used just like all other events to start recordings or to start other actions. In order to do this, the Setup Menu > Event Control > Event Overview > News Events dialog provides the new MxMessageSystem event sensor type.
• Configure special Message Profiles for sending MxBus messages in the new Admin Menu > MxMessageSystem > Message Profiles for Action Groups dialog and use these message profiles within the action groups in the Setup Menu > Event Control > Action Group Overview dialog.
• Optionally configure the MxMessageSystem to exchange messages between the individual MxBus systems in the new Admin Menu > MxMessageSystem > Network Distribution of Messages dialog.
• If required, you can also set up softbuttons to send MxBus messages. To do this, the new MxMessageSystem function has been added when defining softbuttons.

For detailed information on the MxMessageSystem, please read the camera's online help or the Technical Note – MxMessageSystem, which is available in the Support > MX Media Library > Compact Guides section of the MOBOTIX website.

Multi-Device Support

With the introduction of the new MxBus messaging system, it is now also possible to operate more than one MxBus module of the same type on the same MxBus.

Note:
Currently, only the MX-232-IO-Box supports this feature. You can attach several of these devices to one camera and use them to send messages if signal inputs are triggering and switch signal outputs upon receiving specific messages.

Updating the Firmware of MxBus Modules

In order to update the firmware of the MxBus modules in the Admin Menu > Hardware Configuration > Manage MxBus Modules, it is no longer necessary to update the modules one by one. A new button allows starting the firmware update for all modules at once.

Other Improvements

• DHCP settings
  Starting with this software release, all MOBOTIX cameras are running as DHCP client by factory default. In addition, you can reach the cameras using the factory IP address (10.x.x.x) since this address is used as second IP address.
• E-mail encryption
  In order to encrypt e-mails, you can set Server Settings to use SSL/TLS in the e-mail profiles. This setting is a prerequisite for using many e-mail service providers.
• Support of the new HD lenses
  The Admin Menu > Hardware Configuration > Lens Configuration dialog has been extended to use the new HD lenses, which will be available soon. These lenses have an f-stop of 1.8 and are significantly more light-sensitive than the lenses with f-stop 2.0 that are used currently. Setting the proper lens type is important since this information is used when correcting the lens distortion and for showing the correct illumination value in the image (^Ir or ^Il placeholders).
• OpenVPN encryption
  The Admin Menu > Network Configuration > OpenVPN Client Settings contains the new Encryption parameter, which allows using one of many different encryption algorithms for establishing a VPN connection.
• Texts in the serial interface
  You can now use other characters besides CR (0xD) and LF (0xA) for inserting line feed characters in texts that are sent via the RS232 interface. To do so, edit the camera configuration file as follows:

  SECTION rs232d
  ...
  RS232DLINEBREAK=<character as hexadecimal>[,<character as hexadecimal>]...[,<character as hexadecimal>]
  ...
  ENDSECTION rs232d

  Example:

  RS232DLINEBREAK=0x0,0x3

• Enhanced system messages
  The system messages listed in the Admin Menu > System Information > System Messages dialog now also contains connections to the camera from MxDisplay units or the MOBOTIX App. These will appear as "...STREAM eventstream...".
• API command for deleting the system messages
  If a camera sends the <IP address>/admin/transferresults?delete HTTP command to delete its own system messages, the camera will produce an error message in its system messages. You can avoid this by using the new <IP address>/admin/rcontrol?action=delete_system_messages command.
• Improvements in the camera online help for the Remote Configuration API
  The online for the remote configuration API now contains an example for changing network message profiles using the <IP address>/admin/remoteconfig... commands.

Bugfixes

• $(SEN.PIR) variable for showing the PIR level
  The PIR level value shown in the camera image using the $(SEN.PIR) variable was faulty on M15 cameras.
• Gray image in Player of the MOBOTIX App
  After double-tapping on an event to change from the Event view to the Player, the Player only showed an empty gray image instead of the event image.
• Loading of events in the Event view of the MOBOTIX App
  The loading of events in the Event view was faulty starting with camera software release V4.2.1.43. Sometimes, only one event image was loaded instead of the selected number of events.
• Dual live image with distortion correction with full image recording
  Hemispheric 5MP dual cameras sometimes produced errors and rebooted if both image sensors had been generating corrected images while using full image recording.
• MxEasy Privacy Mode
  Activating the Privacy Mode in MxEasy did not disable recording, but instead recorded black images.
• MxActivitySensor on Thermal cameras with custom temperature range
  On thermal sensor images with customized limits for the displayed temperature range, MxActivitySensor sometimes triggered on objects and image contents that were not visible in the image.
• Corrections of the online help
  The online help for the text variables (e.g., $(EVT.EST.SELECTED)) contained some faulty links (e.g., ../control/event). Moreover, the online help on the serial terminal still contained the (deprecated) MODE parameter.
• Camera configuration after simultaneous HTTP API calls
  Several external programs that called the <IP address>/control/control?set... HTTP command at the same time to change the camera configuration sometimes produced incomplete sections in the configuration file.

Known Limitations

• Door station – access using PIN
  After changing the access information on the MxDisplay (e.g., training RFID cards or activating combined access identification), it will take up to three minutes until the PIN/combined access can be used to gain access.
• MxPEG ActiveX control
  Due to a problem with the certificate, the MxPEG ActiveX control of this release cannot be installed. An updated version will be published in the Support > Software Downloads > Plugins section. As a temporary workaround, you can adjust the settings of Internet Explorer in the Tools > Internet Options dialog:
  • In section Security > Trusted Sites > Sites, add the camera URL (http://<IP address>).
  • Deactivate the Require server verification (https) for all sites in this zone checkbox and close the dialog.
  • Click on Custom Level to open the Security Settings dialog.
  • In the ActiveX Controls and Plugins section, activate the Download unsigned ActiveX controls option, then close all dialogs of the Internet Explorer.
• MxFFS Archive Size
  In the Storage on External File Server / Flash Device dialog, entering a size larger than 4000 GiB (= 4 TBytes) for the MxFFS Archive Size parameter is not possible, although an MxFFS archive can get bigger. In order to enter a larger size, you can edit the camera configuration file in the SECTION fileserver and adjust the MXFFS_ARCHIVE_SIZE=<value in GiB> line. This new value will be shown properly in the Storage on External File Server / Flash Device dialog.
• Translations
  Currently, only the English and German translations of the camera's web browser interface are up-to-date.

top

Software Release MX-V4.2.1.61 - for MOBOTIX Cameras D24M, M24M, Q24M, T24M, D14Di, S14, V14D, D25M, M25M, Q25M, T25M, D15Di, M15, M15-Thermal, S15 and V15D

Creation Date: 2014-08-27

Publishing Date: 2014-09-08

Notes on Upgrading – PLEASE READ CAREFULLY:

• After uploading a configuration file created by a camera software V4.0.x, make sure that you check the resulting configuration to ensure that it is functioning properly and adjust it, if required.

Enhancements and Improvements

MxFFS Archive Storage

On any Secure camera model, when recording to a Flash device (SD card, USB pendrive/SSD) or a USB harddisk as a Primary Target, you can set up an additional MxFFS Archive on an SMB/CIFS or NFS file server. The camera will then copy all data of the primary target (e.g., the SD card) to this archive as well. The size of the MxFFS archive is virtually unlimited. The MxFFS archive itself is implemented as a ring buffer, i.e., if the maximum size is reached, the oldest data will be overwritten. As opposed to the folder and file structure created by the camera when using a file server as a primary target, an MxFFS archive consists of noticeably fewer binary files (1 GB each) that cannot be read directly.

The archiving itself, i.e., copying the data from the Flash device to the archive, can take place either continuously or can be controlled by a time table to push the copying to specific times during the day. The camera automatically detects connection failures to the archive file server and — after the connection has been re-established — will copy any data recorded on the Flash device during the outage to the archive. Note, however, that this only works if the video data are still available on the Flash device (and have not been overwritten because the outage lasted too long and the ring buffer storage overwrote the oldest events). When using an MxFFS archive, the time ranges defined as storage limits will be used on both the Flash device (SD card, etc.) and the archive.

Open the Admin Menu > Storage > Storage on External File Server / Flash Device dialog and activate the MxFFS archive by selecting the corresponding MxFFS Archive Target. This option is only available if the Primary Target is a Flash device (SD card, USB pendrive/SSD) or a USB harddisk.

Storing on an SD card combined with this new feature will also allow recording virtually unlimited amounts of video data. The SD card is used as a large buffer, which is used to bridge even longer file server outages. Filling the archive only at specific times creates a whole array of new application scenarios, e.g., cameras using SD card recording in buses that archive new video data when they are parked at the depot.

Notes:

• Currently, you can access the video data stored in the MxFFS archive only via the camera. MOBOTIX is currently working on the solutions that will allow the applications (e.g., MxMultiViewer, ...) to access the archive directly.
• After activating MxFFS on a camera that had already stored recordings in the "old" event folder structure on a file server, the camera will not be able to read the old recordings any more. In such a case, you should use MxControlCenter to access the old recordings, since this application can read and evaluate the event folder structure directly on the file server.

Compared to the precedessor software release MX-V4.2.1.43, the MxFFS Archive Storage feature has been considerably improved and optimized.

Support for 1MP/3MP Camera Models

This software release has also been approved for all camera models D24M, M24M, Q24M, T24M, D14Di, S14, V14D. This means that these models not only benefit from the improvements of the current release, but also from the general, not 5MP-specific enhancements and bugfixes from the predecessor versions 4.2.1.43 and 4.1.10.35.

MxFFS Archive Storage for Secure Models

The MxFFS Archive Storage of the predecessor version MX-V4.2.1.43 has been enhanced considerably and optimized even further. You can now use this feature without limitations on all Secure camera models.

Enhancements for Thermal Image Sensors

The Setup Menu > Thermal Sensor Settings dialog contains the following improvements and enhancements to adjust the image generation of thermal image sensors:

• Color Palette
  The factory default of the Color Palette parameter has been changed from Grayscale to Rainbow.
• Value Range
  The new Value Range parameter in the Thermal Range section allows selecting different temperature ranges (i.e., the range between the lowest and the highest temperature value displayed in the image). A small value range results in noticeably higher sensitivity (i.e., the smallest difference in temperature that can be shown) compared to a large value range. The factory default setting is thus Small (High Sensitivity).
• Allow Immediate Updates
  This parameter in the Thermal Range section has been disabled by factory default.
• Level of Detail
  This new parameter in the Thermal Range section can be set to Medium or High to amplify the contrast in scenes with only little temperature differences. Image noise will increase slightly, but the image will show considerably more details. The factory default setting is Low.

Other Improvements

• Font Size for Text Display
  The font size for texts that are displayed in the image can now be set to 8pt, 16pt or 24pt. This is possible in the following dialogs that contain the new Display Font Size parameter:
  • Setup Menu > Text & Display Settings
  • Setup Menu > Recording ("Full Image Recording" section)
  • Admin Menu > Image Profiles
• Limit Frame Rate When Idle
  This option in the Setup Menu > General Image Settings dialog is activated by factory default and reduces the image rate if the camera does not provide any live streams. This will improve the performance when playing back recordings via the MOBOTIX App. When recording with pre-alarm (up to 5 seconds), however, this setting will reduce the frame rate of the pre-alarm recording to only 1 fps!
  IMPORTANT: If this behavior is not desired for pre-alarm recording, make sure that you deactivate this option.

Bugfixes

• Accessing Cameras via the MOBOTIX App
  After installing the previous release of the camera software, the MOBOTIX App could only access cameras that had been integrated using admin access rights. This is not required any more. You can now integrate cameras without access credentials, if the Live access right of the corresponding camera has been set to Public Access.
• IP Notify Event
  It is again possible to define accepted sender addresses for events of the type IP Receive. The parsing of these addresses did not work properly, which prevented this event from triggering properly.
• Small video motion windows on Hemispheric cameras
  Hemispheric cameras sometimes did not trigger events if very small video motion (VM) windows had been defined.
• Image mirroring on dual Hemispheric cameras with Day/Night switching
  If the night image sensor of a dual Hemispheric camera had been set to use a distortion-corrected display mode (such as Panorama) and image mirroring had been activated at the same time, the image did not get mirrored after automatically switching to the night sensor.
• Live stream preview of dual Hemispheric cameras
  If a dual Hemispheric camera had been set to use the Surround display mode, the live preview of one image sensor delivered a faulty image that contained only two instead of four partial images. This happened in the live preview of MxControlCenter or when using the HTTP API <IP address>/control/faststream.jpg?stream=full&camera=left&preview&fps=20&size=1024x768).

Known Limitations

• Size of an MxFFS archive
  In the Storage on External File Server / Flash Device dialog, entering a size larger than 4000 GiB (= 4 TBytes) for the MxFFS Archive Size parameter is not possible, although an MxFFS archive can get bigger. In order to enter a larger size, you can edit the camera configuration file in the SECTION fileserver and adjust the MXFFS_ARCHIVE_SIZE=<value in GiB> line. This new value will be shown properly in the Storage on External File Server / Flash Device dialog.
• Behavior with activated "Dual Lens Analysis" option
  If full image recording is not being used, activating this option will result in different behavior when using video motion detection and ActivitySensor. If only the image of one sensor is visible, video motion detection is also executed on the other image sensor. The ActivitySensor is only evaluated on the visible image sensor, the other sensor is ignored.
• Translations
  Currently, only the English and German translations of the camera's web browser interface are up-to-date.

top

Software Release MX-V4.2.1.43 – for all MOBOTIX 5MP/Thermal Cameras D25M, M25M, Q25M, T25M, D15Di, M15, M15D-Thermal, S15 and V15D

Creation Date: 2014-05-22

Publishing Date: 2014-06-17

Notes on Upgrading – PLEASE READ CAREFULLY:

• This software version has been released only for cameras with 5MP or thermal image sensors!
• After uploading a configuration file created by a camera software V4.0.x, make sure that you check the resulting configuration to ensure that it is functioning properly and adjust it, if required.

Enhancements and Improvements

Support of the Cameras M15D-Thermal and S15 with Thermal Image Modules

This software release also supports the new M15D-Thermal camera model, which combines reliable, light-independent motion detection via MxActivitySensor of a thermal image sensor with the functionality of a surveillance camera with color or black&white image sensor. In addition, you can also use this software on an S15D with the new thermal image sensor modules. You can choose to install either one or two thermal image sensors or one thermal image sensor and one standard sensor module (with color or black&white image sensor).

CAUTION:
When using a MOBOTIX S15D, on which the PoE class setting had been changed manually from the factory default to PoE Class 2 before, you need to set the camera to use PoE Class 3 before connecting the sensor modules!

To do so, start the camera without connected sensor modules and open the Admin Menu > Hardware Configuration > Image Sensor Configuration dialog. Under Left Sensor and Right Sensor, set the corresponding ports (External Sensor Cam1,External Sensor Cam2) for the Thermal Sensor Modules that are to be attached.

Now open Admin Menu > Network Configuration > Ethernet Interface and in the Ethernet Hardware Options section, Power Supply row, click on the Change link. In the Power over Ethernet wizard, select Power over Ethernet (Class 3), then follow the instructions. When you are prompted to reboot the camera, disconnect the power supply of the camera. Then attach the thermal sensor modules and reconnect the power supply.

To configure the thermal sensors, open the Setup Menu > Image Control > Thermal Sensor Settings dialog.

Just like for the standard image sensors, you can use numerous possibilities for adjusting/enhancing the generated images of thermal sensors, as in the following list:

• Mirror the image
• Obscuring Image Areas
• Executing PTZ actions (pan, tilt, zoom)
• Text and logo display
• Display of event/action symbols
• Level meters as bar or scroll chart

Configure the corresponding parameters in the Setup Menu > Image Control section.

Extended Options for Image Control of Thermal Image Sensors

When generating images, the camera determines the current temperature range of the image sensor and displays the values of the temperature range according to the selected color palette (e.g., Rainbow). If objects get in the image area that are either a lot hotter or a lot colder than before (i.e., the temperature is well outside the current limits), the temperature range is extended accordingly. This change in value range or temperature control serves to stretch the contrast. In order to make even the smallest changes in temperature visible, the camera is adjusting the value range automatically. Temperature control can lead to a change in the distribution of colors and brightness within the image, resulting in an adjusted display of objects that had been in the image before.

You can use two additional options in the Thermal Sensor Settings dialog (Setup Menu > Image Control) to better control or even avoid this effect:

• Allow Immediate Updates
  If this option is activated, the adjustment of the temperature range (as described above) and the inherent change in the color or brightness gradient will take place immediately and automatically.
  If this option is not activated, adjustment is deferred a little bit and will take place depending on the Update Speed setting (Slow, Medium, Fast).
• Temperature Window
  This parameter allows setting a specific image area that will be used to determine the temperature range. By factory default, the camera will use the entire image area of the sensor (Full Image setting). Selecting Custom Windows and doing a "Shift-.Click, Click" with the mouse will allow you to select the image area with graphical means - just like when defining exposure windows.
  By defining temperature windows in areas, where no changes due to hot or cold objects are to be expected, you can maintain a constant color or brightness distribution.

OpenVPN

Starting with this software release, MOBOTIX cameras contain an OpenVPN client. Using this client, you can establish a secure connection to a camera that is connected via a router (including 3G and 4G/LTE) to the Internet, without requiring the camera to have its own public IP address. All you need is a publicly accessible OpenVPN server, to which both the camera's OpenVPN client and the OpenVPN client of the end device (computer, laptop, etc.) connect in order to establish a connection via a secure tunnel. To configure the camera's OpenVPN client, open the OpenVPN Client Settings dialog (Admin Menu > Network Configuration). As far as network protocols are concerned, the client supports both UDP and TCP. Make sure that the certificates and keys that are required for the VPN server are available in .PEM format.

Improved Audio Quality Thanks to HD Wideband Audio

The audio system of the camera has been completely overhauled. It now delivers notably better sound quality thanks to a higher sampling rate (16 kHz) and higher quantization (16 bits). This results in much better quality of the different sounds played by the camera (announcements, default messages, sounds, etc.) and of the audio messages recorded by the camera. VoIP phone connections now use the G.722 HD Audio codec, which delivers a much better audio quality as compared to the PCMA and GSM codecs used before.

MxFFS Archive Storage (BETA Version)

When recording to a Flash device (SD card, USB pendrive/SSD) or a USB harddisk as a Primary Target, you can set up an additional MxFFS Archive on an SMB/CIFS or NFS file server. The camera will then copy all data of the primary target (e.g., the SD card) to this archive as well. The size of the MxFFS archive is virtually unlimited. The MxFFS archive itself is implemented as a ring buffer, i.e., if the maximum size is reached, the oldest data will be overwritten. As opposed to the folder and file structure created by the camera when using a file server as a primary target, an MxFFS archive consists of noticeably fewer binary files (1 GB each) that cannot be read directly.

The archiving itself, i.e., copying the data from the Flash device to the archive, can take place either continuously or can be controlled by a time table to push the copying to specific times during the day. The camera automatically detects connection failures to the archive file server and — after the connection has been re-established — will copy any data recorded on the Flash device during the outage to the archive. Note, however, that this only works if the video data are still available on the Flash device (and have not been overwritten because the outage lasted too long and the ring buffer storage overwrote the oldest events). When using an MxFFS archive, the time ranges defined as storage limits will be used on both the Flash device (SD card, etc.) and the archive.

Open the Admin Menu > Storage > Storage on External File Server / Flash Device dialog and activate the MxFFS archive by selecting the corresponding MxFFS Archive Target. This option is only available if the Primary Target is a Flash device (SD card, USB pendrive/SSD) or a USB harddisk.

Storing on an SD card combined with this new feature will also allow recording virtually unlimited amounts of video data. The SD card is used as a large buffer, which is used to bridge even longer file server outages. Filling the archive only at specific times creates a whole array of new application scenarios, e.g., cameras using SD card recording in buses that archive new video data when they are parked at the depot.

Currently, you can access the video data stored in the MxFFS archive only via the camera. MOBOTIX is currently working on the solutions that will allow the applications (e.g., MxMultiViewer, ...) to access the archive directly.

Controlling Camera Arming Based on Changes in Illumination

The illumination measured by the camera can be used to control the general arming of the camera as well as the arming of recording and actions. It was already possible to control the arming switches in the General Event Settings, Action Group Overview and Recording dialogs (Setup Menu > Event Control) by using the custom signals (CS1, ... CS5, CSL). These signals can now be set to use an illumination value (By Illumination option) for switching.

To do so, open the General Event Settings dialog and for the Arming parameter, select one of the custom signals (CS1, ..., CS5, CSL). Now set the Source of the selected signal to By Illumination. As Illumination Source, you can now select the illumination measured by an image sensor (Auto, Right, Left, Both, depending on the model) or you can use an external illumination sensor (e.g., of an attached MX-GPS-Box).

Notes

When arming depending on a specified illumination value, you should consider the following issues:

• The camera does not "measure" the illumination value, but calculates the value based on exposure time and the image brightness.
• A configured arming based on low illumination can be influenced or even deactivated if bright sources of light (e.g., car headlights) appear in the image area. This can be avoided by using an MX-GPS-Box that is mounted in a spot that is not influenced by any unwanted sources of light.
• A black&white image sensor can deliver high illumination values, especially when combined with infrared lighting. This may also deactivate the arming of recording, if it is configured to start when illumination drops below a specific level.

Extended Day/Night Switching

On a Day/Night camera (Secure models), it was already possible to use the measured illumination to switch between the day and night lenses (Setup Menu > Image Control > General Image Settings > Camera Night Switch, Illumination from camera option). M15D or S15D cameras with a thermal image module will use this module as "night lens" and will use the illumination value of the standard image module for switching. From this software release on, it is also possible to use the illumination sensor of an attached MX-GPS-Box for switching between the day and night lenses (Illumination from MX-GPS-Box).

In addition, you can assign one of the custom signals (CS1, ..., CS5, CSL) to be used a day/night switch. This allows using any kind of signal source (e.g., a key switch) to switch between the day and the night lenses.

When combined with the camera's ability to copy the state of a master camera, you can use e.g., the custom signal CS1 set to From Master to switch an entire group of cameras from the day to the night lens or vice versa. The master camera itself is switched using CS1 wired to a key switch or the illumination sensor of an attached MX-GPS-Box.

Other Improvements

• Zooming Hemispheric cameras
  When zooming, the Hemispheric display modes (Normal, Panorama, Double Panorama, Panorama/Focus, Surround) deliver a noticeably higher image quality as compared to preceding software releases. In addition, the object sizes of the zoomed image correspond much more closely to the zoom levels than before.
• File Server Test
  The Storage on External File Server / Flash Device dialog (Admin Menu > Storage) now contains an additional Start Test button in the File Server Options section. This button allows using the specified access data of an NFS or SMB/CIFS file server for a connection test. The test itself runs in a popup window and the results are shown behind the button.
• ActiveX component for 32-bit and 64-bit systems
  In this software release, the MxPEG ActiveX component used to display MxPEG camera streams in Internet Explorer (IE) is contained as a 32-bit (V1.7.1.0) and a 64-bit package (V1.8.5.0). When selecting the ActiveX component in IE, the browser will automatically load the proper version of the component for the current operating system.
• Number of time table programs increased to 100
  The number of time table programs has been increased from 10 to 100. This also means that the camera better supports the calendar feature of MxEasy.
• FTP transfer of the entry log
  On door station cameras, you can now use FTP to transfer the camera's entry log (Door opened, New message, etc.). To do so, simply select Entry Log as file type in the FTP profiles.
• Configuration parameters to support Polycom VVX 1500 SIP video phones
  By adding the line VOIPVIDEOSENDRECV=1 to the audionotify section of the camera configuration (Admin Menu > Configuration > Edit), the camera can establish a SIP video connection to Polycom VVX 1500 SIP video phones.

Bugfixes

• Image errors due to faulty configuration parameters for MxActivitySensor or video motion windows (VM)
  If the camera configuration contained faulty or incomplete parameters for MxActivitySensor or the video motion windows (Admin Menu > Configuration > Edit), the camera sometimes generated faulty images after rebooting. This sometimes also prompted the camera to reboot unexpectedly.
• Using the digit "7" to select "Sunday" for time tasks
  Using the digit "7" to execute time tasks on Sundays prompted the camera to execute that task every day.
• Event recording with history images (HR) in Hemispheric display modes
  When recording a live image with activated distortion correction (Panorama, Normal, etc.) as a history image, the camera always recorded the full image instead of the distortion-corrected live image.
• Commands for changing the contents of JPEG comments using an RS232 or network message
  These commands for changing the contents of JPEG comments (e.g., ---clear--- for deleting the contents and \n for adding a line break) sometimes did not lead to the desired results.
• Empty network messages
  When receiving an empty network message (i.e., network message of the Text only file type without any text), the camera did not trigger an event.
• Event navigation in the browser event list
  The camera did not activate the >> link (Move 20 sequences forward) in the Event List of the browser-based user interface.
• Using Quick Controls to add VM windows
  When adding video motion windows (VM) using the Recording > Add Window Quick Controls, the camera sometimes deleted parts of previously defined messaging and other event configuration settings.
• Variables in texts of e-mail profiles
  If the text field of an e-mail profile contained variables in the first line (e.g., $(id.hostname)), the camera did not replace the variables by the actual text.
• Factory IP address in SIP accounts of the "SIP Server Settings" dialog
  When using a fixed IP address that was different from the factory IP address, the SIP accounts in the SIP Sever Settings dialog sometimes showed the factory IP address instead of the current IP address (@10.x.y.z). This also happened if the Additional IPv4 Address in the Ethernet Interface dialog had been deactivated.

Known Limitations

• Behavior with activated "Dual Lens Analysis" option
  If full image recording is not being used, activating this option will result in different behavior when using video motion detection and ActivitySensor. If only the image of one sensor is visible, video motion detection is also executed on the other image sensor. The ActivitySensor is only evaluated on the visible image sensor, the other sensor is ignored.
• Display of SD card encryption key
  After entering an encryption key in the Formatter Wizard: MxFFS Volume Partitioning dialog and closing the wizard, the Admin Menu > Storage on External File Server / Flash Device dialog will not show the encryption key. The dialog will only show the key after you have reloaded the dialog.
• Window definition for D15Di-Sec-Pano models
  For these models, exposure windows, video motion windows, and obscured area windows can only be defined in the Full Image display mode.
• Translations
  Some translations are missing on all language versions other than English and German in the web browser interface of the camera.

top

Software Release MX-V4.1.10.35 – for all MOBOTIX 5MP Cameras D25M, M25M, Q25M, T25M, D15Di, M15, S15 and V15D

Creation Date: 2014-02-21

Publishing Date: 2014-02-25

Notes on Upgrading – PLEASE READ CAREFULLY:

• This software version has been released only for 5MP camera models!
• After uploading a configuration file created by a camera software V3.x, make sure that you check the resulting configuration to ensure that it is functioning properly and adjust it, if required.

Enhancements and Improvements

Improved Camera Behavior When Displaying Only Parts of the Image Sensor

The behavior of exposure windows as well as video motion detection and ActivitySensor windows when displaying only parts of the image sensor (i.e., when executing vPTZ actions) has been improved. If full image recording has not been activated, the camera software will only evaluate those areas of the detection windows that are in the visible section of the image. If exposure windows have been defined, which are completely outside of the visible image section due to vPTZ actions, the camera automatically switches exposure control to the Visible Image Section setting. If full image recording is activated, all defined detection windows will be evaluated. This change improves image quality most notably on 5MP cameras when zooming and in the Panorama view of a 5MP Hemispheric camera.
Due to the approach described above, the Live Image Priority option in the Setup Menu > vPTZ Settings dialog was not required any more and has been removed.

Extended Parameters for Exposure Control and Image Improvement (5MP, MxLEO)

The parameters for exposure control and image improvement on 5MP sensors (color and B&W) can now be better adjusted to situations, which are different from the standard requirements for video surveillance. This may be the case in webcam scenarios or in security applications that demand color images even in dark scenes, for example. For this purpose, the following new options have been implemented (you may have to click on the More button at the bottom of the dialog):

• "Automatic Sharpness Control" option in the "Setup Menu > General Image Settings" dialog
  Use this option to adjust the configured sharpness to the current image brightness as soon as the illumination drops considerably below 10 Lux. For web applications, it is now recommended to set this value to Disabled.
• "Sensor Gain Range" option in the "Setup Menu > Exposure Settings" dialog
  Changing the Full default value to High or Low will reduce the range that is used in very dark scenes to control the hardware gain range of the image sensor. The image will stay darker and will have less image noise.
• "Automatic Saturation Control" option in the "Setup Menu > Color Settings" dialog
  Use this option to adjust the configured color saturation to the current image brightness. This automatic adjustment reduces the saturation as the illumination levels drop, eventually resulting in a B&W image. This parameter may not produce the desired results in webcam applications. In such a case, set this parameter to Disabled.

Notes:

• The Webcam image program disables the two Automatic Sharpness Control and Automatic Saturation Control options and sets the Sensor Gain Range to Low.
• If you had used the Webcam image program with an older software release, the new settings will not be applied automatically. If you need the new settings after updating the software, you should re-apply this image program!

Bugfixes

• MxFFS recording to large USB storage devices
  The recording to USB storage media (USB sticks or hard drives) with more than 128 GBytes in MxFFS format did not work properly.
• File server checks and camera reboot
  Activating the File Server Checks produced an error when executing a software reboot. If e-mail notification had been configured, the camera sent the corresponding e-mail messages.

Known Limitations

• Behavior with activated "Dual Lens Analysis" option
  If full image recording is not being used, activating this option will result in different behavior when using video motion detection and ActivitySensor. If only the image of one sensor is visible, video motion detection is also executed on the other image sensor. The ActivitySensor is only evaluated on the visible image sensor, the other sensor is ignored.
• Display of SD card encryption key
  After entering an encryption key in the Formatter Wizard: MxFFS Volume Partitioning dialog and closing the wizard, the Admin Menu > Storage on External File Server / Flash Device dialog will not show the encryption key. The dialog will only show the key after you have reloaded the dialog.
• Window definition for D14Di-Sec-180°/D15Di-Sec-Pano models
  For these models, exposure windows, video motion windows, and obscured area windows can only be defined in the Full Image display mode.
• Translations
  Some translations are missing on all language versions other than English and German in the web browser interface of the camera.

top

Software Release MX-V4.1.10.28 – for all MOBOTIX D24M, M24M, Q24M, T24M, D14Di, S14, V14D, D25M, M25M, Q25M, T25M, D15Di, M15, S15 and V15D Cameras

Creation Date: 2013-10-29

Publishing Date: 2013-11-14

Notes on Upgrading – PLEASE READ CAREFULLY:

• This software version contains important enhancements and improvements. Before running the upgrade, you should be aware of the changes and the limitations of this version (see Known Limitations section below), since downgrading to older versions 4.0.4.x on T24M cameras is only possible with assistance from MOBOTIX Support. Make sure that you save the current camera configuration to the computer before running the upgrade.
• When upgrading the software, the camera automatically adjusts the camera configuration in several sections. Note that you cannot use such an adjusted and stored configuration on cameras with software releases lower than 4.1.x.
• After uploading a configuration file created by a camera software V3.x, make sure that you check the resulting configuration to ensure that it is functioning properly and adjust it, if required.
• Due to the changes in the exposure programs, you should check the exposure when updating a 5MP camera (D15, S15, M15, V15D, Q25M, M25M, D25M, T25M). In such a case, you may have to select a different exposure program. Please read additional information on this topic in the Optimized Exposure Programs and Color Reduction for 5MP Sensors section below.

Enhancements and Improvements

Support of the New Q25M, M25M, D25M and T25M Camera Models

This software release also supports the new Q25M, M25M, D25M and T25M camera models, which also have more light-sensitive 5MP image sensors on both color and black&white lenses, just like the D15Di, S15, M15 and V15D models. The maximum resolution of the Basic and IT variants has been increased to HD resolution (1280x720 pixels); before, these variants had been limited to VGA resolution (640x480 pixels). For M25M models, there is an additional tele lens with very large focal length (L320) available.

MxBus for Q25M, M25M, D25M

With this software, the new Q25M, M25M and D25M camera models support attaching MxBus devices. This means, that you can attach an MX-232-IO-Box in order to use extra signal input/output lines or that you can attach an MX-GPS-Box in order to use a camera as a time server.

Optimized Exposure Programs and Color Reduction for 5MP Sensors

The exposure programs of the predecessor version MX-V4.1.9.29 for all 5MP models have been optimized even further. In scenes with illumination levels below 25 Lux, exposure times tend to be even shorter, thus further reducing motion blur. To adjust the exposure times to special scenarios and applications, you can now use the -2, -1, 0 (default setting), +1, +2, +4 and +6 exposure programs. The new exposure programs +4 and +6 correspond to the +3 and +5 exposure programs of the predecessor version.
In addition, the camera will perform a more significant color reduction in scenes with diminishing illumination (especially below 5 Lux). This transition to Black/White mode reduces the color noise that increases as illumination diminishes, thus significantly improving image quality.

CAUTION:
After updating the software of a running system, you should definitely check the changes in exposure under low-light conditions and possibly adjust the settings. Likewise, you should verify that the video motion detection settings (video motion sensors and MxActivitySensor) are still working properly in dark scenes. Generally speaking, if you want to get the same exposure times as in the software releases before MX-V4.1.9.29, you should select an exposure program that is one or two values above the current program. For web applications, it is now recommended to use the +6 program.

IPv6 Support

This software release is the first one to support live http/https connections from a web browser to the camera via an IPv6 network. To configure an IPv6 address, open the Admin Menu > Network Configuration > Ethernet Interface dialog and configure the address in the IPv6-Ethernet-Parameter section (in addition to the IPv4 address).

Integrated Shock Sensor for all 5MP Models

All current 5MP models D15Di, S15, M15, Q25M, M25M, D25M, T25M and V15D have an integrated shock sensor, which allows detecting acts of vandalism against the camera, for example. To be able to react to physical shocks, the new Shock Sensor event type has been added to the Setup Menu > Event Overview > Environment Events dialog. This means that the camera can execute any action (e.g., e-mail, FTP transfer, sound alarm, etc.) when detecting such an event.

Other Improvements

• ActiveX adjustments for IE 11
  The ActiveX control for showing a live camera image with MxPEG and audio in Internet Explorer now also works with IE 11.
• Number of addressees for door station
  The Admin Menu > Video Door Station > Bell Behavior and Video Mailbox dialog for configuring the features of an IP Video Door Station now allows configuring up to 150 addressees. Before, the number of addressees had been limited to 17.

Bugfixes

• Playback in MOBOTIX App in LoRes Mode
  When playing back recorded MxPEG videos in the MOBOTIX App, the video sometimes showed tiles in LoRes mode.
• Registration of Sipgate Premium Account
  Registering a Sipgate Premium account as VoIP provider did not work – this has been fixed. Note, however, that – although the SIP address (User Name and Domain fields in the camera configuration) has the form "xyz@sipgate.de", you need to enter the corresponding proxy server (e.g., "proxy.live.sipgate.de").
• Text display using the ^Sx variables
  When using image profiles, (e.g., for an FTP transfer) the displayed text of one of the ^Sx variables, which is reading input from a serial interface (e.g., a weather station), had been faulty.
• Time tables for recording on a door station
  It was not possible on door stations to control continuous recording using one of the time tables (weekly schedules). In such a case, the continuous recording was running permanently.
• Pre-alarm created tiles
  When recording MxPEG videos with long pre-alarm times (5 sec), the camera sometimes generated tiles at the beginning of the alarm on large images or images with high bandwidth requirements. This has been fixed for M15, T25M and Q25M models.

Known Limitations

• Display of SD card encryption key
  After entering an encryption key in the Formatter Wizard: MxFFS Volume Partitioning dialog and closing the wizard, the Admin Menu > Storage on External File Server / Flash Device dialog will not show the encryption key. The dialog will only show the key after you have reloaded the dialog.
• Window definition for D14Di-Sec-180°/D15Di-Sec-Pano models
  For these models, exposure windows, video motion windows, and obscured area windows can only be defined in the Full Image display mode.
• Translations
  Some translations are missing on all language versions other than English and German in the web browser interface of the camera.

top

Software Release MX-V4.1.9.29 – for all Cameras M24M, D24M, Q24M, T24M, D14Di, D15Di, S14, S15, M15, V14D and V15D

Creation Date: 2013-09-09

Publishing Date: 2013-09-10

Notes on Upgrading – PLEASE READ CAREFULLY:

• This software version contains important enhancements and improvements. Before running the upgrade, you should be aware of the changes and the limitations of this version (see Known Limitations section below), since downgrading to older versions 4.0.4.x on T24M cameras is only possible with assistance from MOBOTIX Support. Make sure that you save the current camera configuration to the computer before running the upgrade.
• When upgrading the software, the camera automatically adjusts the camera configuration in several sections. Note that you cannot use such an adjusted and stored configuration on cameras with software releases lower than 4.1.x.
• After uploading a D12D configuration file to a D14Di or a D15Di, make sure that you check the resulting configuration to ensure that it is functioning properly and adjust it, if required.
• Due to the changes in the exposure programs, you should check the exposure when updating a 5MP camera (D15, S15, M15). In such a case, you may have to select a different exposure program. Please read additional information on this topic in the Optimized Exposure Programs and Noise Filters for 5MP Sensors section below.

Enhancements and Improvements

Optimized Exposure Programs and Noise Filters for 5MP Sensors

In contrast to the previous software releases for the 5MP camera models D15Di, S15, M15 and V15, the exposure programs of this release have been improved in such a way that the camera can use considerably shorter exposure times for image generation. This applies mainly for low-light situations with illumination levels below 25 Lux. The improvements are most perceptible in the range between 10 and 0 Lux. Thanks to the shorter exposure times, the camera images now show a significant reduction of motion blur. In addition, the cameras can now use higher image rates even in very dark scenes, since the maximum frame rate is limited only at considerably lower illumination levels. In conjunction, both measures mean an important improvement especially for security applications.

In order to allow the users to deliberately use long exposure times, the existing exposure programs have been expanded – you can now select programs between -2 and +5. For web applications, for example, motion blur is not really an issue since the focus is on best image quality. In such a case, users would rather choose the exposure program +5.

This improvement is the result of a re-designed image noise filter of the 5MP sensors. Especially under low-light conditions, the new noise filter allows using significantly shorter exposure times while maintaining the same low level of image noise as compared to previous versions.

CAUTION:
After updating the software of a running system, you should definitely check the changes in exposure under low-light conditions and possibly adjust the settings. Likewise, you should verify that the video motion detection settings (video motion sensors and MxActivitySensor) are still working properly in dark scenes. Generally speaking, if you want to get the same exposure times as in the previous software releases, you should select an exposure program that is one or two values above the current program. For web applications that had been using the image program +2 up until now, it is now recommended to use a setting of +5.

Support of S15 and M15 Cameras with Hemispheric Lenses (L12) and Mixed Focal Lengths

This software is the first release to support the new S15 and M15 with 5MP hemispheric image sensors (L12). This means that the corresponding 5MP color and B/W sensor modules with hemispheric lenses are available for these camera models. Another novelty is the fact that it is now possible to use mixed focal lengths in dual camera models, i.e., one hemispheric sensor module (L12) with another, non-hemispheric sensor module (L25, L51, etc.). Note that the camera models with hemispheric 5MP sensor modules support the same display modes, vPTZ and other actions as in the older hemispheric cameras with 3MP sensors.

When using image sensors with different focal lengths, this software offers all possible display modes, i.e., the hemispheric modes (Full Image, Normal, Surround, Panorama, Panorama/Focus, Dual Panorama) as well as the non-hemispheric modes (Full Image, Lens Correction (L25 only), Picture in Zoom, Event in Picture). Note that when selecting a display mode that is not valid for the current lens, the software will ignore the request.

Enhanced Door Station Features

Using S14/S15 Cameras as IP Video Door Station

This software release allows using and configuring S14 and S15 camera models as door stations. In order to be used as a door station, you can connect the same door station components (KeypadRFID, BellRFID, external bell buttons, DoorMaster, etc.) to these camera models as to a T24 IP Video Door Station. The new AudioMount in particular is a valuable installation aid with integrated speaker and microphone that is geared to using these camera models as a hemispheric door station. The functions for configuring and running the camera as a door station are the same as for a T24. Only difference: you need to press the two camera keys to start configuring the camera using the auto configuration feature (instead of the T24 bell button). For further information on configuring and using such a camera as a door station, download the S15 User Manual from www.mobotix.com/other/Support/Manuals/IP-Camera-Systems/FlexMount-S15.

Support of the New BellRFID Module for Door Stations

This software release supports configuring and running a BellRFID module in a MOBOTIX IP Video Door Station. This flexible bell button module has up to five buttons and can be used with any door station. In addition, the integrated RFID unit provides for opening doors without keys, but with RFID transponders (RFID cards, keyring pendants, etc.) Configuring and using a BellRFID module follows the same procedures as the KeypadRFID module. For further information on this topic, download the Quick Installation Guide: BellRFID from www.mobotix.com/other/Support/Manuals/IP-Video-Door-Station/Single-Components.

Note:
At present, this software release allows using either a KeypadRFID or a BellRFID module with one door station. Using both modules at the same time is not possible.

Other Enhancements and Changes

• Mono Operation of M15 Cameras
  With this software, M15 cameras can be run with only one instead of two sensor modules. For information on installing an M15 camera with only one sensor module, download the M15 User Manual from www.mobotix.com/other/Support/Manuals/IP-Camera-Systems/AllroundDual-M15.
• Higher Degree of Image Detail when Using the Camera Zoom
  By activating the new Live Image Priority option in the Setup Menu > vPTZ Settings dialog, you can increase the degree of image detail in case you have used vPTZ actions to zoom into the image and have thus moved any previously defined exposure, video motion or ActivitySensor windows out of the visible image.
• MxAnalytics Removed for Q24 Camera Models
  Starting with this software version, the video analysis features of MxAnalytics for Q24 camera models are NOT available any more!

Bugfixes

• PTZ behavior of Q24 mounted to ceiling
  When zooming or tilting the camera image of a Q24 that has been mounted to the ceiling farther than the image center, the automatic flipping of the image ("Ceiling/Floor Flip") did not work properly and sometimes produced image jumps.
• Audio output of internal camera announcements in Turkish
  The audio output of the camera's announcements (e.g. the IP address) did not work if the language of the camera had been set to Turkish. In such a case, the camera will now make its announcements in English (as for all other languages except German).
• Rotated images too sharp
  If the camera images were being rotated by the camera software by 90 or 270 degrees, image sharpness was to high.
• Signaling of messages at the KeypadRFID
  In case more than nine messages had been left for a mailbox user, the KeypadRFID did not signal this properly. The "9" key kept blinking, although it should have been on continuously.

Known Limitations

• "Object Tracing" feature
  It is not possible to use the Object Tracing (OT) option in Hemispheric cameras with L11/L12 lenses and other cameras with L22/L25 lenses, on which you have set the corresponding lens in the Admin Menu > Lens Configuration dialog. If you would like to use this feature anyhow on a camera with L22/L25 lens, you can set a different lens (e.g. L43/L51) in the dialog; note that this means that the distortion correction will not work any more.
• Display of SD card encryption key
  After entering an encryption key in the Formatter Wizard: MxFFS Volume Partitioning dialog and closing the wizard, the Admin Menu > Storage on External File Server / Flash Device dialog will not show the encryption key. The dialog will only show the key after you have reloaded the dialog.
• Window definition for D14Di-Sec-180°/D15Di-Sec-Pano models
  For these models, exposure windows, video motion windows, and obscured area windows can only be defined in the Full Image display mode.
• Translations
  Some translations are missing on all language versions other than English and German in the web browser interface of the camera.

top

Software Release MX-V4.1.6.27 – for all Cameras M24M, D24M, Q24M, T24M, D14Di, D15Di, S14, V14D and V15D

Creation Date: 2013-06-04

Publishing Date: 2013-06-10

Notes on Upgrading – PLEASE READ CAREFULLY:

• This software version contains important enhancements and improvements. Before running the upgrade, you should be aware of the changes and the limitations of this version (see Known Limitations section below), since downgrading to older versions 4.0.4.x on T24M cameras is only possible with assistance from MOBOTIX Support. Make sure that you save the current camera configuration to the computer before running the upgrade.
• When upgrading the software, the camera automatically adjusts the camera configuration in several sections. Note that you cannot use such an adjusted and stored configuration on cameras with software releases lower than 4.1.x.
• After uploading a D12D configuration file to a D14Di or a D15Di, make sure that you check the resulting configuration to ensure that it is functioning properly and adjust it, if required.

Enhancements and Improvements

Support of the New D15Di and V15D Camera Models

This software release also supports the new camera models D15Di and V15D, which now have more light-sensitive 5MP image sensors on both color and black&white lenses. The maximum resolution of IT variants of the D15Di has been increased to HD resolution (1280x720 pixels); before, these variants had been limited to VGA resolution (640x480 pixels). In addition, this software release also supports the vandalism-protected V14D and V15D camera models.

Bugfixes

• Image sharpness on Hemispheric display modes
  On Hemispheric camera models, the image sharpness with activated distortion correction was lower than in the predecessor release. This was the case for the Normal, Surround, Panorama, Double-Panorama and Panorama-Focus display modes.
• MxCC-Alarm network messages
  Because the camera did not properly send network messages (IP Notify) of the type MxCC-Alarm, MxControlCenter ignored these messages. Other network message of the type Text only and the message contents camnotify=ownip were not affected and worked properly.
• Evaluating Heatmap reports using Internet Explorer
  When evaluating a heatmap report using Internet Explorer, the heatmap was sometimes not displayed properly.

Known Limitations

• MxAnalytics Heatmap Reports
  When using MxControlCenter or MxEasy to export a heatmap, the result may be an invalid JPEG file.
• No specific Door Station functionality for S14 available
  This camera model cannot be used in conjunction with the DoorMaster or the KeypadRFID module. Likewise, neither Door Station auto configuration for Grandstream phones nor manually setting up a mailbox are supported.
• "Object Tracing" feature
  It is not possible to use the Object Tracing (OT) option in Hemispheric cameras with L11 lenses and other cameras with L22 lenses, on which you have set the corresponding lens in the Admin Menu > Lens Configuration dialog. If you would like to use this feature anyhow on a camera with L22 lens, you can set a different lens (e.g. L43) in the dialog; note that this means that the distortion correction will not work any more.
• Display of SD card encryption key
  After entering an encryption key in the Formatter Wizard: MxFFS Volume Partitioning dialog and closing the wizard, the Admin Menu > Storage on External File Server / Flash Device dialog will not show the encryption key. The dialog will only show the key after you have reloaded the dialog.
• Window definition for D14Di-Sec-180°/D15Di-Sec-Pano models
  For these models, exposure windows, video motion windows, and obscured area windows can only be defined in the Full Image display mode.
• Translations
  Some translations are missing on all language versions other than English and German in the web browser interface of the camera.

top

Software Release MX-V4.1.6.25 – for all Q24M, D24M, M24M T24M, D14Di, S14 and V14D Cameras

Creation Date: 2013-05-03

Publishing Date: 2013-05-06

Notes on Upgrading – PLEASE READ CAREFULLY:

• This software version contains important enhancements and improvements. Before running the upgrade, you should be aware of the changes and the limitations of this version (see Known Limitations section below), since downgrading to older versions 4.0.4.x on T24M cameras is only possible with assistance from MOBOTIX Support. Make sure that you save the current camera configuration to the computer before running the upgrade.

• When upgrading the software, the camera automatically adjusts the camera configuration in several sections. Note that you cannot use such an adjusted and stored configuration on cameras with software releases lower than 4.1.x.

• After uploading a D12D configuration file to a D14Di, make sure that you check the resulting configuration to ensure that it is functioning properly and adjust it, if required.

Enhancements and Improvements

New software function "MxActivitySensor" for camera internal motion analysis

This software version provides for the first time the new MxActivitySensor for camera internal motion analysis on all Q24M, M24M, D24M, T24M, D14Di, S14 and V14D Secure models. In contrast to the current video motion (VM) analysis, the MxActivitySensor does not react to just any movement in the image, but only on objects that move in a certain direction. It is thus considerably less sensitive to disturbances affecting the complete image, such as rain, snow, wobbling motion of the camera mast, etc. and it is also much easier to configure than the VM detection. The configuration of MxActivitySensor is done via the web browser in the same dialog page as for the configuration of the VM event triggers. The Image Analysis Events section of the Event Overview dialog, accessed via Setup Menu > Event Control now contains new event sensor types named MxActivitySensor. The events generated by MxActivitySensor can be used just as VM events for image storage or the execution of any particular actions.

More information about the MxActivitySensor can be found in the online help and in the downloadable documentation titled "Compact Guide: MxAnalytics" found on the MOBOTIX website under Support > MX Media Library > Compact Guides.

Other Enhancements and Improvements

• Time zones
  The list of time zones in the camera was brought up to date (as of 11 March 2013).

• MxAnalytics Improvements (only for Q24M-Sec)

  • Heatmap Reports for Week and Month
    The evaluation of MxAnalytics data in heat map reports can now be executed not only for days but also for weeks and months.

  • Transfer of Reports via FTP
    MxAnalytics Heatmap and Counting Line reports can now be transferred via FTP. Two additional file types named Counting Line Report and Heatmap Report are now available in the definition of FTP profiles.

Bugfixes

• Automatically generated VM windows on dual cameras
  When using the command "$ generate = ..." for the automatic generation of VM windows, the sensor number (0 or 1) was not properly evaluated and generated VM windows in both sensors instead of the desired sensor.

• Description of the variables $ (SEN.INA) - $(SEN.INP)
  The description of the variables $(SEN.INA) - $(SEN.INP) used for display of the states of Signal In and Signal Out has been updated in the online help.

• MxAnalytics - Export of Heatmap Reports
  In order to perform an export of a Heatmap Report via a Softbutton, previously it was necessary to grant a user rights for the Setup Menu. This has been changed - now a user only needs rights for "API" and an additional command has been added which can be executed via a Softbutton using the following URL:
  <IP-Address>/control/stat_export_api?heatmap_profile=<Profile name>

• List of VM windows for individual Image Analysis Event Profiles
  The list of VM windows used for a particular Image Analysis Video Motion Event Profile may not have been correctly interpreted resulting in the addition of unwanted VM windows in the profile. An example of this would be entering "1,3-4" in the window list and the result would be that the VM with number 2 would have been erroneously included as well.

• "Normal" Display Mode on D14Di-180° model cameras
  The two image areas of the left and right sensor were not properly joined in the middle of the picture when using "Normal" Display Mode on this particular camera model.

• Problem with MxAnalytics and User-Defined Image Settings
  Errors could occur during the generation of MxAnalytics reports when user-defined image resolution was used together with image rotation or mirroring.

Known Limitations

• MxAnalytics Heatmap Reports
  An error can occur during the generation of a Heatmap export from MxControlCenter or MxEasy resulting in an improperly formed JPEG file. Other than that, an error can occur during the display of the Heatmap in the browser when the Heatmap report is generated using the Internet Explorer.

• No specific Door Station functionality for S14 available
  This camera model cannot be used in conjunction with the DoorMaster or the KeypadRFID module. Likewise, neither Door Station auto configuration for Grandstream phones nor manually setting up a mailbox are supported.

• "Object Tracing" feature
  It is not possible to use the Object Tracing (OT) option in Hemispheric cameras with L11 lenses and other cameras with L22 lenses, on which you have set the corresponding lens in the Admin Menu > Lens Configuration dialog. If you would like to use this feature anyhow on a camera with L22 lens, you can set a different lens (e.g. L43) in the dialog; note that this means that the distortion correction will not work any more.

• Display of SD card encryption key
  After entering an encryption key in the Formatter Wizard: MxFFS Volume Partitioning dialog and closing the wizard, the Admin Menu > Storage on External File Server / Flash Device dialog will not show the encryption key. The dialog will only show the key after you have reloaded the dialog.

• Window definition for D14Di-Sec-180° models
  For this model, exposure windows, video motion windows, and obscured area windows can only be defined in the Full Image display mode.

• Translations
  Some translations are missing on all language versions other than English and German in the web browser interface of the camera.

Software Release MX-V4.1.4.70 – for all Q24M, D24M, M24M T24M, D14Di and S14 Cameras

Creation Date: 2013-03-04

Publishing Date: 2013-03-07

Notes on Upgrading – PLEASE READ CAREFULLY:

• This software version contains important enhancements and improvements. Before running the upgrade, you should be aware of the changes and the limitations of this version (see Known Limitations section below), since downgrading to older versions 4.0.4.x on T24M cameras is only possible with assistance from MOBOTIX Support. Make sure that you save the current camera configuration to the computer before running the upgrade.
• When upgrading the software, the camera automatically adjusts the camera configuration in several sections. Note that you cannot use such an adjusted and stored configuration on cameras with software releases lower than 4.1.x.
• After uploading a D12D configuration file to a D14Di, make sure that you check the resulting configuration to ensure that it is functioning properly and adjust it, if required.

Enhancements and Improvements

Support for the new MOBOTIX App for iPhone, iPad, iPad mini and iPod touch

This version contains many internal enhancements to support the new MOBOTIX App for Apple devices. This software is a mandatory update if you want to use the MOBOTIX App and all of its features with door stations and other cameras.

• Important features such as the reduction of image resolution and frame rates to limit bandwidth requirements when remotely operating the cameras or optimizations when playing back stored video and audio data are now part of the camera software.
• This includes the introduction of a GSM phone call fallback, which is used if the camera cannot reach the MOBOTIX App via a TCP connection. Open the Admin Menu > Video Door Station > Bell Behavior and Video Mailbox dialog to activate this feature. Make sure you have already defined a corresponding phone profile.

New HD and FullHD Image Formats

This software support the new 16:9 image formats HD (1280x720 pixels) and FullHD (1920x1080 pixels).

Note: These image formats have a different aspect ratio than the camera's CMOS image sensor (4:3). It is therefore NOT possible to use these image formats for Full Image recording, since this would mean that parts of the full sensor image would get lost.

Changed "Normal" Image Quality and Factory Default

The behavior of the image quality setting Normal has been changed for XGA (1024x768 pixels) and MEGA (1280x960 pixels) resolutions. This setting now results in a slightly improved frame rate, but also shows a slightly reduced image quality. To achieve a better, i.e., the best image quality, it is still recommended to use the Image Quality=High setting. In accordance with this change, the factory default has been changed from Normal to High. When using the XGA factory default resolution, the results corresponds exactly to the result of the predecessor version.

Other Enhancements, Improvements and Changes

• Full Image recording for T24 cameras
  Full Image recording has been deactivated for T24 cameras as per factory default setting.
• Frame rate optimization for recording
  If applications do not request a live image stream from the camera, specific settings result in a higher frame rate when recording.
• Loading PTZ positions
  When switching pre-defined PTZ positions, the camera switches directly to the new position instead of slowly moving to the new position.
• Adjusted microphone noise suppression
  Noise suppression (also active if echo cancellation has been activated), has been reduced.
• ActiveX with new certificate
  The certificate of the ActiveX control version 1.7.1.0 has been renewed.
• Calculation of flash cell wear
  The internal calculation of flash cell wear has been adjusted.
  Notes:
  • This means that the displayed values may increase after updating the software and resetting the camera to factory defaults.
  • You can adjust this value by editing the MAXIMUM_BLOCK_SWEEPS parameter in the fileserver section of the configuration file (Admin Menu > Configuration > Edit).
• Dialogs in Turkish
  All dialogs of this release (except the online help) are available in Turkish.

Bugfixes

• Audio from T24 Door Stations to Grandstream on bell sound
  When using a camera sound to signal the ringing of a T24 doorbell, the SIP connection to a Grandstream IP phone only showed the video, but did not contain the sound.
• Call forwarding when using SIP servers
  Forwarding a call when using an external or the internal SIP server of the camera did not work.
• Polycom phones did not succeed in establishing a Video SIP connection to the camera
  Establishing a Video SIP connection (H.264) from a Polycom phone to the camera is not possible. In order to establish connections from Polycom phones, you need to edit the configuration file of the camera (Admin Menu > Configuration > Edit) and add the line VOIPVIDEOSENDRECV=1 to the audionotify section.
• Initial view of the Grandstream GXV3140 did not show full image when calling the camera from the phone
  Due a change in the Grandstream software, the camera was unable to change the default view of the Grandstream phone to full image. Rather, the Grandstream phone used its default Picture-in-Picture view.
• System restore from Grandstream phone deletes its own web password
  When restoring the system from a Grandstream phone, the phone deleted the password for its own web access by setting the password to "empty". Subsequent attempts of Auto Configuration to change the password failed. You had to manually set a new password in the phone's web interface.
• MxPEG recognition problems for dark objects/image areas on D14 and S14 cameras with Night sensors
  In these cases, the night sensor of the cameras showed tiling artefacts with delayed recognition of images changes.
• Time-based filter against image noise on dark illumination situations on D14 and S14 camera models
  The image noise filter for moving objects has been improved.
• Not possible to activate Full Image Recording on IP Video Door Stations (T24)
  When activating Full Image Recording on an IP Video Door Station (T24), the camera used the default settings for recording instead.
• Number of phone profiles of SIP-capable camera models limited to 20
  The number of definable phone profiles for outbound calls (Admin Menu > Outgoing Calls Settings) has been increased to 150.
• Video calls to Cisco9971
  When executing video VoIP calls to a Cisco 9971 phone using Cisco Call Manager, the video did not work properly.
• Software update using Safari on OS X Mountain Lion
  When using Safari on this OS X version, it was not possible to update the software of a camera.

Known Limitations

• No specific Door Station functionality for S14 available
  This camera model cannot be used in conjunction with the DoorMaster or the KeypadRFID module. Likewise, neither Door Station auto configuration for Grandstream phones nor manually setting up a mailbox are supported.
• "Object Tracing" feature
  It is not possible to use the Object Tracing (OT) option in Hemispheric cameras with L11 lenses and other cameras with L22 lenses, on which you have set the corresponding lens in the Admin Menu > Lens Configuration dialog. If you would like to use this feature anyhow on a camera with L22 lens, you can set a different lens (e.g. L43) in the dialog; note that this means that the distortion correction will not work any more.
• Problems in MxAnalytics when using custom image settings
  When using MxAnalytics together with custom image areas or rotated/mirrored images, MxAnalytics results may not be correct.
• Display of SD card encryption key
  After entering an encryption key in the Formatter Wizard: MxFFS Volume Partitioning dialog and closing the wizard, the Admin Menu > Storage on External File Server / Flash Device dialog will not show the encryption key. The dialog will only show the key after you have reloaded the dialog.
• VoIP remote stations not reachable after updating T24 Video Door Stations with software 4.0.4.28
  After updating a T24 Video Door Station with software 4.0.4.28 to 4.1.4.10, the configured VoIP remote stations (e.g. Grandstream video phones) are not reachable any more. This can be repaired by manually setting the proper SIP proxy in the Admin Menu > Outgoing Calls Settings dialog.
• Window definition for D14Di-Sec-180° models
  For this model, exposure windows, video motion windows, and obscured area windows can only be defined in the Full Image display mode.
• Translations
  Some translations are missing on all language versions other than English and German in the web browser interface of the camera.

Software Release MX-V4.1.4.11 (Release) – for all Q24M, D24M, M24M T24M, D14Di and S14 Cameras

Creation Date: 2012-07-11

Publishing Date: 2012-07-12

Notes on Upgrading – PLEASE READ CAREFULLY:

• This software version contains important enhancements and improvements. Before running the upgrade, you should be aware of the changes and the limitations of this version (see Known Limitations section below), since downgrading to older versions 4.0.4.x on T24M cameras is only possible with assistance from MOBOTIX Support. Make sure that you save the current camera configuration to the computer before running the upgrade.
• When upgrading the software, the camera automatically adjusts the camera configuration in several sections. Note that you cannot use such an adjusted and stored configuration on cameras with software releases lower than 4.1.x.
• After uploading a D12D configuration file to a D14Di, make sure that you to check the resulting configuration to ensure that it is functioning properly and adjust it, if required.
• As compared to the predecessor version 4.1.1.24 for T24M and D14Di cameras, this version contains an updated firmware for the attached MxBus modules (KeypadRFID version 1.0.2.0, DoorMaster 1.0.1.6). While updating the firmware is not mandatory, it is recommended since it improves the behavior of the modules. After upgrading the camera software to version 4.1.4.11, cameras with attached MxBus modules show a corresponding message in the live image. If this is the case, you should upgrade the firmware of the attached modules in the Admin Menu > Manage MxBus Modules dialog by clicking on the corresponding Update SW button for each module.

  Note:
  Updating the firmware may take up to ten minutes per module. In addition, it is not possible to update several modules at once, but only one after the other.

• Differences compared to version 4.0.4.28
  Compared to version 4.0.4.28 for the M24M, D24M and Q24M camera models, this version contains all general enhancements and changes from versions 4.1.1.7 to 4.1.1.24 for the aforementioned cameras. This specifically includes the event profiles, which had been available form version 4.1.1.7 for T24M camera models only.
• Please also follow the note on changed trigger behavior of the video motion detection windows in the Improved Image Quality and Frame Rates.

Enhancements and Improvements

S14M/D Camera Models with Dual Hemispheric Features

This software release also supports the new S14 camera models, which had initially been delivered with software release 4.1.4.6. With the introduction of the S14D, the Hemispheric technology is available in a dual camera for the first time. This means that both sensor modules can use all Hemispheric display modes that up until now had only been available in the Q24M. In the course of introducing these features, the software has been enhanced and improved in the following ways:

• "Admin Menu > Image Sensor Configuration" dialog
  This dialog allows setting the number and type of sensor modules (=image sensors) that have been attached to the S14D.

  CAUTION:
  When running the camera for the first time, it automatically detects the sensors and stores this information in the camera configuration. Subsequently, the camera repeats the image sensor discovery after each reboot and compares this information to the stored configuration. If the software discovers changes, it shows a corresponding message in the live image and logs a "critical" system error message.

• Quick Controls
  S14D camera models with two attached sensor modules allow selecting individual display modes for the two sensor modules using the Display Mode (Right) and Display Mode (Left) Quick Controls.
• vPTZ Control and OnScreen Control
  This version allows configuring the individual "subviews" within the displayed single or dual camera image using the OnScreen Control. To do so, select the subview you would like to configure, then click on the arrow icon in the upper left corner. The camera now shows the OnScreen Control, which allows configuring the corresponding subview. This means that it is also possible to rotate and customize the individual focus windows of the Panorama/Focus view.

  Example: A dual image with the Panorama/Focus display mode for the left and Double Panorama display mode for the right camera image consists of a total of five subviews (three of the left and two of the right camera image).

  Note:
  This enhanced use of the OnScreen Controls not only applies to the S14, but to all other Hemispheric cameras as well!

• "Admin Menu > Speaker and Microphone" dialog
  This dialog allows selecting the microphones that are to be used for the audio channel of the camera – one external microphone or one or both microphones of the sensor modules.

For additional information on the different features specific to the S14, please also read the S14 camera manual!.

Integrated MxAnalytics image analysis features for Q24M models

For the first time, this software release contains the new MxAnalytics image analysis tools for Q24M models. This means that a Q24M mounted to a ceiling or wall can automatically detect and record information about moving objects in the image. The results can be displayed as heatmaps or when crossing counting lines defined in the image. The results are stored continuously on the camera's integrated SD card; they can be evaluated, displayed or exported for further analysis later on. To do so, the camera uses "report profiles", which define the type of evaluation and the time range covered by the report, e.g. "how many objects crossed this line within the last month". In order to configure the image analysis, the Setup Menu of the camera contains the new MxAnalytics Control section with the following dialogs:

• General MxAnalytics Settings
  Use this dialog to activate and configure the basic MxAnalytics settings, such as all parameters for object recognition and how to display the results in the camera's live image when testing.
• MxAnalytics Overview
  This dialog provides an overview of the activation status and the defined report profiles.
• Counting Line Report Profiles
  Allows defining the report profiles, which are used to subsequently evaluate the image analysis data for objects crossing the counting lines that are stored by the camera on a continuous basis.
• Heatmap Report Profiles
  Allows defining the report profiles, which are used to subsequently evaluate the image analysis data for the distribution of objects ("heatmap") that are stored by the camera on a continuous basis.

Notes:

• In order for MxAnalytics to be able to store the data on the camera's integrated SD card, it needs to be formatted accordingly. For this purpose, the Formatter Wizard: MxFFS Volume Partitioning contains an additional MxAnalytics Storage option. In addition, you need to activate the corresponding option in the Admin Menu > Storage on External File Server / Flash Device dialog in order to store the analysis data.
• Please refer to the camera's online help of the MxAnalytics dialogs if you would like more information on this topic.
• Note that you can use the MxControlCenter (version 2.5.2 and higher) and MxEasy (version 1.6 and higher) applications to configure MxAnalytics, the evaluation of the data and the display of the results.

Support of the New Functional Boxes

This software supports not only the MX-GPS-Box, but also the new MX-232-IO-Box (using either the USB or MxBus connection).

• When connecting this functional box via USB and after activating in the Admin Menu > Manage Hardware Expansions dialog, you can use the known RS232 features as well as two signal inputs and two signal outputs.
• When connecting the MX-232-IO-Box via MxBus and after activating in the Admin Menu > Manage MxBus Modules dialog, you can currently use only the two signal inputs and two signal outputs.

Please see the corresponding product documentation for additional information.

Other Enhancements and Improvements

SD Card Recording with Encryption

If security is an issue, you can opt to store only encrypted video and audio data on the camera's integrated SD card. Note that you need to set an encryption key and format the SD card accordingly before you can start recording on the card. You can set the encryption key in the Formatter Wizard: MxFFS Volume Partitioning dialog. If you want to use such an encrypted card in a different camera or read the card's contents using MxControlCenter, you need to enter the encryption key that had been set when formatting the SD card. In addition, the camera failure checks have been improved in detecting errors when accessing the SD card.

JPEG Files with EXIF Header

When activating the new EXIF Data option in the Setup Menu > JPEG Settings dialog, the camera will add an EXIF header to the generated JPEG files (e.g. event images). In this case, the header contains general information, such as Date, time and – if an MX-GPS-Box is attached to the camera – the current GPS coordinates. The EXIF header can be read by many other applications.

CAUTION:
In order to properly show the videos and single images with activated EXIF header in MOBOTIX applications, you need MxControlCenter version 2.5.1.1 or higher, MxEasy version 1.5.1 or higher or the ActiveX control for Internet Explorer version 1.7.1.0 or higher.

Improved Image Quality and Frame Rates

• Color sensors
  The behavior of the image quality settings (High, Normal and Fast) for color sensors has been modified. This results in overall improved image quality and sharpness when using the High and Normal settings. As compared to the predecessor versions, the frame rates when using the Normal setting can be slightly reduced for certain resolutions. When using the Fast setting, image quality has been reduced noticeably – with the same or even slightly improved frame rates as before.
• B/W image sensors
  When using B/W image sensors, this version shows higher frame rates for most combinations of Image Quality and Resolution settings – with the same or even improved image quality. Image quality and sharpness have been improved noticeably when using Image Quality = Fast. The image quality settings High and Normal are producing the same results in this version.
• CAUTION:
  Due to the higher frame rates of B/W image sensors, the trigger behavior of the video motion windows (VM) has changed. Make sure that you check and adjust the existing VM definitions after updating the software.

PoE Classes When Using MxBus Modules

Starting with this version, you need to use PoE class 3 instead of class 2 when using MxBus modules on D14Di cameras (Admin Menu > Ethernet Interface).

Improved "Time and Date" Dialog

The Admin Menu > Time and Date dialog has been redesigned and improved in this version. It is now easier to use a camera as time server by activating the Use Camera as Time Server checkbox.

Improved "Manage MxBus Modules" Dialog

The Admin Menu > Manage MxBus Modules dialog has been redesigned and improved in this version.

MX-GPS-Box Data Available as Variables

The values for illumination, temperature, GPS coordinates, speed, etc. delivered by an attached MX-GPS-Box can now be displayed in the live image and in image profiles using the corresponding variables: $(SEN.LXE), $(SEN.TGP.CELSIUS), $(SEN.GPS), $(SEN.GVE) ...

Arming Recordings Using Actions

The arming status of the camera recording can also be controlled indirectly by using a triggering event. To do so, you need to define a custom signal (CS1, CS2 ...), which is activated by an action that is in turn triggered by an event. This is possible using a new feature that allows switching custom signals using actions. To use this feature, set the CS1, CS2, etc. signals in Setup Menu > General Event Settings to the By Action and activate the arming in the same dialog.

New ActiveX Control Version 1.7.1.0

Version 1.7.1.0 of the ActiveX control for Internet Explorer is required to properly show the camera's video stream, if it contains EXIF header data.

Bugfixes

• De-bounce time for ExtIO signal inputs
  The ExtIO signal inputs did not trigger properly, if the de-bounce time had been set to a value higher than 0.
• Changes in illumination using MxPEG and time-based noise filter
  When using the time-based noise filter, changes in illumination had not been carried over in the image, but became only apparent after some time had elapsed.
• D14Di and rotated images with text display
  D14Di cameras with rotated images (90 or 270 degrees) and displayed text sometimes showed image errors.
• D14Di with attached MX-GPS-Box as time server
  When using a D14Di with attached MX-GPS-Box as time server for other cameras, time synchronization sometimes did not work properly.
• T24M with activated continuous recording
  Activating continuous recording on a T24M could sometimes did not stop the recording.
• Image profiles in CIF resolution on Q24M
  When using CIF resolution in image profiles in conjunction with a distortion-corrected view (e.g. Normal) on Hemispheric cameras (e.g. Q24M), the images were sometimes corrupted.
• Setup of modem and serial interface in the browser
  When attaching a USB RS232 adapter to the camera, the changes made in the browser dialog for serial interface and modem operation had not been saved properly.
• Triggering of a direct VoIP call using the API
  When triggering a direct VoIP call using the camera API (<IP address>/rcontrol?action=voipcall...), the camera's audio channel remained deactivated.
• Format of variables for displaying exposure time
  The value of the $(IMG.EXA.RIGHT.SECOND) variable had been shown in milliseconds instead of split seconds (i.e., 1/60).
• "Admin Menu > Date and Time" dialog in IE9
  Displaying the dialog in Internet Explorer 9 sometimes resulted in errors.

Known Limitations

• No specific Door Station functionality for S14 available
  This camera model cannot be used in conjunction with the DoorMaster or the KeypadRFID module. Likewise, neither Door Station auto configuration for Grandstream phones nor manually setting up a mailbox are supported.
• Image sharpness on D14Di with Black/White image sensors
  Compared to the predecessor version 4.1.1.24, image sharpness on B/W image sensors may be slightly reduced. If this is the case, you should increase the image sharpness using the corresponding QuickControl.
• "Object Tracing" feature
  It is not possible to use the Object Tracing (OT) option in Hemispheric cameras with L11 lenses and other cameras with L22 lenses, on which you have set the corresponding lens in the Admin Menu > Lens Configuration dialog. If you would like to use this feature anyhow on a camera with L22 lens, you can set a different lens (e.g. L43) in the dialog; note that this means that the distortion correction will not work any more.
• Problems in MxAnalytics when using custom image settings
  When using MxAnalytics together with custom image areas or rotated/mirrored images, MxAnalytics results may not be correct.
• Display of SD card encryption key
  After entering an encryption key in the Formatter Wizard: MxFFS Volume Partitioning dialog and closing the wizard, the Admin Menu > Storage on External File Server / Flash Device dialog will not show the encryption key. The dialog will only show the key after you have reloaded the dialog.
• Incompatibility with MxEasy 1.5.1 and MxControlCenter 2.5.1.1 when defining windows
  Due to enhancements and changes in the format of the video stream generated by the camera, there are compatibility issues when defining exposure windows, video motion windows, obscured image areas, custom image areas and subsequent video motion analysis (Post VM). This applies to all display modes without active distortion correction! The application versions MxEasy 1.6 and MxControlCenter 2.5.2 will fix this issue.
• Loading Views and vPTZ positioning
  When loading predefined views or moving to a mouse click position on a hemispheric display mode, the camera can move unnaturally within the image.
• Issues with displaying windows during vPTZ actions
  When executing vPTZ actions on hemispheric display modes, the software sometimes shows the windows for exposure control, video motion detection and obscured image areas improperly.
• VoIP remote stations not reachable after updating T24 Video Door Stations with software 4.0.4.28
  After updating a T24 Video Door Station with software 4.0.4.28 to 4.1.4.11, the configured VoIP remote stations (e.g. Grandstream video phones) are not reachable any more. This can be repaired by manually setting the proper SIP proxy in the Admin Menu > Outgoing Calls Settings dialog.
• Limitations when talking back and forth using MxEasy on a computer
  The audio quality in intercom mode when using MxEasy on a computer largely depends on the audio components of the computer (hardware and software). Using a headset typically produces the best results if the input level of the microphone is set to a lower value. Note that you definitely need to adjust the audio settings to the individual situation. However, it is not recommended to increase the sensitivity of the camera microphone (default = Low), since this release still reduces the quality of the echo cancellation on the camera.
• Window definition for D14Di-Sec-180° models
  For this model, exposure windows, video motion windows, and obscured area windows can only be defined in the Full Image display mode.
• Translations
  Some translations are missing on all language versions other than English and German in the web browser interface of the camera.

Software Release MX-V4.1.1.24 (Release) – only for T24M and D14i Camera Models

Creation Date: 2012-03-29

Publishing Date: 2012-04-05

Notes on Upgrading – PLEASE READ CAREFULLY:

• This software version has been released only for T24M and D14Di camera models!
• This software version contains important enhancements and improvements. Before running the upgrade, you should be aware of the changes and the limitations of this version (see Known Limitations section below), since downgrading to older versions 4.0.4.x on T24M cameras is subject to certain restrictions. Make sure that you save the current camera configuration to the computer before running the upgrade.
• When upgrading the software, the camera automatically adjusts the camera configuration in several sections. Note that you cannot use such an adjusted and stored configuration on cameras with software releases lower than 4.1.x.
• After uploading a D12D configuration file to a D14Di, you need to check the resulting configuration to ensure that it is functioning properly.

• As compared to the predecessor version 4.1.1.7 for T24M cameras, this version contains an updated firmware for the attached MxBus modules (Keypad, Security DoorOpener). While updating the firmware is not mandatory, it is recommended since it improves the behavior of the modules. After upgrading the camera software to version 4.1.1.24, T24M cameras with attached MxBus modules show a corresponding message in the live image. If this is the case, you should upgrade the firmware of the attached modules in the Admin Menu > Manage MxBus Modules dialog by clicking on the corresponding Update SW button for each module.

  Note:
  Updating the firmware may take up to ten minutes per module. In addition, it is not possible to update several modules at once, but only one after the other.

Enhancements and Improvements

Support of the New MX-GPS-Box

This software version is the first version to support the new MX-GPS-Box. This weatherproof add-on module is connected to the camera via the MxBus interface and provides GPS position and time information. In addition, it also has a temperature and illumination sensor.

• Connecting the MX-GPS-Box
  To activate the MX-GPS-Box, connect the box to the MxBus interface of the camera. Next, open the Admin Menu > Manage MxBus Modules dialog and activate the box.
• Using the GPS-Box as time base
  Once the MX-GPS-Box has been activated, it is automatically used as time base for the attached camera and its status is displayed in the Admin Menu > Time and Date dialog. If this camera is used as time server for the other cameras, you can use the GPS time to synchronize all cameras in the same network.
• Using the GPS, illumination and temperature data as event triggers
  Once the GPS-Box has been activated, you can open the Setup Menu > Event Overview > Environment Events dialog to set illumination, temperature position or speed values of the GPS-Box to trigger the corresponding events. This dialog also provides the Determine position button, which shows the current GPS position data including the variations that are inherent to GPS technology.

Improved Dialog for Configuring Door Stations

The Admin Menu > Video Door Station > Manage Users dialog for configuring the features of a T24 door station has been renamed to Bell Behavior and Video Mailbox. In addition, this dialog's structure and contents have been overhauled.

Bugfixes

• Using the camera as time base
  Using the camera as time base for other cameras in the same network by entering the 127.127.0.1 IP address did not work properly.
• Image profiles with dark images on T24 models
  If the live image of a T24 became so dark that the noise filters were added, using image profiles (e.g. for FTP file transfers or e-mails) resulted in images that had been rotated by 180 degrees.

Known Limitations

• "Object Tracing" feature
  The Object Tracing (OT) option in the Setup Menu > Text & Display Settings dialog is not available in this version.
• Limitations when talking back and forth using MxEasy on a computer
  The audio quality in intercom mode when using MxEasy on a computer largely depends on the audio components of the computer (hardware and software). Using a headset typically produces the best results if the input level of the microphone is set to a lower value. Note that you definitely need to adjust the audio settings to the individual situation. However, it is not recommended to increase the sensitivity of the camera microphone (default = Low), since this release still reduces the quality of the echo cancellation on the camera.
• Window definition for D14Di-Sec-180° models
  For this model, exposure windows, video motion windows, and obscured area windows can only be defined in the Full Image display mode.
• Translations
  Some translations are missing on all language versions other than English and German in the web browser interface of the camera.

Software Release MX-V4.1.1.21 (Release) – only for T24M and D14Di Camera Models

Creation Date: 2012-02-13

Publishing Date: 2012-02-29

Notes on Upgrading – PLEASE READ CAREFULLY:

• This software version has been released only for D14Di and T24M camera models!

• This software version contains important enhancements and improvements. Before installing the upgrade, you should be aware of the changes and limitations of this version (see Known Limitations section below), since downgrading to older versions 4.0.4.x is subject to certain restrictions for T24M models. Make sure that you save the current camera configuration to the computer before installing the upgrade.

• When upgrading the software, the camera automatically adjusts the camera configuration in several sections. Note that you cannot use such an adjusted and stored configuration on cameras with software releases lower than 4.1.x.

• After uploading a D12D configuration file to a D14Di, you need to check the resulting configuration to ensure that it is functioning properly.

Important Notes

• First software release for dual P3 models
  This is the first software release for the dual camera models D14Di that are equipped with the PX320 "XScale" processor, the so-called P3 models. So far these D14Di models have been delivered with the software version 4.1.0.8.

• Dual QXGA images for D14Di models
  With the P3 dual system platform for the D14Di and the associated enhancements and increases in performance, the image resolution QXGA can now be activated for both image sensors simultaneously. This results in a total resolution of 6.2 megapixels. This feature had already been available in version 4.1.0.8.

• Differences to previous versions
  If not stated differently, the enhancements, improvements, and bug fixes described below refer to the previous versions 4.1.1.7 for T24M models and 4.1.0.8 for D14Di models.

• New firmware for attached MxBus modules
  As compared to the predecessor version 4.1.1.7 for T24M cameras, this version contains an updated firmware for the attached MxBus modules (Keypad, Security DoorOpener). While updating the firmware is not mandatory, it is recommended since it improves the behavior of the modules. After upgrading the camera software to version 4.1.1.21, T24M cameras with attached MxBus modules show a corresponding message in the live image. If this is the case, you should upgrade the firmware of the attached modules in the Admin Menu > Manage MxBus Modules dialog by clicking on the corresponding Update SW button for each module.

  Note:
  Updating the firmware may take up to ten minutes per module. In addition, it is not possible to update several modules at once, but only one after the other.

Enhancements and Improvements

Special Integration of D14Di-Sec-180° Models

Specific adjustments have been made for the D14Di-Sec-180° camera models, so that these models now basically behave like 6 megapixel mono cameras.

• Dual image behaves like one 6 megapixel image
  For these camera models, all settings and actions related to the camera image are applied to the dual image. This applies to the Full Image and Panorama image modes avalable in the Display Mode Quick Control. Note that this applies to vPTZ actions as well as to the definition of exposure windows, video motion windows and obscured image areas. In addition, the option Linked Image Control is activated by default. This means that the images of the left and right sensors are generated with the same exposure settings and therefore appear as a homogenous dual image.

• Panorama configuration
  The Panorama view of the D14Di-Sec-180° models has been improved significantly, so that it now resembles the Panorama view of the Hemispheric camera models (e.g. Q24M). Straight horizontal lines converging in the middle of the image do no longer appear buckled. When setting up a D14Di-Sec-180°, the two sensor images need to be properly adjusted in order to create a good panorama image. To adjust the panorama view, activate the Panorama View Configuration QuickControl. This on-screen screen control has also been improved and has additional functions.

  NOTE:
  When using a D14Di-Sec-180° with software version 4.1.0.8, the configured Panorama view remains unchanged after a software update. Also when configuring the panorama view using the QuickControls, the new improved view is not shown automatically. For that purpose, you need to reset the image settings manually using the Manage Settings > Load factory image settings QuickControl. This automatically shows the improved Panorama view and also activates the on-screen control to align the images.

Integrated Shock Detector

D14Di models are shipped with an integrated shock detector. This sensor allows detecting shocks experienced by the camera itself – caused by acts of vandalism, for example. Therefore, the new Shock Detector event sensor type has been added to the Setup Menu > Event Overview > Environment Events dialog. Actions, e.g. sound alarms or e-mail notifications can also be triggered by this event.

Extended Recording Functions for T24M Models

In software version 4.1.1.7 for T24M models, the recording functions beyond the new mailbox functions for the operation of an IP Video Door Station were limited in comparison to the versions 4.0.4.x. These limitations do not exist any longer, i.e., the same settings as in versions 4.0.4.x can be applied. Some restrictions may occur when operating a T24M with activated mailbox function within a IP Video Door Station. The mailbox functions cannot be combined freely with other recording settings. In this case, warnings will be shown in the Setup Menu > Recordings dialog.

Other Enhancements

Support of D14Di-Sec-DNight-FIX

Version 4.1.1.21 supports this new D14Di Day/Night model. It features a day and a night image sensor, pre-installed on a special lens bracket, with both lenses pointing in the same direction (as in an M12D).

VoIP Home View for T24

For T24 models, a previously defined PTZ position can now be used as the default view (home view) on a VoIP/SIP phone. This home view can be defined using the new VoIP Home View softbutton, which is available on the camera live screen in a web browser. During a video SIP connection to the camera, the home view can be selected by pressing the "0" key at the phone.

Changed Camera Reboot Behavior

The automatic camera reboot, which is activated by factory default, is now executed weekly on Mondays sometime between 3am and 4am.

Integration of SNMP for Network Configuration Queries

Support for SNMP (SNMPv2c or SNMPv3) has been added so that it is now possible to obtain information on the camera's network configuration such as host name, IP address, etc. using certain network management tools (e.g. HP OpenView). To activate and configure the service, open Admin Menu > Network Setup > SNMP Configuration. Note that this information is read-only.

(This enhancement had already been included in version 4.1.0.8 for D14Di models and in version 4.1.1.7 for T24M models.)

Focusing Aid with Sound Support

The focusing aid has now been supplemented with sound output so that the lens focus can be adjusted without having to see the live image from the camera. Once activated, the camera emits a continuous tone that changes pitch as the focus changes.

(This enhancement had already been included in version 4.1.0.8 for D14Di models and in version 4.1.1.7 for T24M models.)

Bugfixes

• Full Image recording with switching of image sensors
  Using Full Image recording on dual camera models now allows switching the image sensors. This includes the Auto setting for automatic day/night switching, independent of the live image.

• Rotation of 90 and 270 degrees with improved image quality
  When rotating the camera image by 90 or 270 degrees, the image was slightly zoomed and had lower quality.

• Double phone call with activated forwarding service on a Grandstream
  If the forwarding service had been activated on a Grandstream IP video phone, the door bell triggered two calls to the target device of the forwarding service.

• Problems with access restriction by a supervisor
  Defining a temporary access restriction by a supervisor caused problems for the input of time ranges. In a few cases, the time ranges entered were not accepted by the system.

• Using the $(SEN.VM1) and $(SEN.VM2) variables for text displays
  When using the $(SEN.VM1) and $(SEN.VM2) variables, the ID values of the video motion windows that triggered the last event are now displayed properly.

• Meta events did not trigger
  The Event Logic for defining and triggering meta events did not always work reliably.

• RS232 support for USB-to-FTDI adapter
  Using the RS232 interface with the mini USB port of the camera and an FTDI adapter did not work properly.

Known Limitations

• "Object Tracing" option
  The Object Tracing (OT) option in the Text & Display Settings dialog in the Setup Menu is not available in this version.

• Limitations when talking back and forth using MxEasy on a computer
  The audio quality in intercom mode when using MxEasy on a computer largely depends on the audio components of the PC (hardware and software). Using a headset typically produces the best results if the input level of the microphone is set to a lower value. Note that you definitely need to adjust the audio settings to the individual situation. However, it is not recommended to increase the sensitivity of the camera microphone (default = Low), since this release still reduces the quality of the echo cancellation on the camera.

• Window definition for D14Di-Sec-180° models
  For this model, exposure windows, video motion windows, and obscured area windows can only be defined in the Full Image display mode.

• Translations
  Some translations are missing on all language versions. At the moment, the Admin Menu > Video Door Station > Manage Users dialog is only available in English, but with an online help in German. The online help for this dialog will also be created as an independent document and made available at the MOBOTIX website for downloading.

Software Release MX-V4.1.1.7 (Release) – only for T24M Camera Models

Creation Date: 2011-12-15

Publishing Date: 2011-12-22

Notes on Upgrading – PLEASE READ CAREFULLY:

• This software version has been released only for T24M camera models!
• This software version contains important enhancements and improvements. Before running the upgrade, you should be aware of the changes and the limitations of this version (see Known Limitations section below), since downgrading to older versions 4.0.4.x is subject to certain restrictions. Make sure that you save the current camera configuration to the computer before running the upgrade.
• When upgrading the software, the camera automatically adjusts the camera configuration in several sections. Note that you cannot use such an adjusted and stored configuration on cameras with software releases lower than 4.1.x.

Enhancements and Improvements

Support of the New T24 Door Station Modules

This software is the first release to support the new Keypad and Security Door Opener modules. It allows to operate the MOBOTIX IP Video Door Station (T24M camera module, Keypad and Info module) together with a Security Door Opener. This means that the following functions are available:

• Initial operation without computer and operation of the system in combination with a Grandstream GVX3140 IP video phone.
• Convenient and easy-to-use auto configuration feature
• Access control using RFID cards and PIN codes
• Support of SIP phones and MxEasy for answering the door station
• Audio/video connections with intercom and remote-control functions for opening the door and switching the lights
• Audio/video answering machine (mailbox feature)
• Secure encrypted communication between MxBus modules
• Backup power supply (provides for keyless entry even on power failures)
• System backup and restore features
• Various door bell sounds

Notes on the Documentation

For more information on installation, configuration, initial operation and on using such a door station with the modules mentioned above, see the documents listed in the following (also available for download on www.mobotix.com in the Support > Manuals section):

• T24 System Manual Part 1: System Overview and Installation
• T24 System Manual Part 2: Initial Operation and Configuration
• T24 Quick Guide

Remark:
The T24 System Manual Part 3: User Guide is still under development.

Notes on Using Siedle Components

• A T24M camera module can still be used together with Siedle modules (e.g. bell module). It is likewise possible to use MOBOTIX components ()e.g. Keypad and Security Door Opener) together with Siedle components (e.g. bell module). This is also described in the T24 System Manual Part 1: System Overview and Installation.

• The initial operation including the auto configuration feature described in the T24S System Manual is still valid. Note, however, that the description of the doorbell configuration using a Grandstream IP phone or MxEasy has changed! In order to configure a Siedle bell module, it is required that you execute the following steps using the onscreen menu of the Grandstream phone:

  • Press '*' key 3x => Setup menu
  • Press '4' key => Admin Setup menu
  • Press '3' key => Doorbell + Mailbox menu
  • Press '6' key => Additional bell buttons menu
  • Press the key '1' to '4' (to select a bell button) => configure the phones and mailboxes for the selected bell in the next dialog.

  If you have additional questions, please contact the MOBOTIX support (support@mobotix.com).

Notes on Changes in the "Admin Menu" Dialogs

In order to accommodate for the changes of the new functions mentioned above, the following dialogs in the Admin Menu have been adjusted or added:

• New Video Door Station section with these dialogs:
  • Manage Users
  • Automatic Configuration
  • Entry Permissions
  • Entry Log
• Changed dialogs in the Audio and VoIP Telephony section:
  • SIP Client Settings
  • SIP Server Settings
  • Outgoing Calls Settings
  • Incoming Calls Settings
• Changed dialogs in the Hardware Configuration section:
  • Managing MxBus Modules
• Changed dialogs in the Configuration section:
  • Backup and Restore

For further information on individual changes, please read the online help topics of the dialogs!

Event Profiles

In order to increase the flexibility and to prepare the camera for additional events based on advanced image analysis, the event control has been changed according to the same principles as the action control. You can now use seven event groups with 20 event profiles each; each group has its own name and represents its own definition. In addition, there are two new events: the Event Group Termination in the Internal Events group as well as the Logical AND Event (in the Meta Events group).

This new approach allows creating up to 20 video motion events or video motion groups and in turn execute specific actions for these events.

The event profiles of the factory default correspond to the events of previous software releases. Note that the event control based on profiles is not backwards-compatible with the predecessor versions of this release. It is thus not possible to reuse older configurations of T24M cameras without checking and reconfiguring the entire event control part of the configuration. Another limitation applies to the video search and configuration capabilities of MxCC (up to V2.5.0.2) and MxEasy (up to V1.4.1); only the upcoming releases of both applications will fully support these features.

Please note:
With the introduction of event profiles, all dialogs in the browser user interface in Setup Menu > Event Control section have changed. For further information on individual changes, please read the online help topics of the dialogs!

Other Improvements

Announcements via Camera Speaker are also Recorded

If a T24 door station is recording while a conversion is in progress, the door station will also record the tone of the remote station from the camera speaker.

Simplified DTMF Control

After a SIP audio connection (without SIP video) has been established to the T24 door station, the Open door and Switch light actions can be executed using the corresponding keys of the phone. Note that you need to use the same keys as on the Grandstream IP phone's on-screen menu, followed by the '#' key:

• '1' + '#' = open door
• '3' + '#' = switch light

Configurable Display of "Missed Calls"

You can now open Admin Menu > SIP Server Settings and activate the display of "missed calls" if calls from a door station to a Grandstream IP phone has not been answered. Note that this only works if the camera uses its internal SIP server to establish SIP connections.

Updated Time Zones

The time zone definitions of this release are dated October 2011.

Bugfixes

• Stripes sometimes appeared in the image
  T24M models sometimes generated images with stripes or mirrored image sections.
• Calls to Grandstream IP phones sometimes failed
  SIP calls from the door station to a Grandstream or a different SIP phone sporadically failed.

Known Limitations

• Restricted standard recording functions as compared to release 4.0.4.x
  Except for the new mailbox recording functions, recording is now limited in the following areas (compared to release 4.0.4.x):
  • Snapshot Recording is not available.
  • The following applies to Event Recording:
    Recording frame rate is always Maximum fps, recording time is 120s, recording always includes audio, no pre-alarm, no recording after stop, no terminate recording (TR)
  • The following applies to Continuous Recording used together with Event Recording:
    Event recording frame rate is always Maximum fps, event recording time is 120s, recording always includes audio, no event recording after stop, no event terminate recording (TR)
• Limitations when Talking Back and Forth using MxEasy on a PC
  The audio quality in intercom mode when using MxEasy on a PC largely depends on the audio components of the PC (hardware and software). Using a headset typically produces the best results if the input level of the microphone is set to a lower value. Note that you definitely need to adjust the audio settings to the individual situation. However, it is not recommended to increase the sensitivity of the camera microphone (default = Low), since this release still reduces the quality of the echo cancellation on the camera.
• Testing the Doorbell after Auto Configuration only Possible After Training the Keypad
  The testing of the doorbell as described in the T24 System Manual Part 2, section 2.1.4, Functional Test, item 4 if a Keypad is part of the system can only be tested once the keypad has been trained (i.e., you need to enter a Super PIN and train the Admin card at the Keypad).
• Configuration Using MxEasy only Fully Supported in Version 1.5.1
  The assignment of the signal inputs for door sensor and lock sensor can only be configured using the upcoming release of MxEasy 1.5.1. Until then, you need to use the on-screen menu of the Grandstream IP phone or a web browser to configure this setting.
• Event Profiles in MxControlCenter only Fully Supported in Version 2.5.1.1
  Configuring video motion windows and other events of cameras running software release 4.1.1.7 or higher is only fully supported in the upcoming release of MxControlCenter 2.5.1.1.
• Translations
  Some translations are missing on all language versions other than English and German.

Software Release MX-V4.0.4.28 (Release) – for all Q24M, D24M, M24M and T24M Cameras

Creation Date: 2011-10-19

Publishing Date: 2011-11-25

Attention:

• You can use this software version for all MOBOTIX Q24M, D24M, M24M and T24M cameras!
• If you intend to use older software versions, please read the release notes for release 4.0.4.18.

Enhancements and Improvements

Improved Password Definition

Camera passwords can now be between 5 and 99 characters in length. In addition, the hash algorithm used to store the passwords in the camera configuration has been improved.

Time Zones Updated

The definitions of all global time zones have been updated.

SSL/TLS for Sending E-Mails Can Now Be Switched Off

When using older mail servers, which do not support SSL/TLS connections for sending e-mails, you can deactivate SSL/TLS in the camera configuration. To do so, add the following line in section mail of the configuration file:

tls=0

Option Added to Prevent Web Crawling

The Admin Menu > Language and Start Page dialog now offers the additional option Web Crawler Restrictions. It allows preventing web crawlers such as Googlebot and other search engines from indexing all camera websites.

Subfolders of Shares on CIFS File Servers Can Be Used as Storage Targets

The camera can now use subfolders of a shared folder as storage target for the camera recordings. Up until now, the camera was only able to use the shared folder itself and not its subfolders.

Bugfixes

• Problems with camera reboot after connection with CIFS file servers failed
  When trying to reboot a camera that had been storing its recordings on a file server and which experienced connections problems, the camera sometimes did not respond to the reboot command (neither from a web browser nor from an application). In order to reboot the camera, it was necessary to briefly disrupt its PoE power supply.
• ExtIO connection problems after camera reboot
  After rebooting the camera, the connection to an attached ExtIO was sometimes not restored automatically.
• Not more than three concurrent VoIP calls possible
  A camera (including the T24M models) could not place more than three concurrent VoIP calls. This limitation has been removed.
• State of the signal output after camera reboot not restored
  After rebooting, the camera did not restore the setting of the signal output that had been set before.
• Variable with different values for the same event
  When using the $(TMS.TIMET) variable for displaying or processing an event time in different actions (e.g. FTP and network message (IP Notify)), the variable showed different results for the different actions.
• Automatic reduction of image sizes when placing SIP video calls
  If the data rate had been set to 150 kbit/s, the camera automatically reduced a TV CIF image to QCIF without asking. This has been changed by setting the default data rate to 500 kbit/s. If the data rate is 150 kbit/s or less, the camera reduces the image size to QCIF and will does not show the on-screen menu any more.
• Problem when trying to establish a SIP connection via the internal SIP server of the camera
  When trying to establish a SIP connection via the internal SIP server of the camera, some SIP clients had problems since the camera had been sending the "User Agent" header entry of the SIP invitation twice.
• Variable ^Ld not updated when using full image recording
  When using the ^Ld variable to show the time of the last event in the image, the camera did not update the variable if it had been set to full image recording.
• Variable $(SEN.MIC) showed a faulty value
  When using the $(SEN.MIC) variable, the software displayed the microphone trigger value instead of the current level.

Software Release MX-V4.0.4.19 (Release) – for all Q24M, D24M, M24M and T24M Cameras

Creation Date: 2011-04-26

Publishing Date: 2011-05-13

Attention:

• You can use this software version for all MOBOTIX Q24M, D24M, M24M and T24M cameras!
• If you intend to use older software versions, please read the release notes for release 4.0.4.18.

Enhancements and Improvements

Enhancements for the Integration of MOBOTIX Cameras into the New Releases of MxControlCenter and MxEasy

This release contains the adjustments and enhancements in the MxPEG video stream that are required for the new features of the upcoming software releases MxControlCenter V2.5 and MxEasy V1.4. Among other new features, the new versions of the two applications will allow searching for video motion in recordings (post video motion detection, e.g. in continuous recordings).

Bugfixes

• Variable for microphone value displayed wrong value
  When using the '$(SEN.MIC)' variable, the software displayed the microphone trigger value instead of the current microphone (input) level.
• Additional camera reboot when streaming while rebooting
  When other applications (e.g. MxControlCenter) had been trying to get a live video stream from the camera while it was still rebooting, the camera sometimes rebooted again.
• Image errors after camera reboot
  On rare occasions, the camera stopped image generation about five minutes after rebooting.
• System instability when running for extended periods of time and using MxControlCenter's Layout Sequencer
  When a camera had been running without regular reboots and had been used by the Layout Sequencer in MxControlCenter, this sometimes resulted in an instable system and to camera reboots.

Software Release MX-V4.0.4.18 (Release) – for all Q24M, D24M, M24M and T24S Cameras

Creation Date: 2010-09-09

Publishing Date: 2010-09-22

Attention:

• You can use this software version for all MOBOTIX Q24M, D24M, M24M and T24S cameras!
• Note that you can only install software releases 4.0.4.5 or higher on T24S camera models.
• Note that you can only install software releases 4.0.2.27 or higher on Hemispheric cameras with B/W sensors.
• Note that you can only install software releases 4.0.2.x or higher on M24M camera models.
• Note that you can only install software releases 4.0.1.x or higher on Q24M and D24M camera models. Software releases with a lower version number cannot be installed on these cameras.

Enhancements and Improvements

Action Profiles and Action Groups

If the camera detects an event (video motion, signal input, etc.), it can execute specific actions (e.g. phone call, FTP transfer, e-mail, network message, sound). The following describes how these camera actions have been redesigned and enhanced:

• Action Profiles
  Before the camera can use any actions, you need to set up the corresponding action profiles. Besides using the existing profiles for phone calls, e-mails, FTP file transfers and network messages, you can now also use the new action profiles for playing back sounds and for setting the signal outputs. The Action Groups (see below) combine the action profiles as one or more Actions for execution later on.
• Action Groups
  One action group allows combining different events with one or more actions (= existing action profiles). If the camera detects one of the selected events, it can execute the actions simultaneously or consecutively (including subsequent evaluation of the success). Note that you can arm (i.e. activate) the individual action groups either manually in the Action Group Overview dialog, or automatically using the camera's signal inputs (e.g. key switch) or time table programs (weekly schedules).

  Note that the number of action profiles as well as the number of action groups are "virtually" unlimited; you can define up to 20 action profiles per type (phone call, e-mail, FTP transfer, network message, etc.) and up to 20 action groups. For each action group, you can define up to 20 actions.

This approach allows sending ten different network messages in different action groups and to trigger these action groups using totally different events. Likewise, you can send ten different network messages to ten different recipients if the camera detects the event selected in one action group.

Enhancements for VoIP/SIP Telephony

The SIP video telephony functionality of the camera has been enhanced and improved in various ways.

• Camera with integrated SIP server for local VoIP/SIP connections
  If you would like to establish local VoIP/SIP connections between SIP-capable devices (e.g. a MOBOTIX camera and several Grandstream IP phones) you can now activate the camera's SIP server (partysip). Open the Admin Menu > SIP Server Settings dialog to activate and configure the SIP server.
• Enhanced OnScreen menus
  After establishing a SIP video connection, the camera automatically shows the OnScreen menus. These menus have been redesigned from scratch and further improved. In addition, the camera can display a special help dialog for every regular dialog.
• Support of H.264 video codec
  SIP video connections can now use the H.264 video codec besides the H.263+ codec. Open the Admin Menu > VoIP Settings dialog to configure the video codec to use.

Special Functions for Supporting T24M Cameras

For T24M camera models, this software version adds the following new features:

• Auto Configuration
  This feature provides for easy configuration of a local network (one T24M and several Grandstream IP phones), which includes finding and applying the appropriate SIP settings. Once auto configuration has been performed, you can establish SIP video connections from the camera to the Grandstream IP phones and vice versa. For additional information on this topic, see the T24S System Manual (www.mobotix.com in the Support > Manuals section).
• Signal Inputs
  When used in a Siedle Vario system, the T24S camera supports up to 16 signal inputs for connecting bell modules, door contacts, PIR modules, etc. As before, these signal inputs are configured in the Setup Menu > Event Settings dialog.

Other Enhancements and Improvements

RS232 Support using USB FTDI Adapter

When attaching a USB FTDI adapter, you can also use the USB interface of the MOBOTIX cameras Q24M, D24M and M24M to control devices via an RS232 interface. This allows controlling a mechanical pan/tilt head or a weather station from the camera models mentioned above, for example. In order to use this interface, you need to connect the USB FTDI adapter to the camera's USB interface in the Admin Menu > Manage Hardware Expansions dialog. Once this has been done, you can configure the RS232 interface in the Admin Menu >Serial Interface and Modem Setup dialog.

Using the Camera as DHCP Server

This software version allows using one camera in a local network as a DHCP server (e.g. for other cameras or IP phones). To activate the camera's DHCP server, open the Admin Menu > Ethernet Interface dialog and find the corresponding option in the BOOTP/DHCP section. This feature is used by the auto configuration mechanism of T24M cameras, for example, in order to set up a local network (one T24M and several Grandstream IP phones) where the T24M provides the DHCP service. Note that you can set additional options regarding NAT (Network Address Translation) in the Routing dialog.

E-Mails via Encrypted Connections (SSL/TLS)

When using this software version, the camera automatically sends e-mails via encrypted connections (SSL/TLS). This does not require any further configuration of the camera.

Bugfixes

• Logo profiles in image profiles did not work properly
  Using different logo profiles in different image profiles did not properly. When activating a logo profile for use in the image profiles, the logo appeared in all image profiles in the same image format.
• Video motion detection (VM) on B/W image sensors and low light conditions was not sensitive enough
  When using a B/W image sensor (1 megapixel) under low light conditions (approx. 1 Lux or less), the video motion windows had not been sensitive enough if noise filtering was activated (by default). If VM noise filtering had been explicitly deactivated in the corresponding VM definition line by setting the $noiseadjust=0 variable, the error did not occur. This only applied to the predecessor version 4.0.4.5 of the T24M camera. For all other cameras, this error has already been fixed in version 4.0.2.33.r2.
• Additional protection against Cross-Site Scripting (XSS)
  In order to fulfill the PCI Compliance requirements (PCI = Payment Card Industry), additional websites of the camera have been hardened against Cross-Site scripting.
• Simultaneous switching of several signal outputs via HTTP API did not work properly
  When using the rcontrol API function with the outmask=0x3 parameter in order to switch two signal outputs at once, the camera only switched one signal output.
• Full image recording reduced JPEG quality when camera is disarmed
  When activating full image recording while the arming switch for recording was deactivated (i.e. the camera did not record), the live images were sometimes shown in lower JPEG quality.
• Host entry added to network messages with HTTP 1.0 header
  When sending network messages using the HTTP protocol, the camera now adds a host entry to the header.
• Using custom sizes in image profiles did not work properly
  When using custom sizes in image profiles, the camera did not evaluate the size definition parameters properly, resulting in images that had not been properly scaled.

Known Limitations

• Rotation of 90 and 270 degrees cannot be combined with Full Image storage mode
  If the camera image is rotated by 90 or 270 degrees, the camera automatically deactivates Full Image storage and the camera records the live image. To alert the user of this, the camera will display an error message in the image.
• Problems with Windows 2008 servers when using CIFS NTLMv2
  When using CIFS with the NTLMv2 option on Windows 2008 servers, the cameras are sometimes unable to connect to the server.
• ActiveX PTZ with joystick via proxy server
  When accessing the camera via a proxy server, the joystick control does not work in combination with the ActiveX control.
• Network messages cannot be configured using MxControlCenter
  From this version on, you cannot use MxControlCenter to configure network messages from the camera for alerting an MxControlCenter application or a different recipient. This limitation is valid for all MxControlCenter versions up to 2.4 and will be fixed in version 2.5.
• Flickering images in Firefox browser
  When using versions 3.6.0 to 3.6.6 of the Firefox web browser, the ServerPush browser mode produces flickering images. In this case, you can set the Browser Quick Control to JavaScript. It is recommended, however, to update Firefox to the newest version.
• Translations
  Some translations are missing on all language versions other than English and German.

Software Release MX-V4.0.2.33.r2 (Release) – for all Q24M, D24M and M24M Cameras

Creation Date: 2010-07-01 (originally 2010-03-31)

Publishing Date: 2010-07-08 (originally 2010-04-30)

Note on the creation and publishing dates

• This version had been originally created on Mar 31, 2010, and published on Apr 30, 2010 as MX-V4.0.2.33. After the end of the signature's lifetime, this version had been recreated and published without any other changes and a new signature on May 17, 2010. After installing, version MX-V4.0.2.33 shows a Creation Date of 2010-03-31 (see Admin Menu > System Information > Hardware and Release Information). Note that the older version cannot be installed as the signature is invalid.
• On Jul 1, 2010, this version was recreated as MX-V4.0.2.33.r2 with an updated video motion detection; it was published on Jul 8, 2010. After installing, this versions shows a Creation Date of 2010-07-01 (see Admin Menu > System Information > Hardware and Release Information).

Attention:

• You can use this software version for all MOBOTIX Q24M, D24M and M24M cameras!
• Note that you can only install software releases 4.0.2.27 or higher on Hemispheric cameras with B/W sensors.
• Note that you can only install software releases 4.0.2.x or higher on M24M camera models.
• Note that you can only install software releases 4.0.1.x or higher on Q24M and D24M camera models. Software releases with a lower version number cannot be installed on these cameras.

Enhancements and Improvements

Support of Hemispheric cameras with B/W image sensors and improved B/W image quality

This software release can be used on all Q24M, D24M and M24M camera models. This specifically includes the models MX-Q24M-Sec-N11 and MX-M24M-Sec-N11. From this release onwards, the software supports the same Hemispheric features (display modes and vPTZ actions) as in the corresponding models with daylight (color) image sensors.
In addition, this release brings further improved image quality and image sharpness for all models with B/W image sensors.

New MxPEG ActiveX Control V1.6.3.0

This version achieves better performance when using free scaling of the displayed video thanks to additional options.

Bugfixes

• Connection to ExtIO lost after rebooting the camera
  After rebooting the camera, the connection to an attached ExtIO (USB or IP variant) got lost in some rare occasions.
• Faulty images when using full image recording
  If different resolutions had been set for the live image and full image recording, the recordings sometimes contained faulty images.
• Missing Quick Controls
  The Backlight Correction, Color Saturation and Sharpness entries had been missing in the Quick Controls.
• Wrong PTZ position stored using combined display modes
  When using combined display modes, such as Double Panorama, the software did not store the position of the current image section if the position had been stored using the OnScreen Control. Instead, the software had stored the vPTZ coordinates of the second but last position. This problem did not occur when MxControlCenter, MxEasy or the http API had been used to store the position.
• JPEG quality in the live image too low when using full image recording
  The following combination of configuration settings produced live JPEG images with lower JPEG quality: Activated full image recording, recording not armed, active image profile (e.g. for FTP transfers).
• Reduced Video Motion detection (VM) sensitivity with B/W image sensor under low illumination conditions
  On cameras with 1 megapixel B/W image sensor, low illumination (1 Lux or less) could result in reduced sensitivity if VM noise filtering was active (factory default). The error did not occur if the $noiseadjust=0 variable to deactivate noise filtering had been used in the VM window definition line. This error only occurred in software versions 4.0.2.23 and 4.0.2.33 and has been corrected in version 4.0.2.33.r2.

Known Limitations

• Rotation of 90 and 270 degrees cannot be combined with Full Image storage mode
  If the camera image is rotated by 90 or 270 degrees, the camera automatically deactivates Full Image storage and the camera records the live image. To alert the user of this, the camera will display an error message in the image.
• Problems with Windows 2008 servers when using CIFS NTLMv2
  When using CIFS with the NTLMv2 option on Windows 2008 servers, the cameras are sometimes unable to connect to the server.
• ActiveX PTZ with joystick via proxy server
  When accessing the camera via a proxy server, the joystick control does not work in combination with the ActiveX control.
• Translations
  Some translations are missing on all language versions other than English and German.

Software Release MX-V4.0.2.23 (Release) – for all Q24M, D24M and M24M Cameras

Creation Date: 2010-05-17 (originally 2009-12-08)

Publishing Date: 2010-05-17 (originally 2009-12-09)

Note on the creation and publishing dates
This version had been originally created on Dec 8, 2009, and published on Dec 9, 2009. After the end of the signature's lifetime, this version had been recreated and published without any other changes and a new signature on May 17, 2010. After installing, version MX-V4.0.2.23 shows a Creation Date of 2009-12-08 (see Admin Menu > System Information > Hardware and Release Information). Note that the older version cannot be installed as the signature is invalid.

Caution: You can use this software version for all MOBOTIX Q24M and D24M cameras! MOBOTIX Q24M and D24M cameras will not accept software with a lower version than 4.0.1.

Caution: You can use this software version for all MOBOTIX M24M cameras! MOBOTIX M24M cameras will not accept software with a lower version than 4.0.2.

Enhancements and Improvements

Improved Exposure Control

This software version contains a completely redesigned Exposure Control mechanism which has made substantial improvements in the following areas:

• Faster reaction of exposure control to changes in illumination
  The exposure control now reacts substantially faster to changes in illumination than the previous version of the software. The camera now delivers an image with optimum exposure quicker than before. This is valid particularly for large changes in illumination, e.g. when turning on a light in a dark scene.
• Improved white balance
  An improved white balance now produces images with more realistic colors in scenes that have a large portion of only one color, e.g. a golf range. The improved white balance also eliminates color distortions and false color images which sometimes resulted from strong changes in illumination.
• Improved auto contrast
  The auto contrast now automatically adapts to scenes with large differences in illumination (e.g. dark shadows in the lower part of the image with a bright sky above) and substantially improves the contrast of this kind of scenes. In addition to this, auto contrast cannot only be switched off or on as before, but now has three settings: Standard, Extended and Aggressive. As before, you can select the settings in the Setup Menu > Exposure Settings dialog. This dialog also contains an explanation of these three new auto contrast methods.

Image Rotation by 90 and 270 Degrees

The images of non-hemispheric camera models can now also be displayed rotated by 90 or 270 degrees. The setting for the image rotation can be made in the Setup Menu > General Image Settings dialog. This dialog also allows to selectively pivot the 4:3 aspect ratio of the rotated image so that the aspect ratio of the resulting image is either 4:3 or 3:4 as desired. With a 3:4 aspect ratio, the complete image content is visible because of a 1 to 1 width-to-height relationship, but when the aspect ration is not pivoted with the image rotation, the camera only shows a centered section of the rotated image.

Note:
This setting will lead to slightly reduced frame rate and slightly lower image quality compared to the original image since the camera needs to convert the image. The difference between the original image and the converted one is about equal to the image resulting from distortion correction for L11/L22 lenses compared to the original image.

Other Improvements in Image Settings

• JPEG files can now be used for logos
  In addition to .BMP and .PNG files, .JPG files can now also be created and used for definition of logos in the camera.
• PTZ positions now available in Image Profiles
  The different display modes (Normal, Panorama, etc.) along with pre-defined vPTZ positions can now be used in Image Profiles. Open the Admin Menu > Image Profiles dialog and select one of the vPTZ positions defined before via the Quick Controls from the View selection box.
• Visualization of exposure windows as a clear rectangle in darkened window
  When defining exposure windows, the window is displayed as a rectangle with a clear view of the exposure area inside a darkened frame. This does not affect the optional permanent highlighting of exposure windows with a green frame.
• Enhanced Preview API functionality
  The http API functions for retrieving a preview image stream or single images from the camera have been enhanced. The 'preview' parameter can now be combined with other parameters to specifically retrieve camera images with smaller resolutions (using the 'size' parameter), lower JPEG quality (using the 'quality' parameter) or reduced image rates (using the 'fps' parameter; only relevant for an image stream). Thus, applications can fetch a substantially reduced data stream from the camera, if you are adding a camera with limited network bandwidth, for example. The extensions are valid for the following cgi programs:

  http://<camera ip>/cgi-bin/image.jpg?preview
http://<camera-IP>/cgi-bin/faststream.jpg?preview
http://<camera ip>/control/faststream.jpg?preview
http://<camera ip>/control/event.jpg?preview

  Please refer to the camera's online help if you would like more information on this topic.

Improvements to Data Storage

• Recording to Flash Devices Can Also Use Storage Limits
  When recording to MxFFS-formatted Flash media, it had not been possible set storage limits for storage size, keep time and number of sequences. The camera always used the complete storage capacity available on the MxFFS device. This software version fully supports the storage limits when storing on MxFFS-formatted Flash media. For example, you can set up continuous recording, but only keep the last 30 minutes of the recording if the workers council has asked to do so.
• "Reserve Storage" to prevent load peaks on external file servers
  The Storage on External File Server / Flash Device dialog now contains a Reserve Storage field, which is visible after clicking on the More button at the bottom of the dialog. If the camera detects a possible overload on the file server used for recording (storage times are too high), it will add the reserve storage space to the maximum storage space that is used for recording. Since the camera uses the storage space like a ring buffer, it will stop all delete operations, because there is enough space available. File deletion will only start if the defined reserve storage has been filled up or the file server storage times have dropped to normal levels. Since deleting many files at once can overload a file server, this strategy can improve the storage behavior of the camera in many cases.
• Recording symbol is disabled by default
  The dot (or ball) recording symbol used to display the current recording status in the upper right corner of the camera image is now disabled by default. Open the Setup Menu > Recording dialog and activate the Recording Status Symbol option to display the symbol again.

Extended Hemispheric Functionality

The functionality of Hemispheric camera models, i.e. cameras equipped with an L11 lens (Fisheye), has been changed and extended as follows:

• New default settings
  Hemispheric camera models are now factory-preset for wall mounting together with the Panorama display mode.
• Floor mount
  Certain application situations require a mounting type other than Ceiling or Wall and therefore a Floor mounting type has been implemented. The same display modes are available as when using the Ceiling mounting type. Using this mode for cameras mounted on their back pointing upwards, results in an image that is natural and not turned upside-down. In addition, you can use the joystick as usual.
• Horizon correction
  If a Q24M camera has been mounted on a wall, the delivers a Panorama image that is slanted, i.e. the "horizon" of the image is not parallel to the scene. The new horizon correction of the camera allows correcting such a slanted image. To correct the image, open the interactive OnScreen Control for Panorama correction. The OnScreen Control has been expanded by an additional horizontal control bar at the lower border. Clicking into this bar will tilt the image left or right until the image horizon is level again. This control allows correcting images that are slanted up to 30 degrees in either direction.

Improved Connections to ExtIOs

• Use of audio signals
  When connecting an ExtIO to the camera, the camera will not be forced to use the ExtIO's audio signals. Instead, you can decide for both speaker and microphone individually, whether the camera devices or the ExtIO devices should be used.
• Improved Ethernet connection
  When using camera software version 4.0.2.23 with the new ExtIO firmware version 1.1.0.9, the Ethernet connection to an ExtIO is much more robust against interruptions than previous software versions. Also, if an interruption of the Ethernet connection cannot be avoided, the reconnect times are much shorter than before.

  CAUTION:
  It is highly recommended to update the ExtIO firmware to version 1.1.0.9 if you are updating the connected camera to software version 4.0.2.23!

Extended LED Signaling

The signaling of the camera LEDs had been expanded to include two new settings for the Main Switch in the Admin Menu > LED Setup dialog:

• Standard Configuration
  The camera uses a permanently lit LED 0 to signal that it is running. In case of an error, this LED will blink. LED 1 signals the different recording modes. All other LEDs are off. This is the new factory default setting.
• Transparency
  In this mode, LED 0 flashes twice every three seconds. In addition to the recording status, LED 1 is signaling live image access. This mode is special as it is easy to recognize by looking at the blinking pattern, if the camera allows live access and to check the recording status of the camera.

New MxPEG ActiveX Control V1.6.2.3

• Changed signing method
  Since the signing method has been changed for the ActiveX control, it is easier installed in Internet Explorer.
• New Proxy="auto" property
  Setting this property will force the ActiveX control to use the proxy settings of Internet Explorer for its own network connections.
• New LoginPrompt property
  This property controls how often you can enter wrong login credentials before the control locks up. The property takes values equal to or larger than 0 (zero).

Other Enhancements and Improvements

• All password field now masked
  The password fields in all configuration web pages are now masking the entered characters. Clicking on the lock icon next to the field will show the password in regular text again.
• Maximum number of users and user groups increased
  Up to 25 different user groups and a maximum of 100 users can now be created and administered.
• Quick Controls now show the current values
  The Quick Controls have been changed to show the current settings. Before, some Quick Controls had shown Select instead of the current value.
• VoIP connections with H.263+
  SIP video connections are now using the newer codec H.263+ since it delivers better quality (was H.263 before).
• System messages after a reboot
  Up until this release, a camera reboot deleted all system messages, which meant that you did not see the old messages any more when opening the Admin Menu > System Messages dialog. The camera now stores existing messages before a reboot so it can display the messages again in the System Messages dialog.
• Additional IL2 event
  The illumination of the camera's surrounding can now be used as an additional event trigger Illumination (IL2), which can be combined a second trigger condition. Thus, it is now possible to configure an event trigger based upon a minimum threshold in combination with a maximum threshold using both IL and IL2.
• Display of the Stop icon upon detection of possible hardware defects
  If the camera detects a possible hardware defect, it displays the Stop icon in the upper left corner of the live image. For more information on the meaning of this icon and how to hide it, see the Online help of the camera on the Live Screen page (http://<camera ip>/help/help?page-live).
• Report.dmp for Dual cameras
  The report.dmp camera report now contains a current dual image on dual lens models.
• Documentation of the HTTP API completed
  Among other enhancements, the API documentation now also contains the remoteconfig.cgi API function, which allows reading and writing sections of the camera configuration file.

Bugfixes

• Problems using file server recording in combination with an ExtIO
  When using an ExtIO, the camera was unable to properly initialize file servers. In this case, the camera was unable to use the file server for recording purposes.
• Camera display in browser - cache problem
  When updating an older Q24M camera to this version, you had to empty the browser cache before you were able to see the camera in the browser. Otherwise, the Quick Controls above the live image sometimes stayed empty and the live image stopped.
• Problems with recordings using CIFS or NFS on file servers with large volumes
  Recording sometimes failed on CIFS or NFS file servers with large volumes of more than 2 billion blocks. These applied to volumes that had at least 2 TB size and a block size of only 1 kB.
• ActiveX control and mouse pointer on Internet Explorer
  On some combinations of Windows operating systems and the Internet Explorer, the mouse pointer sometimes retained the crosshairs look even though the pointer had been moved away from the camera image (i.e. the ActiveX control). If this was the case, the pointer could not be used to operate the other page elements. This problem could be fixed by displaying the context menu (right-click), which had reset the mouse pointer.
• Pumping from exposure control
  In very infrequent instances, the autocorrection function would cause a "pumping" of the image if it required changes in exposure times. The camera then kept changing back and forth between a longer and a shorter exposure time and the image looked brighter and darker in rapid succession.
• Symbol display hidden on continuous recording without activated events
  When starting a continuous recording without having activated any events, the camera did not show any symbols at the bottom border of the image.

Known Limitations

• Rotation of 90 and 270 degrees cannot be combined with Full Image storage mode
  If the camera image is rotated by 90 or 270 degrees, the camera automatically deactivates Full Image storage and the camera records the live image. To alert the user of this, the camera will display an error message in the image.
• Problems with Windows 2008 servers when using CIFS NTLMv2
  When using CIFS with the NTLMv2 option on Windows 2008 servers, the cameras are sometimes unable to connect to the server.
• ActiveX PTZ and Proxy
  When accessing the camera via a proxy server, the joystick control does not work in combination with the ActiveX control.
• Translations
  Some translations are missing on all language versions other than English and German.

Software Release MX-V4.0.1.15 (Release) – for all Q24M and D24M Cameras

Creation Date: 2009-07-20

Publishing Date: 2009-07-23

Caution: You can use this software version for all MOBOTIX Q24M and D24M cameras! These camera models will not accept software with a lower version than 4.0.1.

Important Notes

• First published software for P3 models
  This is the first software release that is published for the camera models with the new PXA320 "XScale" microprocessor platform, the so-called P3 models.
• Identical user interface
  The software of the cameras with the new hardware platform is mostly identical to the software of predecessor cameras M12/D12/V12/M22M/D22M/Q22M - the so-called P2 models with respect its handling, its features and the menu structure.
• Higher performance
  Thanks to the higher performance of the P3 system platform, it also brings new platform-specific features, which would not have been possible on the P2 platform (note, that MOBOTIX will continue to support this platform). The Q24M and D24M camera models in particular are reaching twice the frame rate of their predecessors Q22M and D22M, thus achieving the maximum frame rates of 25/30 frames per second (depending on the frequency of the power network) in considerably more application scenarios when applying the corresponding settings. Generally speaking, the improved performance results in quicker responses in all aspects of using the camera.
• Support of existing configurations
  You can load existing camera configuration files of the corresponding P2 camera models without any problems. This is important when exchanging a camera or when integrating new cameras into existing systems.

The following list describes the new features, enhancements, improvements and bugfixes as compared to the software release V3.4.5.10 of the MOBOTIX M12/D12/V12/M22M/D22M/Q22M cameras based on the P2 platform.

Enhancements and Improvements

Twice the frame rates

The P3 models achieve about twice the frame rate as compared to the P2 models (with a maximum of 25/30 fps, depending on the frequency of the power network). There are no relevant changes regarding the settings required to achieve these frame rates. The improved frame rates result in more efficient applications that are using Full Image Recording and thus allow using this mode in more application scenarios. This storage mode also means that the camera has a higher processor load, which in turn may reduce the live image rates. The higher performance, on the other hand, attenuate this effect to a certain degree.

Recording on the Factory-Installed 4 GB microSD Card

The two Q24M-Sec and D24M-Sec models are delivered with a factory-installed 4 GB microSD card. The storage card has been formatted and has been set as the active recording target in the Admin Menu > Storage on External File Server / Flash Device dialog. To activate the SD card recording, simply set the Recording > Recording on Quick Control. Next, the camera immediately starts recording events using the pre-defined video motion window in the center of the live image

Q24M – Panorama Mode with OnScreen Control (OSC) for Flexible Adjustment

You can now flexibly adjust the Panorama view mode of the Q24M models to the specific scenario. To do so, select the Panorama view mode and click on the lock icon in the Quick Control bar to unlock the view mode. The camera displays a small icon in the upper left corner; click on this icon to display the so-called "OnScreen Control" (OSC) in the live image. Simply click on the different areas of the OnScreen Control to adjust the Panorama view mode. This control also allows zooming, panning and tilting the image as desired.

One speciality in this scenario is the "Panorama correction", which allows straightening tilted vertical lines. This will be important if the camera has been mounted to a wall with a downwards inclination or the image center has been tilted downwards or afterwards using the vPTZ features. Once you have adjusted the image, you should lock the view by clicking on the lock icon to prevent inadvertent changes to the Panorama view. For additional information on the OnScreen Control, see section 3.3.2, Special Q24M Configuration in the Browser, in the Q24M Camera Manual.

Variable PoE Classes

The upper area of the Admin Menu > Ethernet Interface dialog contains the new Power Supply section. Click on the Change link to change the PoE class of the camera's power supply. If you do not need accessories such as a USB stick or audio output, you can select PoE class 1 (up to 3.84 W). This means that you can attach more cameras to the same switch as if these cameras would be using the factory default PoE class 2 (up to 6.49 W). For additional information on this topic, see section 2.11.2, PoE Variables, in the Q24M Camera Manual.

Audio Codec with Echo Cancellation

The P3 models feature a new audio codec with integrated echo cancellation. The camera now supports VoIP connections in full duplex mode, which means the camera will not deactivate the microphone as soon as the camera sends sound over the speaker. This results in true bi-directional communication. Note that you can also disable this feature in the Admin Menu > Speaker and Microphone dialog for special requirements.

IMPORTANT:
This echo cancellation is only available on camera models with integrated speaker and microphone, such as the Q24M. When using the external audio devices of an ExtIO, echo cancellation will be disabled.

Improved Support of Windows File Servers

This area has been enhanced and improved in the following ways:

• New CIFS file system
  When storing on Windows file servers, the camera now only proposes the new CIFS protocol. This protocol usually also supports older storage devices that are using the older SMB protocol instead of the newer CIFS. As a consequence, corresponding option in the Admin Menu > Storage on External File Server / Flash Device dialog has been renamed to SMB/CIFS File Server.
• Compatibility to SMB configuration
  If you are loading an existing camera configuration with SMB defined as storage protocol, the camera will continue to use the old SMB protocol; this option is also visible in the Admin Menu > Storage on External File Server / Flash Device dialog.
• NTLMv2 support
  When using CIFS file servers, the camera now also supports the NTLMv2 authentication mode. This is the default option on newer Windows server systems, such as Windows 2008 Server. To activate this feature, select the corresponding option in the Admin Menu > Storage on External File Server / Flash Device dialog.

All Languages in One Package

Instead of several language-dependent software packages, you can only download one MX*.mpl software package, which contains all supported languages. This means that all languages are stored in the camera and that you can select any language at run-time.

Other Improvements

• Improved Quick Controls
  When selecting the Display Mode, Installation, Recording and Exposure Control Quick Controls, they will show the actual values instead of the unspecific Select ....
• Camera-specific certificates
  Every camera now has its own certificate, which is used e.g. for establishing https/SSL connections and for digitally signing the recordings.

Known Issues

• Camera display in browser - cache problem
  When updating an older Q24M camera to this version, you have to empty the browser cache before you can see the camera in the browser. Otherwise, the Quick Controls above the live image may stay empty and the live image may stop!
• Problems with recordings using CIFS or NFS on file servers with large volumes
  Recording will fail on CIFS or NFS file servers with large volumes of more than 2 billion blocks. These are volumes that have at least 2 TB size and a block size of only 1 kB.
  Workarounds:
  
  • If you are setting up the server, you can format the volume using a larger block size (e.g. 4 kB), resulting in a block size that is lower than the 2 billion limit.
  • If you cannot reformat the volume, you can remedy the error by using the older SMB protocol. Make sure that the configuration file contains the FS_TYPE=WIN entry in the SECTION fileserver. Note that the older SMB protocol is now again available in the dialog.
• ActiveX PTZ and Proxy
  When accessing the camera via a proxy server, the joystick control does not work in combination with the ActiveX control.
• ActiveX control and mouse pointer on Internet Explorer
  On some combinations of Windows operating systems and the Internet Explorer, the mouse pointer sometimes retained the crosshairs look even though the pointer had been moved away from the camera image (i.e. the ActiveX control). If this was the case, the pointer could not be used to operate the other page elements. This problem can be fixed by displaying the context menu (right-click), which resets the mouse pointer.
• Translations
  Some translations are missing on all language versions other than English and German.