__TOC__

== Main (front) camera unit preparation ==
The main unit comes prepared for bus/large truck setup (cable routing) or vehicles with mostly vertical windshields''.'' To set up the unit for an average truck or passenger vehicle, dismantle partially as shown below:
{| class="wikitable"
|+
! colspan="6" |Unit preparation
|-
|[[File:Camera1.jpg|center|frameless|181x181px]]
|1. Remove cover
|[[File:Camera1.jpg|center|frameless|186x186px]]
|2. Remove (2x) screws,
remove plastic cover
|[[File:Camera3.png|center|frameless|216x216px]]
|3. Remove (2x) screws,
pry plastic mounting

frame off Unit from corners
|-
|[[File:Camera4.png|center|frameless|199x199px]]
|4. Reroute the main
cable (and rear camera

cable, if adding) around unit

to front (glass side)
|[[File:Camera5.png|center|frameless|221x221px]]
|5. Press tightly into
channels when routing cables.

Remove front camera dust sticker
|[[File:Camera6.png|center|frameless|238x238px]]
|6. Replace 1 cover only
removed from step 3.

Replace 2 screws.

Leave the remaining

covers off until the last step
|}

== Vehicle installation ==

1. Clean the spots on the windshield with the ''alcohol wipe'' where you plan to mount the hardware. Remove the red 3M tape and mount the main unit underneath the rear-view mirror as centered (left/right) and straight as possible (if it ''must be off center'' by a few inches, that’s okay – measurements will be taken later). Be certain not to obstruct the drivers view.

[[File:Vehinst1.jpg|frameless|191x191px|d ]]

2. Run the main-unit cable across the headliner and down to the driver side under-dash. This may require removing the A-pillar temporarily. Follow factory harnesses, always run behind any airbags.

3. Attach the mount (from the plastic bag) and stick the LCD indicator on the windshield in the driver’s line-of-sight, usually close to the A-pillar so it can be easily seen and controlled if required. Run this cable down to the driver’s under-dash as well.

[[File:Vehinst2.jpg|frameless]]

4. Once both cables are run to the under-dash, connect them to the provided PCI unit at the proper ports.

[[File:Vehinst3.png|frameless|248x248px]][[File:Vehinst4.png|frameless|310x310px]]

5. Connect the Teltonika FMx125,FMX225 tracker to the main unit using RS232 cable. Please refer connection scheme below.

'''Please note that camera must be connected to ignition source, in other way camera will drain battery'''

[[File:ADAS wiring scheme 2 v2.jpg|center|frameless|1160x1160px]]

'''FMxy25 wiring with DOUT'''
Please note, that alternative wiring with DOUT is possible, in order to receive additional data from ADAS while the ignition is off, but the key is turned to the ACC position. That way it would be possible to control the power supply by turning on/off the camera. To find information on how to configure DOUT, please visit [[FMB setdigout|FMB DOUT]].

[[File:ADAS_w_DOUT.jpg]]

{| class="wikitable"
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| PIN NUMBER
! style="width:15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| PIN NAME
! style="width:25%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| DESCRIPTION
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 4
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''RS232-Tx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| ADAS output for data transmission through RS232
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 3
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''RS232-Rx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| ADAS input for data reception through RS232
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 1
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''VCC (9-36V) (+)'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| Power supply for the ADAS
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 7
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| '''GND''' (-)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| Ground
|-
|}

'''For FMX640 + ADAS connection'''

'''Please note that camera must be connected to an ignition source, in other way the camera will drain battery'''

'''Also, some RJ45 cables have two modifications, some have RS232 output on 3/4 pins some on 5/6 pins'''

For FMX640 devices, RJ45 cable is required with one end cut and loose. Connect the RJ45 cable to the FMX640 device's port 1 or port 2, both slots have RS232 support. Once connected, the other end of the cable should have pin 5-Rx, and 6-Tx shaved and connected to ADAS camera Rx and Tx cable. For the rest of the connection please refer to the picture below.[[File:Adas112233.jpeg]]

'''ADAS connection with relay'''
If it is necessary to receive additional data from the ADAS when the ignition is off but the key is inserted and turned to the ACC position, you can do it by connecting the camera to a power source using a relay in order to control the power supply by turning on/off the camera. To find information on how to configure DOUT, please visit [[FMB setdigout|FMB DOUT]].

[[File:ADAS_w_DOUT6.jpg]]

'''Two cameras FMC650 Installation with Relay'''
. If you need to receive additional data from the Two cameras or one of them when the ignition is off, you can also connect the camera to a power source using the relay, to control the power supply by turning on/off the camera. To find information on how to configure DOUT, please visit [[FMB setdigout|FMB DOUT]].

[[File:2 cameras dout.JPG]]

'''Two cameras FMC650 Installation with Ignition Source.''' To connect the two cameras to the FMC650 device, you have to make sure to connect 4 PIN's of the camera to the PIN's of your device correctly.

NOTE: Two cameras must be connected to the ignition source or another source, where then you turn off ignition camera will turn off in another case camera will drain the battery if you connect directly.

[[File:688548 DualCam and DSM with FMC650.jpg]]

{| class="wikitable"
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| PIN NUMBER
! style="width:15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| PIN NAME
! style="width:25%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| DESCRIPTION
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 6
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''RS232-Tx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| ADAS output for data transmission through RS232
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 5
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''RS232-Rx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| ADAS input for data reception through RS232
|-
|}

6. Connect the provided Power/Ground harness connection to a chassis ground (black wire) and Ignition source (red wire). The circuit must provide ~3 Amp @12v. Connect the plug to the PCI unit at the ‘Power’ port.

[[File:Vehinst8.png|frameless|357x357px]]

===Installation: for CAN-equipped vehicles===
Many vehicles are available in the database for using the CAN bus for vehicle signals (turn signals, brake and speed sense). This makes for a much faster installation. See below for checking the availability of a downloadable CAN file for your vehicle. NOTE: not all vehicles are available on the database currently, even if the vehicle has CAN. The list is constantly updated, so if the vehicle isn’t there now, it may be later. The installation may still be completed using analogue connections instead of CAN – see next section.

Check to see if there is a CAN file available by opening a Chrome browser and going to http://info.mdas.co.kr/customer/login

USER: [[telematics.adas@teltonika.lt]]

PASS: mDaSdataBase

1. Choose the vehicle ''make'' and ''model'' into the selector at the left.

2. Click the page icon (at right) and the database information will show CAN wire location information (if available) and download the ''‘CAN File Download’'' file at the bottom. '''''NOTE''': this filename will always be ‘mdasinfo.dat’ and cannot be renamed – so if you’re installing another ADAS and using this computer to set up, make a separate file folder (every time) with the vehicle year and model, and put this file inside of it.''
[[File:Vehinst9.png|center|frameless|996x996px]]

3. If there is a CAN file available, connect the provided CAN harness (contactless reader) to the (transmission) CAN bus wires – either where stated or at the OBD2 port, typically pins 14 & 6, if the vehicle is available on the database only.
[[File:Vehinst10.png|center|frameless|454x454px]]

'''''NOTE''': this connection uses inductance. There is no need to strip the CAN wires – just open the black box, lay the CAN High and Low in the channels, then close the box.''

4. Connect the 4-pin plug from the CAN harness to the ‘CAN’ port on the PCI unit.

If the vehicle is not listed in the database, you must use the provided Analog harness, see next section. NOTE: vehicles that are 1 year (or so) off, may still work for CAN access!

===Installation: For Analog signals (no CAN)===
[[File:Vehinst11.png|right|frameless|263x263px]]
If the vehicle has no CAN bus or there is no CAN file available, you must tap the turn signal (left and right), brake and speed signal manually (various locations).

1. With a digital multimeter or test light, locate the brake signal wire that activates when the brake is pressed (the vehicle may need to be ON). Connect and insulate the '''black/white wire''' to this vehicle’s wire. This may be a (+) or (-) signal.

2. With a digital multimeter or test light, locate the left turn signal wire that activates with the left turn signal. Connect and insulate the '''blue/white wire''' to this vehicle’s wire. This may be a (+) or (-) signal.

3. With a digital multimeter or test light, locate the right turn signal wire that activates with the right turn signal. Connect and insulate the '''blue wire''' to this vehicle’s wire. This may be a (+) or (-) signal.

4. Locate the VSS wire. Connect and insulate the '''brown/white wire''' to this vehicle’s wire.

NO other wires are required for typical installation – ground the remaining wires.

==ADAS Calibration==
ADAS Calibration requires:

*a laptop with an internet connection and a browser

*micro-USB cable

*tape measure

*parking the car with a clear, open stretch of about a 45 meters unobstructed view (try to park close to your facility to keep the internet connection accessible – at least during the calibration driver installation)
*a partner to drive the vehicle while speed correction is performed

Before beginning, insert the provided micro-SD card into the main unit in the location shown below until it clicks and turn the Ignition ON. Wait for the prompt, then press and release the center button one time. After the successful prompt and the unit reboots, continue to step 1.
[[File:Vehinst12.png|center|frameless|335x335px]]

1. Park the vehicle in a spot with a clear stretch of unobstructed line-of-sight (about 45 meters). Leave the vehicle running
2. Connect the USB cable to the Mirco-USB port on the side of the main unit (windshield) and the other end to the laptop. If on a windows 10 machine, it should automatically install the required driver. If not or on an older machine, go to movon.co.kr, go to the ‘ADAS’ tab at the top then to ‘Downloads’ under Support. Download the appropriate zip file (contains driver) and extract it fully for your version of Windows OS (if using the 7/8 driver, install the .exe file). If WIN10, once downloaded, disconnect/reconnect the USB and it should automatically install, or find the unit in Device Manager and right-click, Update Driver and browse for driver locally.[[File:Vehinst13.png|center|frameless|335x335px]]
3. Open Chrome browser again and type in ''’10.0.0.1’'' into the URL bar''.'' If the driver was installed properly, the calibration screen will appear. Input credentials and press ''LOGIN'' USER: ''admin'' PASS: ''1234'' 
4. '''Select Vehicle Signal Type:''' there are several wiring options for installation: CAN-BUS / Analog (GPIO) / GPS (Speed). Select the proper calibration option based off which was installed: CAN (if CAN file is available), Analog (if analogue signals were tapped)

'''''Vehicle Data File''''' (CAN-BUS)For CAN-BUS connection, choose the ‘Vehicle info file’ tab and select ‘Choose File’ to upload the previously downloaded ‘mdasinfo.dat’ file (see ‘CAN-Equipped vehicles’ section).
[[File:Vehinst14.jpg|center|frameless|363x363px]]

