<< return to Pixycam.com

User Tools

Site Tools


wiki:v2:ccc_api

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
wiki:v2:ccc_api [2018/07/02 16:34]
pixycam
wiki:v2:ccc_api [2018/10/10 20:05] (current)
jfrench added protocol reference link
Line 2: Line 2:
  
 This API can be called through the _ccc_ member of the [[wiki:​v2:​general_api|Pixy2 object]], for example: This API can be called through the _ccc_ member of the [[wiki:​v2:​general_api|Pixy2 object]], for example:
- 
- 
-[{{wiki:​v2:​image_365.png?​500|Line tracking coordinates. ​ See note (3) below about resolution.}}] 
- 
  
  
Line 14: Line 10:
 </​code>​ </​code>​
  
-The functions in this API will return errors unless ​the [[wiki:​v2:​color_connected_components|color_connected_components]] program is being run+See also the [[wiki:​v2:​general_api|Pixy2 General ​API]], [[wiki:​v2:​line_api|Line tracking API]], and [[wiki:​v2:​video_api|Video API]] for other functionality. 
 + 
 +For a byte-level reference to the protocol, check out the new [[wiki:​v2:​protocol_reference|Pixy2 Serial Protocol - Packet Reference]] 
 + 
 +Firmware versions 3.0.11 and greater ​will automatically switch to the [[wiki:​v2:​color_connected_components|color_connected_components]] ​program when making requests through the color connected components API. Older firmware versions will return errors when attempting to call these functions while the color connected components ​program is not running.
  
 A good program to run to familiarize yourself the CCC algorithm is the *ccc\_hello\_world* example found in the Arduino library.  ​ A good program to run to familiarize yourself the CCC algorithm is the *ccc\_hello\_world* example found in the Arduino library.  ​
 +
 +
 +
 +[{{wiki:​v2:​image_365.png?​500|Color connected components image coordinates from Pixy2'​s perspective}}]
 +
 +
  
 ==== Member functions ==== ==== Member functions ====
Line 50: Line 56:
  
 == uint16_t m_x == == uint16_t m_x ==
-This variable contains the x location of the center of the block. ​ The value ranges between 0 and _frameWidth_ (316).+This variable contains the x location of the center of the block. ​ The value ranges between 0 and _frameWidth_ (315).
  
 == uint16_t m_y == == uint16_t m_y ==
Line 56: Line 62:
  
 == uint16_t m_width == == uint16_t m_width ==
-This variable contains the width of the block. ​ The value ranges between 0 and _frameWidth_ (317).+This variable contains the width of the block. ​ The value ranges between 0 and _frameWidth_ (316).
  
 == uint16_t m_height == == uint16_t m_height ==
-This variable contains the height of the block. ​ The value ranges between 0 and _frameHeight_ (207).+This variable contains the height of the block. ​ The value ranges between 0 and _frameHeight_ (208).
  
 == int16_t m_angle == == int16_t m_angle ==
wiki/v2/ccc_api.1530549294.txt.gz · Last modified: 2018/07/02 16:34 by pixycam