WIRED Autopia slips into driver's seat of QNX reference vehicle

Chances are, you've seen pictures of the new QNX reference vehicle. You may have even seen the "making of" video that QNX released a few days ago. But have you seen any video of the vehicle in action?

If not, check out this vid by Doug Newcomb of WIRED Autopia. Last week, at Telematics Detroit, Doug met up with Andrew Poliak of QNX for a tour of the vehicle and its various features, including a re-skinnable UI and voice-controlled Facebook integration. The camera was rolling, and here's what it caught:


 

The making of the QNX reference vehicle: Jeep Wrangler

Guest post from Nicole Forget of QNX Software Systems

Nicole Forget

Just one week ago, our new reference vehicle was revealed at Telematics Detroit 2012. The Jeep Wrangler features QNX’s digital instrument cluster, which is totally re-skinnable. In fact, the entire user interface of the head unit, which was created using HTML5, can also be re-skinned. The head unit supports loads of functions, too, including the virtual mechanic, which are outlined in an earlier post.

The following video gives you some insight into the hard work that was put into the making of the reference vehicle. Check it out!


 

Moving beyond the browser: HTML5 as an automotive app environment

If you’ve already visited this blog, you’ll know that we are bullish on HTML5 as a way to implement infotainment system HMIs. Not surprisingly, I’ve spent a fair amount of time searching the Web for facts and opinions on using HTML5 in the car, to see how this idea is catching on.

Overall, people see numerous benefits, such as the ability to leverage mobile app development to keep pace with the consumer demands, the availability of a large pool of knowledgeable developers, and the attractiveness of a truly open specification supported by many possible vendors.

But when it comes to the challenges of making HTML5 a reality in the car, I found a common thread of questions, mostly rooted in the erroneous belief that an HTML5 application environment is “just a browser.” Everyone is familiar with the concept of a browser, so it’s easy to see why people take this point of view.

So what are the key differences between a browser and an HTML5 application environment? Here’s my quick view.

The experience
Everyone is familiar with the browser experience. You navigate to a web site through bookmarks, a search engine, or direct entry of a URL. The browser implements a user interface (aka the chrome) around a rendering engine and provides bookmarks, URL entry, back and forward, scrolling and panning, and other familiar features.

An automotive HMI based on HTML5 provides a different experience — just look at the accompanying screen shots and decide for yourself if they look like a browser. In fact, the user experience of an HTML5-based HMI is similar to that of any other purpose-built HMI. It can consist of a main screen, window management, navigation controls, and other typical user interface widgets.


A radio tuner and a media player from the QNX CAR 2 application platform. Both apps are based on HTML5, but beyond that, they neither act nor look like a web browser.

A system that uses an HTML5-based HMI can include:

• core applications that look and act like native applications
   
• add-on (downloaded and installed) applications that have controlled interfaces to the underlying hardware
   
• “web link” applications that simply link to a cloud-hosted application that can be downloaded on demand and cached

The web link approach makes it easy to update applications: just update the server and the remote client systems will automatically pull the application when needed.

Local resources
Web browsers pull text, images, and other content from the web and render it on the user’s machine. The process of loading this remote content accounts for much of the user’s wait time. This paradigm changes with a local HTML5 application environment — because resources can exist locally, images and other components can load much more quickly.

What’s more, screens and user interfaces can be designed to fit the platform’s display characteristics. There is no need for panning and scrolling, and only limited need for zooming. Resources such as RAM can be optimized for this experience.

Security and sandboxing
Browsers load content and executable JavaScript code dynamically. This really is the power of the web technologies. The problem is, dynamically loaded code represents a threat to an embedded platform.

Browsers are designed to be sandboxed. By default, JavaScript code can execute only in the context of a browser engine, and cannot access the underlying operating system primitives and hardware. This approach changes in an HTML5 application environment. To give JavaScript code the ability to behave like a native application, the environment needs interfaces to the underlying OS through to the hardware. Plugins are used to implement these HTML5-to-OS interfaces.

Nonetheless, access to the underlying platform must be carefully controlled. Hence, a security scheme forms a critical component of the HTML5 application environment.

