Ford ports SmartDeviceLink to QNX CAR Platform

QNX joins Ford, Toyota, and other industry leaders to help drive new standard for app integration.

Paul Leroux

For as long as I can remember, QNX Software Systems has been at the forefront of integrating cars and smartphones. Through our flexible OS architecture and large automotive ecosystem, we provide automakers and Tier 1 suppliers with the ultimate choice in connectivity options for smartphones and other smart devices. And now, QNX customers will have even greater choice, with the availability of Ford’s SmartDeviceLink (SDL) technology for the QNX CAR Platform for Infotainment.

If you’ve never heard of SDL, it’s the open source version of Ford AppLink, the software that allows Ford SYNC users to access smartphone apps through voice commands and dashboard controls. Ford donated AppLink to the open source community to create a standard way for consumers to interact with smartphone apps, regardless of which phone they use or vehicle they drive.

SDL is quickly gaining industry advocates, including Toyota, UI Evolution, and, of course QNX. What’s more, companies like PSA, Honda, Subaru, Mazda are evaluating it for use in next-generation vehicles.

Why the interest in SDL? Because it’s a flexible, vendor-neutral standard that can benefit drivers, automakers, and developers alike. With SDL:

• Drivers can interact with apps by using voice commands, steering-wheel buttons, and other in-car controls, so they can keep their eyes on the road and hands on the wheel.
• Automakers can deliver a consistent app experience across vehicles, while retaining the flexibility to customize that experience for each vehicle brand or model.
• Developers can create apps that can work across multiple smart devices and multiple automotive brands — which means they have greater incentive to create automotive apps.

SDL for QNX builds on a history of successful collaborations between Ford and QNX, including the QNX-powered Ford SYNC 3 infotainment system. According to Paul Elsila, CEO of Livio, the Ford subsidiary that maintains the SDL open source project, “With its large market share, QNX can play a key role in driving the adoption of auto industry standards, and we are excited to work with them in building vendor-neutral technology that can simplify the integration of smartphone apps in any brand or type of vehicle.”

SDL works with multiple smartphone platforms. Moreover, it is highly flexible: it can work across a full range of vehicles, from entry-level to premium, and across a wide range of displays. It can even be used in systems without displays — for instance, in systems that use a voice interface.

To learn more about SDL, check out the announcements that Ford, Toyota, and QNX issued this morning.

The demo is in the details

A new video of the 2015 QNX technology concept car reveals some thoughtful touches.

Paul Leroux

QNX technology concept cars serve a variety of purposes. They demonstrate, for example, how the flexibility of QNX technology can help automakers deliver unique user experiences. They also serve as vehicles — pun fully intended — for showcasing our vision of connected driving. And they explore how thoughtful integration of new technologies can make driving easier and more enjoyable.

It is this thoughtfulness that impresses me most about the cars. It is also the hardest aspect to convey in words and pictures — nothing beats sitting inside one of the cars and experiencing the nuances first hand.

The minute you get behind the wheel, you realize that our concept team is exploring answers to a multitude of questions. For instance, how do you bring more content into a car, without distracting the driver? How do you take types of information previously distributed across two or more screens and integrate them on a single display? How do you combine information about local speed limits with speedometer readouts to promote better driving? How do you make familiar activities, such as using the car radio, simpler and more intuitive? And how much should a car’s UX rely on the touch gestures that have become commonplace on smartphones and tablets?

Okay, enough from me. To see how our 2015 technology concept car, based on a Maserati Quattroporte, addresses these and other questions, check out this new video with my esteemed colleague Justin Moon. Justin does a great job of highlighting many of the nuances I just alluded to:



In just over a month, QNX will unveil a brand new technology concept vehicle. What kinds of questions will it explore? What kinds of answers will it propose? We can’t say too much yet, but stay tuned to this channel and to our CES 2016 microsite.

A low-down look at the QNX concept cars

Paul Leroux

It’s that time of year again. The QNX concept team has set the wheels in motion and started work on a brand new technology concept car, to be unveiled at CES 2016.

The principle behind our technology concept cars is simple in theory, but challenging in practice: Take a stock production vehicle off the dealer’s lot, mod it with new software and hardware, and create user experiences that make driving more connected, more enjoyable, and, in some cases, even safer.

It’s always fun to guess what kind of car the team will modify. But the real story lies in what they do with it. In recent years, they’ve implemented cloud-based diagnostics, engine sound enhancement, traffic sign recognition, collision warnings, speed alerts, natural voice recognition — the list goes on. There’s always a surprise or two, and I intend to keep it that way, so no hints about the new car until CES. ;-)

In the meantime, here is a retrospective of QNX technology concept cars, past and present. It’s #WheelWednesday, so instead of the usual eye candy, I’ve chosen images to suit the occasion. Enjoy.

The Maserati Quattroporte GTS
From the beginning, our technology concept cars have demonstrated how the QNX platform helps auto companies create connected (and compelling) user experiences. The Maserati, however, goes one step further. It shows how QNX can enable a seamless blend of infotainment and ADAS technologies to simplify driving tasks, warn of possible collisions, and enhance driver awareness. The car can even recommend an appropriate speed for upcoming curves. How cool is that?

---

The Mercedes CLA 45 AMG
By their very nature, technology concept cars have a short shelf life. The Mercedes, however, has defied the odds. It debuted in January 2014, but is still alive and well in Europe, and is about to be whisked off to an event in Dubai. The car features a multi-modal user experience that blends touch, voice, physical buttons, and a multi-function controller, enabling users to interact naturally with infotainment functions. The instrument cluster isn’t too shabby, either. It will even warn you to ease off the gas if you exceed the local speed limit.

---

