(→nobdy) |
(→nobdy) |
||
| (One intermediate revision not shown) | |||
| Line 1: | Line 1: | ||
| - | + | This article describes applications that do automotive networking. | |
== nobdy == | == nobdy == | ||
| - | One application that provides an application API to access vehicle data and even control certain things in the vehicle is [http://wiki.openice.org/index.php?title=Nobdy nobdy]. nobdy works by exposing a dbus interface to applications for access to common vehicle services often found in modern vehicles. Through this API, applications can gain access to controls like door locking and extract information such as velocity, fuel economy, etc. The vehicle service API is very much a work in progress and may be extended to meet future needs. | + | One application that provides an application API to access vehicle data and even control certain things in the vehicle is [http://wiki.openice.org/index.php?title=Nobdy nobdy]. nobdy works by exposing a dbus interface to applications for access to common vehicle services often found in modern vehicles. Through this API, applications can gain access to controls like door locking and extract information such as velocity, fuel economy, etc without knowledge of the underlying network topology or protocol. The vehicle service API is very much a work in progress and may be extended to meet future needs. |
nobdy also exposes a lower level API where applications can "subscribe" to specific bus messages. | nobdy also exposes a lower level API where applications can "subscribe" to specific bus messages. | ||
| Line 9: | Line 9: | ||
nobdy is listed as a feature in MeeGo IVI: [https://bugs.meego.com/show_bug.cgi?id=8822 FEA #8822] | nobdy is listed as a feature in MeeGo IVI: [https://bugs.meego.com/show_bug.cgi?id=8822 FEA #8822] | ||
| + | |||
| + | [[Category:IVI]] | ||
This article describes applications that do automotive networking.
One application that provides an application API to access vehicle data and even control certain things in the vehicle is nobdy. nobdy works by exposing a dbus interface to applications for access to common vehicle services often found in modern vehicles. Through this API, applications can gain access to controls like door locking and extract information such as velocity, fuel economy, etc without knowledge of the underlying network topology or protocol. The vehicle service API is very much a work in progress and may be extended to meet future needs.
nobdy also exposes a lower level API where applications can "subscribe" to specific bus messages.
nobdy provides a 3rd party plugin API so that OEMs can create vehicle-specific "providers" for their vehicles. This also puts the burden of security on the OEM to protect sensitive bus messages.
nobdy is listed as a feature in MeeGo IVI: FEA #8822