Table of Contents  MOBOTIX Online Help

Message Configuration for MxBus Modules

Open the Message Configuration for MXBUS Modules dialog to configure the messages sent by connected MXBUS modules. Upon detecting specific events, an MXBUS module can send messages using the MxMessageSystem; in turn, the module can also execute a specific action upon receiving a corresponding message.

Open the Manage MxBus Modules dialog and make sure that the attached MxBus modules have been activated and that the firmware is up-to-date.

Notes

Managing Messages

First, load the configuration from the attached modules by clicking on the Load configuration of connected devices button.

Set the MxMessageSystem names in the Edit Messages section.

A valid MxMessageSystem name must follow these rules:

Note that all entries are case-sensitive. Use the New message and Remove buttons to create new messages and to delete existing ones, respectively. Note that you can only remove a message, if it is not used in any device configuration. When leaving an input field, all messages are stored temporarily on this page and are used to fill the dropdown fields in the configuration forms of all devices. Note that the messages are not yet written to any device configurations.

You can set a message range for every message. This range specifies where to distribute the message. The scope of the ranges is defined as follows:

A message can contain parameters and can thus be used to transmit values. The "Parameter" operating mode will be selected automatically depending on the specified configuration. Every message will get a specific signature according to the parameter types that are transmitted. The message dropdown fields are automatically filled and updated using only messages of the same type (i.e., the same signature).

Configuring the MxMessageSystem of the Devices

After loading the configuration, the dialog lists all discovered MxBus modules in separate sections below the message section. Depending on the features of the module, the corresponding form section contains subsections for configuring the function components that are available in that module. These can be, for example:

Inputs

The configuration sections for inputs are present if the module has inputs. Add creates a new line for configuring the current input. To delete a configuration line, click on the corresponding Remove button. Use the first dropdown edge type to set either the desired edge trigger (falling, raising, both), a level period or a parameter. The other selection fields are filled according to the first selection:

  • When using an edge trigger, the second dropdown field contains the messages that will be triggered.

  • When using Level period, you need to select the type of level to test for (high, low) and the duration that will trigger a message. In addition, you can set a dead time that can be used to set a pause before sending the next message.

  • When using a parameter, the second dropdown field contains messages that correspond to the signature, and which can be used to transmit the input state.

Outputs

The configuration sections for outputs are present if the module has outputs. Add creates a new line for configuring the current output. To delete a configuration line, click on the corresponding Remove button. The first dropdown field shows the generated message names that will be executed when receiving the message. The second dropdown field shows the action to be executed; depending on the selection, more fields will be displayed.

  • Off: When receiving the message, switches the output off (opens the output).

    • Lock prevents changes in the output state by any timers.

  • On: When receiving the message, switches the output on (closes the output).

    • Lock prevents changes in the output state by any timers.

  • Toggle: When receiving the message, toggles the output.

    • Lock prevents changes in the output state by any timers.

  • Timer: Allows settings a switching time in seconds. The output will be switched to the specified state On or Off for this duration.

    • Lock prevents changes in the output state while the timer is running.

  • Parameter: Changes the initial state of the output depending on the parameter contained in the received message.

RFID Modules

The KeypadRFID and BellRFID modules can trigger messages when specific RFID cards are presented. To use this feature, you need to add the unique identifier (UID) of the card on the text field. The UID is printed on the back of the card in the center and it can have up to 16 characters in hexadecimal notation (0−9, A−F):

Example 1. UID of an RFID Card

49131 047C18C2022C80 48315

Audio feedback

For modules with the ability for audio feedback, you can add/remove messages and the corresponding feedback types (error, success, alarm).

Visual feedback

For modules with the ability for visual feedback, you can add/remove messages and the corresponding feedback types (error, success, alarm).

Keys

For modules such as the BellRFID, you can configure messages for the available edge triggers in the sections of the corresponding bell button. When using the Parameter setting, the message will transmit the state of the bell buttons as a parameter. Accordingly, you can only select messages that correspond to the signature (sea also under Managing Messages).

KeypadRFID

The KeypadRFID module has its own configuration section. Its purpose is to map number codes to different messages. Every number code can have up to 16 digits. Note that you can also send function codes with the messages. A function code is a sequence of a digits and one of the following special key designators:

  • K: Key

  • M: Mail

  • B: Bell

  • E: ESC

  • O: OK

