A Porsche you could talk to

Paul Leroux

I have a confession to make. The day before QNX Software Systems unveiled this technology concept at car at 2012 CES, I leaked the news on the On Q blog. Mind you, the leak was unintentional. I had been editing a post that described the car and, instead of hitting Save, I hit Publish by mistake. Dumb, I know.

I immediately took down the post and informed my colleagues of the error. Fortunately, my RSS feed didn't give me away, and the launch, which had been strictly under wraps, went ahead as planned. But boy, did I feel stupid.

Now that I've got that off my chest, let's see what the hubbub was about. The car, based on a Porsche 911 Carrera, came equipped with an array of features built by the QNX concept team, including one-touch smartphone pairing, high-definition hands-free calls, rear-seat entertainment, and a digital instrument cluster.

So, you ready for a tour?

The car
Let's start with the exterior. Because man, what an exterior:



The instrument cluster
Once you got behind the wheel, the first thing you saw was the instrument cluster. But
this was no ordinary cluster. It could dynamically reconfigure itself — in response to voice commands, no less. It could even communicate with the navigation system to display turn-by-turn directions. And it was designed to honor the look-and-feel of the stock 911 cluster:



The head unit
To your right, you could see the head unit. Here is the unit's main screen, from which you could access all of the system's key functions:



And here's another screen, showing the system's media player:



The front-seat control of backseat infotainment
The Porsche also showcased how a head unit could offer front-seat control of backseat entertainment — perfect for when you need to control what your kids are watching or listening to:



The voice recognition
The Porsche was outfitted with cloud-based voice recognition, which let you enter navigation destinations naturally, without having to use artificial grammars. Check out this Engadget clip, taken at an AT&T event in New York City:



The car also included features that neither words nor pictures can capture adequately. But let me try, anyway:

One-touch Bluetooth pairing — Allowed you to pair a phone to the car simply by touching the phone to an NFC reader embedded in the center console; no complicated menus to wade through.

Text-to-speech integration — Could read aloud incoming emails, text messages, and BBM messages.

High-definition voice technology — Used 48KHz full stereo bandwidth for clear, high-fidelity hands-free calls.

The car also ran a variety of apps, including TCS hybrid navigation, Vlingo voice-to-text, Poynt virtual assistant, Weather Network, and streaming Internet radio from Pandora, Nobex, Slacker, and TuneIn.

The point
The point of this car wasn't simply to be cool, but to demonstrate what's possible in next-gen infotainment systems. More specifically, it was designed to showcase the capabilities of the QNX CAR Platform for Infotainment. In fact, it did such a good job on that count that the platform took home the 2012 CES Best of Show award, in the car tech category:

Read More

More QNX-powered cars and infotainment systems from 2011 CES

The second installment in our CES Cars of Fame series. Today, we look at several systems from the 2011 CES event, starting with this week's inductee, a BMW Z4.

Paul Leroux

I've led you astray — sort of. Last week I stated that the LTE Connected Car, the first QNX-powered technology concept car, appeared at 2011 CES. But I didn't mention that QNX technology was at the core of several other innovative vehicles and infotainment systems at CES that year.

So let me set the record straight. And the best place to start is the QNX booth at 2011 CES, where a BMW Z4 roadster was the front-and-center attraction.

BMW Z4 Roadster with ConnectedDrive
The Z4 wasn't a technology concept car, but a true production car straight off the dealer lot. It was equipped with the QNX-based BMW ConnectedDrive system, which offers real-time traffic information, automatic emergency calling, and a text-to-speech feature that can read aloud emails, appointments, text messages, and other information from Bluetooth smartphones. It's a cool system right at home in this equally cool cockpit:



Heck, the whole car was cool, from the wheels up:



Audi A8 with Google Earth
Mind you, the coolness didn't stop at the QNX booth. Just down the hall, Audi showcased an A8 sedan equipped with the QNX-based 3G MMI infotainment system, featuring Google Earth. This same model drove home with the 2011 Edmunds Breakthrough Technology award a short while later.

I don't have any photos of the Audi from the CES show floor, but if you head over to the On Q blog, you can see some snaps from an automotive event that QNX hosted in Stuttgart two months earlier. The photos highlight the A8's innovative touchpad, which lets you input destination names by tracing them with your finger.

Toyota Entune infotainment system
And now to another award-winning QNX-based system. Toyota Entune embraces a simple, yet hard-to-achieve concept: help drivers interact with mobile content and applications in a non-distracting, handsfree fashion. For instance, if you are searching for a nearby restaurant, Entune lets you ask for it in a conversational fashion; no need for specific voice commands.

You could tell the judges for the CNET Best of CES awards were impressed, because they awarded Entune first prize, in the Car Tech category — the first of three QNX-powered systems to do. QNX Software Systems went on to win in 2011 for its QNX CAR Platform and then Chevy won in 2012 for its MyLink system. Not too shabby.

A cluster of clusters
We've looked at just three of the many QNX-based automotive systems showcased at 2011 CES. For instance, QNX also demonstrated digital instrument clusters built by Visteon for the Land Rover Range Rover and for the Jaguar XJ sedan, below:



Freescale, NVIDIA, TeleNav, and Texas Instruments also got into the act, demonstrating QNX systems in their booths and meeting areas.

Do you have any memories of 2011 CES? I'd love to hear them.

Read More

Controlled openness

Paul Leroux

The title of this post sounds like a contradiction in terms. But you know what? It captures the predicament faced by every automaker today.

On the one hand, automakers need to convince mobile developers that it's worthwhile to create apps for the car. They also need to make the process of creating and monetizing car apps as easy and open as possible. Otherwise, why would a developer spend time developing a car app when a phone app could reach many more customers? (About 60 million cars shipped in 2012, compared to more than 545 million smartphones — and most of those cars can't host apps.)

On the other hand, apps can't run willy-nilly in the car. For safety's sake, automakers must impose control on when specific apps can be used, and the apps themselves must be designed or modified to minimize distraction, possibly in accordance with government-mandated rules and guidelines. That may sound like an imposition on developers, but not really. After all, developers want to create apps that will prove popular with consumers, and consumers will be far more interested in apps that can be used while the car is moving — apps that, for safety reasons, can be used only when the car is stopped will hold less appeal.

But enough from me. Recently, my colleague Andy Gryc caught up with Thilo Koslowski, VP Distinguished Analyst at Gartner, and they discussed the notion of controlled openness for the car — along with how HTML5 fits into the picture. The cameras were rolling, so grab some popcorn, dim the lights, and check it out:

Read More

Telematics Detroit 2013: The recap

Justin Moon

The Telematics Detroit conference always provides a great opportunity to take the pulse of the automotive connectivity market and understand what key players in the industry are doing — and are planning to do in the next couple of years.

Prior to the show, I had the opportunity to participate in an executive roundtable session hosted by Ernst and Young. The focus was the future of mobile integration and how it will change the market as we know it. The roundtable brought together views from the entire ecosystem, including OEMs, tier one suppliers, software and service providers, dealerships, and, ultimately, the end consumer. It was a great session with a lot of interaction.

Telematics Detroit, Day 1

The Bentley attracted lots of traffic

Okay, let’s go through the event checklist:

• QNX technology concept car based on a Bentley Continental and outfitted with our latest instrument cluster and infotainment concepts. Check.
   
• QNX reference vehicle based on a Jeep Wrangler, rocking a new Qt-based HMI on the QNX CAR Platform for Infotainment. Check.
   
• How about a functional over-the-air software update demo from our colleagues at Blackberry to blow people away? OK, got that, too.
   
• And let’s not forget a demo showcasing the latest in fast boot technology and Android app integration for the QNX CAR Platform. Check, and ready to go.

Inside the Jeep: a new Qt-based HMI

Now we’re set for the show. Day 1 opened with a keynote address on “Winning the Telematics Race”, presented by Thilo Koslowski of Gartner; it set the stage what for turned out to be a great show. Our booth was busy pretty much the entire day — but look at the list above… of course, it was busy! :-)

In addition to great booth traffic, I had the opportunity to participate on a panel on autonomous vehicles and the challenges they present — the discussion was very engaging and it did in fact “drive” traffic to our booth for further discussion. Meanwhile, my colleague Andrew Poliak presented a keynote on HMI trends. To my mind, his talk clearly demonstrated that we are thought leaders in this industry.

The evening brought the annual Telematics and Tonics mixer, co-hosted by QNX and several of its partners: AT&T, NVIDIA, Pandora, Tweddle, and Elektrobit. It was a huge success with well over 300 attendees — standing room only, all night. There were great discussions with great people until the wee hours of the night… really wee hours.

