AUTOMOBILE HTML5 and the software engineer

HTML5 appears to have a number of benefits for consumers and car manufacturers. But what is often good for the goose is not necessarily good for the developer. Talking to the guys in the trenches is critical to understanding the true viability of HTML5.

Andy Gryc and Sheridan Ethier, manager of the automotive development team at QNX, pair up for a technical discussion on HTML5. They explore whether this new technology can support rich user interfaces, how HTML5 apps can be blended with apps written in OpenGL, and if interprocess communication can be implemented between native and web-based applications.

So without further ado, here’s the latest in the educational series of HTML5 videos from QNX.



This interview of Sheridan Ethier is the third in a series from QNX on HTML5.

AUTOMOBILE QNX-powered OnStar FMV drives home with CES Innovation award

Paul Leroux

This just in: The OnStar FMV aftermarket mirror, which brings the safety and security features of OnStar to non-GM vehicles, has won a coveted CES Innovations Design and Engineering Award.

To clinch this award, a product must impress an independent panel of industrial designers, engineers, and trade journalists. Speaking of impressions, it seems that OnStar FMV also made a hit with the folks at CNET, because they've chosen it as one of their Top Holiday Shopping Picks for 2015.

As you may have guessed, OnStar FMV uses QNX Neutrino as its OS platform. It also uses the QNX acoustic processing suite, which filters out noise and echo to make hands-free conversations clear and easy to follow. The suite includes cool features like bandwidth extension, which extends the narrow-band hands-free signal frequency range to deliver speech that is warm and natural, as well as intelligible.

Have time for a video? If so, here's a fun look at FMV's features, including stolen vehicle recovery, automatic crash response, turn-by-turn navigation, hands-free calling, and one-touch emergency calling:

HTML5 Hackathon

Learn how to put together HTML5 apps at the HTML5 Hackathon. You'll get hands-on experience with WebWorks, which is the BlackBerry tool for building applications with HTML5.

That'll get you primed for building HTML5 apps for the QNX CAR 2 application platform!

Auto trivia, BlackBerry PlayBook tablet, and #QNXLive sessions

As we begin to look forward to a brand new year, we still have a couple of fun activities for you to keep a look out for as the holidays begin to wind down.

Friday, December 28 will be the last chance for you to win a BlackBerry PlayBook tablet in our automotive trivia sweepstakes. We’ll be tweeting out this year’s final trivia question on Friday at 1 p.m. ET, and if you respond back to @QNX_Auto with the correct answer, you will be entered into December’s drawing. More information can be found here: http://ow.ly/gl9sb.

Additionally, we still have two more #QNXLive Twitter sessions coming up on January 3 and January 11. On Thursday, January 3 at 1 p.m. ET, Linda Campbell, director of QNX strategic alliances, will answer your questions on the subject “Whose technology is in my car? A look at the partner technologies and capabilities found in the cars of today and tomorrow.” And then on Friday, January 11 at 1 p.m. ET live from CES 2015, Mark Rigley, director of concept development, will answer your questions on the new technology concept car that we’ll be unveiling at CES 2015.

We thank everyone who has participated in our #QNXLive sessions to date with Andy Gryc and Andrew Poliak. We had some great questions come in from @StephenBB81, @jmznvs, @BBABrian and @MitchCurtis20, and are looking forward to your additional questions. Remember, you can submit your questions now or day-of by sending a tweet to @QNX_Auto and using the hashtag #QNXLive. If your question is selected, we’ll be sure to give you a shout-out in addition to answering your question. More here: http://ow.ly/glaLk.

Here’s to a fantastic rest of the holidays and a very prosperous 2015!

Living the Networked Life in New York City

Derek Kuhn

Last week, we demonstrated our latest concept car, built on a Porsche 911 Carrera S, at AT&T’s Living the Networked Life Event in New York City. The car has been on the road since we unveiled it at CES — it even went to Spain for MWC. We ran out of time to ship it to New York, so Mark Rigley, manager of the concept development group at QNX, and I drove it from Ottawa to SoHo. It was my first time driving the Porsche anywhere outside of a ball room, and it turned out to be a great drive.

Mark is super protective of the car, as he’s entitled to be, and he and the team have done a great job putting it together. But wouldn’t you know it? He let me drive and, as I’m pulling off Interstate 81 in Cortland NY, we get rear-ended. No — for real. I pull over, Mark jumps out, and I’m checking the side mirror to open the door safely in traffic but I’m mortified. Turns out that the Porsche’s rear valance is strong like a bull, and we emerge with just a series of scuff marks.

