RaceOps SIM2CAN
A standalone browser-based CAN bus and sim racing bridge for connecting real motorsport CAN hardware to PC simulator titles.
RaceOps SIM2CAN connects steering wheels, dashboards, ECUs and dataloggers to simulator inputs, and can also send live sim telemetry back out to real CAN devices. It also works as a virtual CAN workbench, allowing engineers, rig builders and educators to design, validate and test CAN setups without hardware connected.
RaceOps SIM2CAN is part of the RaceOps software family, but it uses a standalone architecture and does not share the connected RaceOps operational database.
CAN testing should not depend on guesswork, hardware delays or hand-decoded payloads
Motorsport-grade simulator builds often need to connect real CAN devices to PC sims, virtual controllers, dashboards or data systems. That usually means juggling hardware adapters, DBC files, payload decoding, virtual joystick drivers, sim telemetry and safety risks. RaceOps SIM2CAN puts the workflow into one structured browser-first workbench.
Built for technical motorsport users
Standalone architecture inside the RaceOps family
RaceOps SIM2CAN sits inside the RaceOps family but runs on its own architecture — separate from the shared operational database used by the connected RaceOps apps.
RaceOps Assist, Quote, Logistics, Scenario and Driver are connected operational apps that share a common database for clients, projects, assets, events, drivers, support activity and reporting.
shared operational database
RaceOps SIM2CAN is a specialist technical workbench with its own standalone architecture. It is built for CAN bus, DBC files, local bridge communication, virtual HID, SimHub telemetry and bench-testing workflows.
The main interface runs in a modern browser. DBC files, profiles and mappings live in SIM2CAN's own standalone data store and are not synced with the connected RaceOps operational database.
- ›TanStack-style browser UI
- ›Supabase-backed account sync
- ›Guest mode for friction-free exploration
- ›Cloud-synced DBCs, profiles and mappings
A lightweight local PC agent exposes http://localhost:42700 using HTTP and WebSocket. It handles the USB/CAN drivers and virtual HID drivers that the browser cannot access directly.
- ›Local HTTP and WebSocket bridge
- ›PEAK PCAN support
- ›Kvaser support
- ›CANable and SLCAN support
- ›vJoy support
- ›ViGEm support
- ›Virtual HID handling
Core capabilities
Detect live CAN frames from real hardware and map changing signals to virtual controller inputs for simulator use.
- ›Live bridge status with heartbeat
- ›Adapter and bitrate selection
- ›Listen-only safe default
- ›Live CAN frame table
- ›ID filtering
- ›DBC-decoded overlay
- ›Input detection wizard
- ›Virtual joystick test panel
- ›Axis and button mapping table
Transmit simulator telemetry to real dashboards, ECUs and dataloggers using scheduled CAN frames.
- ›Transmit CAN frames on schedule
- ›Cycle time from DBC or custom value
- ›Per-stream enable and disable
- ›SimHub shared-memory viewer
- ›Live telemetry to outgoing CAN streams
- ›Safety banner and TX state pill
- ›Explicit confirmation before sending
Import, inspect, validate, decode and encode DBC files without needing heavyweight desktop tools just to understand a CAN database.
- ›Import .dbc files up to 5 MB
- ›Parse VERSION, BU_, BO_, SG_, CM_ and GenMsgCycleTime
- ›DBC library with active, archive and duplicate states
- ›Pretty-printed read-only viewer
- ›Sortable and filterable messages table
- ›Sortable and filterable signals table
- ›Start bit, length, factor, offset, min/max, unit, byte order and multiplexing views
- ›Interactive decode and encode
- ›Validator for overlapping signals, missing units, out-of-range factors and unreferenced nodes
- ›Import summary with message and signal counts
- ›Usage view showing profiles, streams and mappings linked to each DBC
Design and test CAN setups with zero hardware connected using a virtual engine that drives the same code paths as a real adapter.
- ›60Hz requestAnimationFrame simulation engine
- ›GT3-style telemetry
- ›Speed, RPM, throttle, brake, gear and steering
- ›One-lap replay
- ›Realistic corner curves
- ›Timeline scrubbing
- ›0.25x to 4x playback speed
- ›Loop mode
- ›Raw frames and DBC-decoded signals side by side
- ›Reproduce edge cases at a known timestamp
Bundle devices, DBCs, mappings and virtual controllers into profiles so different cars, rigs and test benches can be switched quickly.
- ›Profile-based configuration
- ›Device registry
- ›DBC assignment
- ›Mapping bundles
- ›Virtual controller declarations
- ›vJoy, ViGEm and HID options
- ›Button and axis counts
- ›Debounce settings
- ›Import and export profiles
- ›Export debug bundles as JSON
- ›Protocol-level debugger panel
SIM2CAN is designed for simulator and bench-testing workflows with clear safety defaults and guided help throughout the interface.
- ›Global app defaults
- ›Bridge URL settings
- ›Heartbeat and timeout settings
- ›CAN adapter defaults
- ›Virtual controller driver defaults
- ›Default-deny TX
- ›Confirm-before-send
- ›Require-profile-for-TX
- ›Listen-only by default
- ›Dedicated Help and Guides tab
- ›Contextual red information icons
- ›Troubleshooting and glossary support
Why RaceOps SIM2CAN is different
No heavyweight desktop app beyond a small local bridge.
Use the virtual CAN engine to design, test and demo before connecting devices.
Parse, validate, decode, encode and share DBC data in the browser.
Use real CAN devices as simulator input, or drive real dashboards from simulator telemetry.
Use SimHub-supported titles as a source for outgoing CAN telemetry.
Listen-only mode, default-deny transmit and explicit confirmation before sending.
Swap complete rig, car or bench-test configurations in one click.
A specialist RaceOps app with its own architecture, kept separate from the shared operational database.
From CAN device to simulator, or simulator to dashboard
Why SIM2CAN is standalone
RaceOps SIM2CAN works close to the user's local machine, CAN adapters, virtual HID drivers and simulator telemetry sources. Because it needs a local bridge, driver access and specialist CAN workflows, it is designed as a standalone RaceOps app rather than part of the shared operational database used by the other RaceOps apps.
SIM2CAN relies on a local bridge to communicate with CAN adapters and virtual HID drivers.
DBC files, CAN signals, payloads, mappings and telemetry streams are different from the operational records used by the other RaceOps apps.
Transmit controls, listen-only defaults and bench-testing workflows are kept separate from the shared operational app database.
Built for the details engineers care about
RaceOps SIM2CAN screenshot galleries
Each gallery uses the RaceOps screenshot carousel — upload screenshots, set titles, captions, alt text and sort order. Desktop and tablet open large floating previews; mobile uses a full-screen viewer.