Skip to main content

​
ChkCreate_NodeDead, ChkStart_NodeDead

Valid for: CANoe DE • CANoe4SW DE

​
Function Syntax

  • dword ChkCreate_NodeDead (Node n, Duration aMaxQuietTime, char [] CaplCallback); // form 1
  • dword ChkStart_NodeDead (Node n, Duration aMaxQuietTime, char [] CaplCallback); // form 2
  • dword ChkStart_NodeDead (char [] Node, Duration aMaxQuietTime, char [] CaplCallback); // form 3

​
Constructor

TestCheck::CreateNodeDead (Node n, Duration aMaxQuietTime, char [] CaplCallback); // form 1
  • TestCheck::StartNodeDead (Node n, Duration aMaxQuietTime, char [] CaplCallback); // form 2
  • TestCheck::StartNodeDead (char [] Node, Duration aMaxQuietTime, char [] CaplCallback); // form 3

​
Check Name

Node Active (Check Description)

​
Description

All monitored nodes must send at least one of their Tx messages within a specified interval. Otherwise, an event will be triggered. Gateway nodes require that the bus context corresponds to the bus that is being observed. This means that the check only works correctly if the current bus context corresponds to the database in which the node is defined. For FlexRay only valid data frames and PDUs are recognized as communication, Null Frames and Erroneous frames are ignored. 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

  • n/Node: Defined node in database.
  • aMaxQuietTime: Upper limit of time interval. > 0; default unit [ms], if not changed with ChkConfig_SetPrecision.
  • CaplCallback: In simulation nodes this parameter has to be set. In test modules this parameter is optional.

​
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

​
Check-specific Queries

​
Example

// checks that at least one message of the node is sent in each 100 ms
checkId = ChkStart_NodeDead (Node1, 100);
TestAddCondition(checkId);
// sequence of different actions and waiting conditions
TestWaitForTimeout(1000);
TestRemoveCondition(checkId);
Functions to Configure Checks • Commands to Control Checks