Our best CES yet

Anecdotes and observations from the QNX booth at 2013 CES

As a wrap-up to last week’s Consumer Electronics Show, I would love to regale you with all the cool technologies and nifty gadgets that I saw. But over the course of the entire four days, I rarely left the 20’x40’ patch of white carpet that was the QNX booth — with brief exceptions, of course, for bodily maintenance. The booth was just too busy for me to get away. If you checked out the QNX booth webcam, you know what I'm talking about.

Paul Leroux and Nancy Young have already posted a lot of information and photos about the show and the new QNX concept car, which is based on a Bentley Continental GT. So let me provide my personal view of CES through assorted anecdotes or observations collected at the booth.

• As you’d expect, the Bentley got a lot of attention. But our reference vehicle, based on a Jeep Wrangler, got more attention than I thought it would, even though this is the third time we’ve shown it in public. Many of the people interested in the Jeep just wanted to see what our QNX CAR application platform looked like “out of the box” without customization. And some were confessed Jeep or truck aficionados, without the “luxury brand lust” experienced by most.
   
• People in the auto industry knew who we were without introduction. Non-automotive people didn’t know who we were until I mentioned that “we are a wholly owned subsidiary of Research In Motion,” at which point most of them said “Oh, you’re that QNX.” Seems that your average person has heard quite a bit about QNX in the context of BlackBerry, but has no idea that the same company is doing things in automotive — or in anything else, for that matter. I usually then spoke about our 30+ year legacy in life- and mission-critical systems. When people learned that an OS used for mission-critical systems will also power their next potential phone, their reaction was “wow—that’s really cool.”
   
• Tanner Foust is a really nice young kid. (Actually, he’s not that much younger than me, but he sure looks young!) I didn’t know who he was when he was being filmed in the booth, surrounded by a throng of admirers. But since then, I’ve watched a lot of his YouTube videos and boy, can he drive! He's an accomplished race car driver, TV personality, and stuntman for lots of famous movies, but it’s nice to see he hasn’t let it go to his head.
   
• We wanted to make sure that our concept car respected the Bentley brand. To do that, we ran our design sketches by the folks at Bentley and they occasionally suggested some tweaks. It was all our own work, however, and the Bentley folks never saw it before it hit the show floor. When they came to the booth, they were very happy with what they saw — enough so that they said “it looked like we did it.” That, to me, was the ultimate compliment.
   
• Most frequent question: “Are you giving this away?” As it turns out, it’s something that people have said for every concept car we’ve done to date. Second most frequent question: “Can I drive it?” Unfortunately, but unsurprisingly, the answer to both is “No.”
   
• I was a little surprised by the enthusiastic response to the car's video conferencing. Of course, it works only while the car is parked, and you only get audio while the car is in Drive. But the part that seemed to impress people the most is the audio: two channel stereo and a full 20Hz to 22KHz means that the call sounds so much better than your typical hands-free call. You could see the reaction when the our director of acoustics Phil Hetherington started talking — you don’t know what you’ve been missing until you hear it.
   
• Bentley wanted us to add our video conferencing solution to the technology concept car. Because many Bentley vehicle owners aren’t necessarily the drivers, this feature makes a whole lot more sense for rear-seat systems than you might initially imagine.
   
• I was really impressed by two members of the media: Brian Cooley of CNET and Craig Peterson of Clear Channel. Both could receive a five minute technology core dump, quickly digest it, and talk intelligently about it on video or live radio (respectively) with no stumbles, questions, or missteps. I’ve had the pleasure of seeing both in action before, but their consummate professionalism is really quite amazing.
   
• I and every other QNX’er was delighted that we didn’t win the CNET Best of CES award! Instead, our customer, Chevrolet, won it for their MyLink system, and we couldn’t have been happier. Two out of the three nominees were QNX-based systems (the Garmin K2 was the other), so our odds were good. I’d rather that we never win another Best of CES award if it meant that one of our customers could always win instead.
   
