Line 1: |
Line 1: |
| __TOC__ | | __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|FMC640}}} device. All I/O configuration is as described I/O elements} |
| | | |
| ==LVCAN== | | ==LVCAN== |
Line 7: |
Line 7: |
| 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. |
| | | |
− | [[image:FMB640 LVCANSettings.gif]] | + | [[image:FMC640 LVCANSettings.gif]] |
| | | |
| ==FMS== | | ==FMS== |
Line 17: |
Line 17: |
| 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. |
| [[image:Vehicle_Data_priority_settings.png]] | | [[image:Vehicle_Data_priority_settings.png]] |
− | [[Category:FMB640 Configuration]] | + | [[Category:FMC640 Configuration]] |
| <br> | | <br> |
| | | |
− | By defaulf, FMB640 sends Tachograph data included into regular record, but device can be configured to send Tachograph data as separate AVL packet | + | By defaulf, FMC640 sends Tachograph data included into regular record, but device can be configured to send Tachograph data as separate AVL packet |
− | [[image:FMB640_Tachograph_Settings.gif]] | + | [[image:FMC640_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 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. |
Line 33: |
Line 33: |
| ---- | | ---- |
| | | |
− | ''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|FMC640}}} device. All I/O configuration is as described I/O elements} |
| | | |
| ==LVCAN== | | ==LVCAN== |
Line 39: |
Line 39: |
| 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. |
| | | |
− | [[image:FMB640 LVCANSettings.gif]] | + | [[image:FMC640 LVCANSettings.gif]] |
| | | |
| ==FMS== | | ==FMS== |
Line 49: |
Line 49: |
| 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. |
| [[image:Vehicle_Data_priority_settings.png]] | | [[image:Vehicle_Data_priority_settings.png]] |
− | [[Category:FMB640 Configuration]] | + | [[Category:FMC640 Configuration]] |
| <br> | | <br> |
| | | |
− | By defaulf, FMB640 sends Tachograph data included into regular record, but device can be configured to send Tachograph data as separate AVL packet | + | By defaulf, FMC640 sends Tachograph data included into regular record, but device can be configured to send Tachograph data as separate AVL packet |
− | [[image:FMB640_Tachograph_Settings.gif]] | + | [[image:FMC640_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 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. |