The dev toolchain underneath Wayne AI and FleetConnect — the same one our team uses to integrate diesel, BEV, hydrogen, and hybrid powertrains. AI-assisted DBC generation, full SAE J1939 decode, automated trace analysis, 100K+ DTC reference, product composition, and a full REST API.
Every tool is callable from the REST API. Every artifact — DBC, trace, product, signal — is versioned and addressable. The same workbench Wayne reasons over.
AI-assisted DBC generation, editing, and validation. Multi-source merge, conflict resolution, bit-level signal packing diagrams.
DBC Tools →Full SAE J1939 library built in. Multipack BAM/CTS decode, DM1/DM2/DM4 active faults, engine-grade signal interpretation.
J1939 Library →Drop a trace file. Get decoded signals, timeline plots, and statistical + ML anomaly flags — automatically.
Trace + Timeline →100K+ DTC definitions across 40+ manufacturers. Generic + manufacturer-specific. AI lookup in one click.
DTC Reference →Compose products from CAN signals, DTCs, and OEM PIDs. JSON product definitions, versioned, validated, QA configs per device.
Product Builder →Full REST API. Every artifact in the workbench is API-accessible — including POST /wayne/ask for conversational reasoning.
Pinouts for J1939, OBD-II, NMEA 2000, ISOBUS, ISO 7638 and more, each checked against at least two published sources, with an interactive wiring converter, connector finder and bus calculators.
CAN Connector Guide →Authentication, pagination, and webhooks documented in the full API reference.
# Compose a product from signals + DTCs POST /products GET /products/{id}/things # Decode a trace file with applied DBCs GET /traces/{id}/decode # Look up any fault code across 40+ manufacturers GET /dtc/lookup?code=P0420 # Read every signal off a deployed device GET /things/{id}/signals # Ask Wayne in plain English POST /wayne/ask
If you're an OEM integrating telematics into a vehicle program, or a fleet engineering team that needs to own its CAN integration end-to-end — talk to us.
Talk to Engineering →