299
edits
Changes
→ADAS configuration for FMx650
==FMx640 Configuration==
==FMx640 Configuration==
'''It is important to note that ONLY specific ADAS cameras starting with the Serial Number S/N: 9C can be connected and used with FMX640 devices. Cameras starting with different S/N numbers for example; 9B, are currently only supported by FMX125/225 devices.''' However, upon receipt of the cameras, if the S/N number starts with 9B, check whether there is a red circle sticker on the camera as shown in the picture below. If there is, please connect the camera to the computer, install the required drivers and visit IP 10.0.0.1 on the browser. In the further window, details about the camera is displayed where the actual S/N number of the camera will start with 9C meaning that the camera is compatible with FMX640 devices. This is due to the serial numbers being pre-attached to the camera case from the manufacturer and is kept the same for warranty purposes.
'''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]]
[[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'''
'''Device Configuration'''
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.
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.
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.
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.
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.
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: <b>GPS, CAN adapter (CAN adapter can be connected with the help of ECAN-02), FMS or K-Line</b>. Once you select one of these options, it will be used as the source for your speed information.
If you choose to use the "Speed" overlay, you will have four different options to choose from: <b>GPS, CAN adapter, FMS or K-Line</b>. 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 <b>1000 ms</b>
'''Garbage collector'''
'''Garbage collector'''
[[File:ADAS-settings13.png|alt=|frameless|400px]]
[[File:ADAS-settings13.png|alt=|frameless|400px]]
ADAS system can save files inside of itself or FMX640 device if 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 microSD card allowing it efficiently operate for longer periods of time.
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'''
'''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 to their server. Selecting priority will also allow the users to receive specific ADAS functionalities and ignore the ones they do not need.
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]]
[[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==
==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 new ADAS IO section was created.
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).
In order for ADAS functionality to work „ADAS Camera“ RS232 mode has to be selected (151 parameter ID, value 21).
[[File:Adas232set.png|center|frameless|300x300px]]
[[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 differnet features which they would like to receive to their server. Selecting priority will also allow the users to receive specific ADAS functionalities and ignore the ones they do not need.
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]]
[[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]]
[[Category: Teltonika ADAS]]