The vehicle has to decide in milliseconds, every time, for the life of the program.
Perception, sensor fusion and motion control for electrified and off-road vehicles, engineered for deterministic response and supported from the United States.
What it costs you
Where vehicle programs lose time and money on compute.
Average latency is the wrong number
A control loop that is fast on average and slow once an hour cannot be signed off. In a vehicle, the worst case sets the requirement.
Controllers multiply
Each added function tends to arrive with its own controller, enclosure, harness and software stack to validate. The bill of materials grows faster than the feature list.
Support has to outlast the model year
Programs run for years after launch. A supplier whose engineers sit several time zones away turns every field issue into a scheduling problem.
Runs on: AMD Kria KD240 and K26 modules.
What it looks like in practice
- SenseWheel, inertial, camera and driver inputs
- FuseOne consistent vehicle state
- EstimateGrip, load and intent
- CommandDrive, brake and steering requests
- LogSignals for calibration and validation
Logged drive data feeds calibration and validation for the next software release.
Evidence
Automotive case study coming soon
Details of our current automotive work will be published here soon.
Nyx IndustriesThe first step
A fixed-price architecture phase against your vehicle, ending in a frozen interface baseline and a firm price for the build.
NYX