CCP CAN Protocol Block

From NewEagleWiki
Revision as of 15:07, 8 July 2010 by Anonymous (talk | contribs) (Created page with 'Use this MotoHawk™ block to manage handling of a CAN Calibration Protocol (CCP) connection via CAN. ===Block ID=== CCP CAN Protocol ===Block Library=== MotoHawk_lib/CCP Sla…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Use this MotoHawk™ block to manage handling of a CAN Calibration Protocol (CCP) connection via CAN.

Block ID

CCP CAN Protocol

Block Library

MotoHawk_lib/CCP Slave

Block Description


CCP (CAN Calibration Protocol) is a standard intended to create a common interface to electronic control modules. It is possible to use multiple instances of this block, giving each a unique Instance Name, and thus implement multiple CCP handlers. For more information on CCP, see CAN Calibration Protocol.

The list of data acquisition (DAQ) triggers is pre-selected to:

  • FGND_RTI_PERIODIC
  • FGND_2XRTI_PERIODIC
  • FGND_10XRTI_PERIODIC
  • FGND_20XRTI_PERIODIC
  • BGND_BASE_PERIODIC
  • BGND_BASEx2_PERIODIC
  • BGND_BASEx10_PERIODIC
  • ONE_SECOND_EVENT

The CCP Command packets are responded to in IDLE time of the application. To implement a different triggering scheme, use the CCP CAN Protocol External Trig block from the CCP Slave Library, and supply triggering to the Command Trigger input with a MotoHawk Trigger block.


Supported operations: upload calibrations, download calibrations, data acquisition, seed and key security.

Not supported: Flashing operations


Block Parameters

Note: Setting the "Command Processor Busy" check-box to checked has been necessary when the combination of ETAS INCA and the MotoHawk target ECU565-128 are being used together.

Retrieved from "https://wiki.neweagle.net//index.php?title=CCP_CAN_Protocol_Block&oldid=1483"