===Camera location and Vehicle Measurement===
Camera location and vehicle measurement can affect ADAS performance. It`s very important put accurate data for the best performance.
[[File:Vehinst15.png|center|frameless|404x404px|alt=]]
<table class="nd-othertables" style="width: 68%;">
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Camera Option</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Camera Height</td>
<td style="width: 8%; text-align:left">Distance from ground to the center of camera lens.</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera Center</td>
<td style="width: 8%; text-align:left">Distance from the center of windshield to camera lens
“-“: Left Side / “+”:Right Side

(If ADAS is attached 5cm to the right from the center, input 5.

If ADAS is attached 5cm to the left from the center, input -5.)
</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera to Wheel</td>
<td style="width: 8%; text-align:left">Distance from the camera to the center of the wheel.
'''For trucks or buses''', some vehicles’ wheels are located behind.

In this case, please input 20cm.
</td>
</tr><tr><td>Vehicle Width</td><td>Distance between the wheels.
Measure the distance from the left outside border to the right outside border of the wheels.
</td></tr><tr><td>Camera to bumper</td><td>Distance from the camera lens to the end of the bumper.
For trucks or buses, it is recommended to input 300 if a sensitive FCW warning is needed.
</td></tr></table>

Camera angle – adjust the camera angle to locate the horizontal between the red guidelines.
[[File:Vehinst16.png|center|frameless|316x316px]]
In case of indoor installation or somewhere you cannot see the horizon properly, use the same data to "'''Camera Height'''”. Mark the same height on the wall apart about 3 ~ 5 meters from the vehicle.
[[File:Vehinst17.png|center|frameless|332x332px]]

Fine Camera Angle - For better accuracy of ADAS, locate the yellow dotted line in the horizon as close as possible.
[[File:Vehinst18.png|center|frameless|344x344px]]

Hood Line - Locate the red line at the end of the vehicle’s hood line to remove the useless area.
[[File:Vehinst19.png|center|frameless|360x360px]]
Please follow the link for video instructions: https://www.youtube.com/watch?v=93wrc6j9aqA

===ADAS configuration===
{| class="wikitable"
| colspan="2" |'''You can adjust the LDW Sensitivity for your convenience'''
|-
|
* Enable LDW function. (On / Off)

* Set the Activation Speed (15, 30, 45, 60, 75km/h).
* Set the sensitivity of LDW warning on a scale of 1 to 5.
* As the level gets higher, it gets more sensitive.
* Enable Repeat LDW (On / Off)
* If it’s on, ADAS keeps warning until the driver secures the lane.
* Warning sound: Select preferred warning sound for LDW.
|[[File:Mdconfi1.png|center|frameless]]

|-
| colspan="2" |'''You can adjust the FCW Sensitivity for your convenience:'''
|-
|
* Enable FCW function. (On / Off)
* Set the sensitivity of FCW warning on a scale of 1 to 5.
(As the level gets higher, it gets more sensitive)
* Enable Repeat FCW (On / Off).
(If it’s on, ADAS keeps warning until the driver secures safe distance)
* Enable Sync with Brake (On / Off).
(If it’s on, ADAS won’t give FCW warning if the brake pedal was used)
* Warning sound: Select preferred warning sound for FCW
|[[File:Mdconf2.png|center|frameless|301x301px]]
|-
| colspan="2" |'''Safety distance alert setup:'''
|-
|
* Enable SDA function. (On / Off)
* Set the sensitivity of SDA on a scale of 1 to 5.
* As the level gets higher, it gets more sensitive.
* Repeat SDA and SDA re-alert can be changed. (On / Off)

- Repeat SDA: If it’s on, ADAS keeps warning until the driver secures safe distance.

''- Re-alert SDA: If it’s on, ADAS gives warnings every time''

''the same front vehicle gets closer than safe distance.''
|[[File:Mdconfi3.png|center|frameless]]
|-
| colspan="2" |'''Pedestrian collision warning setup:'''
|-
|
* Enable PCW function. (On / Off)

* Warning sound: Select preferred warning sound for PCW.
|[[File:Mdconfi4.png|center|frameless]]
|-
| colspan="2" |'''Advanced ADAS setup:'''
|-
|
* Enable Forward Proximity Warning function. (On / Off)
* Set the warning range on a scale of 1 to 3.
(As the level gets higher, it gets more sensitive)
* Enable Front vehicle start alarm. (On / Off)
* Enable Speed Limit Recognition. (On / Off)
* Set the warning sensitivity (0, 5, 10, 15, 20%).
Ex) If you set 10% then you will get alarm

when your speed over the limit more than 10%,

100km limit -> Warning start from 110km speed.
* Enable voice guidance (On / Off).
|[[File:Mdconfi5.1.png|center|frameless]]
|-
| colspan="2" |'''Fleet management setup'''
|-
|
* Set Speed limit warning (Off, 80, 90, 100, 110, 120, 130, 140km/h).

- You can set your own speed limit for your fleet.

- You can set speed limit of your vehicle and get warning if you over the speed limit.

* Enable Transmit data RS-232 feature
(115200 mode should be selected to work with FMx125).

It allows ADAS event data transmission to integrated device.
* Set Lock volume button control on a scale of 1 to 5 and Off.
You can fix the volume level and prevent the driver from adjusting the

settings using indicator.
* Set Break time alarm on a scale of 1 to 6 hours and Off.

* Enable Vibration setting for LDW, FCW, PCW (On / Off / Both).
You can check the connection with the button.
|[[File:Image (3).png|center|frameless]]
|-
| colspan="2" |'''Miscellaneous Settings:'''
|-
|
* Speed Unit on Analog video output (km/h or MPH).

* Set Video out format (NTSC / PAL).

* Set Voice guide language
(English / Korean / Chinese / Spanish / Japanese / Hebrew/ No Sound).
* Enable Indicator buzzer (On / Off).

* Speed Display on Indicator could be ON/Off
|[[File:Mdconfi7.png|center|frameless]]
|-
| colspan="2" |'''ADAS Setup Complete'''
|-
|
* Click “Complete” button to finish Calibration setup. Then ADAS will be
rebooted automatically.
* Click “Export vehicle profile” button, if you want to download vehicleprofile.dat.

This vehicleprofile contains all the calibration settings you’ve set.

With this file, you can simply apply current settings to another vehicle.
|[[File:Mdconfi8.png|frameless|alt=|center|351x351px]]
|}

[[Category: Teltonika ADAS]]

File:688548 DualCam and DSM with FMC650.jpg

2024-06-10T07:55:47Z

Maksim.jefisov:

ADAS First Start

2024-06-03T05:47:05Z

Maksim.jefisov: /* Vehicle installation */

__TOC__

== Main (front) camera unit preparation ==
The main unit comes prepared for bus/large truck setup (cable routing) or vehicles with mostly vertical windshields''.'' To set up the unit for an average truck or passenger vehicle, dismantle partially as shown below:
{| class="wikitable"
|+
! colspan="6" |Unit preparation
|-
|[[File:Camera1.jpg|center|frameless|181x181px]]
|1. Remove cover
|[[File:Camera1.jpg|center|frameless|186x186px]]
|2. Remove (2x) screws,
remove plastic cover
|[[File:Camera3.png|center|frameless|216x216px]]
|3. Remove (2x) screws,
pry plastic mounting

frame off Unit from corners
|-
|[[File:Camera4.png|center|frameless|199x199px]]
|4. Reroute the main
cable (and rear camera

cable, if adding) around unit

to front (glass side)
|[[File:Camera5.png|center|frameless|221x221px]]
|5. Press tightly into
channels when routing cables.

Remove front camera dust sticker
|[[File:Camera6.png|center|frameless|238x238px]]
|6. Replace 1 cover only
removed from step 3.

Replace 2 screws.

Leave the remaining

covers off until the last step
|}

== Vehicle installation ==

1. Clean the spots on the windshield with the ''alcohol wipe'' where you plan to mount the hardware. Remove the red 3M tape and mount the main unit underneath the rear-view mirror as centered (left/right) and straight as possible (if it ''must be off center'' by a few inches, that’s okay – measurements will be taken later). Be certain not to obstruct the drivers view.

[[File:Vehinst1.jpg|frameless|191x191px|d ]]

2. Run the main-unit cable across the headliner and down to the driver side under-dash. This may require removing the A-pillar temporarily. Follow factory harnesses, always run behind any airbags.

3. Attach the mount (from the plastic bag) and stick the LCD indicator on the windshield in the driver’s line-of-sight, usually close to the A-pillar so it can be easily seen and controlled if required. Run this cable down to the driver’s under-dash as well.

[[File:Vehinst2.jpg|frameless]]

4. Once both cables are run to the under-dash, connect them to the provided PCI unit at the proper ports.

[[File:Vehinst3.png|frameless|248x248px]][[File:Vehinst4.png|frameless|310x310px]]

5. Connect the Teltonika FMx125,FMX225 tracker to the main unit using RS232 cable. Please refer connection scheme below.

'''Please note that camera must be connected to ignition source, in other way camera will drain battery'''

[[File:ADAS wiring scheme 2 v2.jpg|center|frameless|1160x1160px]]

'''FMxy25 wiring with DOUT'''
Please note, that alternative wiring with DOUT is possible, in order to receive additional data from ADAS while the ignition is off, but the key is turned to the ACC position. That way it would be possible to control the power supply by turning on/off the camera. To find information on how to configure DOUT, please visit [[FMB setdigout|FMB DOUT]].

[[File:ADAS_w_DOUT.jpg]]

{| class="wikitable"
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| PIN NUMBER
! style="width:15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| PIN NAME
! style="width:25%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| DESCRIPTION
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 4
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''RS232-Tx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| ADAS output for data transmission through RS232
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 3
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''RS232-Rx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| ADAS input for data reception through RS232
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 1
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''VCC (9-36V) (+)'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| Power supply for the ADAS
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 7
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| '''GND''' (-)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| Ground
|-
|}

'''For FMX640 + ADAS connection'''

'''Please note that camera must be connected to an ignition source, in other way the camera will drain battery'''

'''Also, some RJ45 cables have two modifications, some have RS232 output on 3/4 pins some on 5/6 pins'''

For FMX640 devices, RJ45 cable is required with one end cut and loose. Connect the RJ45 cable to the FMX640 device's port 1 or port 2, both slots have RS232 support. Once connected, the other end of the cable should have pin 5-Rx, and 6-Tx shaved and connected to ADAS camera Rx and Tx cable. For the rest of the connection please refer to the picture below.[[File:Adas112233.jpeg]]

'''ADAS connection with relay'''
If it is necessary to receive additional data from the ADAS when the ignition is off but the key is inserted and turned to the ACC position, you can do it by connecting the camera to a power source using a relay in order to control the power supply by turning on/off the camera. To find information on how to configure DOUT, please visit [[FMB setdigout|FMB DOUT]].

[[File:ADAS_w_DOUT6.jpg]]

'''Two cameras FMC650 Installation with Relay'''
. If you need to receive additional data from the Two cameras or one of them when the ignition is off, you can also connect the camera to a power source using the relay, to control the power supply by turning on/off the camera. To find information on how to configure DOUT, please visit [[FMB setdigout|FMB DOUT]].

[[File:2 cameras dout.JPG]]

{| class="wikitable"
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| PIN NUMBER
! style="width:15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| PIN NAME
! style="width:25%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| DESCRIPTION
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 6
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''RS232-Tx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| ADAS output for data transmission through RS232
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 5
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''RS232-Rx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| ADAS input for data reception through RS232
|-
|}

6. Connect the provided Power/Ground harness connection to a chassis ground (black wire) and Ignition source (red wire). The circuit must provide ~3 Amp @12v. Connect the plug to the PCI unit at the ‘Power’ port.

[[File:Vehinst8.png|frameless|357x357px]]

===Installation: for CAN-equipped vehicles===
Many vehicles are available in the database for using the CAN bus for vehicle signals (turn signals, brake and speed sense). This makes for a much faster installation. See below for checking the availability of a downloadable CAN file for your vehicle. NOTE: not all vehicles are available on the database currently, even if the vehicle has CAN. The list is constantly updated, so if the vehicle isn’t there now, it may be later. The installation may still be completed using analogue connections instead of CAN – see next section.

Check to see if there is a CAN file available by opening a Chrome browser and going to http://info.mdas.co.kr/customer/login

USER: [[telematics.adas@teltonika.lt]]

PASS: mDaSdataBase

1. Choose the vehicle ''make'' and ''model'' into the selector at the left.

2. Click the page icon (at right) and the database information will show CAN wire location information (if available) and download the ''‘CAN File Download’'' file at the bottom. '''''NOTE''': this filename will always be ‘mdasinfo.dat’ and cannot be renamed – so if you’re installing another ADAS and using this computer to set up, make a separate file folder (every time) with the vehicle year and model, and put this file inside of it.''
[[File:Vehinst9.png|center|frameless|996x996px]]

3. If there is a CAN file available, connect the provided CAN harness (contactless reader) to the (transmission) CAN bus wires – either where stated or at the OBD2 port, typically pins 14 & 6, if the vehicle is available on the database only.
[[File:Vehinst10.png|center|frameless|454x454px]]

'''''NOTE''': this connection uses inductance. There is no need to strip the CAN wires – just open the black box, lay the CAN High and Low in the channels, then close the box.''

4. Connect the 4-pin plug from the CAN harness to the ‘CAN’ port on the PCI unit.

If the vehicle is not listed in the database, you must use the provided Analog harness, see next section. NOTE: vehicles that are 1 year (or so) off, may still work for CAN access!

===Installation: For Analog signals (no CAN)===
[[File:Vehinst11.png|right|frameless|263x263px]]
If the vehicle has no CAN bus or there is no CAN file available, you must tap the turn signal (left and right), brake and speed signal manually (various locations).

1. With a digital multimeter or test light, locate the brake signal wire that activates when the brake is pressed (the vehicle may need to be ON). Connect and insulate the '''black/white wire''' to this vehicle’s wire. This may be a (+) or (-) signal.

2. With a digital multimeter or test light, locate the left turn signal wire that activates with the left turn signal. Connect and insulate the '''blue/white wire''' to this vehicle’s wire. This may be a (+) or (-) signal.

3. With a digital multimeter or test light, locate the right turn signal wire that activates with the right turn signal. Connect and insulate the '''blue wire''' to this vehicle’s wire. This may be a (+) or (-) signal.

4. Locate the VSS wire. Connect and insulate the '''brown/white wire''' to this vehicle’s wire.

NO other wires are required for typical installation – ground the remaining wires.

==ADAS Calibration==
ADAS Calibration requires:

*a laptop with an internet connection and a browser

*micro-USB cable

*tape measure

*parking the car with a clear, open stretch of about a 45 meters unobstructed view (try to park close to your facility to keep the internet connection accessible – at least during the calibration driver installation)
*a partner to drive the vehicle while speed correction is performed

Before beginning, insert the provided micro-SD card into the main unit in the location shown below until it clicks and turn the Ignition ON. Wait for the prompt, then press and release the center button one time. After the successful prompt and the unit reboots, continue to step 1.
[[File:Vehinst12.png|center|frameless|335x335px]]

1. Park the vehicle in a spot with a clear stretch of unobstructed line-of-sight (about 45 meters). Leave the vehicle running
2. Connect the USB cable to the Mirco-USB port on the side of the main unit (windshield) and the other end to the laptop. If on a windows 10 machine, it should automatically install the required driver. If not or on an older machine, go to movon.co.kr, go to the ‘ADAS’ tab at the top then to ‘Downloads’ under Support. Download the appropriate zip file (contains driver) and extract it fully for your version of Windows OS (if using the 7/8 driver, install the .exe file). If WIN10, once downloaded, disconnect/reconnect the USB and it should automatically install, or find the unit in Device Manager and right-click, Update Driver and browse for driver locally.[[File:Vehinst13.png|center|frameless|335x335px]]
3. Open Chrome browser again and type in ''’10.0.0.1’'' into the URL bar''.'' If the driver was installed properly, the calibration screen will appear. Input credentials and press ''LOGIN'' USER: ''admin'' PASS: ''1234'' 
4. '''Select Vehicle Signal Type:''' there are several wiring options for installation: CAN-BUS / Analog (GPIO) / GPS (Speed). Select the proper calibration option based off which was installed: CAN (if CAN file is available), Analog (if analogue signals were tapped)

'''''Vehicle Data File''''' (CAN-BUS)For CAN-BUS connection, choose the ‘Vehicle info file’ tab and select ‘Choose File’ to upload the previously downloaded ‘mdasinfo.dat’ file (see ‘CAN-Equipped vehicles’ section).
[[File:Vehinst14.jpg|center|frameless|363x363px]]

===Camera location and Vehicle Measurement===
Camera location and vehicle measurement can affect ADAS performance. It`s very important put accurate data for the best performance.
[[File:Vehinst15.png|center|frameless|404x404px|alt=]]
<table class="nd-othertables" style="width: 68%;">
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Camera Option</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Camera Height</td>
<td style="width: 8%; text-align:left">Distance from ground to the center of camera lens.</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera Center</td>
<td style="width: 8%; text-align:left">Distance from the center of windshield to camera lens
“-“: Left Side / “+”:Right Side

