A question of architecture

The second of a series on the QNX CAR Platform. In this installment, we start at the beginning — the platform’s underlying architecture.

In my previous post, I discussed how infotainment systems must perform multiple complex tasks, often all at once. At any time, a system may need to manage audio, show backup video, run 3D navigation, synch with Bluetooth devices, display smartphone content, run apps, present vehicle data, process voice signals, perform active noise control… the list goes on.

The job of integrating all these functions is no trivial task — an understatement if ever there was one. But as with any large project, starting with the right architecture, the right tools, and the right building blocks can make all the difference. With that in mind, let’s start at the beginning: the underlying architecture of the QNX CAR Platform for Infotainment.

The architecture consists of three layers: human machine interface (HMI), middleware, and platform.



The HMI layer
The HMI layer is like a bonus pack: it supports two reference HMIs out of the box, both of which have the same appearance and functionality. So what’s the difference? One is based on HTML5, the other on Qt 5. This choice demonstrates the underlying flexibility of the platform, which allows developers to create an HMI with any of several technologies, including HTML5, Qt, or a third-party toolkit such as Elektrobit GUIDE or Crank Storyboard.

A choice of HMIs

Mind you, the choice goes further than that. When you build a sophisticated infotainment system, it soon becomes obvious that no single tool or technology can do the job. The home screen, which may contain controls for Internet radio, hands-free calls, HVAC, and other functions, might need an environment like Qt. The navigation app, for its part, will probably use OpenGL ES. Meanwhile, some applications might be based on Android or HTML5. Together, all these heterogeneous components make up the HMI.

The QNX CAR Platform embraces this heterogeneity, allowing developers to use the best tools and application environments for the job at hand. More to the point, it allows developers to blend multiple app technologies into a single, unified user interface, where they can all share the same display, at the same time.

To perform this blending, the platform employs several mechanisms, including a component called the graphical composition manager . This manager acts as a kind of universal framework, providing all applications, regardless of how they’re built, with a highly optimized path to the display.

For example, look at the following HMI:



Now look at the HMI from another angle to see how it comprises several components blended together by the composition manger:



To the left, you see video input from a connected media player or smartphone. To the right, you see a navigation application based on OpenGL ES map-rendering software, with an overlay of route metadata implemented in Qt. And below, you see an HTML page that provides the underlying wallpaper; this page could also display a system status bar and UI menu bar across all screens.

For each component rendered to the display, the graphical composition manager allocates a separate window and frame buffer. It also allows the developer to control the properties of each individual window, including location, transparency, rotation, alpha, brightness, and z-order. As a result, it becomes relatively straightforward to tile, overlap, or blend a variety of applications on the same screen, in whichever way creates the best user experience.

The middleware layer
The middleware layer provides applications with a rich assortment of services, including Bluetooth, multimedia discovery and playback, navigation, radio, and automatic speech recognition (ASR). The ASR component, for example, can be used to turn on the radio, initiate a Bluetooth phone call from a connected smartphone, or select a song by artist or song title.

I’ll drill down into several of these services in upcoming posts. For now, I’d like to focus on a fundamental service that greatly simplifies how all other services and applications in the system interact with one another. It’s called persistent/publish subscribe messaging, or PPS, and it provides the abstraction needed to cleanly separate high-level applications from low-level business logic and services.

PPS messaging provides an abstraction layer between system services and high-level applications

Let’s rewind a minute. To implement communications between software components, C/C++ developers must typically define direct, point-to-point connections that tend to “break” when new features or requirements are introduced. For instance, an application communicates with a navigation engine, but all connections enabling that communication must be redefined when the system is updated with a different engine.

This fragility might be acceptable in a relatively simple system, but it creates a real bottleneck when you are developing something as complex, dynamic, and quickly evolving as the design for a modern infotainment system. PPS addresses the problem by allowing developers to create loose, flexible connections between components. As a result, it becomes much easier to add, remove, or replace components without having to modify other components.

So what, exactly, is PPS? Here’s a textbook answer: an asynchronous object-based system that consists of publishers and subscribers, where publishers modify the properties of data objects and the subscribers to those objects receive updates when the objects have been modified.

So what does that mean? Well, in a car, PPS data objects allow applications to access services such as the multimedia engine, voice recognition engine, vehicle buses, connected smartphones, hands-free calling, and contact databases. These data objects can each contain multiple attributes, each attribute providing access to a specific feature — such as the RPM of the engine, the level of brake fluid, or the frequency of the current radio station. System services publish these objects and modify their attributes; other programs can then subscribe to the objects and receive updates whenever the attributes change.