Application packaging
The app experience has become familiar to anyone who owns a smartphone or tablet. An HTML5 application environment in the car can also support this kind of experience: developers create and sign application packages, and users can download those packages from an application store. In an automotive context, authenticity of the applications and control over what they can or cannot do is critical. Again, a security model that enforces this forms a key part of the HTML5 application environment.

So, how should you think of an HTML5 application environment?
From my perspective, an HTML5 environment is like any other traditional HMI toolkit, but with much more flexibility and with inherent support for connected applications. In an HTML5 application environment, you can find technologies similar to those of any proprietary toolkit, including:

• a rendering engine (HTML5 rendering engine)
• a set of content authoring and packaging tools
• layout specifications (HTML5 and CSS3)
• a programming language (JavaScript)
• an underlying data model (DOM)

The difference is, these components are developed with a web experience in mind. This, to me, is the most significant benefit: the web platform is open, scalable, and well understood by countless developers.

Full disclosure: QNX releases first complete photos of new reference vehicle

"Any customer can have a car painted any color... so long as it is black."

We've come a long way since 1909, when Henry Ford penned this now-famous sentence. Not only can modern consumers pick the colors and features they want in a vehicle, but, in many cases, they can order them online. Getting the car you want, with the options you want, has never been easier.

Still, most forms of personalization are baked in. Once you order a car in, say, Barcelona Red (the color of my new Venza), it's hard to reverse the decision. But imagine the day when you can sit behind the wheel and watch your car's instrument cluster automatically reconfigure itself according to your personal preferences. And imagine if the cluster could do the same for everyone else who uses the car.

That's the kind of future QNX is working to make happen.

But you know what? I'm getting ahead of myself. I promised pictures of the new QNX reference vehicle, so let's look at them — especially since they offer tantalizing examples of what I was just talking about. :-)

The vehicle
Up to now, we've only released teaser images of the reference vehicle, with just enough detail to get people guessing as to what it might be. But enough with the mystery. Here's a full-on shot of the vehicle — a Jeep Wrangler Sahara — in all its off-road glory:


Yes, it's a Jeep

By the way, if you were one of the first 25 people in Canada or the US to guess it was a Jeep during our recent teaser campaign, congratulations! We'll identify the winners shortly.

The cluster
Once you get behind the wheel, the first thing you'll see is the digital instrument cluster. Let's zoom in so you can get a good look:



The cluster is implemented entirely in software and can reconfigure itself on the fly to display various types of information. Better yet, you can re-skin the cluster at the tap of a touchscreen button, like so:



As you can see, the cluster communicates with the head unit's navigation system to display turn-by-turn directions. Nice touch.

The head unit
Now look to your right, and you'll see the head unit. It supports a whack of functions (note my deft use of technical language), including one-touch pairing with Bluetooth smartphones, hybrid navigation, text-to-speech, natural speech recognition, streaming Internet radio, weather reporting, parking search, and too many other things to mention here.

In this photo, the head unit displays one of my favorite applications, the virtual mechanic. Intrigued? Check out my description of an early version of this app.



You know what else is cool? The unit's media player can post Facebook updates that list the song currently playing — but only when you tell it to, using voice commands. (Personal control over technology. I like that.) To view these updates later today and tomorrow while the Jeep is at Telematics Detroit, check out the QNX Facebook page.

Here's another photo of the head unit, showing its app tray:



The radio
What car would be complete without a radio? Mind you, in this case, "radio" includes support for streaming Internet radio from Pandora and TuneIn. And keeping in tune with the personalized listening experience these services offer you, the head unit's radio gives you a choice of skins:





In fact, almost every aspect of the head unit can be easily re-skinned. What's more, the underlying code remains the same: only the user interface, created in HTML5, changes from one skin to another. Which means automotive developers can create a single code base and re-use it across multiple vehicle lines. Doing more with less — what could be bad?

That's all I have for now, but before you go, check out the two press releases QNX issued this morning on the Jeep's personalization and Facebook features. Also, check out the QNX Flickr page for even more photos of the Jeep.
 

Phonedog connects with QNX concept car at BlackBerry World 2012

If you aren't at BlackBerry World this week, you're missing out. For starters, you won't get to see what, in my biased opinion, is the world's coolest car: the QNX-powered and very connected Porsche 911.