The Bentley Continental GT
I dubbed our Bentley the “ultimate show-me car,” partially because that’s exactly what people would ask when you put them behind the wheel. The digital cluster was drop-dead gorgeous, but the head unit was the true pièce de résistance — an elegantly curved 17” high-definition display based on TI’s optical touch technology. And did I mention? The car’s voice rec system spoke with an English accent.

---

The Porsche 911 Carrera
Have you ever talked to a Porsche? Well, in this case, you could — and it would even talk back. We outfitted our 911 with cloud-based voice recognition (so you could control the nav system using natural language) and text-to-speech (so you could listen to incoming BBMs, emails, and text messages). But my favorite feature was one-touch Bluetooth pairing: you simply touched your phone to an NFC reader in the center console and, hey presto, the phone and car were automatically paired,

---

The Chevrolet Corvette
I have a confession to make: The Corvette is the only QNX technology concept car that I got to drive around the block. For some unfathomable reason, they never let me drive another one. Which is weird, because I saw the repair bill, and it wasn’t that much. In any case, the Corvette served as the platform for the very first QNX technology concept car, back in 2010. It included a reconfigurable instrument cluster and a smartphone-connected head unit — features that would become slicker and more sophisticated in our subsequent concept vehicles. My favorite feature: the reskinnable UI.

---

The Jeep Wrangler
Officially, the Wrangler serves as the QNX reference vehicle, demonstrating what the QNX CAR Platform can do out of the box. But it also does double-duty as a concept vehicle, showing how the QNX platform can help developers build leading-edge ADAS solutions. My favorite features: in-dash collision warnings and a fast-booting backup display.



Well, there you have it. In just a few months’ time, we will have the honor of introducing you to a brand new QNX technology concept car. Any guesses as to what the wheels will look like?

---

If you liked this post, you may also be interested in... The lost concept car photos

Intel and QNX Software Systems talk connected cars

By Megan Alink, Marketing Communications Director for Automotive

How many collaborations in embedded have lasted more than three decades? Our relationship with Intel comes immediately to mind.

I’m told it all began in 1981, when the first IBM PCs ran the Intel 8088 microprocessor and the OS could be swapped out for QNX. A quick trip to your local Sears, ComputerLand or IBM Product Center, followed by an order to QNX Support, and the most reliable computer the market could offer was all yours.

The first IBM PC: 21lbs without the diskette drive and complete with a cassette player jack.
Photo credit: https://www-03.ibm.com/ibm/history/exhibits/pc25/pc25_album.html

Fast forward 34 years, and QNX and Intel are still changing the technology landscape. Earlier this summer, Intel announced their plans to work with us on technologies for a variety of connected car applications, including infotainment systems, digital instrument clusters and advanced driver assistance systems (ADAS). Right around that same time, our Andrew Poliak, global director of business development, met up with Ken Obuszewski, director of automotive marketing for Intel, at TU-Automotive Detroit, where they spoke on camera with Bill Hampton from The AutoBeat Group. The topic was, of course, the connected car, and both gentlemen made compelling comments about the future of this exciting aspect of automotive and our mutual plans to deliver:

“With the evolution of the connected car, the capabilities that you’re seeing in the vehicle are really starting to expand dramatically…QNX is a long-time leader in the automotive market, Intel – we’re one of the technology leaders making a large investment in automotive, [so] it’s very natural for us to expand our working relationship and to bring consumers great technologies going forward.” — Ken Obuszewski

“Making systems that can be upgradable and updateable even after you purchase the vehicle so that way it stays fresh and current over the life of the vehicle is really a key foundation of a software platform running in a real[ly] flexible architecture like Intel’s.” — Andrew Poliak

Check out the entire video below. Many thanks to our friends at Intel for this opportunity to talk about our shared vision.

It seems like only yesterday...

By Megan Alink, Director of Marketing Communications for Automotive

What were you doing on September 14, 1999? It was likely an inauspicious day for most people, but for QNX, the date represented our official entry into the automotive market:

Don’t get me wrong — QNX was no tentative newcomer on the scene. After all, we were marking almost two decades in the embedded software business. QNX OS technology was already powering mission-critical systems for credit card processing, energy generation, healthcare, mail sorting, precision manufacturing, mining, security, and warehouse automation worldwide. (Whew!) But it was time to take that reliability and flexibility to more markets, ones with needs similar to our existing customer base. Enter automotive. (And we did.)

Today, we are pleased to be able to say that QNX software is found in more than 60 million vehicles on the road. In telematics systems like OnStar. In infotainment services like Volkswagen's RNS 850 GPS navigation system and Ford SYNC 3. In the digital instrument clusters of the state-of-the-art Audi TT and Mercedes S-Class Coupé.

60 million is a very big number. Obviously, we wouldn’t have reached this milestone without the support of our Tier 1 customers who build QNX into their systems every day, the 40+ automakers who choose these QNX-based systems, and our ecosystem of automotive partners who enrich our offering with their market-leading innovations. We want to thank all of these companies for the exciting and challenging opportunities they give us. Here’s to the next 60 million!

The A to Z of QNX in cars

Over 26 fast facts, brought to you by the English alphabet

Paul Leroux

A is for Audi, one of the first automakers to use QNX technology in its vehicles. For more than 15 years, Audi has put its trust in QNX, in state-of-the-art systems like the Audi virtual cockpit and the MIB II modular infotainment system. A is also for QNX acoustics software, which enhances hands-free voice communications, eliminates “boom noise” created by fuel-saving techniques, and even helps automakers create signature sounds for their engines.

B is for Bentley, BMW, and Buick, and for their QNX-powered infotainment systems, which include BMW ConnectedDrive and Buick Intellilink.

