Open AD Kit integration

[ZaynabEM]

Greetings,

While exploring the integration of OpenAD Kit v3.0, I encountered multiple problems with the documentation:

1. Several links return 404 errors or contain TODO placeholders.
2. The container image reference in the docs points to autoware-openadk package, which is not accessible.
3. AVA advanced setup Advanced setup for AVA Platform, also not accessible.

I checked the following references :

• https://learn.arm.com/learning-paths/automotive/openadkit1_container/
• https://autowarefoundation.github.io/open-ad-kit-docs/openadkit_v3/version-3.0/start-guide/
• https://github.com/odincodeshen/openadkit_demo.autoware
• https://ieeexplore.ieee.org/document/8443742
• https://autowarefoundation.github.io/autoware-documentation/pr-347/how-to-guides/integrating-autoware-with-your-vehicle/
• https://www.adlinktech.com/Products/Computer_on_Modules/COM-HPC-Server-Carrier-and-Starter-Kit/Ampere_Altra_Developer_Platform
• https://autowarefoundation.github.io/autoware_universe/main/vehicle/autoware_raw_vehicle_cmd_converter/

and I understand that Integration steps are :

1. Hardware bring-up (AVA ADLINK + EWAOL): boot, kernel/driver enablement, networking.
2. Containers: pull/run images for Autoware.Universe, Scenario Simulator, and demo components.
3. Sensing integration:

• LiDAR (required)
• IMU, camera, GNSS (optional)
• Install drivers, configure rates, set frame IDs.

5. Actuation integration (vehicle interface):

• Adapt Autoware command topics (/control/command/control_cmd) to ECU/drive-by-wire inputs (steering, throttle, brake).
• Map ECU feedback to Autoware status topics (/vehicle/status).

6. Time sync: configure PTP/NTP across ECU, sensors, and host.
7. Calibrations: extrinsics (LiDAR↔IMU↔Camera), ego parameters, wheelbase, offsets.
8. Maps: build HD map for the target area and load into the stack.
9. Localization + Planning/Control: configure launch profiles and parameters for the vehicle.
10. Validation path: sim-in-the-loop → bench/HIL → on-road.

Could anyone clarify whether the missing documentation and resources are intentional placeholders or if updated versions are available elsewhere? In particular:

1. Is there an updated version of the documentation planned, and if so, is there a release timeline?
2. Are the container images and related resources going to be published publicly, or are they still in development?

Thank you in advance for the clarification.

[idorobotics]

@oguzkaganozt could you assist with this?

[rt-2pm2]

Hi @ZaynabEM, I also got stuck with the old documentation in the past. If I am not wrong, in the OpenADKit WG they were discussing about removing it, but it's still there and users get entangled.

Anyway, I think @oguzkaganozt can add more details regarding this, but I can try to help by pointing out to the new source of documentation for OpenADKit at: https://autowarefoundation.github.io/openadkit/
They are working on that actively.

I was also interested in getting more low-level details about the AmpereAltra Develeopment Platform (AADP) + EWAOL setup and the OpenADKit orchestration with XEN, but I think it's still an ongoing work.

Best

[oguzkaganozt]

Hi @ZaynabEM and @rt-2pm2, thanks for questions and the feedback. Regarding your points:

• Open AD Kit v3.0 documentation is now obsolete and the new documentation page is live on Open AD Kit. The links from main web page and autoware documentation will be updated accordingly.

• AVA ADLINK + EWAOL setup with detailed instructions will be available soon under the Hardware and Platforms section of the new documentation.

• All of these updates are expected to be released by the end of this month.

• In the meantime you can check out the new Open AD Kit repo and the documentation, where you can find basic demos for launching Open AD Kit containers.

Best