FMC640 Mobileye

From Wiki Knowledge Base | Teltonika GPS
Revision as of 10:12, 6 December 2019 by Sandra.Gasyte (talk | contribs) (Replaced content with "{{Template:FMB6 Mobileye | model = FMC640}} Category: FMC640 Configuration")

(diff) ← Older revision | Approved revision (diff) | Latest revision (diff) | Newer revision → (diff)
Main Page > EOL Products > FMC640 > FMC640 Configuration > FMC640 Mobileye


The Mobileye is a vision sensor that helps keep drivers and other traffic participants safe. To communicate between sensors and drivers is using the 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 the driver if there is a potential danger on the road ahead.
FMC640 devices support Mobileye data. This data could be sent to the server as other AVL elements. In order to do that, you need to connect and set the configuration for FMC640 correctly. This document describes how to connect FMC640 device to the Mobileye unit and how to configure it in Teltonika Configurator.

Note: There are 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

The Mobileye 5 CAN interface (CAN Bus) is located in the Main unit (SeeQ/camera). The Typical SeeQ CAN Channel dedicated to FMS Integrations and similar communication is the CAN-A channel. FMC640 devices use CAN1 by default configuration for Mobileye and FM communications.

Fmm 650 2x10 pinout.png

You need to connect this CAN bus interface to Mobileye CAN-A channel dedicated CAN bus interface for FMC640. In Mobileye 5 the CAN-A Channel is accessible for physical connection using the CAN-AM Male connector, (6 Pins connector labeled “EyeCAN”) in the Mobileye 5 main harness.


FMC640 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 FMC640) are not supplied. This connection cable should be provided for FMC640 CAN1 connection with Mobileye 5 “EyeCAN” port.

Note: CAN-A Male connector also can be connected with FMC640 CAN2 H and CAN2 L.

FMC640 device configuration

Mobileye and FMC640 devices communicate through the CAN bus. FMC640 CAN1 bus is dedicated to Mobileye to FM communication. As described in Mobileye documentation, the default baud rate is 500 Kbps. Using the configurator, in CAN\Tachograph tab, CAN1 Bus Settings, select 500 kbps CAN1 bus speed (kbps). Also, in CAN1 bus mode please select the "Normal" option.

FMB640 mobileye boudrate.gif

Users must select Codec8 Extended data type in order to get Mobileye data packets to the server because Mobileye I/O AVL 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, Protocol Settings. When Codec8 Extended type is selected Mobileye I/O elements could be selected.

FMB640 Codec8Extended tab 1.png

Note: Mobileye data will be sent together with periodical AVL records.

Note: ME TSR IO elements are not parsed in FMC640 device, they must be parsed according to Mobileye documentation, because FMC640 will send 8 bytes size RAW data of those parameters. All other elements are already parsed and showing correct values. Simply select elements that you want to get and generation type as other FMC640 I/O elements.
FMB640 Mobileye IO elements v1.png