Even though it is not possible to connect an ExtIO to multiple cameras, it is possible to work around this by using MxMessage. The cameras not directly connected to the ExtIO (via Ethernet or USB) will send an MxMessage to the camera connected with the ExtIO.
Note: This process is the same if you an Mx-Output-Box or Mx-RS232-IO-BOX connected to a camera.
Tip: Connecting the ExtIO via USB is recommended, as it proves to be more stable then via Ethernet
In this example we will be using the Output of the ExtIO to trigger an electronic door strike on a T26 Door Station. In which case you will first need to ensure that the Auto-Configuration has been completed first. This is paramount in order to have the “Device Out: ~Door” as an action in the Action Groups.
Configuring the Door Stations not connected to the ExtIO
- Admin Menu > Network Distribution of Messages
- Ensure that “Networking” is enabled
- Admin Menu > Message Profiles for Action Groups create the following profile:
MxMessageSystem Name: <Name of Message>
Message Range: Global
Note: The MxMessage name must be 100% consistent through out the whole process. The MxMessage name is case sensitive.
- In Setup Menu Menu > Event Overview > Signal Events create the following event:
Event Sensor Type: Signal Input
Signal Input Pin: Camera Bell Buton
Trigger Condition: Falling (high/NC) to Closed (low/NO)
- Setup Menu > Action Group Overview and create the following Action Group
Event Selection: Signal Input Event created in Step 3.
Action 1: MxMessage Profile created in Step 2.
Configuring Non-Door Station IoT MOBOTIX camera, which are not connected to the ExtIO
It is possible to trigger the Output on the ExtIO from a Non-Door Station IoT Mobotix camera in the same manner. The difference is that the Non-Door Station IoT MOBOTIX camera does not have a Camera Bell Button as an event to initiate the action.
In this example we will use the UC Event as the trigger. However you can use any event available to your model of camera, to trigger the Action Group.
- Admin Menu > Network Distribution of Messages
- Ensure that “Networking” is enabled
- Admin Menu > Message Profiles for Action Groups create the following profile:
MxMessageSystem Name: <Name of Message>
Message Range: Global
Note: The MxMessage name must be 100% consistent through out the whole process. The MxMessage name is case sensitive.
- In Setup Menu Menu > Event Overview > Signal Events create the following event:
Event Sensor Type: UC Soft Button
- Setup Menu > Action Group Overview and create the following Action Group
Event Selection: Signal Input Event created in Step 3.
Action 1: MxMessage Profile created in Step 2.
Configuring the Door Station connected to the ExtIO
We have outlined above how to configure the satellite Door Stations / Cameras which are not connected to the ExtIO, to send an MxMessage. Now we need to configure the Door Station connected to the ExtIO to be able to receive and act accordingly to the MxMessages.
- Admin Menu > Network Distribution of Messages
100%•75%•50%
- Ensure that “Networking” is enabled
- In Setup Menu Menu > Event Overview > Message Event create the following event:
Event Sensor Type: MxMessageSystem
Message Name: <MxMessage name created on the satellite Door Stations / Cameras>
Message Range: Global
Note: The MxMessage Name must 100% match the MxMessage being sent from the Door Station / Camera
- In Admin Menu > Assign Wires ensure that the ExtIO Output connected to the Door Strike is populated in the Door Release Actuator drop down menu
- Setup Menu > Action Group Overview and create the following Action Group
Event Selection: Message Event created in Step 2.
Action 1: Device Out: ~Door