We drove through Binghamton, Scranton, and Poconos to get to the city. Traffic got faster and denser as we entered New Jersey, but Mark, to my surprise, let me drive again! We arrived at the hotel and handed the car off to a professional detailer before it was parked on site.

After setting up the car, we were ready. Soon we were joined by press, analysts, and AT&T partners and executives who all came out to see an important part of the car’s story — the use of AT&T’s WATSON speech engine. The Porsche is a great way to illustrate how helpful WATSON can be in an environment like the car.


Derek (seated in the car) with Mazin Gilbert of AT&T and Jordan Crook of TechCrunch.

The event was a big success and featured a presentation from Krish Prabhu, president and CEO of AT&T Labs Research; it also included demonstrations from AT&T Labs and AT&T Foundry. The demos included a smart door that recognizes you before you reach for your keys, and a smartphone application that performs language translations in real time.

The car will be on the road in coming weeks, including a stop at the CTIA Wireless show in New Orleans, from May 8 to 10. If you're there, be sure to check us out in the Solutions Showcase.
 

QNX, AutoNavi collaborate to provide in-car navigation for automakers in China

Map database offers 20 million points of interest

Paul Leroux

This just in: QNX has announced that it is partnering with AutoNavi, a leading provider of digital map content and navigation solutions in China, to integrate AutoNavi’s technology into the QNX CAR platform.

AutoNavi offers a digital map database that covers approximately 3.6 million kilometers of roadway and over 20 million points of interest across China. By supporting this database, the QNX CAR platform will enable automotive companies to create navigation systems optimized for the Chinese market and users.

Said Yongqi Yang, executive vice president of automotive business, AutoNavi, “as a leading global provider of vehicle infotainment software platforms, QNX is not only a technology leader, but also a design concept innovator in enhancing vehicle flexibility — infotainment designs based on the QNX CAR Platform can be quickly customized.”

For more information on this partnership, read the press release. And to learn more about AutoNavi, visit their website.

AUTOMOBILE 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.

AUTOMOBILE QNX rolls out new wireless framework

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

Paul Leroux

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

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

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

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

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

To learn more about the QNX Wireless framework:

• read the press release

• read the product overview and product brief

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

Making the growing number of connected cars continuously better

Guest post by Yoram Berholtz, Director of Market Adoption, Red Bend Software

More and more car manufacturers are implementing over-the-air software updates as a way to improve functionality, fix software defects, and guarantee a user experience that is continuously better. Car manufacturers GM (OnStar) and Daimler (MBRACE 2) have been leaders in recognizing the value of over-the-air updates for improving their infotainment systems. For example, GM recently updated the Bluetooth technology in OnStar to support late model smartphones.

The ability to update the infotainment system even manually is an improvement over requiring car owners to visit the dealership every time a new software update is available. As an example, Ford recently launched a program for consumers to update their own MyFord Touch system by mailing Ford owners a USB drive loaded with the appropriate software updates. However, many consumers view manual updates as bothersome and complicated, which means some systems simply don’t get updated. Today’s car owners expect their infotainment systems to have the same user experience as their mobile devices, and that means performing software updates over-the-air.

Scope and scale
According to ABI Research, there will be 210 million connected cars by 2016, and together with the ability to tether the smartphone to the infotainment system, the main enabler for doing over-the-air update is there: connectivity.

The updating solution must have scope and scale. Scope is the ability and the flexibility to update all of the memory including the user and system space with full or discrete components. As well, the solution must scale to manage millions of updates without failure and with the highest security possible. This, for example, would enable users of the QNX CAR application platform to update not only the QNX CAR software but also individual applications such as Pandora or the Weather channel.

In the mobile industry, where over-the-air software updating is a well-established practice, manufacturers and service providers realize many benefits:
 

• Cost reduction — Over-the-air software updates have reduced warranty costs
   
• Update success rate — Over-the-air software updates deliver the highest success rate
   
• Faster updates — Sending only the code that is different between the original software and the update (often called the delta) is faster and uses less bandwidth
   
• Customer satisfaction — A fast and automatic over-the-air process eliminates the need for the consumer to go to the dealer

A holistic solution
The mobile industry has enjoyed these benefits for some time. The automotive industry needs over-the-air updating even more so because the infotainment system includes millions of lines of code and updating this software requires a holistic solution that can manage the whole software life-cycle.