• A number of people asked about the RIM booth and its absence. I explained that RIM was focusing on their launch at the end of January, and that since they wouldn’t have a new product to show the public, it didn’t make sense to be there. (It’s notable that Microsoft wasn’t there either, and Apple never is.) RIM was in Las Vegas in a hotel outside the convention center, giving media private previews of the upcoming phones that seemed to be extremely well received. And we had a few of our RIM compatriots helping us out at the QNX booth as well.
   

That’s all I’ve got to say about CES 2013 — our best show yet. See you next year!

Okay, time to get technical

Have glossy photos of the QNX concept car left you hungry for more? Dig into a technical whitepaper with our friends from Texas Instruments.

By now, many of you have seen photos and videos of the new QNX technology concept car, a specially modded Bentley Continental GT. Now, I'd like to say that the car was completed in record time by a small team of highly creative QNX engineers. And in many ways, that's absolutely true. But it's just as true that the work started more than 10 years ago, when QNX Software Systems started to build deep partnerships with leading players in the auto industry.

Because the truth is, you don't create this kind of magic overnight. And you don't do it on your lonesome. QNX has become successful in automotive for many reasons, but one of the most important is our ability to work closely, and productively, with A-list partners like Texas Instruments.

Inside the concept car

Take a look at the amazing displays in the Bentley, and the speed at which the screens redraw, and you get a taste just for how well QNX software and TI silicon work together under the covers.

Which brings me to a new white paper co-authored by Andy Gryc of QNX, and Matt Watson and Scott Linke of TI. It's titled "In-Vehicle Connectivity is So Retro," and among other things, it tells the story of how technologies from QNX and TI have co-evolved to help automotive developers build high-performance systems in less time and at less cost.

If your working vocabulary includes terms like OMAP 5, 1080p video decode/encode, floating-point DSP, MOST MLB, Ethernet AVB, PCIe, SATA, WiLink, Bluetooth, GPS, and NFC, this paper is for you.

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.

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.

Day one of CES — so far so great!

The QNX booth was like a mob scene. I think Phil Hetherington, senior director of the QNX acoustics group, hit the nail on the head when he said, "it's like a mosh pit in here." (He meant it in a good way. ;-)

I'm so proud and happy for the guys who spent their Christmas vacation working on the car. People are absolutely clamoring over each other to see it. I think there were more pictures taken of the Bentley than of the attractive talents in all other booths combined.

CES is a show like no other. Even as I write this I know I am missing something exciting on the show floor.

So with this in mind, I bid everyone adieu. I'll get some more shots today.



One of three demos in the Elektrobit booth (3220 North), showcasing the QNX CAR application platform.


Another example of what happens when you put two world-class suppliers together — Elektrobit and QNX, of course.


This demo replicates an impressive infotainment unit created for Audi using the QNX CAR application platform and EB street director.


EB street director and QNX CAR application platform — up close and personal.


Such an honor to be recognized again at this year's CES show!


Solowheel was a big hit! It's a gyro-stabilized electric unicycle that can be used as you would an electric bicycle. www.solowheel.com


Shooting our own video was really challenging as it was so hard to get 5 minutes in the Bentley. When we did, we still couldn't keep people away from the car!


Alexandre James, from the QNX concept design team, moved smoothly from software developer to company spokesperson.


Mark Rigley, concept design team lead, looked a lot more refreshed than he did last week when the car was still in a work in progress.


It seemed almost everyone wanted to capture the excitement of the new QNX technology concept car. Here's Andy Gryc, the perennial spokesperson, giving one of many demos throughout the day.


While the Bentley Continental was the bell of the CES ball, the Jeep Wrangler (2012 QNX reference vehicle) still did the job of capturing people's interest.


Sheridan Ethier, the hard-working manager of the QNX CAR engineering team, talked nonstop about the technology that he and his engineering group create.

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:

Delphi taps QNX CAR platform for next-generation infotainment

This just in: Delphi Automotive, a global supplier of automotive electronics with operations in 30 countries, has chosen the QNX CAR application platform 2.0 for use in next-generation infotainment systems.

This week, at 2013 CES, Delphi will demonstrate how it has leveraged the HTML5 framework in the QNX CAR platform to create a powerful graphics system for automotive use.

