Template:FMB6 Mobileye - Revision history

Jonas.sterbavicius at 07:39, 10 March 2023

2023-03-10T07:39:41Z

← Older revision		Revision as of 10:39, 10 March 2023
Line 14:		Line 14:
	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:{{{model\|FMB6YX}}-Mobileye-scheme.png\|800x800px]]		[[File:{{{model\|FMB6YX}}}-Mobileye-scheme.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}}} CAN1 connection with Mobileye 5 “EyeCAN” port. <br> <br>		{{{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}}} CAN1 connection with Mobileye 5 “EyeCAN” port. <br> <br>

Jonas.sterbavicius at 07:35, 10 March 2023

2023-03-10T07:35:56Z

← Older revision		Revision as of 10:35, 10 March 2023
Line 14:		Line 14:
	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:Mobileye-scheme ~~(2)~~.png\|800x800px]]		[[File:{{{model\|FMB6YX}}-Mobileye-scheme.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}}} CAN1 connection with Mobileye 5 “EyeCAN” port. <br> <br>		{{{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}}} CAN1 connection with Mobileye 5 “EyeCAN” port. <br> <br>

Jonas.sterbavicius: /* Physical connection to Mobileye 5 CAN-A port */

2023-03-10T07:18:25Z

Physical connection to Mobileye 5 CAN-A port

← Older revision		Revision as of 10:18, 10 March 2023
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:~~Asset 1 v1~~.png\|600x600px]]		<br />[[File:Fmm 650 2x10 pinout.png\|600x600px]]

Jonas.sterbavicius at 07:06, 10 March 2023

2023-03-10T07:06:50Z

