Teltonika DualCam solution

From Wiki Knowledge Base | Teltonika GPS
Revision as of 10:44, 9 February 2022 by PavelSafonov (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Solution description

All kinds of unpredictable situations occur on the road – from accidents caused by technical issues or careless driving to various crimes and other incidents punishable by law. No matter what happens, one thing is for sure – having a detailed proof about the event will make things much simpler and easier. This is exactly what Teltonika Telematics has to offer – GPS tracking solution enhanced with Teltonika DualCam possibilities.

Here You will find how to prepare and test this solution.

What you need for the solution?

  • Teltonika FM device which is compatible with this use case. Recommended products are: FMC125, FMM125, FMU125, FMB125, FMU126.
  • Teltonika DualCam device which is compatible with this use case. This product is DualCam.
  • One or two SIM card(s) in order to receive data to Your server.
  • Teltonika Configurator to set up FM device correctly for the solution.
  • FOTA WEB to remotely send the configuration to the device.

Intallation

FMC125 2x6 socket pinout

Connecting wires:

  • Wires should be connected while the module is not plugged in.
  • Wires should be fastened to stable wires or other non-moving parts. Any heat emitting and/or moving objects should be kept away from the wires.
  • There should be no exposed wires. If factory isolation was removed while connecting wires, the isolation material should be applied.
  • If the wires are placed in the exterior or in places where they can be damaged or exposed to heat, humidity, dirt, etc., additional isolation should be applied and the wires should not be loose.
  • Wires cannot be connected to the board computers or control units.

Connecting power source:

  • Be sure that after the car computer goes to sleep mode, power is still available on the power wires. Depending on car, this may happen in 5 to 30 minutes period.
  • When module is connected, measure voltage again to make sure it did not decrease.
  • It is recommended to connect to the main power cable in the fuse box.
  • 3 A, 125 V external fuse shall be used.

Connecting ignition wire:

  • Be sure to check if it is a real ignition wire i. e. power does not disappear after starting the engine.
  • Check if this is not an ACC wire (when key is in the first position, most of the vehicle electronics are available).
  • Check if power is still available when you turn off any of vehicles devices.
  • Ignition is connected to the ignition relay output. As alternative, any other relay, which has power output when ignition is on, may be chosen.

Connecting ground wire:

  • Ground wire is connected to the vehicle frame or metal parts that are fixed to the frame.
  • If the wire is fixed with the bolt, the loop must be connected to the end of the wire.
  • For better contact scrub paint from the spot where loop is going to be connected.

Alert.png || NOTE: PAY ATTENTION! Connecting the power supply must be carried out in a very low impedance point of on-board vehicle network. These points in the car are the battery terminals. Therefore, we recommend connecting the power of FMC125, FMB125, FMM125, FMU125 and FMU126 (GND and POWER wires) directly to the battery terminals. Another valid option is to connect the wires to the main POWER cable inside the fuse box (if there is none, then to the power supply where the fuses of vehicle’s computer are), GND wire must be connected in a special point, designed to connect GND vehicle computer. Connecting the GND at an arbitrary point to the mass of the car is unacceptable, as static and dynamic potentials on the line GND will be unpredictable, which can lead to unstable FMC125 operation and even its failure.

To connect the DualCam to a supported device, you have to make sure to connect 4 PINs of the camera to the PINs of your device correctly.

Dual camera scheme 1.3 (1).jpg

PIN NUMBER PIN NAME DESCRIPTION
1 RS232-Tx DualCam output for data transmission through RS232
2 RS232-Rx DualCam input for data reception through RS232
3 VCC(9-36V) (+) Power supply for the DualCam
4 GND (-) Ground

Configuration

1. Prerequisites:

1.1. Read through First start guide

2. Configuration of DualCam solution:

Parameter ID - Parameter name

SIM1 GPRS Settings:

  • 2001 – APN for SIM1.
  • 2002 – APN username (if there are no APN username, empty field should be left) for SIM1.
  • 2003 – APN password (if there are no APN password, empty field should be left) for SIM1.


SIM2 GPRS Settings:

  • 2012 – APN for SIM2.
  • 2013 – APN username (if there are no APN username, empty field should be left) for SIM2.
  • 2014 – APN password (if there are no APN password, empty field should be left) for SIM2.




Server Settings:

  • 2004 – Domain.
  • 2005 – Port.
  • 2006 – Data sending protocol (0 – TCP, 1 – UDP).

After successful GPRS/SERVER settings configuration, device will synchronize time and update records to the configured server. Time intervals and default I/O elements can be changed by using Teltonika Configurator or SMS parameters. After familiarizing with devices first start guide, device's GPRS settings and operation mode for RS232 are set - configuration for DualCam can be done.


Crash detection configuration:

  • 11400 - Priority. In Hight Priority module makes additional record with high priority flag and sends event packet immediatley to the selected server by GPRS (0 - Disable, 1 - Low, 2 - High, 3 - Panic).
  • 11401 - Duration. Time period for acceleration detection (value range: 0 - 1000 ms).
  • 11402 - Threshold. Acceleration threshold (value range: 100 - 6000 mg).
  • 7037 - Send SMS to. ID of SMS recipient.
  • 8037 - SMS Text. SMS Event Text in default or composed format. TextMaxLenght = 160.
  • 11412 - Trace Filter. Crash trace sends raw (Disable) or filtered (Enable) accelerometer data (0 - Disable, 1 - Enable).
  • 11406 - Crash Trace. Enable Crash Event trace for additional data about crash (0 - Disable, 1 - Trace Changes, 2 - Trace Full).
  • 11415 - Crash Counter. Crash adds eventual record and tracegrouping by ID 317 (0 - Disable, 1 - Enable).
  • 11410 - Trace ODR. Crash event output data rate. Values in hertz (value range: 20 - 200 Hz).
  • 11407 - Accel duration. Crash event monitoring duration of linear accelerometr value before and after event. Values in seconds (value range: 2 - 15 s).
  • 11408 - GNSS duration. Crash event monitoring duration of GNSS data before and after event. Values in seconds (value range: 2 - 30 s).



External device (DualCam) configuration for RS232 interface:

  • 150 - External UART Mode (0 - Disable, 1 - RS232, 2 - RS485).
  • 151 - RS232 Mode. Parameter, which determines what mode to use for RS232 functionality (0 - Silent, 1- Log Mode, 2 - NMEA, 3 - LLS , 4 - LCD, 5 - RFID HID, 6 - RFID MF7, 7 - Garmin FMI, 8 - TCP/UDP Ascii, 9 - TCP/UDP Binary, 10 - TCP/UDP Ascii Buffered, 11 - TCP/UDP Binary Buffered, 12 - Mercury C4, 13 - UL202 Fuel Sensor, 14 - DualCam).
  • 66000 - Camera Picture Resolution. Set resolution to use when taking pictures (0 - 160 x 120, 1 - 320 x 240, 2 - 640 x 480, 3 - 1280 x 720, 4 - 1920 x 1080).
  • 66001 - Camera Picture Compression. Set compression to use when taking pictures (value range: 0 - 100).
  • 66002 - OSD Display. Enables/disables OSD displaying in corner (0 - Disable, 1 - Enable).
  • 66003 - Video Frame Rate. Set video frame rate to use when capturing videos. Value in FPS (20 - 20, 25 - 25, 30 - 30).






Server and mode.jpg

DualCam Scenario Settings configurations:

  • 66006 - Periodic Image Sending. Controls periodic image sending to server at configured interval (0 - Disabled, 1 - Front Camera, 2 - Rear Camera, 3 - Both Cameras).
  • 66007 - Sending interval.Sets intervals at which to send pictures to server to. Values in seconds (value range: 10 - 1800).
  • 66022 - Image Sending Trigger. Triggers for capturing and sending image to the server (2 - DIN1, 4 - DIN2, 8 - Crash, 16 - Towing, 32 - Idling, 64 - Geofence, 128 - Unplug, 256 - Green Driving).
  • 66023- Video Sending Trigger. Triggers for capturing and sending video clip to the server (2 - DIN1, 4 - DIN2, 8 - Crash).
  • 66009 - Video duration before trigger. Sets how many seconds of video to send before trigger. Value in seconds (value range: 1 - 10 s).
  • 66010 - Video duration after trigger.Sets how many seconds of video to send after trigger. Value in seconds (value range: 1 - 10 s).
  • 66020 - Camera Scenario Mode. Sets how DualCam scenario works: only when there is an ignition detected or all the time (0 -On Ignition, 1 - Always).
  • 66040 - Video Source for trigger DIN1. Select which camera to use for each trugger (0 - None, 1 - Front, 2 - Rear, Front and Rear).
  • 66041 - Video Source for trigger DIN2. Select which camera to use for each trugger (0 - None, 1 - Front, 2 - Rear, Front and Rear).
  • 66042 - Video Source for trigger Crash. Select which camera to use for each trugger (0 - None, 1 - Front, 2 - Rear, Front and Rear).




DualCam server settings and RS232 Settings:

  • 66004 - Domain. Server domain for sending picture / video data to.
  • 66005 - Port. Server port for sending picture / video data to.
  • 152 - Baudrate. RS232 Baudrate selection. Different external sensors and devices support different connectionbaudrates. It is necessary to select proper baudrate for good communication. Values in kbps (0 - Default, 1 - 1200, 2 - 2400, 3 - 9600, 4 - 14400, 5 - 19200, 6 - 38400, 7 - 57600, 8 - 115200, 9 - 4800)
  • 153 - Parity. Possibility to set desirable parity (0 - Default, 1 - None, 2 - Odd, 3 - Even)




Quick start: From default configuration to Teltonika DualCam solution in one SMS:

"  setparam 2001:APN;2002:APN_username;2003:APN_password;2012:APN;2013:APN_username;2014:APN_password;2004:Domain;2005:Port;2006:0;
11400:2;11412:1;11406:2;11415:1;150:1;151:18;66002:1;66006:3;66022:10;66023:10;66009:10;66010:10;66020:1;66004:Domain;66005:Port"

This SMS will set up your device to send data and photo/video to your previously provided server.

Note: Before SMS text, two space symbols should be inserted if no SMS username or password was set in SMS / Call settings.


Parsing information

1. Prerequisites:

1.1. Open TCP/UDP port

1.2. Go to Java parser first start guide

2.Parsing example:

Demonstration in platform

Packet information can be displayed visually. In the picture below, the event location is displayed on the map. The dot on the map represents a record. By clicking on it, it is possible to see what kind of information is gathered in the particular entry.

In order to visually see received information on the platforms:

WIALON: Open WIALON → Open messages → Push unit ( select your device) → Select the date interval → Select message (data messages) → Push execute button and you will see all information. (Note: Figure below is an example and doesn't represent the actual visualization of the packet in the parsing example).