4
Reading Mobile Caddy Unit (MCU) requires an ancillary
MDR-MCU-R-
01
to transfer SATA connector to USB 3.0 which allows directly
connect to a Windows™ operating computer.
USB-B (3.0) interface on the Mobile Caddy Unit (MCU) for displaying
video recordings on a Windows™ operating system using MDR-
Dashboard 6.0
Built-in G-Sensor and 1x EIA/TIA 232 (RS232) for optional Remote
Status & Interface Panel to provide buzzer functionality (RS232
–
RS485 transfer is needed).
Built-in G-Sensor, Audible Buzzer and 1x EIA/TIA 485 (RS485) for
optional Remote Status & Interface Panel
2 MDR Server Requirements and Installation
MDR Server 6.0 is required software that runs on the Windows Server. This software enables an MDR unit to connect to the Windows Server.
MDR Server controls the assignment of ports and its functionalities.
Note:
This software runs on a Y
early Licence
and
Authentication
. When the
Yearly Licence
is nearing the expiration date (1
st
Dec every year), please visit Brigade
’s website (
to download the new license file. This file needs to be
copied onto the Windows Server running MDR Server 6.0. Copy this file to the following path
C:\Program Files (x86)\MDR
Server\TransmitServer
and overwrite the existing version. For
Authentication
, please contact Brigade support to obtain
available auth file. Without an auth file, the server provides 1 month trial with 20 vehicle connectivity in maximum.
2.1 MDR Server Requirements
To use mobile network and Wi-Fi connectivity features, networking expertise are required for implementation. The mobile network server is
accessed by the MDR externally through a public IP (Internet Protocol) address. The Wi-Fi server is accessed by the MDR using a Wi-Fi
network. This setup requires all devices (Server, Client and MDR) to be connected to a shared network. Client refers to MDR-Dashboard 6.0 or
BRIGADE MDR 6.0 mobile apps. It is better for customers to use both network connectivity options to achieve different goals, live camera
capabilities of mobile networks and the low data cost of downloading video data over Wi-Fi.
Warning: If you have two separate MDR Server 6.0 software installations, video and metadata stored on each server is NOT linked.
Table 4: The minimum requirements below for MDR Server 6.0 with 1-10 MDR units
COMPONENT
MINIMUM REQUIREMENTS
CPU (Central Processing Unit)
Quad Core
– 2.2 GHz (Intel Xeon) or greater
RAM (Random Access Memory)
8GB or greater
Requested HDD space for software installation
10 GB required, 40 GB or more recommended (depending on the
number of MDRs connected at one instant and the features used). Each
MDR requires an additional 250MB of storage
Video
Super VGA or higher video card and monitor
Operating System
Windows Server 2012 R2 Standard or greater
Framework
Microsoft .Net Framework v3.5 SP1 version must be installed on both
server and client**
Wireless Adaptor
Wireless Access Point 802.11 b/g/n
**Client refers MDR-Dashboard 6.0 software
Table 5: The Recommended requirements below for MDR Server 6.0 with >10 MDR units <100
COMPONENT
RECOMMENDED REQUIREMENTS
CPU (Central Processing Unit)
8 Core/16 Threads or greater
RAM (Random Access Memory)
12GB
Requested HDD space for software installation
10 GB required, 150 GB or more recommended (depending on the
number of MDRs connected at one instant and the feature used)
Video
Super VGA or higher video card and monitor
Operating System
Windows Server 2012 R2 Standard 32\64bit
Framework
Microsoft .Net Framework v3.5 SP1 version must be installed on both
server and client**
Wireless Adaptor
Wireless Access Point 802.11 b/g/n
**Client refers MDR-Dashboard 6.0 software
Warning: The limitations to view several MDR video data feeds at one instant would be dependent on network speed, mobile network
coverage, Windows Server
’s HDD (Hard Drive Disk) and RAM (Random Access Memory) capacity.