11/22/2012

Meet the folks behind the QNX concept car (and other cool stuff)

An example of the concept
team's work
Imagine if you went to a Rolling Stones concert and the entire band played behind a curtain. That would be totally weird, right? Well, we realized that much the same scenario was playing out with the QNX concept team. Their work, including the QNX concept car, has appeared in A-list venues like CES and Mobile World Congress, yet the team itself has remained largely behind the curtain. And that’s too bad, since the team members embody the qualities I like best about QNX. Innovation, for example.

So, in the spirit of setting things right, we decided to pull back that curtain and make some introductions. And where better to start than with Mark Rigley, the team’s director.

If I were to describe Mark in one word, I’d choose chutzpah. Or gumption. Or moxie. He is the antithesis of wait-and-see. To spot him in a room, just look for the guy who says, “Let’s do it!” when everyone else is still stuck in “maybe,” “might work,” or “I need to get back to you on that.” And when you think about it, that attitude fits the bill perfectly. Because when your job is to take something like a Porsche 911 (an example of automotive perfection, if ever there was one) and make it even cooler, you’d better have a measure of confidence in yourself — and in your team.

Indeed, if anything shines out from this interview, it is the awe and respect that Mark holds for his team members. (Okay, I’ll admit it. Something else shines brightly: Mark’s enthusiasm for the next QNX technology concept car. Did I mention the team is working on one?)



This post originally appeared on the QNX auto blog.

11/14/2012

Taking a long, hard look at the ozone hole

For more than 20 years, a Harvard research team has been taking QNX technology to stratospheric heights

The NASA ER-2 high-altitude
aircraft
Hey, do you remember when everyone was in a knot over the ozone hole? You know, the one over Antarctica? The one the size of Antarctica? Based on all the press it has received lately (read: not much), it is yesterday's problem. I, for one, haven’t worried about it — or even thought about it — for a good 10 years.

But here’s the thing. The ozone hole didn’t go away. And it’s not going away soon. Yes, evidence suggests that the hole will heal, but the process promises to take decades — by 2050, if we’re lucky. (Strictly speaking, the hole heals every Austral Spring, but only temporarily; it always returns the next Austral Winter. And it isn’t exactly a hole, since the ozone doesn’t disappear completely from the upper stratosphere. It does disappear from the lower stratosphere, however.)

Did I mention only one hole? Sorry to mislead you. There are, in fact, substantial ozone losses over the Arctic as well, with the loss during the winter of 2011 achieving ozone hole status.

Ozone depletion is serious stuff. It may contribute to an enormous list of problems, from crop failures to eye cataracts to skin cancer. So it’s important to do the hard science and measure its progress, along with any factors that can affect it. Otherwise, how do you argue for a cogent policy on controlling substances and industrial practices to prevent ozone depletion? And do you know whether the policies and practices you put in place are doing any good?

Problem is, measuring and analyzing ozone depletion is a long-term project that takes patience and commitment. Fortunately, the Anderson Research Group from Harvard University seems to have those qualities in spades.

Making the upgrade
The group has been operating continuously since 1979. (For context, that was the year that Philips demonstrated the first Compact Disc. Remember those?) For the first few years, the group used a balloon to carry their instruments high into the atmosphere, but with the discovery of the Antarctic ozone hole in the mid-80s, they graduated to a NASA ER-2 high-altitude aircraft, which flies as high as 21 kilometers. (If the ER-2, depicted above, looks to you like a modded U-2, you’re right.)

The team’s first QNX-based instrument,
which measured OH in the lower
stratosphere, was deployed in an ER-2.
Lots of things have changed since 1979, but for the past two decades, one thing hasn’t: the group’s use of QNX technology. It all started in 1990, when the group decided to replace their homegrown OS kernel with the QNX RTOS v2. They then upgraded to the QNX RTOS v4 in 1992, which is also when they deployed their first QNX-based system, an instrument that measured OH (hydroxyl radical) in the lower stratosphere. More recently, they migrated to the latest generation of the QNX technology, the QNX Neutrino RTOS, aka v6.

Alphanumeric soup
To measure phenomena in the stratosphere, the team created a data acquisition architecture that takes advantage of core QNX strengths, including multitasking, message passing, realtime performance, and transparent distributed networking. Flexibility is a key characteristic of this architecture, since it must support a variety of instruments that measure an alphanumeric soup of airborne radicals and reactive intermediates. These include BrO, ClO, ClONO2, ClOOCl, NO2, OH, HO2, O3, CH4, N2O, CO, and CO2, as well as water vapor, water isotopes, and total water. (Why measure water? Because its presence in the stratosphere can contribute to ozone depletion. And because the increased frequency of heavy storms, such as Hurricane Sandy, may inject more water into the stratosphere.)

Here is the full configuration of the data acquisition architecture, which includes control and acquisition programs running on a flight computer as well as display and interactive commands running on a ground support computer:



According to Norton Allen, a software engineer for the Anderson group, “From the start, we needed an OS platform that would scale with our growing requirements, and that would satisfy our demands for high reliability — sending a plane into the lower stratosphere is a costly proposition, so there’s no room for software failures. At the same time, we needed a standards-based platform that would let us write portable applications. The QNX OS has been able to deliver on all counts."

“We needed an OS platform that would scale
with our growing requirements, and that would
satisfy our demands for high reliability.”

Global scale
I’ve barely touched on the many research activities of the Anderson Research Group. To quote their website, the group “addresses global scale issues at the intersection of climate and energy using a combination of experimental and theoretical approaches drawn from the disciplines of chemistry, physics and applied mathematics.”

So if you’ve got a minute, visit the site. Who knows, you may learn something — I did.

11/05/2012

My connected car word cloud is (still) getting around

Has it been 3 years already? I can't believe it. In any case, this story begins in 2009, when I generated a word cloud to promote the LTE Connected Car, a concept vehicle created by Alcatel-Lucent, QNX Software Systems, Atlantic Records, Toyota Motor Sales, and the ng Connect alliance.

Here's what the word cloud looked like:


Click to magnify.

I created the word cloud just for fun, but thought the result was pretty cool — and it seems I wasn't alone. Someone from BMW, for instance, used the word cloud in a conference presentation back in 2010.

Fast forward to last week, when I discovered that Google has a reverse image lookup function. (Yes, I know, I'm probably one of the last people on the planet to make this discovery.) And so, once again for fun, I decided to see if any images I've published have made their way onto other websites. I thought that the word cloud would be a good candidate, and I was right.

For instance, the word cloud has appeared on these sites (text blurred to respect copyright):

Computer World Brazil:


Social Media Council Europe:


inTELEMATICS today:


UIEvolution blog:


WinfWiki wiki:


There are a few other sites, but frankly, I don't understand what some of them are about. Still, it's cool to know I've created something that fills a need, however miniscule. Mind you, it would be even cooler if everyone who used the image acknowledged where they got it. Just saying.

And speaking of presidents...
This is a near-total non-sequitur, but in honor of the upcoming U.S. election, here are word clouds for every presidential inaugural address, starting with George Washington's address in 1789. (And no, the cloud doesn't contain the words "cherry," "tree," or "lie".)

10/26/2012

What has the QNX auto team been up to?

Well, let's see...

10/18/2012

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

No, not that kind of squeezing.
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 my colleague 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
    Who should attend: Automotive software engineers and managers

This post also appeared on the QNX Auto Blog.

10/17/2012

QNX at SAE Convergence: Cool screens and a mobile theme

Let's start with the theme. And no, I don't mean the kind of theme you download onto your smartphone. I'm referring instead to the main theme of a press release that QNX issued yesterday at SAE Convergence.

First, some context. If you're an automaker, you have little choice: you have to offer infotainment systems that can keep pace with the crazy fast advances in mobile devices. You also need to keep your systems fresh with apps, features, and content that consumers will expect long after they've bought your car. And to do that, you'll need to tap into the skills and products of the mobile app community. Otherwise, that ultra-cool infotainment system you ship today will rapidly transform itself into the 8-track of tomorrow. Goodbye, brand image.