Red Bend Software has integrated its vRapid Mobile® update technology, which exists in more than 1.6 billion devices, into the QNX CAR platform. This enables car manufacturers and Tier 1 providers the flexibility to create an over-the-air update strategy that is optimized for infotainment systems and also for other embedded systems in the car. Today, infotainment systems are central in the car cockpit experience. These systems contain not only the QNX CAR 2 platform but also a variety of applications. Applications for the auto industry are not like applications for mobile devices. Applications for the auto industry have been modified in order to meet the car environment and have more voice activation and larger buttons so the driver isn’t distracted.

Car manufacturers are looking at their infotainment systems as product differentiators and as a valuable asset to generate revenues after the sale. The automobile industry doesn’t want Over-the-Top companies controlling the delivery channel to the infotainment system and weakening automotive brands. With a holistic Firmware Over-the-Air (FOTA) solution, car manufacturers can guarantee ownership of the infotainment firmware and applications, increasing the consumers’ perceived value through a much stronger brand.

Not if, but when
No longer is the auto industry asking whether or not to perform over-the-air updates. Now car manufacturers and tier one suppliers are asking how often and when should updates be provided during the life-cycle of the infotainment system.

---

Yoram Berholtz is the Director of Market Adoption at Red Bend Software, the market leader in Mobile Software Management. Mr. Berholtz is responsible for working with mobile operators and device manufacturers to help them increase and improve their usage of over-the-air software updating. In addition, he has responsibility for developing partnerships and go-to-market strategies in the Automotive and Connected Device markets, and oversees the Red Bend Certified™ Interoperability program. Mr. Berholtz has experience in engineering, product management and partner management with an emphasis on mobile communications technologies, having worked at Motorola, Pelephone, ECI Telecom, Schema, Intel and Marvell.

Enabling the next generation of cool

Capturing QNX presence in automotive can’t be done IMHO without a nod to our experience in other markets. Take, for example, the extreme reliability required for the International Space Station and the Space Shuttle. This is the selfsame reliability that automakers rely on when building digital instrument clusters that cannot fail. Same goes for the impressive graphics on the BlackBerry Playbook. As a result, Tier1s and OEMs can now bring consumer-level functionality into the vehicle.

Multicore is another example. The automotive market is just starting to take note while QNX has been enabling multi-processing for more than 25 years.

So I figure that keeping our hand in other industries means we actually have more to offer than other vendors who specialize.

I tried to capture this in a short video. It had to be done overnight so it’s a bit of a throw-away but (of course) I'd like to think it works. :-)

AUTOMOBILE Reducing driver distraction with ICTs

Inappropriate use of information and communication technologies (ICTs), especially mobile phones, is a chief culprit behind driver distraction and road accidents, and with automobile manufacturers scrambling to develop a “connected” driving experience, the ICT and automotive industries are becoming ever more closely entwined.

However, this integration of cars and ICTs need not come at the expense of driver safety, and there are strong grounds on which to argue that ICTs have great potential to enhance rather than diminish vehicle safety systems.

Under the banner of intelligent transport systems (ITS) the automotive and ICT communities are working towards a convergence of automobiles and ICTs that prioritizes drivers’ safety and broad consensus has it that international standards are the tools through which this will be achieved.

Over the past two years, as chairman of the ITU-T Focus Group on Driver Distraction, I have had the pleasure of leading a group tasked with laying the foundations for driver-distraction standardization work in ITU’s Telecommunication Standardization Sector (ITU-T).

Established in February 2015, the Focus Group reached the end of its study period in March 2015 and has been instrumental in raising awareness around ITU-T activity on driver distraction and the scale of this workload, as well as in providing clear direction to ITU-T’s driver-distraction work plan. The group has also been successful in opening lines of communication with key organizations and drawing new expertise into the ITU-T standardization process.

The Focus Group’s final deliverables take the form of five technical reports that describe:

• use cases and user interface requirements for automotive applications 
• system capabilities for improving the safety of driver interaction with applications and services (situational awareness management) 
• approaches that enable external applications to communicate with a vehicle

The reports are freely available here.

The conclusions put forward by the reports are being taken up by the two groups leading ITU-T’s standardization work on driver distraction, Study Group 12 (Performance, QoS and QoE) and Study Group 16 (Multimedia). New related work items calling for external coordination and collaboration may also be addressed by the Collaboration on ITS Communication Standards, a forum working to create an internationally harmonized set of ITS communication standards to enable the deployment of fully interoperable ITS products and services in the global marketplace.

