Ron.Lewis at 22:14, 17 May 2012

2012-05-17T22:14:14Z

Ron.Lewis: Created page with "=CCP Security Challenge Trigger (DAQ)= Use this MotoHawk™ block to fire a trigger if a GET_SEED CCP command is issued by the client. ==Block ID== CCP Security Challenge T..."

2012-05-17T22:06:52Z

Created page with "=CCP Security Challenge Trigger (DAQ)= Use this MotoHawk™ block to fire a trigger if a GET_SEED CCP command is issued by the client. ==Block ID== CCP Security Challenge T..."

New page

=CCP Security Challenge Trigger (DAQ)=

Use this MotoHawk™ block to fire a trigger if a GET_SEED CCP command is issued by the client.

==Block ID==

CCP Security Challenge Trigger (CAL)

==Library==

MotoHawk_lib/CCP Slave

==Description==

[[Image:CCPSecTrigCAL2.png]]

Connected to this trigger should be a security function and a [[MotoHawk:Blocks:CCP Security Challenge Seed & Key (CAL)| Security Challenge Seed & Key ]] block to provide the 32-bit Seed & Key values for the request. The security function can be any function where the Key can be computed from the Seed via a "known" function. The client must have the identical function to be able to compute the key. For improved security, the Seed value should be as random as possible. Consider using the absolute time block along with the module serial number to create a pseudo-random seed. Instance Name must match the instance name assigned in the [[MotoHawk:Blocks:CCP CAN Protocol Handler|CCP Handler ]] block.

'''Note:''' There are CAL-designated blocks and DAQ-designated blocks. The respectively named CAL and DAQ blocks are functional equivalents and are actually interchangeable; these block names serve to inform that it may be useful to have security access requirements for calibration activity as separate and distinct from the security for data acquisition requests. For instance, one would typically use the (CAL) set to configure a security scheme for a calibration request, and/or set up security for a data acquisition request using the (DAQ) blocks.

For more information on CCP security, see [[CCPSecurity CCP Security]] and the [[CCP Slave Blocks| MotoHawk CCP Blockset]].

==Block Parameters==

{| class="TableMHStyle"
! class="TableHeaderTDStyle" style="width: 172px" | Parameter Field
! class="TableHeaderTDStyle" style="width: 158px" | Values
! class="TableHeaderTDStyle" style="width: 299px" | Comments/Description
|-
| class="TableTDStyle" style="width: 172px" valign="top" | Instance Name
| class="TableTDStyle" style="width: 158px" valign="top" | Alpha-numeric text, single-quote enclosed
| class="TableTDStyle" style="width: 299px" valign="top" |
Enter name to match the instance name assigned in the [CCPCANProtocolHandler.html CCP Handler] block. No special characters, such as spaces, dashes, commas (underscore allowed).
|}

<br />

@@ Line 19: / Line 19: @@
 '''Note:'''  There are CAL-designated blocks and DAQ-designated blocks.  The respectively named CAL and DAQ blocks are functional equivalents and are actually interchangeable; these block names serve to inform that it may be useful to have security access requirements for calibration activity as separate and distinct from the security for data acquisition requests.  For instance, one would typically use the (CAL) set to configure a security scheme for a calibration request, and/or set up security for a data acquisition request using the (DAQ) blocks.
-For more information on CCP security, see [[CCPSecurity CCP Security]] and the [[CCP Slave Blocks| MotoHawk CCP Blockset]].
+For more information on CCP security, see [[CAN_Calibration_Protocol#CCP Security| CCP Security]] and the [[CCP Slave Blocks| MotoHawk CCP Blockset]].
 ==Block Parameters==

MotoHawk:Blocks:CCP Security Challenge Trigger (DAQ) - Revision history

Ron.Lewis at 22:14, 17 May 2012

Ron.Lewis: Created page with "=CCP Security Challenge Trigger (DAQ)= Use this MotoHawk™ block to fire a trigger if a GET_SEED CCP command is issued by the client. ==Block ID== CCP Security Challenge T..."