2,556
edits
Changes
no edit summary
FMB640 devices supports Mobileye data. This data could be sent to server as other AVLelements. In order to do that you need to connect and set configuration for FMB640 correctly. This document describes how to connect FMB64 device to Mobileye unit.
== Introduction ==
The Mobileye is a vision sensor that helps keep drivers and others traffic participants safe. To communicate between sensors and drivers are using Advanced Driver Assistance System (ADAS). The sensor can view the road ahead and indicate objects like vehicles, pedestrians, cyclists, lane markings and speed limit signs. Consistently gathering of all this information is continuously calculated for potentially imminent danger. By this, the system determines to driver if there is a potential danger on the road ahead. <br>
FMB640 devices supports Mobileye data. This data could be sent to server as other AVL elements. In order to do that you need to connect and set configuration for FMB640 correctly. This document describes how to connect FMB640 device to Mobileye unit and how to configurate in Teltonika Configurator. <br> <br>
'''Note:''' there is few different Mobileye module modifications and it might not be described in this document. For more detailed information ask for Mobileye support.
== Physical connection to Mobileye 5 CAN-A port ==
in this document for more detailed information ask for Mobileye support. FMB640 devices uses
The Mobileye 5 CAN interface (CAN Bus) is located in the Main unit (SeeQ/camera). The Typical SeeQ CAN Channel dedicated for FMS Integrations and similar communication is CAN-A channel. FMB640 devices uses CAN1 by default configuration for Mobileye to FM communications. <br>
CAN1 for Mobileye to FM communications. You need to connect this CAN bus interface to
Figure 1. FMB640 20-PIN output <br>
Mobileye and FMB640 devices communicates through CAN bus. FMB640 CAN1 bus is dedicated for Mobileye to FM communication. As described in Mobileye
You need to connect this CAN bus interface to Mobileye CAN-A channel dedicated CAN bus interface for FMS units. In Mobileye 5 the CAN-A Channel is accessible for physical connection using the CAN-A Male connector, (6 Pins connector labeled “EyeCAN”) in the Mobileye 5 main harness. <br>
Figure 2. Mobileye 5 CAN-A 6 PIN male connector PIN layout <br>
FMB640 device CAN1 H signal must be connected to “EyeCAN” PIN1 and CAN1 L to PIN2. Please take a note that connectors for FMS devices (in this case FMB640) are not supplied. This connection cable should be provided for FMB64 CAN1 connection with Mobileye 5 “EyeCAN” port. <br> <br>
'''Note:''' CAN-A Male connector also can be connected with FMB640 CAN2 H and CAN2 L.
===Physical connection to Mobileye 5 CAN-A port===
== FMB640 device configuration ==
Mobileye and FMB640 devices communicate through CAN bus. FMB640 CAN1 bus is dedicated for Mobileye to FM communication. As described in Mobileye documentation, default baud rate is 500 Kbps. Using configurator, in CAN/Tachograph tab, CAN1 Bus Settings, select 500 kbps CAN1 bus speed (kbps). <br>
Figure 3. Bus speed configuration of CAN1 for Mobileye to FMB640 communication <br>
User must select Codec8 Extended data type in order to get Mobileye data packets to server because ME I/O ALV ID’s are over than 255. This is because of Codec8 Extended can sent 2 bytes data of AVL ID while Codec8 – 1 byte. This parameter is located in configurator System tab in Protocol Settings.
When Codec8 Extended type is selected Mobileye IO elements could be selected. <br>
Figure 4. Codec8 Extended parameter dropdown <br>
'''Note:''' Mobileye period affects only record saving. Mobileye records will be sent together with base AVL records. <br> <br>
'''Note:''' ME TSR IO elements are not parsed in FMB640 device, they must be parsed according to Mobileye documentation, because FMB640 will send 8 bytes size RAW data of those parameters. All other elements are already parsed and showing correct values. Simply select elements which you want to get and generation type as other FMB640 IO elements. <br>
Figure 5. Mobileye IO elements <br>
