·
"Execute Script" allows to execute a script and provides additional parameter
"Execute on every Xth Event" so that it is possible to execute the script only for e.g.
every third timeout.
OnReceiveTimeOutResolvedAction
This event is triggered if a receive mapping which time out before is received again. If this
happens all the variables mapped to the PGN are automatically considered valid again
(assuming the PGN received really contained a value for them) and additionally the action
is executed.
If you should see any "Event Options" for this event - ignore them like the PClient does.
Possible actions that can be assigned are
·
"No Action" which is the default
·
"Set Value" to assign a constant value to a variable, e.g. to reset a counter, raise an
alarm or trigger something attached to a variable where "Force Writing" is true.
·
"Execute Script" allows to execute a script and provides additional parameter
"Execute on every Xth Event" so that it is possible to execute the script only for e.g.
every third timeout.
OnMappingReceived
The action for this event is executed EVERY TIME the mapping is received (regardles of
value changes).
When a script action is executed, the variables used in the mapping will already have been
updated with the values from the CAN message.
Do NOT execute complex scripts at this event if the mapping is received very often!
Monitor the performance on the device with a realistic cycle time of all CAN messages.
Monitor the cycle time of transmit messages (the CAN stack has to wait until the received
action is over before taking care of other tasks like sending out transmit mappings).
If you should see any "Event Options" for this event - ignore them like the PClient does.
Possible actions that can be assigned are
·
"No Action" which is the default
·
"Set Value" to assign a constant value to a variable, e.g. to reset a counter, raise an
alarm or trigger something attached to a variable where "Force Writing" is true.
·
"Execute Script" allows to execute a script and provides additional parameter
"Execute on every Xth Event" so that it is possible to execute the script only for e.g.
every third timeout.
After setting all the general properties of the mapping now the data part has to be defined.
Some general rules apply:
·
All variable and constant positions define the position of the least significant bit (for
little and big endian)
·
Receive mappings can have gaps - as long as the length can be determined.
·
Receive mappings are recognized if all the following conditions are true:
if ( ( (PGN received) == (PGN configured) )
&& ( (ECU source address) == (ECU configured) )
&& ( (message length) == (message length configured) )
&& ( ((constants received >> shift) AND configured mask)
== ((constants configured >> shift) AND configured mask) ) )
Note: It is allowed to leave gaps in the data section of receive mappings.
To Next Page
Loading...