But not all is lost. You can still watch this video from Sydney Myers of PhoneDog.com, who caught with up with Mike Shane of QNX for a tour of the car's features — from instant smartphone pairing and off-board navigation to handsfree calling with HD stereo. Check it out:



My favorite part? When the text overlay on the video shouts out "The audio quality was REALLY good." Got that right.

And did I mention? Mike is one of the super-talented people who built the concept car. He's a keeper.
 

Find me a Starbucks! QNX concept car showcases power of WATSON speech engine

Yes, you can talk to the QNX concept car and tell it what to do.

Recently, our friends at AT&T invited us to bring the concept car to their "Living the Networked Life" event in New York. We said yes, of course! After all, what could be cooler than riding the streets of Gotham City in a digitally pimped-out Porsche 911?

Kidding aside, the event provided an excellent opportunity to demonstrate how the car takes advantage of WATSON, AT&T's natural-language speech engine. To get an idea of what WATSON can do, check out this video from Terrence O'Brien of Engadget:



For the full Engadget article, click here. And stay tuned for more updates from the Living the Networked Life event.
 

Making of the QNX concept car... honest

We created this video as a backdrop for CES 2012 where we unveiled the latest QNX concept car (a Porsche 911). Good thing, too, as people clearly stated that they would not have believed we did this cool retrofit ourselves without proof.


 

QNX joins Car Connectivity Consortium

This just in: QNX Software Systems has announced its membership in the Car Connectivity Consortium (CCC), the organization dedicated to developing the MirrorLink standard for car-smartphone connectivity.

MirrorLink offers a way to help car occupants access their smartphone applications. For instance, it could allow occupants to access their phone apps through the infotainment touchscreen, steering-wheel buttons, or other in-car controls.

Source: CCC

As a core member of the CCC, QNX Software Systems will have access to MirrorLink specifications under development and to various MirrorLink work groups. It will also be able to support future MirrorLink options in QNX-based systems, and help drive development of the standard.

“QNX Software Systems is a key player in the evolution of car infotainment technology and we are pleased to welcome them into the organization,” commented Mika Rytkonen, the CCC's chairman and president.

The announcement fits into QNX's strategy of enabling automotive developers to leverage widely supported industry standards.

“We believe in giving automotive customers choice and the flexibility to use the technologies best-suited to their requirements — contributing to the CCC helps us deliver on that commitment,” added Andy Gryc, automotive product marketing manager for QNX. (This is, of course, the same Andy Gryc who contributes to this blog.)

To read the press release, click here.

 

Everything you wanted to know about HTML5 in the car, Part III

Welcome to the third installment in my Q&A series on HTML5 in the car. In Part II, we looked at web servers, native plug-ins, instrument clusters, and display updates. This week, we turn our attention to tools, touch gestures, UI performance, and vehicle resources.

Are there any HTML5 HMI builder tools available?
Most of the well-known IDEs, including Eclipse, Dreamweaver, and Netbeans, support some flavor of HTML5 in their latest release. Adobe Edge, a new tool now available in preview, also lets you create animated HTML5 content. I suggest you check out the HTML5 Tools site, which publishes up-to-date tool reviews.

Often, automotive customers will ask system designers to make an infotainment system work "like an iPhone,” with the popular gesture controls. Does HTML5 support "inertial" menus and two-finger zoom?
Multi-touch is handled at the app level; here’s an example. Pinch zooming at the browser level is browser-dependent — the QNX browser handles it, but not every browser does. As for physics-based scrolling, HTML5 doesn’t support it “out of the box”; it needs to be added. Frameworks like Sencha Touch provide these types of controls.

Will the performance of HTML and JavaScript be adequate for critical user interface components or computations, such as safety-related notifications?
This has to be tested on a case-by-case basis. For the UI elements, yes, the performance should be adequate. Our testing indicates you can build HMIs that are surprisingly responsive. Also, our WebKit port lets you do things things like run JavaScript code in other tabs, threads, or processes to ensure those ocmponents aren’t being thread-blocked by something less critical.

I do get a little gun-shy recommending HTML5 for safety-critical components, because JavaScript isn't inherently real-time. If you wouldn't feel comfortable using Java for a critical coding task, you shouldn't use HTML5 either. If you want predictable, real-time performance for a lower-level computation that cannot tolerate any delay, the code should execute in a non virtual-machine environment. Most code doesn’t really fit that description, so most of the time JavaScript should work just fine.