According to Jugal Vijayvargiya, senior vice president of Delphi and president of Delphi Electronics & Safety, “Our more than ten-year collaboration with QNX Software Systems has resulted in highly successful infotainment solutions that we’ve been able to bring to market quickly, thanks to the efficient, modular architecture of the QNX platform and its rich associated toolset. We’re very pleased to now extend our work on advanced in-vehicle technology with the latest version of the platform, which we were able to experience through QNX Software Systems' early access program.”

Read the full press release.

If you're 2013 CES this week, be sure to visit the Delphi booth in the North Hall, #730. You can also follow Delphi on Twitter: @DelphiAuto

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.

TI’s Jacinto 5 automotive processor selected for Audi's “MIB High” infotainment system

Well, it couldn't happen to a nicer technology partner. Yesterday, Texas Instruments announced that the QNX-based MIB High system, the next-generation infotainment platform for Audi vehicles, is the first automotive system to incorporate the TI Jacinto 5 automotive infotainment processor. According to the TI press release, the Jacinto 5 plays a key role in the system’s architecture, which consist of a multimedia applications unit and a highly integrated radio-and-car-control unit.

If you’re unfamiliar with the Jacinto 5, it’s an automotive-qualified multicore processor based on an ARM Cortex-A8 core. The processor integrates a variety of automotive peripherals and connectivity options.

QNX’s role in the MIB High was revealed in 2011, when e.solutions announced that QNX Software Systems had been chosen to supply the system’s OS and multimedia engine. See my blog post on that announcement, where I explain why the architecture of MIB High is so cool.

And if you’d like to check out the MIB High first hand, may I suggest you take one of these for a test drive.

What if…

Imagine if your car could help you become more connected to friends and family — and to the road ahead. Enter a new video that peers into the not-so-distant future.

It blows my mind, but some people still see connectivity in the car as the enemy. They think that, the more connected the car, the more distracting and dangerous it will be. But you know what? Responding to their concerns is easy. I simply ask them what if.

For instance, what if connectivity helped you drive with greater situational awareness? What if it helped you sidestep traffic jams and axle-busting pot holes? What if it helped you detect a stop sign hidden behind a tree? And what if it helped you become more connected to the people important to you, as well as to the road and the cars around you?

When we talk connectivity at QNX, that’s the kind of connectivity we envision. It isn’t just about Bluetooth or Wi-Fi or LTE — that’s only the plumbing. Rather, it’s about keeping you in tune and in sync with your car, your environment, your business, your friends. Your life.

Top 8 questions for squeezing high-end tech into low-end infotainment

A couple of weeks ago, I hosted a webinar that addressed the question, “Is it possible to build an infotainment system that meets today's customer demands with yesterday's price tag?” The webinar explored several ways to reduce RAM and ROM requirements, eliminate hardware, and share hardware, all with the goal of cutting BOM costs.

As always, the audience asked lots of great questions, several of which I have answered here. Of course, these provide only a hint of the ground covered in the webinar, so I invite you to download the archived version to get the full details.

Built-in phone module versus brought-in smart phone: what is your take on this, and is a hybrid approach feasible?
The approach will vary from automaker to automaker. I think that embedded phones will be required for certain cars, especially if they use systems that rely on cloud-based services. This approach adds to the BOM cost, of course, but it may reduce overall cost, depending on what features can be off-loaded to the cloud.

Some brands will encourage brought-in devices as the lowest-cost alternative. The consumer will then have to deal with the setup and maintenance issues required to pair or charge the phone. I don’t see a clear-cut analysis that says one method will be better than the other — it really depends on what you want to accomplish.

Any thoughts on using MirrorLink to clone a virtual display to a remote physical LCD?
If you’re talking about a remote (as in cloud-based) device, I would say that HTML5 is a much more natural choice for a server-based application. If it’s a brought-in device, then MirrorLink or HTML5 could be appropriate.

If GPS is moved to a brought-in phone, how will a stolen vehicle be located?
It won’t be, unless the phone was left in the vehicle. This is one of the trade-offs you make when trying to reduce cost.

Of the cost-saving techniques you discussed, which are most likely to be used?
Already, some system designers are removing wake-up micros and DSPs. I’m not aware of any systems where the LCD has been removed, but this approach would probably offer the largest cost savings, making it a likely choice for entry-level systems and cost-sensitive markets.

