Request for Comments - introduction to OEM integration

Added by Jakob Eriksson over 3 years ago


I am writing this after some discussion here at VCE.


The documentation of AGA can of course be improved, but it's quite good from an application developers perspective.

However, if AGA is going to get some traction, AGA needs to adopted and used by OEMs, such as ourselves. (Volvo Construction Equipment.)

To use AGA, an OEM needs to implement for instance the VIL components. Currently, we can't find much on how to do this.

We realize, that this is a responsibility of the OEM.

Yet, there is a huge difference between having a simple, example implementation to modify and extend, vs. having to implement it from scratch.

In my humble opinion, there would ideally be both an example (reference) implementation in git, and a how-to on the wiki: "How to implement OEM components in AGA".

 

Replies (1)

RE: Request for Comments - introduction to OEM integration - Added by Jonas Berg almost 3 years ago

We have implemented an AGAAdapter tool that converts messages from the MQTT protocol to the SDP protocol, for experimenting with the AGA framework. Prototyping is very easy when using MQTT, in part due to the availability of open source MQTT libraries, brokers and command line tools. 

You can have a look in the source to understand how to do SDP communication (and using SCS data types) with the AGA framework.

To verify the AGA infotainment system and the TCP/IP connection to it, a vehicle mock utility (sends vehicle signals) is included. It will send SDP messages (scriptable) to the AGA infotainment system, and display SDP messages sent from the AGA infotainment system.

In order to verify the functionality of this tool, the infotainment mock utility (included) can be used. It is an command line utility that mimics the infotainment system from a SDP communication point of view. It will print out received SDP messages (and is able to send SDP messages).

See https://github.com/caran/AGAAdapter

(1-1/1)