Changes

no edit summary
Line 66: Line 66:  
{{{model|FM36YX}}} connection with CAN adapter is different than with other FM devices, when connecting ALL-CAN300 and LV-CAN200 adapters. {{{model|FM36YX}}} has closed USB connector and CAN adapter is connected with INPUT 5 and INPUT 6 wires as shown in figure below.
 
{{{model|FM36YX}}} connection with CAN adapter is different than with other FM devices, when connecting ALL-CAN300 and LV-CAN200 adapters. {{{model|FM36YX}}} has closed USB connector and CAN adapter is connected with INPUT 5 and INPUT 6 wires as shown in figure below.
 
<br>
 
<br>
[[File:FM36M1_LV-CAN200 ALL-CAN300 Adapter connection cable pinout.png|800px]]
+
[[File:FM36M1_CAN_Adapter_connection_cable_pinout.png|800px]]
    
<br>
 
<br>
Line 87: Line 87:  
===SCAN function===
 
===SCAN function===
 
Scan function can be used when {{{model|FM36YX}}} is connected to CAN adapter and PC (Figure below). After connection is made Press scan button to see available CAN parameters (Note, that car engine must be started). Enable CAN data which needs to be sent to server and save configuration by pressing “Save” button.  
 
Scan function can be used when {{{model|FM36YX}}} is connected to CAN adapter and PC (Figure below). After connection is made Press scan button to see available CAN parameters (Note, that car engine must be started). Enable CAN data which needs to be sent to server and save configuration by pressing “Save” button.  
<br> [[Image:FM36YX_scan_function.png|589px]] <br>
+
<br> [[Image:FM36M1_scan_function.png|589px]] <br>
 
CAN bus data which can be read from your car is shown in “Light Vehicles Can adapter supported cars” document.
 
CAN bus data which can be read from your car is shown in “Light Vehicles Can adapter supported cars” document.
 +
 
===Offline configuration===
 
===Offline configuration===
 
Comming soon
 
Comming soon
Line 102: Line 103:  
<br>
 
<br>
 
Data Acquisition Type – defines when to generate event – when value enters defined range, exits it or both, also is possible to select event which you want to generate then you change values, like crossing both values in high and low levels (Hysteresis). High and Low levels – defines CAN value range. If CAN value enter or exits this range, {{{model|FM36YX}}} generates event by “Data Acquisition Type” settings. Figure below show example of {{{model|FM36YX}}} CAN configuration.
 
Data Acquisition Type – defines when to generate event – when value enters defined range, exits it or both, also is possible to select event which you want to generate then you change values, like crossing both values in high and low levels (Hysteresis). High and Low levels – defines CAN value range. If CAN value enter or exits this range, {{{model|FM36YX}}} generates event by “Data Acquisition Type” settings. Figure below show example of {{{model|FM36YX}}} CAN configuration.
<br>
+
 
'''PICTURE''' ?????
   
<br> [[File:FM36XX_Configurator_LVCAN.png|800px]] <br>
 
<br> [[File:FM36XX_Configurator_LVCAN.png|800px]] <br>
Available CAN Bus IO parameters and configuration can be found in Configurators CAN tab (Figure above) and in  “Parameters ID”. ?????
+
Available CAN Bus IO parameters and configuration can be found in Configurators CAN tab (Figure above) and in  “Parameters ID”.
 
<br><br>
 
<br><br>
 
All information about I/O element parameters description is in section [[{{{model|FM36YX}}} I/O settings|I/O settings]].<br/>All LV-CAN200/ALL-CAN300 I/O parameters configuration settings are described in "{{{model|FM36YX}}} Protocols" document, except ALL-CAN300 bitmasks, which are described in the table below.''
 
All information about I/O element parameters description is in section [[{{{model|FM36YX}}} I/O settings|I/O settings]].<br/>All LV-CAN200/ALL-CAN300 I/O parameters configuration settings are described in "{{{model|FM36YX}}} Protocols" document, except ALL-CAN300 bitmasks, which are described in the table below.''
Line 316: Line 316:  
===Example===
 
===Example===
 
When using older connection schemes where program number displayed as 3-digit program number:
 
When using older connection schemes where program number displayed as 3-digit program number:
[[Image:Fmb120_can_prog_number.png|600px|center]]
+
[[Image:FM36M1_can_prog_number.png|600px|center]]
    
Using LV-CAN200/ALL-CAN300 Bootloader from soft version 2017-09-27 it is necessary to add "1" to the front of program number:
 
Using LV-CAN200/ALL-CAN300 Bootloader from soft version 2017-09-27 it is necessary to add "1" to the front of program number:
 
[[Image:Fmb120_can_updater.png|400px|center]]
 
[[Image:Fmb120_can_updater.png|400px|center]]