How do you call vehicle resources — vehicle HMI, vehicle diagnostics information, etc. — on a HTML web app in the car? What's the process in plain words?
In plain words, it’s kinda hard. :-) But here’s my best take on this question: we solve this by creating a vehicle-bus driver that exports data through a publish/subscribe mechanism. The HTML5 layer talks to that piece through a JavaScript interface.
 

Can auto wag the ITS dog?

Intelligent Transport Systems (ITS) promise to deliver many benefits, from increased road safety to better traffic flow. It’s no surprise, then, that when people talk about ITS, it is often within the context of the auto industry. But is the auto industry alone big enough to attract the businesses needed to innovate and deploy ITS?

This question came up repeatedly at the Fully Networked Car Workshop held at the Geneva Auto Show, for the simple reason that auto is dwarfed by the telecom industry. Car volumes are measured in millions, whereas mobile phones are measured in billions. (In fact, evidence suggests the world may contain more mobile phones than toothbrushes.) It is likely, then, that businesses will focus on ITS-related applications, services, and infrastructure for phones — not cars.

Workshop panelists also pointed out that ITS extends beyond the auto or other transport industries; it is about enabling a connected society on the move. Consumers want mobility solutions that enable them to stay connected to all aspects of their lives in meaningful ways — not just optimize the efficiency and safety of getting from point A to point B.

The need for global standards
Regardless of whether auto or telecom drives ITS, we will need global standards for how these systems work. The good news is, major international standards development organizations (SDOs) are already trying to collaborate on the global standards needed to make ITS a reality. In fact, the Fully Networked Car Workshop was jointly sponsored by the International Telecommunication Union (ITU), the International Organization for Standardization (ISO), and the International Electrotechnical Commission (IEC).

The ITU has also started a collaboration on ITS Communications Standards. The next meeting of this collaboration will take place at SAE Headquarters in Troy, Michigan, USA on April 3, 2012.

A non-starter without industry participation
Mind you, success of ITS standards cannot solely depend on cooperation of the SDOs. Industry involvement is just as important.

Some workshop participants argued, however, that standardization inhibits product differentiation and thereby acts as a barrier to industry participation. But others felt this could be managed by standardizing on the lower layers (i.e. communications layers) and differentiating at the higher layers (i.e. application layers). The one caveat raised was that some aspects of the higher layers need to be standardized for safety reasons. But even then, it is possible to standardize on safety and still differentiate on user experience.

Panelists also discussed the threat of government regulation as a motivation to develop and deploy ITS. Someone pointed out, however, that competition often acts as a bigger motivator for companies than the threat of regulation.

Wagging the dog?
So what will drive innovation and deployment of ITS? It seems that global standards created with industry participation are crucial. Perhaps even more important, the auto industry must start working more closely with other industries such as telecom and consumer to develop ITS solutions that not only help people get from point A to point B efficiently and safely, but also deliver value in other ways to consumers on the move — unless of course you believe that the tail can wag the dog!
 

Crossing the boundaries: Cooperation across industries will fuel the connected car

A guest post by Brian Salisbury of Telecommunication Systems (TCS)

Connected car – these two words appear together more and more these days. Consider, for example, two events that took place in February: The Connected Car Executive Lunch organized by Fierce Wireless and held during the Mobile World Congress in Barcelona, and the Telecom Council’s Mobile Forum: Connected Car meeting hosted by Marvell Semiconductor in Silicon Valley.

Speakers at these events came from mobile operators (AT&T Mobility, Orange, Sprint, Verizon), auto manufacturers (Ford, Hyundai, Nissan, Toyota), and platform and solution providers (Nokia, Pioneer, QNX Software Systems, TCS). No doubt about it, the car is now connecting industries.

Although these two events were held on different continents, the topics on the minds of attendees were very similar:

• Who “owns” the customer?
• Will the connection be part of the car, or brought to the car by its driver?
• How can the “wild west” of the Internet be safely incorporated into the car?
• What is the business model for such a multi-part solution?
• What will be the “killer app” for connected car, or is there no such thing?

