Bitcraze Wiki

User Tools

Site Tools

You are here: index » projects » crazyflie » firmware » log
Trace:
projects:crazyflie:firmware:log

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
projects:crazyflie:firmware:log [2012-10-07 13:56]
arnaud 		projects:crazyflie:firmware:log [2012-10-07 14:18]
arnaud
Line 22: Line 22:
 The first byte of each messages correspond a command. All communication on this port are initated by the client and all answer from the copter will contain the same command byte. The first byte of each messages correspond a command. All communication on this port are initated by the client and all answer from the copter will contain the same command byte.
  
-^ TOC command byte ^ Meaning             ^ +^ TOC command byte ^ Command   ^ Operation ^ 
-|                0 | Get TOC Element     | +|                0 | GET_ITEM  | Get an item from the TOC | 
-|                1 | Get TOC information |+|                1 | GET_INFO  | Get information about the TOC and the LOG subsystem implementation |
  
-=== Get TOC element ===+=== Get TOC item === 
 + 
 +The GET_ITEM TOC command permits to retrieved the log variables name, group and types from the copter. This command is intended to be requested from all the ID from 0 to LOG_LEN (see GET_INFO).
  
 <code> <code>
 Request (PC to Copter): Request (PC to Copter):
-        +-------------+------------+ +        +--------------+----+ 
-        | Command (0) | Element ID | +        | GET_ITEM (0) | ID | 
-        +-------------+------------+ +        +--------------+----+ 
-Length         1            1+Length         1         1
  
 Answer (Copter to PC): Answer (Copter to PC):
-        +-------------+------------+------+------------+--------------+ +        +--------------+----+------+------------+--------------+ 
-        | Command (0) | Element ID | Type |   Group    |     Name     | +        | GET_ITEM (0) | ID | Type |   Group    |     Name     | 
-        +-------------+------------+------+------------+--------------+ +        +--------------+----+------+------------+--------------+ 
-Length        1             1         1    < Null terminated strings >+Length        1          1     1    < Null terminated strings >
 </code> </code>
 ^ Request fields ^ Content                             ^ ^ Request fields ^ Content                             ^
-| Command        | Must be 0 for GET_ELEMENT operation | +| GET_ITEM       | At 0 for GET_ITEM operation | 
-| Element ID     | ID of the element to be retrieved. The variables are numbered from 0 to LOG_LEN (see GET_INFO command) |+| ID             | ID of the item to be retrieved. The variables are numbered from 0 to LOG_LEN (see GET_INFO command) |
  
 ^ Answer fields  ^ Content                             ^ ^ Answer fields  ^ Content                             ^
-| Command        | 0 for GET_ELEMENT operation | +| GET_ITEM       | 0 for GET_ITEM operation | 
-| Element ID     | ID of the element returned  |+| ID             | ID of the item returned  |
 | Type           | Variable type of the element. See variable types list | | Type           | Variable type of the element. See variable types list |
 | Group          | Null-terminated string containing variable group | | Group          | Null-terminated string containing variable group |
 | Name           | Null-terminated string containing the variable name | | Name           | Null-terminated string containing the variable name |
 +
 +=== Get Info ===
 +
 +The get info command is intended to be requested first when connecting to the copter. This permits to know the number of variable, the limitations of the log implementation and the fingerprint of the log variables.
 +
 +<code>
 +Request (PC to Copter):
 +        +--------------+
 +        | GET_INFO (1) |
 +        +--------------+
 +Length         1
 +
 +Answer (Copter to PC):
 +        +--------------+---------+---------+-----------------+-------------+
 +        | GET_INFO (1) | LOG_LEN | LOG_CRC |  LOG_MAX_PACKET | LOG_MAX_OPS |
 +        +--------------+---------+---------+-----------------+-------------+
 +Length        1             1         4             1               1
 +</code>
 +
 +^ Request fields ^ Content                             ^
 +| GET_INFO       | At 1 for GET_INFO operation |
 +
 +^ Answer fields  ^ Content                             ^
 +| GET_INFO       | 1 for GET_INFO operation |
 +| LOG_LEN        | Number of log items contained in the log table of content |
 +| LOG_CRC        | CRC values of the log TOC memory content. This is a fingerprint of the copter build that can be used to cache the TOC |
 +| LOG_MAX_PACKET | Maximum number of log packets that can be programmed in the copter |
 +| LOG_MAX_OPS    | Maximum number of operation programmable in the copter. An operation is one log variable retrieval programming |
 +
  
projects/crazyflie/firmware/log.txt · Last modified: 2021-06-24 16:49 by kimberly

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki