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.

Read More

We’re blushing!

By Megan Alink, Director of Marketing Communications for Automotive

The folks over at TU-Automotive announced their awards finalists today, and what a day it has turned out to be! QNX Software Systems has been declared a finalist in two categories:

• TU-Automotive Influencer of the Year: Andrew Poliak, Global Business Development Director, QNX Software Systems
• Best Mobility Solution Industry Newcomer: QNX Software Systems for the QNX Wireless Framework

Andrew Poliak

A 15-year veteran of QNX, Andrew Poliak is one of the leading experts in the automotive software industry and a trusted advisor and spokesperson for media and analysts on trends and issues, including in the areas of safety, security, ADAS, infotainment, instrument clusters, mobile connectivity, and telematics. On a daily basis, Andrew works with automotive manufacturers and Tier 1 suppliers around the world to help bring new infotainment systems to market. His work has paved the way to our recent achievement of >50% market share in automotive infotainment. You can follow Andrew on Twitter here and read some of his latest thoughts on automotive trends here, here, and here.

The QNX Wireless Framework was developed by a team of mobile wireless experts with hundreds of person-years of experience building advanced, carrier-grade mobile products. The platform helps automotive OEMs enrich the driving experience by adding cellular and Wi-Fi technologies to enable over-the-air updates, deliver access to cloud-based services such as maps, navigation, and voice recognition, and address new regulatory requirements including eCall (Europe), Simrav (Brazil), and GLONASS (Russia). Read more about the QNX Wireless Framework here or check out our webinar.

You can find the complete list of categories and finalists on the TU-Automotive site. Congratulations to all the other finalists, and we’ll see you at the awards dinner!

Read More

QNX-powered Audi Virtual Cockpit in 2015 Audi TT named finalist in CTIA Hot for the Holidays Awards

Andrew Poliak

This just in! The QNX-powered Audi Virtual Cockpit in the 2015 Audi TT has been named a finalist in the connected car category in the 2014 CTIA Hot for the Holidays Awards. Just in time for the holiday buying season, the Hot for the Holidays Awards recognize the hottest mobile consumer electronics, including gadgets and accessories from entertainment and health to the connected car and home. The awards were judged by a panel of recognized industry experts, media and analysts.

The sleek 2015 Audi TT features a one-of-a-kind combined infotainment and fully digital instrument cluster — the Audi virtual cockpit —powered by the QNX OS platform. With the virtual cockpit, all content from current speed to the next turnoff, is located on one 12.3” display directly in front of the driver’s eyes elegantly blending infotainment and car gauges, in crisp, fast 3D. You can check out virtual cockpit in action below.

Winners will be announced on Wednesday, September 10, 2014 during CTIA’s Super Mobility Week in Las Vegas. The Audi Virtual Cockpit in the 2015 Audi TT is also up for the crowd favorite award where attendees and online users have the opportunity to select their favorite product, so please be sure to vote! Online voting ends Monday, September 8 at 5 p.m. PT.

Read More

The challenge of creating an (auto)mobile user experience

On March 12, I had the honor of joining a distinguished group of panelists at a luncheon for the Los Angeles Motor Press Guild. The panelists included:

• Michelle Avary — director of technology strategy, HARMAN International
• Henry Bzeih — head of Kia’s North American Infotainment Technology & Business Unit
• Jim Pisz — corporate manager of North American business strategy, Toyota Motor Sales, U.S.A.
• Wayne Ward — vice president of emerging solutions, Sprint Nextel
• Andrew Poliak (myself) — director of automotive business development, QNX Software Systems

The purpose of the panel was to share information on trends in the connected car space and in the automotive application ecosystem. The panel was well attended, with journalists from publications like the New York Times, and with representatives from companies like Alpine, Beats by Dr. Dre, Hyundai, and Toyota.

Two things stood out for me. First, the press really picked up on the need for solutions that can offer ease of use, upgradeability, and reliability while also reducing distraction and liability. Second, an expert witness hired by car companies to testify in Lemon Law suits told the panel that he was already being hired to provide testimony in cases involving in-vehicle electronics. He speculated that the technology described on the panel was going to “make him rich.”

His comments help illustrate a point. A car isn’t a mobile phone. OEMs and end-users may want the same kind of fresh and updateable experience that a phone can provide, but unlike a phone, an in-car infotainment system must be simple to use even while you’re driving down the highway. Such systems offer the ideal environment for a hard real-time OS that can also enable the latest consumer technologies and applications in a reliable and easy-to-use way.

Jim Pisz mentioned a sign he saw at the Geneva Motor Show. The sign said “Don’t Worry, Be Appy.” That sign makes me realize that the industry is at a crossroads. OEMs want access to consumer app developers and, in some cases, the apps themselves. At the same time they want a reliable solution that they won’t have to “worry” about. With QNX’s pedigree of reliability and amazing app ecosystem, we are uniquely positioned to help OEMs build “appy” cars, without the worry.

Read More

Open standards, open source, and why the difference matters

As Andy Gryc reported in a previous post, Paul Hansen of the Hansen Report asked six automakers whether they plan to ship products based on the GENIVI open source platform. Not one of them said yes.

This underwhelming response to open source may seem surprising, especially to people outside of the auto industry. It seems even more surprising when you consider the many companies that belong to the GENIVI Alliance — a veritable who’s who of high-tech and automotive companies, from ARM to IBM to Volvo. Why the disconnect?

A couple of reasons come to mind. First, the automotive market is exceedingly competitive. Asking automakers to collaborate on a common OS platform — the GENIVI approach — is arguably a non-starter. Also, many automakers seem to grasp that open source OSs don't necessarily address the issues that matter to them most.

Allow me to explain. Automotive companies entertain the option of using open source for several reasons. They want to avoid vendor lock-in. They want to leverage a large developer community. They want to access a rich toolset. And, in many cases, they hope to avoid the costs of runtime licensing.

Yes, open source can help address these requirements. But more often than not, open standards offer a better route to achieving what automakers really need.

Vendor neutral, OS neutral, hardware neutral
Take the goal of avoiding vendor lock-in. An open standard is, by definition, vendor neutral. It is typically the product of a collaborative and transparent process free of domination by a single company or interest group. Likewise, it isn’t controlled or maintained by a single, self-interested entity. HTML 5, for instance, isn’t owned by any one company, but is a standard embraced by Apple, Google, Microsoft, Mozilla, QNX, and others.

HTML5 isn't just vendor neutral; it's also OS and hardware neutral. By using it as an HMI and application environment, automakers gain the freedom to choose the best OS platform for the job at hand, and the option to migrate across platforms, if required. In other words, HTML5 enables automakers to use the platform that can offer fastest boot speed, the highest reliability, the best mobile device integration, or the best performance on automotive silicon — things that can reduce costs and improve the user experience. (To put this another way, the underlying OS platform is anything but a commodity — a fact demonstrated every day in the mobile device world.)

An open source platform may or may not share these characteristics. Even though developers can access the source code, a single entity may still control the technology’s roadmap and licensing terms. In effect, the platform can constitute a single point of failure for the automaker — exactly what automakers try to avoid. Compare this to an open standard, which is defined collaboratively and then supported over a long period of time. POSIX, with its 20+ year history, comes to mind.

Also, open standards like HTML5 are unencumbered by the protective licensing terms often associated with open source OSs — terms that can lead to greater system costs and complexity. For instance, the GNU Public License (GPL) that governs use of the Linux OS ensures that any modifications to the original program are released as open source. That's a problem for any OEM that doesn’t want to “open source” its technology; for instance, vehicle bus information. It is also incompatible with the certifications and licenses of consumer device manufacturers whose licensing terms are designed to prevent integration of their code with GPL code bases; iPod support and integration is a good example. Such technologies must, as a result, be separated into another virtualized OS or onto external hardware modules. The result is a more expensive and more complex system — another thing that automakers try to avoid.

Delivering the goods
Of course, all this hinges on whether a standard like HTML5 can deliver the goods. And from my perspective, it does. For instance, it can provide all the capabilities of a traditional HMI toolkit, including a rendering engine, content authoring and packaging tools, and sophisticated graphic transitions. But unlike proprietary solutions, it can also help automakers:

• tap into a vast pool of apps and developers
• integrate with mobile devices
• build user interfaces that incorporate virtually any delivery model
• customize the UX and simplify access to mobile apps
• customize apps and the UX for context: park, creep, drive, etc.

In addition, HTML5 can, with the right platform, work in concert with other HMI technologies (Adobe AIR, OpenGL ES, Qt, etc.) and blend seamlessly with those technologies on same display. As a result, system designers can choose the most appropriate technology for each application.

Incorporating open source
So is open source a total non-starter in automotive? Absolutely not.

In fact, many standards incorporate open source. Let us once again consider HTML 5. While it is built on an open standard, many HTML5 implementations are developed using open source solutions. For instance, many of the current, industry-leading HTML5 solutions are built on Webkit, an open source solution governed by the Lesser GNU Public License or LGPL.

The point is, the most successful solutions will combine the best that open standards, open source, and proprietary platforms have to offer. But if you were mandate an “open” solution, an open standard would be the best to rally behind.

---

If you're interested in this topic, we recommend you listen to the webinar that Andrew gave last week, "In-vehicle product differentiation: open standards vs open source." — Ed.

Read More

Pimp your ride with augmented reality — Part II

Last week, I introduced you to some cool examples of augmented reality, or AR, and stated that AR can help drivers deal with the burgeoning amount of information in the car.

Now that we’ve covered the basics, let’s look at some use-cases for both drivers and passengers. Remember, though, that these examples are just a taste — the possibilities for integrating AR into the car are virtually endless.


AR for the driver
When it comes to drivers, AR will focus on providing information while reducing distraction. Already, some vehicles use AR to overlay the vehicle trajectory onto a backup camera display, allowing the driver to gauge where the car is headed. Some luxury cars go one step further and overlay lane markings or hazards in the vehicle display.

Expect even more functionality in the future. In the case of a backup camera, the display might take advantage of 3D technology, allowing you to see, for example, that a skateboard is closer than the post you are backing towards. And then there is GM's prototype heads-up system, which, in dark or foggy conditions, can project lane edges onto the windshield or highlight people crossing the road up ahead:



AR can be extremely powerful while keeping distraction to a minimum. Take destination search, for example. You could issue the verbal command, “Take me to a Starbucks on my route. I want to see their cool AR cups”. The nav system could then overlay a subtle route guidance over the road with a small Starbucks logo that gets bigger as you approach your destination. The logo could then hover over the building when you arrive.

You'll no longer have to wonder if your destination is on the right or left, or if your nav system is correct when it says, “You have arrived at your destination.” The answer will be right in front of you.

AR for the passenger
So what about the passenger? Well, you could easily apply AR to side windows and allow passengers to learn more about the world around them, a la Wikitude. Take, for example, this recent video from Toyota, which represents one of the best examples of how AR could make long road trips less tedious and more enjoyable:


 

Read More

Pimp your ride with augmented reality — Part I

The use of electronics is exploding in automotive. Just last week, Intel proclaimed that the connected car “is the third-fastest growing technological device, following smartphones and tablets.”

Ten years ago, you’d be hard-pressed to find a 32-bit processor in your car. Now, some cars have 4 or more 32 bitters: one in the radio, another in the telematics module, yet another in the center display, and still another in the rear-seat system.

Heck, in newer cars, you’ll even find one in the digital instrument cluster — the QNX-powered cluster in the Range Rover, for example. Expect to see a similar demand for more compute power in engine control units, drive-by-wire systems, and heads-up displays.


The Range Rover cluster displays virtual speedometers and gauges, as well as warnings, suspension settings, and other info, all on a dynamically configurable display.

