Every autonomy developer has a stack. It is the software that sees, decides and drives. Teams spend years building it, and no two are alike.
Hardware that goes on an autonomous vehicle has to answer one question first. Will it work with our stack?
A lot of vehicle hardware is a closed box. It does its own thing with its own logic. The stack cannot see inside it and cannot tell it what to do. The developer has to work around it.
AdaptiveMotion™ is the opposite. It is fully open architecture.
That means three things are open to the autonomy stack.
- Control. The stack can command the suspension directly.
- Height. The stack can set ride height for the ground ahead.
- Telemetry. The stack can read what the suspension is sensing, 1,000 times a second.
None of it is locked away. That is the point.
It also means AdaptiveMotion™ does not care whose stack it is. It is not tied to one autonomy provider. It reads the terrain, feeds back to the AV vision stack and responds to it.
Open programming is standard on every active system. For teams that want more, Patriot Dynamic Systems' R&D group works with the customer to build custom programming, so the vehicle does exactly what the mission needs.
Think about how a stack treats the other controls. It does not ask the steering for permission. It sends a command, and the steering does it. Braking and acceleration work the same way.
Suspension should work that way too. The stack sees a side slope, a ledge or a rough stretch coming. It should be able to tell the suspension what to do about it, and then hear back how it went.
A closed suspension is a passenger. An open one is part of the team.
Keep the vision horizon. Protect the stack. Get through with redundancy.
See videos and more on our AV platform at patriotdynamicsystems.com.
Join the conversation