The QNX CAR 2 application platform, with its solid grounding in HTML5, is designed to help infotainment-system designers conquer these (admittedly difficult) challenges. HTML5, after all, has become the lingua franca of the mobile apps market and offers an ideal bridge between the mobile and automotive worlds.

One thing was missing, though — a toolkit that would make it easy for mobile app developers to target the QNX CAR 2 platform. Yesterday, at SAE Convergence, QNX announced a new HTML5 SDK designed to do just that.

An SDK for (auto)mobile developers
The HTML5 SDK for the QNX CAR 2 platform is an extension of the open source BlackBerry WebWorks framework, specially optimized for automotive environments. It allows developers to write, test, and package feature-rich automotive apps based on HTML5, CSS3, JavaScript, and other open standards. It also provides the missing glue between high-level apps and the car, through specialized APIs that provide access to automotive devices and hardware.

Runtime emulator for quicker testing and debugging
This is where the first of the screens comes in. To speed development, the HTML5 SDK provides an emulator that lets developers quickly see how their apps would look and function in a car. Developers can use the emulator to perform JavaScript debugging, HTML DOM inspection, automated testing, and screen-resolution emulation, all from the convenience of a web browser. They can even make changes to their apps and view the results without having to recompile. The simulator is based on the open source BlackBerry Ripple emulator, used by thousands of mobile developers.

For instance, in this screen capture, the emulator is being used to test the virtual mechanic provided by the QNX CAR 2 platform:


Click to magnify

Here's another example, where the emulator is being used to test an audio control application. If you were running this emulator session, you could manipulate the app's onscreen controls to adjust volume, bass, treble, fade, and balance; you could also observe the changes to the underlying data values in the right-hand panel. And you could work the other way: by changing the controls on the right, you could observe changes to the app.


Click to magnify.

QNX also plans to create a virtual marketplace that will allow developers to make their QNX CAR 2 applications available to automakers. The marketplace will provide common ground for app developers and automakers to work together, and will allow automakers to preview the applications that best fit their brands and satisfy their customers. The marketplace is expected to go live when the HTML5 SDK is released.

By the way, my colleague Kerry Johnson provides an interesting back story to the SDK, including the kinds of APIs it provides. You can read his post here. You can also find more images of the emulator on the QNX Flickr page.

3D navigation from Elektrobit
Now for the other screens. Besides announcing the SDK, QNX has brought its QNX reference vehicle, a modded Jeep Wrangler, to the SAE show floor. As always, the Jeep is running the QNX CAR 2 platform. But this time, the Jeep also includes a cool 3D navigation app from automotive software vendor Elektrobit. Here are two examples of the Elektrobit app:





That's it for now. But before you go, be sure to follow @QNX_Auto on Twitter, where we are covering the latest developments, both QNX and non-QNX, from SAE Convergence.

10/04/2012

Now on YouTube: The incredible 1.44M QNX floppy demo!

You have got to watch this. But before you click Play, keep this in mind: The 1.44M QNX floppy demo dates from the late 1990s and its web browser was built for the 1999 Web, not the 2012 Web. So, as you'd expect, the browser in this demo displays some error messages when it's pointed at modern websites.

Other than that, prepared to be amazed. Everything you see here — OS, windowing system, web browser, TCP/IP stack, file manager, games, etc. — fit on a single, self-booting 1.44M floppy. No CD, no hard drive. And as you'll see, the demo could even download and launch new features (including a graphics driver), all on the fly. Cool, that.



Did you know? The ISO image for the 1.44M floppy demo was downloaded more than 1,000,000 times, making it the first truly successful marketing campaign for QNX Software Systems. The purpose of the demo was simple: to show developers how much performance and functionality QNX could squeeze into a resource-constrained device.

A big shout-out to ToastyTech for posting the video!

Want to see a pic of an even older QNX demo disk? Click here.