Bernd Wilhelm, Thilo Schüller, Gerald Eberhard
These Release Notes contain a technical description of the most important changes of this software release of the MOBOTIX M10/D10 and V10 network cameras.
Load the stable customer releases of the software from http://www.mobotix.com/services/software_downloads.
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 e-mail to firstname.lastname@example.org for feedback.
This version is available in the following language combinations:
The following additional time zones can now be set:
Canada/Atlantic (AST, ADT)
A small picture of a pair of binoculars has replaced the „?“ symbol on the button which opens the Event Search dialog.
A button with a small picture of a diskette has been added which, when clicked, opens the dialog for Event Download.
The switch used to adjust the level at which the camera switches between day and night sensors (Setup Menu > General Image Settings) now uses Lux values rather than a percentage of brightness as was previously done.
Factory default setting for Video Motion Night Mode / Dark Video Motion Suppress (Setup Menu > Event Settings) is Off, i.e. by default, video motion event detection is active regardless of the illumination level.
The internal algorithm for the Automatic WB color profile (Setup Menu > Color Settings) has been changed to accommodate very extreme situations whereby strongly colored room lighting sometimes caused the image to take on an unnatural color tint.
The left camera sensor can now be viewed in PDA screens by using one of the following commands:
IP>/pda/sl (160x120 pixels)
http://< (320x240 pixels)
http://< (640x480 pixels)
The ActiveX control necessary for viewing the rapid image rate available via the MPEG stream in the Internet Explorer has been replaced with the improved 1.2.19 release. This version displays a smaller MxPEG logo in the bottom left corner of the live image the first time the video stream is loaded when the browser is using ActiveX and also whenever switching back to the live image from another view (i.e. Event Player or MultiView). The logo is only displayed for a few seconds to confirm that you are actually viewing the MxPEG stream and then fades out. Other than that, this version also contains certain changes and error corrections, the technical details of which are only important, should you be using this ActiveX control in your own custom applications.
Improved Error Handling and
Detection of Problems During Event Storage on File Server
When using event storage on a file server, certain problems could occur when the allocated storage space limit was reached and the file storage process had „wrapped around“ during the write of events. Problems could also occur when the process was in the „wrapped around“ state, deleting/overwriting the oldest events and simultaneously another process (i.e. MxViewer) was accessing these events, or whenever someone manipulated the event storage directory. In certain situations these conditions prevented the camera from recording further events on the file server.
Master-Slave Error Caused by
Long IP Addresses
The use of long IP addresses (3 numerals in all 4 positions in the address) sometimes caused errors during Master-Slave operations.
Erroneously Generated E-Mail
Profile Error Message Box When Editing a Profile
Error messages were sometimes erroneously generated (even though no real error existed) when editing e-mail profiles.
Incorrect Display of Dual
Lens Video Motion Windows
Whenever Dual Lens Video Motion (Setup Menu > Event Settings) had been set, the detection of a Video Motion event in the image sensor that was currently not active would (apparently) generate a false (VM) alarm in the currently active sensor.
Signal-Out State Change
Caused by Switching View Between Image Sensors
Changes to the Signal Out state made via e.g. HTTP-API whereby the state was set to „high“ would get reset to „low“ whenever the image sensor was switched.
Wrong Files Transferred
during FTP with “Clip” File Type
Certain combination of settings for the Time to include before start time, Time to include after start time and the Clip Frame Rate sometimes resulted in missing event pictures or the transfer of post-alarm image when Time to include after start time had been set to Off.
Time Tables for the use of
Logo Profiles for FTP Transfers not Being Used
If a time table/profile was selected for use by the Logo Profile used in a FTP Profile, it was not used/observed.
Response to HTTP Requests
Only Contained LF (Instead of CRLF)
Responses to HTTP requests now contain CRLF instead of only LF to signal a new line.
Network Messages (IP Notify)
Can Only be Sent to a Maximum of 10 Recipients
It is now possible to (again) send IP Notify messages to more than 10 recipients.
Color/Tint-Error in Certain
In certain Pan/Tilt positions (during Software Zoom) the image was a strongly green tinted.
Level Indicator for
PIR-Signal Was Shown for Camera Models Without the Sensor
The display of the PIR Level Indicator was possible on models (V10) that do not posses the PIR sensor.
Display of „Empty“
Dialog Pages in Other Languages
The Spanish and Japanese versions of the camera software contained an error which sometimes caused the display of an empty page when certain menu dialogs were selected.
Sensitivity“ Selection in the Quick Controls of Basic and Web
The presence of the Microphone Sensitivity entry in the Quick-Controls for camera models that do not have a microphone let to errors.
Comment Text Forwarding via
IP Receive (RC) Event Did Not Work Properly
The IP Receive (RC) event option (Setup Menu > Event Settings) for Comment Text Forwarding did not function properly. The text received, regardless of which option had been selected, was forwarded without any formatting and appeared in the forwarded image and JPG comments. This occurred even when Off had been selected.
Event Permanently Deactivated
When Camera Arming Automatically (per Event) Deactivated
If an event was triggered during the dead time of an event that had disarmed the camera, this event trigger would remain deactivated when the camera was armed again.
Incorrect Filename Generated
by Event-Controlled FTP Transfer Using Options „MxPEG Clip“
and „Event Directory“
Files and clips saved using these options could not be played back in MxViewer.
Mouse-Over Function in
MultiView not Possible when „Stop“ Selected
Clicking on the „Stop“ Button not only stopped the streaming of images in MultiView, it also had the undesirable effect of disabling the mouse-over function and all other functions selectable in the “shift-click” menu.
Image From Selected Image
Profile Not Transferred via FTP Started By HTTP API
An image profile name passed to the HTTP API call while executing an FTP transfer (
name>) would be ignored—instead,
only the live image would be transferred.
SI Events Activated Too Late
– Primarily by Mega(Pixel) Resolution
The reaction time of an SI Event generated by a „High“ or „Low“ signal is now significantly faster due to the De-Bounce Time being ignored whenever „High“ or „Low“ is used.
Limitations / Precautions:
The use of Trigger Conditions Rising or Falling sometimes caused a delay of up to 2 seconds before the event was signaled in the live image.
If any of the additional Signal Inputs (SI2, SI3,...) are used, selecting a Trigger Condition other than what is used by the first SI to generate an „instant“ signal (via „High“ or „Low“), will delay the first SI's signal. Therefore, if rapid event generation from one of the Signal Inputs is required and more than one is activated, make sure that those Signal Inputs are all using the same Trigger Condition as the SI.
Incorrect E-Mail Attachment
Sent When Pressing Phone Button 5
Pressing the 5 button on a touchtone telephone resulted in the wrong attachment being sent.
User Click (UC) Event not
Generated When Pressing Phone Button 6
The camera did not reliably and consistently generate the User Click (UC) event when pressing button no. 6 on a touchtone phone when calling the camera.
Error in Setup Menu Dialog
„General Image Settings“ on IT and Web Camera
Error in VM Day/Night
Switching Caused by Selecting „Copy Video Motion
After defining VM Windows for a particular sensor and then activating Copy Video Motion Definitions (so that the other sensor would use the same settings), the settings for adjusting the Video Motion Night Mode (Lux value which determines if and when detection is to be disabled) had been switched.
Release Date: 2006-06-27
The Player screen now has a speaker icon that can be used to toggle the sound recorded by the camera on or off—provided that you are using Internet Explorer on a Windows computer.
This menu allows setting the sensitivity of the camera microphone.
Allows setting all volume levels for the camera speaker and can play back the camera sound files on the speaker.
Allows configuring the camera to deliver the best image quality. This softbutton opens a dialog, which shows all configuration changes, allowing you to approve or cancel the changes.
Settings can be Stored in
If desired, the settings from using the expanded softbuttons can be stored in the camera's flash memory. This option can be deactivated in the dialogs called by the individual softbuttons.
& Record: VM window
The default VM window will only be set if no other windows have been defined.
Audio messages can be deactivated.
All Welcome messages for inbound, outbound and DTMF acknowledgement messages can be deactivated.
The Audio Data Timeout (the time after which the camera hangs up when no audio data are received) can now be configured in the Admin Menu > VoIP Settings dialog.
The Call Duration can be set to Unlimited.
When using DNS, you can
configure NAT address resolution:
If the camera is running behind a router with a dynamic IP address (e.g. regular DSL connection), it can determine the router's external IP address, if the router uses a DynDNS service to publish its external IP address. To use this feature, enter the router's DynDNS name as NAT address in the VoIP Settings dialog.
On IT models, activating audio for MxPEG recording (event/snapshot) did not work.
IP Notify error: When sending empty network messages, the sending camera sometimes produced error messages.
IP Notify error: When sending IP Notify network messages using the HTTP protocol (even to itself), the camera sometimes produced errors when sending the message.
IP Notify error: When receiving IP messages for the IP Receive event, the sender address was not determined correctly. This produced warning messages of the EventD and the address did not appear in the JPEG header of the image files.
Error 52 after rebooting –
camera in administration mode
This error occurred when Mono cameras had to deliver images via ImageLink (/cgi-bin/image.jpg) directly after rebooting and before the live image processing itself had started.
instances of the IE ActiveX component
This error sometimes prevented deactivating the camera sound when using the ActiveX control. This error also played the live sound picked up by the camera microphone when reviewing recorded events in the Player screen.
When renaming ACL groups, it was possible to create duplicate group names.
The softbutton captions can again contain special characters (e.g. Hebrew or Arabic).
The camera used the wrong time when triggering a periodic event (PE) after the camera had performed a day/night switch.
When setting the hangup time for VoIP connections to "Never", the VoIP connection broke off after the camera initially answered the call.
Color distortions in dark
Dark images sometimes shows distorted colors, especially when colored sources of light (e.g. car backlights) where in the image.
When changing the exposure settings (Setup Menu) with the camera in the dark, the camera showed a short "flashing", i.e. image exposure was off for one image.
Manually deleting the "access" section of a camera configuration file made all camera pages publicly accessible instead of using the factory default settings.
Texts received via the RS232 interface or in a network message were sometimes clipped after the last blank in the text.
After rebooting, the Admin dialog showed the wrong tooltip "zoomexpfield" for the Store menu item.
Release Date: 2006-04-06
The difference in the software features of the Basic, Web, IT and Secure models have been revised and partly changed. The following list contains the most important changes:
IT models can also be ordered as Night models.
IT models also have event and continuous recording (MxPEG with audio).
IT models can display logos in the images.
All camera models support the built-in speaker.
All camera models have the full number of time table profiles and custom days.
Event Logic EL1/EL2 is only available for Secure models.
The new Master/Slave features are only available for Secure models..
Open http://www.mobotix.com/products > Feature Overview to find a detailed list of the differences between the individual models.
With software release 126.96.36.199, the following new features have been added to the software:
Simplified Camera Operation—Expanded Softbuttons and Audio Icon
Master/Slave Feature and Custom Signals
Scheduled Access Control by Supervisor
New softbuttons and icons have been added, which are aimed at facilitating crucial configuration tasks. Using these softbuttons can automatically carry out several configuration settings, which would otherwise involve making the settings manually in several dialogs. The settings are shown in a separate dialog, which also allows storing the settings permanently.
This softbutton will transmit the audio channel from the camera microphone to the computer's sound system, provided you are using Microsoft Internet Explorer on a Windows computer.
This new button allows activating/deactivating the audio channel from the camera microphone, provided you are using Microsoft Internet Explorer on a Windows computer.
This softbutton can set are configuration parameters required to arm the camera's event control, including the video motion detection and set the Event Recording mode. If the camera detects a video motion (VM) event, it will store the event as an MxPEG stream.
This feature allows to control the arming of cameras in a MOBOTIX camera network (the so-called "Slave" cameras) from one special camera, the "Master" camera. In other words, the Slave cameras will always be armed, if the Master camera is armed. The arming state will be synchronized as set in the General Event Settings dialog and in the Action and Messaging dialogs.
Open Setup Menu > General Event Settings to configure the Master/Slave settings as required.
The Custom Signals allow accessing the physical signal input of one camera that is connected to the alarm system, from any other camera of the MOBOTIX camera network. The status of the signal input of the Master camera can be used by the other cameras to control individual arming settings.
The Custom Signals are also configured in the General Event Settings dialog.
The new Supervisor user allows
limiting access to the MOBOTIX camera for any user groups (even the
admins group) according to a global rule (for all groups) or
individual group rules.
A typical example would be scheduled access control for camera administrators to prevent misuse of their administration privileges where access to otherwise blocked video/audio data is concerned. In such a scenario, the Supervisor would limit the access of the admins group to a specific time once a week week, during which the administrators would be accompanied by a trusted employee.
The More/Less setting will be stored with the camera settings when storing the configuration and will thus be available even after rebooting.
Camera Arming can be controlled using the VoIP (touchtone menu) remote-control.
Improved White balance for images with bright white areas.
Improved Backlight correction: bright image areas will not be amplified any more.
The Arming Delay/Disarming Delay when using the signal input (SI) can now be configured in the Setup Menu > General Event Settings dialog.
Bright white (overexposed) areas in the image led to false VM events when exposure control intervened after changes in brightness.
When Recording Snapshot (JPEG) Images Without Post-Event Images
This sometimes produced corrupt or missing 'INFO.JPG' files in the sequence folders of the stored event images.
and Errors When Storing the Retrigger Events in Snapshot Recording
This error could lead to different folder contents on the file server and in the internal event ramdisk. If this was the case, the camera event Player and MxViewer with direct file server access showed different event images.
definition of Admin passwords with special characters in the
Special characters could be entered in the Quick Installation wizard when setting the admin password, but were clipped after the first special character.
Recording When Armed Using the Signal Input
This configuration activated continuous recording in the camera—independent of the status of the signal input used for arming the camera.
Some e-mail servers replied with the message "251 - user not local - mail will be forwarded", prompting the camera to abort the sending procedure.
Triggering of IL Event
The lux trigger value had not been evaluated properly and IL events were also triggered below the specified value.
The LED for VoIP activity also lit up if the LED main switch had been deactivated.
Release Date: 2005-12-22
Version M10-V188.8.131.52 is mainly a bugfix release that fixes a software bug in version M10-V184.108.40.206.
Malfunctioning video motion detection (VM) from changes in the exposure control are now suppressed.
Release Date: 2005-12-08
Version M10-V220.127.116.11 is mainly a bugfix release that fixes a software bug in version M10-V18.104.22.168.
The previous versions M10-V2.2.2 had a bug when assessing the state of the signal inputs SI, SI2, SI3, and SI4.
When assessing the state of the signal inputs, the switch states "open" (high) and "closed" (low) had been cross-matched. This also meant that the states "rising" and "falling" of the signal flank had been switched.
This error causes cameras, that were set to trigger an event upon detecting the "signal input open" state now triggered events when the signal input was closed.
This error has been removed in M10-V22.214.171.124.
Caution: If the error had been fixed temporarily for running with software M10-V126.96.36.199 by inverting the signal input trigger from "open" to "closed" or from "rising" to "falling" (or vice versa), you will have to restore the original settings after uploading software version M10-V188.8.131.52.
We recommend to thoroughly test the settings after updating to version M10-V184.108.40.206 when using the Signal Input events.
Management of access control settings has been enhanced in several dialogs.
The Users and Passwords dialog now displays a warning if single areas of the camera are still publicly accessible (i.e. without entering a user name and password). Public access can be disabled directly from this dialog.
The Group Access Control List (ACL) dialog allows removing public access from all areas by clicking on the "Disable all" button.
Upon delivery, image and event settings cannot be changed without user identification.
Improvement of image quality when getting night images using the image link.
Bugfix: When retriggering events, the event back link got lost.
Bugfix: When trying to register for the first time for VoIP Telephony, the settings for NAT had not been used. NAT settings had only been used upon the second registration attempt.
Release Date: 2005-10-28
Individual exposure control for both image sensors.
Redesigned image control and white balance handling to avoid showing tiles in the images.
Extended access control dialog to provide granular access control to groups of users. See Group Access Control List and User Groups and Passwords
Event Logic (EL) events allow logical linking of basic events and also provide for testing the order of occurrence of the selected events.
The camera software can now set to individual exposure times for the image sensors. Even extreme differences in brightness detected by the two image sensors are handled well now.
Full frame rate is now attained by the left image sensor as well.
Dual image and picture-in-picture modes are available for Day/Night models.
day/night switch (Night models only) improved by occasional
evaluation of Day sensor to avoid locking on the Night sensor when
IR illumination is used or when night mode is set manually.
Note: When trying to manually switch from day to night mode by covering the Day sensor (right lens as seen by the camera), the software may require up to 17 minutes to return to day mode.
The new Gray World color profile can be used for white balance if all other color profiles produce unsatisfactory results.
M10 DevKit sometimes shows loss of image quality when using sensor cables with different lengths (greater than 50 cm/20").
$(IMG.EXP.LEFT.SECOND) image variable had led to undefined software behavior under rare conditions.
Under certain rare conditions, a camera set to deliver live dual megapixel images was prone to delete all images stored on a file server. A typical symptom of this behavior was a value of 999,999 lost events in the Camera Status dialog.
When showing picture-in-picture images (RiL or LiR), switching back to single image display (Right or Left) sometimes displayed faulty image areas where the picture-in-picture image had been before.
For certain panning positions (image area moved by clicking into the live image) and with zoom levels 2x or 4x on the right image sensor, switching to the left image sensor may produce faulty images or distorted colors. Moving the panned image area to a different position will resume normal operation.
Second Video Motion (VM2) event with separate window definitions available (click on More). VM windows are displayed with darker dotted (bbbwbbbwbbb...) frames, while VM2 windows have brighter dotted (bbwwbbwwbbww) frames (where b = black and w = white).
Motion (VM, VM2) may be extended to the image sensor that is not
shown on the Live screen using the Dual Lens Video Motion
Note: This may reduce the frame rate.
Video Motion (VM, VM2) windows from the right image sensor can be used on the left image sensor when camera switches from Day to Night mode (Night models only). Use the Copy Video Motion Definitions parameter in Event Settings to control this behavior.
can be linked logically by evaluating two sets of events. You may
define two different (logical) Event Logic events, EL and
Note: These events should be used for filtering actions and messages.
Event Logic allows evaluating logical AND relationships between events, including order of occurrence, sliding time window and minimum time between events. This provides a method for detecting direction of motion.
When arming the camera using signal input (e.g. a key switch), arming is delayed by 60 seconds to allow leaving the camera's image area; this delay is counted down at the bottom of the image.
Improved Signal Input: Up to four signal input events (SI, SI2, SI3, SI4) can be set, using the signal input pin and the pins of the serial interface (extended signal input). Besides detecting the current state (open or closed), you may also trigger upon rising, falling or changing signal flanks.
De-Bounce Time prevents uncontrolled flip-flopping of signal input events.
FTP Profiles: When using temporary file names for FTP transfers, the new Enable, delete before rename option will delete an existing file before renaming the temporary file. This option is intended for FTP on Microsoft IIS servers as IIS does not support renaming to an existing file name.
When using FTP transfers, JPEG clip files will be stored in a common directory.
When using FTP transfers, MxPEG clip files will be stored in a common directory named after the first frame number of the clip.
Control of signal output (SO) removed from LED Setup dialog and new link to test signal output has been added to the Actions dialog.
The standard softbuttons Actions enable and Actions disable of the Player screen have been replaced by the Recording on and Recording off buttons. These softbuttons will no longer activate/deactivate the complete event control, but only event recording.
It is not possible to stop Continuous Recording using the Arming switch set to signal input SI in the General Event Settings dialog, when using a key switch, for example. In this case, set the Arming parameter in the Recording dialog to the same value as in the General Event Settings dialog.
The Illumination (IL) event may not work properly and may trigger events above or below the chosen value.
FTP and E-Mail transmissions may fail if the frame rate in the live image drops below 1 frame/second. This will only appear in these extreme situations:
long exposure times with dual (side-by-side) image
regular exposure times with dual (side-by-side) MEGA image (1260×960)
when reducing the frame rate
Under certain illumination conditions, changing illumination may trigger a VM (Video Motion) event.
The description of the event selection box in the Messaging dialog, Messaging section, contains a wrong header and text.
Access to function sets like live image, recorded image, image link, and image control vs. event control etc. can be permitted to groups of users by defining Group Access Control Lists.
Up to 10 access groups can be defined in Group Access Control Lists.
Up to 30 users can be be assigned to access groups in User Groups and Passwords.
Public Access to function sets can be granted or denied in Group Access Control Lists. (In former versions everything was public that was not protected by a password.)
Enabling access to Screen/View basic function groups in Group Access Control Lists will set necessary additional access rights for the group, but can removed manually one by one.
Administrator group admins cannot be removed in User, Groups, and Passwords . At least one member of that group (not necessarily called "admin") cannot be removed.
New user names, group names and passwords may only contain these characters: "A-Z", "a-z", numbers, "_", "." and "-". Old user names and passwords will be kept.
Minimum length for user and group names is 3, maximum length is 16 characters.
Minimum length for passwords is 5, maximum length is 8 characters.
New users may be created using the undefined group. This is intended behavior to allow presetting users and assigning them to groups later on.
Access to event directories of other cameras on the same file server is restricted by the accessing camera, not by the camera administering the directory as it was before.
Access to event images on file server of a camera running software equal or higher than M10-V220.127.116.11 requires software M10-V18.104.22.168 or higher.
Incoming SIP calls can be restricted to allowed phone numbers in the Phone Call-In dialog.
ISDN data transfer: disabled compression for protocol headers for shorter delay and better performance.
Camera Information lists all ports the camera is listening on.
SIP Telephony: When trying to use VoIP telephony from behind a NAT router, registering with the registrar will only work upon the second attempt. Depending on the duration set in Registration Expires After, the second attempt may take up to five hours.
Only English and German language is up-to-date.
New link to Manage Other Cameras dialog in Admin Menu.
Background image can be set in Language and Entry Page.
Announcement of IP address and network information by pressing a camera button can be disabled in the Loudspeaker and Microphone dialog.
Support of two weather stations added (Reinhardt and Davis) that are connected to the serial interface. For additional information, see MOBOTIX Kurzanleitung Wetterstation (MOBOTIX Weather Station Manual, German). To configure weather stations, open Serial Interface and Modem Setup and set Serial Interface to Weather.
When using an NTP time server for periodic time synchronization, one camera may provide NTP time service for all other cameras. This will also work if the connection to the NTP time server fails.
When an external time server is
not available or the connection is shaky, one camera can be used to
run as backup time server On the "time server" camera,
enter the IP address
127.127.1.0 as time server and
enter the "time server" camera's IP address as time server
on the other cameras.
MxViewer is not part of the camera software M10-V2.2.2 any more. To download the newest version of MxViewer, go to www.mobotix.com/download/.
For current features of MxViewer see separate documentation.
Improved image quality for scaled images.
Release Date: 2005-09-14
It is now possible to connect two weather stations (from Reinhardt and Davis Instruments) to the serial interface. The camera can display the weather data in the image and it can automatically upload the data to an FTP server. The weather station application is configured in the Serial Interface and Modem Setup dialog.
certain circumstances, the camera disabled the Obscure Image Area
This error occurred only when Obscure Image Area had been enabled and the configuration had been changed (right/left lens, resolution, zoom/panning, softbuttons, etc.) while the specified time table had deactivated the function. After that, it was impossible to reactivate the Obscure Image Area function. Reactivating was only possible if a configuration change was taking place at a time when the time table had activated the Obscure Image Area function. This bug was part of all releases of MOBOTIX cameras M10/D10/V10 since software version M10-2.0.
The Java applet for the live image (Browser Quick Control) did not show the live images properly any more.
It is now again possible to delete the default route in the Ethernet Interface dialog.
If the NTP time server in the Time and Date dialog had been set using a host name (i.e. not an IP address) and the DNS server was not reachable, the camera stopped booting and initiated a reboot.
If the NTP server had been used in conjunction with ISDN data dial-out, but ISDN data dial-out had not been set as default route, the camera stopped booting and initiated a reboot.
The second IP address in the Ethernet Interface dialog had not been set with activated DHCP and an empty main IP address.
Initial DNS server for ISDN dial-out has been changed; the DNS server address that is being used is now listed in the Test Network Configuration dialog.
A timeout has been included in all functions that use NTP requests. If the timeout is reached, the corresponding application will issue an error and the normal operation will resume. Errors had occurred when network settings had not been set properly or DNS servers had failed to respond.
Release Date: 2005-07-06
The most important advance of this software version vs. software version M10-22.214.171.124 is the full-fledged integration of Voice over IP (VoIP in short) for all functions that so far could only be operated using ISDN. Manage Voice Messages, Phone Profiles, Phone Call-In and Camera Phone as well as Messaging and Messaging 2.
The Language and Entry Page dialog now allows changing the background image of the user interface by selecting any image file stored in the camera.
A link for testing the settings has been introduced in the Actions and Enhanced Signal Out Options dialogs.
A link for testing the User Click (UC) has been introduced in the Event Settings dialog.
When using Event Storage on external file server, the camera can periodically copy the logfile for event storage, the web server logfile and the system messages to the file server.
If the serial interface has been set to Weather mode, the camera can display the data from a supported weather station in the image. On top, the camera can automatically send the (raw) weather data to an FTP server for further processing.
Reading 'multiline replies' from some severs created problems with some providers when sending e-mails.
When starting ISDN phone call-in using the web interface of the camera (i.e. not after a reboot), the phone key "3" did not work.
The web server logfile in "Less" viewing mode sometimes missed the date information although accesses occurred on different days, leading the user to believe that the accesses had actually occurred on the same day.
FTP event tar file transfer in the Time Tasks has been fixed (bug since version 126.96.36.199).
profiles starting with the string "
not available for transferring an event tar file in the Time
ActiveX plug-in in the Player screen will work with a user and password set for the user access level in the Users and Passwords dialog.
The options for event LEDs have been moved from Admin Menu > LED Setup to Setup Menu > General Event Settings.
The Functional Overview marks new features using the "New Feature!" bullet, enhanced features are marked by an "Enhanced Feature!" bullet.
These notes list the most important news of the software releases M10-V2.0.3 and M10-V2.0.5 for MOBOTIX M10 and M10-V2.1.0 for MOBOTIX D10 camera models.
As the most important improvement of this software release, recording has been completely redesigned to omit the scheme that was used up until now (pre-alarm, alarm and post-alarm images), introducing a clip-based recording mechanism that is completely based on the MOBOTIX MxPEG streaming format. The old functionality can be used almost as before with minor changes. The new recording mechanism also provides for continuous and event-controlled video clip recording. Recording in MxPEG format also allows recording the sound from the camera microphone.
Common software for all MOBOTIX camera models. Specific model differences are read from the different camera models.
Reorganization of the permanent flash memory in preparation of future software enhancements (especially the VoIP telephony feature).
Changed format of upload files. Upgrading a camera to M10-V2.2.0.x will activate a new upload format that will not allow downgrading to previous software releases. This was necessary due to the reorganization of the permanent flash memory.
Prefix for default camera name changed from M to mx,
to avoid confusion with the M10 model designation. Example
New: If the camera starts using the backup operating system (e.g. after a failed software update), the sound Alarm is played and the user interface is red instead of blue.
New for D10 models: When using the magnet to activate the reed switch at boot time, the factory default configuration is used (except passwords). After that, the reed switch is polled for another five seconds; if it is still on, the camera tries to obtain an IP address using DHCP.
New: When booting with an IP address assigned by DHCP (reed switch or front key), the sound Boing will be played twice.
Enhancement: Camera Status contains statistics on Ethernet packets.
New: Web Server Logfile logs all accesses and failed access attempts (wrong passwords). This list can be saved externally.
Time and Date no allows using the
with up to three time servers. If Adjust periodically has
been activated, you can see the status of time synchronization.
Bugfix: Modem receives Disconnect Modem string before trying to establish a connection. This resolves sporadic problems with the Siemens MC35T GPRS modem at boot time.
Enhancement: LED Setup dialog has been adapted to D10 camera models.
New: For M10-DevKit, Image Sensor Configuration in the Admin Menu can be used to control, which sensors have been installed.
New: Image format VGA2 with 640x240 pixels resolution, high frame rate and interpolated lines.
New: When displaying dual or picture-in-picture images (only Dual, not Night models), the images can be separated by a small bar. This feature can be deactivated using the Text & Display Settings > Cover Borders parameter.
Bugfix: MxPEG Stream does not contain sound data when accessing the camera with a guest login.
Dropped: Custom image size is dropped for image profiles and image link.
Bugfix: Obscure Image Area (OA) feature now works with rotated, mirrored, zoomed and panned images.
Bugfix: Auto contrast in the image link was not working properly at times.
When getting an image from the image sensor that is currently not
active, both camera images are read for ten seconds and the
symbol is shown in the image.
Enhancement: Improved Camera Night Switch (DY/NI), trigger value for switching back is adjusted dynamically.
New: Night Improvement is only activated with MxPEG mode when set to Auto, but can also be activated/deactivated manually for MxPEG and JPEG modes.
signals reduced frame rate due to high exposure times,
signals reduced frame rate when reading dual images.
New: Enhanced functions in ActiveX component for the Live and Player screens (only when using Microsoft Internet Explorer on Windows).
New: When switching between the Live and Player screens, the ActiveX component "remembers" its last mode (only when using Microsoft Internet Explorer on Windows).
Bugfix: Several workarounds to fix problems when viewing live images with Konqueror or Safari browsers.
New: Recording settings moved to new dialog linked from the Setup Menu.
New: Recording enhanced to MxPEG format (video clips with audio).
New: Recording offers three modes: Snap Shot Recording (JPEGs as before), Event Recording and Continuous Recording (the latter two only available in Secure models).
New: Recording can now be triggered, retriggered and stopped explicitly. All activated events can be used for these features. Additional parameters provide for adequate post-alarm recording after the selected events have been detected.
New: When using Event Recording or Continuous Recording, the Recording dialog allows setting the standard frame rate. Continuous Recording can automatically increase the frame rate if the camera detects one of the selected events.
New: Sound from the camera microphone can be stored when using Event Recording or Continuous Recording.
Change: The interval between images of pre- and post-alarm images for Snap Shot Recording in the Recording dialog can now be set to values smaller than one second. The behavior now corresponds to recording in version M10-V2.0.
New: When using Event Recording in the expanded Recording dialog, History Images can be stored at regular intervals triggered by the Periodic Event (PE) or the Time Task (TT) event. The image format is selected from one of the Image Profiles. (From model M10-IT).
New: Recording can now be controlled using the Arm Recording main switch or time table profiles.
In Snap Shot Recording mode, activate the Pack story
option to pack JPEG images into one single
file on the external image storage (file server).
When using Event or Continuous Recording, the camera creates
.jpg files on the file
server. Event and history images are stored as JPEG files.
Change: Switching to clip-based Event and Continuous Recording has led to a changed meaning of the folder structure. The folder number does not necessarily correspond to the number of recorded events.
Change: File deletion strategy on file server has been optimized.
REC symbol will always be shown in the image, even
when recording has been deactivated.
Colors of the
Not active (e.g. Arm Recording set to Off)
Waiting for action
New: Phone Call-In and Phone Profile provide for controlling the camera arming main switch using the phone keys. The "3" key of the phone now toggles between Arming activated and Arming deactivated.
Bugfix: Removed error that led to preemptive exit of the function for evaluating the IP Receive (RC) event when receiving several IP messages at once.
Additional signal inputs
of the serial interface can be set in the expanded Event Settings
dialog (from M10-IT models). The serial interface has to be
set to Data, I/O Mode. (This feature was present in software
Enhancement: IP Notify Profiles dialog expanded. Messages can be sent sequentially or in parallel to one or more IP addresses; message can be sent as text only or using HTTP/1.0 protocol with password authentication. Besides text, the message can include a video clip file, image information (JPEG header) or the system messages of a specific time frame.
Enhancement: System messages can be limited to specific time ranges when sending the messages via E-Mail.
New: New events in expanded Event Settings dialog:
Triggered when a recording begins
Triggered when a recording ends
Triggered when the Recording Terminate functions exits
Triggered when storing a History Recording (HR) image
Bugfix: Signal Output (SO) stopped working after rebooting a camera with software version M10-V2.1.0.
Change: Error messages for E-Mail (EM), FTP (FT), IP Notify (IP) and Phone Call-Out (CL) messages and actions are only shown as general message in the image; details are available in the System Messages dialog.
Dropped: Highlight Area for Video Motion Window (VM).
Change: Object Tracing (OT) and Video Motion Window (VM) are only detected by the image sensor that is currently visible.
Bugfix: The temporary
file name for FTP transfers is now created from
the serial number of the camera in hex notation and the internal
profile name in hex notation, to prevent errors from simultaneous
transfers using different profiles. Until now, FTP transfers were
only using the host name.
Change: Key 2 of the phone control now toggles the preset Audio Call-Out Profile between dial out and close connection. Key 3 of the phone is now used to control the Arming of the complete camera event control.
Bugfix: Updated the phone number in the "Zeitansage" example ISDN Audio Call-Out Profile.
Bugfix: Testing the ISDN Audio Call-Out Profiles was not possible under certain circumstances; error message sometimes returned the wrong profile names.