C is for concept vehicles, including the latest QNX technology concept car, a modded Maserati Quattroporte GTS. The car integrates an array of technologies — including cameras, LiDAR, ultrasonic sensors, and specialized navigation engines — to show how QNX-based ADAS systems can simplify driving tasks, warn of possible collisions, and enhance driver awareness.

D is for the digital instrument clusters in vehicles from Alpha Romeo, Audi, GM, Jaguar, Mercedes-Benz, and Land Rover. These QNX-powered displays can reconfigure themselves on the fly, providing quick, convenient access to turn-by-turn directions, back-up video, incoming phone calls, and a host of other information.

E is for experience. QNX has served the automotive market since the late 1990s, working with car makers and tier one suppliers to create infotainment systems for tens of millions of vehicles. QNX has been at work in safety-critical industrial applications even longer — since the 1980s. This unique pedigree makes QNX perfectly suited for the next generation of in-vehicle systems, which will consolidate infotainment and safety-related functions on a single, cost-effective platform.

F is for Ford, which has chosen the QNX Neutrino OS for its new SYNC 3 infotainment system. The system will debut this summer in the 2016 Ford Escape and Ford Fiesta and will be one of the first infotainment systems to support both Apple CarPlay and Android Auto.

G is for GM and its QNX-based OnStar system, which is now available in almost all of the company’s vehicles. GM also uses QNX OS and acoustics technology in several infotainment systems, including the award-winning Chevy MyLink.

H is for hypervisor. By using the QNX Hypervisor, automotive developers can consolidate multiple OSs onto a single system-on-chip to reduce the cost, size, weight, and power consumption of their designs. The hypervisor can also simplify safety certification efforts by keeping safety-related and non-safety-related software components isolated from each other.

I is for the ISO 26262 standard for functional safety in road vehicles. The QNX OS for Automotive Safety has been certified to this standard, at Automotive Safety Integrity Level D — the highest level achievable. This certification makes the OS suitable for a wide variety of digital clusters, heads-up displays, and ADAS applications, from adaptive cruise control to pedestrian detection.

J is for Jeep. The QNX reference vehicle, based on a Jeep Wrangler, showcases what the QNX CAR Platform for Infotainment can do out of the box. In its latest iteration, the reference vehicle ups the ante with traffic sign detection, lane departure warnings, curve speed warnings, collision avoidance alerts, backup displays, and other ADAS features for enhancing driver awareness.

K is for Kia, which uses QNX technology in the infotainment and connectivity systems for several of its vehicles.

L is for LG, a long-time QNX customer that is using several QNX technologies to develop a new generation of infotainment systems, digital clusters, and ADAS systems for the global automotive market.

M is for Mercedes-Benz, which offers QNX-based infotainment systems in several of its vehicles, including the head unit and digital instrument cluster in the S Class Coupe. M is also for market share: according to IHS Automotive, QNX commands more than 50% of the infotainment software market.

N is for navigation. Thanks to the navigation framework in the QNX CAR Platform, automakers can integrate a rich variety of navigation solutions into their cars.

O is for the over-the-air update solution of the BlackBerry IoT Platform, which will help automakers cut maintenance costs, reduce expensive recalls, improve customer satisfaction, and keep vehicles up to date with compelling new features long after they have rolled off the assembly line.

P is for partnerships. When automotive companies choose QNX, they also tap into an incredibly rich partner ecosystem that provides infotainment apps, smartphone connectivity solutions, navigation engines, automotive processors, voice recognition engines, user interface tools, and other pre-integrated technologies. P is also for Porsche, which uses the QNX Neutrino OS in its head units, and for Porsche 911, which formed the basis of one of the first QNX concept cars.

Q is for the QNX CAR Platform for Infotainment, a comprehensive solution that pre-integrates partner technologies with road-proven QNX software to jump-start customer projects.

R is for the reliability that QNX OS technology brings to advanced driver assistance systems and other safety-related components in the vehicle — the same technology proven in space shuttles, nuclear plants, and medical devices.

S is for the security expertise and solutions that Certicom and QNX bring to automotive systems. S is also for the advanced smartphone integration of the QNX CAR Platform, which allows infotainment systems to support the latest brought-in solutions, such as Apple CarPlay and Android Auto. S is also for the scalability of QNX technology, which allows customers to use a single software platform across all of their product lines, from high-volume economy vehicles to luxury models. And last, but not least, S is for the more than sixty million vehicles worldwide that use QNX technology. (S sure is a busy letter!)

T is for Toyota, which uses QNX technology in infotainment systems like Entune and Touch ‘n’ Go. T is also for tools: using the QNX Momentics Tool Suite, automotive developers can root out subtle bugs and optimize the performance of their sophisticated, multi-core systems.

U is for unified user interface. With QNX, automotive developers can choose from a rich set of user interface technologies, including Qt, HTML5, OpenGL ES, and third-party toolkits. Better yet, they can blend these various technologies on the same display, at the same time, for the ultimate in design flexibility.

V is for the Volkswagen vehicles, including the Touareg, Passat, Polo, Golf, and Golf GTI, that use the QNX Neutrino OS and QNX middleware technology in their infotainment systems.

W is for the QNX Wireless Framework, which brings smartphone-caliber connectivity to infotainment systems, telematics units, and a variety of other embedded devices. The framework abstracts the complexity of modem control, enabling developers to upgrade cellular and Wi-Fi hardware without having to rewrite their applications.

X, Y, and Z are for the 3D navigation solutions and the 3D APIs and partner toolkits supported by the QNX CAR Platform. I could show you many examples of these solutions in action, but my personal favorite is the QNX technology concept car based on a Bentley Continental GT. Because awesome.