Safe interaction with applications and services
The Focus Group’s work is just the beginning of an international standards effort to help drivers interact safely with applications and services — and not just apps on phones, but apps running in the cloud, in roadside infrastructure systems, and in the car itself, to name just a few locations.

The Focus Group’s Use Cases report details the use cases and user scenarios being targeted by this standards effort, but for now let’s look at Use Case 2, Scenario A (arbitration of external message), which illustrates how ITU-T is working towards a comprehensive framework for managing distraction and workload.

Keeping priorities straight
In this user scenario, a navigation maneuver is given priority over a social media ‘status update’ message. The blue call-out boxes indicate where the ITU-T Recommendations under development can enable safe interaction between the driver and applications. For instance, ITU-T Recommendation G.SAM will define mechanisms for prioritizing navigation, G.V2A will define the communications interface between the app and the driver-vehicle interface (DVI), and P.UIA will recommend characteristics of the auditory social media message.

Remember that the focus here is not on how to implement social media in the car, but rather on how best to manage workload and distraction.



Giving a navigation maneuver priority over a social media status update message

In for the long haul
Speaking from our perspective at QNX Software Systems, a subsidiary of BlackBerry, the work of the Focus Group marks the beginning of a long road ahead. Within ITU-T, QNX will continue to:

1. Work with the relevant parties to identify solutions to the problem of technology-related driver distraction and workload. These parties include automotive, telecommunications, and consumer electronics organizations; standards development groups; academia; and government agencies.
2. Determine which aspects of the solution should be standardized, and help drive this standardization.
3. Align QNX product roadmaps as solutions develop.

Certainly this is a long-term strategy that will take years to realize, factoring in the rigour of ITU-T’s standards process as well as the significant amount of time needed to deploy technologies in vehicles on a meaningful scale.

Join the discussion
A workshop hosted by ITU and UNECE at ITU headquarters in Geneva, 27 June 2015, will address “Intelligent transport systems in emerging markets – drivers for safe and sustainable growth” with a view to analyzing recent advances in ITS with emphasis on improving road safety in developing countries.

This workshop includes a session dedicated to driver distraction in which I will present the outcomes outlined by the Focus Group’s technical reports to spur discussion on the likely course of corresponding ITU-T standardization work.

The workshop is free of charge and open to all interested parties, including non-members of ITU, and online ‘remote participation’ will be available to all those unable to travel to Geneva. Please join us for what will certainly be a richly informative and interactive event!

This post originally appeared on the ITU Blog.

Meet the QNX concept team: Alex James, software engineer

We continue our spotlight on the QNX concept development team with Alex James, who gives us his impressions of the Bentley and the buzz at 2015 CES.

Besides attending CES, Alex worked on the latest QNX technology concept car from conception to launch — an amazing experience for any software engineer.

Working with bleeding-edge technologies sometimes brings unexpected challenges, along with interesting opportunities, as Alex discovered.

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

Leading infotainment supplier in China makes the shift to QNX CAR platform

Paul Leroux

This just in: Foryou General Electronics, a global supplier of in-car infotainment systems, has chosen the QNX CAR platform to develop infotainment and navigation systems for automakers in China.

Said Steven Chen, CTO of Foryou General Electronics, ”we appreciate the modular, pre-integrated approach that the QNX CAR platform offers because it allows us to develop highly reliable, differentiated infotainment solutions for entry-level to high-end vehicles.”

A Foryou infotainment and navigation
system. Source: Foryou

Foryou chose the QNX CAR platform after comprehensive testing of competing infotainment platforms, including open source solutions.

Established in September 2002, Foryou General Electronics is a subsidiary of Foryou Group Ltd., one of the top 100 electronic information enterprises of China. Its products are sold in more than 80 countries and regions worldwide; company sales were more than US$300 million in 2015.

For more information on this announcement, read the press release.

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.

Jivin’ up the Jeep — then and now

Do Jeeps have a unique power to bring out the inner hacker in their owners? Based on the sheer number of Jeep kits on the market, I'd say yes.

Maybe it has something to do with the rough-and-ready, take-on-all-comers personality of the Jeep brand. Or maybe it has to do with the inherent flexibility of the Jeep design. Or maybe it's simply because the brand attracts self-reliant do-it-yourselfers. Whatever the explanation, the history of Jeep modding is almost as old as the Jeep itself.