Security and reliability are the main concerns of a head unit. Squeezing high-end technologies into low-end systems won’t relax those expectations. For instance, smart phone integration will be an add-on instead of replacing functionality of the head unit. Thoughts?
The trade-offs will need to be communicated to the customer. You can never build a head-unit augmented with a smartphone that works as reliably as the head unit operating by itself. As an OEM or Tier 1, you just don’t have enough control over the brought-in devices.

As an industry, we need to educate consumers. If they start relying on the phone in the car to provide certain features, then they will have to expect an inevitable degradation in overall system quality. It comes back to that famous adage: “cost, quality, or time — pick two”.

MirrorLink has a defined communication interface to the head unit. You also mentioned HTML5 as an option. Is there a defined standard yet for transmitting the HTML5 up to the head unit?
The interface between web server (i.e. phone) and web client (i.e. head unit) is already well established and tested. For some specialized features (for instance, allowing HTML5 code to access vehicle services) some standardization may be required. This will hopefully be a topic of discussion in November, at the automotive HTML5 workshop hosted by the W3C in Rome. Some Connected Car Consortium members have also discussed the possibility that, in the future, MirrorLink could add a transport mechanism based on HTML5.

You discussed peripheral sharing, using QNX transparent distributed processing. Does QNX TDP require secure authentication between distributed boxes?
No, it does not. It relies on standard POSIX user group permissions to provide access rights to devices.

Can you discuss any trends you see regarding Ethernet or TCP/IP in the vehicle?
Ethernet is definitely becoming more interesting in the vehicle, due to the introduction of Ethernet AVB. It makes a very natural replacement for audio-video transmission over MOST, and the additions to AVB that fulfil strict timing requirements can replace CAN or MOST for non-media vehicle messages. Ethernet also has obvious advantages when you need to access Wi-Fi networks, cloud services, and mobile devices.

In-car infotainment and the art of doing more with less

Granted, the title for this blog post doesn't have the pizazz of, say, "Zen and the Art of Motorcycle Maintenance." (Are you old enough to even remember that book?) But it does capture the gist of a webinar that Andy Gryc will deliver next week.

His title for the webinar is "Squeezing high-end technologies into low-end infotainment systems." Admittedly, it's more direct than mine. Which is fitting, given that Andy has direct experience designing in-car systems. OnStar, for example.

But I digress. I'm sure you'd like to know what Andy plans to cover, so here's the overview:

Squeezing high-end technologies into low-end infotainment systems

Today's infotainment systems have it all – full multimedia, mobile device integration, POI-enabled navigation, speech recognition, high-resolution graphics, and cloud connectivity. The only problem is all of these features come with a big price tag.

Join Andy Gryc, automotive marketing manager, for this webinar, where he answers the question: Is it possible to build an infotainment system that meets today's customer demands with yesterday's price tag?

A 50-minute session (plus Q&A), this webinar covers a number of techniques to help slim down your next infotainment's BOM cost; it also suggests ways to target the luxury segment as well as the more cost-conscious, high-volume one with the same basic technology.

Date: Tuesday October 23, 2012

Time: 12:00 pm ET

Duration: 1 hour, including Q&A

Registration: Click here to register

Who should attend: Automotive software engineers and managers

HTML5 SDK for the QNX CAR 2 platform — the back story

Kerry Johnson

Today, at SAE Convergence, QNX Software Systems announced the new HTML5 SDK for the QNX CAR 2 application platform. I’d like to provide some insight into this announcement, describe what you can expect to find in the SDK, and explain how it builds on the HTML5 capabilities already available in the QNX CAR 2 application platform.

Enabling apps for the car
Almost every consumer who owns a smart phone or tablet is familiar with the app experience: you go to an online marketplace, find apps of interest, and download them onto your device. With the HTML5 SDK, the automotive team at QNX is creating an analogous experience for the car.

Just as Apple, Android, and RIM provide SDKs to help vendors develop apps for their mobile platforms, QNX has created an SDK to help vendors to build apps for the QNX CAR 2 application platform. The closest analogies you will find to our HTML5 SDK are Apache Cordova and PhoneGap, both of which provide tools for creating mobile apps based on HTML5, CSS, JavaScript, and other web technologies.

