REXDESKREXGEN 1REXGEN 2REXGEN 2 IMU GNSSREXGEN AirREXGEN ProManual

REXDESK: filter CAN IDs, J1939 PGNs and UDS requests

Updated

Record only the CAN messages that matter, by identifier or by J1939 address and PGN. You can also make the logger request diagnostic data from an ECU with UDS.

How filters work

A filter is a pass list. The logger records only the frames that match it and ignores the rest. Use a filter tool on a bus in place of Log All. Smaller logs are quicker to download and to search.

You can still drop Errors on the same bus to record its error frames. For background on filtering, read Understanding message filters in CAN.

CAN ID filters

  1. Create a project. Select New Project on the toolbar.
  2. Drop Filter on the bus. Drag Filter from the CAN group onto the bus you want to log.
  3. Set the bus. Select the Bus icon and set the bus type and bit rate. See REXDESK: record CAN, CAN FD and LIN.
  4. Enter a range. Select the Filter icon on the bus. In the CAN Filter panel, enter the range of identifiers to log in From CAN ID and To CAN ID.
    The filter list with Active, From CAN ID and To CAN ID columns, the CAN Filter panel with From CAN ID and To CAN ID boxes and a browse button, and the DBC message list it opens
    The browse button beside To CAN ID picks identifiers from a DBC file in the library.
  5. Or pick from a DBC. Select the browse button (...) to choose identifiers from a DBC file in the library.
  6. Add the range. Select Add. The range appears in the list. Use the buttons beside the list to add another filter, edit the selected one or remove it.
  7. Set the log files and run. Set Storage and connect the logger over USB. Select Run, then save and name the project. Logging starts at once.

Watch: Set up CAN message filtering in a REXGEN series logger using a DBC file (1:11)

J1939 filters

The J1939 tool filters J1939 frames by source address, destination address and PGN. Use them together or one at a time.

  1. Drop J1939 on the bus. In a new project, drag J1939 from the CAN group onto the bus. Set the bus as above.
  2. Enter the values. Select the J1939 icon. In J1939 Filter Type, tick Source Address, Destination Address or PGN. Enter a value for each one you tick.
    The J1939 Filter Type panel with Source Address 0x12, Destination Address 0x21 and PGN 0x7F ticked, and the resulting filter listed as active on the left
    A filter that passes only frames from source 0x12 to destination 0x21 with PGN 0x7F.
  3. Or pick a PGN from a DBC. Select the browse button (...) beside PGN to choose one from a J1939 DBC.
  4. Add the filter. Select Add. You can add, edit or remove filters in the list.
  5. Set the log files and run. Set Storage and connect the logger. Select Run, then name the project.

Watch: Set up REXGEN series to log data using a J1939 filter (1:32)

UDS requests

The UDS tool makes the logger send diagnostic requests to an ECU over CAN and record the answers. You can then log values that are never broadcast. Drop UDS on a bus to open its Event messages window.

The Event messages CAN 0 window with SINGLE and REPEATABLE sections, two request rows with TX, RX, Delay, Time Out, Attempt, Type, BRS, DLC and Data columns, the Type list open on CAN FD Extended and the DLC list open showing values up to 64
Messages under SINGLE are sent once. Messages under REPEATABLE are sent again and again.

Use Add and Remove on the toolbar to add or delete a message. Use Move Up and Move Down to reorder the list. Each row is one request:

TX
The identifier the logger, acting as the tester, sends the request on.
RX
The identifier the ECU answers on.
Delay
The interval between messages.
Time Out
How long the logger waits for an answer before it treats the request as timed out.
Attempt
How many times the logger repeats the request.
Type
CAN Standard, CAN Extended, CAN FD Standard or CAN FD Extended.
BRS
Bit rate switch. Sends the data phase of a CAN FD frame at the higher bit rate.
DLC
The number of data bytes, from 0 to 8. CAN FD also allows 12, 16, 20, 24, 32, 48 or 64.
Data
The request bytes.

Put setup requests under SINGLE, such as the request that switches the ECU into its extended diagnostic session. Many data identifiers need that session. Put the requests you want logged over time under REPEATABLE.

A UDS session: open, poll, keep alive UDS · ISO 14229 A UDS session: open, poll, keep alive Tester ECU Repeat 10 03 DiagnosticSessionControl: extended session 50 03 … positive response 22 F1 90 ReadDataByIdentifier: DID F190 62 F1 90 … data 3E 00 TesterPresent: keep the session open 7E 00 positive response A positive response is the service ID plus 40 hex (10 to 50, 22 to 62, 3E to 7E). Repeat the read loop for as long as you log, and send TesterPresent before the session timeout (S3, typically 5 s) or the ECU returns to its default session. Physical IDs, for example 7E0 and 7E8.

New to UDS? Read Understanding UDS. To log OBD-II Mode 1 parameters, see REXGEN: log OBD2 Mode 1 PIDs.

Next: REXDESK: log analogue and digital inputs.

Products in this guide

REXDESK

Logger setup & data export

View REXDESK Ask an engineer

REXGEN 1

Vehicle black box

View REXGEN 1 Ask an engineer

REXGEN 2

Evidence data logger

View REXGEN 2 Ask an engineer

REXGEN 2 IMU GNSS

Motion & location data logging

View REXGEN 2 IMU GNSS Ask an engineer

REXGEN Air

CAN to cloud

View REXGEN Air Ask an engineer

REXGEN Pro

Edge data platform

View REXGEN Pro Ask an engineer

Still stuck?

Our engineers answer support questions on every Influx Technology product.