MxManagementCenter Remote Control: Export on Event

Introduction

With MxMC v2.0 there has been improvements to MxMC Remote Control, in regards to Export. As a result it is now simpler to automate export, as it can be completed in one IP Notify.

Improved Export Commands introduced in MxMC v2.0

exports?export[&camera=<name>][&ip=<ip>]
       &profile=<profile>
       &time=2018-10-01+12:00:00
       [&before=10000&after=30000]
       [&path=file://pathtoexportfolder]
       [&noProgress]
       [&viaCamera]
       [&reImport]
       [&delay=<n>]

starts exporting a <time> range from a camera with predefined profile <profile> range <before> and <after> time given in msec
                           
<noProgress> exports in quite mode
                           
<viaCamera> forces to export recordings via the camera rather than via configured fileserver
                          
<reImport> automatically imports clip after export
                           
<delay> delays export <n> seconds as recordings may not be immediately available for the latest events

Please Note

Exporting via MxMC can very processor intensive for the PC running MxMC. Therefore the for recommendations are designed to ensure the system continues to run smoothly.

  1. Only have 1 or 2 cameras export at the one time. If you require more then 1 or 2 cameras to export on event, you will need to stagger the export by using the [&delay=<n>] in the string.

  2. Do not use this feature to frequently export or export every event that occurs. The intention is to automate export only critical data, not provide another archive. As a result it is not recommended use this feature in conjunction with motion detection (VM & AS).

Example 1: Export Triggered by UC Event

  1. Setup MxMC Remote Control
  2. Create an Export Profile (frame rate and resolution)
  • (This only needs to be done only once, during setup!!!)

http://<PC-IP>:<Remote Control Port>/exports?create&profile=<name_of_profile>&format=MXG&framerate=25&resolution=1024x768&audio[=on/off]&ptz[=on/off]&separate[=on/off]&max=1024

  1. Create IP Notify for the Export
Parameter Value
IP Notify Profile Name Export
Predefined Configuration Custom Configuration
Destination Address <PC_IP>:<MxMC_Remote_Control_Port>
Send Order Parallel send to all
Transfer Protocol HTTP/1.0 Request
CGI-Path /exports
HTTP Authentication <MxMC_remote_control_username>:<MxMC_remote_control_password>
Notification Data Plain text
Message export&ip=<Camera_IP>&profile=<Profile_Name_created_in_Step_2>&time=(TMS.DATE)+(TMS.TIME)&before=1200000&path=<file://path_to_export_to_folder>
  • Time = <is in msecs> , therefore 20 mins = 1200000
  • To get the correct date format you need to use $(TMS.DATE)+$(TMS.TIME)
  1. Setup Menu > Action Group Overview
  • Create a new Action Group

  • Event Selection = Signal: UC

  • Action = <IP Notify created in Step 3>

Example 2: Export Triggered by Hyperlink in MxMC

  1. Setup MxMC Remote Control

  2. Create an Export Profile (frame rate and resolution)

  • (This only needs to be done only once, during setup!!!)

http://<PC-IP>:<Remote Control Port>/exports?create&profile=<name_of_profile>&format=MXG&framerate=25&resolution=1024x768&audio[=on/off]&ptz[=on/off]&separate[=on/off]&max=1024

  1. Create IP Notify for the Export
Parameter Value
IP Notify Profile Name Export
Predefined Configuration Custom Configuration
Destination Address <PC_IP>:<MxMC_Remote_Control_Port>
Send Order Parallel send to all
Transfer Protocol HTTP/1.0 Request
CGI-Path /exports
HTTP Authentication <MxMC_remote_control_username>:<MxMC_remote_control_password>
Notification Data Plain text
Message export&ip=<Camera_IP>&profile=<Profile_Name_created_in_Step_2>&time=(TMS.DATE)+(TMS.TIME)&before=1200000&path=<file://path_to_export_to_folder>
  • Time = <is in msecs>, therefore 20 mins = 1200000

  • To get the correct date format you need to use $(TMS.DATE)+$(TMS.TIME)

  1. Enable MxMessaging to send Message across the network (Admin Menu > Network Distribution of Messages)
  • Networking needs to be enabled

Pic_1_Networking_Enabled

  1. Setup Menu > Event Overview > Message Events
  • Create a new profile

  • Event Sensor Type = MxMessageSystem

  • Message Name= <Name of Message>

  • Please note that MxMessage name needs to be identical through the process and it is case sensitive.
  1. Setup Menu > Action Group Overview
  • Create a new Action Group

  • Event Selection = <Message Event created in Step 5)

  • Action = <IP Notify created in Step 3>

  1. Create Softbutton / Hyperlink in MxMC
  • Name: Export

  • http://<Camera-IP>/control/rcontrol?action=message&name=<Name of Message>

  • Remember the message name needs to match exactly the one used in Step 5

Pic_4_Hyperlink

Example 3: Export triggered by Time Task

  1. Setup MxMC Remote Control
  2. Create an Export Profile (frame rate and resolution)
  • (This only needs to be done only once, during setup!!!)

http://<PC-IP>:<Remote Control Port>/exports?create&profile=<name_of_profile>&format=MXG&framerate=25&resolution=1024x768&audio[=on/off]&ptz[=on/off]&separate[=on/off]&max=1024

  1. Create IP Notify for the Export
Parameter Value
IP Notify Profile Name Export
Predefined Configuration Custom Configuration
Destination Address <PC_IP>:<MxMC_Remote_Control_Port>
Send Order Parallel send to all
Transfer Protocol HTTP/1.0 Request
CGI-Path /exports
HTTP Authentication <MxMC_remote_control_username>:<MxMC_remote_control_password>
Notification Data Plain text
Message export&ip=<Camera_IP>&profile=<Profile_Name_created_in_Step_2>&time=(TMS.DATE)+(TMS.TIME)&before=1200000&path=<file://path_to_export_to_folder>
  • Time = <is in msecs> , therefore 20 mins = 1200000
  • To get the correct date format you need to use $(TMS.DATE)+$(TMS.TIME)
  1. Admin Menu > Time Tasks
  • Add the IP Notify to the Time Task

  • Set the Parameters for the Time Task

http://172.22.0.93/help/help?timetasks