Home

Welcome to the Automotive Message Broker wiki!

Automotive Message Broker (AMB) is a framework for getting data from a vehicle network (ie, CAN) to applications in a secure and flexible API. This allows automotive applications to target one API and work on several vehicles across multiple vehicle vendors, models and trims.

Core Features:

• Multiple plugin architecture.

Similar to "gstreamer", AMB has a source and sink plugin architecture. Sources provide data from a "device" (device being a vehicle network or other device). Sinks consume the data and do interesting things with it. Multiple sources and sinks can be used simultaneously. There are a number of example configurations in the source.

• DBus Interface

The DBus interface allows applications written in any language that supports DBus to use data from AMB. It also allows automotive vendors to protect data so that only authorized applications can read and write to the data. Documentation for the DBus interface can be found here.

• Peer-to-peer interface

AMB comes with a plugin that uses websockets so that multiple instances of AMB running on different physical machines can be chained together and share data.

• Numerous plugins to make testing and development easy

The list of plugins is growing, but here are just few:

• database plugin, logs cutomizable data and can play it back later.
• gpsd plugin, uses "gpsd" to provide location data
• obd-II plugin, gets vehicle data from standard OBD-II.
• opencv plugin, uses opencv to simulate brightness
• wheel plugin, uses the Logitech G27 racing wheel to simulate data

Links

Here are some useful links for more information about using and developing AMB:

• AMB readme
• Development TODO
• AMB Mailing list