eeTimes eeTimes EDN
Forgot password Register
Print - Send - -


Bridging the chasm between HTML5 and the hardware with PPS messaging

May 16, 2012 | Andy Gryc, QNX Software Systems | 222902243
Bridging the chasm between HTML5 and the hardware with PPS messaging Human-Machine Interfaces (HMIs) developed with HTML5 reside in a high-level, virtualized environment, and they work well in this environment. This fact does not preclude their needing to access hardware, however. In mobile devices, for example, they need to retrieve the device orientation and, if there are GPS or accelerometer chips, information these chips provide for applications that use geo-location. In-vehicle systems need to retrieve even more information from low-level components such as the CAN bus, GPIO pins, and I2C and SPI devices.
Page 1 of 7

Writing specific interfaces to communicate between the HMI and each low-level service is a costly—and likely unsustainable—proposal. A better approach is to use an HMI-agnostic, asynchronous messaging model such as Persistent Publish/Subscribe (PPS). A service for pushing out changes and receiving notifications, PPS provides a simple and effective way for the HMI to communicate with low-level componentst and the vehicle hardware.

Fig. 1:  HTML5 usually refers to HTML5 proper, plus ancillary standards and technologies such as CSS3 and JavaScript 

Drawing on our experience building in-vehicle systems, we will describe how a PPS messaging model facilitates communication between an HTML5 HMI and low-level components.

The problem

A problem facing developers of almost all but the simplest systems is the increasing diversity and complexity of components at all levels. On the one hand, an automotive infotainment system integrate many devices and services—from multimedia players to virtual mechanics; on the other, pressures such as release schedules, budgets and re-usability needs have made HMI development in native C/C++ code prohibitively expensive and too time-consuming. HTML5 and its ancillary technologies (CSS3, JavaScript, AJAX, JSON, etc.) offer an excellent, non-proprietary solution for building rich, device-agnostic HMIs. Unfortunately, like other high-level HMI technologies, HTML5 doesn't offer a simple solution for communicating between the HMI layer and the many low-level components found in today's systems.

1 | 2 | 3 | 4 | 5 | 6 | 7 | Next page

Please login to post your comment - click here
Related News
    No news
Technical papers
Which approach is best suited for automotive infotainment connectivity?