The PPS service is programming-language independent, allowing programs written in a variety of programming languages (C, C++, HTML5, Java, JavaScript, etc.) to intercommunicate, without any special knowledge of one another. Thus, an app in a high-level environment like HTML5 can easily access services provided by a device driver or other low-level service written in C or C++.

I’m only touching on the capabilities of PPS. To learn more, check out the QNX documentation on this service.

The platform layer
The platform layer includes the QNX OS and the board support packages, or BSPs, that allow the OS to run on various hardware platforms.

An inherently modular and extensible architecture

A BSP may not sound like the sexiest thing in the world — it is, admittedly, a deeply technical piece of software — but without it, nothing else works. And, in fact, one reason QNX Software Systems has such a strong presence in automotive is that it provides BSPs for all the popular infotainment platforms from companies like Freescale, NVIDIA, Qualcomm, and Texas Instruments.

As for the QNX Neutrino OS, you could write a book about it — which is another way of saying it’s far beyond the scope of this post. Suffice it to say that its modularity, extensibility, reliability, and performance set the tone for the entire QNX CAR Platform. To get a feel for what the QNX OS brings to the platform (and by extension, to the automotive industry), I invite you to visit the QNX Neutrino OS page on the QNX website.

Read More

A sweet ride? You’d better 'beleave' it

Is Autumn the best season for a long, leisurely Sunday drive? Well, I don’t know about your neck of the woods, but in my neck, the trees blaze like crimson, orange, and yellow candles, transfiguring back roads into cathedrals of pure color. When I see every leaf on every tree glow like a piece of sunlight-infused stained glass, I make a religious effort to jump behind the wheel and get out there!

Now, of course, you can enjoy your Autumn drive in any car worth its keep. But some cars make the ride sweeter than others — and the Mercedes S Class Coupe, with its QNX-powered infotainment system and instrument cluster, is deliciously caloric.

This isn’t a car for the prim, the proper, the austere. It’s for pure pleasure – whether you take pleasure in performance, luxury, or beauty of design. Or all three. The perfect car, in other words, for an Autumn drive. Which is exactly what the folks at Mercedes thought. In fact, they made a photo essay about — check it out on their Facebook page.


Source: Mercedes

Read More

Attending SAE Convergence? Here’s why you should visit booth 513

Cars and beer don’t mix. But discussing cars while having a beer? Now you’re talking. If you’re attending SAE Convergence next week, you owe it to yourself to register for our “Spirits And Eats” event at 7:00 pm Tuesday. It’s the perfect occasion to kick back and enjoy the company of people who, like yourself, are passionate about cars and car electronics. And it isn’t a bad networking opportunity either — you’ll meet folks from a variety of automakers, Tier 1s, and technology suppliers in a relaxed, convivial atmosphere.

But you know what? It isn’t just about the beer. Or the company. It’s also about the Benz. Our digitally modded Mercedes-Benz CLA45 AMG, to be exact. It’s the latest QNX technology concept car, and it’s the perfect vehicle (pun fully intended) for demonstrating how QNX technology can enable next-generation infotainment systems. Highlights include:

• A multi-modal user experience that blends touch, voice, and physical controls
• A secure application environment for Android, HTML5, and OpenGL ES
• Smartphone connectivity options for projecting smartphone apps onto the head unit
• A dynamically reconfigurable digital instrument cluster that displays turn-by-turn directions, notifications of incoming phone calls, and video from front and rear cameras
• Multimedia framework for playback of content from USB sticks, DLNA devices, etc.
• Full-band stereo calling — think phone calls with CD quality audio
• Engine sound enhancement that synchronizes synthesized engine sounds with engine RPM

Here, for example, is the digital cluster:



And here is a closeup of the head unit:



And here’s a shot of the cluster and head unit together:



