PCI-DB.com
  1. Driver
  2. Scanner Digital Camera Webcam
  3. MOBOTIX D10 Network Camera Firmware 2.2.3.24

MOBOTIX D10 Network Camera Firmware 2.2.3.24 Download

Posted at May 17, 2024 by PCI-DB Team

Install Driver Automatically
Device NameMOBOTIX D10 Network Camera Firmware 2.2.3.24
CategoryScanner Digital Camera Webcam
ManufacturerMOBOTIX
File Size7.7 MB
Supported OSOS Independent

MOBOTIX D10 Network Camera Firmware 2.2.3.24 Description

Fixes:

- 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 Pan/Tilt-Positions. 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.
- Erroneous „Microphone Sensitivity“ Selection in the Quick Controls of Basic and Web Models. 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 (http://<camera IP>/control/rcontrol?action=ftpcurrent&profile=<profile 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.
- 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 Models. Selecting General Image Settings from the Setup Menu on IT and Web models generated a JavaScript error.
- Error in VM Day/Night Switching Caused by Selecting „Copy Video Motion Definitions“. 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.

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related MOBOTIX Drivers

Find Missing Drivers

© 2024 PCI-DB.com - PCI Database Replacement. All rights reserved.