Example 2. Message with Function Code

If a visitor pressed the keys 1+2+3+4+Key, the message contains the string 1234K.

If a key is pressed longer, the string contains an additional l.

Example 3. Message with Function Code and Long Key Pressure

If a visitor pressed the keys 1+2+3+Key and held the Key button longer, the message contains the string 123Kl.

Sensors of the MX-GPS-Box

The MX-GPS-Box has a temperature sensor, an illumination sensor and a GPS sensor (date and time, position). Since it receives precise time and date information from the GPS satellites, you can use the MX-GPS-Box as camera time server. Please note that the MX-GPS-Box needs to run in classic mode for this purpose. There are two operating modes for the temperature and illumination sensors: Status and Threshold.

In Status mode, the measured values of the sensors can be attached as parameters to the message that will be sent. The message can be sent either using a timer after the specified time in seconds has passed or when receiving the selected message. The default time span for the timer is five minutes (300 seconds); this will prevent the message from being sent too often.

In Threshold mode, you can specify how the threshold or a value range are to be interpreted. To set a threshold, you can use either the Above or the Below comparison type. Note that − in this case − the lower and the upper threshold need to be identical. To set a value range, you can use either the Inner or the Outer comparison type. Enter sensible values for the upper and the lower thresholds. You can send the values of the GPS sensor together with a message. The message can be sent either using a timer after the specified time in seconds has passed or when receiving the selected message. The default time span for the timer is five minutes (300 seconds); this will prevent the message from being sent too often.

Sensors of the MxMultiSense

The MxMultiSense has sensors for measuring temperature, illumination and sound volume as well as an additional PIR (passive infrared) sensor. There are two operating modes for the temperature and illumination sensors: Status and Threshold.

In Status mode, the measured values of the sensors can be attached as parameters to the message that will be sent. The message can be sent either using a timer after the specified time in seconds has passed or when receiving the selected message. The default time span for the timer is five minutes (300 seconds); this will prevent the message from being sent too often.

In Threshold mode, you can specify how the threshold or a value range are to be interpreted. To set a threshold, you can use either the Above or the Below comparison type. Note that − in this case − the lower and the upper threshold need to be identical. To set a value range, you can use either the Inner or the Outer comparison type. Enter sensible values for the upper and the lower thresholds. The PIR and sound volume sensors can trigger messages of the specified trigger values (in percent) are exceeded.

Radar Sensor of the MX-Proximity-Box

The MX-Proximity-Box can trigger messages when detecting movements. The Recurrence time specifies the time to pause before a new message can be sent. Note that you can set the sensor range to either Near or Far. In addition, you can use a movement profile, which combines preset sensor values for amplitude, approach speed and escape speed. These values can be customized when using the Custom profile mode.

Note

Since the speed of approaching or leaving objects can only be measured properly with speeds of up to 15 kph/9.3 mph, the Distance slider will be deactivated for higher speeds.

Storing the Configuration

Once you have finished configuring the modules, you can save the current module's configuration by clicking on the Write configuration button at the bottom of the module section. In order to save the configuration of all modules at once, click on Transfer entire configuration at the bottom of the dialog.

Loading the Configuration

In order to load the entire configuration, click on the Load configuration of connected devices button at the bottom of the dialog. The form shows the corresponding modules and the configuration sections. Note that you can also load individual module configurations. This will only update the corresponding device section of the dialog.

Generating a Default Configuration

Click on the Create default configurations for all devices button at the bottom of the dialog to create a configuration with preset values. This will create configuration sections for all attached modules with appropriate default values and the corresponding messages. Note that you can do this manually for individual modules.

Factory Defaults

You can reset every module to its factory default settings. This will discard all configuration changes for the device made in this dialog. You can either discard the changes of all modules at the same time (click on Factory Defaults at the bottom of the page) or for a single module (Factory Reset at the bottom of a device section).


Storing the Configuration

Click on the Set button to activate your settings and to save them until the next reboot of the camera.

Click on the Factory button to load the factory defaults for this dialog (this button may not be present in all dialogs).

Click on the Restore button to undo your most recent changes that have not been stored in the camera permanently.

Click on the Close button to close the dialog. While closing the dialog, the system checks the entire configuration for changes. If changes are detected, you will be asked if you would like to store the entire configuration permanently.


© 2001-2018 MOBOTIX, · http://www.mobotix.com/