Before you go... This post mentions a number of automotive customers, but please don’t consider it a complete list. I would have gotten them all in, but I ran out of letters!

Concept Car mit QNX-Technologie feiert seinen Auftakt in Europa

Ein Gastbeitrag von Matthias Stumpf, Vertriebsleiter Automotive EMEA, QNX Software Systems
(Guest post from Matthias Stumpf, manager of automotive sales EMEA, QNX Software Systems)

Nachdem der Mercedes-Benz CLA45 AMG, ein mit QNX-Technologie ausgestattetes Concept Car, in Nordamerika für Schlagzeilen gesorgt hat, wagt es nun für seine Europa-Tour den Sprung über den großen Teich. Startschuss ist auf dem Automobile Elektronik Kongress am 23. und 24. Juni in Ludwigsburg, wo das Auto zum ersten Mal in Europa ausgestellt wird.

Alle die den Mercedes in Aktion sehen wollen, sollten im Hauptfoyer des Kongresses vorbeischauen. Dort wird gezeigt, wie der Fahrer völlig natürlich und intuitiv mit dem im Auto verbauten Infotainment-System und den digitalen Instrumenten-Gruppen interagieren kann.

Eine extrabreite Head Unit
Das Auto verfügt über eine extrabreite Head Unit, die Fahrer und Beifahrer mit Hilfe detaillierter Grafiken und über ein durchgehendes 7 Zoll bis 21 Zoll großes Interface mit Informationen versorgt. Dank des nutzerorientierten Designs kann das Infotainment-System optional über den Touchscreen, physische Knöpfe, den Multifunktions-Controller oder via Sprachbefehl gesteuert werden. Das System basiert auf der QNX CAR Platform for Infotainment, einem umfangreichen Ökosystem, das bereits QNX-Software-Systems-Technologien und zahlreiche Partner integriert hat:



Konfigurierbares Instrumente-Cluster
Das digitale Instrumente-Cluster kann dynamisch angepasst werden und zeigt Wegbeschreibungen in Echtzeit, eingehende Telefonanrufe, Videos der Front- und Heck-Bordkameras, Drehzahl- und Geschwindigkeitsmesser sowie weitere virtuelle Instrumente an. Via Tastendruck auf dem Lenkrad werden sogar empfangene Textnachrichten vorgelesen; so behält der Fahrer seine Augen auf der Straße:



Darüber hinaus können mit der “virtuellen Bordmechanik” des Clusters Statusinformationen wie Reifendruck, Bremsverschleiß sowie Treibstoff-, Öl- und Scheibenwaschwasserstand abgerufen werden:



Wenn Sie an weiteren Informationen über die zahlreichen Features des Concept Cars interessiert sind, lesen Sie hier und hier unsere vorangegangenen Blogbeiträge.

Wir freuen uns, Sie in Ludwigsburg begrüßen zu dürfen! Alle weiteren Termine der Europa-Tour des Concept Cars erhalten Sie hier auf unserem Blog.

Getting in sync with brought-in devices

Building a head unit that needs to sync with smartphones, media players, memory cards, and USB sticks? With the QNX CAR Platform, you won’t be left to your own devices.

Paul Leroux

In previous posts, I discussed how the QNX CAR Platform for Infotainment is adept at juggling multiple concurrent tasks. For instance, it can perform 3D navigation, process voice signals, provide active noise control, display vehicle data, manage audio, run multiple application environments, and still deliver a fast, responsive user experience. If that’s not enough, it can also detect and play content from an array of media devices, including local drives, SD cards, and iPods, as well as Bluetooth, DLNA, and MTP devices.

When plugging a media device into a car’s head unit, most users expect immediate access to the device content; they also want to browse the content by metadata, such as genre, title, or artist. To present this content, the head unit must perform metadata synching. The question is, how can the head unit make the content instantly available, even when the media device contains thousands of files that may take many seconds or even minutes to fully synchronize?

To complicate matters, users often want to switch from one media source to another. For instance, a user listening to music stored on a DLNA device may ask the head unit to switch to an Internet radio station. From the user’s perspective, the switch should be fast, simple, and intuitive.

Handling device attachments (and

detachments) gracefully.

The head unit must also cope with the vagaries of user behavior. For instance, if the user yanks out a USB media stick during synching or playback, the system should recover gracefully; it should also provide appropriate feedback, such as displaying a menu that asks the user to choose from another media source. Likewise, if the user yanks out the media device and re-inserts it, the system shouldn’t get confused. Rather, it should simply resume synching content where it left off.

Handling scenarios like these is the job of the QNX CAR Platform’s multimedia architecture.

Architecture at a glance
The multimedia architecture integrates several software components to automatically detect media devices, synchronize metadata with media databases, browse the contents of devices, and, of course, play audio and video files. Together, these components form three layers:

• Human machine interface, or HMI

• Multimedia components

• OS services

Let’s look at each of these layers in turn, starting with the HMI.

At the top of the HMI layer, you’ll see the Media Player, a reference application that allows end-users to control media browsing and playback. Developers can customize this player or write their own player apps, using APIs provided by the QNX CAR Platform.

The Media Player comes in two flavors, HTML5 and Qt 5. To communicate with the architecture’s multimedia engine (mm-player), the HTML5 version uses the car.mediaplayer JavaScript API while the Qt version uses the QPlayer library. In addition to these interfaces, custom apps can use the multimedia engine’s C API. All three interfaces — car.mediaplayer, QPlayer, and C API — provide an abstraction layer that allows a media player app to:

• retrieve a list of accessible media sources: local drives, USB storage devices, iPods, etc.

• retrieve track metadata: artist name, album name, track title, etc.

• start and stop playback

• jump to a specific track

• handle updates in playback state, media sources, and track position

