0
edits
Changes
mLine 82:
Line 82: − + + + Line 118:
Line 120: + + + + + + + + + + + +
→FMB120 ALL-CAN300 and LV-CAN200 parameters configuration
==FMB120 ALL-CAN300 and LV-CAN200 parameters configuration==
==FMB120 ALL-CAN300 and LV-CAN200 parameters configuration==
Because FMB120 have LV-CAN200/ALL-CAN300 RX and TX in its own pinout device configuration can be performed via micro-USB when CAN adapter are connected in vehicle.<br/>When FMB120 are connected to configurator and at the same moment to LV-CAN200 or ALL-CAN300, in configurator LVCAN section user can see all information that is received from vehicle, that data are marked with green background color. Information in this section is automaticali refreshed. CAN bus data which can be read from your car is shown in “Light or ALL Vehicles Can adapter supported cars” document.<br/>The LVCAN I/O element can be configured like any other I/O element in FMB120 configurator.<br/>When using offline configuration metod user can select which CAN data will be red from LV-CAN200 or ALL-CAN300 and directly sent to server without connection to adapter. Please note that parameters depend on vehicle manufacturer and vehicle model. Please for further information check “Light and All Vehicles Can adapter supported cars” document.<br/>All information about I/O element parameters description is in section [[FMB120 I/O settings|I/O settings]].<br/>All LV-CAN200/ALL-CAN300 I/O parameters configuration settings are described in “FMB120 Protocols” document, except ALL-CAN300 bitmasks, they are described in the table below.
Because FMB120 have LV-CAN200/ALL-CAN300 RX and TX in its own pinout device configuration can be performed via micro-USB when CAN adapter are connected in vehicle.<br/>When FMB120 are connected to configurator and at the same moment to LV-CAN200 or ALL-CAN300, in configurator LVCAN section user can see all information that is received from vehicle, that data are marked with green background color. Information in this section is automaticali refreshed. CAN bus data which can be read from your car is shown in “Light or ALL Vehicles Can adapter supported cars” document.<br/>The LVCAN I/O element can be configured like any other I/O element in FMB120 configurator.
[[Image:Fmb120_can_conf_example.png|800px|centre]]
[[Image:Fmb120_can_conf_example.png|800px|centre]]
When using offline configuration method user can select which CAN data will be red from LV-CAN200 or ALL-CAN300 and directly sent to server without connection to adapter. Please note that parameters depend on vehicle manufacturer and vehicle model. Please for further information check “Light and All Vehicles Can adapter supported cars” document.<br/>All information about I/O element parameters description is in section [[FMB120 I/O settings|I/O settings]].<br/>All LV-CAN200/ALL-CAN300 I/O parameters configuration settings are described in “FMB120 Protocols” document, except ALL-CAN300 bitmasks, they are described in the table below.
{| class="wikitable"
{| class="wikitable"
Byte4:<br/><span style=color:#9DCD00>0x01</span> – Car was closed by the factory's remote control<br/><span style=color:#9DCD00>0x02</span> – Car was opened by the factory's remote control<br/><span style=color:#9DCD00>0x03?</span> – Trunk cover was opened by the factory's remote control<br/><span style=color:#9DCD00>0x04</span> – Module has sent a rearming signal<br/><span style=color:#9DCD00>0x05?</span> – Car was closed three times by the factory's remote control<br/>
Byte4:<br/><span style=color:#9DCD00>0x01</span> – Car was closed by the factory's remote control<br/><span style=color:#9DCD00>0x02</span> – Car was opened by the factory's remote control<br/><span style=color:#9DCD00>0x03?</span> – Trunk cover was opened by the factory's remote control<br/><span style=color:#9DCD00>0x04</span> – Module has sent a rearming signal<br/><span style=color:#9DCD00>0x05?</span> – Car was closed three times by the factory's remote control<br/>
- High nibble (mask 0xF0 bit)<br/><span style=color:#9DCD00>0x80</span> – CAN module goes to sleep mode<br/>
- High nibble (mask 0xF0 bit)<br/><span style=color:#9DCD00>0x80</span> – CAN module goes to sleep mode<br/>
|-
! style="text-align: left; vertical-align: top;" | Tachograph driver card presence
| style="text-align: left; vertical-align: top;" | 1
| style="text-align: left; vertical-align: top;" | <span style=color:#9A3300>0x00</span> – No driver card<br/><span style=color:#9A3300>0x01</span> – Driver1 card presence<br/><span style=color:#9A3300>0x02</span> – Driver2 card presence<br/><span style=color:#9A3300>0x03</span> – Driver1 and driver2 cards present<br/>
|-
|-
! style="text-align: left; vertical-align: top;" | Driver 1 states
| style="text-align: left; vertical-align: top;" | 1
| style="text-align: left; vertical-align: top;" rowspan=2 | <span style=color:#124806>0xX0</span> – Break/rest<br/><span style=color:#124806>0xX1</span> – Availability<br/><span style=color:#124806>0xX2</span> – Work<br/><span style=color:#124806>0xX3</span> – Driving<br/><span style=color:#124806>0x0X</span> – No time-related warning detected<br/><span style=color:#124806>0x1X</span> – Limit #1: 15 min before 4 1/2 h<br/><span style=color:#124806>0x2X</span> – Limit #2: 4 1/2 h reached (continuous driving time exceeded)<br/><span style=color:#124806>0x3X</span> – Limit #3: 15 minutes before optional warning 1<br/><span style=color:#124806>0x4X</span> – Limit #4: optional warning 1 reached<br/><span style=color:#124806>0x5X</span> – Limit #5: 15 min before optional warning<br/><span style=color:#124806>0x6X</span> – Limit #6: optional warning 2 reached<br/>
|-
! style="text-align: left; vertical-align: top;" | Driver 2 states
| style="text-align: left; vertical-align: top;" | 1
|}
|}
==Send data with 0, if ignition is off==
==Send data with 0, if ignition is off==
==LV -CAN200/ALLAN300 Important Information==
==LV -CAN200/ALLAN300 Important Information==