What do most of these systems have in common? The need to process tons of information, from both inside and outside of the vehicle, and to present key elements of that data in a safe, contextually relevant, and easy-to-digest fashion.

The next generation of these systems will be built on the following principles:

• Fully integrated cockpits — Vehicle manufacturers see system consolidation as a way to cut costs and reduce complexity, as well as to share information between vehicle systems. For instance, your heads-up display could discreetly let you know who is calling you, without forcing you to take your eyes off of the road. And it could do this even if the smarts integrating your phone and your car reside in another cockpit component — the telematics module, say.
   
• Augmented reality — With all of the data being generated from phones, cloud content services and, perhaps more importantly, the vehicle itself, presenting the right information at the right time in a safe way will become a major challenge. This is where augmented reality comes in.

Augmented reality is a cool use of cameras, GPS, and data to create smart applications that overlay a virtual world on top of the real world. Here are some of my favorite examples:

AR Starbucks cups — Use your phone to make your coffee cup come alive:



AR Starwars — Blast the rebel alliance squirrels!



AR postage stamp — Add a new dimension (literally) to an everyday object:



And here are a couple more for good measure:

AR ray gun — Blast aliens around the house!

Wikitude AR web browser — Explore the world around you while overlaying social networks, images, video, reviews, statistics, etc.

Stay tuned for my next post, where I will explore how AR could enhance the driving experience for both drivers and passengers — Andrew.
 

Read More

Marking over 5 years of putting HTML in production cars

Think back to when you realized the Internet was reaching beyond the desktop. Or better yet, when you realized it would touch every facet of your life. If you haven’t had that second revelation yet, perhaps you should read my post about the Twittering toilet.

For me, the realization occurred 11 years ago, when I signed up with QNX Software Systems. QNX was already connecting devices to the web, using technology that was light years ahead of anything else on the market. For instance, in the late 90s, QNX engineers created the “QNX 1.44M Floppy,” a self-booting promotional diskette that showcased how the QNX OS could deliver a complete web experience in a tiny footprint. It was an enormous hit, with more than 1 million downloads.

Embedding the web,
dot com style:
The QNX-powered Audrey

Also ahead of its time was the concept of a tablet computer that provided full web access. When I started at QNX, I was responsible for tablets, thin clients, and set-top boxes. The most successful of these pioneering devices was the 3COM Audrey kitchen tablet. It could send and receive email, browse the web, and sync to portable devices — incredibly sophisticated for the year 2000.

At the time, Don Fotsch, one of Audrey’s creators, coined the term “Internet Snacking” to describe the device’s browsing environment. The dot com crash in 2001 cut Audrey’s life short, but QNX maintained its focus on enabling a rich Internet experience in embedded devices, particularly those within the car.

The point of these stories is simple: Embedding the web is part of the QNX DNA. At one point, we even had multiple browser engines in production vehicles, including the Access Netfront engine, the QNX Voyager engine, and the OpenWave WAP Browser. In fact, we have had cars on the road with Web technologies since model year 2006.

With that pedigree in enabling HTML in automotive, we continue to push the envelope. We already enable unlimited web access with full browsers in BMW and other vehicles, but HTML in automotive is changing from a pure browsing experience to a full user experience encompassing applications and HMIs. With HTML5, this experience extends even to speech recognition, AV entertainment, rich animations, and full application environments — Angry Birds anyone?

People often now talk about “App Snacking,” but in the next phase of HTML 5 in the car, it will be "What’s for dinner?”!

 

Read More

Countdown to the Auto Summit Japan

I’m here at the QNX Auto Summit Japan 2011  in Nagoya, Japan and really energized about our event!  We’re being supported by some of our key partners including ARM, Redbend, Freescale, A&W, Elektrobit, Texas Instruments, Renesas and TCS.  

There’s presentations, amazing car demos based on QNX and serious networking planned!  Looking forward to meeting many of the Japanese Tier 1s and OEMs.  More to come once the event starts. 

Read More