Communication Protocol document for the complete OFCP instructions information. In some
cases, Wi-Fi connection may be broken due to bad Wi-Fi signal or interference. D310F would
report the connection fail status to external device. Then external device can resume the
connection by issuing re-connection command.
Dash Cam also integrates a few LED indicators to help users catch the system status easily. The
indicators include Wi-Fi ON/OFF/Connection, MIC ON/OFF, Recording ON/OFF.
4. Introduction to Development Tool and Demo
Environment for fast D310F Evaluation
As described previously, D310F starts loop video recording automatically and continuously after
power is on until power is cut o
ff
or Vehicle tracker instructs D310F to execute other missions. A
comprehensive command sets have been implemented and deployed on D310F. A demo and
evaluation tool - “FleetDemo.exe” is provided for system designer to quick examine functionalities
supported by D310F
4.1 OTUS FLEET COMMUNICATION PROTOCOL (OFCP)
OTUS Fleet Communication Protocol (OFCP) is designed to be used in the communication
between Vehicle Tracker and Dash Camera (Vehicle Video Recorder). In the role play of OFCP
target user scenarios, Vehicle Tracker is defined as Protocol Master, and Dash Camera (D310F) is
defined as Protocol Slave.
5
LED Indicators
Wi-Fi
Orange
ON / OFF / Blinking (Connecting to AP)
MIC
Green
ON / OFF / Blinking (Uploading to Cloud)
Recording
Blue
Blinking (Normal Recording) / ON (Event Recording) / OFF
RTMP/HTTP/FTP Server
Fleet Mgmt. Center
D310F Network
Connected Camera
Event Video/Live Video ( Wi-Fi -> 4G LTE)
RS232
3G
/4G
GS
M
Vehicle Tracker
Typical
User
Scenario
:
①
Fleet
Mgmt
.
Platform
Communicates
with
Vehicle
Tracker
through
3G
/
4G
channel
②
Vehicle
Tracker
sends
Event
Triggers
to
D310F
Camera
via
RS232,
and
D310F
can
detect
driving
behavior
events
as
well
③
D310F
uploads
video
upon
Event
Triggered
and
Remote
Requests