(If ADAS is attached 5cm to the right from the center, input 5.

If ADAS is attached 5cm to the left from the center, input -5.)
</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera to Wheel</td>
<td style="width: 8%; text-align:left">Distance from the camera to the center of the wheel.
'''For trucks or buses''', some vehicles’ wheels are located behind.

In this case, please input 20cm.
</td>
</tr><tr><td>Vehicle Width</td><td>Distance between the wheels.
Measure the distance from the left outside border to the right outside border of the wheels.
</td></tr><tr><td>Camera to bumper</td><td>Distance from the camera lens to the end of the bumper.
For trucks or buses, it is recommended to input 300 if a sensitive FCW warning is needed.
</td></tr></table>

Camera angle – adjust the camera angle to locate the horizontal between the red guidelines.
[[File:Vehinst16.png|center|frameless|316x316px]]
In case of indoor installation or somewhere you cannot see the horizon properly, use the same data to "'''Camera Height'''”. Mark the same height on the wall apart about 3 ~ 5 meters from the vehicle.
[[File:Vehinst17.png|center|frameless|332x332px]]

Fine Camera Angle - For better accuracy of ADAS, locate the yellow dotted line in the horizon as close as possible.
[[File:Vehinst18.png|center|frameless|344x344px]]

Hood Line - Locate the red line at the end of the vehicle’s hood line to remove the useless area.
[[File:Vehinst19.png|center|frameless|360x360px]]
Please follow the link for video instructions: https://www.youtube.com/watch?v=93wrc6j9aqA

===ADAS configuration===
{| class="wikitable"
| colspan="2" |'''You can adjust the LDW Sensitivity for your convenience'''
|-
|
* Enable LDW function. (On / Off)

* Set the Activation Speed (15, 30, 45, 60, 75km/h).
* Set the sensitivity of LDW warning on a scale of 1 to 5.
* As the level gets higher, it gets more sensitive.
* Enable Repeat LDW (On / Off)
* If it’s on, ADAS keeps warning until the driver secures the lane.
* Warning sound: Select preferred warning sound for LDW.
|[[File:Mdconfi1.png|center|frameless]]

|-
| colspan="2" |'''You can adjust the FCW Sensitivity for your convenience:'''
|-
|
* Enable FCW function. (On / Off)
* Set the sensitivity of FCW warning on a scale of 1 to 5.
(As the level gets higher, it gets more sensitive)
* Enable Repeat FCW (On / Off).
(If it’s on, ADAS keeps warning until the driver secures safe distance)
* Enable Sync with Brake (On / Off).
(If it’s on, ADAS won’t give FCW warning if the brake pedal was used)
* Warning sound: Select preferred warning sound for FCW
|[[File:Mdconf2.png|center|frameless|301x301px]]
|-
| colspan="2" |'''Safety distance alert setup:'''
|-
|
* Enable SDA function. (On / Off)
* Set the sensitivity of SDA on a scale of 1 to 5.
* As the level gets higher, it gets more sensitive.
* Repeat SDA and SDA re-alert can be changed. (On / Off)

- Repeat SDA: If it’s on, ADAS keeps warning until the driver secures safe distance.

''- Re-alert SDA: If it’s on, ADAS gives warnings every time''

''the same front vehicle gets closer than safe distance.''
|[[File:Mdconfi3.png|center|frameless]]
|-
| colspan="2" |'''Pedestrian collision warning setup:'''
|-
|
* Enable PCW function. (On / Off)

* Warning sound: Select preferred warning sound for PCW.
|[[File:Mdconfi4.png|center|frameless]]
|-
| colspan="2" |'''Advanced ADAS setup:'''
|-
|
* Enable Forward Proximity Warning function. (On / Off)
* Set the warning range on a scale of 1 to 3.
(As the level gets higher, it gets more sensitive)
* Enable Front vehicle start alarm. (On / Off)
* Enable Speed Limit Recognition. (On / Off)
* Set the warning sensitivity (0, 5, 10, 15, 20%).
Ex) If you set 10% then you will get alarm

when your speed over the limit more than 10%,

100km limit -> Warning start from 110km speed.
* Enable voice guidance (On / Off).
|[[File:Mdconfi5.1.png|center|frameless]]
|-
| colspan="2" |'''Fleet management setup'''
|-
|
* Set Speed limit warning (Off, 80, 90, 100, 110, 120, 130, 140km/h).