The presentations and discussions were diverse, as each group sought to define their role in terms that extend logically from their own past experience, and that could provide them with some control over the outcome. Thankfully, every group shared the common goal of making sure that connected cars are safe cars, and that the introduction of new connected services doesn’t create driver distraction problems.

We are clearly on the verge of a new generation of services being extended into the car that can enhance many aspects of owning, operating, and riding in tomorrow’s vehicles. Those of us fortunate enough to be part of one of these groups will have some amazing opportunities to bring the best of our respective industries into this new space, and to build new relationships across industry boundaries.

For an example of how TCS is helping to enable the connected car, check out this post on the VW Polo that was showcased at Mobile World Congress — Ed.

---

Here’s a little more about Brian and TCS:

Brian Salisbury is director of business development at TeleCommunication Systems, Inc. (TCS), where he is responsible for developing new business with OEMs, platform providers, and developers in the LBS ecosystem. Brian has worked in the mobile industry for more than 25 years, with most of that experience being in mobile data and location-based services, and within semiconductor, device manufacturer, and network operator companies.

TCS (NASDAQ: TSYS) is a world leader in highly reliable and secure mobile communication technology. TCS infrastructure forms the foundation for market leading solutions in E9-1-1, text messaging, commercial location and deployable wireless communications. TCS is at the forefront of new mobile cloud computing services providing wireless applications for navigation, hyper-local search, asset tracking, social applications and telematics.
 

Setting the Pace for Automotive Electronic Innovation

Welcome to the first installment in a series of guest posts from Paul Sykes of Freescale’s driver information systems team.

Recently, I traded in my MY2002 SUV for a new MY2012 vehicle. At the time, the MY2002 was quite advanced in its in-cabin electronics and styling, but wow — times have changed! Gone are the aftermarket satellite radio and PND that were attached, with wires dangling, at various places in my cabin.

The newest generation of vehicles offers complete and total integration, including new features that didn’t exist in 2002, such as USB/iPod interfaces, HD Radio, and a rear view camera.

But here’s the problem. I work in this great industry of automotive electronics and have some view of what’s coming in the next wave of vehicles. It’s both a blessing and a curse. Do I buy now or wait for the next model year? It’s like trying to time when to jump into your next cell phone or tablet purchase, only the time scale is a bit different.

The pace of electronic innovation has increased in this industry and you don’t have to wait 10 model years (like I did) to see it. It’s exciting to be a part of the supply base that is helping this industry move faster while maintaining some of the highest standards of quality and reliability over a long product life.

Fundamentally, at the heart of every embedded electronic vehicle system, incoming data needs to get processed and acted upon, using complex software algorithms. At Freescale, sensor and processor innovations make the future possible by doing these fundamental elements better, faster, and more reliably.

Ecosystem partners like QNX Software Systems provide many of the complex algorithms required to realize infotainment and instrument cluster systems. These same systems are often powered with Freescale i.MX processors.

In the latest generation, the i.MX 6 Series, Freescale has provided the most scalable line-up of products available. Scalability means not only performance and function scalability, but also pin-to-pin hardware compatibility across the entire series. This is one example of how the processor can help pick up the innovation pace. With hardware and software compatibility, system makers can develop more products to meet a broader range of market needs, in a shorter amount of time.


The Freescale i.MX 6 Series has been chosen to power the next-generation
GM OnStar system.

In future posts, I will offer Freescale’s perspective on many of the current trends in driver information systems as well as our product collaborations with QNX to bring unique value to the industry.

---

Here’s a little more about Paul and the Freescale Driver Information Team:

Paul has more than 15 years’ experience in the semiconductor industry, including product development, program management, and marketing positions. For the past several years, Paul has lived in Michigan and focuses exclusively on the automotive telematics, audio/infotainment, and instrument cluster application spaces.

Freescale’s Driver Information Team is driving the global strategy and product development for solutions to address the multitude of applications in the rapid growth and innovation area of Driver Information Systems. This includes instrument cluster, graphics displays, audio and infotainment, and telematics.
 

What the connected car is really all about (and what we need to do about it)

