CANopen LSS Configuration Request Trigger

This block creates a trigger that is called when the referenced LSS slave instance recives the selected LSS Configuration request.

Block ID

CANopen LSS Configuration Request Trigger

Library

motohawk_canopen_lib

Description

This block creates a trigger that is called when the referenced LSS slave receives the drop down selected LSS configuration request message. For all requests except LSS activate bit timing parameters, an LSS response on configuration request response block can be used to provide application derived error code values.

Possible LSS Configuration Requests:

This trigger is called when selected LSS configuration request is received. All requests except 'LSS Activate Bit Timing Parameters' requires response. To set appropriate response please use CANopen LSS response on configuration request. When no response is specified by the user, a positive response will be sent.

When the trigger is configured to execute when configuring the LSS node ID, a node ID port will provide the new node ID to use upon transition to LSS operation mode. When the trigger is configured to execute when configuring the CAN baud rate, a table selector and table index port will provide these values to the application for use. Table index value meanings are provided below:

Baud Rate Table Index
1000 kBit 0
800 kBit 1
500 kBit 2
250 kBit 3
125 kBit 4
reserved 5
50 kBit 6
20 kBit 7
10 kBit 8

Example usage of this block together with response:

When a trigger associated with any of the selectable LSS configuration requests is not present, that functionality is disabled and the CANopen software will respond with an error message upon the request.

Block Parameters

Parameter Field Values Comments/Description
LSS Instance Reference String Name of associated CANopen LSS slave instance.
Trigger Name String Name of created trigger. Parameter is optional, if no name is provided in the edit field the trigger name is generated automatically.
LSS Configuration Drop down LSS configuration request on which trigger is called :
  • LSS Configure Node-ID
  • LSS Configure CAN Baud Rate
  • LSS Activate Bit Timing Parameters
  • LSS Store Configuration Parameters
Execution Order within Task Numeric (Integer) More than one trigger may be placed in a model that is driven by the same event. Use the execution order within task attribute to define the execution order of these triggers relative to one another. The triggers will execute from the lowest execution order within task value to the highest.
This trigger is inside another triggered subsystem Checkbox If the trigger is inside another triggered subsystem, this must be checked.
Trigger even when containing subsystem is disabled Checkbox If the trigger is inside another enabled subsystem, then execute this subsystem if that subsystem is enabled.