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

General Information:

• Please download the stable customer releases of the software from www.mobotix.com in the Support > Download Center > Software Downloads section.
• Please send an email to support@mobotix.com for feedback.

top

Software Release MX-V5.4.6.7 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, T26, c26, i26, p26, v26

Creation Date: 2022-01-27

Publishing Date: 2022-02-15

Enhancements and Improvements

• Visual Alarm Profile
  In the Logos and Image Profiles section of the Admin Menu there is now an additional link Visual Alarm Profiles. This means that these profiles can be processed faster than before.
  

Bugfixes

• Bell button of a Keypad on S26 camera
  When using a S26 camera as a door station together with a RFID Keypad in "classic mode", the bell button of the Keypad could not be activated.
• Message for "Lost Sequences"
  When image storage was activated, different values could be displayed for the number of "Lost Sequences" in the Camera Status  and Admin > System Information > System Messages dialogs as well as in the File Server log file.
• Variable $(SEN.TTR.CELSIUS) in email profiles
  In some configurations, the variable $(SEN.TTR.CELSIUS) was not resolved correctly when used in e-mail profiles and only returned a space instead of the current value.

Known Limitations

top

Software Release MX-V5.4.6.3 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, T26, c26, i26, p26, v26

Creation Date: 2021-09-21

Publishing Date: 2021-09-28

Enhancements and Improvements

Enhanced Text Variables

• New temperature variables with additional formats
  For a more flexible display in the live image and better use in camera API calls, new temperature variables have been added. In addition to the existing variables
      '$(SEN.<Sensor type>.Celsius)' and '$(SEN.<Sensor Type>.Fahrenheit)'
  it's now possible to use the new variables
      '$(SEN.<Sensor Type>.<Unit>.<Format>)'.