Recently, I was invited to participate in a webinar that highlighted hits and misses at Mobile World Congress. It occurred to me that some of you might be interested in what I had to say — at the very least, I’d earn points with Paul Leroux, our editor, for spontaneously offering up a blog post. :)  So here's what I said... almost verbatim.

"First, a quick intro on QNX: Many will know us as the wholly owned subsidiary of RIM whose software platform powers the BlackBerry PlayBook. But we also provide the de facto standard platform for all types of in-vehicle infotainment and navigation systems. And it’s from this perspective that I offer these comments. My primary observation is regarding the evolving dialogue surrounding the connected car and what I think it represents. Three years ago we were here with Alcatel-Lucent, showcasing the first LTE connected concept car, based on a Toyota Prius. This car proved so popular that we had to hire a security guard to help manage the traffic. Now, three years later, there are a number of connected production vehicles to be seen, including a QNX-based BMW 7 series in the GSMA’s connected home exhibit. And the announcements this year focused not so much on broadband connectivity per se (it's here, people expect it), but on the integration of the smart phone with the vehicle. At QNX, we talk about the personalization of the in-vehicle experience, as people want to bring in their own devices, their own music, their own contacts and other content — and experience these in the vehicle setting. For instance, Ford not only announced the B-Max vehicle, but used MWC as a platform to launch Ford Sync for Europe. Toyota and Samsung, meanwhile, announced support for Samsung Mobile Car Application for integration of phones to the car's head unit. So if step one was getting a broadband connection to enable a consumer experience in the car, and step two is about personalizing that experience, what’s next? I think that, ultimately, the connected car is all about the consumer, and this is how revenue will be generated in a way that connected telematics on its own could never do. You could be an automaker interested in improving how to service a car and its owner after the car has driven off the dealer's lot. Or you could be a carrier interested in extending your offer beyond connectivity to deliver value-added services. Or perhaps you’re a small business trying to get more people in the door. In each case, the car represents a new frontier. And it offers the added value of context – not only do you know if someone is available and where they are, but you also know that they are driving a vehicle. The next few years are going to be very exciting as the automotive and mobile industries converge to address this opportunity. Think about the brands involved: Companies like Audi, BMW, and GM on one hand and the likes of AT&T, Verizon, and Vodafone on the other. They’re mutually dependent — neither group will be successful without the other. Automotive needs to leverage the investments being made for smart phones, be it device technology, network infrastructure, or developer communities. Meanwhile, the mobile industry has to consider the nature of automotive in terms of safety, security, and liability, not to mention product life cycles. It's safe to say that automotive is just the first example of this type of industry convergence and transformation. All of the carriers are looking at M2M as a huge untapped market opportunity. And within the classic embedded market, there are an almost infinite number of market segments, truly an example of the Long Tail. It will be exciting to watch how mobile transforms those markets and vice versa — what will mobile look like in 5 years from now? I don’t think we can easily predict it; after all, it's not going to be like anything we’ve seen before. But I can’t wait to find out.

So there you have it. If you'd like to hear the entire webinar, you can register here to access the archived version.
 

A quick tour of the QNX CAR 2 application platform

If you're looking for a quick, two-minute intro to the QNX CAR 2 application platform, you've come to the right place.

In this video, Kerry Johnson, automotive product manager at QNX, takes us on a tour of the platform, including its home screen, media player, application area, HTML5 support, phone app, and acoustic processing.

Ready? Then hit the Play button and let's get started:



In case you didn't know, the QNX CAR 2 platform forms the basis of the QNX concept car, a specially modified Porsche 911 that demonstrates what to expect in next-generation car infotainment systems. Earlier this year, the platform drove home with a 2012 Best of CES award, in the Car Tech category.
 

TCS showcases hybrid navigation system in VW Polo

The Porsche 911 concept car that won the 2012 Best of CES award wasn't the only QNX-outfitted vehicle at Mobile World Congress this year. Our friends at TeleCommunication Systems (TCS), who provide hybrid navigation software for the QNX CAR application platform, showcased a VW Polo running the same QNX-powered navigation, maps, and local search capabilities as the Porsche.

Like the Porsche, the Polo featured a retrofitted infotainment system in place of the factory radio — and TCS did a very nice job integrating it into the car.

