Release Notes for MOBOTIX MxDisplay Software
Document Information
Publisher:
|
MOBOTIX AG
|
Author:
|
Bernd Wilhelm
Thilo Schüller
|
Date:
|
2019-01-17
|
Document:
|
release-notes_en.html
|
Confidentiality:
|
public
|
Contents
The MOBOTIX MxDisplay is a video door intercom with touch screen, microphone, speaker, WiFi module, RFID module and integrated video management software for MOBOTIX door stations and cameras. These Release Notes contain a short technical description of the most important features of the software for the MOBOTIX MxDisplay.
Software Releases—Overview:
Release Version
|
Creation Date
|
Publishing Date
|
2.3.0.31
(MxDisplay+ only) |
2018-12-03 |
2019-01-17 |
2.3.0.30
(replaced by V2.3.0.31 ; MxDisplay+ only) |
2018-03-06 |
2018-03-13 |
2.3.0.28
(MxDisplay+ only) |
2017-11-07 |
2017-11-30 |
2.3.0.19
(MxDisplay+ only) |
2017-08-08 |
2017-09-06 |
2.3.0.18
(replaced by V2.3.0.19 ; MxDisplay+ only) |
2017-08-02 |
2017-08-08 |
V2.1.0.33
(MxDisplay+ only)
|
2017-10-10
|
2017-10-20
|
V2.1.0.26
(replaced by V2.1.0.33 ; MxDisplay+ only)
|
2017-09-23
|
2017-09-27
|
V1.0.2.16
|
2015-06-18
|
2015-06-26
|
V1.0.2.0
|
2014-11-14
|
2014-11-17
|
Notes:
- When installing the MxDisplay, make sure that the wire mesh of the network installation cable is properly connected to the ground contact as shown in the installation instructions. Failing to do so may result in a malfunctioning touch screen!
- Please download the stable customer releases of the software from http://www.mobotix.com in the Support > Download Center > Software Downloads section.
- Please send an email to intl-support@mobotix.com for feedback.
top
Software Release V2.3.0.31 for MxDisplay+
Creation Date: 2018-12-03
Publishing Date: 2019-01-17
Important Notes:
- This software will only run on MxDisplay+ devices (order numbers
MX-Display2-EXT-BL/PW
, MX-Display3[-b]
, MX-Display3-EXT[-b]
). For ease of reading, we will use the term MxDisplay instead of MxDisplay+ in these release notes!
- For updating the software, enter the IP address in a browser (user
admin
, password meinsm
) and select Update system software in the menu. By factory default, the MxDisplay is running as DHCP client and has an additional local IP address in the 10.x.x.x address range (see sticker on the back of the device) with a network mask of 255.0.0.0
.
- Make sure that the door stations and cameras have been updated to software release
V4.4.2.73
or higher (see Support > Download Center, Software Downloads > Camera Software section). Otherwise, the improvements and bugfixes listed below will not work.
- The current release
2.3.0.31
is different from its predecessor release 2.3.0.30
only in the additional bugfix "Do Not Disturb" Function.
Enhancements and Improvements
This is a service release and does not contain any new features compared to release 2.3.0.28
.
Bugfixes
- "Do Not Disturb" Function (
V2.3.0.31
)
On installations with several MxDisplay devices, when reactivating the status of the "Do Not Disturb" function on one MxDisplay device, the status was not displayed properly at the other devices.
- Reboot times after software update
A system reboot could take several minutes after a firmware update to version 2.3.0.28
on some devices.
- Network switches with IEEE 802.3az
Connecting a MxDisplay to a switch with activated energy saving mode according to IEEE 802.3az sometimes resulted in connection failures.
- Scrolling in long event lists
A system error could occur when displaying a long list of events and scrolling in this list.
Known Limitations
- Event search
When searching for general events ("lightning" icon), the device can show a wrong number of events or may not properly search the specified time range.
- Access control when using many door stations
If ten or more door stations are connected to one MxDisplay device, the Access Control dialog may not work properly.
- Counter for doorbell events
The displayed number of incoming calls is also incremented, if a doorbell at the door station is pressed or if a number is entered that is not assigned to this MxDisplay as intercom device.
- Display of door status
When using a door station with KeypadRFID, the door status will always show "Door is open", although the door contact and the door lock contact have been connected properly.
- HTTP/HTTPS access using Bonjour
Currently, the Bonjour service (used to make MOBOTIX devices known to other network devices) on an MxDisplay will advertise 80 as HTTP port and 443 as HTTPS port, regardless of the actual ports that have been assigned using the browser-based user interface of MxDisplay. Regardless of this, the unit uses the HTTP/HTTPS ports specified in the browser interface.
top
Software Release V2.3.0.28 for MxDisplay+
Creation Date: 2017-11-07
Publishing Date: 2017-11-30
Important Notes:
- This software will only run on MxDisplay+ devices (order numbers
MX-Display2-EXT-BL/PW
, MX-Display3[-b]
, MX-Display3-EXT[-b]
). For ease of reading, we will use the term MxDisplay instead of MxDisplay+ in these release notes!
- For updating the software, enter the IP address in a browser (user
admin
, password meinsm
) and select Update system software in the menu. By factory default, the MxDisplay is running as DHCP client and has an additional local IP address in the 10.x.x.x address range (see sticker on the back of the device) with a network mask of 255.0.0.0
.
- Make sure that the door stations and cameras have been updated to software release
V4.4.2.73
or higher (see Support > Download Center, Software Downloads > Camera Software section). Otherwise, the improvements and bugfixes listed below will not work.
Enhancements and Improvements
Elimination of WiFi WPA2 Vulnerability
This firmware release 2.3.0.28
eliminates a vulnerability in the WPA2 encryption mechanism ("KRACK issue") when using the MxDisplay in a WiFi network environment.
Bugfixes
- Access PIN and bell messages
Adding a new PIN code for a door station in MxDisplay could delete doorbell notifications that had been defined in the Admin Menu > Video Door Station > Bell Behavior and Video Mailbox dialog, section Messages System Configuration. As a consequence, calls assigned to these doorbell notifications did not work any more.
- Switching lights on/off
After activating the lights connected to a door station via MxDisplay, it was sometimes not possible to switch the lights off again.
- Screen saver on floor call
After receiving a doorbell notification of a configured floor call, the device failed to activate the screen saver.
- HTTP commands via softbuttons
When using HTTP commands as an action of an MxDisplay softbutton, using a Tilde sign "~" led to an error when executing the command.
- Name of selection dialog for configuring the message system
The Settings > Installation > MxMessageSystem > Connection Data > Type dialog showed the title Sensor instead of Type.
Known Limitations
- Access control when using many door stations
If ten or more door stations are connected to one MxDisplay device, the Access Control dialog may not work properly.
- Counter for doorbell events
The displayed number of incoming calls is also incremented, if a doorbell at the door station is pressed or if a number is entered that is not assigned to this MxDisplay as intercom partner device.
- Display of door status
When using a door station with KeypadRFID, the door status will always show "Door is open", although the door contact and the door lock contact have been connected properly.
- HTTP/HTTPS access using Bonjour
Currently, the Bonjour service (used to make MOBOTIX devices known to other network devices) on an MxDisplay will advertise its HTTP port 80 and HTTPS port 443, regardless of the actual ports that have been assigned using the browser-based user interface of MxDisplay. Regardless of this, the unit uses the HTTP/HTTPS ports specified in the browser interface.
top
Software Release V2.3.0.19 for MxDisplay+
Creation Date: 2017-08-08
Publishing Date: 2017-09-06
Important Notes:
- This software will only run on MxDisplay+ devices (order numbers
MX-Display2-EXT-BL/PW
, MX-Display3[-b]
, MX-Display3-EXT[-b]
). For ease of reading, we will use the term MxDisplay instead of MxDisplay+ in these release notes!
- The current release
2.3.0.19
is different from its predecessor release 2.3.0.18
only in the additional bugfix Configuration changes and power failure.
- For updating the software, enter the IP address in a browser (user
admin
, password meinsm
) and select Update system software in the menu. By factory default, the MxDisplay is running as DHCP client and has an additional local IP address in the 10.x.x.x address range (see sticker on the back of the device) with a network mask of 255.0.0.0
.
- Make sure that the door stations and cameras have been updated to software release
V4.4.2.69
or higher (see Support > Download Center, Software Downloads > Camera Software section). Otherwise, the improvements and bugfixes listed below will not work.
Enhancements and Improvements
Support of the MxMessageSystem
Starting with firmware release 2.3.0.19
, the MxDisplay supports the MxMessageSystem. This adds several new features that are described in more detail further down.
To configure the MxMessageSystem, open the new Settings > Installation > MxMessageSystem dialog. When configuring, make sure that the connection data is identical to the connection data on the door stations or cameras that are exchanging messages with the MxDisplay device. To define the messages themselves, open the new Settings > Installation > MxMessageSystem > MxMessages dialog.
Receiving MxMessageSystem Messages
The MxDisplay device can react to MxMessageSystem messages. This means that you can execute softbutton functions from an MxMessageSystem message to switch to the Live view or to open a door, for example. Note that you also need to specify the MxMessage that should trigger the softbutton function. In addition, a softbutton can also use the new MxMessageSystem function to visualize messages that contain a parameter, e.g., you can show the current state of the lights (on/off) on the display.
Sending MxMessageSystem Messages
The custom softbuttons can also be used to send messages using the MxMessageSystem. You can thus send messages via the door station to a connected MX-Output-Box to open a gate or to switch the lights on or off. When defining the softbuttons, select the message that will be sent using the new MxMessageSystem function.
"Room Thermostat" Feature
This firmware release also includes the new room thermostat feature that can control one or more remote-controlled heating valves depending on the current room temperature. This feature has the following properties (only the most important ones listed):
- The heating valve is controlled directly via the signal output of the MxDisplay device or indirectly using an MxMessageSystem message to an MX-Output-Box, which in turn controls the valves.
- The MxDisplay device determines the room temperature using one or more temperature sensors (e.g., MxMultiSense).
- Likewise, the device can determine the state of a window contact directly using the signal input of the MxDisplay or indirectly by MxMessageSystem messages from an MX-Input-Box that is connected to the window contact.
- The desired room temperature is set in the MxDisplay device. This includes defining a hysteresis that is used to compensate short-term temperature differences.
To configure the feature, you should create a new view in MxDisplay (e.g., by the name of "Room Temperature") that contains a softbutton of the new Room Temperature function type. Once you tap the button, you can set all relevant parameters in the Room Thermostat dialog. Once you have completed the configuration, all values will be displayed in the new view and the room temperature control is valid.
For more information on this new feature, please consult the Configure an MxDisplay to Control Thermostats tutorial under Support > Download Center > Software Downloads > MxDisplay in the Application Tutorials section.
Doorbell Signaling Using MxMessageSystem Messages (for "Large Installations")
A door station with a KeypadRFID module can now send a message to all connected MxDisplay devices when entering a specific combination of digits. This will prompt the MxDisplay device to ring that had been configured to respond to this combination of digits. The device will then execute the other functions as defined (show live image, activate intercom, open door, switch lights). In contrast to the "classic method" used before, no permanent connection between the MxDisplay devices and the door station (via the internal "EventStream") is required. This allows connecting virtually any number of MxDisplay devices to one door station.
After properly configuring the MxMessageSystem (see above) and defining a message that is used for receiving the specified combination of digits, the signaling on the door station or camera is actually configured on the MxDisplay device in the new Settings > Installation > Camera Configuration > MxMessages dialog. Make sure to define one receive message of the state of the "bell button" and one send message each for the "door opener" function and the "light switch" function, respectively.
The "bell parameter" should be set to the combination of digits and the letter for the function button that should be pressed on the KeypadRFID to trigger the doorbell message (B = bell button, M = mailbox button, K = key button, O = OK button, E = ESC button, Example: 2121B
). Ensure that the message IDs correspond to those sent by the KeypadRFID and received by the MxDoorMaster. Among other things, the KeypadRFID needs to have a properly configured "Keypad" message of the "Function Code" type, among other things.
Notes:
- The mailbox functionality of a door station will not be supported when using this signaling method.
- For more information on this new feature, please consult the Configure a T25 with Keypad, Door Master and MxDisplay For a "Large” Installation tutorial under Support > Download Center > Software Downloads > MxDisplay in the Application Tutorials section.
Further Improvements
- Floor Call
When using the floor call feature, you can specify the duration of the ring tone and other settings by tapping on Extended.
Bugfixes
- Configuration changes and power failure
After rebooting MxDisplay by removing and restoring the power supply of the device, changes to the configuration sometimes had not been stored.
- Several MxDisplay devices on one door station
When connecting several MxDisplay devices with one door station (multi-party installation), the setting Live Image at Ring Only has to be activated to prevent others from accidentally seeing/hearing third-party conversations. In such a scenario, it sometimes happened that the audio channel of the door station could be heard at a display if this channel was activated inadvertently.
- Setting "Live Image at Ring Only"
If you activated the setting Live Image at Ring Only, this setting was sometimes deactivated after rebooting.
- Factory IP Address
Deactivating the factory default IP address sometimes closed the network connection of the MxDisplay device and required a reboot of the device to reestablish the connection.
- White Display
On rare occasions, the display of the MxDisplay device stayed white after booting.
- Displaying/changing camera configuration settings
In some cases, the MxDisplay did not always show the current camera configuration settings, if these had been changed from another device or from the browser-based user interface of the camera.
Known Limitations
- Access control when using many door stations
If ten or more door stations are connected to one MxDisplay device, the Access Control dialog may not work properly.
- Counter for doorbell events
The displayed number of incoming calls is also incremented, if a doorbell at the door station is pressed or if a number is entered that is not assigned to this MxDisplay as intercom partner device.
- Display of door status
When using a door station with Keypad, the door status will always show "Door is open", although the door contact and the door lock contact have been connected properly.
- HTTP/HTTPS access using Bonjour
Currently, the Bonjour service (used to make MOBOTIX devices known to other network devices) on an MxDisplay will advertise its HTTP port 80 and HTTPS port 443, regardless of the actual ports that have been assigned using the browser-based user interface of MxDisplay. Regardless of this, the unit uses the HTTP/HTTPS ports specified in the browser interface.
top
Software Release V2.1.0.33 for MxDisplay+
Creation Date: 2017-10-10
Publishing Date: 2017-10-20
Important Notes:
- This software will only run on MxDisplay+ devices (order numbers
MX-Display2-EXT-BL/PW
, MX-Display3[-b]
).
- The current release
2.1.0.33
is different from its predecessor release 2.1.0.26
only in the English name for the "floor call" feature (see below). This feature had been named "storey call" before.
- For updating the software, enter the IP address in a browser (user
admin
, password meinsm
) and select Update system software in the menu. By factory default, the MxDisplay is running as DHCP client and has an additional local IP address in the 10.x.x.x address range (see sticker on the back of the device) with a network mask of 255.0.0.0
.
- Make sure that the door stations and cameras have been updated to software release
V4.4.0.31
or higher. Otherwise, the improvements and bugfixes listed below will not work.
Enhancements and Improvements
New Floor Call Feature (Uses the Signal Input/Output Pins of the MxDisplay+)
Starting with firmware release 2.1.0.x
, the MxDisplay+ provides a storey call functionality. It is intended for scenarios in which both – a main door at a building and an apartment door on a floor inside – are present. The main door is equipped with a door station that is controlled by an MxDisplay+ as intercom, while the apartment door is connected directly to the MxDisplay+. The two wires of the apartment doorbell and the wires of any door contacts or door lock contacts are connected to the signal inputs, the electrical door opener is connected to the signal output of the MxDisplay+. The MxDisplay+ will indicate the doorbell that had been pressed, allowing you to open the corresponding door.
To configure this feature, open the new Settings > Installation > Door Configuration > Storey Call dialog. For additional details to the connections that are required for this feature, please read the document Quick Install MxDisplay+, which is available on the MOBOTIX website in the www.mobotix.com/other/Support/Manuals/Network-Technology-Home-Automation/MxDisplay section.
External Temperature Sensor
This firmware supports an external temperature sensor that has been connected to the separate input terminals T+/T- of the MxDisplay+. The following temperature sensors can be used:
- Ni1000
- Ni1000_TK5000
- NTC1.8kOhm
- NTC10kOhm
- NTC15kOhm_B3950
- NTC1kOhm
- NTC20kOhm_B4150
- NTC2kOhm_B3415
- NTC30kOhm_B4150
- NTC3kOhm_B3880
- NTC47kOhm_B3950
- NTC50kOhm_B4170
- NTC8kOhm_B3950
- Pt100
- Pt1000
To select the attached temperature sensor, open the Settings > Installation > Display Configuration > Temperature Sensor dialog.
Bugfixes
- Definition of access times for RFID cards
When defining or modifying access times for trained RFID cards, issues appeared if a Keypad had been involved. The access times defined in MxDisplay+ had not been applied properly at the Keypad or had not been displayed correctly at the MxDisplay+.
- Device ID and DHCP
When requesting an IP address from a DHCP server, the MxDisplay+ did not transfer the same device ID, which resulted in the fact that the DHCP server assigned different IP addresses.
- IP subnet mask
When defining a static IP address for the MxDisplay+, setting a specific subnet mask sometimes did not work properly. Instead of using a specific mask /26
or 255.255.255.192
, for example, you had you to use a more general mask /8
or 255.0.0.0
so you could still reach the MxDisplay+.
- Attached camera with many alarms
When working with cameras that transferred very many alarms to the MxDisplay+, the device sometimes rebooted spontaneously but had lost parts of the previous configuration settings.
Known Limitations
- Counter for doorbell events
The displayed number of incoming calls is also incremented, if a doorbell at the door station is pressed or if a number is entered that is not assigned to this MxDisplay+ as intercom partner device.
- Display of door status
When using a door station with Keypad, the door status will always show "Door is open", although the door contact and the door lock contact have been connected properly.
- HTTP/HTTPS access using Bonjour
Currently, the Bonjour service (used to make MOBOTIX devices known to other network devices) on an MxDisplay will advertise its HTTP port 80 and HTTPS port 443, regardless of the actual ports that have been assigned using the browser-based user interface of MxDisplay. Regardless of this, the unit uses the HTTP/HTTPS ports specified in the browser interface.
- Displaying/changing camera configuration settings
Currently, the MxDisplay may not always show the current camera configuration settings, if these had been changed from another device or from the browser-based user interface of the camera. In such a case, you can reload the connections to all cameras and door stations (and thus, the configuration settings) by simultaneously holding the Letter, Home and Key buttons at the bottom until you hear five beeps.
top
MxDisplay Software-Release V1.0.2.16
Creation Date: 2015-06-18
Publishing Date: 2015-06-26
Important Notes:
- For updating the software, enter the IP address in a browser (user
admin
, password meinsm
) and select Update system software. By factory default, the MxDisplay is running as DHCP client and has an additional local IP address in the 10.x.x.x address range (see sticker on the back of the device) with a network mask of 255.0.0.0
.
- Make sure that the door stations and cameras have been updated to software release
V4.3.2.68
or higher. Otherwise, the improvements and bugfixes listed below will not work.
Enhancements and Improvements
Redesigned "Access Control" Dialog, Tool Tips
The Settings > Access Control dialog has been completely redesigned. The menu structure, in particular, has been improved when adding new RFID cards. In addition, the dialog has been improved for adding PINs, users, parties and door stations that opens when tapping the "+" icon: When tapping and holding an icon, a text explains the icon's function. The same applies to all other dialogs that contain icons.
Note:
If a PIN has been set for an RFID card in the access control, the following applies when trying to gain access using the card: If a KeypadRFID controls the access, you also need to enter the assigned PIN, whereas a BellRFID will grant access using only the card.
New Functions for Softbuttons
Two new functions are available when defining "function icons":
- Announcement: Tap and hold an icon with this new function to make an announcement via the selected camera.
- Send message: This function allows sending a message via the MxMessageSystem of the selected camera. The camera can process the message itself or send it on to attached MxBus modules.
If function icons have been created, the tool bar beneath the live image shows an additional "checkerboard" icon. Tap on this icon to see and to use the defined function icons.
Note: To activate and define function icons, tap and hold the Home button in the MxDisplay main menu.
Enhanced Menus and Screens
- Screensaver: If at least one camera with an attached temperature sensor is connected to MxDisplay, the Standby mode (i.e., before switching of the display) automatically switches between time/date and temperature. You can modify this behavior in the Settings > MxDisplay Settings > Screensaver menu. In addition, the MxDisplay will not turn dark after a couple of minutes, but will follow the screensaver settings.
Note: Changing the Black Screen and Activate after 1min factory default settings of the screensaver will increase the wear on the display, and thus reduce the life expectancy of the MxDisplay.
- Date and Time: The settings for a time server used by MxDisplay are now modified in the Settings > Installation > System Configuration > System Time menu. Note that you can set several connected time servers in that menu. MxDisplay will show the time in red in the main menu if no or only one time server has been defined. If you are using a camera with connected MX-GPS-Box or another time server with acceptable precision, MxDisplay shows the time in white. If the current time of a door station is in the future as compared to the MxDisplay, this will be recognized in door station events. MxDisplay will show an exclamation mark behind the event time and creates a permanent error message.
Note:
If neither an MX-GPS-Box nor another time server with acceptable precision can be used, MxDisplay can show the date and time in white anyway. To do so, activate the No Time Warning option in Settings > Installation > Display Configuration > Date & Time.
- Bell behavior: The behavior of individual bells and the reaction can be modified quicker in the Settings > Bell Behavior menu. In addition, you can modify existing mailboxes and record mailbox announcements.
- Adding cameras and changing network settings: When adding cameras in the Settings > Installation > Camera List > "+" icon, you can now set port numbers and activate/deactivate SSL for the cameras. This means that it is possible to use cameras e.g., via DynDNS in MxDisplay that use a special port for this purpose. When manually entering IP addresses for a camera, name server, gateway or the like, the numeric keypad pops up automatically.
- Event search: In the Event Search menu, you can use the "magnifying glass" icon to filter by cameras and event types.
Bugfixes
- Showing users and parties in Access Control
When defining parties and users within parties, users were sometimes shown twice – once within and once outside of the parties.
- Custom weekly profiles in Access Control
After defining and subsequent editing of custom weekly profiles, these profiles were sometimes shown twice. After deleting one of the profiles, both profiles disappeared. Also, changing the access mode to permanent access ("green key" icon) sometimes failed after using custom weekly profiles.
- Access control with custom time ranges
Using custom time ranges for accessing with specific means (PIN, RFID card) could sometimes fail and did not produce the expected results.
- RFID cards sometimes "unknown"
RFID cards that had been trained in several systems (e.g., Keypad and BellRFID) were sometimes rejected by MxDisplay with a "card unknown" message.
- Backup and restore of access control settings
After backing up and restoring all settings of the Access Control dialog, the defined users and parties were missing.
- Ring tones not played fully
On some ring tones, such as "DingDong", the beginning of the sound did not play and as a result, the sound was too short.
- "Last Event" function icon
The "Last Event" function for function icons showed the event list and not the last event. The function has hence been renamed to "Event List".
- Cameras added with 169 IP address (Zeroconfig)
When adding cameras, cameras that did not get an IP address from a DHCP server were sometimes added with an IP address in the 169 range (Zeroconfig) instead of their additional factory default IP address in the 10.x.x.x range.
- Reconnection after MxEasy Privacy Mode
After activating the MxEasy Privacy Mode, a camera attached to MxDisplay cannot be shown any more due to the modified access data. This state continued even though the MxEasy Privacy Mode had been deactivated in the meantime. MxDisplay will now periodically try to reconnect to such a camera and automatically restores the access once the MxEasy Privacy Mode has been deactivated.
Known Limitations
- Red LED flashing
Sometimes, the left LED will continue to flash red after loosing the connection to a door station/camera even though the connection has been re-established in the meantime.
- HTTP/HTTPS access using Bonjour
Currently, the Bonjour service (used to make MOBOTIX devices know to other network devices) on an MxDisplay will advertise its HTTP port 80 and HTTPS port 443, regardless of the actual ports that have been assigned using the browser-based user interface of MxDisplay. Regardless of this, the unit uses the HTTP/HTTPS ports specified in the browser interface.
- Displaying/changing camera configuration settings
Currently, the MxDisplay may not always show the current camera configuration settings, if these had been changed from another device or from the browser-based user interface of the camera. In such a case, you can reload the connections to all cameras and door stations (and thus, the configuration settings) by simultaneously holding the Letter, Home and Key buttons at the bottom until you hear five beeps.
top
MxDisplay Software-Release V1.0.2.0
Creation Date: 2014-11-14
Publishing Date: 2014-11-17
This is the first officially published software release for the MOBOTIX MxDisplay.
MxDisplay Features
"A Smartphone On the Wall"
That's the first impression of the new wall-mounted display from MOBOTIX. It can be integrated flush with the wall, comes in a stylish design in black or white and users can operate it using gestures, just like a modern smartphone. With just a few swipes, the user can look at an overview of the cameras in the house, retrieve the latest video messages of the door intercoms or create a new access transponder for a visitor.
The MxDisplay is extremely easy to operate and serves as an intercom for the video door station. Regardless of what menu the user is in, tapping the key icon immediately shows the live image of the door station. Tapping and holding opens the door. If necessary, you can increase the security by assigning a PIN or RFID transponder.
Main Features
Besides the features mentioned above, the MxDisplay has many more features; the most important ones are listed in the following:
- Intercom with live image
- Activate electric door opener and switch lights
- HD audio technology for high-quality voice connections between MxDisplay and camera
- Start an instant recording directly in the live image
- Play back mailbox and event recordings of door stations and cameras
- Integrated event search and player features
- Extensive RFID and access control features:
- Train and manage RFID cards/transponders and access PINs
- Create users and lock MxDisplay features for specific users
- Scheduled access control for RFID cards and PIN codes
- Combined access control of RFID card plus PIN
- Simple installation, optional wireless network connection
- WiFi functionality with different modes:
- Client: MxDisplay is used as a WiFi client in an existing WiFi network
- Extend Network (AP): MxDisplay is used as a WiFi access point for other devices (smartphones, tablets) in the same WiFi network for all devices
- Separate Network (AP): MxDisplay is used as a WiFi access point in a separate WiFi network and also has a connection to the camera network (e.g., for different apartments without individual WiFi routers)
- Camera Gateway (Client): MxDisplay is used as a WiFi client in a WiFi network that is different from the camera network (e.g., for different apartments with individual WiFi routers)
- Building automation features programmable (lights, shutters, etc.)
- Configuration of important camera settings
- Management of MxDisplay and system configurations
- Language support (DE, EN, FR, PT (Brazil), ES, IT)
Notes on Setting up MxDisplay
- IP address for DHCP and software update
If the MxDisplay is connected to an existing DHCP server, you can see the current IP address by tapping on Home > Settings > About > Network Interfaces. You will need this IP address, if you want to update the software using the browser-based user interface of the device, for example. For updating the software, enter the IP address in a browser (user admin
, password meinsm
) and select Update system software (please also see the initial operation description in the MxDisplay Quick Install).
- Simultaneous Use of Ethernet and WiFi
When simultaneously using the Ethernet and the WiFi network interfaces, you need to make sure that the IP address ranges of both networks are not overlapping. This would be the case, if both networks would use IP addresses in the range 192.168.0.x
with a subnet mask of 255.255.255.0
. To configure the Ethernet interface, open Settings > Installation > Display Configuration > Network. The WiFi interface is configured in Settings > Installation > Display Configuration > WiFi.
- Setting up RFID cards
In order to use the RFID cards in a multi-door-station installation with the existing MxDisplay units, you need to initialize all door stations and MxDisplay units with the same RFID admin card.
Special Operating Instructions
- Push-to-Talk
If you tap and hold the green receiver icon (two-way communication with the camera) longer than 10 seconds, it will lock and MxDisplay will continue to send the sound from its microphone to the camera. Press the green receiver icon again to stop sending audio to the camera and to hear the sound from the camera microphone on the MxDisplay. Press the red receiver icon to disconnect the audio connection to the camera.
Known Limitations
- HTTP/HTTPS access using Bonjour
Currently, the Bonjour service (used to make MOBOTIX devices know to other network devices) on an MxDisplay will advertise its HTTP port 80 and HTTPS port 443, regardless of the actual ports that have been assigned using the browser-based user interface of MxDisplay. Regardless of this, the unit uses the HTTP/HTTPS ports specified in the browser interface.
- Display of dialogs after large "time lapses"
If the MxDisplay is connected to a time server for synchronization purposes and the time needs to make a large correction (e.g., because the connection to the time server had been disrupted for a longer period of time), the MxDisplay may show incomplete or overlapping dialogs.
- Displaying/changing camera configuration settings
Currently, the MxDisplay may not always show the current camera configuration settings, if these had been changed from another device or from the browser-based user interface of the camera. In such a case, you can reload the connections to all cameras and door stations (and thus, the configuration settings) by simultaneously holding the Letter, Home and Key buttons at the bottom until you hear five beeps.
Copyright © 1999 – 2017, MOBOTIX AG, Germany, sales@mobotix.com