Changes

Created page with "__TOC__ <br /> 30px '''Functionality description is based on latest firmware - 55.01.02.Rev.01.''' =Manual CAN Basic parameters purpose= Manual CAN bas..."
__TOC__

<br />

[[File:Alert.png|30px]]

'''Functionality description is based on latest firmware - 55.01.02.Rev.01.'''

=Manual CAN Basic parameters purpose=

Manual CAN basic parameters can be used to detect Speed or Ignition, when Speed / Ignition sources are set to '''CAN''' in device's configuration.
<br><br>
[[image:Manual CAN Ignition Speed source.png]]

=Configuration explained for Ignition=

{| style="width: 100%"
|[[Image:CAN source explained.png|right]]

To use '''Manual CAN''' functionality for Ignition detection, '''Ignition Source''' parameter must have '''CAN''' option enabled.

Additionally, since this functionality works only with '''Manual CAN''' protocol, '''Manual CAN''' option should be enabled as well under '''CAN Protocol''' parameter.
|}

----------------------------------------------------
<br>
Further configuration, to extract Ignition information from a '''CAN message''' is done under '''Manual CAN Settings''' section in configurator.

*'''Ignition Manual CAN Slot''' defines with which '''Manual CAN slot''' a CAN message containing information about Ignition will be captured.

[[image:Manual CAN Ignition Source.png]]

-----------------------------------------------------
<br>
*'''Ignition Data Mask''' defines which '''bits''' from incoming '''CAN message''' are responsible for '''ignition information'''. In other words - Ignition Data Mask parameter defines which data mask will be applied to received CAN data.

Ignition Data Mask parameter is '''8 byte HEX''' value.

{| class="wikitable"
! rowspan="2" |Parameter Id
! rowspan="2" |Name
! colspan="2" |Value
|-
!Min
!Max
|-
|322
|Ignition Data Mask
|0000000000000000
|FFFFFFFFFFFFFFFF
|}

-----------------------------------------------------
<br>

*'''Ignition Range Low''' defines lowest value limit to detect ignition (if ignition detection has several states)
{| class="wikitable"
! rowspan="2" |Parameter Id
! rowspan="2" |Name
! colspan="3" |Value
|-
!Min
!Max
!Default
|-
|323
|Ignition Range Low
|0
|18446744073709551615
|1
|}

-----------------------------------------------------
<br>

*'''Ignition Range High''' defines highest value limit to detect ignition (if ignition detection has several states)
{| class="wikitable"
! rowspan="2" |Parameter Id
! rowspan="2" |Name
! colspan="3" |Value
|-
!Min
!Max
!Default
|-
|324
|Ignition Range High
|0
|18446744073709551615
|1
|}

----------------------------------------------
<br>
'''Example:'''

Ignition information data value will be ''Received Data Value'' '''AND''' ''Data Mask''.

Let's say that '''7th byte of 8 bytes CAN message''' is responsible for '''ignition information''', ''Received Data Value'' would be 0x11223344556677'''01'''.

Since only Ignition value is needed and it is located on 7th byte of previous CAN message, 00000000000000'''FF''' ''Data Mask'' should be applied.

In this case, incoming CAN message would hold only our masked ignition information - 0x00000000000000'''01'''.

=Configuration explained for Speed=

{| style="width: 100%"
|[[Image:CAN Speed source.png|right]]

To use '''Manual CAN''' functionality for Speed monitoring, '''Speed Source''' parameter must have '''CAN''' option enabled.

Additionally, since this functionality works only with '''Manual CAN''' protocol, '''Manual CAN''' option should be enabled as well under '''CAN Protocol''' parameter.
|}

----------------------------------------------------
<br>
Further configuration, to extract Speed information from a '''CAN message''' is done under '''Manual CAN Settings''' section in configurator.

*'''Speed Manual CAN Slot''' defines with which '''Manual CAN slot''' a CAN message containing information about Speed will be captured.

[[image:Speed Manual Can Slot.png]]

-----------------------------------------------------
<br>
*'''Speed Data Mask''' defines which '''bits''' from incoming '''CAN message''' are responsible for '''speed information'''. In other words - Speed Data Mask parameter defines which data mask will be applied to received CAN data.

Speed Data Mask parameter is '''8 byte HEX''' value.

{| class="wikitable"
! rowspan="2" |Parameter Id
! rowspan="2" |Name
! colspan="2" |Value
|-
!Min
!Max
|-
|326
|Speed Data Mask
|0000000000000000
|FFFFFFFFFFFFFFFF
|}

----------------------------------------------
<br>
*'''Speed Offset''' defines offset which will be substracted from calculated Speed value.
{| class="wikitable"
! rowspan="2" |Parameter Id
! rowspan="2" |Name
! colspan="3" |Value
|-
!Min
!Max
!Default
|-
|327
|Speed Offset
| -2147483648
|2147483647
|0
|}

----------------------------------------------
<br>
*'''Speed Coefficient''' defines coefficient which raw CAN value will be multiplied with.
{| class="wikitable"
! rowspan="2" |Parameter Id
! rowspan="2" |Name
! colspan="3" |Value
|-
!Min
!Max
!Default
|-
|328
|Speed Coefficient
|0.0000001
|1000000
|1
|}

----------------------------------------------
<br>
'''Example:'''

Speed information data value will be ''Received Data Value'' '''AND''' ''Data Mask''.

Let's say that '''7th byte of 8 bytes CAN message''' is responsible for '''speed information''', ''Received Data Value'' would be 0x11223344556677'''01'''.

Since only Speed value is needed and it is located on 7th byte of previous CAN message, 00000000000000'''FF''' ''Data Mask'' should be applied.

In this case, incoming CAN message would hold only our masked Speed information - 0x00000000000000'''01'''.




[[Category: TFT100 FAQ]]
0

edits