App developers want to see the largest possible market for their apps. To that end, QNX also announced today that it will participate in the W3C’s Web and Automotive Workshop. The workshop aims to achieve industry alignment on how HTML5 is used in the car and to find common interfaces to reduce platform fragmentation from one automaker to the next. Obviously, app developers would like to see a common auto platform, while automakers want to maintain their differentiation. Thus, we believe the common ground achieved through W3C standardization will be important.

It bears mentioning that, unlike phone and tablet apps, car apps must offer a user experience that takes driver safety into consideration. This is a key issue, but beyond the scope of this post, so I won’t dwell on it here.

So what’s in the SDK, anyway?
As in any SDK, app developers will find tools to build and debug applications, and APIs that provide access the underlying platform. Specifically, the SDK will include:

• APIs to access vehicle resources, such as climate control, radio, navigation, and media playback
• APIs to manage the application life cycle: start, stop, show, hide, etc.
• APIs to discover and launch other applications
• A packaging tool to combine application code (HTML, CSS, JavaScript) and UI resources (icons, images, etc.) with QNX CAR APIs to create an installable application – a .bar file
• A emulator for the QNX CAR 2 platform to test HTML5 applications
• Oh yeah, and documentation and examples

The development and deployment flow looks something like this:




Emulator and debugging environment
The QNX automotive team has extended the Ripple emulator environment to work with the QNX CAR 2 application platform. Ripple is an emulation environment originally designed for BlackBerry smart phones that RIM has open sourced on github.

Using this extended emulator, application developers can test their applications with the correct screen resolution and layout, and watch how their application interacts with the QNX CAR 2 platform APIs. For example, consider an application that controls audio in a car: balance, fade, bass, treble, volume, and so on. The screenshot below shows the QNX CAR 2 screen for controlling these settings in the Ripple emulator.


Using the Ripple emulator to test an audio application. Click to magnify.

In this example, you can use the onscreen controls to adjust volume, bass, treble, fade, and balance; you can also observe the changes to the underlying data values in the right-hand panel. And you can work the other way: by changing the controls on the right, you can observe changes to the on-screen display. The Ripple interface supports many other QNX CAR 2 features; for examples, see the QNX Flickr page.

You can also use the emulator in conjunction with the Web Inspector debugger to do full source-code debugging of your Javascript code.

Creating native services
Anyone who has developed software for the QNX Neutrino OS knows that we offer the QNX Momentics Tool Suite for creating and testing C and C++ applications. With the QNX CAR 2 application platform, this is still the case. Native-level services are built with the QNX Momentics suite, and HTML5 applications are built with our new HTML5 SDK. We've decided to offer the suite and the SDK as separate packages so that app developers who need to work only in the HTML5 domain needn't worry about the QNX Momentics Tool Suite and vice versa. Together, these toolkits allow you to create HTML5 user interface components with underlying native services, where required.

QNX, NVIDIA team up to deliver infotainment solutions

Today, at SAE Convergence, QNX announced that it is working with graphics leader NVIDIA to bring infotainment solutions to the automotive market. As part of this initiative, the companies will integrate support for the NVIDIA Tegra processor into the QNX CAR 2 application platform.

The Tegra system-on-chip is the size of thumbnail, yet it incorporates a quad-core ARM CPU and a GeForce GPU, as well as dedicated audio, video, and image processors.

The NVIDIA Tegra visual
computing module

“QNX Software Systems and NVIDIA have a proven track record of delivering on production programs for Audi... and we’re excited to add support for Tegra to the latest generation of our automotive platform,” said Linda Campbell, QNX director of strategic alliances.

Speaking of Audi, NVIDIA is bringing an Audi A6 to SAE Convergence, equipped with an infotainment system powered by technology from QNX and NVIDIA. The system bristles with high-end features, including 3D navigation with Google Maps and Google Earth, as well as natural voice recognition.

For more information on this announcement, read the press release, and for more information on QNX activities at SAE Convergence, visit our Convergence overview page.