The interfaces that provide access to these operations aren’t specific to any device type, so player apps can work with a wide variety of media hardware.

The media player can quickly access and display a variety of metadata (artist name, album name, track title, etc.) stored in a small-footprint SQL database.

Multimedia components layer
If you look at the top of the multimedia components layer, you’ll see a box labeled mm-player; this is the architecture’s media browsing and playback engine. The mm-player does the dirty work of retrieving metadata, starting playback, jumping to a specific track, etc., which makes custom player apps easier to design. It also supports a large variety of media sources, including:

• local drives

• USB storage devices

• Apple iPod devices

• DLNA devices, including phones and media players

• MTP devices, including PDAs and media players

• devices paired through Bluetooth

To perform media operations requested by a client media player, mm-player works in concert with several lower-level components that help navigate media-store file systems, read metadata from media files, and manage media flows during playback. The components include a series of plugins (POSIX, AVRCP, DLNA, etc.) that interface with different device types. For instance, let’s say you insert an SD card. The POSIX plugin supports this type of device, so it will learn of the insertion and inform mm-player of the newly connected media source; it will also support any subsequent media operations on the SD card.

If you look again at the diagram, you’ll see several other components that provide services to mm-player. These include:

• mm-detect — discovers media devices and initiates synchronization of metadata
• mm-sync — synchronizes metadata from tracks and playlists on media devices into small-footprint SQL databases called QDB databases
• mm-renderer — plays audio and video tracks, and reports playback state
• io-audio — starts audio device drivers to enable the output of audio streams

OS services layer
The lowest layer of the multimedia architecture includes device drivers and protocol stacks that, among other things, detect whether the user has inserted or removed any media device. The following diagram summarizes what happens when one of these services detects an insertion:

1. User inserts the device.
2. The corresponding driver or protocol stack informs device publishers of the insertion.
3. The publishers write the device information to Persistent Publish Subscribe (PPS) objects in a directory monitored by the mm-detect service. (Read my previous posts here and here to learn how QNX PPS messaging enables loosely coupled, easy-to-extend designs.)
4. To start synchronizing the device’s metadata, mm-detect loads the device’s QDB database into memory and passes the device’s mountpoint and database name to mm-sync.
5. mm-sync synchronizes the metadata of all media files on the device.
6. mm-sync uses media libraries to read file paths and other information from media tracks found on the device. It then copies the extracted metadata into the appropriate database tables and columns. Applications can then query the QDB database to obtain metadata information such as track title and album name.

These steps may describe how the architecture detects and synchronizes with devices, but they can't capture the efficiency of the architecture and how it can deliver a fast, responsive user experience. For that, I invite you to check out this video on the QNX CAR Platform. The section on multimedia synchronization starts at the 1:32 mark, but I encourage you to watch the whole thing to see how the platform performs multimedia operations while concurrently managing other tasks:



Media browsing and playback
I’ve touched on how the multimedia architecture automatically detects and synchronizes devices. But of course, it does a lot more, including media browsing and media playback. To learn more about these features, visit the QNX CAR Platform documentation on the QNX website.

---

Previous posts in the QNX CAR Platform series:
 

• A question of getting there — wherein I examine how the platform gives customers the flexibility to choose from a variety of navigation solutions

• A question of architecture — wherein I discuss how the platform simplifies the challenge of integrating multiple disparate technologies, from graphics to silicon

• A question of concurrency — wherein I address the a priori question: why does the auto industry need a platform like QNX CAR in the first place?

We showed you so

QNX has been building NFC functionality into concept cars since 2011. Now, with the advent of automotive-grade tags and chips, NFC may be coming to a dashboard near you.

Paul Leroux

Why does QNX transform vehicles like the Maserati QuattroPorte GTS, Mercedes-Benz CLA45, and Bentley Continental into technology concept cars? I can think of many reasons, but three stand out. First, the cars allow us to demonstrate the inherent flexibility and customizability of QNX technology. If you could put all of the cars side by side, you would quickly see that, while they all use the same QNX platform, each has a unique feature set and a distinctive look-and-feel — no two are alike. This flexibility is of immense importance to automakers, who, for reasons of market differentiation, need to deliver a unique brand experience in each marque or vehicle line. Alf Pollex, Head of Connected Car and Infotainment at Volkswagen, says it best: “the QNX platform... enables us to offer a full range of infotainment systems, from premium level to mass volume, using a single, proven software base.”

Second, the cars explore how thoughtful integration of new technologies can make driving easier, more enjoyable, and perhaps even a little safer. Case in point: the Maserati’s obstacle awareness display, which demonstrates how ADAS systems can aggregate data from ultrasonic and LiDAR sensors to help drivers become more aware of their surroundings. This display works much like a heads-up display, but instead of providing speed, RPM, or navigation information, it offers visual cues that help the driver gauge the direction and proximity of objects around the vehicle — pedestrians, for example.

Look ma, no menus: At 2012 CES, a QNX concept car

showcased how NFC can enable single-tap Bluetooth
phone pairing. Source CrackBerry.com

Third, the cars explore solutions that address real and immediate pain points. Take, for example, the pairing of Bluetooth phones. Many consumers find this task difficult and time-consuming; automakers, for their part, see it as a source of customer dissatisfaction. So, in 2011, we started to equip some of our concept cars with near field communication (NFC) technology that enables one-touch phone pairing. This pairing is as easy it sounds: you simply touch an NFC-enabled phone to an NFC tag embedded in the car’s console, and voilà, pairing with the car’s infotainment system happens automatically.