As for the engine sound enhancement and high-quality hands-free audio, I can’t reproduce these here — you’ll have come see the car and experience them first hand. (Yup, that's an invite.)

If you like what you see, and are interested in what you can hear, visit us at booth #513. And if you'd like to schedule a demo or reserve some time with a QNX representative in advance, we can accommodate that, too. Just send us an email.

Read More

A question of concurrency

The first of a new series on the QNX CAR Platform for Infotainment. In this installment, I tackle the a priori question: why does the auto industry need this platform, anyway?

Define your terms, counseled Voltaire, and in keeping with his advice, allow me to begin with the following:

Con•cur•ren•cy \kən-kûr'-ən-sē\ n (1597) Cooperation, as of agents, circumstances, or events; agreement or union in action.

A good definition, as far as it goes. But it doesn’t go far enough for the purposes of this discussion. Wikipedia comes closer to the mark:

“In computer science, concurrency is a property of systems in which several computations execute simultaneously, and potentially interact with each other.”

That’s better, but it still falls short. However, the Wikipedia entry also states that:

“the base goals of concurrent programming include correctness, performance and robustness. Concurrent systems… are generally designed to operate indefinitely, including automatic recovery from failure, and not terminate unexpectedly.”

Now that’s more like it. Concurrency in computer systems isn’t simply a matter of doing several things all at once; it’s also a matter of delivering a solid user experience. The system must always be available and it must always be responsive: no “surprises” allowed.

This definition seems tailored-made for in-car infotainment systems. Here, for example, are some of the tasks that an infotainment system may perform:

• Run a variety of user applications, from 3D navigation to Internet radio, based on a mix of technologies, including Qt, HTML5, Android, and OpenGL ES
• Manage multiple forms of input: voice, touch, physical buttons, etc. 
• Support multiple smartphone connectivity protocols such as MirrorLink and Apple CarPlay 
• Perform services that smartphones cannot support, including:
  
  • HVAC control
  • discovery and playback of multimedia from USB sticks, DLNA devices, MTP devices, and other sources
  • retrieval and display of fuel levels, tire pressure, and other vehicle information
  • connectivity to Bluetooth devices
• Process voice signals to ensure the best possible quality of phone-based hands-free systems — this in itself can involve many tasks, including echo and noise removal, dynamic noise shaping, speech enhancement, etc. 
• Perform active noise control to eliminate unwanted engine “boom” noise 
• Offer extremely fast bootup times; a backup camera, for example, must come up within a second or two to be useful
   

Jugging multiple concurrent tasks

The primary user of an infotainment system is the driver. So, despite juggling all these activities, an infotainment system must never show the strain. It must always respond quickly to user input and critical events, even when many activities compete for system resources. Otherwise, the driver will become annoyed or, worse, distracted. The passengers won’t be happy, either.

Still, that isn’t enough. Automakers also need to differentiate themselves, and infotainment serves as a key tool for achieving differentiation. So the infotainment system must not simply perform well; it must also allow the vehicle, or line of vehicles, to project the unique values, features, and brand identity of the automaker.

And even that isn’t enough. Most automakers offer multiple vehicle lines, each encompassing a variety of configurations and trim levels. So an infotainment design must also be scalable; that way, the work and investment made at the high end can be leveraged in mid-range and economy models. Because ROI.

Projecting a unique identity

But you know what? That still isn’t enough. An infotainment system design must also be flexible. It must, for example, support new functionality through software updates, whether such updates are installed through a storage device or over the air. And it must have the ability to accommodate quickly evolving connectivity protocols, app environments, and hardware platforms. All with the least possible fuss.

The nitty and the gritty
Concurrency, performance, reliability, differentiation, scalability, flexibility — a tall order. But it’s exactly the order that the QNX CAR Platform for Infotainment was designed to fill.

Take, for example, product differentiation. If you look at the QNX-powered infotainment systems that automakers are shipping today, one thing becomes obvious: they aren’t cookie-cutter systems. Rather, they each project the unique values, features, and brand identity of each automaker — even though they are all built on the same, standards-based platform.

So how does the QNX CAR Platform enable all this? That’s exactly what my colleagues and I will explore over the coming weeks and months. We’ll get into the nitty and sometimes the gritty of how the platform works and why it offers so much value to companies that develop infotainment systems in various shapes, forms, and price points.

Stay tuned.

POSTSCRIPT: Read the next installment of the QNX CAR Platform series, A question of architecture.

Read More

Ontario tech companies team up to target the connected car

To predict who will play a role tomorrow's connected vehicles, you need to look beyond the usual suspects.

When someone says “automobile,” what’s the first word that comes to mind? Chances are, it isn’t Ontario. And yet Ontario — the Canadian province that is home to QNX headquarters — is a world-class hub of automotive R&D and manufacturing. Chrysler, Ford, General Motors, Honda, and Toyota all have plants here. As do 350 parts suppliers. In fact, Ontario produced 2.5 million vehicles in 2012 alone.

No question, Ontario has the smarts to build cars. But to fully appreciate what Ontario has to offer, you need to look beyond the usual suspects in the auto supply chain. Take QNX Software Systems, for example. Our roots are in industrial computing, but in the early 2000s we started to offer software technology and expertise to the world’s automakers and tier one suppliers. And now, a decade later, QNX offers the premier platform for in-car infotainment, with deployments in tens of millions of vehicles.

QNX Software Systems is not alone. Ontario is home to many other “non-automotive” technology companies that are playing, or are poised to play, a significant role in creating new automotive experiences. But just who are these companies? The Automotive Parts Manufacturers Association (APMA) of Canada would like you to know. Which is why they've joined forces with QNX and other partners to build the APMA Connected Vehicle.

A showcase for Ontario technology.

The purpose of the vehicle is simple: to showcase how Ontario companies can help create the next generation of connected cars. The vehicle is based on a Lexus RX350 — built in Ontario, of course — equipped with a custom-built infotainment system and digital instrument cluster built on QNX technology. Together, the QNX systems integrate more than a dozen technologies and services created in Ontario, including gesture recognition, biometric security, emergency vehicle notification, LED lighting, weather telematics, user interface design, smartphone charging, and cloud connectivity.

Okay, enough from me. Time to nuke some popcorn, dim the lights, and hit the Play button:

Read More

The lost concept car photos

Have you ever rummaged through old boxes in your basement and discovered family photos you had totally forgotten about — or never knew existed? I experienced a moment like that a couple of weeks ago. Except, in this case, no basement was involved. And the box wasn't a box, but a shared drive. And the photos weren't of my family, but of cars. QNX technology concept cars, to be exact.

At least once a year, the QNX concept team retrofits a new vehicle to demonstrate how our technology can help auto companies push the envelope in connectivity, infotainment, and acoustics. And, in every case, we take pictures — sometimes, lots of them. Inevitably, we end up choosing a few images for publicity purposes and filing the others. But as I discovered, the images we don't use are often just as good as the ones we do use. We just don't need all of them!

In any case, stumbling across these photos was great fun. I thought you might enjoy them, too, so here goes...

The Porsche
First up is the QNX technology concept car based on a Porsche 911, which made its debut at 2012 CES. We had originally planned to drive the car back to Ottawa once CES was over — but that was before we spoke to our friends at Texas Instruments, who provided the silicon for the car's instrument cluster and infotainment system. They liked the car so much, they asked if we could bring it to their HQ in Dallas, where the following two photos were taken. All I can say is, Dallas is home to at least one awesome cool photographer. Because rather than curse the crazy lighting, the photographer used it to create some playful compositions:





If you look below, you'll see another shot of the Porsche, taken just before we shipped it off to CES. The image really doesn't belong in this collection, as it appeared once on a partner website. But it's rare nonetheless, so I decided to include it. And besides, it's cool. Literally.



Did you know? The original Porsche 911, which debuted in the early 60s, was dubbed the 901. Problem was, Peugeot had exclusive rights in France to three-digit car names with a 0 in the middle. And so, the 901 became the 911.

---

The Bentley
Next up is the QNX technology concept car based on a Bentley Continental GT. In this image, the driver is interacting with the center stack's main control knob, which was mounted directly on a 17" touchscreen. See the row of icons just above the knob? These represented HVAC, music, navigation, hands-free calling and other system functions. The  system would automatically display these icons as your hand approached the display; you would then turn the knob to choose the function you wanted. (This image was taken by a BlackBerry employee, whose name I have most ungraciously forgotten.)



As with our all concept vehicles, the intent was to showcase the technology that we had built into the car's dashboard and center stack. Which probably explains why the following image of the car's exterior was never published. Pity, as it's quite lovely — a classic case of flare adding flair.



Did you know? Those wheels aren't just for show. The Bentley comes equipped with a 616 hp W12 engine (yup, three banks of cylinders) that can do 0-60 mph in a little over 4 seconds — it took me way longer than that to type this sentence.

---

The Jeep
Next up is the Jeep Wrangler, which serves as the QNX reference vehicle. The Jeep plays a different role than the other vehicles highlighted here: instead of demonstrating how QNX technology can help automotive companies innovate, it shows what the QNX CAR Platform for Infotainment can do right out of the box. In this image, you can see the vehicle's main navigation menu:



Did you know? The original infotainment system in the reference vehicle could post Facebook updates that listed the title and artist of the song currently playing. The system performed this magic in response to simple voice commands.

---

The Vette
The QNX technology concept car based on a Chevrolet Corvette made its debut at SAE Convergence 2010. Among other things, it showed how digital instrument clusters can morph on the fly to provide drivers with context-sensitive information, such as turn-by-turn directions. You can see a slicker, more sophisticated approach to reconfigurable clusters in our most recent technology concept car based on a Mercedes CLA45.



Did you know? We used the Corvette to demonstrate how QNX technology enables automotive companies to create customizable, reskinnable user interfaces. Check out this post on the Corvette's 30-day UI challenge.

---

The Prius
The first QNX-powered technology concept car was a digitally modded Prius — aka the LTE Connected Car. The car was a joint project of several companies, including QNX and Alcatel-Lucent, who wanted to demonstrate how 4G/LTE networks could transform the driving experience with a host of new in-vehicle applications.

Here's the car with a very proud-looking Derek Kuhn, who spearheaded the LTE Connected Car project while serving as a VP at Alcatel-Lucent. Derek subequently joined QNX as VP of sales and marketing:



Did you know? When this car was created, telecom companies had yet to light up their first commercial LTE towers. Also, the car had more infotainment systems than any other QNX technology concept car: two in the front (one for the driver and one for the front-seat passenger) and two in the back.

---

Some things get lost, albeit temporarily. And some you just never see again. Fortunately, all these images belong to the first category. Any favorites?

Read More

QNX-powered Audi MMI framework to support Android Auto

This just in: Audi has announced that its Audi MMI mobile media application framework, which is built on the QNX CAR Platform for Infotainment, will support the new Android Auto connectivity solution.

The new feature will allow drivers to access Android-device car apps using Audi MMI displays and controls, which Audi has optimized for safe and intuitive operation on the road.

Audi states that the MMI system will still maintain its compatibility with other smartphones. Moreover, drivers will be able to switch between the Android view and Audi infotainment functions, as desired.

Audi is a long-standing customer of QNX Software Systems. Audi systems based on QNX technology include the recent Audi Virtual Cockpit and Audi Connect with Google Earth.

Audi plans to introduce Android Auto support in all-new models launched in 2015. For the complete story on Audi support for Android Auto, read the Audi press release.

Read More

Crowd-sourced maps: the future of in-car navigation?

Guest post by Daniel Gast, innovation manager, Elektrobit Automotive

Crowdsourcing has become a major trend. Even McDonald’s has been getting into the act, asking consumers to submit new ideas for burgers. In 2013 the company’s “My Burger 3.0” campaign elicited an enormous response in Germany, with more than 200,000 burger ideas and more than 150,000 people voting for their favorites.

From burgers we go to a key component of navigation systems: digital maps. OpenStreetMap (OSM), a well-known and globally crowdsourced project, is dedicated to creating free worldwide maps and has attracted more than 100,000 registered contributors. These people volunteer their services, creating digital maps without being paid; take a glimpse of their work at www.openstreetmap.org.

Why is the amount of data behind OSM constantly growing?
Creating OSM maps is a kind of charity work, open to all to contribute and to use with free licenses. The technology behind it is very user friendly, which will help ensure long-term loyalty among contributors. But probably the most important factor is the fun it brings. Contributing content to this project consists of recording streets, buildings, bridges, forests, point of interests, and other items that you would benefit from having in a map. For many OSM editors, this is their favorite hobby — they are “addicts” in the best sense of the word. They love the project and aspire to create a perfect map. That’s the reason why the growing amount of available map data is of very good quality.

Can automakers and drivers benefit from crowd-sourced map data like OpenStreetMap?
Yes, they can. Because so many people contribute to the project, the amount of data is growing continuously. Every contributor can add or edit content at any time, and changes are integrated into the public OSM database immediately.

In the beginning only streets were collected, but because the data format is extensible, editors can add data like parking spots or pedestrian walkways. For instance, a group of firemen added hydrants for their region to the map material, using OSM’s flexibility to define and add new content. Automakers could take advantage of this flexibility to integrate individual points of interest like car repair shops or to drive business models with third-party partners, such as couponing activities.

Because it’s free of charge, OSM data could, in the mid to long term, develop into a competitive and low-priced alternative to databases being provided by commercial map data suppliers.

For their part, automakers could easily provide toolkits that allow drivers to edit wrong or missing map data on the go. Or even better, allow them to personalize maps with individual content like preferred parking places or favorite burger restaurants.

Are automotive infotainment systems ready for these new kinds of map data?
From a technical point of view, automotive software like the QNX CAR Platform for Infotainment or EB street director navigation can, without modifications, interpret this new kind of data, since the OSM map data can be converted to a specific format, much like commercial map data. It’s like creating your individual burger: the bread and meat remains the same, but you opt for tomatoes instead of onions.

That said, some gaps in the OSM data must be filled before it can provide full-blown automotive navigation. Features like traffic signs, lane information, and turn restrictions are available, but coverage remains limited. Also, the regional coverage varies widely — coverage in Germany, for example, is much higher than in countries in Africa or South America.

From the automaker’s perspective, it could be an interesting challenge to encourage the community to contribute this type of content. One opportunity to support this idea is to develop an OSM-based navigation system for mobile use. After reaching maturity the system could be easily merged into the vehicle and would allow drivers to use premium directions from automotive-approved infotainment systems like EB street director — which we saw at CES in the QNX CAR Platform — for less money.

---

Daniel Gast has worked for Elektrobit since 2000, initially as software engineer, later as product manager for EB street director navigation. Subsequent to this he took over the responsibility for the business area navigation solutions. He now coordinates innovation management for Elektrobit Automotive. Daniel studied computer science in Erlangen.

Keep up to date with Elektrobit's latest automotive news and products by signing up for the EB Automotive Newsletter — Ed.

Read More

When is a road trip not a road trip?

The über-cool modified Mercedes-Benz CLA45 AMG that QNX unveiled at CES is on its inaugural road trip. Well, sort of. It's actually winging its way to Barcelona for Mobile World Congress 2014.

For those that didn't have a chance to see it at CES, the car incorporates state-of-the-art voice recognition; navigation from Elektrobit, Here, and Kotei; smartphone connectivity based on Miracast and on MirrorLink from RealVNC; advanced multi-media streaming, including iHeartRadio; and a reconfigurable digital instrument cluster, all delivered in a user-centric, multi-modal experience.

For those that have seen it, it is still worthwhile taking the time to check it out because this time around it's powered by Qualcomm’s Snapdragon S602A Automotive Solution. We announced the relationship with Qualcomm at CES and just over a month later we're showcasing the relationship in the Mercedes. Imagine what we'll do by Telematics Detroit.

You can check it out in the Qualcomm booth, Hall 3, Mobile World Congress 2014

Now powered by Qualcomm’s Snapdragon S602A Automotive Solution: the latest QNX technology
concept car, based on a Mercedes CLA45 AMG.

Read More

Why I should have gone to CES this year

No problem, I said, I'll be happy to stay back at the office. After all, somebody has to hold down the fort while everyone is at CES, and it may as well be me.

Of course, I didn't know what Audi was bringing to the show. Because if I did, I wouldn't have been so willing to take one for the team. If you're wondering what I am talking about, it's the new user-programmable instrument cluster for the upcoming 2015 Audi TT. It's based on the QNX CAR Platform for Infotainment, and it's about the coolest thing I've seen in a car, ever — even if I haven't yet had a chance to see it in person.

Roll the tape...

Read More

In good company: QNX partner solutions at 2014 CES

Guest post by Peter McCarthy of the QNX global partnerships team

Peter McCarthy

If anyone thinks that creating an infotainment system is easy, they obviously haven’t thought about it hard enough. It is, in fact, a massive undertaking that requires seamless integration of navigation engines, voice technologies, app environments, HMI tools, Internet music services, smartphone connectivity, automotive-hardened processors — the list goes on.

No single company could possibly offer all of these technologies. And even if it could, it still wouldn’t address the needs of automakers and tier one suppliers, who need the power of choice. Any company building an infotainment system needs the flexibility to combine Navigation Engine A with Processor B and Bluetooth Solution C.

Enabling customers to enjoy such choice without worrying about integration issues is something that QNX works very hard at. For evidence, look no further than our latest technology concept car, a modified Mercedes-Benz CLA45 AMG, which debuted this week at our CES booth. The car integrates an array of partner tech, including:

• voice recognition from Nuance
   
• navigation engines from Elektrobit (EB), Kotei Informatics, and HERE
   
• automotive processors from Texas Instruments
   
• MirrorLink smartphone-to-vehicle connectivity from RealVNC
   
• Android Jellybean version of iHeartRadio
   

Meanwhile, the head unit in our reference vehicle, also featured in the QNX booth, integrates several partner apps and holds the distinction of being the world’s first in-vehicle implementation of Qualcomm’s Snapdragon Automotive Solutions. And if that’s not enough, our booth contains demos of a navigation engine from Aisin AW and a digital instrument cluster built with HMI tools from HI Corporation.

Mind you, the action isn’t restricted to the QNX booth. Several partners have also gotten into the act and are demonstrating QNX-based systems in their CES booths and meeting rooms. For instance:

• Elektrobit — Demonstrating a new concept electric vehicle that sports an instrument cluster and infotainment system based on the QNX Neutrino Realtime Operating System.
   
• Freescale — Demonstrating the QNX CAR Platform for Infotainment on its i.MX 6 Applications Processors for Automotive.
   
• Gracenote — Demonstrating how its technology can personalize the in-vehicle music experience, using a system based on the QNX Neutrino OS.
   
• NVIDIA — Demonstrating Audi's newest infotainment system featuring the NVIDIA Tegra processor and the QNX Neutrino OS.
   
• Qualcomm — Demonstrating the QNX CAR Platform on Snapdragon Automotive Solutions.
   
• Red Bend Software — Demonstrating virtualization technology that runs the QNX CAR Platform and a digital instrument cluster on dual displays driven by a single processor.
   
• Texas Instruments — Demonstrating the QNX CAR Platform running on its latest Jacinto processors
  

For the fully skinny on QNX partner technology at CES, I invite you to check out our press release, along with joint announcements that we have issued with Aisin AW, HERE, HI Corporation, and Qualcomm.

---

About Peter
When he isn't talking on oversized mobile phones, Peter McCarthy serves as director of global partnerships at QNX Software Systems, where he is responsible for establishing and fostering partnerships with technology and services companies in all of the company's target industries.

Read More

The wraps are off! First look at the new QNX technology concept car

A quick tour of one of the vehicles that QNX is unveiling at 2014 CES

You know what? Writing this post isn’t easy. All I’ve got are words and pictures, and neither could ever do justice to the user experience offered by the new QNX technology concept car. They cannot, for example, recreate the rich, luminous sound of the car’s full-band and wide-band hands-free calls. Nor can they evoke how the car blends speech recognition with a touch interface and physical controls to make navigation, Internet radio, and other applications wonderfully easy to use.

But on second thought, words and pictures aren’t that bad. Especially when the car — and the in-dash systems that the QNX concept team created for it — are so downright gorgeous. So what are we sitting around for? Time for a tour!

Actually... hold that thought. I just want to mention that, if you visit our Flickr page, you can find full-resolution versions of most of the images I've posted here. Because why settle for low res? Okay, back to the tour.

The car
I've got two things to say here. First, the car is based on a Mercedes-Benz CLA45 AMG. If you guessed the model correctly based on the teaser images we published on the QNX website, I bow in homage to your eagle eye. Second, while we snapped this photo in the QNX garage, don’t think for a minute that the garage is ever this neat and tidy. On any given day, it’s chock full of drill presses, tool boxes, work tables, embedded boards, and QNX engineers joyously modding the world’s coolest cars — exactly the kind of place you expect it to be. And want it to be! But to humor the photographer, we (temporarily) made this corner clutter-free. We're nice that way.



The dash
Let's get behind the wheel, where you can see the car's custom-built digital instrument cluster and infotainment system. The bold design, the clean layout, the super-easy-to-access controls — they all add up to systems you want to interact with. Just as important, the look-and-feel of the instrument cluster and infotainment system are totally different from the corresponding systems in our previous concept car — an excellent illustration of how the QNX platform can help customers create their own branded experiences.



The multi-talented cluster
Time to zoom in on the digital instrument cluster, which helps simplify driving tasks and minimize distraction with an impressive array of features. Turn-by-turn directions pulled from the navigation system? Check. Video feed from front and rear-view cameras? Check. Notifications of incoming phone calls? Check. Alerts of incoming text messages, which you can listen to at the touch of a steering-wheel button? Check.



The Android app support
Automakers want to tap into the talents of the mobile app community, and the QNX CAR Platform for Infotainment helps them do just that, with built-in support for Android, OpenGL ES, and HTML5. In the concept car, for example, you'll find an Android Jellybean version of iHeartRadio, Clear Channel’s digital radio service, running in a secure application container. The QNX CAR Platform takes this same sandboxed approach to running HTML5 apps — perfect for protecting both the HMI and the overall system from unpredictable web content:



Helping you get there in more ways than one
We designed the QNX CAR Platform to give automotive developers the greatest possible choice and flexibility. And that’s exactly what you see when it comes to navigation. For instance, the car supports navigation from Elektrobit:



and from HERE:



and from Kotei Informatics:



If that’s not enough, a demo system in the QNX booth at CES also demonstrates a navigation system from Aisin AW — more on that in an upcoming post.

Pardon me while I barge in
As I alluded earlier, what you can't see in the new concept car is just as important as what you can see. For instance, if you look at this image, you'll see the infotainment system's media player. But what you can't see is new acoustics technology from QNX that lets you "barge in" and issue voice commands even when a song is playing. How cool is that?



When you find yourself in times of trouble...
... don't let it be, but rather, check and see. And to do that, you can use the infotainment system's virtual mechanic, which keeps tabs on your car's health, including fluid levels, brake wear, and, in this case, low tire pressure:



The cloud connection
Hold on, what's this? It looks like a smartphone app with an interface similar to that of the virtual mechanic, above. In fact, it's a lot more than that, and it touches on some cool (and very new) technology that can help cars become fully managed citizens of the cloud. More on that in an upcoming post.



That's it for now. For more details on what QNX is showcasing this week at CES, check out the press releases posted on the QNX website. And stay tuned to this channel for further updates from 2014 CES — including a profile of our very new QNX technology concept car for acoustics.

Read More

The ultimate show-me car

It's one thing to say you can do something. It's another thing to prove it. Which helps explain why we create technology concept cars.

You see, we like to tell people that flexibility and customization form the very DNA of the QNX CAR Platform for Infotainment. Which they do. But in the automotive world, people don't just say "tell me"; they say "show me". And so, we used the platform to transform a Bentley Continental GT into a unique concept car, equipped with features never before seen in a vehicle.

Now here's the thing. This is the same QNX CAR Platform found in the QNX reference vehicle, which I discussed last week. But when you compare the infotainment systems in the two vehicles, the differences are dramatic: different features, different branding, different look-and-feel.

The explanation is simple: The reference vehicle shows what the QNX CAR Platform can do out of the box, while the Bentley demonstrates what the platform lets you do once you add your imagination to mix. One platform, many possibilities.

Enough talk; time to look at the car. And let's start with the exterior, because wow:



The awesome (and full HD) center stack
And now let's move to the interior, where the first thing you see is a gorgeous center stack. This immense touchscreen features a gracefully curved surface, full HD graphics, and TI’s optical touch input technology, which allows a physical control knob to be mounted directly on the screen — a feature that’s cool and useful. The center stack supports a variety of applications, including a 3D navigation system from Elektrobit that makes full use of the display:



At 17 inches, the display is big enough to display other functions, such as the car’s media player or virtual mechanic, and still have plenty of room for navigation:



The awesome (and very configurable) digital instrument cluster
The instrument cluster is implemented entirely in software, though you would hardly know it — the virtual gauges are impressively realistic. More impressive still is the cluster’s ability to morph itself on the fly. Put the car in Drive, and the cluster will display a tach, gas gauge, temperature gauge, and turn-by-turn directions — the cluster pulls these directions from the center stack’s navigation system. Put the car in Reverse, and the cluster will display a video feed from the car’s backup camera. You can also have the cluster display the current weather and current sound track:



The awesome (and just plain fun) web app
The web app works with any web browser and allows the driver to view data that the car publishes to the cloud, such as fluid levels, tire pressure, brake wear, and the current track being played by the infotainment system. It even allows the driver to remotely start or stop the engine, open or close windows, and so on:



The awesome (and nicely integrated) smartphone support
The Bentley also showcases how the QNX CAR Platform enables advanced integration with popular smartphones. For instance, the car can communicate with a smartphone to stream music, or to provide notifications of incoming email, news feeds, and other real-time information — all displayed in a manner appropriate to the automotive context. Here's an example:



The awesome everything else
I’ve only scratched the surface of what the car can do. For instance, it also provides:

• Advanced voice rec — Just say “Hello Bentley,” and the car’s voice recognition system immediately comes to life and begins to interact with you — in a British accent, of course.
   
• Advanced multimedia system — Includes support for Internet radio.
   
• Video conferencing with realistic telepresence — Separate cameras for the driver and passenger provide independent video streams, while fullband voice technology from QNX offers expanded bandwidth for greater telepresence.
   
• LTE connectivity — The car features an LTE radio modem, as well as a Wi-Fi hotspot for devices you bring into the car.

Moving pictures
Okay, time for some video. Here's a fun look at the making of the car:



And here's a run-through of the car's many capabilities, filmed by our friends at TI during 2013 CES:

Read More