← Older revision		Revision as of 10:06, 10 March 2023
Line 26:		Line 26:

	Users must select [[Codec#Codec 8 Extended\|Codec8 Extended]] data type in order to get Mobileye data packets to the server because [[{{{model\|FMB6YX}}} Teltonika Data Sending Parameters 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 [[{{{model\|FMB6YX}}} System settings\|System tab]], Protocol Settings.		Users must select [[Codec#Codec 8 Extended\|Codec8 Extended]] data type in order to get Mobileye data packets to the server because [[{{{model\|FMB6YX}}} Teltonika Data Sending Parameters 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 [[{{{model\|FMB6YX}}} System settings\|System tab]], Protocol Settings.
	When [[Codec#Codec 8 Extended\|Codec8 Extended]] type is selected [[{{{model\|FMB6YX}}} ~~Teltonika Data Sending Parameters~~ ID#Mobileye elements\|Mobileye I/O]] elements could be selected.		When [[Codec#Codec 8 Extended\|Codec8 Extended]] type is selected [[{{{model\|FMB6YX}}} 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 [[{{{model\|FMB6YX}}} ~~AVL ID~~#~~Permanent I~~.~~2FO elements~~\|{{{model\|FMB6YX}}} I/O]] elements. <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 [[{{{model\|FMB6YX}}} Teltonika_Data_Sending_Parameters_ID#Permanent_I.2FO_elements\|{{{model\|FMB6YX}}} I/O]] elements. <br>
	[[File:FMB640 Mobileye IO elements v1.png\|800x800px]]<br>		[[File:FMB640 Mobileye IO elements v1.png\|800x800px]]<br>

Jonas.sterbavicius: /* {{{model|FMB6YX}}} device configuration */

2023-03-10T07:02:15Z

{{{model|FMB6YX}}} device configuration

← Older revision		Revision as of 10:02, 10 March 2023
Line 26:		Line 26:

	Users must select [[Codec#Codec 8 Extended\|Codec8 Extended]] data type in order to get Mobileye data packets to the server because [[{{{model\|FMB6YX}}} Teltonika Data Sending Parameters 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 [[{{{model\|FMB6YX}}} System settings\|System tab]], Protocol Settings.		Users must select [[Codec#Codec 8 Extended\|Codec8 Extended]] data type in order to get Mobileye data packets to the server because [[{{{model\|FMB6YX}}} Teltonika Data Sending Parameters 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 [[{{{model\|FMB6YX}}} System settings\|System tab]], Protocol Settings.
	When [[Codec#Codec 8 Extended\|Codec8 Extended]] type is selected [[{{{model\|FMB6YX}}} ~~AVL~~ ID#Mobileye elements\|Mobileye I/O]] elements could be selected.		When [[Codec#Codec 8 Extended\|Codec8 Extended]] type is selected [[{{{model\|FMB6YX}}} Teltonika Data Sending Parameters ID#Mobileye elements\|Mobileye I/O]] elements could be selected.

	<br>[[File:FMB640 Codec8Extended tab 1.png]]		<br>[[File:FMB640 Codec8Extended tab 1.png]]

Jonas.sterbavicius at 07:00, 10 March 2023

2023-03-10T07:00:04Z

← Older revision		Revision as of 10:00, 10 March 2023
Line 25:		Line 25:


	Users must select [[Codec#Codec 8 Extended\|Codec8 Extended]] data type in order to get Mobileye data packets to the server because [[{{{model\|FMB6YX}}} ~~Teltonika_Data_Sending_Parameters_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 [[{{{model\|FMB6YX}}} System settings\|System tab]], Protocol Settings.		Users must select [[Codec#Codec 8 Extended\|Codec8 Extended]] data type in order to get Mobileye data packets to the server because [[{{{model\|FMB6YX}}} Teltonika Data Sending Parameters 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 [[{{{model\|FMB6YX}}} System settings\|System tab]], Protocol Settings.
	When [[Codec#Codec 8 Extended\|Codec8 Extended]] type is selected [[{{{model\|FMB6YX}}} AVL ID#Mobileye elements\|Mobileye I/O]] elements could be selected.		When [[Codec#Codec 8 Extended\|Codec8 Extended]] type is selected [[{{{model\|FMB6YX}}} AVL ID#Mobileye elements\|Mobileye I/O]] elements could be selected.

Jonas.sterbavicius: /* {{{model|FMB6YX}}} device configuration */

2023-03-10T06:56:19Z

{{{model|FMB6YX}}} device configuration

← Older revision		Revision as of 09:56, 10 March 2023
Line 25:		Line 25:


	Users must select [[Codec#Codec 8 Extended\|Codec8 Extended]] data type in order to get Mobileye data packets to the server because [[{{{model\|FMB6YX}}} ~~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 [[{{{model\|FMB6YX}}} System settings\|System tab]], Protocol Settings.		Users must select [[Codec#Codec 8 Extended\|Codec8 Extended]] data type in order to get Mobileye data packets to the server because [[{{{model\|FMB6YX}}} Teltonika_Data_Sending_Parameters_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 [[{{{model\|FMB6YX}}} System settings\|System tab]], Protocol Settings.
	When [[Codec#Codec 8 Extended\|Codec8 Extended]] type is selected [[{{{model\|FMB6YX}}} AVL ID#Mobileye elements\|Mobileye I/O]] elements could be selected.		When [[Codec#Codec 8 Extended\|Codec8 Extended]] type is selected [[{{{model\|FMB6YX}}} AVL ID#Mobileye elements\|Mobileye I/O]] elements could be selected.

Jonas.sterbavicius at 06:52, 10 March 2023

2023-03-10T06:52:35Z

Tomas.kriauciunas at 07:52, 23 April 2021

2021-04-23T07:52:29Z

← Older revision		Revision as of 10:52, 23 April 2021
Line 22:		Line 22:
	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.		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>[[~~File~~:FMB640 mobileye boudrate.gif~~\|800x800px~~]]		<br>[[image:FMB640 mobileye boudrate.gif]]

Tomas.kriauciunas at 07:51, 23 April 2021

2021-04-23T07:51:41Z

← Older revision		Revision as of 10:51, 23 April 2021
Line 22:		Line 22:
	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.		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>[[File:FMB640 boudrate.~~png~~\|800x800px]]		<br>[[File:FMB640 mobileye boudrate.gif\|800x800px]]

← Older revision		Revision as of 10:39, 10 March 2023
Line 14:		Line 14:
	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:{{{model\|FMB6YX}}-Mobileye-scheme.png\|800x800px]]		[[File:{{{model\|FMB6YX}}}-Mobileye-scheme.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}}} CAN1 connection with Mobileye 5 “EyeCAN” port. <br> <br>		{{{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}}} CAN1 connection with Mobileye 5 “EyeCAN” port. <br> <br>

← Older revision		Revision as of 10:35, 10 March 2023
Line 14:		Line 14:
	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:Mobileye-scheme ~~(2)~~.png\|800x800px]]		[[File:{{{model\|FMB6YX}}-Mobileye-scheme.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}}} CAN1 connection with Mobileye 5 “EyeCAN” port. <br> <br>		{{{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}}} CAN1 connection with Mobileye 5 “EyeCAN” port. <br> <br>

← Older revision		Revision as of 09:52, 10 March 2023
Line 16:		Line 16:
	[[File:Mobileye-scheme (2).png\|800x800px]]		[[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 ~~FMB64~~ CAN1 connection with Mobileye 5 “EyeCAN” port. <br> <br>		{{{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}}} 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==		=={{{model\|FMB6YX}}} 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 [[~~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.		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 [[{{{model\|FMB6YX}}} 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>[[image:FMB640 mobileye boudrate.gif]]		<br>[[image:FMB640 mobileye boudrate.gif]]


	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.		Users must select [[Codec#Codec 8 Extended\|Codec8 Extended]] data type in order to get Mobileye data packets to the server because [[{{{model\|FMB6YX}}} 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 [[{{{model\|FMB6YX}}} System settings\|System tab]], Protocol Settings.
	When [[Codec#Codec 8 Extended\|Codec8 Extended]] type is selected [[~~FMB640~~ AVL ID#Mobileye elements\|Mobileye I/O]] elements could be selected.		When [[Codec#Codec 8 Extended\|Codec8 Extended]] type is selected [[{{{model\|FMB6YX}}} 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 [[~~FMB640~~ AVL ID#Permanent I.2FO elements\|~~FMB640~~ I/O]] elements. <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 [[{{{model\|FMB6YX}}} AVL ID#Permanent I.2FO elements\|{{{model\|FMB6YX}}} I/O]] elements. <br>
	[[File:FMB640 Mobileye IO elements v1.png\|800x800px]]<br>		[[File:FMB640 Mobileye IO elements v1.png\|800x800px]]<br>