Prime time
NFC in the car holds much promise, but when, exactly, will it be ready for prime time? Pretty soon, as it turns out. In a recent article, “NFC looks to score big in cars,” Automotive Engineering International points to several vendors, including Broadcom, NXP, Melexis, Texas Instruments and ams AG, that have either announced or shipped automotive-grade NFC solutions. NXP, for example, expects that some of its NFC tags and chips will first go into production cars around 2016.

Mind you, NFC isn’t just for phone pairing. It can, for example, enable key-fob applications that allow phones to store user preferences for seat positions and radio stations. It can also enable use cases in which multiple drivers operate the same vehicle, such as car sharing or fleet management. The important thing is, it’s moving from concept to production, marking one more step in the seamless integration of cars and smartphones.

---

Did you know…

• BMW embeds NFC tags not only in its cars, but also in print ads.

• IHS has predicted that, in 2018, global shipments of NFC-equipped cellphones will reach 1.2 billion units.

• NFC World publishes a living document that lists all of the NFC handsets available worldwide.

QNX rolls out new wireless framework

Framework abstracts the complexity of modem control, enabling embedded developers to upgrade cellular and Wi-Fi hardware without having to rewrite applications.

Paul Leroux

Building cellular or Wi-Fi connectivity into a vehicle is never trivial (read: it can be an outright headache). Take, for example, the large amount of software needed to manage a cellular modem. The software needs to monitor and control power consumption, ensure data throughput and reliability, minimize call drops and call-setup failures, and manage modem reset and recovery — because even the best modems crash.

To complicate matters, modem technology for embedded systems is evolving quickly. Development teams need the freedom to upgrade to newer, more capable modems, without having to rewrite or redesign their applications. Likewise, they need the flexibility to choose the best modem for a particular region, product line, or price point.

Enter the QNX Wireless Framework, which QNX Software Systems released last week. Designed to simplify system design, the framework encapsulates the complexities of modem control through an easy-to-use application programming interface (API). Moreover, the API remains consistent across wireless modules and chipsets, allowing systems to quickly support new cellular or Wi-Fi products from vendors such as Gemalto, Sierra Wireless, Telit Wireless Solutions, and u-blox.

The QNX Wireless Framework can scale to meet a broad range of product requirements.
 

The QNX Wireless Framework is built on technology already deployed in millions of BlackBerry devices, supported by hundreds of mobile carriers, and field-proven in complex wireless environments. Better yet, it's backed by a dedicated, world-class team of wireless experts with hundreds of person-years of experience building carrier-grade mobile products.

To learn more about the QNX Wireless framework:

• read the press release

• read the product overview and product brief

• download the webinar on applying smartphone wireless technology to connected embedded systems

Keeping it fresh for 35 years

By Megan Alink, Director of Marketing Communications for Automotive

Recently, my colleagues Paul Leroux and Matt Young showed off a shiny new infographic that enlightens readers to the many ways they encounter QNX-based systems in daily life (here and here). After three-and-a-half decades in business we’ve certainly been around the block a time or two, and you might think things are getting a bit stale. As the infographic shows, that couldn’t be further from the truth here at QNX. From up in the stars to down on the roads; in planes, trains, and automobiles (and boats too); whether you’re mailing a letter or crafting a BBM on your BlackBerry smartphone, the number and breadth of applications in which our customers deploy QNX technology is simply astounding.

For those who like some sound with their pictures, we also made a video to drive home the point that, wherever you are and whatever you do, chances are you’ll encounter a little QNX. Check it out:

Building smartphone-caliber connectivity into cars

Paul Leroux

Implementing cellular and Wi-Fi connectivity in a vehicle is never trivial. But with the right technology, the task can become a lot simpler.

When it comes to selling cars, just how important is connectivity? Can the services provided by connected cars, such as Internet radio, remote diagnostics, and real-time traffic information, influence vehicle buying decisions? And if so, how much?

In 2014, telecom giant Telefónica decided to find out. In a survey of 5000 consumers, the company found that 71% of respondents were interested in using, or were already using, connected car services. Other studies report similar findings. Parks Associates, for example, found that 78% of people who already own a connected car will demand connectivity features in their next vehicle.

Of course, “connected car” means different things to different people. It could, for example, refer to a car that has a built-in cellular modem, or to a car that uses the driver’s smartphone to access online services. Moreover, the features offered by my connected car may differ completely from the features offered by your connected car. But no matter what form it takes, or what applications it enables, connectivity in the car can be a challenge to implement. In a recent blog post on LinkedIn, Roger Lanctot of Strategy Analytics attests to this difficulty, stating that nearly every car maker seeking to implement connectivity has stumbled on issues ranging from bad connections and poor user interfaces to interminable delays.

Consider, for example, the challenge of embedding a cellular modem in a vehicle — or any other embedded device, for that matter. Initializing and managing the modem requires a large set of software that, among other things, must:

• handle modem reset and recovery, because even the best modems crash
• monitor and manage power consumption to optimize current draw
• ensure data throughput and reliability
• reduce or eliminate call-drops and call-setup failures

The challenge doesn’t stop there. Network operators, for example, are paying more attention to M2M connections on their networks, thereby increasing the demand for operator-approved modems and modules. Meanwhile, system designers may need to swap out modems to target different regions or price points, or to take advantage of newer, more capable modem technology. The goal, then, is to implement a flexible, future-proofed design that can accommodate such changes with a bare minimum of fuss.

Enter a new webinar hosted by my colleagues Karen Bachman and Leo Forget. In “Applying smartphone wireless technology to connected embedded systems,” they will examine the challenges of embedding wireless connectivity and explore how to address these challenges through software frameworks developed for smartphones and other mobile devices. True to the title, Karen and Leo will look at use cases not just for automotive, but for other industries as well, such as medical and industrial. The bulk of the conversation, though, will focus on common issues that embedded developers face, regardless of the device type they are building.

