Proprietary CAN Signal Decode
Off-the-shelf DBC files cover the standard PGNs. But the OEM-specific proprietary signals — the ones that actually matter to your project — aren’t in any public database. We reverse-engineer them.
Tell us what you need decoded. We’ll review and let you know how we can help — no obligation.
Igor Ramos — 10+ years in CAN-based systems. Technical Leader for Caterpillar’s paver product line. 8 CAN-specific patents. Built the PGN Calculator and Live Analyzer used by thousands of engineers every month.
The Problem
The SAE J1939 Digital Annex defines roughly 2,000 standard PGNs. Commercial DBC files cover these well. But real-world CAN traffic is 20–40% proprietary — OEM-specific PGNs (PF=0xEF for Proprietary A, PF=0xFF for Proprietary B) that carry the signals you actually need: engine protection parameters, aftertreatment status, machine-specific sensor data, OEM diagnostic codes.
No public database has these. No DBC file you can buy includes them. They’re defined by each manufacturer for their own ECUs and kept proprietary.
That’s what we decode.
What You Get
You know the PGN and ECU but not what the bytes mean. We identify every signal: scaling factors, offsets, units, and valid ranges.
Full decode package: every proprietary PGN mapped with bit positions, resolution, range, and engineering units. Drop it into CANalyzer, SavvyCAN, PCAN-View, or your telematics platform.
DBC delivery plus hands-on help integrating decoded signals into your diagnostic tool, telematics gateway, or data pipeline.
How It Works
You Send CAN Traces
Raw CAN logs captured under known physical conditions. Idle, 1500 RPM, full throttle, specific operating modes. The more varied the conditions, the faster we correlate signals to physical values. We’ll tell you exactly what to capture.
We Decode the Signals
We analyze traffic patterns, correlate byte-level changes with physical behavior, and identify signal definitions — bit positions, scaling, offsets, units, enumerations.
Validate & Deliver
We verify every decoded signal against your real-world data before delivery. If more captures are needed, we’ll request specific conditions. The cycle repeats until the decode is confirmed.
Every project is scoped individually
The scope depends on how many ECUs, how many proprietary PGNs, and what capture data you already have. Tell us what you need and we’ll propose a fixed-price engagement.
Who Needs This
Your platform shows unknown PGNs from OEM ECUs. You need the signal definitions to build dashboards, alerts, and predictive maintenance.
You’re building hardware that reads OEM-specific signals. We decode the proprietary messages so your device speaks the right language.
Your scan tool handles standard J1939 but misses manufacturer-specific parameters. We fill in the gaps with validated signal definitions.
You have terabytes of CAN logs but 30% of the data is proprietary and unlabeled. We decode it so you can build models on complete datasets.
Frequently Asked Questions
What data do I need to provide?
Raw CAN traces (log files) captured under known physical conditions. Example: traces at idle, at 1500 RPM, at full throttle, with AC on vs off, during a regen cycle. The more varied the conditions, the faster we correlate byte changes to physical values. We’ll send you a capture guide.
What format do you deliver in?
DBC file (compatible with Vector CANalyzer, SavvyCAN, PCAN-View, and most telematics platforms), plus a human-readable signal map documenting bit positions, scaling, offset, valid range, and units for every decoded signal.
How is this different from buying a J1939 DBC file?
Commercial DBC packs (like CSS Electronics’ J1939 database) cover the publicly-defined standard PGNs — excellent for that purpose. But they don’t include proprietary signals. The OEM-specific data that makes up 20–40% of real-world CAN traffic is what we decode. We complement off-the-shelf DBC files, not replace them.
Can you decode any manufacturer’s signals?
CAN is CAN. Whether it’s Caterpillar, John Deere, Volvo, AGCO, Cummins, or any other OEM — the reverse engineering method is the same. We’ve decoded signals across heavy equipment, agricultural, marine, automotive, and industrial automation.
Do you sign NDAs?
Yes. We regularly work under NDA for fleet operators, OEMs, and aftermarket companies. Enterprise engagements include full compliance with your procurement and legal processes.
What about J1939 Proprietary A vs Proprietary B?
Proprietary A (PGN 61184, PF=0xEF) is peer-to-peer and uses the destination address to identify the message. Proprietary B (PGNs 65280–65535, PF=0xFF) is broadcast. Both require knowing the source ECU and manufacturer to decode. Our PGN Calculator detects both types and links here when it identifies a proprietary PGN.
Limited availability: I take on 2–3 decode engagements per month to ensure thorough validation of every signal.
Every unknown signal is data you’re leaving on the table.
Tell us what you need decoded. We’ll review and let you know if we can help.
Need general CAN diagnostics instead? View consulting services → | Try our free PGN Calculator