- You can set your own speed limit for your fleet.

- You can set speed limit of your vehicle and get warning if you over the speed limit.

* Enable Transmit data RS-232 feature
(115200 mode should be selected to work with FMx125).

It allows ADAS event data transmission to integrated device.
* Set Lock volume button control on a scale of 1 to 5 and Off.
You can fix the volume level and prevent the driver from adjusting the

settings using indicator.
* Set Break time alarm on a scale of 1 to 6 hours and Off.

* Enable Vibration setting for LDW, FCW, PCW (On / Off / Both).
You can check the connection with the button.
|[[File:Image (3).png|center|frameless]]
|-
| colspan="2" |'''Miscellaneous Settings:'''
|-
|
* Speed Unit on Analog video output (km/h or MPH).

* Set Video out format (NTSC / PAL).

* Set Voice guide language
(English / Korean / Chinese / Spanish / Japanese / Hebrew/ No Sound).
* Enable Indicator buzzer (On / Off).

* Speed Display on Indicator could be ON/Off
|[[File:Mdconfi7.png|center|frameless]]
|-
| colspan="2" |'''ADAS Setup Complete'''
|-
|
* Click “Complete” button to finish Calibration setup. Then ADAS will be
rebooted automatically.
* Click “Export vehicle profile” button, if you want to download vehicleprofile.dat.

This vehicleprofile contains all the calibration settings you’ve set.

With this file, you can simply apply current settings to another vehicle.
|[[File:Mdconfi8.png|frameless|alt=|center|351x351px]]
|}

[[Category: Teltonika ADAS]]

ADAS First Start

2024-06-03T05:45:56Z

Maksim.jefisov:

__TOC__

== Main (front) camera unit preparation ==
The main unit comes prepared for bus/large truck setup (cable routing) or vehicles with mostly vertical windshields''.'' To set up the unit for an average truck or passenger vehicle, dismantle partially as shown below:
{| class="wikitable"
|+
! colspan="6" |Unit preparation
|-
|[[File:Camera1.jpg|center|frameless|181x181px]]
|1. Remove cover
|[[File:Camera1.jpg|center|frameless|186x186px]]
|2. Remove (2x) screws,
remove plastic cover
|[[File:Camera3.png|center|frameless|216x216px]]
|3. Remove (2x) screws,
pry plastic mounting

frame off Unit from corners
|-
|[[File:Camera4.png|center|frameless|199x199px]]
|4. Reroute the main
cable (and rear camera

cable, if adding) around unit

to front (glass side)
|[[File:Camera5.png|center|frameless|221x221px]]
|5. Press tightly into
channels when routing cables.

Remove front camera dust sticker
|[[File:Camera6.png|center|frameless|238x238px]]
|6. Replace 1 cover only
removed from step 3.

Replace 2 screws.

Leave the remaining

covers off until the last step
|}

== Vehicle installation ==

1. Clean the spots on the windshield with the ''alcohol wipe'' where you plan to mount the hardware. Remove the red 3M tape and mount the main unit underneath the rear-view mirror as centered (left/right) and straight as possible (if it ''must be off center'' by a few inches, that’s okay – measurements will be taken later). Be certain not to obstruct the drivers view.

[[File:Vehinst1.jpg|frameless|191x191px|d ]]

2. Run the main-unit cable across the headliner and down to the driver side under-dash. This may require removing the A-pillar temporarily. Follow factory harnesses, always run behind any airbags.

3. Attach the mount (from the plastic bag) and stick the LCD indicator on the windshield in the driver’s line-of-sight, usually close to the A-pillar so it can be easily seen and controlled if required. Run this cable down to the driver’s under-dash as well.

[[File:Vehinst2.jpg|frameless]]

4. Once both cables are run to the under-dash, connect them to the provided PCI unit at the proper ports.

[[File:Vehinst3.png|frameless|248x248px]][[File:Vehinst4.png|frameless|310x310px]]

5. Connect the Teltonika FMx125,FMX225 tracker to the main unit using RS232 cable. Please refer connection scheme below.

'''Please note that camera must be connected to ignition source, in other way camera will drain battery'''

[[File:ADAS wiring scheme 2 v2.jpg|center|frameless|1160x1160px]]

'''FMxy25 wiring with DOUT'''
Please note, that alternative wiring with DOUT is possible, in order to receive additional data from ADAS while the ignition is off, but the key is turned to the ACC position. That way it would be possible to control the power supply by turning on/off the camera. To find information on how to configure DOUT, please visit [[FMB setdigout|FMB DOUT]].

[[File:ADAS_w_DOUT.jpg]]

{| class="wikitable"
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| PIN NUMBER
! style="width:15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| PIN NAME
! style="width:25%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| DESCRIPTION
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 4
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''RS232-Tx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| ADAS output for data transmission through RS232
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 3
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''RS232-Rx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| ADAS input for data reception through RS232
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 1
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''VCC (9-36V) (+)'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| Power supply for the ADAS
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 7
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| '''GND''' (-)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| Ground
|-
|}

'''For FMX640 + ADAS connection'''

'''Please note that camera must be connected to an ignition source, in other way the camera will drain battery'''

'''Also, some RJ45 cables have two modifications, some have RS232 output on 3/4 pins some on 5/6 pins'''

For FMX640 devices, RJ45 cable is required with one end cut and loose. Connect the RJ45 cable to the FMX640 device's port 1 or port 2, both slots have RS232 support. Once connected, the other end of the cable should have pin 5-Rx, and 6-Tx shaved and connected to ADAS camera Rx and Tx cable. For the rest of the connection please refer to the picture below.[[File:Adas112233.jpeg]]

'''ADAS connection with relay'''
If it is necessary to receive additional data from the ADAS when the ignition is off but the key is inserted and turned to the ACC position, you can do it by connecting the camera to a power source using a relay in order to control the power supply by turning on/off the camera. To find information on how to configure DOUT, please visit [[FMB setdigout|FMB DOUT]].

[[File:ADAS_w_DOUT6.jpg]]

'''Two cameras FMC650 Installation with Relay'''
. If you need to receive additional data from the Two cameras or one of them when the ignition is off, you can also connect the camera to a power source using the relay, to control the power supply by turning on/off the camera. To find information on how to configure DOUT, please visit [[FMB setdigout|FMB DOUT]].
.

{| class="wikitable"
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| PIN NUMBER
! style="width:15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| PIN NAME
! style="width:25%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| DESCRIPTION
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 6
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''RS232-Tx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| ADAS output for data transmission through RS232
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 5
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''RS232-Rx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| ADAS input for data reception through RS232
|-
|}

6. Connect the provided Power/Ground harness connection to a chassis ground (black wire) and Ignition source (red wire). The circuit must provide ~3 Amp @12v. Connect the plug to the PCI unit at the ‘Power’ port.

[[File:Vehinst8.png|frameless|357x357px]]

===Installation: for CAN-equipped vehicles===
Many vehicles are available in the database for using the CAN bus for vehicle signals (turn signals, brake and speed sense). This makes for a much faster installation. See below for checking the availability of a downloadable CAN file for your vehicle. NOTE: not all vehicles are available on the database currently, even if the vehicle has CAN. The list is constantly updated, so if the vehicle isn’t there now, it may be later. The installation may still be completed using analogue connections instead of CAN – see next section.

Check to see if there is a CAN file available by opening a Chrome browser and going to http://info.mdas.co.kr/customer/login

USER: [[telematics.adas@teltonika.lt]]

PASS: mDaSdataBase

1. Choose the vehicle ''make'' and ''model'' into the selector at the left.

2. Click the page icon (at right) and the database information will show CAN wire location information (if available) and download the ''‘CAN File Download’'' file at the bottom. '''''NOTE''': this filename will always be ‘mdasinfo.dat’ and cannot be renamed – so if you’re installing another ADAS and using this computer to set up, make a separate file folder (every time) with the vehicle year and model, and put this file inside of it.''
[[File:Vehinst9.png|center|frameless|996x996px]]

3. If there is a CAN file available, connect the provided CAN harness (contactless reader) to the (transmission) CAN bus wires – either where stated or at the OBD2 port, typically pins 14 & 6, if the vehicle is available on the database only.
[[File:Vehinst10.png|center|frameless|454x454px]]

'''''NOTE''': this connection uses inductance. There is no need to strip the CAN wires – just open the black box, lay the CAN High and Low in the channels, then close the box.''

4. Connect the 4-pin plug from the CAN harness to the ‘CAN’ port on the PCI unit.

If the vehicle is not listed in the database, you must use the provided Analog harness, see next section. NOTE: vehicles that are 1 year (or so) off, may still work for CAN access!

===Installation: For Analog signals (no CAN)===
[[File:Vehinst11.png|right|frameless|263x263px]]
If the vehicle has no CAN bus or there is no CAN file available, you must tap the turn signal (left and right), brake and speed signal manually (various locations).

1. With a digital multimeter or test light, locate the brake signal wire that activates when the brake is pressed (the vehicle may need to be ON). Connect and insulate the '''black/white wire''' to this vehicle’s wire. This may be a (+) or (-) signal.

2. With a digital multimeter or test light, locate the left turn signal wire that activates with the left turn signal. Connect and insulate the '''blue/white wire''' to this vehicle’s wire. This may be a (+) or (-) signal.

3. With a digital multimeter or test light, locate the right turn signal wire that activates with the right turn signal. Connect and insulate the '''blue wire''' to this vehicle’s wire. This may be a (+) or (-) signal.

4. Locate the VSS wire. Connect and insulate the '''brown/white wire''' to this vehicle’s wire.

NO other wires are required for typical installation – ground the remaining wires.

==ADAS Calibration==
ADAS Calibration requires:

*a laptop with an internet connection and a browser

*micro-USB cable

*tape measure

*parking the car with a clear, open stretch of about a 45 meters unobstructed view (try to park close to your facility to keep the internet connection accessible – at least during the calibration driver installation)
*a partner to drive the vehicle while speed correction is performed

Before beginning, insert the provided micro-SD card into the main unit in the location shown below until it clicks and turn the Ignition ON. Wait for the prompt, then press and release the center button one time. After the successful prompt and the unit reboots, continue to step 1.
[[File:Vehinst12.png|center|frameless|335x335px]]

