Difference between revisions of "Template:FMB6 Mobileye"
m |
(Undo revision 64895 by Kriauciunas.to (talk)) Tag: Undo |
||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 9: | Line 9: | ||
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. {{{model|FMB6YX}}} devices use CAN1 by default configuration for Mobileye and FM communications. | 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. {{{model|FMB6YX}}} devices use CAN1 by default configuration for Mobileye and FM communications. | ||
| − | <br />[[File: | + | <br />[[File:Asset 1 v1.png|600x600px]] |
You need to connect this CAN bus interface to Mobileye CAN-A channel dedicated CAN bus interface for {{{model|FMB6YX}}}. 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. | You need to connect this CAN bus interface to Mobileye CAN-A channel dedicated CAN bus interface for {{{model|FMB6YX}}}. 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. | ||
| − | [[File: | + | [[File:Mobileye-scheme (2).png|800x800px]] |
| − | {{{model|FMB6YX}}} 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 {{{model|FMB6YX}}}) are not supplied. This connection cable should be provided for | + | {{{model|FMB6YX}}} 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 {{{model|FMB6YX}}}) 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 {{{model|FMB6YX}}} CAN2 H and CAN2 L. | '''Note:''' CAN-A Male connector also can be connected with {{{model|FMB6YX}}} CAN2 H and CAN2 L. | ||
| − | == | + | ==FMB640 device configuration== |
| − | Mobileye and {{{model|FMB6YX}}} devices communicate through the CAN bus. {{{model|FMB6YX}}} 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 [[ | + | Mobileye and {{{model|FMB6YX}}} devices communicate through the CAN bus. {{{model|FMB6YX}}} 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 [[FMB640 CAN \ Tachograph|CAN\Tachograph tab]], CAN1 Bus Settings, select 500 kbps CAN1 bus speed (kbps). Also, in CAN1 bus mode please select the "Normal" option. |
| − | <br>[[ | + | <br>[[File:FMB640 boudrate.png|800x800px]] |
| − | Users must select [[Codec#Codec 8 Extended|Codec8 Extended]] data type in order to get Mobileye data packets to the server because [[ | + | Users must select [[Codec#Codec 8 Extended|Codec8 Extended]] data type in order to get Mobileye data packets to the server because [[FMB640 AVL ID#Mobileye elements|Mobileye I/O AVL ID]]’s are over than 255. This is because of [[Codec#Codec 8 Extended|Codec8 Extended]] can sent 2 bytes data of AVL ID while [[Codec#Codec 8|Codec8]] – 1 byte. This parameter is located in configurator [[FMB640 System settings|System tab]], Protocol Settings. |
| − | When [[Codec#Codec 8 Extended|Codec8 Extended]] type is selected [[ | + | When [[Codec#Codec 8 Extended|Codec8 Extended]] type is selected [[FMB640 AVL ID#Mobileye elements|Mobileye I/O]] elements could be selected. |
<br>[[File:FMB640 Codec8Extended tab 1.png]] | <br>[[File:FMB640 Codec8Extended tab 1.png]] | ||
| Line 32: | Line 32: | ||
'''Note:''' Mobileye data will be sent together with periodical AVL records. <br> <br> | '''Note:''' Mobileye data will be sent together with periodical AVL records. <br> <br> | ||
| − | '''Note:''' ME TSR IO elements are not parsed in {{{model|FMB6YX}}} device, they must be parsed according to Mobileye documentation, because {{{model|FMB6YX}}} 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 [[ | + | '''Note:''' ME TSR IO elements are not parsed in {{{model|FMB6YX}}} device, they must be parsed according to Mobileye documentation, because {{{model|FMB6YX}}} 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 [[FMB640 AVL ID#Permanent I.2FO elements|FMB640 I/O]] elements. <br> |
[[File:FMB640 Mobileye IO elements v1.png|800x800px]]<br> | [[File:FMB640 Mobileye IO elements v1.png|800x800px]]<br> | ||
Revision as of 09:51, 23 April 2021
Pages with broken file links > Template:FMB6 MobileyeIntroduction
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.
FMB6YX 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 FMB6YX correctly. This document describes how to connect FMB6YX 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. FMB6YX devices use CAN1 by default configuration for Mobileye and FM communications.
You need to connect this CAN bus interface to Mobileye CAN-A channel dedicated CAN bus interface for FMB6YX. 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.
.png)
FMB6YX 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 FMB6YX) are not supplied. This connection cable should be provided for FMB64 CAN1 connection with Mobileye 5 “EyeCAN” port.
Note: CAN-A Male connector also can be connected with FMB6YX CAN2 H and CAN2 L.
FMB640 device configuration
Mobileye and FMB6YX devices communicate through the CAN bus. FMB6YX 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.
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.
Note: Mobileye data will be sent together with periodical AVL records.
Note: ME TSR IO elements are not parsed in FMB6YX device, they must be parsed according to Mobileye documentation, because FMB6YX 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 FMB640 I/O elements.
