FOR BUILDERS
Build the motorcycle.
Lose the wiring maze.
NodeIQ is being developed for limited space, mixed signal types, electrical noise, serviceability, and clean packaging—including a future hardwired ignition controller that communicates wirelessly with the central hub.
THE BUILDER WORKFLOW
01 / Define
Choose the bike, engine configuration, signals, telemetry, and future ignition-control requirements that matter.
02 / Wire & place
Mount the hub and wireless nodes, then hardwire the ignition module to power, ground, trigger inputs, and ignition outputs.
03 / Detect & verify
Discover the system, identify engine and trigger configuration, verify signal health, and confirm base timing with proper tools.
04 / Map & validate
Begin from a compatible baseline, apply guarded map changes, and validate operation on the bench, dyno, and road.
FUTURE BUILDER INTEGRATION / IGNITION
One hardwired controller. One wireless system.
Engine-side installation
The ignition module will use dedicated, protected connections to vehicle power, ground, crank or cam trigger signals, and coil or ignition outputs. Wire routing, shielding, grounding, heat, vibration, and service access are part of the installation—not afterthoughts.
Automatic commissioning
The system is intended to identify cylinder count and trigger behavior, then propose a compatible starting configuration. The builder confirms trigger alignment, base timing, coil compatibility, operating limits, and map suitability.
Wireless configuration
Once commissioned, the ignition module exchanges maps, telemetry, and diagnostics with the hub without making the wireless link responsible for spark timing.
Safe service path
Versioned maps, last-known-good fallback, explicit apply and rollback, fault visibility, and documented recovery are planned as core service features.
Ignition work can damage an engine or create unsafe operation if configured incorrectly. Final installation and calibration requirements will depend on validated hardware, the specific motorcycle, and qualified setup.
Designed to work with existing motorcycles
The platform is intended to accept conditioned versions of existing RPM, speed, fuel, and switch signals where practical. High-impedance sensing and robust input protection remain design priorities.
| Older motorcycles | Add data without replacing the machine’s identity |
| Custom builds | Reduce long signal runs and clean up packaging |
| Modern platforms | Extend sensing where isolated add-ons are appropriate |
NodeIQ 