The Polo was a hit, driving discussions with mobile operators, handset manufacturers, automakers, and automotive tier ones. Seems the connected car is a hot topic just about everywhere you go these days.

Here's the Polo in the TCS booth:



And here's a close-up of the retrofitted infotainment system:


 

HTML5: Bustin' the myths

Did you know you can build HTML5 apps that don't use an Internet connection? Did you know you can run HTML5 apps without a web browser? And did you know HTML5 apps can show snappy performance even on automotive silicon? (As you can well imagine, in-car infotainment systems don't ship with quad-core server-class CPUs.)

If you answered no to any of these questions, you need to stop for a minute and check out this interview with QNX Software Systems' Kerry Johnson. Heck, even if you answered yes to all three questions, you'll probably still appreciate what Kerry has to say — and besides, you'll catch a glimpse of a complete in-car UI coded in HTML5. What could be bad?



While I have you, check out Andy Gryc's Q&A series on HTML5, if you haven't already. You'll find the first two installments here and here.
 

Audi A8 drives home with best connected car award

This just in: Connected World magazine has announced the winners of its first annual Connected Car of the Year awards, and the Audi A8 has won top prize in the ultra-luxury category.

According to Connected World, the awards honor vehicles with technology that strikes the right balance of safety, convenience, and infotainment. The magazine's editorial team decides the winners.

The Audi A8's infotainment system, dubbed the MMI, is based on the QNX Neutrino OS. The MMI offers some extremely cool features, including 3D navigation powered by Google Earth and a touchpad that lets you input destinations names by tracing them with your finger.

Here, for example, is a photo of the navigation display:



And here is a photo of someone using the touchpad, known as MMI Touch:



Both these photos were taken at a QNX Automotive Summit that took place in Stuttgart in 2010.

Connected World also handed out awards to the Ford Focus, Chrysler 300, and Cadillac XTS. These cars won in the small, mid-size, and luxury categories, respectively.
 

Everything you wanted to know about HTML5 in the car, Part II

Welcome to the second installment in my Q&A series on HTML5 in the car. Last week, we looked at CSS, cross-platform execution, and asynchronous design. This week, we turn our attention to web servers, native plug-ins, instrument clusters, and display updates.

If I don’t use a web server in my infotainment system, will I miss out on some features of HTML5?

A web server isn’t strictly necessary, but there are two very good reasons for including one. First, it lets you export a user interface to devices outside the car, thereby allowing mobile phones or tablets to run apps that are hosted on the vehicle head unit. Second, it lets you export internal car resources, as a URL, to HMI software running in the head unit. For instance, the web server could provide the HMI with access to static vehicle-configuration data (through an xml file) or to a back-up camera (through a video stream).

Will using native code plug-ins compromise my ability to leverage HTML5?

This is tricky, because a lot of things you want to do may require native code. So, yes, use native code, but do it judiciously. The more native code you use, the more it will limit the cross-platform capability of the HTML5 code that relies on it. The good news is that with HTML5 gaining so much functionality, plug-ins are needed far less than ever before.

A sample climate control app from the
QNX CAR 2 platform, created with HTML5.

Would you consider HTML5 as an option for cluster instruments: speedometers, tachometers, etc.?

At this point, I’d say no. HTML5 makes a lot of sense for in-vehicle infotainment, but it doesn’t provide the response needed for a vehicle cluster and it won't ensure safety-critical certification. Plus, the instrument cluster isn’t where you realize a lot of HTML5’s value: downloadable apps, connectivity to mobile devices, and so on. If the cluster and the infotainment system eventually merge into one big screen, then it’s more likely you could use HTML5 for both — but that’s still a few years out.

What’s a good way to get responsive display updates (10Hz update) into HTML5? Websockets?

If you need to deliver high-speed updates to your head unit, Websockets is one way to go. Make sure, however, that you don’t stall the rest of the JavaScript engine while your main thread is blocked on tasks. If you create another thread to monitor for changes, you can do it just as effectively (and probably with less work) with a JNEXT or NPAPI call into native code.
 

Auto + Mobile

I love this play on words. I can’t claim it as my own but I think it’s very cool that the word automobile breaks down into auto and mobile. I’m sure the term originally referred to automatically mobile horseless-carriages or some such thing. According to one online source, the word dates from 1895 and means “self-propelled motor vehicle”.