• Unit from {'Celsius', 'C, 'c, 'Fahrenheit', 'F', 'f', 'Kelvin', 'K', 'k'}
• Format from {'INT', 'I10', ''F10', 'F41', 'F72', 'NUM'} with the following meanings:
• INT: Output as an integer with possibly negative sign
• I10: Output of the value multiplied by 10 as an integer with possibly negative sign
• F10: Output of the value as an integer with at least one place and with sign
• F41: Left-aligned output with at least 4 digits, with 1 decimal place and sign
• F72: Left-aligned output with at least 7 digits, with 2 decimal places and signs
• NUM: Output as a decimal number with decimal places with possibly negative sign - specially designed for use within JSON expressions
• Examples of a measured Thermal TR temperature value of +56.7 C°:
• $(SEN.TTR.C.INT) => "56"
• $(SEN.TTR.C.I10) => "567"
• $(SEN.TTR.C.F41) => "+56.7"
• $(SEN.TTR.C.F72) => "+56.70 "
• $(SEN.TTR.C.NUM) => "56.7"

• 'SKIP' option for text variables
  The $(<Variable>, SKIP=<Number>)' option skips the first <number> characters of the value of  <Variable> in the output. For a negative <number> the characters of the variable value are skipped from the end.
• Temperature variables for different Thermal Measurement Windows
  In addition to the variables $(SEN.TTR.CELSIUS/FAHRENHEIT)now also the variables $(SEN.TTR.0. CELSIUS/FAHRENHEIT), $(SEN. TTR.1.CELSIUS/FAHRENHEIT),... $(SEN.TTR.<(number of measurement windows)-1>.CELSIUS/FAHRENHEIT) are available to determine the specific temperature values in the individual Measurement Windows 0,... <(number of measurement windows)-1>.

Other Enhancements

• Resolutions of SIP Video Connections
  The image resolution used for SIP video telephony connections can now be set. For this purpose, in the Video Settings section of the Admin > Audio and VoIP Telephony > SIP Client Settings dialog, there is the new Video Size selection option. In addition to the Automatic value, resolutions from 128x96 up to 640x480 pixels can be selected there.

• LLDP
  In the Admin > Network Configuration > Ethernet Interface dialog there is the new IEE 802.1AB area to activate the LLDP protocol. Using this protocol, network devices such as manageable switches can detect the camera on the network and request basic information, such as the network device name and IP address from it.
  

Bugfixes

• Intrusion detection with many HTTP clients
  With intrusion detection activated for the web server, requests from many different HTTP clients caused the camera to deny every further request and no longer open web pages after exceeding a certain number of HTTP requests.
• RTSP streaming
  When integrating the camera into VMS or NVR systems via RTSP, the camera could restart after longer runtimes and the RTSP stream could not be restarted automatically afterwards.
• Password for file server
  If the password for a file server contained the string 'user', an error occurred when connecting to the file server.
  
• Full-Image recording with hemispheric cameras
  In the Full-Image recording of T26 and other hemispheric cameras with a rotated built-in image sensor, parts of the hemispheric full image on the left side were obscured by the black area.
• Variables $(ID.ET0)/$(ID.FIP)
  When using the variables $(ID.ET0)and $(ID.FIP) in this order together,  the current camera IP address was returned twice instead of the current IP address and factory IP address.
• Polygon Thermal Measurement Window
  When using polygons instead of rectangles to define Thermal Measurement Windows, activated Level Meters were partially displayed outside the polygon areas.

Known Limitations

top

Software Release MX-V5.4.0.55 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, T26, c26, i26, p26, v26

Creation Date: 2021-04-21

Publishing Date: 2021-06-02

Improvements

• Increased security for HTTPS connections (HSTS)

• Sensor configuration for D16 cameras also with 5MP sensor modules

• Audio connections via MxWeb

• Extended "HTTP Authorization Buffer"

• Push Notification for MxLive

Bugfixes

• Video delays during RTSP streaming
  Some RTSP clients could experience a delay in the video signal and a disturbed time synchronization with the audio signal during RTSP streaming from the camera.
• Image quality for RTP streams
  In the configuration of RTP streams, the values of the Quality and Minimum Quality settings were reversed, resulting in the CBR (constant bitrate) setting for Bit Rate Control being ineffective.
• Thermal variables in network messages
  When using thermal variables (e.g. $(SEN.TTR.CELSIUS)) within the text of network messages ("IP-Notify") the values of the variables were not transmitted correctly.
• Definition of e-mail profiles in the MxManagementCenter (MxMC)
  After defining an e-mail profile within the  MxMC Configuration view and storing the profile on the camera, the use of the profile within the camera resulted in an error. Only after opening the e-mail profile configuration in the dialog of the web browser and pressing the button "Set" to apply the settings again, could the profile be used error-free.
• SSL certificates
  When installing SSL certificates on the camera, problems and error messages could occur.
• SFTP connections
  For SFTP connections, the use of a port other than the standard port 22 resulted in errors.
• Variable $(EVENT. Est. ACTIVATED) in network messages
  If the above variable was used in network messages that, in case of an event, also send images before the triggering event ("pre-alarm") as an attachment, the value of the variable was not transmitted correctly.

Known Limitations

top

Software Release MX-V5.4.0.49 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, T26, c26, i26, p26, v26

Creation Date: 2020-12-11

Publishing Date: 2020-12-16

Bugfixes

• Thermal events with temperature reference window
  The use of the Reference Temperature Measurement Mode with a Reference Range to define a thermal TR event could lead to false alarm.
• Thermal events above 178°C
  Thermal cameras could get an error message at temperatures above 178°C despite setting the Value Range to Large or Auto.
• Door Station and MxWeb
  After running the door station's Auto Configuration or a manual configuration of a door opener, the icon for opening the door in the MxWeb page of the camera's web browser interface was not functional.
• SIP and DTMF
  For SIP audio connections to the camera, the DTMF function for button 3 (DTMF #3) was faulty and did not switch to any connected signal output.
• Access data for file servers
  The password of a file server defined for storage in the Admin  > Storage > Storage on External File Server / Flash Device dialog can again contain the special character '#'.
• Integration Protocols and IE11
  When using Internet Explorer 11 as a web browser, errors occurred in the Admin > Camera Administration > Integration Protocols dialog, e.g. the Optimize settings function was not available. 
• Integration with Lenel OnGuard
  The ONVIF integration of IoTcameras in the Lenel OnGuard VMS resulted in errors and the cameras could not be connected.
• ONVIF metadata
  There were problems streaming metadata within an ONVIF integration of the camera. These were resolved by changing the 'meta data default event filter' to 'all events'.
• MxAnalytics on M16 cameras and Indoor models
  The storage of MxAnalytics data could no longer be activated on M16 (day-night), c26 and p26 camera models in the Admin  > Storage > Storage on External File Server / Flash Device dialog.
• IP-Notify Profiles for MxMC
  The pre-defined IP-Notify profiles 'MxMC-*' for calling  MxMC remote control commands lacked the character '/' at the beginning and the execution of these profiles without subsequent adjustment resulted in an error.
• FTP Transfer
  When transferring image files using an FTP profile, FTP servers that prefer to use TLS1.3 to establish a connection, could experience incomplete transfers.
• Image quality on D16 panorama models
  Compared to the previous versions 5.2.6.x, the images on D16 panorama models were darker and less sharp. 
• Dual images in faststream-preview function
  When picking up a camera dual image via the API call http://<IP>/cgi-bin/faststream.jpg?stream=full&preview&camera=both&... the left and right camera images were swapped.
• Testing the network interface
  In the Admin > Network Configuration > Test Current Network Configuration dialog, the current IP address was displayed as the broadcast address.

Known Limitations

top

Software Release MX-V5.4.0.45 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, T26, c26, i26, p26, v26

Creation Date: 2020-11-09

Publishing Date: 2020-11-12

Bugfixes

• Automatic Value Range for Thermal Cameras
  Thermal cameras did not allow you to set an Automatic Value Range in the Setup > Thermal Sensor Settings  dialog. 
• Thermal TR Events
  When defining Thermal TR events, the use of a Thermal Range instead of a fixed threshold to trigger events was incorrect.
• Variables $(ID.ETHERNET) and $(ID.ET0)
  The two variables, $(ID.ETHERNET) and  $(ID.ET0), could no longer be used for text overlays in the image.
• Audio and SIP
  No audio was transmitted for the camera's SIP connections.
• CIFS Protocol
  When connecting a file server using the CIFS protocol, a malformed protocol version (V3.11) is now ignored, avoiding connection failures.

Known Limitations

top

Software Release MX-V5.4.0.44 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, T26, c26, i26, p26, v26

Creation Date: 2020-09-17

Publishing Date: 2020-09-18

Enhancements and Improvements

Integration Protocols (RTP Server, ONVIF & Genetec Integration)

For this release, the RTP server as well as the ONVIF and Genetec integration drivers have been fundamentally revised and modified. The reasons for these changes were:

• Improving ONVIF interoperability on the RTP server
• Enhanced support for ONVIF (OSD, AudioBackchannel) features
• Support for H.264 Multi-Streaming
• Improve overall performance and streaming stability

Changes compared to the previous version

Stream-Layout

• Stream 1 and 2 with support for H.264, MJPEG and MxPEG
• Stream 3 and 4 with support for MJPEG and MxPEG

• RTP-Integrationsmodus: rtsp://<IP>:<RTSP-Port>/stream/profile
• Genetec integration modus: rtsp://<IP>:<RTSP port>/stream/genetec_video-0 - 3.
  The access URLs are automatically transferred to the Security Center via the Genetec protocol. It is not necessary to enter these URLs manually. If you are updating an already built-in camera, you must reconnect the camera to ensure that Security Center reloads the new URLs.
• ONVIF integration mode: rtsp://<IP>:<RTSP port>/stream/onvif-<ONVIF PROFILE TOKEN>
  The access URLs are automatically transferred to the ONVIF clients. It is therefore not necessary to enter these URLs.

Image Control

• If the Integration Protocol is set to "ONVIF" or "Genetec" and the selected aspect ratio is not “Free”, the RTP server takes control of the system-wide resolution and display mode settings. It configures the system-wide resolution globally to the maximum resolution required to use the RTP streams, which is the maximum resolution configured for one of the RTP streams.
• If the “Free” aspect ratio mode is selected, the RTP server does not reconfigure the resolution and display mode parameters of the live image. Instead, the available resolutions for the RTP streams are limited to one smaller or equal to the system-wide settings.
• For Integration Protocol “RTP”, the aspect ratio mode is always set to “Free”.
  
• In some scenarios where the system-wide settings do not meet the RTP server requirements the image may be adjusted to the desired RTP streaming resolution by inserting black rows at the top and bottom of the image.

Resolutions

• The list of supported resolutions is: CIF, VGA, XGA, HD, FullHD, QXGA, QHD(5MP), 6MP
• The actual pixel dimensions of these resolutions depend on the setup of the system-wide image parameters and/or the aspect ratio settings in the RTP server.
• The following maximum resolutions apply for the different codecs:
  - H.264 streaming: FullHD
  - MJPEG streaming: FullHD
  - MxPEG streaming: unlimited

The maximum resolution of H.264 or MJPEG streams might be lower than FullHD, depending on the live image’s current aspect ratio.

Legacy-Modus

Updating existing setups

• The old stream layout (1xH.264, 4xMJPEG and 4xMxPEG) replaces the new one
• The existing streaming URLs are redirected to the corresponding new ones (Genetec and ONVIF APIs return the new URLs when they are requested)
• Resolutions that are no longer available are mapped in the best possible way:
• Mega -> HD
• Live image
• in "Free" mode -> current live resolution
• otherwise -> VGA
• ONVIF media profiles are migrated, including the default profiles
• No "new" ONVIF default profiles are created
• H.264 Multi-Streaming is disabled
• Changing the Integration Protocol is not supported in legacy mode.
• Genetec Configuration Wizard is disabled in legacy mode

Uploading Legacy Configuration Files

1. Open dialog Integration Protocols and set the Integration Protocol to "Off".
2. Set and save the configuration in the flash
3. Upload the Legacy Configuration File to the camera
4. Save the configuration permanently in the flash
5. Restart the camera

Important notes

1. Configuration migration is only recommended for updates from 5.2.6.x to 5.4.0.44.  To make the migration work best, we recommend that you upgrade the camera to 5.2.6.7 first and then to 5.4.0.44.
2. Make a backup copy of your configuration before upgrading to version 5.4.0.44. If you decide to downgrade later, you will need to install the backup configuration to restore your Integration Protocol settings.
3. Please check your settings after updating the firmware.
4. Configuration migration cannot cover all possible scenarios. If something doesn't work as expected after upgrading to 5.4.0, we recommend that you reset the Integration Protocol settings to factory settings and reconfigure your streams.
5. If you are using the Genetec Integration Protocol, please remove all multicast IPs in the stream configuration before the firmware upgrade. Genetec configures multicast through its own APIs, and additional multicast settings in the stream configuration can cause post-update streaming issues.

Cybersecurity and Network

• Support for a certificate server as an ACME client
  In addition to the known mechanisms, camera certificates can now also be obtained from an ACMEv2-compatible Certifikats server (e.g. Let's Encrypt). The setup takes place in the new section Obtain X.509 certificate  via ACME client of the dialog  Admin > Network Setup > Web server.
• OpenVPN connections with TLS authentication
  Network connections of the camera via the integrated OpenVPN client can now be additionally secured by an optional TLS authentication. For this purpose, the two new options TLS Auth Key Direction  and Remote Certificate TLS Server Extension Verification are available in the  Admin > Network Setup > OpenVPN Configuration  dialog.
• VLAN tagging according to IEEE 802.1Q
  The camera now directly supports VLAN configurations according to the IEEE 802.1Q standard for switches that use ports using VLAN tagging simultaneously for different VLANs. The camera as a network device also transmits the ID of the VLAN to be used for all Ethernet packets. VLAN tagging is configured using two additional options in the new IEEE 802.1Q section of the Admin > Network Configuration> Ethernet Interface a dialog.  
• Camera addresses in the JPEG header
  The JPEG header of the individual camera images no longer contains any information about the Mac address and the current IP address of the camera. Instead, the factory IP address of the camera is output as the value of the new variable ID(ID.SNO) in the JPEG header.
• Clickjacking Attacks
  This version has been further protected against clickjacking attacks.

Storage

• File count for MxFFS archives
  To improve access times, the storage in an MxFFS archive (additional or buffered archive) has been modified so that a maximum of 1000 files are created on the file server. The size of the individual files is variable and exceeds the previously fixed size of 2 GB per file from an archive size of 2 TByte.
• NTLM on SMB/CIFS file servers
  When including an SMB/CIFS file server for recording, no NTLM version needs to be selected. The camera automatically uses the most secure method that the file server supports.
• Configuration of a buffered MxFFS archive in the MxMC
  When defining a buffered MxFFS archive using the MxManagementCenter (MxMC), archive sizes of more than 4 TByte can now also be specified.
• Passwords for file servers at MxMC
  When entering the password for a file server, additional checks are performed and invalid characters (e.g.) are directly rejected with an error message.

Transfer Profiles

• FTP profiles with SFTP
  The secure SFTP protocol is now also available for transferring images, clips or streams via FTP protocol. To set the value  SFTP can be selected in the dialog Admin > Transfer Profiles > FTP Profiles as the Connection.  
• Network messages with HTTPS/SSL
  The encrypted protocol HTTPS/SSL can now be used to send network messages. For this purpose, you can select the new value HTTP/HTTPS in the dialog Admin > Transfer Profiles > IP Notify Profiles as the IP Notify Type and then make the desired configuration of the HTTPS network message.
• Network messages HTTP/HTTPS-Post-Requests
  With the help of the above new network message type  HTTP/HTTPS,  POST and DELETE requests can now be performed in addition to HTTP(S)-GET requests. In addition, multipart messages now only send the content-length information once at the end of the HTTP(S) header. For example, a POST request can be used to specifically change individual parameters in the camera (such as microphone activation) using the  <IP>/config/camera/<Function Range> API.  For example, the POST request /config/camera/audio/micro  with  data type  JSON  and value 0 disables the camera microphone.
• HTTPS address and redirecting of addresses for image profiles
  HTTPS addresses can now also be used when uploading image files in the Admin > Logos and Image Profiles > Manage Image Files  dialog. In addition, redirects to other HTTP/HTTPS addresses are now supported.
• Attachments for e-mailprofiles
  For the file attachments of e-mails sent by the camera, explicit names can now be defined, so the files can be better managed. In the new File Name field of the Admin  > Transfer Profiles > E-Mail Profiles dialog, both texts and variables can be used for this purpose. By using the variable $(FPR. ENO), for example, the number of the last event can be integrated into the file name.

Thermal Delta Analysis

For Thermal TR camera models, the new Environment Event type Thermal Delta Analysis has been inserted. This makes it possible to trigger events when the temperature values determined in the Measurement Area rise or fall over a certain observation period. This type of event is also configured in the Environment Events section of the Setup > Event Control > Event Overview dialog. The following new options are specific to this type of event::

• Threshold Direction
  This option determines whether falling, rising, or temperature changes in both directions should trigger an event.
• Measurement Time
  This determines the time difference, which is between two measured temperature values, the temperature difference of which then leads to an event triggering according to the set conditions.
• Samples
  This determines the time interval at which the temperature comparison is repeated. The quotient (Measuring Time/Samples) gives the time difference, after which a new comparison of the temperature at the current time T with the temperature at the time (T - Measurement Time) is carried out.

All other parameters correspond to those of the Thermal Radiometry event type.

Online Camera-Hilfe (OLH)

• Thermal Offset Correction
  The online help page  (<ip>/help/help?event_env) for describing thermal  radiometry environment events has been extended to include the Thermal Offset Correction  section.   This describes the offset correction of the temperature values determined by thermal cameras using a black body radiator. The described function has been supported since version 5.2.6.2 and is currently the only method for determining exact temperature values, especially in changing conditions (ambient temperature, humidity, etc.). The options in the  Setup > Event Overview > Environment Events dialog for using this feature have been updated with a link to the new online help section.
• Manage other cameras
  The Admin > Configuration > Manage other cameras help page has been supplemented with important notes on transferring configurations to cameras of older model lines.

Other improvements

• Meta Events
  For special applications, Meta Events can now be defined so that the events involved occur within a maximum period of 50 milliseconds. For this purpose, small values of up to 0.05 seconds can be entered in the Setup > Event Overview > Meta Events dialog for Maximum delay, instead of 1 second as before. It should be noted that the time between successive events cannot be less than the reciprocal value of the current frame rate.
• Improved data rate for MxPEG/M-JPEG codec
  The video codecs MxPEG and M-JPEG have been further optimized, so that data rate savings of about 15% are achieved with the same image quality, depending on the setting. Scenes without movement can save up to 50%.
• 180° Panorama View for S16 cameras
  The special panoramic view of the D16 panorama models can now also be configured and used for S16 cameras. For this camera model, also the value Double Lens Carrier PAN/180 is selected first as Type of carrier in the dialog Admin > Hardware Configuration > Image Sensor Configuration. After a subsequent camera restart, the Quick Control function Panorama View Configuration is available. This function sets up the panorama image first before the Display Mode Normal or Panorama can be selected to use it for the camera live image.
  

Hint

In order for this software function to be used sensibly, after installation the two 90° lenses must be aligned exactly as is the case with the double lens carrier of a D16 panorama camera. Alternatively, such a lens carrier can be used for installation. 

Bugfixes

• MxMessageSystem messages and image changes
  When receiving messages from the MxMessageSystem in combination with subsequent image changes (e.g. display/hide the logo, change resolution, etc.), which were triggered by an IP-Notify message from the camera to itself, it could happen that after some time the received MxMessageSystem messages were not processed correctly.
• SMB/CIFS storage
  When recording on a SMB/CIFS file server as Primary Target (= storage in folder/file structure), the storage process could hang on some systems, so that no further data was recorded. The issue has been fixed for file servers that support the SMB V2. 0 protocol. This protocol version is now automatically preferred by the camera.
  
• MxFFS Archive Storage
  When recording on the in-camera SD card with an additional MxFFS archive, recording sequences could be missing from the archive even though they were present on the SD card.
• Camera status and storage usage 
  The entry Current Usage in the File Server/Flash Device area of the Camera Status dialog indicated the maximum size of the archive instead of the current level for MxFFS archives.
• Manage MxBus Modules
  When disabling and then activating MxBus modules in the Admin > Hardware Configuration > Manage MxBus Modules  dialog, an error message "408 Request Timeout: Please reload the form without submitting CGI parameters" could result.
• Text overlays in MxAnalytics heatmap
  For a set language of the camera user interface that cannot be represented with the ASCII character set (e.g. JP, RU), the displayed texts of an MxAnalytics heatmap were displayed with unreadable characters. With such languages, the text fade-in at the place is now always in EN.
• Text insertions of variables with specified length 
  The parameter  len was not properly taken into account in the text display of a variable, so that subsequent texts were not only displayed from position len+1, but immediately after the end of the variable text in the image. The characters, which can be defined by the parameter fill for the filling after the end of the variable text up to the position len, were also overwritten.
• Temperature values for thermal TR events
  In very rare cases, the temperature values measured by a thermal TR camera could be significantly too high, e.g. above 1000°C instead of 60°C.  In addition, the live image output of the temperature values in Fahrenheit was not quite correct, there was an error in the first decimal place.
• MxMessageSystem messages for door station modules
  When exchanging MxMessageSystem messages between MxBus modules of a door station, there could be problems sending these messages.
• S26/S16 as door station
  After setting up a S26 or S16 camera as a door station using the auto configuration, the Admin > Hardware Configuration > Assign Wires dialog showed the MainBell connected to the right instead of to the left camera button.
• Remote control of a door station
  In the Admin  > Audio and VoIP Telephony > SIP Client Settings  dialog, the settings for remote control of a door station via DTMF sounds during a VoIP call were incorrect and were corrected as follows: only two switching output functions can be set instead of three (function A and B) and these are triggered via the keys "1" and "3".
• FTP transfer with video clips and Full Image recording
  When Full Image recording was enabled, errors occurred when sending video clip files within an FTP profile.
• API function faststream  with option "roi"
  When retrieving the left or right part image of a current camera dual live image by calling  http://<IP>/cgi-bin/faststream.jpg?stream=full&roi&camera=<left/right> lines were partially truncated. For example, for the resolution FullHD an image with 1920x1072 instead of 1920x1080 pixels was returned.
• Definition of the camera name in the MxMC
  When defining the camera name within the MxMC Configuration view, it was possible to enter invalid characters (e.g. '.').
• MxAnalytics and MxFFS Storage
  When using MxAnalytics counting corridors at the same time as MxFFS storage on the SD card (with and without additional archive), or together with the storage in a Buffered MxFFS archive, the counting results could not be stored on the SD card and requested counting corridor reports were empty.

Known Limitations

top

Software Release MX-V5.2.6.7 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, T26, c26, i26, p26, v26

Creation Date: 2020-06-16

Publishing Date: 2020-06-24

Enhancements and Improvements

Bugfixes

Known Limitations

top

Software Release MX-V5.2.6.4 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, T26, c26, i26, p26, v26

Creation Date: 2020-05-15

Publishing Date: 2020-05-20

Enhancements and Improvements

MxAnalytics with cumulative counting corridor evaluation

This version allows the accumulated evaluation of MxAnalytics counting corridors of several integrated cameras. The total calculated from them can be displayed in a separate dialog. For example, according to the corresponding definition of counting corridors at the entrances and exits of a shop, the customers are counted and evaluated as passes in "north direction" when entering and when leaving as passes in "south direction". The current number of visitors in the shop is then the difference between all passes in the north direction and the passes in the south direction and can be displayed in a separate dialog. The setup and display of the result are done as follows:

• Definition of the required counting corridors for the entrances and exits of a shop, each in the Setup > MxAnalytics Control > General MxAnalytics Settings of the mounted cameras.
• Definition of a "master camera" and integration of all MxAnalytics cameras involved in the evaluation as profiles in the new dialog Setup > MxAnalytics Control > Accumulated Difference Setting and Remote Camera Profiles of the master camera. In this dialog, settings for the behavior of the evaluation dialog (limit, correction value "offset", title, warning message when the limit is exceeded, name of the MxMessage, which is sent when the limit is exceeded, etc.) can be defined.
• Evaluation of the current counting corridor values of all integrated MxAnalytics cameras and display of the overall result (number of shop visitors) by opening the Setup > MxAnalytics Control > Accumulated Difference of Counting Corridors dialog on the master camera.

Notes

• The counting corridors of the master camera are automatically counted without the camera itself having to be entered as a profile in the specified dialog.
• The counter can be reset by defining a suitable value for the parameter Offset or by an individual reset of the counting corridor values in the dialog Setup > MxAnalytics control > MxAnalytics Overview of the individual cameras.
• The above dialog for displaying the overall result can also be opened directly in the web browser by entering the URL <IP address>/control/stat_export?inside_count.
• The names of the two new above-mentioned dialogs and the texts within these dialogs are available in this version exclusively in English.

Bugfixes

• Temperature offset correction for thermal TR cameras
  The temperature offset correction function introduced with version 5.2.6.2 could also be activated with a Measurement Mode set to Reference Temperature and was ineffective in this case. For the Absolute Temperature Measurement Mode, the offset correction did not work correctly for the Alarm Type Temperature Range instead of Temperature Value.

Known Limitations

top

Software Release MX-V5.2.6.2 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, T26, c26, i26, p26, v26

Creation Date: 2020-04-23

Publishing Date: 2020-05-05

Enhancements and Improvements

Thermal enhancements and other improvements

• Temperature values with higher accuracy in Thermal TR
  The temperature values measured in Thermal TR cameras are now displayed with two decimal places in the image or output via variables. Two decimal places can also be used in 0.05°C increments when entering temperature values to define thresholds, value ranges, reference windows, tolerances, etc.
• Temperature offset correction for thermal TR cameras
  Thermal TR cameras now have the possibility of offset correction. For this purpose, the new option  Thermal Offset Correction can be activated when defining the Thermal TR events. After activating this option, the Edit Offset Correction Reference Area option can be used to define an area in the image that displays the temperature of a heat source used for calibration, such as a black emitter. The known temperature of this heat source is then entered in the new field Calibration source temperature. The offset between the entered and the temperature measured for the heat source is then used to correct all measured temperature values.
• Time span for Meta Events
  The events evaluated for a Meta Event, e.g. of type Event Counter, can now have a maximum time interval (option Maximum Delay) of 24 hours instead of one hour. If you use a large time interval, you must ensure that the count is not interrupted by a camera restart or a configuration change.

Bugfixes

• Thermal Variable $(SEN. TCO)
  When using the Thermal variable $(SEN. TCO) together with various Thermal TR event profiles, the values of the variable were transmitted only during events of the first defined event profile. Now the values of events from all defined profiles are passed.
• Decimal digits for variables for Thermal (-TR) temperatures
  When using variables (e.g. $(SEN.TTR.CELSIUS), $(SEN.TSR.CELSIUS)) for the output of measured Thermal (TR) temperatures within profiles for network messages, FTP and e-mail, as well as when calling the API function '<IP>/control/rcontrol?action=gettext&message', there was always 0 output as a decimal place. Now two correct decimal places are issued.
• Difference to raw temperature data from Thermal(-TR) cameras
  The values of the raw thermal data available from the JPEG header of the image files of Thermal (TR) cameras were 0.5°C lower than the displayed and output temperature values. This difference has been corrected.
• Thermal image quality after longer runtime
  Some Thermal(-TR) cameras may cause the thermal image to slowly deteriorate over time and show fewer details in certain situations due to the characteristics and settings of the thermal sensor shutter. In this case, the behavior of the shutter can now be changed and the image can be improved by a special entry in the camera configuration file. The required entry can be obtained from the MOBOTIX Support (support@mobotix. com).
  
• FTP profiles with images
  Sending images via FTP profiles failed in conjunction with full-screen recording.
• Messages of Storage Failure Detection
  When storing the video and audio data on the camera-internal SD card in MxFFS format or on a SMB/CIFS file server as the Primary Target, an incorrect error message "Transfer of images files stopped since 3960 seconds" or "Transfer of image files delayed more than 360 seconds!" could occur.
• SIP calls
  Using the camera's VoIP/SIP client could cause an error, so no connection was made. In the camera report there was the error message 'mxsipphone unhandled page fault'.

Known Limitations

top

Software Release MX-V5.2.5.15-r1 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, T26, c26, i26, p26, v26

Creation Date: 2020-03-05

Publishing Date: 2020-03-12

General Improvements

• Soft-Buttons
  The list of predefined soft buttons that can be used to define the soft buttons in the Live, Player and MultiView views has been extended in the factory settings by the hemispheric views Panorama-Focus and Double-Panorama.  
• JSON-API
  The camera's JSON-API now shows also the camera's "uptime" in /api/json/status/camera tree.
• Clickjacking Attacks
  This version has been secured against clickjacking attacks.

Bugfixes

• Decimal temperature values for Thermal TR events (V5.2.5.15-r1)
  The decimal place was ignored when decimal temperature values (e.g. 37.5°C) were used to trigger Thermal TR events and the event was already triggered when the integer temperature value was reached (e.g. 37°C).
  
• Several improvements to MxFFS (Archive storage):

• Access to MxFFS USB media after camera power failures
  When recording to an already fully written USB-MxFFS media (USB-stick or USB-SSD/hard-drive) it could occur after several power interruptions (power failures) that data was then partially overwritten on the medium. In addition, in this case, it was no longer possible to read all the remaining data on the medium. 
• Access to MxFFS USB media after media errors
  If there were media-related recording errors while saving to an USB media, the result could be incorrect time and sequence numbers in the recording after a camera restart. In some cases, not all data could be read any more.
• Shrinking a MxFFS archive
  If the camera configuration initiated the shrinking of an MxFFS archive on the file server and then a camera restart occurred before the downsizing was complete, the archive was no longer written after the reboot in some cases.

• Camera Status and File Server Type
• When the camera was configured to store video in a buffered archive, SMB/CIFS was sometimes displayed instead of  RAM Buffer with Archive in the camera status after a camera restart.
• When saving to a SMB/CIFS file server, internal ring buffers  instead of  SMB/CIFS were sometimes displayed in the camera state after a camera restart.
• Quick installation and IP address
  An IP address in the network range of 10 (10.x.x.x) entered in the Network area of the Quick Installation was not applied correctly.
• Camera temperature SNMP
  The camera temperature of an M16 that can be accessed via an SNMP MIB file was incorrect.
• Network messages with HTTP requests
  Attaching video clips could cause errors when sending HTTP network messages.
• Image rotation by 180°
  With an Image Rotation by 180° set in the Setup > Image Control > General Image Settings dialog there could be image errors (vertical stripe) in the upper right corner of the image.
• Temporal noise filter for black and white sensors
  The (accidental) setting of the temporal noise filter to Chroma caused black-and-white sensors to stop delivering an image.
• SMB/CIFS passwords
  No comma characters (',') could be used in the password when connecting SMB/CIFS file servers for video storage.
• RTSP streaming
  When permanently retrieving an H.264 RTSP stream, there could be interruptions to the stream and a camera restart after longer run times.
• Thermal TR Events
  
  • For Thermal TR cameras, setting a large Value Range (low sensitivity) in the Setup > Thermal Settings dialog caused Thermal TR events to stop triggering reliably.
  • In addition, thermal events at high temperatures (185°C and above) could not always be triggered.

Known Limitations

The version contains the same known limitations as the version  MX-V5.2.4.15/.15-r2.

top

Software Release MX-V5.2.4.15-r2 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, T26, c26, i26, p26, v26

Creation Date: 2019-09-25

Publishing Date: 2019-10-01

Bugfixes

• Special treatment of "empty battery issue"
  With this release, the operating system of dual cameras will deliver a live image even if the battery of the RTC clock is empty and will set the camera to use the last known system time.
• Issues with file-based file server storage
  The camera now detects this status, triggers an automatic reboot of the camera and resumes video storage.
• SIP video issue
  On some SIP clients, the camera showed a blue screen 15 minutes after establishing a SIP video connection.
• Accessing MxFFS Snapshot recordings after reboot
  When recording snapshot videos on MxFFS media (SD card or USB drives), the camera sometimes could not access the recordings any more after a power failure and subsequent reboot of the camera.
• Archive settings from MxManagementCenter
  When configuring an MxFFS archive in addition to SD card recording in the Configuration section of MxManagementCenter, the camera ignored the preselected size of the archive (16 GB) and created an archive with the wrong size.

top

Software Release MX-V5.2.4.15 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, T26, c26, i26, p26, v26

Creation Date: 2019-07-26

Publishing Date: 2019-07-31

Enhancements and Improvements

Support of Door Station Configuration (MxManagementCenter 2.1.1 and Higher)

Starting with release 2.1.1, MxManagementCenter offers a new wizard for initializing one or more door stations. After updating the camera software to the current release, you can use this wizard to initialize S26, S16, and T26 door stations.

• Initialization Results
  After completing the different steps of the wizard, the MxDisplay devices and MxMC have been assigned to all selected door stations as intercoms and will be notified if someone presses a door station bell buttons. This means that executing the auto configuration by pressing the bell button (Mx4/5 models) or the light button (Mx6 models) at a special point in time after booting the device is now obsolete.
• Remaining Configuration
  The remaining steps for configuring the door stations will still have to be executed at the individual devices or on the web interface of the door stations. These steps include initializing the door stations modules (KeypadRFID, BellRFID), entering the Super PIN, training the RFID cards, definition of door bells and other configuration steps such as the proper assignment of existing door bells/number codes to intercom devices. The last page of the wizard contains more information on these steps.

Support of PelcoD PTZ Heads by MxManagementCenter (MxMC 2.1.1 and Higher)

This software release allows using MxManagementCenter to control MOBOTIX IoT cameras mounted to a PelcoD PTZ heads (MxMC 2.1.1 and higher). The following steps are required to use a PelcoD PTZ head:

• Mount the camera to the PTZ head and establish the serial connection to the USB interface of the camera using an FTDI-to-USB adapter.
• Activate the USB RS232 interface of the camera in the Admin Menu > Hardware Configuration > Manage Hardware Expansions dialog and restart the camera.
• Configure the serial interface of the camera in the Admin Menu > Serial Interface > Setup dialog and restart the camera.
• Add the camera in MxMC using the MOBOTIX with PelcoD option as connection protocol.

Optimized Performance When Recording to CIFS Servers

When using a CIFS server as a primary target (=folder/file structure), or as an MxFFS archive, performance is boosted by a new caching strategy. The performance improvements are achieved by reducing the number of random access and file lock operations. The new caching strategy is applied when using the SMBv2 or a more recent version of the protocol.

Bugfixes

• $(SEN.TSR.CELSIUS) text variable when using Thermal Spotmeter
  The $(SEN.TSR.CELSIUS) text variable showed wrong temperature values (–990 °C) on Thermal cameras with activated Spotmeter event.
• Image control and overexposed images
  When the illumination of a scene changed quickly and dramatically, the camera sometimes produced an almost white, overexposed image.
• SNMP sysObjectID and SNMP objects
  The sysObjectID required for adding devices to SNMP management systems was not unique and did not contain any reference to the partial tree of the SNMP object structure specific to MOBOTIX. In addition, some objects delivered by the camera via SNMP (e.g., storageArchiveBufferFillLevel) had been listed at the wrong positions in the SNMP MIB file.
• Password for SNMP authentication
  When defining passwords for SNMP authentication, you could only use letters, numbers, and the characters “-” and “_”. You can now also use special characters here.
• 802.1x authentication and DHCP
  The authentication of a camera at a network device (e.g., a switch) using the 802.1x standard sometimes failed if the DHCP client had been running on the camera.
• DNS server did not function properly
  The IP address of a DNS server stored from a previous configuration was not applied properly after updating the software. The DNS service was hence not available any more. This error could be remedied by once again configuring the DNS server.
• Second network route
  Defining alternative network routes in the Admin Menu > Network Configuration > Routing dialog did not work properly.
• Storage limits and MxAnalytics reports
  Time-related storage limits also applied to the data for MxAnalytics reports. If the storage limit had been set to one day, for example, the MxAnalytics weekly report only contained the data of the last day.
• Functions “Backup” and “Restore”
  Creating a system backup on the internal SD card of the camera did not work properly. The partition on the SD card used for this purpose was not found reliably and thus could not be addressed for these functions.
• Door station auto configuration
  Executing the auto configuration on a system with several door stations only applied to the door station on which it had been started. The other door stations remained untouched.
• Door station reported “408 HTTP Request Timeout”
  When configuring a door station (T26, S15, S16), the web browser sometimes showed a permanent “408 HTTP Request Timeout” error message. This could only be remedied by rebooting the camera.

Known Limitations

• MxAnalytics:
  • When using events for behavioral detection in combination with high frame rates (20 frames per second and more), the camera does not recognize enough events. This applies to the Reverse Direction, Opposite Direction and Turn event types.
  • If a camera restart occurs within the first half hour after a camera restart, the MxAnalytics result data generated within this time may be lost after the second restart. The problem can be bypassed by pressing the Force New Data Set button in the Setup Menu > MxAnalytics Controls > MxAnalytics Overview dialog before the second required restart.
• RTSP Streaming
  In the following two cases, a distorted image may occur when fetching an RTSP stream:
  • Live image with an aspect ratio of 16:9 and Panorama display mode.
  • Q26 camera in factory settings – to remedy this error, temporarily change the current display mode.
• Shrinking MxFFS archives
  When shrinking existing MxFFS archives, you can shrink in 2 GB steps. On rare occasions, the camera can delete one file too many and thus delete 2 GB too much.
• Dual cameras and 5MP Image sensors
  On dual cameras with 5MP image sensors where only one sensor image is displayed (mainly Day/Night models), switching between the sensors can on rare occasions cause the camera to restart.
• MOBOTIX ExtIO only supported via USB
  The usage of the MX-ExtIO via network (Ethernet) is no longer supported by MOBOTIX with its current camera portfolio. The MX-ExtIO can still be used via a direct USB connection to a MOBOTIX camera.

top

Software Release MX-V5.2.3.30 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, c26, i26, p26, v26

Creation Date: 2019-04-11

Publishing Date: 2019-04-15

Enhancements and Improvements

Improved frame rates

This version achieves significantly improved frame rates. This applies mainly to high resolutions and M-JPEG or MxPEG with high motion rates, where increases of up to 96% can occur.

Improved image quality through new 3D noise filter

An additional optional time-based noise filter improves the image quality and reduces the data rate by up to 20%. This filter can be activated in the browser's user interface under Setup Menu > Image Control > General Image Settings with the Temporal Noise Filter option. The reduction is up to 20% on a 24-hour average and up to 50% on dark, noisy images. If stored on a NAS or file server, this leads to a noticeable relief of the storage device. Please note that the filter may reduce the frame rate depending on the picture settings and scene complexity. This is especially true if the camera is already delivering a reduced frame rate due to a high load situation or complex scene content, as would be possible under optimal conditions.

Genetec- and ONVIF-Integration

The integration of the cameras into ONVIF-Clients or the Genetec Security Center via the integration protocol has been greatly facilitated.

• Optimize settings:
  The Admin Menu > Camera Administration > Integration Protocols dialog now offers the new function Optimize Settings. This function is available as soon as Genetec or Genetec + ONVIF has been selected as protocol in the specified dialog. Clicking the Optimize Settings button opens the new Configuration Optimization dialog. This dialog displays all predefined setting changes and offers additional setting options that are automatically applied to the camera by pressing Apply & Save. This eliminates the need to manually configure MOBOTIX cameras according to the Genetec Integration Guide.
• Image size and aspect ratio
  For integration into an ONVIF, Genetec or other RTSP-based system, a desired aspect ratio can now be set for the RTSP stream. For this purpose the option Limit aspect ratio in the Admin Menu > Camera Administration > Integration Protocols in the Configuration Optimization dialog (see section above) and the Global Settings area has been added. For all selected values except free, only resolutions with the selected aspect ratio will be offered for selection in the RTSP client. These can be up to 6MP in size and higher than the currently set resolution of the live camera image. The first time the RTSP stream is requested, the live image is automatically reconfigured by the camera accordingly. If several RTSP clients are used, the live image is converted to the highest resolution retrieved from one client. When the selected aspect ratio is free, the camera behaves as before. Then only resolutions smaller than or equal to the resolution of the live camera image are available via RTSP and there is no automatic reconfiguration of the live image. Further information can be found in the camera online help under <IP address>/help/help?integrationprotocols.
• ONVIF API and RTSP-over-HTTP Tunnel
  The default web server of the camera with port 80 is now used additionally for both the ONVIF API and the HTTP tunneled RTSP access. An activation of MxWeb with port 8080 is no longer necessary, but is still supported.

Other improvements

• Thermal improvements
  The display and output of temperature values for Thermal(-TR) cameras is now done with higher accuracy (one decimal place).
• Network Messages (IP Notify) with Image Profiles
  When sending network messages, it is now also possible to generate images according to a previously selected image profile and send them together with the message. The Data Type option for configuring a network message has been extended by the additional value Image. 
• faststream API extension (ROI)
  Using the faststream API function, it is now possible to retrieve a video stream from the camera that contains only a specific image section instead of the entire camera image. The two parameters roi and roisize have been added. Further information can be found in the camera online help under <IP-Adress>/help/help?cgi-image#faststream.jpg.

Bugfixes

• Door station and RFID
  In T26 door stations, RFID cards with a KeypadRFID or BellRFID module could not be read after a software update to V5.2.1.4.
• Red Camera LED
  The signaling by LED 1 (red) did not work with the camera models i26B, p26B, S26B, S16B.
• Directional ActivitySensor Events
  When defining event profiles with the MxActivitySensor that should only react to certain directions of movement (e.g. left or right), undetected movements or missing event triggers could occur.
• Permanent Microphone Destruction
  An error message "408 Request Timeout" occurred when attempting to permanently switch off the microphone via the Admin Menu > Audio and VoIP Telephony > Microphone and Loudspeaker dialog.
• FTPS Streaming
  Using FTP streaming did not work when FTPS was enabled. Correction: FTP streaming automatically disables FTPS.

Known Limitations

• MxAnalytics
• Problems may occur when setting up MxAnalytics and storing the data on the camera's internal SD card. It is recommended that you test the functions after setup, ensuring that the data is stored correctly by checking the values displayed in the Records section of the Setup Menu > MxAnalytics Control > MxAnalytics Overview dialog. If problems occur, click the Force new record button in the same dialog.
  
• The use of events for behavior detection can be too insensitive at high frame rates (20 and more frames per second) and can detect too few events. This applies to the event types reverse direction, opposite direction and turn.
• If a camera restart occurs within the first half hour after a camera restart, the MxAnalytics result data generated within this time may be lost after the second restart. The problem can be bypassed by pressing the Force New Data Set button in the Setup Menu > MxAnalytics Controls > MxAnalytics Overview dialog before the second required restart.
• RTSP streaming
  In the following two cases, a distorted image may occur when fetching an RTSP stream:
• Live image with set aspect ratio 16:9 and display mode panorama
• Q26 camera in factory settings - here a temporary change of the current display mode helps
• Shrinking MxFFS archives
  When shrinking existing MxFFS archives, you can shrink in 2 GB steps. On rare occasions, the camera can delete one file to many and thus delete 2 GB too much.
• Auto configuration of the door station
  Auto configuration in systems with more than one door station currently only works on the door station where auto configuration was started. The other door stations must be started separately via auto configuration. As long as these ones are still accessible via the standard access data (admin/meinsm), they must be temporarily disconnected from the network before the auto configuration is executed on the first door station, otherwise their configuration can become corrupted. If an MxDisplay is used in this case, the previously configured door stations must also be entered manually in the camera list of the MxDisplay.
• Dual cameras and 5MP image sensors
  For dual cameras with 5MP image sensors where only one sensor image is displayed (mainly day/night models), switching between the sensors may in rare cases cause the camera to restart.

top

Software Release MX-V5.2.1.4 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, c26, i26, p26, v26

Creation Date: 2018-12-20

Publishing Date: 2018-12-20

Enhancements and Improvements

Improved Support of the Extended Camera Configuration in MxMC 2.0.1

This release supports the different enhancements and improvements of the camera configuration in MxManagementCenter (MxMC) 2.0.1 (e.g., for setting up a camera as a time server, setting up buffered archive).

Bugfixes

• Wrong system messages
  The Transfer of image files delayed more than 60 seconds! message erroneously appeared in the system messages and triggered false alarms of the store failure detection, if it had been configured.
• Sensor configuration of D16 bodies
  For D16 complete cameras and D16 bodies, the Admin Menu > Hardware Configuration > Image Sensor Configuration dialog for setting the installed sensor configuration (Pano, Day/Day, Day/Night) did not show.
• Door station modules
  When using the new door station modules Mx-A-KEYC* and Mx-A-BELLC* for T26 Door Stations, the RFID features sometimes failed.

Known Limitations

• Shrinking MxFFS archives
  When shrinking existing MxFFS archives, you can shrink in 2 GB steps. On rare occasions, the camera can delete one file to many and thus delete 2 GB too much.
• MxAnalytics results after camera restart
  If a camera restart occurs within the first half hour after a previous camera restart, the MxAnalytics result data generated within that time may be lost. This problem can be prevented by pressing the Force New Record button in the Setup Menu > MxAnalytics Control > MxAnalytics Overview dialog before executing the second restart.
• Auto configuration of the door station
  When running the auto configuration on systems with more than one door station, the auto configuration will only configure the door station from which the auto configuration had been started. Note that it is necessary to run the auto configuration on every additional door station you want to configure. As long as these ones are still accessible via the standard access data (admin/meinsm), they must be temporarily disconnected from the network before the auto configuration is executed on the first door station, otherwise their configuration can become corrupted.. When using MxDisplay, you need to add the configured door stations manually into the camera list of the device.
• Dual cameras and 5MP image sensors
  When using Dual cameras with 5MP image sensors that are typically showing only one image (such as Day/Night models), the camera can reboot on rare occasions when switching between image sensors.
• Red camera LED
  On i26B, p26B, S26B, and S16B camera models, the red LED currently does not signal anything.

top

Software Release MX-V5.2.0.61 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, T26, c26, i26, p26, v26

Creation Date: 2018-10-30

Publishing Date: 2018-11-02

Enhancements and Improvements

Door Station Features – Support of T26, S26, S16

With this release, the door station features are available on cameras of the Mx6 model range. The software supports the T26 door station as the successor of the T25, as well as the S26 and S16 models, which can also be used as door station when running this software release.

Support of MxMC 2.0 With Integrated New Features (Advanced Config, Health Check)

MxManagementCenter (MxMC) 2.0 includes an advanced camera configuration, which almost makes switching to the browser-based user interface of each camera unnecessary.

In addition, MxMC 2.0 contains the new Health Check feature. It allows testing all MOBOTIX IoT cameras of the Mx6 model range for problems regarding the system status. The results are displayed with traffic light icons (Green – no problems, Yellow – at least one warning in the system, Red – at least one critical state of one camera). If warnings (Yellow) and errors (Red) have been detected, the system will propose solutions and recommendations to resolve the issues.

For additional information on MxMC 2.0, please see the corresponding release notes and the integrated online help.

Enhanced System Performance

Many improvements in details of this software release have resulted in a perceptible increase in system performance. The increase in computing speed and the further stabilized, higher frame rates that can be attained in this release even under high loads (large image sizes, many camera features activated) are proof of the increased performance.

ONVIF S Extensions

Thanks to the additional ONVIF S audio features of release MX-V5.2.0.x, all MOBOTIX Mx6 camera models are conforming to ONVIF S after updating to this release (with or without microphone). The cameras will be listed in the near future as Conformant Products on the ONVIF website. In addition, this release also supports the PTZ features of the camera via the ONVIF S protocol.

Extended SNMP Support

The Admin Menu > Network Configuration > SNMP Configuration dialog now offers to download an SNMP MIB file, which can be used for subsequent requests by SNMP clients. SNMP clients can now get additional information regarding the current camera status, such as temperature, date and time, network properties, flash cell wear, etc.

MxAnalytics for Dual Cameras

You can now use MxAnalytics on dual cameras (e.g., the D16-B-F) if the camera uses only one image sensor ("Auto" image mode on Day/Night models and "Right" or "Left" on dual models).

Automatic Detection of Attached Image Sensors

In the D16, M16 and S16 camera models, the software now automatically recognizes the types of the attached sensor modules (6MP/5MP image sensors, Thermal sensors, MxDigitizer) and configures the system accordingly. The manual sensor module configuration by the user has thus become obsolete.

Enhancements for Thermal Cameras

• Temperature range (thermal range) for events
  On all cameras with Thermal sensors, you can now set a temperature range instead of a specific trigger value for triggering events. The measured values (in the measurement window of Thermal-TR cameras, in the spot of non-TR cameras) can be compared with the temperature in the specified range and the camera can trigger an event if the measured temperature is within or outside of the range.
• Hottest Pixel
  On Thermal-TR cameras, the software can now visualize the hottest pixel measured in the image and can also show the value using a variable. The camera also adds this information to the header of the JPEG images.
• Temperature Raw Data
  To be able to use the temperature data in third-party software, the camera adds the temperature raw data and the xy coordinates to the header of the JPEG images.
• Reference Window
  When using the reference window mode, you can now set a tolerance to the specified trigger value in degrees.

Other Enhancements and Changes

• Cross-Site Request Forgery (CSRF)
  The camera software has been further hardened against CSRF attacks.
• MxPEG+ and Image Noise
  The MxPEG+ codec can now better handle image noise in bright scenes.
• Storage on External File Servers
  When specifying the connection data for an external SMB/CIFS file server, you can now set a domain for the specified user.
• Genetec Integration
  The implementation of the supported Genetec protocol has been enhanced for the param.cgi interface (configuration of the network interface). In addition, the software now supports the firmwareupgrade.cgi interface for upgrading the firmware.

Bugfixes

• MxAnalytics and S16
  MxAnalytics did not run on S16 cameras with only one attached sensor.
• D16-Cameras − IP Address Announcement
  On some D16 cameras, the software falsely detected a pressed button on the camera, which prompted the camera to inadvertently announce its current IP address.
• FTP Transfer
  FTP transfers sometimes failed if FTPS (= default) had been activated (Error 52).

Known Limitations

• Shrinking MxFFS archives
  Shrinking existing MxFFS archives takes place in 2GByte steps and it can happen that a file and thus 2 GByte too much can be deleted.
• MxAnalytics results after camera restart
  If a camera restart occurs within the first half hour after a previous camera restart, the MxAnalytics result data generated within that time may be lost. This problem can be prevented by pressing the Force New Record button in the Setup Menu > MxAnalytics Control > MxAnalytics Overview dialog before executing the second restart.
• Auto configuration of the Door Station
  When running the auto configuration on systems with more than one door station, the auto configuration will only configure the door station from which the auto configuration had been started. Note that it is necessary to run the auto configuration on every additional door station you want to configure. As long as these ones are still accessible via the standard access data (admin/meinsm), they must be temporarily disconnected from the network before the auto configuration is executed on the first door station, otherwise their configuration can become corrupted. When using MxDisplay, you need to add the configured door stations manually into the camera list of the device.
• Dual cameras and 5MP image sensors
  When using Dual cameras with 5MP image sensors that are typically showing only one image (such as Day/Night models), the camera can reboot on rare occasions when switching between image sensors.

top

Software Release MX-V5.1.0.99-r4 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, c26, i26, p26, v26

Creation Date: 2018-10-24

Publishing Date: 2018-11-06

Enhancements and Improvements

New Storage Method "Buffered MxFFS Archive"

In the Admin Menu > Storage > Storage on external file server dialog, the new option Buffered MxFFS Archive can now be selected as the Primary Target. SMB / CIFS and NFS File Servers can also be used here as an MxFFS Archive Target.  As a result, data in MxFFS format is no longer stored first on the SD card but directly on a connected file server (e.g. NAS device). The internal SD card is then used only for storing some administrative information. Only in the case of a detected file server failure (e.g. lost connection) will the storage be automatically switched to the SD card. Once the file server is available again, the data previously saved on the SD card will be transferred to the server. Due to the significantly reduced load on the SD card, its service life is considerably extended.

Support of Mx6-B Camera Models With MxBus

This release supports the use of MxBus features in the new B variants of the Mx6 models.

Support of the Camera Configuration in MxManagementCenter (MxMC)

As of version 1.8 of the MxManagementCenter (MxMC), the most important settings on the camera can be made from this program. For Mx6 camera models, the current or a newer version of the camera firmware is required to support that function in MxMC.

Automatic Request for Password Change And Password Length

When you first log in to the camera, the user is automatically prompted to change the default password ('meinsm') for the admin user. The new password to be entered must also be at least 8 characters long.

Improved Dual-Core Support

This firmware version now better supports the dual-core processor architecture of the Mx6 camera model. As a result, more functions can be performed by the camera at the same time, without negatively affecting the frame rate.

Improved Online Help

The online help's layout has been improved and all pages now start with an index including links to the different chapters. Additionally the online help page for the Admin Menu > Storage > Storage on External File Server/Flash Device dialog has been completely redesigned and important notes and best practices, mainly for the MxFFS archive, have been added.

Other Improvements and Changes

• Network settings
  Changing the network settings in the Admin Menu > Network configuration > Ethernet Interface dialog is now directly applied directly by pressing the Set button and a camera restart is no longer necessary. Settings are also directly applied (without a camera restart) even when loading a configuration file with changed network settings. When making such a change, it is necessary to ensure that the camera can still be connected via the current network!
• Dual cameras with PoE Class 3
  By default, all Mx6 dual cameras are now set to PoE class 3. This can be changed to class 2 if necessary, but this then leads to deactivation of the second processor core.
• Thermal reference windows (V5.1.0.99-r3 and higher)
  On Thermal cameras without TR sensor, you can now use thermal reference windows when defining events.
• Genetec-Integration
  Integration in the Genetec Security Center now also supports MxAnalytics behavioral events (length of stay, restricted area,...). These are offered for selection in the Security Center in the Events area of the Options dialog (although they are named somewhat differently).
• MxActivitySensor 2.1
  Further improvements to Activity-Sensor 2.1 resulting in reduced false alarms in dark "noisy" images.

Bugfixes

• S26 with external sensors (V5.1.0.99-r3 and higher)
  After connecting and activating an external image sensor to an S26, the information about the on-board image sensor was faulty. As a consequence, the camera did not offer the different display modes for correcting the distortion of the hemisperical lens.
• Image generation with special combinations of MxActivitySensor and MxAnalytics (V5.1.0.99-r3 and higher)
  If you had been using both MxAnalytics and MxActivitySensor and the MxActivitySensor window had a lower height than the MxAnalytics window, image generation did not work properly. This happened quite easily if you had been using the entire image area for MxAnalytics (factory default) and chose to reduce the size of the MxActivitySensor window.
• vPTZ actions in the live image
  After applying vPTZ functions, it could happen that the live image jumped after that and displayed a different area than previously set.
• S26 and Audio
  When using the microphone of an external sensor module with an S26 camera, the audio input in the Admin Menu > Audio and VoIP Telephony > Speaker and Microphone dialog has to be set to Disabled instead of the microphone of the connected sensor module in order to receive an audio signal. Also, with S26 cameras, when using an external speaker (such as the MOBOTIX AudioMount) and with other models when the echo cancellation is activated, a steady soft whistling tone could be heard after a camera restart.
• Alarm notification for storage failure detection
  In the case of a detected failure of MxFFS archives, it was possible that an alarm notification (e.g. E-mail) configured in the Admin Menu > Storage Failure Detection dialog was still sent even after the archive was available again.

Known Limitations

• Shrinking MxFFS archives
  Shrinking existing MxFFS archives takes place in 2GByte steps and it can happen that a file and thus 2 GByte too much can be deleted.
• MxAnalytics results after camera restart
  If a camera restart occurs within the first half hour after a previous camera restart, the MxAnalytics result data generated within that time may be lost. This problem can be prevented by pressing the Force New Record button in the Setup Menu > MxAnalytics Control > MxAnalytics Overview dialog before executing the second restart.
• SIP video
  This release does not support SIP video. This feature will be available again in a later release.
• Translations
  Currently, only the English and German translations of the camera's web browser interface and online help are up-to-date.

top

Software Release MX-V5.0.2.14 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, c26, i26, p26, v26

Creation Date: 2018-02-07

Publishing Date: 2018-02-14

Enhancements and Improvements

ONVIF S Compatibility

With this release, cameras of the Mx6 product range are compliant to the ONVIF S standard. With respect to the predecessor release, the following functions have been added for ONVIF:

• Event Handling (Notify, Pull Point, Meta Data Stream)
• Meta Data Streaming

Support of the Optional POS Features in MxManagementCenter (MxMC) 1.7 and Higher

From this version on, Mx6 cameras can be integrated with Vectron cash point systems (POS = point of sale) in order to transfer the transaction data of a cash point (e.g., the items on a sales slip) to MxManagementCenter. You can then use MxMC to search and retrieve the transaction data in different views. In addition, MxMC can play back the video recordings for individual transactions.

To set up such a system, a special script for MOBOTIX cameras needs to be installed and configured on the Vectron cash point. To set up the POS system on the camera, you need to follow the steps below:

• Enter the name of the cash point in the new Admin Menu > Camera Administration > Retail Configuration dialog.
• If required, activate the Event Logging option in the Admin Menu > Storage on External File Server / Flash Device dialog (activated by factory default).
• Reboot the camera.

After that, you need to license the feature in MxMC to be able to configure a new "Retail System" consisting of the cash point and the assigned camera. You can now search the transaction data of the cash point to retrieve the corresponding recordings in the special "Retail view" of MxMC.

For additional information about this new feature, please also see the Online Help of the camera.

Bugfixes

• MxFFS archive with files of 4 bytes size
  When writing MxFFS archives, the archives sometimes contained files with 4 bytes, which led to a situation where the camera could not write to the archive any more.
• MxAnalytics Reports
  The counting corridor and heatmap reports sent after MxAnalytics events sometimes did not contain any data.
• Network switches with IEEE 802.3az
  Connecting a camera to a switch with activated energy saving mode according to IEEE 802.3az sometimes resulted in connection failures.
• Image errors on S16 cameras
  After updating the camera software from release V5.0.x to V5.0.1.53, S16 cameras sometimes showed image errors.
• Power supply of USB devices
  USB devices connected to the camera were powered by the camera although they had not been activated in the software.
• Translations
  On some dialogs of the browser-based web interface of the camera, the French, Spanish, Italian and Portuguese texts were faulty.

Known Limitations

• SIP video
  This release does not support SIP video. This feature will be available again in a later release.

top

Software Release MX-V5.0.1.53 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, c26, i26, p26, v26

Creation Date: 2017-10-26

Publishing Date: 2017-11-20

Enhancements and Improvements

MxPEG+ Video Codec

Together with the new Mx6 hardware, the proprietary MxPEG video codec by MOBOTIX has been improved to MxPEG+. This codec is now the default codec on Mx6 cameras, although the visible name has not changed. From this release onward, the "MxPEG" codec actually uses the much more efficient MxPEG+ variant, which uses significantly less bandwidth for displaying and storing the video stream than its predecessor. Using MxPEG+ instead of MxPEG typically saves about 25 % in bandwidth. In dark scenes or at night, the increased efficiency is much more significant – the required bandwidth drops by up to 50 %.

MxActivitySensor 2.1

MxActivitySensor 2.1 of this release uses a significantly improved strategy compared to its predecessor release 2.0. The main objective is to avoid false alarms that occurred in a scene due to changes in illumination or light shadows, for example. The basic functionality and the sensor settings have not changed from MxActivitySensor 2.0.

ONVIF Enhancements

This release contains some important enhancements regarding ONVIF:

• Authentication
  The authentication of an ONVIF client now uses a WS security UsernameToken profile. HTTP digest authentication has been removed from ONVIF.
• ONVIF Users
  The users required for establishing an ONVIF connection are now managed separately from the regular camera users. Open the Admin Menu > Camera Administration > Integration Protocols dialog and go to the ONVIF section to add ONVIF users and to change their passwords. By factory default, three different ONVIF users are already present – admin, operator, user.
  Note: After upgrading a camera from release 5.0.0.x to the current release with existing ONVIF clients, you need to change all connections to the camera to the new ONVIF users. This does not happen automatically.
• Multicast Support
  You can now use the Multicast interface of the camera via an ONVIF connection.

Bitrate Control for H.264 Streaming

You can now set H.264 streaming to maintain image quality and to reduce the frame rate instead, if required. This happens only if the defined bit rate (bandwidth) is exceeded. Open the Admin Menu > Camera Administration > Integration Protocols dialog, go to the H.264 Settings section and activate the new Constant Quality Mode option.

Support of the New MxIOBoard-IC Module for x26 Indoor Cameras

Thanks to the new MxIOBoard-IC Module, the c26, i26, p26, and v26 camera models can use two signal inputs and two signal outputs (isolated relay or 12 V self-powered). 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 isolated relay 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.

Other Enhancements

• Shock Detector
  This release supports the on-board shock detector that can trigger events of the type Shock Detector.
• RTSP Streaming
  The camera can now send the requested RTSP stream via an HTTP tunnel. Open the Admin Menu > Camera Administration > Integration Protocols dialog, go to the Global Settings section and activate the new RTSP-over-HTTP Tunnel option.

Bugfixes

• MxActivitySensor
  When using MxActivitySensor areas together with the new $generate option, the camera sometimes developed issues and rebooted.
• H.264 Streaming
  H.264 streaming produced image errors and instabilities on some streaming clients (such as some DVRs).
• Configuration of S16 and S26
  On the S16 and S26 camera models, the browser-based user interface contained the Admin Menu > Video Door Station section.
• MxAnalytics Counters
  Resetting the MxAnalytics counters in blue counting corridors did not work properly.

Known Limitations

• Image errors on S16 cameras
  After updating the camera software from release V5.0.x to V5.0.1.53, S16 cameras sometimes show image errors.
• MxAnalytics Reports
  Creating MxAnalytics reports with counting corridors or a heatmap from the data stored on an SD card does not work properly in this release.
• SIP video
  This release does not support SIP video. This feature will be available again in a later release.
• Translations
  Some languages (such as FR, ES) show texts in some dialogs that actually belong to other dialogs.

top

Software Release MX-V5.0.0.133 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, c26, i26, p26, v26 − With Thermal Sensors as well as 6MP and 5MP Image Sensors

Creation Date: 2017-07-21

Publishing Date: 2017-08-08

Enhancements and Improvements

Support of FTPS (TLSv1, TLSv1.1 and TLSv1.2)

This software release supports file transfers of the camera using FTPS (FTP via Transport Layer Security). The supported TLS versions are TLSv1, TLSv1.1 and TLSv1.2.

Other Improvements

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

Bugfixes

• Fixed gSOAP security issue in OVIF integration
  This release fixes the gSOAP security issue "Devil's Ivy", which was created due to a vulnerable part of the ONVIF Toolkit.
  

  However, this vulnerability could only be exploited in the affected software releases, if the ONVIF integration had been activated. If only the MxPEG video streaming codec developed by MOBOTIX was being used, the vulnerability could not be exploited.

• 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.
• Integration Protocols dialog and IE 11
  The Admin Menu > Cameras Administration > Integration Protocols dialog did not work properly when using Internet Explorer 11. The changes made in the dialog were not stored properly in the camera.

Known Limitations

• SIP video
  This release does not support SIP video. This feature will be available again in a later release.
• Shock Sensor
  This version does not yet support the integrated shock sensor to trigger Shock Sensor events.

top

Software Release MX-V5.0.0.130 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26, c26, i26, p26, v26 − With Thermal Sensors as well as 6MP and 5MP Image Sensors

Creation Date: 2017-06-21

Publishing Date: 2017-07-14

Enhancements and Improvements

Support of Mx6 Indoor Camera Models

This software release also supports the new Mx6 indoor camera models i26, c26, p26 and v26. As a consequence, the new features of the Mx6 camera line are also supported on these models (noticeably higher frame rates, H.264 video streaming, ONVIF etc. In addition, the design and the handling of the i26, c26, p26 and v26 cameras does not differ from their predecessor models of the P3 camera line.

Factory Default Settings changed

The following factory default settings have been changed in this version:

• Image size = MEGA and Image Quality = Normal
  The camera now delivers 25 fps immediately after first start because of this change.
• Genetec and ONVIF Support activated per default
  The integration of cameras in Genetec and ONVIF video management systems is easier now because Genetec and ONVIF are now activated per default in the Admin Menu > Camera Administration > Integration Protocols dialog.

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-V5.0.0.130 (just like MX-V5.0.0.127) 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:
! " # $ % & ' ( ) * +, −. /:; < = >? @ [ \ ] ^ _ `{ | } ~.

ONVIF Description

The online help for the ONVIF integration has been extended.

Bugfixes

• M16: Day/night operation
  When using an M16 in Day/Night mode, the Black&White (Night) image sensor sometimes showed image errors.
• Warning note for network settings
  After changing and storing the network settings in the Admin Menu > Network Configuration > Ethernet Interface dialog, the Administration dialog showed a faulty warning in the Network Configuration section.
• Storage on external file server after changing the language
  After setting French or Italian as language in the browser-based user interface, the Admin Menu > Storage > Storage on External File Server / Flash Device dialog showed some wrong contents.

Known Limitations

• IP Notify profiles and full image recording
  When using IP notify (network message) profiles with event images in combination with full image recording, errors may occur if the event that triggered the sending of the message not also triggers a recording.
• Logo upload
  The automated loading of logos from web server URLs does not always work reliably.
• Thermal TR cameras show temperature values above 2000 °C.
  On rare occasions, Thermal-TR cameras can show temperatures above 2000 °C.
• Integration Protocols dialog and IE 11
  The Admin Menu > Cameras Administration > Integration Protocols dialog does not work properly when using Internet Explorer 11. The changes made in the dialog will not be stored properly in the camera.
• SIP video
  This release does not support SIP video. This feature will be available again in a later release.
• Shock Sensor
  This version does not yet support the integrated shock sensor to trigger Shock Sensor events.

top

Software Release MX-V5.0.0.127 − for Mx6 Camera Models D16, M16, S16, V16, D26, M26, Q26, S26 − with Thermal Sensors as well as 6MP and 5MP Image Sensors

Creation Date: 2017-04-27

Publishing Date: 2017-05-05

The following list describes the new features, enhancements and improvements as compared to the P3 models (software releases V4.x).

Enhancements and Improvements

Higher Frame Rates

As mentioned above, the Mx6 models display noticeably higher frame rates with less variation as in the P3 camera models. This is mainly due to the higher computational power of the dual-core processor. The frame rate can reach 42 fps when using HD image size (1280x720), the MxPEG video codec and Normal image quality:

RTP Streaming, H.264 and Genetec Integration

To integrate these camera models into other video management systems, you can use RTP streaming, H.264 and a special Genetec integration interface. Open the Admin Menu > Camera Administration > Integration Protocols dialog and activate the RTP Server and/or Genetec options to use these features.

ONVIF Integration

This is the first software release to support the ONVIF standard; it complies with many basic features of this global and open communication standard. Currently, the following ONVIF features or codecs and protocols are supported: Discovery Service, Digest Authentication, Scope Management, Profiles with Reset via Web UI, H.264, M-JPEG, RTP, TCP, HTTP.

Open the Admin Menu > Camera Administration > Integration Protocols dialog and activate the ONVIF option to activate the integrated ONVIF support. If you activate the ONVIF Discovery Service in this dialog, you can also define ONVIF Scopes and show or delete the ONVIF Profiles created by an ONVIF video management system.

Bugfixes

The bugfixes described in the following refer to the software releases prior to release V5.0.0.127 that had been delivered with the first Mx6 camera models.

• Recording on SMB/CIFS file server
  When using an SMB/CIFS file server as primary recording target (with MX folder/file structure) or as MxFFS archive, the camera sometimes could not connect to the file server.
• Several RTP H.264 streams
  When requesting more than one RTP H.264 stream, the additional streams sometimes displayed image errors.
• RTP server and storage on file server as primary target
  When recording on a file server as primary storage target (MX folder/file structure) and activating the RTP server, a camera reboot sometimes deleted the recorded video data.

Known Limitations

• SIP video
  This release does not support SIP video. This feature will be available again in a later release.
• Shock Sensor
  This version does not yet support the integrated shock sensor to trigger Shock Sensor events.