Skip to main content

​
ChkCreate_J1939AddressClaimViolation, ChkStart_J1939AddressClaimViolation

Valid for: CANoe DE • CANoe4SW DE

​
Function Syntax

dword ChkCreate_J1939AddressClaimViolation (Node aNode, dword aAddress, dword aac, dword ig, dword sys, dword sysi, dword fct, dword fcti, dword ecui, dword mc, dword in, dword aTimeout, dword aFlags, char[] callback1);
dword ChkStart_J1939AddressClaimViolation (Node aNode, dword aAddress, dword aac, dword ig, dword sys, dword sysi, dword fct, dword fcti, dword ecui, dword mc, dword in, dword aTimeout, dword aFlags, char[] callback1);

​
Constructor

TestCheck::CreateJ1939AddressClaimViolation 
TestCheck::CreateJ1939AddressClaimViolation (Node aNode, dword aAddress, dword aac, dword ig, dword sys, dword sysi, dword fct, dword fcti, dword ecui, dword mc, dword in, dword aTimeout, dword aFlags, char[] callback2);
TestCheck::StartJ1939AddressClaimViolation (Node aNode, dword aAddress, dword aac, dword ig, dword sys, dword sysi, dword fct, dword fcti, dword ecui, dword mc, dword in, dword aTimeout, dword aFlags, char[] callback2);

​
Check Name

J1939 Address Claiming

​
Description

Observes the Address Claiming of a J1939 node. The specified node must respond to a Request for Address Claim. Optionally the check allows sending other messages, only if an Address Claim message (0xEE00) of the node is received first. You can add further nodes to this check with Chk_AddNode. Note Dependent on the used parameter type the appropriate bus context in a multibus environment has only to be set before the function is called if the corresponding database object will be ambiguous. Further information on site MultiBus Environment.

​
Parameters

  • aNode: Name of the node to be checked. Must exist in database.
  • aAddress: Address of the node. 0-253 or -1 (or 0xFFFFFFFF) if value of the node in database is used.
  • aac: Arbitrary Address Capable 0..1 or -1 (or 0xFFFFFFFF) if value of the node in database is used.
  • ig: Industry Group 0..7 or -1 (or 0xFFFFFFFF) if value of the node in database is used.
  • sys: Vehicle System 0..127 or -1 (or 0xFFFFFFFF) if value of database is used.
  • sysi: Vehicle System Instance 0..15 or -1 (0xFFFFFFFF) if value of the node in database is used.
  • fct: Function 0..255 or -1 (or 0xFFFFFFFF) if value of the node in database is used.
  • fcti: Function Instance 0..31 or -1 (or 0xFFFFFFFF) if value of the node in database is used.
  • ecui: ECU Instance 0..7 or -1 (or 0xFFFFFFFF) if value of the node in database is used.
  • mc: Manufacturer Code 0..2047 or -1 (or 0xFFFFFFFF) if value of the node in database is used.
  • in: Identity Number 0.. 2097151 or -1 (or 0xFFFFFFFF) if value of the node in database is used.
  • aTimeout: Within this time a Request for Address Claim has to be responded. Default unit [ms], if not changed with ChkConfig_SetPrecision.
  • aFlags:
    • Bit 0: Allow address usage before Address Claim.
    • Bit 1: Allow Address Claim messages from non-configured nodes.
    • Bit 2: Allow claiming of other address than configured.
  • callback1: This parameter is optional. Name of the callback which is called when the check fails. Signature: void Callback( dword checkId )
  • callback2: This parameter is optional. Name of the callback which is called when the check fails. Signature: void Callback( TestCheck check )

​
Return Values

  • 0: Check could not be created and must not be referenced.
  • > 0: Check was created successfully and may be referenced using the returned (handle-) value.

​
Possible Errors

  • Node object does not exist in database.

​
Example

TestCheck c;
// checks the address claim violation of node N1
c = TestCheck::CreateJ1939AddressClaimViolation( N1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, 200, 0x01);

// add node N2 to the check
c.AddNode (N2, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1);
TestAddCondition(c);

// Start check
c.start();

// sequence of different actions and waiting conditions
TestWaitForTimeout(1000);
TestRemoveCondition(c);
Functions to Configure Checks • Commands to Control Checks