Skip to main content

Convert Between CAN and CAN FD Protocols

Use MicroPeckerX InstaGW to convert between CAN and CAN FD communication protocols.

Usage Example​

Protocol conversion example

A protocol gateway is configured between Ch1 (CAN FD) and Ch2 (CAN). The GW setting file example is shown below.

Common Settings​

Com Sheet​

Com sheet example
  • Configure the baud rates for Arbitration Part and Payload Part for each channel. In this example, Ch1 is CAN FD and Ch2 is CAN.
  • When using Immediate GW, Immediate GW Protocol defines the protocol for each channel. In this example, Ch1 is CAN FD and Ch2 is CAN.

When Using Immediate GW​

Immediate GW Sheet​

Immediate GW sheet example
  • Immediate GW provides low-latency gateway operation[*].
  • Set target CAN IDs for protocol gateway on each channel. In this example, target CAN IDs are 200, 201, 202 for 1->2 (CAN FD->CAN), and 100, 101, 102 for 2->1 (CAN->CAN FD).
  • Immediate GW supports up to 32 CAN IDs.

[*]: Gateway latency is approximately 3.5 us (measured with CAN FD communication: arbitration phase 500 kbps, data phase 2 Mbps).

When Using Standard GW​

Gateway Sheet​

Gateway sheet example
  • Standard GW[*] supports ID replacement and transmission timing control.
  • Configure target CAN IDs for gateway on each channel. In this example, 1->2 (Ch1->Ch2) is configured as CAN FD->CAN protocol conversion.
  • ID replacement is also configured, for example CAN ID 200 -> CAN ID 180.
  • For Ch1 CAN IDs 200, 201, 202, 203, a 5 ms delay is added before forwarding to Ch2.
  • Standard GW supports up to 64 CAN IDs.

[*]: Gateway latency is approximately 12.5 to 20 us (depends on data length), measured with CAN FD communication (arbitration phase 500 kbps, data phase 2 Mbps).

Immediate GW and Standard GW​

Immediate GW and Standard GW can be used together.

Immediate GW supports up to 32 CAN IDs, and Standard GW supports up to 64 CAN IDs. By combining them, up to 96 CAN IDs can be configured.