FMB can＿info: Difference between revisions

VisualWikitext

Latest revision as of 14:10, 17 December 2025

Command Overview

The can_info command provides the status of the CAN1 and CAN2 interfaces.

It can be checked via SMS as follows:

Send the message: can_info<x>

Note: include a space before the command in the SMS message.

Parameter <x>: Specifies which CAN line should be included in the response:

0 – CAN1
1 – CAN2

Example of responses sent and received via phone:

Example response:

[CAN1] State:"SetBitrate" R:500kBit E:40250/2/4/1/0, Got:0 F:0/0 Proc:0/0 Ovf:0/0 TxF:4, PHY:On/Normal

[CAN2] State:"Active" R:250kBit E:40080/2/0/0/0, Got:0 F:0/0 Proc:0/0 Ovf:0/0 TxF:0, PHY:On/Normal

Field Explanation Table

Field	Explanation
State:	Disabled - CAN not active SetBitrate - Initializing can with set bitrate Checkbitrate - Checking for errors or messages Active - messages recieved or no errors found
R:	Current bitrate
E:X/y1/y2/y3/y4	Status and error counters X - ESR register value Y1 - Re-init counter Y2 - Warning counter Y3 - Error passive counter Y4 - Buss OFF counter
Got:	Can frames received total
F:x1/x2	X1 - frames send to software filter X2 - frames accepted by software filter
Proc:x1/x2	X1 - frames send for parsing X2 - parsed frames
Ovf:x1/x2	X1 - Frames dropped because no memory X2 - Frames dropped because queue full
Ovf:x1/x2	X1 - Frames dropped because no memory X2 - Frames dropped because queue full
TxF:x1	X1 - Messages count failed to send to CAN bus
PHY:x1/x2	X1 - CAN Power Status On/Off X2 - CAN Mode Normal/Silent

@@ Line 1: / Line 1: @@
+===Command Overview===
 The ''can_info'' command provides the status of the CAN1 and CAN2 interfaces.
 It can be checked via SMS as follows:
+Send the message: '''can_info<x>'''
+'''Note:''' include a space before the command in the SMS message.
+Parameter '''<x>''':
+Specifies which CAN line should be included in the response:
+*0 – CAN1
+*1 – CAN2
+Example of responses sent and received via phone:
+[[File:Can info example.png]]
+Example response:
+[CAN1] State:"SetBitrate" R:500kBit E:40250/2/4/1/0, Got:0 F:0/0 Proc:0/0 Ovf:0/0 TxF:4, PHY:On/Normal
+[CAN2] State:"Active" R:250kBit E:40080/2/0/0/0, Got:0 F:0/0 Proc:0/0 Ovf:0/0 TxF:0, PHY:On/Normal
+===Field Explanation Table===
 {| class="wikitable"
 ! Field
@@ Line 7: / Line 31: @@
 |-
 | State:
-| ''Disabled'' - CAN not active<br>''SetBitrate'' - Initializing can with set bitrate<br>''Checkbitrate'' - Checking for errors or messages<br>''Active'' - messages recieved or no errors found
+|
+''Disabled'' - CAN not active
+<br>''SetBitrate'' - Initializing can with set bitrate
+<br>''Checkbitrate'' - Checking for errors or messages
+<br>''Active'' - messages recieved or no errors found
 |-
 | R:
-| Current bitrate
+|
+Current bitrate
 |-
 |E:X/y1/y2/y3/y4
-| Satus and error counters <br
+|
+Status and error counters
+<br> ''X'' - ESR register value
+<br> ''Y1'' - Re-init counter
+<br> ''Y2'' - Warning counter
+<br> ''Y3'' - Error passive counter
+<br> ''Y4'' - Buss OFF counter
+|-
+|Got:
+|
+Can frames received total
+|-
+|F:x1/x2
+|
+<br>''X1'' - frames send to software filter
+<br>''X2'' - frames accepted by software filter
+|-
+|Proc:x1/x2
+|
+<br>''X1'' - frames send for parsing
+<br>''X2'' - parsed frames
+|-
+|Ovf:x1/x2
+|
+<br>''X1'' - Frames dropped because no memory
+<br>''X2'' - Frames dropped because queue full
+|-
+|Ovf:x1/x2
+|
+<br>''X1'' - Frames dropped because no memory
+<br>''X2'' - Frames dropped because queue full
+|-
+|TxF:x1
+|
+<br>''X1'' - Messages count failed to send to CAN bus
+|-
+|PHY:x1/x2
+|
+<br>''X1'' - CAN Power Status On/Off
+<br>''X2'' - CAN Mode Normal/Silent
 |}