Attend this webinar to learn about:

• Applications that stand to benefit the most from wireless connectivity
• Challenges and complexity of bringing connectivity to cars and other embedded systems
• Potential security and privacy risks introduced by wireless connectivity, including unauthorized access and unencrypted data transfer
• The benefits of creating flexible products that easily accommodate advances in modem technology

Here are the webinar coordinates:

Applying smartphone wireless technology to connected embedded systems
Thursday, March 26, 2015
12:00 pm to 1:00 pm EST
Register: TechOnLine

Long time, no see: Catching up with the QNX CAR Platform

By Megan Alink, Director of Marketing Communications for Automotive

It’s a fact — a person simply can’t be in two places at one time. I can’t, you can’t, and the demo team at QNX can’t (especially when they’re brainstorming exciting showcase projects for 2016… but that’s another blog. Note to self.) So what’s a QNX-loving, software-admiring, car aficionado to do when he or she has lost touch and wants to see the latest on the QNX CAR Platform for Infotainment? Video, my friends.

One of the latest additions to our QNX Cam YouTube channel is an update to a video made just over two and a half years ago, in which my colleague, Sheridan Ethier, took viewers on a feature-by-feature walkthrough of the QNX CAR Platform. Now, Sheridan’s back for another tour, so sit back and enjoy a good, old-fashioned catch-up with what’s been going on with our flagship automotive product (with time references, just in case you’re in a bit of a hurry).

Sheridan Ethier hits the road in the QNX reference vehicle based on a modified Jeep Wrangler, running the latest QNX CAR Platform for Infotainment.

We kick things off with a look at one of the most popular elements of an infotainment system — multimedia. Starting around the 01:30 mark, Sheridan shows how the QNX CAR Platform supports a variety of music formats and media sources, from the system’s own multimedia player to a brought-in device. And when your passenger is agitating to switch from the CCR playlist on your MP3 device to Meghan Trainor on her USB music collection, the platform’s fast detection and sync time means you’ll barely miss a head-bob.

The QNX CAR Platform’s native multimedia player — the “juke box” — is just one of many options for enjoying your music.

About five minutes in, we take a look at how the QNX CAR Platform implements voice recognition. Whether you’re seeking out a hot latté, navigating to the nearest airport, or calling a co-worker to say you’ll be a few minutes late, the QNX CAR Platform lets you do what you want to do while doing what you need to do — keeping your hands on the wheel and your eyes on the road. Don’t miss a look at concurrency (previously discussed here by Paul Leroux) during this segment, when Sheridan runs the results of his voice commands (multimedia, navigation, and a hands-free call) smoothly at the same time.

Using voice recognition, users can navigate to a destination by address or point of interest description (such as an airport).

At eight minutes, Sheridan tells us about one of the best examples of the flexibility of the QNX CAR Platform — its support for application environments, including native C/C++, Qt, HTML5, and APK for running Android applications. The platform’s audio management capability makes a cameo appearance when Sheridan switches between the native multimedia player and the Pandora HTML5 app.

Pandora is just one of the HTML5 applications supported by the QNX CAR Platform.

As Sheridan tells us (at approximately 12:00), the ability to project smartphone screens and applications into the vehicle is an important trend in automotive. With technologies like MirrorLink, users can access nearly all of the applications available on their smartphone right from the head unit.

Projection technologies like MirrorLink allow automakers to select which applications will be delivered to the vehicle’s head unit from the user’s connected smartphone. 

Finally, we take a look at two interesting features that differentiate the QNX CAR Platform — last mode persistence (e.g. when the song you were listening to when you turned the car off starts up at the same point when you turn the car back on) and fastboot (which, in the case of QNX CAR, can bring your backup camera to life in 0.8 seconds, far less than the NHTSA-mandated 2 seconds). These features work hand-in-hand to ensure a safer, more enjoyable, more responsive driving experience.

Fastboot in 0.8 seconds means that when you’re ready to reverse, your car is ready to show you the way.

Interested in learning more about the QNX CAR Platform for Infotainment? Check out Paul Leroux’s blog on the architecture of this sophisticated piece of software. To see QNX CAR in action, read Tina Jeffrey’s blog, in which she talks about how the platform was implemented in the reimagined QNX reference vehicle for CES 2015.

Check out the video here:

QNX and Qualcomm Technologies give show goers another stunner at 2015 CES

Guest post By Nilesh Parekh, Director of Product Management at Qualcomm Technologies

Year after year, CES attendees are repeatedly amazed by the advances in automobile infotainment. Not so long ago, it was about having a great stereo in the car and maybe a tiny screen in the center stack with a primitive navigation system. Then came Bluetooth connectivity… multiple multimedia screens… front and rear displays… gaming… 3G and 4G connectivity… Wi-Fi hotspots…

This year, QNX Software Systems and Qualcomm Technologies are bringing you something really special — a “mashup,” you could say, of a Maserati Quattroporte GTS, the QNX OS, the QNX CAR Platform, and the Snapdragon™ Automotive Solutions (SAS) platform, all working together in a show-stopping technology concept car.



The QNX concept team worked closely with Qualcomm Technologies to create an immersive in-vehicle experience using advanced technologies for infotainment, digital instrument clusters, and driver assistance systems. These systems feature high-resolution UIs with multi-touch support, 3D graphics for navigation, and LiDAR-based obstacle detection. And note the side mirrors have been swapped for smart displays that eliminate typical vehicle blind spots and present relevant color-coded overlay information to promote safer driving.

Inner beauty

