Ron.Lewis: Created page with "=CCP CAN Protocol Handler= Use this MotoHawk™ block to manage handling of a CAN Calibration Protocol (CCP) connection via CAN. ==Block ID== CCP CAN Protocol ==Library== ..."

2012-05-17T21:34:26Z

Created page with "=CCP CAN Protocol Handler= Use this MotoHawk™ block to manage handling of a CAN Calibration Protocol (CCP) connection via CAN. ==Block ID== CCP CAN Protocol ==Library== ..."

New page

=CCP CAN Protocol Handler=

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

==Block ID==

CCP CAN Protocol

==Library==

MotoHawk_lib/CCP Slave

==Description==

[[Image:CCPCANHandler.png]]

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 [../MotoHawk_topics/CANCalibrationProtocol.html 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 [CCPCANProtocolHandlerTriggered.html CCP CAN Protocol External Trig] block from the CCP Slave Library, and supply triggering to the Command Trigger input with a [FunctionTrigger.html MotoHawk Trigger] block.

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

Not supported: Flashing operations

==Block Parameters==

{| class="TableMHStyle"
| class="TableHeaderTDStyle" style="width: 203px" | Parameter Field
| class="TableHeaderTDStyle" style="width: 158px" | Values
| class="TableHeaderTDStyle" style="width: 299px" | Comments/Description
|- id="mam"
| class="TableTDStyle" style="width: 203px" valign="top" | CCP Handler Instance Name
| class="TableTDStyle" style="width: 158px" valign="top" | Alpha-numeric text, single-quote enclosed
| class="TableTDStyle" style="width: 299px" valign="top" | Enter unique name for this handler instance. No special characters, such as spaces, dashes, commas (underscore allowed).
|-
| class="TableTDStyle" style="width: 203px" valign="top" | CCP Station Address (16-bit integer)
| class="TableTDStyle" style="width: 158px" valign="top" | hex2dec('value')
| class="TableTDStyle" style="width: 299px" valign="top" | Define the address that will used to communicate via the CCP Handler. On a CAN bus with multiple MotoTron modules, MotoTune can communicate with each module via the respective station address. Therefore, each CCP handler on a bus MUST have a unique address.
|- id="bus"
| class="TableTDStyle" style="width: 203px" valign="top" | CAN Channel Name
| class="TableTDStyle" style="width: 158px" valign="top" | Alpha-numeric text, single-quote enclosed - 'CAN_1'
| class="TableTDStyle" style="width: 299px" valign="top" | Specify which CAN channel to use - CAN_1, CAN_2, CAN_3
|- id="btime"
| class="TableTDStyle" style="width: 203px" valign="top" | Receive ID (CRO)
| class="TableTDStyle" style="width: 158px" valign="top" | hex2dec('18ef0231')
| class="TableTDStyle" style="width: 299px" valign="top" | Specify ID to be used for CCP communication of Command Request Object (CRO).
|-
| class="TableTDStyle" style="width: 203px" valign="top" | Receive ID Type (0=Std, 1=Ext)
| class="TableTDStyle" style="width: 158px" valign="top" | 0 or 1
| class="TableTDStyle" style="width: 299px" valign="top" | Specify 0 for Standard (11-bit identifiers), 1 for Extended (29-bit identifiers) on the CAN bus.
|-
| class="TableTDStyle" style="width: 203px" valign="top" | Receive ID Mask
| class="TableTDStyle" style="width: 158px" valign="top" | hex2dec('1FFFFFFF')
| class="TableTDStyle" style="width: 299px" valign="top" | Specify Receive ID Mask
|-
| class="TableTDStyle" style="width: 203px" valign="top" | Transmit ID (DTO/DAQ)
| class="TableTDStyle" style="width: 158px" valign="top" | hex2dec('18ef0231')
| class="TableTDStyle" style="width: 299px" valign="top" | Specify Transmit ID for Data Transfer Objects and Data Acquisition.
|-
| class="TableTDStyle" style="width: 203px" valign="top" | Transmit ID Type (0=Std, 1=Ext)
| class="TableTDStyle" style="width: 158px" valign="top" | 0 or 1
| class="TableTDStyle" style="width: 299px" valign="top" | Specify 0 for Standard (11-bit identifiers), 1 for Extended (29-bit identifiers) on the CAN bus.
|- id="mototune_group"
| class="TableTDStyle" style="width: 203px" valign="top" | Total Number of DAQs (0-253)
| class="TableTDStyle" style="width: 158px" valign="top" | 0-253
| class="TableTDStyle" style="width: 299px" valign="top" | Set the number of Data Acquisitions (DAQs) for the CCP. DAQs are lists of automatically transmitted signals. <br />
|- id="mototune_group0"
| class="TableTDStyle" style="width: 203px" valign="top" | Total Number of Object Descriptors (ODT) per (DAQ) (1-253)
| class="TableTDStyle" style="width: 158px" valign="top" | 11-253
| class="TableTDStyle" style="width: 299px" valign="top" | Set the number of Object Descriptors (ODTs) per Data Acquisitions for the CCP. ODTs determine the length of each DAQ list.
|- id="mototune_group1"
| class="TableTDStyle" style="width: 203px" valign="top" | Store DTs in NonVolatile (0=RAM, 1=EEPROM, 2=CAL)
| class="TableTDStyle" style="width: 158px" valign="top" | 0, 1, 2
| class="TableTDStyle" style="width: 299px" valign="top" | Select choice of Storage for Object Descriptors
|- id="send_cpb_resp"
| class="TableTDStyle" style="width: 203px" valign="top" | Send "Command Processor Busy" response prior to long memory writes
| class="TableTDStyle" style="width: 158px" valign="top" | checkbox (default = unchecked)
| class="TableTDStyle" style="width: 299px" valign="top" | The download of calibrations has the possibility of exceeding the allotted timeout for the DNLOAD command (25 ms). Some calibration tools are capable of extending this timeout if an initial "Command Processor Busy" response is received within the normal timeout period. Checking this option will enable the sending of a "Command Processor Busy" response as soon as a DNLOAD command is recieved where the data will be writing to EEPROM space.
|-
| class="TableTDStyle" style="width: 203px" valign="top" | MotoTune Group String
| class="TableTDStyle" style="width: 158px" valign="top" | Alpha-numeric text
| class="TableTDStyle" style="width: 299px" valign="top" | Determines Folder name and hierarchy as displayed in MotoTune. Use "|" character between folder names to delineate subfolder structure.
|}

'''Note:'''<br /> Setting the "Command Processor Busy" checkbox to ''checked'' has been necessary when the combination of ETAS INCA<br /> and the MotoHawk target ECU565-128 are being used together.

MotoHawk:Blocks:CCP CAN Protocol Handler - Revision history

Ron.Lewis: Created page with "=CCP CAN Protocol Handler= Use this MotoHawk™ block to manage handling of a CAN Calibration Protocol (CCP) connection via CAN. ==Block ID== CCP CAN Protocol ==Library== ..."