Difference between revisions of "ADAS Configuration"
MindaugasK (talk | contribs) |
|||
| (18 intermediate revisions by 3 users not shown) | |||
| Line 2: | Line 2: | ||
==FMx640 Configuration== | ==FMx640 Configuration== | ||
| + | '''Spec ID Firmware Requirement for FMX640 + ADAS''' | ||
| − | '''It is important to note that ADAS cameras with Serial | + | '''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. |
| − | |||
| − | |||
[[File:ADAS 9B sticker.png | 250px]] | [[File:ADAS 9B sticker.png | 250px]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
'''Device Configuration''' | '''Device Configuration''' | ||
| Line 29: | Line 22: | ||
In RS232/RS485 settings enable ADAS under RS232 mode in order for the configurator to open additional settings for ADAS accessory. | 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.''' | + | '''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 to update the camera through the SD card to version 0.95 or later.''' |
[[File:ADASbaud2.png|alt=|frameless|500px]] | [[File:ADASbaud2.png|alt=|frameless|500px]] | ||
| Line 100: | Line 93: | ||
Re-Alert setting gives warning if the same vehicle in the front gets too close every time. | Re-Alert setting gives warning if the same vehicle in the front gets too close every time. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
'''Pedestrian collision warning PCW''' | '''Pedestrian collision warning PCW''' | ||
| Line 144: | Line 120: | ||
[[File:ADAS-settings11.png|alt=|frameless|400px]] | [[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 | + | 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 same server but different port. |
| − | Periodic image | + | Periodic image sending functionality is also available with configurable sending interval. |
| − | Image and Video sending can also be triggered by different inputs such as | + | Image and Video sending can also be triggered by different inputs such as DIN's for photo's 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. | Video duration can also be configured before and after the trigger event. | ||
| Line 160: | Line 136: | ||
Available information to display can be chosen between "Date and time", "GPS information" and "Speed". | Available information to display can be chosen between "Date and time", "GPS information" and "Speed". | ||
| − | GPS information can have | + | GPS information can have configurable update period which can be specified by the user allowing the device to use more or less network resources. |
| − | |||
| − | |||
| − | |||
| − | |||
'''Garbage collector''' | '''Garbage collector''' | ||
| Line 170: | Line 142: | ||
[[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 | + | 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 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 | + | 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. |
[[File:Adas conf2.png|center|frameless|1000x1000px]] | [[File:Adas conf2.png|center|frameless|1000x1000px]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==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 | + | 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. |
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). | ||
| Line 226: | Line 166: | ||
[[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 | + | 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. |
[[File:Adasconf1.png|center|frameless|1000x1000px]] | [[File:Adasconf1.png|center|frameless|1000x1000px]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category: Teltonika ADAS]] | [[Category: Teltonika ADAS]] | ||
Revision as of 11:39, 15 November 2022
Main Page > Video Solutions > DSM > ADAS ConfigurationFMx640 Configuration
Spec ID Firmware Requirement for FMX640 + ADAS
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.
Device Configuration
It is necessary to change Data Protocol to Codec 8 Extended
Configure the Domain and Port to send the data to the desired server.
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 to update the camera through the SD card to version 0.95 or later.
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
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
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
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
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
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
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
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.
Pedestrian collision warning PCW
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
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
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 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 same server but different port.
Periodic image sending functionality is also available with configurable sending interval.
Image and Video sending can also be triggered by different inputs such as DIN's for photo's 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
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 configurable update period which can be specified by the user allowing the device to use more or less network resources.
Garbage collector
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 IO
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.
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.
In order for ADAS functionality to work „ADAS Camera“ RS232 mode has to be selected (151 parameter ID, value 21).
Note:
1) Please use Codec08 extended protocol with ADAS functionality
2) RS232 baudrate should be configured 115200 bps
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.
