Changes

Line 1: Line 1:    −
==LVCAN I/O,FMS IO and Tachograph data 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 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 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 same way like with normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command.
   −
* FMS IO
+
==FMS==
    
FMS, or Fleet Management Systems Interface, is a sector to configure and manage events based on vehicle data of commercial vehicles. Vehicle data comes through CAN lines. Event configuring isn’t different from those in LVCAN and I/O sectors. The only difference is IDs.
 
FMS, or Fleet Management Systems Interface, is a sector to configure and manage events based on vehicle data of commercial vehicles. Vehicle data comes through CAN lines. Event configuring isn’t different from those in LVCAN and I/O sectors. The only difference is IDs.
   −
* Tachograph data
+
==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. As the other elements’ windows, this one also has all the options to configure event generating.