But today, it represents the convergence of two historically independent industries, auto and mobile. Now, more than ever, consumers are extending their digital lives into their cars. They want a personalized in-vehicle experience, including access to their music, to their friends, to their favourite places, and to their schedules — both personal and professional. And that’s just the beginning.

Following the Consumer Electronics Show (CES) in January, I heard many in the industry refer to CES as one of the most important automotive shows of the year. You heard that right: CES is now considered an automotive show.

The new QNX concept car is
scheduled to appear at MWC.

Now it’s February and QNX Software Systems is headed to Barcelona where we will demonstrate our connected concept car on the BlackBerry stand in Hall 7 at Mobile World Congress. This same car won a Best of CES award in the car tech category.

MWC is the show for mobile phones and everything related. During the show, we will participate on a luncheon panel hosted by Fierce Markets, Paving the Way to Success for the Connected Car. Other panelists include Ford, AT&T, and the GSMA.

MWC isn’t known as an auto-focused event but I expect this to change. Most carriers see the connected car as an emerging growth market, as do silicon vendors. Meanwhile, handset and car companies work towards improving the integration of the mobile experience into the car without impacting driver distraction.

Auto + Mobile. End of story.

For more info on the panel, click here.
 

ITU-T: Developing standards to fight driver distraction

The telecommunication standardization sector of the International Telecommunications Union is poised to play a crucial role in tomorrow’s connected cars. And yet, many people in the auto industry have never heard of the ITU, or of its standardization sector, the ITU-T. So let’s start with a quick introduction.

The ITU is the United Nations agency that deals with telecommunications. More specifically, it is where governments come together to agree on international standards for Information and Communications Technologies (ICTs).

Currently, the ITU-T is developing recommendations for ICTs that interact with drivers — examples include networked-based navigation systems, web browsers, and mobile phones. These recommendations will apply to networks; to applications accessed by drivers; and to connected, nomadic, and factory-installed devices. Strictly speaking, these recommendations are voluntary, which is precisely why they are referred to as “recommendations.” However, they can become binding if mandated by regional government agencies or customers.

ITU-T recommendations for the car are needed for several reasons:

• ICTs are moving into the automotive cockpit — Increasingly, ICT systems under the scope of the ITU-T are finding their way into the cockpit and interacting with drivers. Technology-related driver distraction has been recognized as a global problem that needs to be addressed. Internationally agreed guidance on the design and performance of these systems can help increase safety.
   
• Easy-to-find guidance for ICT community — ICT designers, developers, and application authors need easy access to guidance on design and performance requirements for ICT systems that interact with drivers. The ICT community consults ITU-T recommendations for guidance and requirements on ICT systems. Therefore, there is real value in having ITU-T recommendations that can serve as a reference to existing driver distraction-related standards and to fill any standardization gaps.
   
• Internationally agreed standards — The ITU-T is where governments come together to agree on international telecommunications standards. This is what makes these standards unique. It also gives them more weight with regional Standards Development Organizations (SDOs) and regulatory authorities. There is even value in an ITU-T recommendation that simply references existing standards since it will have gone through the ITU-T approval process.

Focus group on driver distraction
Last year, I became the founding chair for the ITU’s Focus Group on Driver Distraction (FG Distraction), which was created to pull expertise from the automotive industry and human factors experts into the ITU-T standardization process. The group currently has 3 planned ITU-T recommendations related to driver distraction:

G.SAM — recommendation on mechanisms for managing the situational awareness of drivers:

 

G.V2A — recommendation on an automotive interface (for instance, APIs) for applications external to the vehicle gateway:



P.UIA — recommendation on automotive user interface requirements:



FG Distraction will finalize pulling together input from industry and human factors experts by December 2012. Approved ITU-T recommendations are not expected until late 2013.

Want to contribute?
If you’d like to participate in FG Distraction, the group is open to any individual from a country that is a member of ITU and who is willing to contribute to the work (which is just about everyone). This includes anyone who is also a member or representative of an interested SDO. There is no cost to participate.

For more information about FG Distraction and upcoming meetings, click here. The next meeting will take place on April 4-5 at the SAE Headquarters in Troy, Michigan, USA.