Telematics Detroit, Day 2
Day 2 was busy, busy, busy. Did I mention it was busy? We provided demos galore to OEMs, tier ones, partners — the works. Andy Gryc sat on a panel discussing the ultimate intuitive user interface and knocked it out of the park, as he always does.

The booth was busy until the show closed. We then we put the cars to bed in their shipping truck and headed off to the airport, tired but extremely happy nonetheless.

Read More

Jivin' up the Jeep with a fresh new version of the QNX CAR Platform

by Paul Leroux

Reskinnable, reconfigurable,
and refreshed

If you haven’t already heard, we've announced version 2.1 of the QNX CAR Platform for Infotainment. In fact, we’re demonstrating it this week at the Telematics Detroit conference.

So what’s new in 2.1? Well, let’s start with what hasn’t changed. The platform is still based on the same, reliable QNX architecture proven in tens of millions of vehicles. (Fact: In 2012, QNX technology shipped in 11 million cars. If you put those cars end to end, they’d circle the earth — and you’d still have about 6000 miles of cars left over. That's a lot of cars.) The platform also retains its inherent flexibility, allowing infotainment system designers to use multiple app environments, connect to multiple mobile platforms, and create a wide range of systems.

Um... let me correct that statement. The new version is, in fact, more flexible. From the beginning, the QNX CAR Platform has supported both HTML5 and OpenGL ES, the two most popular open standards for mobile development. And now, with version 2.1, it also supports Android apps, as well as apps and human machine interfaces (HMIs) built with the popular Qt 5 application framework.

The QNX reference vehicle — a modded Jeep Wrangler — is the perfect, well, vehicle for showcasing these new capabilities. Take, for example, the new digital instrument cluster, which is implemented in OpenGL ES:



I enjoyed the look of the reference vehicle’s original cluster, and still do. But you know what I like about the new version? It shows how a digital cluster can deliver state-of-the-art features, yet still honor the look-and-feel of an established brand like Jeep. These features include dynamic reconfigurability and the power to display turn-by-turn directions, weather updates, and other information provided by the head unit.

Speaking of which, here is the head unit’s main screen, which serves as a one-stop information center for turn-by-turn directions, weather, music, and recent messages:



Now let’s slide over to the passenger seat for a different perspective. If you look below, you’ll see the head unit’s app tray, which shows how the QNX CAR Platform can blend a variety of apps and HMI technologies on the same display — in this case, native and Android apps running on an HMI built with the Qt 5 application framework. In case you’re wondering, the Android app icons in this image are AutoTrader and TapTu. (That's right, they can be accessed just like other apps.)



If you’ve seen images of the QNX technology concept car (you know, the Bentley!), you’re already familiar with the gorgeous 3D navigation system created by our partner Elektrobit. Well, the reference vehicle also comes with a version of Elektrobit’s nav system, seen here:



And last, here’s an image of my personal favorite, the virtual mechanic. In this case, it's displaying trip information, including duration, mileage, and average speed:



There's a lot to see in version 2.1 of the QNX CAR Platform for Infotainment, but there's also a lot you can't see — such as improved power management, optimizations for faster boot time, and support for more hardware platforms, including Freescale i.MX 6Dual and i.MX 6Quad, NVIDIA Tegra 3, Texas Instruments OMAP 5, and Texas Instruments Jacinto 5 Eco.

What's more, I haven't shown you any of the new, pre-integrated partner apps that have been added to the platform, including HearPlanet, Parkopedia, Soundtracker, and wcities eventseekr. But no worries, I plan to reveal more in coming posts.

In the meantime, I invite you to check out the press release we issued this morning.

Read More

Specs for Cars?

Tina Jeffrey

As Google Glass, the latest in experimental computer wearables, starts to make its way into the hands of select users, a multitude of use cases is popping up. For instance, a WIRED article recently explored the notion of your car being a ‘killer app’ for Google Glass. Now, you may not want to think of your car as a killer app, but let’s contemplate this use case for a moment.

Drivers wearing Glass could pair their new specs to their phone and instantly have a personal heads-up display (HUD) that overlays virtual road signs and GPS information over the scene in front of them. For instance:


Source: Google

Glass also understands voice commands and could dictate an email, display turn by turn directions, or set up and display point-of-interest destination data based on a simple voice command such as “Find the nearest Starbucks”.

This is all very cool — but does it bring anything new to the driving experience that isn’t already available? Not really. Car makers have already deployed voice-enabled systems to interface with navigation and location-based services; these services either run locally or are accessed through a brought-in mobile device and displayed on the head unit in a safe manner. ADAS algorithms, meanwhile, perform real-time traffic sign detection and recognition to display speed limits on the vehicle’s HUD. All this technology exists today and works quite well.

Catch me if you can
Another aspect to consider is the regulatory uncertainty created by drivers wearing these types of devices. Police can spot a driver with their head down texting on a cellphone or watching a movie on a DVD player. But detecting a driver performing these same activities while wearing a head-mounted display — not so easy. There’s no way of knowing whether the activities a driver is engaged in are driving related or an outright distraction. Unlike an HUD specified by the automaker, which is designed to coordinate and synchronize displayed data based on vehicle conditions and an assessment of cognitive load, a head-mounted display like Glass could give a driver free reign to engage in any activity at any time. This flies in the face of driver distraction guidelines being promulgated by government agencies.

Don’t get me wrong. Glass is cool technology, and I see viable applications for it. For instance, as an alternative to helmet cams when filming a first-person perspective of a ski run down a mountain, or in taking augmented reality gaming to the next level. (You can see many other applications on the Glass site.) But Glass is a personal display that operates as an extension of your cellphone, not as a replacement for a car’s HUD. Cars need well-integrated, useable systems that can safely enhance the driving experience. Because of this, I don’t believe that devices like Glass, as they are currently conceived, will garner a spot in our cars.

Read More

Report from Barcelona: first meeting of the W3C automotive business group

Last week, I had the privilege of attending the first face-to-face meeting of the W3C automotive business group and the honor of being nominated group co-chair. (The other co-chair is Adam Abramski, an open source project manager for Intel.) With more than 70 members, the group has already become the eight-largest group in the W3C, even though it is barely two months old. Clearly, it’s generating a lot of interest.

The meeting included three presentations and two contributions. I presented on the lessons we’ve learned with the QNX CAR platform, how we think the market is changing, and how these changes should drive HTML5 standardization efforts.

I presented my three “musts” for standardizing HTML5 in the car:

1. Must create something designed to run apps, not HMIs (unless HMIs come along for free)
2. Must focus on mobile developers as the target development audience
3. Must support integration of HTML5 environments with native environments like EB Guide and Qt

I described some of the changes that have resulted from the alignment of the QNX CAR platform with the Apache Cordova framework, and why they are crucial to our HTML5 work. Unfortunately, we didn't have our W3C contribution ready due to these changes, but members generally agreed that having a standard consistent with mobile development was an appropriate course change.

Tizen and GenIVI gave presentations about their vehicle APIs. Tizen has contributed its APIs, but GenIVI hasn't yet — still waiting on final approvals. Webinos contributed its APIs before the meeting, but didn’t deliver a presentation on its contribution; members had reviewed the Webinos work before the meeting.

The meeting was a great chance to sit down with people I don’t normally meet. Overall, the group is moving in the right direction, creating a standard that can help automakers bring the goodness of HTML5 into the car.

Read More

Traveling on reserve power

Or how a new kind of electro-mobility can be fun. A guest post from Thomas Fleischmann of Elektrobit Automotive.

Thomas Fleishmann

Imagine you are always driving on reserve power. You find this difficult? Get used to it — and welcome to the new era of electro-mobility! Vehicles like the Chevy Volt, with its secondary combustion engine, are already addressing this challenge — but having to support two types of driving technology can be challenging and costly.

So how can electro-mobility, which is supported by software, be implemented meaningfully? And how do we get drivers to accept it? Certainly not by abandoning the driver with nothing but a nicely animated display of the car’s battery condition.

Let's assume you live in a big city. You don’t even own a car. Instead, you subscribe to a certain number of hours of travel time with your favorite car brand. In addition to your S or XL subscription for four weeks a year, you get access to a fossil-fuel engine for your vacation in another state or country twice a year.

In the morning you find and reserve a car with your BlackBerry phone and get into it at a nearby charge-point. The HMI adapts to your profile settings automatically — your friends, contacts, addresses, and music are already there. The navigation system is your energy consultant; it tells you, based on traffic conditions and topography, how far you can drive with this car and, at the appropriate time, suggests an available electric socket within easy reach. Or the system warns you to turn back soon if you want to arrive home safely. After parking the car successfully, your smartphone guides you for the last few kilometers by bus or subway to your destination — it knows the way and easily adopts the data of your navigation system.

Using software solutions like EB GUIDE or EB street director and frameworks like the QNX CAR application platform you can concentrate on creating the end-user experience and transform the journey on reserve power into something fun and convenient — suddenly an electric vehicle becomes a smart mobility concept.

Check this out; I fried it last week. The yellow center represents the area in which you can drive and go back home. The white area represents the range you can drive, depending on traffic or topography:

---

Thomas Fleischmann is Senior Product Manager at Elektrobit Automotive responsible for the HMI solution EB GUIDE. Contact him at Thomas.Fleischmann@elektrobit.com.

Read More

Pandora interview: Using HTML5 to deliver content to the car

At CES this year, our own Andy Gryc had a chance to sit down with Tom Conrad, CTO at Pandora, a long-time QNX CAR platform partner. Pandora is already in 85 vehicle models today and continues to grow their footprint, not only in automotive but in consumer as well.

Take a couple minutes to hear Tom's perspective on standardizing on HTML5 across markets and to get a glimpse of the future of Internet radio in automotive. And make sure you watch the whole thing — there's some fun outtakes at the end.

Read More

Creating HTML5 apps for the car

Adding a downloadable app capability to the car isn't just a matter of bolting consumer-grade technology onto an automotive hardware platform, dusting your hands, and calling it a day.

Apps should be integrated into the vehicle experience, which means they need access to vehicle resources. But you must carefully control that access: the apps should be isolated in their own environment to protect the rest of the car software. Most of all, the apps need to conform to safe driving practices, which typically entails a re-write of the user interface.

Still, we should leverage as much as possible from the mobile world. That’s where the real innovation happens; the mobile community provides a much bigger pool of fresh ideas than automakers could ever build by themselves. And the best tools and libraries are focused on mobile development.

That’s why QNX Software Systems is building the best of both: an application tool that draws heavily from mobile, but is adapted to the car. It's provisionally named the HTML5 SDK for the QNX CAR application platform and, while it isn't yet available to the public, beta versions are now available for QNX CAR platform customers.

For a preview of what we’ll be rolling out, check out this video:

Read More

First look: HTML5 SDK for the QNX CAR platform

Whenever I hear the word “ripple,” I think of ice cream: butterscotch ripple, chocolate ripple, lemon ripple, and (yum) strawberry ripple. Well, the video I'm about to show you isn’t about ice cream, but it is about something that’s just as cool and just as sweet: the Ripple mobile environment emulator.

Ripple already supports multiple platforms, such as BlackBerry 10 and Apache Cordova, allowing developers to preview how their apps will look and function on a variety of mobile devices. And now, thanks to extensions provided by the QNX CAR development team, it will also emulate how an app looks and performs in a vehicle infotainment system.

Simply put, the same tool that helps app developers target mobile platforms will also help them target the car.

QNX Software Systems will offer this modded version of Ripple as part of the HTML5 SDK for the QNX CAR platform. The goal of the SDK is simple: to help mobile developers and automakers work together on creating apps for in-vehicle infotainment systems.

If you’re a developer, you’ll be able to use the Ripple emulator and its associated Web Inspector to perform JavaScript debugging, HTML DOM inspection, automated testing, and screen-resolution emulation, all from the convenience of a web browser. You’ll also be able to modify your apps and view the results without having to recompile — simply edit your source code and hit refresh in the browser. You’ll even be able to perform remote debugging on the evaluation board or final hardware used by the automaker, again from the same browser environment.

Enough from me. Let’s get the complete scoop from my colleague Andy Gryc:

Read More

Designing interfaces from the outside in

User interfaces are a pet peeve of mine.

I’m one of those people whose VCR always blinked 12:00. Not because I couldn’t figure it out but because I resented that I had to.

Basically, I have neither the time nor the inclination to read manuals. If I’m paying good money for a consumer-facing product then it better not require an engineering degree to use it.

Not surprisingly, then, I think UI design is every bit as important as product; maybe even more so. Because if your user experience sucks, make no mistake; I will be walking and talking to your competitors.

It wasn’t until I entered the glamorous world of software development that I came to the following conclusion: Interfaces are complicated because development tools require an engineer (or similarly brilliant individual) to use them.

Of course this is a sweeping statement and I’ll gladly debate it but the point is this: Someone with unique skills and knowledge about user-centric design should be creating interfaces. Not someone who knows the product from the inside out.

I know in a traditional model this can create a lot of churn but companies like Crank Software have come up with a way to decouple the roles of embedded engineer and UI designer, allowing them to work in parallel while focusing on their individual core competencies.

I spoke to several members of the QNX concept development team when they were heavily embroiled in creating the latest technology concept car. It was obvious when talking to the engineers and the UI designers that Crank’s Storyboard made both jobs that much easier and the process a whole lot quicker. The end result, achieved in a very short time frame, speaks for itself.

This is great news for people like me who curse like sailors whenever using a remote, microwave, GPS, treadmill, camera, and so on. Indeed, I'm counting on teams like QNX and Crank to ensure the digital car is an enjoyable and intuitive  experience. If not, I do know who I'm gonna call.

Read More

Meet the QNX concept team: True Nguyen, UX designer

We continue our spotlight on the QNX concept development team with True Nguyen, the team's user experience designer.

We interviewed True just prior to CES 2013, and she was hoping that people's impressions of the latest QNX technology concept car would be as fantastic as hers. True's love of cars stems back to her childhood, and that really comes out in the interview.

If you haven't had a chance to meet the other team members, you can read their stories here.

Next up, we'll interview Alexandre James to get his impressions of the Bentley and the buzz from CES 2013.

Read More

Day two of CES - QNX, Harman, and Vipers, oh my!

Day two came and went very fast. It felt as frantic as day one. I did manage to leave the north hall though... only to find the center hall to be just as intense. Maybe even more so. It had booths the size of city blocks. Maybe even bigger; certainly louder.

I somehow found Harman International. And I was not disappointed. There were at least four demos sporting QNX technology.

QNX CAR 2 was on display and in full form in the Harman booth. Nice to see the QNX logo so prominently displayed.


Closer look at different display in the same demo system. This 3D map from Elektrobit just never gets old.


Harman again. QNX again. This is almost embarrassing! ;-)


Harman and QNX and Vipers, oh my!


I managed to get permission to poke my head into the car. The digital instrument cluster was gorgeous.


The Viper's infotainment system was just as beautiful. Note to my boyfriend: I do believe this car is currently shipping.


The QNX booth staff, including biz dev manager Emil Dautovic, were hard at work once again. Although how hard can it be to talk to nice people all day? Maybe if there were more chairs...


Of course we knew our latest concept car would be a hit but we weren't exactly expecting the mob scene that it was again on day two.


Joe Cusumano, automotive field applications engineer, in conversation.


Linda Campbell, director of QNX strategic alliances, was her usual tireless self.


Our inimitable automotive field applications engineer Dan Baergen.


And our very own Dr. Phil, mastermind of the QNX acoustics processing and noise cancellation products.

Read More

QNX-powered Chevy Mylink drives home with 2013 Best of CES award

Congratulations to the infotainment team at Chevrolet! Their next-generation Chevy MyLink system has just won a Best of CES award, in the car tech category. The competition judges were particularly impressed with MyLink's user interface and integration with the car's instrument cluster.

The MyLink system was one of two QNX-powered finalists in this year's competition; the other was Garmin's K2 infotainment platform.

Chevy plans to roll out the new version of MyLink later this year.

Read More

Now on YouTube! First video of QNX technology concept car

Yesterday, some friends from Texas Instruments dropped by our CES booth for a demo of the new QNX concept car. The cameras were rolling, and here's what they caught.

Mark Rigley, head of the QNX concept team, did a fantastic job of guiding TI's Michael Guillory through the car's many features, including the gorgeous HD display powered by TI DLP technology and by a TI OMAP 5 processor. Check it out:



My favorite part? The exceedingly cool video conferencing. What's yours?

Read More

Works for me: The making of the QNX technology concept car

If I were asked to create a recruitment video for QNX Software Systems, this is the video I'd want to shoot. Because this is the QNX that I know and feel proud to represent.

A place where people work hard. A place where people work together. A place where people work on technology that is changing how we drive and communicate. A place where I'd rather work than anywhere else.

Enough said. Roll the tape:

Read More

It's a Bentley! A guided tour of the new QNX technology concept car

"Bend it, shape it, any way you want it"
— Headline from a QNX advertisement, circa 1987

I’m about to show you some pictures of a car. Not just any car, but a powerful, luxurious, and stunningly beautiful car. A car that has undergone a technological transformation.

If you’re like me, you'll be fascinated by the car’s features, some of which have never been seen in a vehicle — until now. But if you can, remember that it isn’t just about the cool features. It’s also about the platform that enabled them.

I’m speaking, of course, of the QNX CAR application platform.

We created the new QNX technology concept car — a modified Bentley Continental GT — to demonstrate that flexibility and customization form the very DNA of the QNX CAR platform. If you’ve seen the QNX reference vehicle, you already know that the platform provides an extremely rich environment for in-car infotainment, complete with HMI frameworks, smartphone integration, an HTML5 engine, a mobile device gateway, and a host of pre-integrated partner technologies — everything to kickstart our customers' projects. But in the automotive world, differentiation is everything. So it’s just as important that the platform enables customers to add their own branding, features, and sizzle. And to do it quickly.

Ease of branding and
personalization is just one

of the capabilities of the
QNX CAR platform.

Which is where the new concept car comes in. To create it, we used the same base QNX CAR platform that we offer our customers. But when you compare the Bentley to the Jeep, which uses a stock version of QNX CAR, the differences are dramatic: different features, different branding, and a different look-and-feel. In effect, the Jeep shows what QNX CAR can do out of the box, while the Bentley shows what QNX CAR lets you do once you start bending it to your imagination. One platform, many possibilities.

Which brings me to the slogan at the top of this post. It's amazing to think that a core value of QNX technology in the 1980s — giving customers the flexibility to achieve what they want to do — remains just as true today. Some values, it seems, are worth keeping.

And now, the car…
I know that you’re anxious to peek inside the car and see what we’ve done. But before we go any further, take a moment to savor the car’s beautifully sculpted exterior. This is one classy set of wheels. In fact, if you ask me, the wheels alone are worth the price of admission:



The awesome (and full HD) center stack
Okay, time to hop in — but get ready to prop up your jaw. Because the first thing you’ll notice is the jaw-droppingly beautiful 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. (In the photo below, the clock display appears within the knob.)

The center stack supports a host of applications, including a 3D navigation system from Elektrobit that makes full use of the display. Just check out this bird’s-eye view of the Las Vegas Strip:



So how big is the display? Big enough to provide access to other functions, such as the car’s media player or virtual mechanic, and still have plenty room for navigation. Check it out:



The awesome (and very polite) voice rec system
Time to talk to the car. 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, no less. You can now tell the media player what you’d like to hear and the navigation system where you’d like to go.

To provide natural language speech recognition, the system uses the cloud-based AT&T Watson speech engine, as well as an “intent framework” from QNX. It also uses keyword spotting technology from Sensory so you can start the system simply by talking to it.

The awesome (and nicely integrated) smartphone support
The Bentley also showcases how the QNX CAR platform enables automakers to offer 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 (and just plain fun) web app
I know, I know: the car looks cool, but you’re not at CES this week to see it first-hand. But how about the next best thing? Just connect to the web app and keep tabs on the Bentley in real time. (Note: The car will go online later this morning.) The app lets you view a variety of data that the car publishes to the cloud, such as what song the infotainment system is playing and whether someone has just opened a door. It also displays information that would be extremely helpful if this were your personal car, such as fluid levels and tire pressure. (This is a preliminary screen for the app, so I'm not sure if the tire pressures are realistic.)



UPDATE: The web app is now live, and the desktop version features a live camera feed of the Bentley and Jeep. Check it out!



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. But 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 (cool, that). Put the car in Reverse, and the cluster will display a video feed from the car’s backup camera.



There are other options as well. For instance, the cluster can display information from the media player or display the current weather:



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

• Advanced multimedia system — Offers direct support for Pandora radio and the first embedded in-car implementation of the Shazam music discovery service.
   
• Video conferencing with realistic telepresence — Separate cameras for the driver and passenger provide independent video streams, while high-definition voice technology from QNX offers expanded bandwidth for greater realism, as well as stereo telepresence for making the remote caller sound as if they’re sitting right next to you.
   
• LTE connectivity — The car features an LTE radio modem, as well as a Wi-Fi hotspot for devices you bring into the car.

Super size those images
Want to see the center stack and instrument cluster in all their high-resolution glory? Just check out our QNX Flickr account.

That's all for now, but stay tuned: We’ll have plenty more news for you today and all through this week.

Read More