46
As a policy of continual improvement, STAUFF reserves the right to alter the specification without prior notice.
201.031
Date of Issue: 06 November 2018
The easiest approach is to use LASPAC-View to configure the test parameters and result format. Then
the customer application only has to read the results.
The CAN-bus parameters are configured from the Communication Settings dialogue, accessed from the
LPM Settings dialogue (see section 6.3.3).
Figure 6.30 Communication Settings Dialogue
The LPM
can use either CAN 2.0A “basic” format with 11 bit identifiers, or CAN2.0B “extended frame”
format with 29 bit identifiers.
6.4.2.2.2 CAN2.0B and J1939
The default 29 bit format is designed to be compatible with the J1939 standard. It should also be
possible to use the LPM with any system that permits arbitrary raw CAN-bus 2.0B identifiers to be
received.
The dialogue shows the default CAN-bus settings. The LPM transmits all data using a range of message
identifiers star
ting at that selected. If the “Use Defaults” button is pressed, the program constructs an
identifier suitable for J1939 (i.e. this will use PGNs within the region allocated to proprietary applications,
starting at 0x00FFB53F).
At the end of each test, the LPM
will generate a “test result codes” message using the selected CAN-bus
identifier.
On a J1939 network the test result will appear as PGN 0x00ff00. Users not using J1939 can simply listen
for messages with the identifier shown in the dialogue, e.g. 0x18FFB53F.
6.4.2.2.3 CAN2.0A and CanOpen
The 11 bit format is designed to be compatible with the CanOpen standard. It can also be used with any
system that allows raw CAN-bus 2.0A identifiers to be received.
In order to use 11 bit identifiers (CAN 2.0A) se
t a value below 0x7ff for the “Base Address”.
For a CanOpen network, use a base address of 0x182 for example. This will result in message IDs
corresponding to the CanOpen ``pre-
defined connection set’’.