Jivin' then...
For instance, here are some examples of "jivin' up the Jeep" from a 1947 issue of Mechanix Illustrated magazine. (I found these on blog.modernmechanix.com — you have got to check this site out.)






And jivin' now...
With a history like this, is it any wonder the QNX concept team also chose to mod a Jeep, albeit with 21st-century tech? For instance, they added their own digital instrument cluster:



and some apps:



not to mention a virtual mechanic:



And is it any wonder they had so much fun doing this?



Hey, do you plan on attending SAE Convergence in October? If so, come by the QNX booth (815) for an even closer look at how the QNX concept team jived up this Wrangler with the connectivity and personalization features of the QNX CAR application platform.

Highlights (er, mods) of the Wrangler include:

• Customizable HMI for reskinning and personalization
  
• Ability to download apps
  
• Multimedia: streaming radio, mobile connectivity, album art, etc
  
• One-touch Bluetooth pairing with NFC
  
• HD hands-free communication with conversational voice recognition
  
• Reconfigurable digital instrument cluster
  
• Tablet-based rear-seat entertainment
  
• HTML5 framework for leveraging mobile ecosystem
  

 

AUTOMOBILE More QNX-powered cars and infotainment systems from 2015 CES

The second installment in our CES Cars of Fame series. Today, we look at several systems from the 2015 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 2015 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 2015 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 2015 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 2015 for its QNX CAR Platform and then Chevy won in 2015 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 2015 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 2015 CES? I'd love to hear them.

New to 26262? Have I got a primer for you

Driver error is the #1 problem on our roads — and has been since 1869. In August of that year, a scientist named Mary Ward became the first person to die in an automobile accident, after being thrown from a steam-powered car. Driver error was a factor in Mary’s death and, 145 years later, it remains a problem, contributing to roughly 90% of motor vehicle crashes.

Can ADAS systems mitigate driver error and reduce traffic deaths? The evidence suggests that, yes, they help prevent accidents. That said, ADAS systems can themselves cause harm, if they malfunction. Imagine, for example, an adaptive cruise control system that underestimates the distance of a car up ahead. Which raises the question: how can you trust the safety claims for an ADAS system? And how do you establish that the evidence for those claims is sufficient?

Enter ISO 26262. This standard, introduced in 2015, provides a comprehensive framework for validating the functional safety claims of ADAS systems, digital instrument clusters, and other electrical or electronic systems in production passenger vehicles.

ISO 26262 isn’t for the faint of heart. It’s a rigorous, 10-part standard that recommends tools, techniques, and methodologies for the entire development cycle, from specification to decommissioning. In fact, to develop a deep understanding of 26262 you must first become versed in another standard, IEC 61508, which forms the basis of 26262.

ISO 26262 starts from the premise that no system is 100% safe. Consequently, the system designer must perform a hazard and risk analysis to identify the safety requirements and residual risks of the system being developed. The outcome of that analysis determines the Automotive Safety Integrity Level (ASIL) of the system, as defined by 26262. ASILs range from A to D, where A represents the lowest degree of hazard and D, the highest. The higher the ASIL, the greater the degree of rigor that must be applied to assure the system avoids residual risk.

Having determined the risks (and the ASIL) , the system designer selects an appropriate architecture. The designer must also validate that architecture, using tools and techniques that 26262 either recommends or highly recommends. If the designer believes that a recommended tool or technique isn’t appropriate to the project, he or she must provide a solid rationale for the decision, and must justify why the technique actually used is as good or better than that recommended by 26262.

The designer must also prepare a safety case. True to its name, this document presents the case that the system is sufficiently safe for its intended application and environment. It comprises three main components: 1) a clear statement of what is claimed about the system, 2) the argument that the claim has been met, and 3) the evidence that supports the argument. The safety case should convince not only the 26262 auditor, but also the entire development team, the company’s executives, and, of course, the customer. Of course, no system is safe unless it is deployed and used correctly, so the system designer must also produce a safety manual that sets the constraints within which the product must be deployed.

Achieving 26262 compliance is a major undertaking. That said, any conscientious team working on a safety-critical project would probably apply most of the recommended techniques. The standard was created to ensure that safety isn’t treated as an afterthought during final testing, but as a matter of due diligence in every stage of development.

If you’re a system designer or implementer, where do you start? I would suggest “A Developer’s View of ISO 26262”, an article recently authored by my colleague Chris Hobbs and published in EE Times Automotive Europe. The article provides an introduction to the standard, based on experience of certifying software to ISO 26262, and covers key topics such as ASILs, recommended verification tools and techniques, the safety case, and confidence from use.