1. Park the vehicle in a spot with a clear stretch of unobstructed line-of-sight (about 45 meters). Leave the vehicle running
2. Connect the USB cable to the Mirco-USB port on the side of the main unit (windshield) and the other end to the laptop. If on a windows 10 machine, it should automatically install the required driver. If not or on an older machine, go to movon.co.kr, go to the ‘ADAS’ tab at the top then to ‘Downloads’ under Support. Download the appropriate zip file (contains driver) and extract it fully for your version of Windows OS (if using the 7/8 driver, install the .exe file). If WIN10, once downloaded, disconnect/reconnect the USB and it should automatically install, or find the unit in Device Manager and right-click, Update Driver and browse for driver locally.[[File:Vehinst13.png|center|frameless|335x335px]]
3. Open Chrome browser again and type in ''’10.0.0.1’'' into the URL bar''.'' If the driver was installed properly, the calibration screen will appear. Input credentials and press ''LOGIN'' USER: ''admin'' PASS: ''1234'' 
4. '''Select Vehicle Signal Type:''' there are several wiring options for installation: CAN-BUS / Analog (GPIO) / GPS (Speed). Select the proper calibration option based off which was installed: CAN (if CAN file is available), Analog (if analogue signals were tapped)

'''''Vehicle Data File''''' (CAN-BUS)For CAN-BUS connection, choose the ‘Vehicle info file’ tab and select ‘Choose File’ to upload the previously downloaded ‘mdasinfo.dat’ file (see ‘CAN-Equipped vehicles’ section).
[[File:Vehinst14.jpg|center|frameless|363x363px]]

