Changes

FMB640 LVCAN I/O,FMS IO and Tachograph data elements (view source)

Revision as of 09:25, 9 September 2022

23,113 bytes added , 09:25, 9 September 2022

Line 1: Line 1: +

__TOC__

−

''LVCAN'', ''FMS IO'' and ''Tachograph data'' sections shows I/O elements that can be obtained accordingly from external devices connected to {{{model|FMB640}}} device. All I/O configuration is as described I/O elements}

+

''LVCAN'', ''FMS IO'' and ''Tachograph data'' sections shows I/O elements that can be obtained accordingly from external devices connected to {{{model|FMB640}}} device. All I/O configuration is as described [[{{{model|FMB640}}}_I/O_settings|I/O elements]].

==LVCAN==

−

LVCAN elements can be configured in same way ~~like with~~ normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command.

+

LVCAN elements can be configured in the same way as normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command.

[[image:FMB640 LVCANSettings.gif]]

Line 14: Line 15:

==Tachograph Data==

−

Tachograph data can be taken from Tachograph via K-Line, ALLCAN, Tacho CAN or FMS. Data here is constantly refreshed. As the other elements’ windows, this one also has all the options to configure event ~~generating~~.

+

Tachograph data can be taken from Tachograph via K-Line, ALLCAN, Tacho CAN, or FMS. Data here is constantly refreshed. Like the other elements’ windows, this one also has all the options to configure event generation.

[[image:Vehicle_Data_priority_settings.png]]

−

~~[[Category:FMB640 Configuration]]~~

−

By ~~defaulf~~, FMB640 sends Tachograph data included ~~into~~ regular record, but device can be configured to send Tachograph data as separate AVL packet

+

By default, FMB640 sends Tachograph data included in the regular record, but the device can be configured to send Tachograph data as a separate AVL packet

[[image:FMB640_Tachograph_Settings.gif]]

−

If Tachograph data included ~~into~~ regular record is Disabled, Tachograph periodic record timeout will define how often Tachograph Data will be sent to the server as separate AVL packet.

+

If Tachograph data included in the regular record is Disabled, Tachograph periodic record timeout will define how often Tachograph Data will be sent to the server as a separate AVL packet.

''Send data with last good value''

−

Added a feature ~~which~~ allows ~~to choose~~ to generate Tachograph data record or not depending on remembered last good value. If parameter is enabled and if there were good data values received but now no new data is ~~receiving~~, when record will be generated it will be filled with last good data values.

+

Added a feature that allows choosing to generate a Tachograph data record or not depending on remembered last good value. If the parameter is enabled and if there were good data values received but now no new data is received, when the record will be generated it will be filled with the last good data values.

−

In base version as well as in this special firmware there is a 30 seconds timeout during which Kline values are still being stored in RAM.

+

In the base version as well as in this special firmware there is a 30 seconds timeout during which Kline values are still being stored in RAM.

−

If last good value parameter is disabled and good data stopped streaming, data will still be available for 30 seconds.

+

If the last good value parameter is disabled and good data stopped streaming, data will still be available for 30 seconds.

−

Tachograph data parameters ~~which~~ support different communications:

+

===Tachograph Counter related elements===

+

Newly added IO elements (AVL ID 10504-10517 and 10522-10531 from 01.02.12 firmware version) include data reading from the Tachograph Counter functionality – displaying daily/weekly remaining driving and rest times on the tachograph menu.

+

Note that these parameters can be optional on your tachograph - meaning that by default not all the tachographs have this feature enabled/supported from the factory.

+

For example – VDO DTCO tachographs support the Counter functionality from version 2.0, however in OEM tachograph versions – non-universal tachographs – meant specifically for truck manufacturers i.e. Mercedes/DAF – Counter functionality can be disabled from the factory.

+

'''In order to properly read these IO elements with FMX640 – Counter functionality has to be enabled.'''

+

VDO DTCO 2.1 tachograph can be updated via “DTCO VDO Counter Update Card” – '''P/N A2C5951660366'''

+

[[image:VDO_Counter.png]]

+

Newer DTCO versions can have the Counter functionality enabled by entering the license key provided by the manufacturer.

+

To see if new IO elements will be read from your tachograph, we recommend contacting your local workshop, specifying the tachograph part number, and following the workshop instructions if any are required.

+

Tachograph data parameters that support different communications:

----

{| class="wikitable"

|+

−

! rowspan="2" style="width:50%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |Parameter

+

! rowspan="1" style="width:50%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |Parameter

−

! rowspan="2" style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |K-Line

+

! rowspan="1" style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |K-Line

−

! rowspan="2" style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |K-Line (Front Panel)

+

! rowspan="1" style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |K-Line (Front Panel)

−

! rowspan="2" style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |ALLCAN

+

! rowspan="1" style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |ALLCAN

−

! rowspan="2" style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |TachoCAN

+

! rowspan="1" style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |TachoCAN

−

! rowspan="2" style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FMS

+

! rowspan="1" style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FMS

−

|-

−

~~! style="width:5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |~~

−

~~! style="width:5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |~~

|-

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" |Timestamp

Line 233: Line 240:

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | +

|-

+

! colspan="6" |From Firmware 01.02.12:

+

|-

+

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" |Drivers hours rules pre warning time delay

+