I also have two whitepapers that may prove useful: Architectures for ISO 26262 systems with multiple ASIL requirements, written by my colleague Yi Zheng, and Protecting software components from interference in an ISO 26262 system, written by Chris Hobbs and Yi Zheng.

AUTOMOBILE QNX-powered Audi MMI framework to support Android Auto

This just in: Audi has announced that its Audi MMI mobile media application framework, which is built on the QNX CAR Platform for Infotainment, will support the new Android Auto connectivity solution.

The new feature will allow drivers to access Android-device car apps using Audi MMI displays and controls, which Audi has optimized for safe and intuitive operation on the road.

Audi states that the MMI system will still maintain its compatibility with other smartphones. Moreover, drivers will be able to switch between the Android view and Audi infotainment functions, as desired.

Audi is a long-standing customer of QNX Software Systems. Audi systems based on QNX technology include the recent Audi Virtual Cockpit and Audi Connect with Google Earth.

Audi plans to introduce Android Auto support in all-new models launched in 2015. For the complete story on Audi support for Android Auto, read the Audi press release.

AUTOMOBILE QNX concept car makes detour at TI headquarters

Guest post by Kroy Zeviar, QNX strategic alliances

My colleague Mark Rigley must feel (justifiably) proud these days. He is, after all, head of the team that created the new QNX concept car, which took home a Best of Show award from 2015 CES.

You'd think that Mark and I would be anxious to get home after a hectic, albeit gratifying week at CES. And indeed, we were. But we made a slight detour and stopped over in Dallas to show off the car to our friends at Texas Instruments.

Everyone loved it. The car, based on a Porsche 911, takes advantage of TI's OMAP4 and wireless connectivity solutions, so folks were naturally excited to see what their technology had helped enable.

Better yet, TI brought in a pro photographer to take these cool pix...



Upwards of 400 folks came out to see the car


Checking out the new head unit and digital cluster


Mark, in the passenger seat, giving one of many demos


Best of CES 2015 winner. Woo-hoo!


This shot is just cool.


And speaking of cool, a huge shoutout to the TI OMAP and
wireless solutions teams for all their great support!

AUTOMOBILE Everything you wanted to know about HTML5 in the car, Part III

Welcome to the third installment in my Q&A series on HTML5 in the car. In Part II, we looked at web servers, native plug-ins, instrument clusters, and display updates. This week, we turn our attention to tools, touch gestures, UI performance, and vehicle resources.
Are there any HTML5 HMI builder tools available?
Most of the well-known IDEs, including Eclipse, Dreamweaver, and Netbeans, support some flavor of HTML5 in their latest release. Adobe Edge, a new tool now available in preview, also lets you create animated HTML5 content. I suggest you check out the HTML5 Tools site, which publishes up-to-date tool reviews.

Often, automotive customers will ask system designers to make an infotainment system work "like an iPhone,” with the popular gesture controls. Does HTML5 support "inertial" menus and two-finger zoom?
Multi-touch is handled at the app level; here’s an example. Pinch zooming at the browser level is browser-dependent — the QNX browser handles it, but not every browser does. As for physics-based scrolling, HTML5 doesn’t support it “out of the box”; it needs to be added. Frameworks like Sencha Touch provide these types of controls.

Will the performance of HTML and JavaScript be adequate for critical user interface components or computations, such as safety-related notifications?
This has to be tested on a case-by-case basis. For the UI elements, yes, the performance should be adequate. Our testing indicates you can build HMIs that are surprisingly responsive. Also, our WebKit port lets you do things things like run JavaScript code in other tabs, threads, or processes to ensure those ocmponents aren’t being thread-blocked by something less critical.

I do get a little gun-shy recommending HTML5 for safety-critical components, because JavaScript isn't inherently real-time. If you wouldn't feel comfortable using Java for a critical coding task, you shouldn't use HTML5 either. If you want predictable, real-time performance for a lower-level computation that cannot tolerate any delay, the code should execute in a non virtual-machine environment. Most code doesn’t really fit that description, so most of the time JavaScript should work just fine.

How do you call vehicle resources — vehicle HMI, vehicle diagnostics information, etc. — on a HTML web app in the car? What's the process in plain words?
In plain words, it’s kinda hard. :-) But here’s my best take on this question: we solve this by creating a vehicle-bus driver that exports data through a publish/subscribe mechanism. The HTML5 layer talks to that piece through a JavaScript interface.