===Camera location and Vehicle Measurement===
Camera location and vehicle measurement can affect ADAS performance. It`s very important put accurate data for the best performance.
[[File:Vehinst15.png|center|frameless|404x404px|alt=]]
<table class="nd-othertables" style="width: 68%;">
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Camera Option</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Camera Height</td>
<td style="width: 8%; text-align:left">Distance from ground to the center of camera lens.</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera Center</td>
<td style="width: 8%; text-align:left">Distance from the center of windshield to camera lens
“-“: Left Side / “+”:Right Side

(If ADAS is attached 5cm to the right from the center, input 5.

If ADAS is attached 5cm to the left from the center, input -5.)
</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera to Wheel</td>
<td style="width: 8%; text-align:left">Distance from the camera to the center of the wheel.
'''For trucks or buses''', some vehicles’ wheels are located behind.

In this case, please input 20cm.
</td>
</tr><tr><td>Vehicle Width</td><td>Distance between the wheels.
Measure the distance from the left outside border to the right outside border of the wheels.
</td></tr><tr><td>Camera to bumper</td><td>Distance from the camera lens to the end of the bumper.
For trucks or buses, it is recommended to input 300 if a sensitive FCW warning is needed.
</td></tr></table>

Camera angle – adjust the camera angle to locate the horizontal between the red guidelines.
[[File:Vehinst16.png|center|frameless|316x316px]]
In case of indoor installation or somewhere you cannot see the horizon properly, use the same data to "'''Camera Height'''”. Mark the same height on the wall apart about 3 ~ 5 meters from the vehicle.
[[File:Vehinst17.png|center|frameless|332x332px]]

Fine Camera Angle - For better accuracy of ADAS, locate the yellow dotted line in the horizon as close as possible.
[[File:Vehinst18.png|center|frameless|344x344px]]

Hood Line - Locate the red line at the end of the vehicle’s hood line to remove the useless area.
[[File:Vehinst19.png|center|frameless|360x360px]]
Please follow the link for video instructions: https://www.youtube.com/watch?v=93wrc6j9aqA

===ADAS configuration===
{| class="wikitable"
| colspan="2" |'''You can adjust the LDW Sensitivity for your convenience'''
|-
|
* Enable LDW function. (On / Off)

* Set the Activation Speed (15, 30, 45, 60, 75km/h).
* Set the sensitivity of LDW warning on a scale of 1 to 5.
* As the level gets higher, it gets more sensitive.
* Enable Repeat LDW (On / Off)
* If it’s on, ADAS keeps warning until the driver secures the lane.
* Warning sound: Select preferred warning sound for LDW.
|[[File:Mdconfi1.png|center|frameless]]

|-
| colspan="2" |'''You can adjust the FCW Sensitivity for your convenience:'''
|-
|
* Enable FCW function. (On / Off)
* Set the sensitivity of FCW warning on a scale of 1 to 5.
(As the level gets higher, it gets more sensitive)
* Enable Repeat FCW (On / Off).
(If it’s on, ADAS keeps warning until the driver secures safe distance)
* Enable Sync with Brake (On / Off).
(If it’s on, ADAS won’t give FCW warning if the brake pedal was used)
* Warning sound: Select preferred warning sound for FCW
|[[File:Mdconf2.png|center|frameless|301x301px]]
|-
| colspan="2" |'''Safety distance alert setup:'''
|-
|
* Enable SDA function. (On / Off)
* Set the sensitivity of SDA on a scale of 1 to 5.
* As the level gets higher, it gets more sensitive.
* Repeat SDA and SDA re-alert can be changed. (On / Off)

- Repeat SDA: If it’s on, ADAS keeps warning until the driver secures safe distance.

''- Re-alert SDA: If it’s on, ADAS gives warnings every time''

''the same front vehicle gets closer than safe distance.''
|[[File:Mdconfi3.png|center|frameless]]
|-
| colspan="2" |'''Pedestrian collision warning setup:'''
|-
|
* Enable PCW function. (On / Off)

* Warning sound: Select preferred warning sound for PCW.
|[[File:Mdconfi4.png|center|frameless]]
|-
| colspan="2" |'''Advanced ADAS setup:'''
|-
|
* Enable Forward Proximity Warning function. (On / Off)
* Set the warning range on a scale of 1 to 3.
(As the level gets higher, it gets more sensitive)
* Enable Front vehicle start alarm. (On / Off)
* Enable Speed Limit Recognition. (On / Off)
* Set the warning sensitivity (0, 5, 10, 15, 20%).
Ex) If you set 10% then you will get alarm

when your speed over the limit more than 10%,

100km limit -> Warning start from 110km speed.
* Enable voice guidance (On / Off).
|[[File:Mdconfi5.1.png|center|frameless]]
|-
| colspan="2" |'''Fleet management setup'''
|-
|
* Set Speed limit warning (Off, 80, 90, 100, 110, 120, 130, 140km/h).

- You can set your own speed limit for your fleet.

- You can set speed limit of your vehicle and get warning if you over the speed limit.

* Enable Transmit data RS-232 feature
(115200 mode should be selected to work with FMx125).

It allows ADAS event data transmission to integrated device.
* Set Lock volume button control on a scale of 1 to 5 and Off.
You can fix the volume level and prevent the driver from adjusting the

settings using indicator.
* Set Break time alarm on a scale of 1 to 6 hours and Off.

* Enable Vibration setting for LDW, FCW, PCW (On / Off / Both).
You can check the connection with the button.
|[[File:Image (3).png|center|frameless]]
|-
| colspan="2" |'''Miscellaneous Settings:'''
|-
|
* Speed Unit on Analog video output (km/h or MPH).

* Set Video out format (NTSC / PAL).

* Set Voice guide language
(English / Korean / Chinese / Spanish / Japanese / Hebrew/ No Sound).
* Enable Indicator buzzer (On / Off).

* Speed Display on Indicator could be ON/Off
|[[File:Mdconfi7.png|center|frameless]]
|-
| colspan="2" |'''ADAS Setup Complete'''
|-
|
* Click “Complete” button to finish Calibration setup. Then ADAS will be
rebooted automatically.
* Click “Export vehicle profile” button, if you want to download vehicleprofile.dat.

This vehicleprofile contains all the calibration settings you’ve set.

With this file, you can simply apply current settings to another vehicle.
|[[File:Mdconfi8.png|frameless|alt=|center|351x351px]]
|}

[[Category: Teltonika ADAS]]

File:2 cameras dout.JPG

2024-05-31T14:38:26Z

Maksim.jefisov: Maksim.jefisov uploaded a new version of File:2 cameras dout.JPG

Template:Video Solutions

2024-05-07T09:53:56Z

Maksim.jefisov:

[[Teltonika DualCam]] 
[[Teltonika DashCam]] 
[[Teltonika ADAS]] 
[[DSM|Teltonika DSM]]

ADAS Firmware errata

2024-04-23T11:22:24Z

Maksim.jefisov: /* ADAS Firmware Version */

__TOC__

We are always improving our device's performance, stability, and reliability. 
This document describes '''ADAS platform''' devices' firmware improvements, changes, new features implementations as well as current firmware release version.

'''Firmware download for FMX:125/225/640/FMC650'''

Link: [https://drive.teltonika.lt/d/c4a0dfc59e5f4fbdb991/ Firmware]

Password: lXKOpgIu

==Firmware for FMC650==

{| class="wikitable" style="width: 100%;"
|+
|-
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |CHANGES
|-

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.00.14.Rev.116'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2024-04-05}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* '''NEW:''' ADAS support.
|-
|}
==ADAS Firmware Version==

{| class="wikitable" style="width: 100%;"
|+
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FMX640 FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |CHANGES
|-

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''01.02.22.Rev.105'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2024-04-15}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Video download improvements
* Overlay functions improvements
* Save to SD settings improvements
* Improve stable work

|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''01.02.22.Rev.102'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2023-03-13}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* CRC calculation from a proper location not from a hardcoded Flash area
* Wrong server used with consecutive uploads
* Metadata request type changed for periodic snapshot
* Periodic image request by date instead of the current snapshot
* Fixed auto baud rate functionality unpausing scheduled jobs
* Prevent SD card access when downloading from MDAS
* Remount SD card when a disk error occurs
* Camera resolution configuration
* Default server\port in SMS requests
* Setting the overlay when it is disabled
* MDAS speed source selection
* Record sending with file details

|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''01.02.22.Rev.101'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-10-21}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Crash in DDD files sending
* ADAS base update

|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''01.02.10.Rev.103_ID1039'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-07-05}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Firmware for FMC640 and FMB640
* Base update to latest version
* Video/photo by request
* Periodic photo sending
|-
|}

{| class="wikitable" style="width: 100%;"
|+
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FMX125/FMX225 FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |CHANGES
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.27.13.Rev.370'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-07-26}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Base update to latest version Meig Support
* Accessory monitoring port to MDAS9
* Firmware for FMX125 and FMX225 also for Meig
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.27.07.Rev.370'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2021-10-18}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Base update to latest version
* Minor configurator fixes
* Improved system stability and fixed general bugs
* Firmware for FMX125 and FMX225
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.27.01.Rev.242'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2021-01-06}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* FPW and FVSA bug fixes
* Minor improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.27.01.Rev.240'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2020-10-26}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Added ADAS camera support
* Initial release
|-
|}

{| class="wikitable" style="width: 100%;"
|+
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |ADAS FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |CHANGES
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''0.6.32'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2023-04-17}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* [FIX] File transfer resume multiple presents for the same request
* [FIX] Packet index number in transfer resume CMD according to argument 2023.12.05
* [FIX] Packet index number in transfer resume
* [FIX] Video and snapshot transfer resume
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''0.6.15'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2023-06-15}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Fix Video and snapshot transfer resume
* Fix OSD ON/OFF functionality
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''0.6.10'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-10-14}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Fixed malfunction of Lock Volume function
* Fix on vehicle file not applied properly via FMS command
|-

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''0.6.03'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-07-22}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Fixed miss usage of HEX values instead of DEC
|-

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''0.6.01'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-07-12}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Fix where protocol version changed to 13 or 0x13
* Fix for wrong GPS coordinates offset
|-

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''0.5.99'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-07-10}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Added video compression quality change via 0x7D
* Added file transfer resume via 0x9F
* Fixed abnormal packet communication during fw update
* Fixed speed value display on overlay
* Fixed option to use only FMx GPS data via 0x9C
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''0.5.95'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-06-01}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Support 128 Gb SD card
* Video/photo by request
* Periodic photo sending
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''0.5.78'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2021-07-21}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Configurable video size supported
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''0.5.68'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2021-04-19}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Russian language added
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''0.5.12'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2019-07-19}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* LDW activation speed (mph) changed
|-

|}
[[Category: Teltonika ADAS]]

ADAS Configuration

2024-04-23T11:19:37Z

Maksim.jefisov: /* ADAS configuration for FMx650 */

__TOC__

==FMx640 Configuration==

'''It is important to note that ADAS cameras with Serial Numbers (S/N) starting with "9C" are exclusively compatible with FMX640 devices. However, cameras with Serial Numbers beginning with "9B" are typically designed for use with FMX125/225 devices.''' In the event you receive a camera with a Serial Number starting with "9B," it is crucial to check for a red circle sticker on the camera. The presence of this red sticker indicates that the camera, despite its "9B" Serial Number, is actually compatible with FMX640 devices, functioning equivalently to cameras with a "9C" Serial Number. This is due to the serial numbers being pre-attached to the camera case by the manufacturer and remaining constant for warranty purposes. If your camera with a "9B" Serial Number has this red sticker, proceed to connect it to a computer, install the required drivers, and visit IP 10.0.0.1 in a browser. Here, you will find more details about the camera, which will confirm its compatibility with FMX640 devices, as the actual Serial Number displayed will start with "9C.

'''NOTE: You need to insert an SD card into the FMX640 device; otherwise, you will not receive any video or photo on the server.'''

[[File:ADAS 9B sticker.png | 250px]]

{| class="wikitable" style="border-style: solid; border-width: 0px;"
| style="width: auto; text-align: left; background: #F6F6FB;" |'''NOTE!'''
| style="width: auto; text-align: left; background: #F6F6FB;" |ADAS devices which start with '''9C''' - will provide a red sticker, as shown on the picture. ADAS devices which start with '''9B''' - '''WILL NOT''' provide a red circle sticker.

The picture has been only made for explanation purposes, and does not show the real replication of the sticker for 9B.
|}

'''Device Configuration'''

It is necessary to change Data Protocol to [[Codec#Codec_8_Extended | Codec 8 Extended]]

[[Image:Data_protocol.gif|300px]]

Configure the Domain and Port to send the data to the desired server.

[[File:Server222.jpg|alt=|frameless]]

In RS232/RS485 settings enable ADAS under RS232 mode in order for the configurator to open additional settings for ADAS accessory.

'''Please also note, a new baudrate "460800" is now supported. Please set baudrate settings to either Auto or 460800. This baudrate will allow faster photo/video transfers however, it is required ADAS FW version of 0.5.95 or later, be updated via SD card, for this update please contact the sale manager or fil the VipHelp Desk.'''

[[File:ADASbaud2.png|alt=|frameless|500px]]

Once ADAS under RS232 mode is enabled, new tabs will open with additional configurable settings to "ADAS" and "ADAS IO".

In these settings it is important to remember that when a feature is enabled under "ADAS" tab, in order for the FMX640 device to send data about this feature to the server, it has to be given a priority "Low, Medium, High" inside of "ADAS IO" tab.

'''Crash event video settings'''

[[File:ADAS-settings1.png|alt=|frameless|400px]]

These settings are responsible for video length before and after the event. User can set up to 20 seconds of video data to be saved before the crash and a maximum of 10 seconds after the crash. A minimum of 5 seconds is required between the both settings.

Please note, more seconds means longer sending periods and more data usage.

'''Image/video settings'''

[[File:ADAS-settings2.png|alt=|frameless|400px]]

Image/video resolution can be chosen between 640x480 and 1280x720.

Please note, 1280x720 resolution is almost twice as large as the 640x480. This means that videos would take much larger storage space and sending them to the server would take more time.

'''Forward vehicle start alarm FVSA'''

[[File:ADAS-settings3.png|alt=|frameless|400px]]

This setting enables front vehicle movement detection and sets up an alarm once the vehicle starts moving.

Sensitivity ranging from 1 to 5 where 1 is least sensitive and 5 is the most sensitive option. Warning sound can be set by the user to their liking.

'''Speed limit recognition SLR'''

[[File:ADAS-settings4.png|alt=|frameless|400px]]

This setting allows fleet management companies or users to set maximum speed limit for that one particular vehicle and if that speed is exceeded, the driver is notified.

Sensitivity setting would indicate how sensitive the ADAS camera would be to exceeding speed limit, 1 would be least sensible giving driver the most room for exceeding the speed limit whereas 5 would strictly stick to the speed limit.

'''Lane departure warning LDW'''

[[File:ADAS-settings5.png|alt=|frameless|400px]]

This feature allows ADAS camera to track driver's lane changing and will notify the driver if the vehicle is moving out of its lane. This feature is also effective if the driver falls asleep and the vehicle starts to swivel.

Activation speed is a setting from which this feature activates.

Sensitivity settings determines how sensitive the camera will be to swiveling on the road meaning 1, swiveling in lane should not activate this feature while 5 which is the highest sensitivity will activate the feature if the vehicle swivels more than it should.

Warning sound repeat can be turned on which will keep on making warning sound until vehicle returns to lane.

'''Forward collision warning FCW'''

[[File:ADAS-settings6.png|alt=|frameless|400px]]

This feature if enabled, notified the driver if the vehicle is getting too close to the obstacle in front.

Sync with brake allows the ADAS camera to deactivate warning sounds if it detects vehicle stopping meaning the driver is aware of obstacle in the front.

Vibration activation will notify the driver when the vehicle is hitting small object which are too small for camera to notice so instead, vehicle starts to vibrate during collision with small objects and therefore the feature will activate warning sounds. Sensitivity setting will determine whether weak vibration should be detected or not.

Repeat function will keep the warning sounds on until the event will deactivate

'''Safety distance alert SDA'''

[[File:ADAS-settings7.png|alt=|frameless|400px]]

This feature activates if the vehicle in front is too close and the distance should be increased.

Re-Alert setting gives warning if the same vehicle in the front gets too close every time.

{| class="wikitable"
|-
! colspan="5" | SDA sensitivity
|- style="font-weight:bold;"
| Level 1
| Level 2
| Level 3 (Default)
| Level 4
| Level 5
|-
| 0.6 sec
| 0.9 sec
| 1.2 sec
| 1.5 sec
| 2.0 sec
|}

'''Pedestrian collision warning PCW'''

[[File:ADAS-settings8.png|alt=|frameless|400px]]

This feature if enabled, notified the driver if the vehicle is getting too close to the obstacle in front.

Vibration activation will notify the driver when the vehicle is hitting small object which are too small for camera to notice so instead, vehicle starts to vibrate during collision with small objects and therefore the feature will activate warning sounds. Sensitivity setting will determine whether weak vibration should be detected or not.

'''Forward proximity warning FPW'''

[[File:ADAS-settings9.png|alt=|frameless|400px]]

This feature once enabled, provides warning if there is an object in the front of the vehicle or within ADAS camera's proximity.

Sensitivity from 1 to 5 is responsible for distance the event triggers, 1 is the least sensitive option while 5 is the strongest sensitivity.

'''Event Indication'''

[[File:ADAS-settings10.png|alt=|frameless|400px]]

This feature allows ADAS system to work in sync with FMX640 safety driving features such as Eco-driving, Over Speeding and Geofence. These features usually work with buzzers, LEDs and etc. connected straight to FMX640 device as outputs however, FMX640 devices can be connected straight with ADAS system which has sound warnings and the need for external peripherals is not required anymore.

'''File upload settings'''

[[File:ADAS-settings11.png|alt=|frameless|400px]]

File upload settings feature is responsible for image and video sending to user's preferred server if they require these files to be sent to another server or even the same server but different port.

Periodic image-sending functionality is also available with configurable sending intervals.

Image and Video sending can also be triggered by different inputs such as DINs for photos and videos, and different FMX640 features such as Crash, Towing, Idling and etc for photos.

Video duration can also be configured before and after the trigger event.

'''Overlay'''

[[File:ADAS-settings12.png|alt=|frameless|400px]]

Image and video records can have specific overlays on it recorded in order to provide additional information to the viewer.

Available information to display can be chosen between "Date and time", "GPS information" and "Speed".

GPS information can have a configurable update period which can be specified by the user allowing the device to use more or less network resources.

If you choose to use the "Speed" overlay, you will have four different options to choose from: GPS, CAN adapter, FMS or K-Line. Once you select one of these options, it will be used as the source for your speed information. Speed overlay settings can be useful in case wiring schemes are not available for specific vehicles, that way it would allow more flexible speed source configuration.

The overlay information update period determines how often information will be updated. Recommended value is 1000 ms

'''Garbage collector'''

[[File:ADAS-settings13.png|alt=|frameless|400px]]

ADAS system can save files inside of itself or FMX640 device if an additional microSD card is connected. However, from time to time, a lot of files can be accumulated which in turn will fill up the free space overcrowding the card and new files will stop producing. To reduce the hassle of taking out the card and deleting the contents inside of it manually, garbage collector functionality is introduced. It automatically deletes all records older than the specified days thus freeing up the space in the microSD card allowing it efficiently operate for longer periods of time.

'''ADAS IO'''

New IO elements called "ADAS" will appear in the configurator. Under this tab, the user can select either low or high priority on different features which they would like to receive on their server. Selecting priority will also allow the users to receive specific ADAS functionalities and ignore the ones they do not need.

[[File:Adas conf2.png|center|frameless|1000x1000px]]

==ADAS configuration for FMx650==

'''(!) Required firmware version - 03.00.14.Rev.116'''. [[DSM_Firmware_errata|Firmware errata.]]

*Make sure '''Data Protocol''' is set to [[Codec#Codec_8_Extended | Codec 8 Extended]]

[[Image:Data_protocol.gif|300px]]

*In ''RS232 \ RS485 settings tab'', make sure to enable '''Camera interface''' by "Enable", and select '''ADAS''' in the Mode drop-down menu, afterwards '''ADAS COM1''' and '''Camera I/O''' should appear in the tab list.

[[Image:ADAS COM1.gif|600px]]

*Make sure to change '''Camera I/O''' camera state '''Priorities''' to ''Low''
'''
[[File:ADAS CameraIO.gif|500px]]
'''

*In appeared ''ADAS COM1'' tab, make sure to '''configure everything by your needs''', and do not forget to complete the '''"Domain"''' and '''"Port"''' settings in ''File upload settings''

[[File:ADAS.png|500px]]

*'''''NOTE:''''' ''This is a base setup for the device to work properly. Other device configuration is made according to your needs.

===Connecting two cameras simultaneously for FMx650===
------------------
The new feature for FMx650 ADAS configuration, which is available from '''03.00.14.Rev.114-Rev.116 iCamera''' allows you to connect two of your cameras at once. Method for connection and configuration stays the same, for this you are only required to choose '''two''' cameras in '''"RS232 \ RS485"''' tab from the configurator.

In the new functionality, you are able to connect any combo of the cameras by your wish, as an example: you are able to connect ''ADAS/DSM'', ''ADAS/DualCam'', ''DSM/Dualcam'', ''DashCam/DualCam'', ''DSM/DSM'', ''DualCam/DualCam'' and etc.

[[File:Twincamera.gif|500px]]

==FMx125/FMX225 Configuration==
ADAS functionality is intended for use with devices, that have RS232. It was implemented in '''FMB.Ver.03.27.01.Rev.242'''. New RS232 mode was implemented for ADAS camera data reading and a new ADAS IO section was created.

In order for ADAS functionality to work „ADAS Camera“ RS232 mode has to be selected (151 parameter ID, value 21).
[[File:Rs232adas.jpg|center|frameless|250x250px]]

'''Note''':

1) Please use Codec08 extended protocol with ADAS functionality

[[File:Codec8adas.png|center|frameless|300x300px]]

2) RS232 baudrate should be configured 115200 bps

[[File:Adas232set.png|center|frameless|300x300px]]

3) New IO elements called "ADAS" will appear in the configurator. Under this tab, the user can select either low or high priority on different features which they would like to receive on their server. Selecting priority will also allow the users to receive specific ADAS functionalities and ignore the ones they do not need.

[[File:Adasconf1.png|center|frameless|1000x1000px]]

==Crash Detection Functionality using DOUT==

'''The crash detection feature''' is a crucial capability provided by our device. It enhances evidential documentation through video or photo evidence in the event of a crash. However, activating this functionality necessitates a direct connection of the camera to a power source. Nonetheless, such a direct connection can lead to '''battery drainage'''.

To circumvent this issue, we recommend utilizing DOUT and a relay for connection. This setup enables control via SMS or GPRS command, or through predefined scenarios within our device. By activating DOUT post-ignition, the camera receives power, allowing it to function and record evidence even after the ignition is turned off following a crash. '''For your convenience, the connection scheme can be found here: [[ADAS First Start]]'''

'''It is important to note that in the event of a fatal crash where fatalities may occur,''' we cannot guarantee the retrieval of video or photo evidence due to the severity of the accident. Moreover, both the camera and the device itself may sustain irreparable damage in such instances

[[Category:DSM]]

[[Category: Teltonika ADAS]]

File:ADAS.png

2024-04-23T11:18:27Z

Maksim.jefisov:

2024-04-09T10:44:38Z

Maksim.jefisov: /* Crash Detection Functionality using DOUT1 */

==FMX125/225 configuration==

*Please make sure to download the latest DualCam FW version. The latest FWs can be downloaded from the following Wiki page — [[DualCam Firmware errata]]

*It is necessary to change '''Data Protocol''' to [[Codec#Codec_8_Extended | Codec 8 Extended]]

[[Image:Data_protocol.gif|300px]]

*Make sure to change '''I/O''' Camera state '''Priorities''' to ''Low''
'''
[[File:Io.gif|500px]]
'''

*In '''RS232\RS485''' settings change '''Mode''' to ''RS232'' and in '''RS232 Mode''' select ''DualCam''
[[File:232.gif|500px]]

*'''Do not forget''' to configure ''DualCam'' server information. In '''RS232\RS485''' fill in '''DualCam Server Settings''' with ''Domain'' and ''Port'' entries.
[[File:Dualcamserver.png|600px]]

==FMC650 DualCam Configuration==

'''(!) Required firmware version - 03.00.14.Rev.114'''. [[DualCam Firmware errata|Firmware errata.]]

*Make sure '''Data Protocol''' is set to [[Codec#Codec_8_Extended | Codec 8 Extended]]

[[Image:Data_protocol.gif|300px]]

*In ''RS232 \ RS485 settings tab'', make sure to enable '''Camera interface''' by "Enable", and select '''DualCam''' in the Mode drop-down menu, afterwards '''DualCam COM1''' and '''Camera I/O''' should appear in the tab list.

[[Image:DualCam config.gif|600px]]

*Make sure to change '''Camera I/O''' camera state '''Priorities''' to ''Low''
'''
[[File:DualCam IO FMC650.gif|500px]]
'''

*In appeared ''DualCam COM1'' tab, make sure to '''configure everything by your needs''', and do not forget to complete the '''"Domain"''' and '''"Port"''' settings in ''"DualCam" Scenario Settings''

[[File:DualCam COM1.png|500px]]

*'''''NOTE:''''' ''This is a base setup for the device to work properly. Other device configuration is made according to your needs.

*'''''NOTE:''''' ''There are different settings for picture quality and compression, these settings will affect picture/video sizes and upload speeds. For more information about transfer sizes and timings, please visit our [[Camera_Manual#DualCam_data_transfer_timing | DualCam Data Transfer Timing]] section

===Connecting two cameras simultaneously for FMx650===
------------------
The new feature for FMx650 DualCam configuration, which is available from '''03.00.14.Rev.114 iCamera''' allows you to connect two of your cameras at once. Method for connection and configuration stays the same, for this you are only required to choose '''two''' cameras in '''"RS232 \ RS485"''' tab from the configurator.

In the new functionality, you can connect any combo of the cameras by your wish, as an example: you are able to connect ''DSM/Dualcam'', ''DashCam/DualCam'', ''DSM/DSM'', ''DualCam/DualCam'' etc.

[[File:Twincamera.gif|500px]]

==Camera Scenario Mode==

The options On Ignition and Always determine the working mode.

'''On Ignition''' means the camera scenarios will operate the way it was up to '''03.27.03.Rev.105''', that is it will work only when the ignition is detected.

'''Always''' mode means the camera scenarios will work all the time, including whenever the device is in sleep mode (excepting Ultra sleep mode during which scenario is disabled). During sleep footage requests (if the network is available), periodic image sending and triggers work as well.

'''Warning:''' using Always mode, depending on the configuration, the device might wake up from sleep very frequently. That has to be taken into consideration when configuring the scenarios.

==Periodic image sending scenario==
Periodic image sending triggers photo capture from a front camera, whenever the timeout is reached (sending interval parameter).

'''Update: Since 03.27.03.Rev.04 firmware''', Periodic Image Sending Enable/Disable switch was replaced by a camera selection:
* Both cameras deselected – periodic image sending is disabled (value 0)
* Front camera selected – front camera’s pictures will be sent periodically (value 1)
* Rear camera selected – rear camera’s pictures will be sent periodically (value 2)
* Both cameras selected – both cameras’ pictures will be sent periodically (value 3)
If the camera has not finished uploading pictures to the server, then the photo capture is skipped.

==File Transfer priority==
Filet transfer priority allows changing the priority of the specific type (photo or video) when both types are ready at once. The file transfer priority can be the following:
<ul>
<li>Picture — the photo type of files will be prioritized. </li>
<li>Video — the video type of files will be prioritized. </li>
<li>Alternating — the priority will be changing from picture to video and vice versa after each file transmission. </li>
</ul>
[[File:filetransferpriority.gif|500px]]

==Camera RTC synchronization==
Camera RTC synchronization is done anytime the device itself is synchronized (via NTP, NITZ or GNSS).

After 03.27.07.Rev:364 firmware for FMX125 we added a feature to set camera time, same as device selecting time.

[[File:Zone.jpg|alt=|frameless]]

'''NOTE''':

That after changes of the time it can be that you can receive files which the old-time or just do not have any video/photo on this periodical time then you change time, but then it will be back to normal work.

Time zone changes the inside clock of the camera, not only the OSD displayed time but all recordings will be done according to that.

For example, if you request a video from, say, 9:00 AM GMT+0, and the camera time is GMT+0 (matches our device's time), it is all fine. But if you were to configure time zone later to, for instance, GMT+10, the camera time will be set according to that time zone (time forwarded by 10 hours in this case). Which means that time gets forwarded with no real continuation as the camera does not understand the concept of time zones, it just uses time that we set. For continuation reasons in our device, we continue using GMT+0 in the camreq and then compensate with time zone if needed. The result of that, if we send the same request command as before (when requesting 9:00 AM video) with time zone GMT+10 set, the camera will receive video request for 7 PM (19:00) and the videos were not recorded at that time which will result in "file doesn't exist".
 

== Camera control using DOUT1 ==
'''It is possible to control the camera ON/OFF state using DOUT1 control in the "Features" selections.''' In order to achieve

this functionality, please see the connection diagram located in the [[First Start#Connection of Dualcam to vehicle via DOUT1|First start]] page.

[[File:DOUt_control1.jpg|left]]

DOUT 1 Output Type has selections of either normal or inverted. Selecting inverted will make the dualcam turn on when the DOUT1 state will be 0 and turn off the the state changes to 1 and vice versa. This is recommended as inverted selection will turn on the camera upon turning on you FMx device. When 'Normal' is selected, you will need to send an SMS message to the device requesting to turn on DOUT1 every time '''IF DOUT control via ignition''' is not turned on.

'''Dout control via ignition''' stands for controlling DOUT when the ignition turns on, this setting can be chosen instead of Inverted dout. Please make sure ignition settings in the 'System' tab is correctly set and the device will turn on when the ignition of the vehicle is on. '''Ignition Off Timeout''' is a specified amount of seconds which the device will wait after ignition turns off before turning the device off. If the ignition comes back within the specified timeframe, timeout will turn off and the camera will not be turned off.

'''DOUT deactivation via DIN''' turns of Dualcam when the state of DIN1 changes. This can be set with a button which when pressed will disable DOUT1 thus ensuring camera has no power.

DOUT control can also be set using sms command such as '''setdigout'''.

''"'''setdigout # Y1 Z1'''"'' The complete setdigout command structure, listed below is explanation:

<nowiki>#</nowiki> – 0; 1 or ? (0 - OFF, 1 – ON, ? - Ignore) for DOUT1.

Y1 – timeout value for DOUT1 if needed (in seconds).

Z1 – maximum speed value for DOUT1 if needed.

===Crash Detection Functionality using DOUT1===

'''The crash detection feature''' is a crucial capability provided by our device. It enhances evidential documentation through video or photo evidence in the event of a crash. However, '''activating this functionality necessitates a direct connection of the camera to a power source.''' Nonetheless, such a direct connection can lead to '''battery drainage'''.

To circumvent this issue, we recommend utilizing DOUT and a relay for connection. This setup enables control via SMS or GPRS command, or through predefined scenarios within our device. By activating DOUT post-ignition, the camera receives power, allowing it to function and record evidence even after the ignition is turned off following a crash. '''For your convenience, the connection scheme can be found here: [link].'''

'''It is important to note that in the event of a fatal crash where fatalities may occur,''' we cannot guarantee the retrieval of video or photo evidence due to the severity of the accident. Moreover, both the camera and the device itself may sustain irreparable damage in such instances

==Other camera related functionality==
Camera is configured if all of these conditions are met:

#'''RS232 mode is selected (DualCam)'''
#'''Camera was not configured since startup or one of the related parameters were changed (compression, framerate or OSD)'''
#'''Camera file transfer is not active'''

Active camera reconfiguration is accompanied by two consecutive camera shutter clicks.
If camera is disconnected and later reconnected, a device will detect it by periodic camera ping packet. Once camera is detected, the device will reissue the reconfiguration procedure.
 

[[Category:Teltonika DualCam]]

DualCam Configuration

2024-04-09T10:39:30Z

Maksim.jefisov:

==FMX125/225 configuration==

*Please make sure to download the latest DualCam FW version. The latest FWs can be downloaded from the following Wiki page — [[DualCam Firmware errata]]

*It is necessary to change '''Data Protocol''' to [[Codec#Codec_8_Extended | Codec 8 Extended]]

[[Image:Data_protocol.gif|300px]]

*Make sure to change '''I/O''' Camera state '''Priorities''' to ''Low''
'''
[[File:Io.gif|500px]]
'''

*In '''RS232\RS485''' settings change '''Mode''' to ''RS232'' and in '''RS232 Mode''' select ''DualCam''
[[File:232.gif|500px]]

*'''Do not forget''' to configure ''DualCam'' server information. In '''RS232\RS485''' fill in '''DualCam Server Settings''' with ''Domain'' and ''Port'' entries.
[[File:Dualcamserver.png|600px]]

==FMC650 DualCam Configuration==

'''(!) Required firmware version - 03.00.14.Rev.114'''. [[DualCam Firmware errata|Firmware errata.]]

*Make sure '''Data Protocol''' is set to [[Codec#Codec_8_Extended | Codec 8 Extended]]

[[Image:Data_protocol.gif|300px]]

*In ''RS232 \ RS485 settings tab'', make sure to enable '''Camera interface''' by "Enable", and select '''DualCam''' in the Mode drop-down menu, afterwards '''DualCam COM1''' and '''Camera I/O''' should appear in the tab list.

[[Image:DualCam config.gif|600px]]

*Make sure to change '''Camera I/O''' camera state '''Priorities''' to ''Low''
'''
[[File:DualCam IO FMC650.gif|500px]]
'''

*In appeared ''DualCam COM1'' tab, make sure to '''configure everything by your needs''', and do not forget to complete the '''"Domain"''' and '''"Port"''' settings in ''"DualCam" Scenario Settings''

[[File:DualCam COM1.png|500px]]

*'''''NOTE:''''' ''This is a base setup for the device to work properly. Other device configuration is made according to your needs.

*'''''NOTE:''''' ''There are different settings for picture quality and compression, these settings will affect picture/video sizes and upload speeds. For more information about transfer sizes and timings, please visit our [[Camera_Manual#DualCam_data_transfer_timing | DualCam Data Transfer Timing]] section

===Connecting two cameras simultaneously for FMx650===
------------------
The new feature for FMx650 DualCam configuration, which is available from '''03.00.14.Rev.114 iCamera''' allows you to connect two of your cameras at once. Method for connection and configuration stays the same, for this you are only required to choose '''two''' cameras in '''"RS232 \ RS485"''' tab from the configurator.

In the new functionality, you can connect any combo of the cameras by your wish, as an example: you are able to connect ''DSM/Dualcam'', ''DashCam/DualCam'', ''DSM/DSM'', ''DualCam/DualCam'' etc.

[[File:Twincamera.gif|500px]]

==Camera Scenario Mode==

The options On Ignition and Always determine the working mode.

'''On Ignition''' means the camera scenarios will operate the way it was up to '''03.27.03.Rev.105''', that is it will work only when the ignition is detected.

'''Always''' mode means the camera scenarios will work all the time, including whenever the device is in sleep mode (excepting Ultra sleep mode during which scenario is disabled). During sleep footage requests (if the network is available), periodic image sending and triggers work as well.

'''Warning:''' using Always mode, depending on the configuration, the device might wake up from sleep very frequently. That has to be taken into consideration when configuring the scenarios.

==Periodic image sending scenario==
Periodic image sending triggers photo capture from a front camera, whenever the timeout is reached (sending interval parameter).

'''Update: Since 03.27.03.Rev.04 firmware''', Periodic Image Sending Enable/Disable switch was replaced by a camera selection:
* Both cameras deselected – periodic image sending is disabled (value 0)
* Front camera selected – front camera’s pictures will be sent periodically (value 1)
* Rear camera selected – rear camera’s pictures will be sent periodically (value 2)
* Both cameras selected – both cameras’ pictures will be sent periodically (value 3)
If the camera has not finished uploading pictures to the server, then the photo capture is skipped.

==File Transfer priority==
Filet transfer priority allows changing the priority of the specific type (photo or video) when both types are ready at once. The file transfer priority can be the following:
<ul>
<li>Picture — the photo type of files will be prioritized. </li>
<li>Video — the video type of files will be prioritized. </li>
<li>Alternating — the priority will be changing from picture to video and vice versa after each file transmission. </li>
</ul>
[[File:filetransferpriority.gif|500px]]

==Camera RTC synchronization==
Camera RTC synchronization is done anytime the device itself is synchronized (via NTP, NITZ or GNSS).

After 03.27.07.Rev:364 firmware for FMX125 we added a feature to set camera time, same as device selecting time.

[[File:Zone.jpg|alt=|frameless]]

'''NOTE''':

That after changes of the time it can be that you can receive files which the old-time or just do not have any video/photo on this periodical time then you change time, but then it will be back to normal work.

Time zone changes the inside clock of the camera, not only the OSD displayed time but all recordings will be done according to that.

For example, if you request a video from, say, 9:00 AM GMT+0, and the camera time is GMT+0 (matches our device's time), it is all fine. But if you were to configure time zone later to, for instance, GMT+10, the camera time will be set according to that time zone (time forwarded by 10 hours in this case). Which means that time gets forwarded with no real continuation as the camera does not understand the concept of time zones, it just uses time that we set. For continuation reasons in our device, we continue using GMT+0 in the camreq and then compensate with time zone if needed. The result of that, if we send the same request command as before (when requesting 9:00 AM video) with time zone GMT+10 set, the camera will receive video request for 7 PM (19:00) and the videos were not recorded at that time which will result in "file doesn't exist".
 

== Camera control using DOUT1 ==
'''It is possible to control the camera ON/OFF state using DOUT1 control in the "Features" selections.''' In order to achieve

this functionality, please see the connection diagram located in the [[First Start#Connection of Dualcam to vehicle via DOUT1|First start]] page.

[[File:DOUt_control1.jpg|left]]

DOUT 1 Output Type has selections of either normal or inverted. Selecting inverted will make the dualcam turn on when the DOUT1 state will be 0 and turn off the the state changes to 1 and vice versa. This is recommended as inverted selection will turn on the camera upon turning on you FMx device. When 'Normal' is selected, you will need to send an SMS message to the device requesting to turn on DOUT1 every time '''IF DOUT control via ignition''' is not turned on.

'''Dout control via ignition''' stands for controlling DOUT when the ignition turns on, this setting can be chosen instead of Inverted dout. Please make sure ignition settings in the 'System' tab is correctly set and the device will turn on when the ignition of the vehicle is on. '''Ignition Off Timeout''' is a specified amount of seconds which the device will wait after ignition turns off before turning the device off. If the ignition comes back within the specified timeframe, timeout will turn off and the camera will not be turned off.

'''DOUT deactivation via DIN''' turns of Dualcam when the state of DIN1 changes. This can be set with a button which when pressed will disable DOUT1 thus ensuring camera has no power.

DOUT control can also be set using sms command such as '''setdigout'''.

''"'''setdigout # Y1 Z1'''"'' The complete setdigout command structure, listed below is explanation:

<nowiki>#</nowiki> – 0; 1 or ? (0 - OFF, 1 – ON, ? - Ignore) for DOUT1.

Y1 – timeout value for DOUT1 if needed (in seconds).

Z1 – maximum speed value for DOUT1 if needed.

===Crash Detection Functionality using DOUT1===

The crash detection feature is a crucial capability provided by our device. It enhances evidential documentation through video or photo evidence in the event of a crash. However, activating this functionality necessitates a direct connection of the camera to a power source. Nonetheless, such a direct connection can lead to battery drainage.
To circumvent this issue, we recommend utilizing DOUT and a relay for connection. This setup enables control via SMS or GPRS command, or through predefined scenarios within our device. By activating DOUT post-ignition, the camera receives power, allowing it to function and record evidence even after the ignition is turned off following a crash. For your convenience, the connection scheme can be found here: [link].
It's important to note that in the event of a fatal crash where fatalities may occur, we cannot guarantee the retrieval of video or photo evidence due to the severity of the accident. Moreover, both the camera and the device itself may sustain irreparable damage in such instances

==Other camera related functionality==
Camera is configured if all of these conditions are met:

#'''RS232 mode is selected (DualCam)'''
#'''Camera was not configured since startup or one of the related parameters were changed (compression, framerate or OSD)'''
#'''Camera file transfer is not active'''

Active camera reconfiguration is accompanied by two consecutive camera shutter clicks.
If camera is disconnected and later reconnected, a device will detect it by periodic camera ping packet. Once camera is detected, the device will reissue the reconfiguration procedure.
 

[[Category:Teltonika DualCam]]