Admittedly, the car is a thing of beauty. But being in the tech field, I find the real beauty inside the car — deep inside. There, working hand-in-hand with the field-proven QNX OS, is the Snapdragon Automotive Solutions (SAS) platform. The SAS platform manages all infotainment features; it also processes vital vehicle safety information, collected via a myriad of camera, ultrasonic, and LIDAR sensors, and delivers all relevant information to the driver in real time — that’s a lot of computing and processing power.

What’s so special about the SAS platform? First, let me define what it is (put on your tech hats): a highly integrated, thermal-efficient automotive-grade platform that incorporates an optimized combination of CPU, GPU, 4G LTE modem, GPS/GNSS, Bluetooth, and Wi-Fi. What’s special is that it is engineered to not only enhance the driver and passenger experiences with the infotainment features we know today, but it future-proofs the vehicle for next-generation features — some of which haven’t even been dreamt of yet. More important, it allows automakers and tier ones to accelerate development schedules and to focus on creating feature-rich, reliable infotainment and safety systems built with solutions such as the QNX CAR Platform.

Let’s take a closer look at the three areas of this special technology concept car where I think the presence of SAS makes the biggest impact: the instrument cluster, the infotainment system, and the driver assistance system. And keep in mind that this vehicle is more than a showcase of what’s “out there” and possible — it’s a test bed we’ll use to gain relevant experience and knowledge that we can apply to future technologies in real cars.

The all-digital, reconfigurable instrument cluster
The cluster — the go-to information display for drivers — on the technology concept car can cycle through a number of views, providing the driver with relevant data on what’s going on, in, and around the car in real time. Rear-view park assist, current audio track, navigation data, forward-collision warnings, and vehicle data are all examples of information rendered in the cluster:



The infotainment system
You can’t help but notice the 12” portrait touchscreen next to the instrument cluster. The system is built using the QNX CAR Platform for Infotainment — an automotive-hardened software platform built on the QNX OS. The QNX CAR Platform runs on the SAS hardware and implements a sophisticated UI design that supports voice recognition, touch (including tap, swipe, and pinch and zoom on the map), and synchronizes with the rear-seat control system, allowing rear-seat passengers to manage navigation, song selection, and temperature settings.

Here's a photo of the touchscreen in action. As you can see, it's displaying map info, an incoming call, and a "Now Playing" section. If you simply tap the map, which is powered by Elektrobit (EB) street director navigation and works with EB electronic horizon, it will automatically take over two-thirds of the screen:



Driver assistance system
The car's driver assistance system makes use of LIDAR and ultrasonic sensors to detect the presence of obstacles around the vehicle and renders warning information to the driver through the cluster or side-view displays, and also through an obstacle awareness system made up of dashboard LEDs. This system projects color-coded warnings onto the windshield to indicate the location and proximity of the object.

Other highlights include:

• “Always On” rear-view display — The rear-view mirror has been converted into a display that renders a wide-angle perspective of the area behind the car
• Elektrobit electronic horizon — Topographical map data is used to provide curve-speed recommendations and warnings that are displayed in the cluster

If you have the opportunity to see this car at CES, I highly recommend it — it really is an amazing technology concept vehicle that showcases the next-generation of automobile infotainment and safety. It will be located in the Qualcomm booth located in Central Plaza #21A Jan 6-9. If you cannot make it to CES, you can learn more here.

Volkswagen and LG Gear up with QNX

Design wins put QNX technology in a wide range of infotainment systems, instrument clusters, and ADAS solutions.

Earlier today, QNX Software Systems announced that infotainment systems powered by the QNX Neutrino OS are now shipping in several 2015 Volkswagen vehicle models, including the Touareg, Passat, Polo, Golf, and Golf GTI.

The systems include the RNS 850 GPS navigation system in the Volkswagen Touareg, which recently introduced support for 3D Google Earth maps and Google Street View. The system also offers realtime traffic information, points-of-interest search, reverse camera display, voice control, Bluetooth connectivity, rich multimedia support, four-zone climate control, a high-resolution 8-inch color touchscreen, and other advanced features.

Bird's eye view: the RNS 850 GPS navigation system for the Volkswagen Touareg SUV. Source: VW

“At Volkswagen, we believe deeply in delivering the highest quality driving experience, regardless of the cost, size, and features of the vehicle,” commented Alf Pollex, Head of Connected Car and Infotainment at Volkswagen AG. “The scalable architecture of the QNX platform is well-suited to our approach, enabling us to offer a full range of infotainment systems, from premium level to mass volume, using a single, proven software base for our Modular Infotainment Modules (MIB) and the RNS 850 system.”

QNX and LG: a proven partnership
QNX also announced that LG Electronics’ Vehicle Components (VC) Company will use a range of QNX solutions to build infotainment systems, digital instrument clusters, and advanced driver assistance systems (ADAS) for the global automotive market.

The new initiative builds on a long history of collaboration between LG and QNX Software Systems, who have worked together on successful, large-volume telematics production programs. For the new systems, QNX will provide LG with the QNX CAR Platform for Infotainment, the QNX Neutrino OS, the QNX OS for Automotive Safety, and QNX Acoustics for Voice.

“QNX Software Systems has been our trusted supplier
for more than a decade... helping LG deliver millions
of high-quality systems to the world’s automakers”
— Won-Yong Hwang, LG's VC Company
“QNX Software Systems has been our trusted supplier for more than a decade, providing flexible software solutions that have helped LG deliver millions of high-quality systems to the world’s automakers,” commented Won-Yong Hwang, Director and Head of AVN development department, LG Electronics’ VC Company. “This same flexibility allows us to leverage our existing QNX expertise in new and growing markets such as ADAS, where the proven reliability of QNX Software Systems’ technology can play a critical role in addressing automotive safety requirements.”

Visit the QNX website to learn more about the Volkswagen and LG announcements.