FC-501 reads J1939, CANopen and raw CAN on two buses (expandable to four), turns frames into named signals on the device, and ships them to iMatrix Cloud over LTE or Starlink. It runs on programmable Linux, and you push configuration to deployed vehicles over the air.
A raw frame logger leaves the hard part to you: multipacket reassembly, fault decoding, signal scaling and keeping firmware current on vehicles you can't reach. FC-501 handles each of those on the gateway.
Two CAN ports built in, running J1939, CANopen or RAW on each. The CAN Expansion Module adds two more for a separate battery, body or implement network. An RS-232 port handles legacy serial ECUs.
Messages longer than 8 bytes arrive as BAM broadcasts or RTS/CTS sessions. The gateway reassembles them at the edge, so long DM messages and component IDs reach the cloud intact, with no partial decodes.
DM1 active, DM2 previously active and DM4 freeze-frame data are decoded and interpreted. "FMI 5: current below normal" replaces "0x05", and the fault goes to the maintenance queue as an event.
An industrial Linux gateway with 128 MB RAM, 128 MB flash (512 MB available) and Secure Boot support. OEMs and integrators build on the FC-501 OEM program rather than a closed black box.
Hotfix a DBC, regenerate the configuration in Workbench and push it OTA to every deployed FC-501. Firmware and service governance run from iMatrix Cloud, with no truck roll.
A decoder compiled from your DBC runs on the device. Only named, scaled signals go upstream, which keeps cellular usage low and the cloud schema clean from the first message.
FC-501 takes 9–32 VDC vehicle power and connects to the CAN buses directly, with no OBD-II port required. That suits Class 7/8 trucks, off-highway machines and EV battery networks.
The built-in J1939 SAE library covers the standard PGN/SPN catalog. Manufacturer-specific PGNs (Cummins, Detroit Diesel, Volvo, PACCAR and others) layer on top, and DBC import covers everything proprietary.
LTE Cat-1 (18 bands) with 3G and 2G fallback on the EdgeUplink eSIM. Where cellular doesn't reach, the FC-501-SAT variant adds integrated Starlink.
Wayne AI is standard on the FC-501 at no extra licensing fee. It maps J1939 and CAN signals 340× faster than manual reverse engineering and answers fleet questions in plain English.
| CAN | 2 ports standard (J1939, CANopen, RAW); 4 with the CAN Expansion Module ($130, SKU FC-501-CANX) |
|---|---|
| Serial | RS-232 |
| Cellular | LTE Global Cat-1 (18 bands) · 3G fallback · 2G quad band |
| Satellite | FC-501-SAT variant with integrated Starlink |
| GNSS | Concurrent GPS / GLONASS / BeiDou / Galileo |
| Local connectivity | BLE 4.1 sensor bridging · Ethernet · GPIO |
| Compute | Linux · RAM 128 MB · Flash 128 MB (512 MB available) · Secure Boot support |
| Motion | 6-axis gyro + accelerometer: impact, tilt, roll and tamper events |
| Power | 9–32 VDC · optional 150 mAh battery assist for ignition-off and power-loss reporting |
| Environmental | IP67 · SAE J1455 · −30 °C to +70 °C |
| Price | $500 single-unit MSRP · volume pricing on request |
Full datasheet on the FC-501 product page.
Not every heavy vehicle needs a programmable gateway. Here's how the J1939-capable FleetConnect devices line up.
| FC-202 Rugged Hardwired | FC-501 Industrial Gateway | FC-502 5G Gateway | |
|---|---|---|---|
| Best for | Fleets that want location, J1939 data and alerts, with no development work | Fleets, integrators and OEMs that need multi-bus decode and their own logic | OEM and heavy-equipment programs that need more radio, buses and compute |
| CAN buses | J1939 | 2, expandable to 4 | 4 built in |
| Programmable | No Linux app development required | Linux, fully programmable | Multi-core edge compute |
| Cellular | LTE Cat 1 | LTE Cat-1 + 3G/2G · Starlink option | 5G RedCap + LTE Cat 4 fallback |
| Power | Hardwired vehicle power | 9–32 VDC | 9–48 VDC (48 V EV systems) |
| Pricing | Contact sales | $500 MSRP | Contact us |
| View FC-202 → | View FC-501 → | View FC-502 → |
A J1939 gateway connects to a heavy-duty vehicle's SAE J1939 CAN network, decodes its parameter groups (PGNs) and suspect parameters (SPNs), and forwards the data to another system, usually a cloud platform over cellular. A telematics-grade gateway also reassembles multipacket messages, decodes diagnostic messages such as DM1, and can be updated remotely.
Yes. DM1 (active), DM2 (previously active) and DM4 (freeze frame) messages are decoded, and Failure Mode Identifiers are translated into plain-language failure types that arrive in iMatrix Cloud as events.
The FC-501 is a programmable Linux gateway. OEMs and integrators develop on it through the FC-501 OEM program: an SDK Kit, developer seats and production plans. See OEM Embedded Telematics.
Over the air. Workbench builds a configuration from your DBC and pushes it to deployed FC-501 units through iMatrix Cloud, which also governs firmware updates.
Yes. Every bus runs J1939, CANopen or RAW, so one gateway can read the OEM J1939 network and your own CANopen network at the same time. Proprietary signals are decoded from a DBC file.
The FC-501-SAT variant integrates Starlink for remote sites. Every plan includes the EdgeUplink eSIM with Zone 1 (Europe) and Zone 2 (North America & more); other zones are available on request.
See your J1939 data in iMatrix Cloud.
Tell us what you run and a telematics engineer will walk you through the right gateway, plan and integration.