Success! Solar Impulse 2 completes trans-Pacific flight

Solar-powered plane lands in Santa Clara county after nonstop, 62-hour trip

Solar Impulse flies over Golden Gate Bridge
Source: Solar Impulse

Imagine you are piloting a plane the size of a 747. But unlike a 747, this plane has an unheated, unpressurized cockpit in which temperatures fall as low as -40°. Moreover, you have to fly for over 60 hours straight, without ever getting up to stretch. And as for sleep, don’t count on getting much. You can take naps, but only about 6 a day, each lasting 20 minutes.

Sound like your kind of challenge? If so, you should sign up to join the Solar Impulse team. Because that’s exactly the kind of endurance needed to pilot Solar Impulse 2, the solar-powered plane that has just completed the latest leg of its historic round-the-world flight.

Last Thursday, Solar Impulse 2 took off from Kalaeloa, Hawaii, with pilot Bertrand Piccard at the helm. (This is the same Piccard who, in 1999, became the first person to complete a non-stop balloon circumnavigation of the earth.) Sixty-two hours later, the plane touched down on Moffett airfield, in Santa Clara county. From there, it will fly to several points across the U.S. before it takes off from New York for a non-stop flight across the Atlantic Ocean.

Solar Impulse 2 has four propellers, but doesn’t sip an ounce of fuel. Instead, it relies solely on the power of the sun. As such, it is a testament to modern technology. But as I’ve already hinted, it is also a testament to the depths of human endurance and stick-with-it-ness. If you were impressed that anyone could pilot a plane for over 60 hours straight, consider the plane’s nonstop solo flight from Japan to Hawaii, which took 120 hours from start to finish!

QNX Software Systems is proud to be the official realtime OS partner for the Solar Impulse team. The plane uses the QNX Neutrino OS for several control and data communication functions.

Read my previous posts on this groundbreaking project and check out the Solar Impulse website.

Solar Impulse returns to the skies

Crew of QNX-equipped solar plane set to resume historic flight

Solar Impulse: powered only
by the sun  Source: Solar Impulse

In case you missed it, Solar Impulse, the solar-powered airplane that is flying around the world to promote green energy, has returned to the skies.

The Solar Impulse team suffered a temporary setback last summer, when the plane’s batteries overheated during a five-day flight between Japan and Hawaii. Battery problems notwithstanding, the 120-hour trip set a world record for longest non-stop solo flight.

The team has since upgraded the plane with a newer (and cooler) battery system and has successfully completed three test flights. If all goes as planned, the plane will take off from Hawaii in mid-April for a four-day journey to the continental United States. Once the plane completes its U.S. crossing, it will fly non-stop across the Atlantic.

The plane’s round-the-world trek began on March 9, 2015, when it took off from an airport in Abu Dhabi. It then completed several hops, totaling 18000 kilometers, before landing in Kalaeloa on June 28.

Solar Impulse may be powered by the sun, but it can fly at night, using energy stored in its lithium-ion batteries — all 17250 of them. The plane is massive, with the wing span of a Boeing 747, yet weighs no more than a family car.

Solar Impulse bootup screen. Screen-grab from video.

QNX Software Systems is the official realtime OS partner for the Solar Impulse team. The plane uses the QNX Neutrino OS for several control and data communication functions.

I’ve been tracking the progress of the Solar Impulse project since 2009. Read my previous posts, which include a look at the plane’s virtual cockpit. And remember to check out the Solar Impulse website.

From clean socks to secure transactions, QNX brings it all to Embedded World

Every year, QNX Software Systems exhibits at the Embedded World conference in Nuremburg. And every year, we like to mix things up and do something different. For instance, in years past, we have showcased a robotic vacuum, a heart defibrillator, a pipeline inspection system, an Oscar-winning flying camera, a programmable logic controller, and a control panel for bulldozers — all running on the QNX Neutrino OS.

What have we got lined up this year? Plenty, as it turns out. Once again, our booth will feature several QNX-based products, including:

• An innovative double-drum washing machine that cleans two loads of laundry simultaneously — finally, you can wash lights and darks at the same time!
• A Modular Train Control System (MTCS) from MEN Mikro Elektronik that complies with the EN 50155 functional safety standard and is based on the QNX OS for Safety
• A hardware security module from Worldline that protects secret keys and performs high-speed cryptographic operations for secure data transactions
• A traffic-light controller from SWARCO that helps improve traffic flow and optimizes the use of existing road infrastructure — learn more about this system in this morning’s press release

It’s hard to imagine four systems that could be more different. And yet, the developers of these systems all chose the same OS — a testament to the “bend it, shape it, any way you want it” quality of QNX technology. Not to mention its performance and reliability.

The Bluetooth connection
Of course, we can’t show up at Europe’s biggest embedded systems conference without bringing something new for embedded developers. And so, this year, we are demonstrating the QNX SDK for Bluetooth Connectivity, a new middleware solution for medical devices, industrial automation systems, consumer appliances, and other embedded system applications.

Designed for flexibility, the SDK offers a dual-mode Bluetooth Smart Ready stack that supports classic Bluetooth connectivity as well as connectivity to Bluetooth Low Energy devices. It also supports a comprehensive set of pre-integrated Bluetooth profiles, including the classic PAN, SPP, HDP, HID, FTP, and OPP profiles, as well as the BAS, FMP, HRP, HOGP, and PXP Low Energy profiles. Here’s the SDK at a glance:

For developers of infusion pumps, vital-sign monitors, and other medical devices, the SDK includes an IEEE 11073 Personal Health Data stack certified by the Continua Health Alliance. This stack enables easy interoperability with pulse oximeters, weight scales, and other Bluetooth-enabled peripherals, and addresses the growing demand for health devices that can wirelessly collect patient data, either at home or in a clinical setting.

Of course, the proof of the Bluetooth pudding is in the pairing. So we've also built a demo that shows how the SDK can help developers build vital-sign monitors and other connected embedded systems. The demo system can discover and pair with Bluetooth classic and Bluetooth Low Energy devices, render their data onto a touchscreen display based on Qt 5, and provide a history of heart rate, blood oxygen levels, and other vitals:

A screen capture of the Bluetooth-powered QNX medical demo

Read the press release and product-overview page to learn more about the new QNX SDK for Bluetooth Connectivity.

And if you are Nuremberg this week, drop by and see us! We’re in Hall 4, Booth 534.

They did it! Solar Impulse team makes non-stop flight from Japan to Hawaii

Solar-powered plane sets new endurance record while completing toughest leg of round-the-world journey.

Touching down in Kalaeloa

Source: Solar Impulse 

Now here's good news for a Friday afternoon: The Solar Impulse 2, a solar-powered plane outfitted with QNX technology, has landed safely in Kalaeloa, Hawaii, after completing the longest leg of its round-the-world mission and setting a new endurance record for solo flight.

The plane lifted off from Nagoya on June 28 and touched down in Kalaeloa almost 120 hours later, using the sun as its only power source. And did I mention? The plane had only pilot, André Borschberg, who was at the helm for the entire 5-day flight. Yes, he was able to take naps while the plane was on autopilot — but only 6 a day, each lasting 20 minutes. Color me impressed.

The team’s round-the-world flight, which started on March 9 in Abu Dhabi, hit a snag when the plane reached Nagoya, where weeks of bad weather threatened to cancel the project. But, finally, a five-day window of clear weather opened and the team was able to resume its historic journey, which is dedicated to the promotion of green energy.

The team’s other pilot, Bertrand Piccard, will fly the next leg, from Honolulu to Phoenix, Arizona. Piccard’s name may ring a bell, but not because of any Star Trek connection: In 1999, he became the first person to complete a non-stop balloon circumnavigation of the earth.

QNX Software Systems is the official realtime OS partner for the Solar Impulse team, and the plane uses the QNX Neutrino OS for several control and data communication functions. Read my previous posts for more information on the Solar Impulse project.

Developing software for safety-critical systems? Have I got a book for you

Chris Hobbs is the only person I know who holds a math degree with a specialization in mathematical philosophy. In fact, before I met him, I didn’t know such a thing even existed. But guess what? That’s one of the things I really like about Chris. The more I hang out with him, the more I learn.

Come to think of it, helping people learn has become something of a specialty for Chris. He is, for example, a flying instructor and the author of Flying Beyond: The Canadian Commercial Pilot Textbook. And, as a software safety specialist at QNX Software Systems, he regularly provides advice to customers building systems that must comply with functional safety standards like IEC 61508, EN 5012x, and ISO 26262.

Chris has already written a number of papers on software safety, some of which I have had the great privilege to edit. You can find several of them on the QNX website. But recently, Chris upped the ante and wrote an entire book on the subject, titled Embedded Software Development for Safety-Critical Systems. The book:

• covers the development of safety-critical systems under ISO 26262, IEC 61508, EN 50128, and IEC 62304
• helps readers understand and apply remarkably esoteric development practices and be prepared to justify their work to external auditors
• discusses the advantages and disadvantages of architectural and design practices recommended in the standards, including replication and diversification, anomaly detection, and so-called “safety bag” systems
• examines the use of open-source components in safety-critical systems

I haven’t yet had a chance to review the book, but at 358 pages, it promises to be a substantial read.

Interested? Well, you can’t get the book just yet. But you can pre-order it today and get one of the first copies off the press. It’s scheduled for release September 1.

A version of this post appeared in the QNX Auto Blog.

Behind the controls of the Solar Impulse

Virtual cockpit lets you follow progress of round-the-world flight in real time.

What’s it like to get behind the controls of a solar-powered plane — a plane now in the process of circumnavigating the globe? You and I will never really know, but we can enjoy the next best thing: a virtual cockpit that provides a pilot’s eye view of the plane’s instrument panel.

Just point your browser to the Solar Impulse website whenever the plane is in the air, and you will see real-time updates to the plane’s flight instruments. For instance, in this screen capture, you can see the current position of the ailerons, airbrakes, elevators, and rudder, along with the airspeed (in knots), vertical speed (rate of climb or descent), heading, and altitude:



And in the following screen capture, you can see much of the same information, presented in a different fashion, along with the attitude indicator, which shows whether the wings are level and whether the nose is pointing above or below the horizon:



I've covered only a subset of the real-time information displayed on the Solar Impulse website. For example, you can also view a map of the plane’s progress, a video feed of the mission-control center, and the current power mode of the plane’s electrical system:



QNX Software Systems is the official realtime OS partner for the Solar Impulse team, and the plane uses the QNX Neutrino OS for several control and data communication functions.

Flying in the dark on solar energy

Crew of QNX-equipped Solar Impulse plane gears up for historic flight.

The Solar Impulse 2, aka SI2
Source: Solar Impulse

The countdown has begun. On Monday, March 9, the Solar Impulse 2, a one-of-a-kind airplane that runs exclusively on solar power, will take off from an airport in Abu Dhabi. The destination? Abu Dhabi!

That’s right, this is a round trip — but not just any round trip. It is, in fact, the first attempt to fly around the world using only the power of the sun. On board will be André Borschberg, the former jet pilot who, together with Bertrand Piccard, cofounded the Solar Impulse project 12 years ago. (Piccard’s name may ring a bell — as well it should. In 1999, he became the first person to complete a non-stop balloon circumnavigation of the earth.)

The Solar Impulse can fly at night, using energy stored in its lithium-ion batteries. But it’s no fly-by-night operation. Borschberg and Piccard have spent the last 12 years on this project and have set 8 world records in the process, including longest uninterrupted flight (26 hours, 10 minutes) and highest altitude (9235 meters) for a solar-powered plane. That’s pretty impressive, but then, everything about this plane is remarkable, from the wingspan (72 meters) to the number of voltaic cells (17250) that power its electric motors.

Solar Impulse bootup screen. Screen-grab from video.

The human element is equally impressive. To cross the Pacific or Atlantic ocean, the plane, which has a cruise speed of 90  km/h, will need to stay airborne for about 5 days, nonstop. And that means the pilot also needs to stay airborne for 5 days, in an unheated, unpressurized cabin with temperatures ranging from -40°C to +40°C. Yes, the pilot is allowed to take naps, but only 6 a day, each lasting 20 minutes. Not surprisingly, both pilots (Borschberg and Piccard will each take turns flying the plane), have learned self-hypnosis and meditation techniques to help them enter and exit deep sleep as quickly as possible. The plane can accommodate only one pilot at a time, and the team plans a total of five stops to allow changes of pilots.

As mentioned in previous posts, QNX Software Systems is the official realtime OS partner for the Solar Impulse team, and the plane uses the QNX Neutrino OS for several control and data communication functions. So, as you can imagine, come next Monday, my browser will be tuned to the Solar Impulse website. I hope yours will, too.

Until then, here's a “making of” video of the Solar Impulse 2. Enjoy.

Hypervisors, virtualization, and creating a safety-critical system that keeps up with the Joneses

A new webinar on how virtualization can help you add new technology to existing designs.

First things first: should you say “hypervisor” or “virtual machine monitor”? Both terms refer to the same thing, but is one preferable to the other?

Hypervisor certainly has the greater sex appeal, suggesting it was coined by a marketing department that saw no hope in promoting a term as coldly technical as virtual machine monitor. But, in fact, hypervisor has a long and established history, dating back almost 50 years. Moreover, it was coined not by a marketing department, but by a software developer.

“Hypervisor” is simply a variant of “supervisor,” a traditional name for the software that controls task scheduling and other fundamental operations in a computer system — software that, in most systems, is now called the OS kernel. Because a hypervisor manages the execution of multiple OSs, it is, in effect, a supervisor of supervisors. Hence hypervisor.

No matter what you call it, a hypervisor creates multiple virtual machines, each hosting a separate guest OS, and allows the OSs to share a system’s hardware resources, including CPU, memory, and I/O. As a result, system designers can consolidate previously discrete systems onto a single system-on-chip (SoC) and thereby reduce the size, weight, and power consumption of their designs — a trinity of benefits known as SWaP.

The QNX Hypervisor is an example of a 

Type 1 “bare metal” hypervisor.

That said, not all hypervisors are created equal. There are, for example, Type 1 “bare metal” hypervisors, which run directly on the host hardware, and Type 2 hypervisors, which run on top of an OS. Both types have their benefits, but Type 1 offers the better choice for any embedded system that requires fast, predictable response times — most safety-critical systems arguably fall within this category.

Moreover, some hypervisors make it easier for the guest OSs to share hardware resources. The QNX Hypervisor, for example, employs several technologies to simplify the sharing of display controllers, network connections, file systems, and I/O devices like the I2C serial bus. Developers can, as a result, avoid writing custom shared-device drivers that increase testing and certification costs and that typically exhibit lower performance than field-hardened, vendor-supplied drivers.

Adding features, without blowing the certification budget
Hypervisors, and the virtualization they provide, offer another benefit: the ability to keep OSs cleanly isolated from each other, even though they share the same hardware. This benefit is attractive to anyone trying to build a safety-critical system and reduce SWaP. Better yet, the virtualization can help device makers add new and differentiating features, such as rich user interfaces, without compromising safety-critical components.

That said, hardware and peripheral device interfaces are evolving continuously. How can you maintain compliance with safety-related standards like ISO 26262 and still take advantage of new hardware features and functionality?

Enter a new webinar hosted by my inimitable colleague Chris Ault. Chris will examine techniques that enable you to add new features to existing devices, while maintaining close control of the safety certification scope and budget. Here are some of the topics he’ll address:

• Overview of virtualization options and their pros and cons
   
• Comparison of how adaptive time partitioning and virtualization help achieve separation of safety-critical systems
   
• Maintaining realtime performance of industrial automation protocols without directly affecting safety certification efforts
   
• Using Android applications for user interfaces and connectivity

Webinar coordinates:
Exploring Virtualization Options for Adding New Technology to Safety-Critical Devices
Time: Thursday, March 5, 12:00 pm EST
Duration: 1 hour
Registration: Visit TechOnLine

A version of this post was published on the QNX Auto Blog.

Autonomous forklifts gear up with QNX and HTML5

Warehouse robots need reliable realtime control. They also need an intuitive user interface. Can one OS handle both?

When it comes to forklifts, I am as dumb as they come. I had always assumed that one forklift is much like any other, aside from obvious differences in size and color. Boy, did I get that wrong. A quick perusal of Wikipedia reveals some 30 forklift types, ranging from “walkie stackers” (which, true to their name, are walked, not ridden) to “EX-rated lift trucks” (which, contrary to their name, aren’t designed to carry erotica but to be explosion proof).

Forklifts also come in driverless variants called automated guided vehicles, or AGVs. Case in point: the QNX-powered AGVs built by Euroimpianti, a global leader in automated warehouse systems. These vehicles can, without human intervention, load and unload trucks, as well as move materials from one area of a warehouse or factory to another. Moreover, they can operate 24/7, using a list of prioritized missions downloaded from a central management system.

As you might expect, Euroimpianti uses the QNX Neutrino OS in the realtime control systems of its AGVs. After all, predictable response times and high reliability — qualities essential to safe operation of a driverless vehicle in a busy warehouse — are QNX Neutrino’s stock-in-trade.

But here’s the thing: Euroimpianti has also decided to standardize on QNX Neutrino for the human machine interfaces (HMIs) of its operator panels. Why do that, when the HMIs could run on an OS like Windows Embedded or Android? The answer lies in the many features introduced in the QNX Neutrino OS 6.6 and the new QNX SDK for Apps and Media.

These features include a framework for creating apps and HMIs with industry-standard technologies like HTML5, JavaScript, and CSS, and a graphical composition manager that can seamlessly blend apps and graphical components created in HTML5, OpenGL ES, Qt, and other environments, all on the same display. In addition, the SDK offers secure application management, comprehensive multimedia support, mobile device connectivity, an optimized HTML5 engine, and other features for building mobile-class user experiences into embedded systems — including, of course, AGVs.

To quote Maurizio Calgaro, electronic engineering manager, Euroimpianti, “With its new QNX SDK for Apps and Media, QNX Neutrino enables us to create dynamic HMIs that leverage the latest Web technologies, including HTML5. Our operator panels and control systems can now run on the same, standards-based OS, and that means greater productivity for our developers and, ultimately, faster time-to-market for our solutions.”

The QNX SDK for Apps and Media includes an HTML5 environment to create and deploy applications.

Euroimpianti's QNX-based robotic systems also include Cartesian robots, anthropomorphic robots, and selective compliance assembly robot arms (SCARA). The systems are deployed internationally in the automotive, beverage, cosmetic, food, dairy, electrical, glass, and pharmaceutical industries. Learn more on the Euroimpianti Website, which includes many videos of the robots in action.

Using the same OS for both realtime control and user interface control.

Bend it, shape it, any way you want it

Last year, at Embedded World 2014, QNX Software Systems demonstrated three systems built by its customers: a touch display that connects washing machines to the Web, an operator panel that controls forklifts and bulldozers, and an inspection system that detects cracks in gas pipelines. These systems perform very different functions, and operate in very different environments, yet they have one thing in common: the QNX Neutrino OS.

Fast-forward to Embedded World 2015, where, once again, QNX will showcase the remarkable flexibility of its OS technology, in everything from a medical device that saves lives to a robot that cleans carpets. Of course, the new demos aren’t just about flexibility. They also showcase how QNX technology can make embedded systems easier to build, easier to certify, and easier to use. Not to mention more reliable.

So if you’re at Embedded World this week, come on over and visit us at Booth 4-358. In the meantime, here's a quick peek at what we plan to showcase:

Demo #1: The autonomous vacuum
Chances are, the QNX booth will have the cleanest floor in all of Embedded World. And for that, you can blame the Neato Botvac robot vacuum.

This Botvac is one smart appliance: Before it starts to suck up dirt, it scans and maps the entire room so it can work as quickly and methodically as possible. It’s also smart enough, and quick enough, to maneuver around furniture and to avoid staircases.

To quote Mike Perkins, vice president of engineering at Neato Robotics, “our autonomous home robots need fast, predictable response times, and the QNX OS enabled our engineers to achieve very high performance on cost-effective hardware. The QNX OS also helped us create a software architecture that can quickly accommodate new features, giving us the flexibility to scale product lines and deliver compelling new capabilities.”

Check out this video of the Botvac in action:



Demo #2: The defibrillator
If you don’t already know, the QNX Neutrino OS is used in dialysis machines, infusion pumps, angiography systems, surgical robots, and a variety of other hospital-based medical devices. But it’s also used in mHealth devices that provide critical therapy or diagnostics when the nearest hospital is miles away. Case in point: the corpuls1, a defribrillator and patient monitor for fire fighters and other first responders, built by GS Elektromedizinische Geräte G. Stemple:




Demo #3: The medical reference demo
The QNX booth will also feature our latest medical reference demo, which integrates a suite of QNX, BlackBerry, and third-party technologies for building connected, safety-critical medical devices. Here is what the demo system looks like:



And here is a sample of what’s under the covers:

● IEC 62304-compliant QNX OS for Medical
● HL7, the international standard for transfer of clinical data
● User interface based on the Qt application framework
● Java runtime engine
● Remote device management and end-to-end security of the BlackBerry BES12 architecture

Demo #4: The QNX SDK for Apps and Media
We released the first version of this SDK almost exactly one year ago. In a nutshell, it extends the capabilities of the QNX Neutrino OS 6.6, enabling embedded developers to create rich user interfaces and applications with HTML5, JavaScript, CSS, and other Web technologies. It also offers secure application management, comprehensive multimedia support, mobile device connectivity, an optimized HTML5 engine, and other advanced features for building mobile-class user experiences into embedded devices.

You can learn more about the SDK on the QNX Website. In the meantime, here’s the home screen of the SDK, showing several of its built-in applications and demos:



Demo #5: The [CENSORED] robot
What kind of robot, you ask? Sorry, you’ll have to wait until the first day of Embedded World, when we will showcase a video of this (very cool) QNX system in action.

Demo #6: The all-new QNX [CENSORED]
Again, I can’t tell you what this is. I can’t even give you a hint. I can mention, however, that it’s a brand new product that will run on an automotive demo system in our booth. But don’t be fooled by the automotive connection! The new product can, in fact, be used in a wide variety of devices, not just cars. Stay tuned.



Visit www.qnx.com to learn more about QNX at Embedded World, including presentations on IoT and safety-critical design. And while you're at it, download this infographic to see how flexible QNX technology really is.

Breaking up is hard to do

Separation can be painful. But often, the failure to separate can result in even more pain over the long haul.

No, I’m not talking love, marriage, or other affairs of the human heart. I am talking software design. In particular, the design of complex software systems that must perform safety-critical functions. The software, for example, in a medical device, automotive ADAS unit, or train-control system.

In systems like these, separation is critical: software components must be cleanly isolated from one another. Otherwise, you risk the chance that the behavior of one component will inadvertently interfere with the behavior of another. For this reason, component isolation is a key thrust of functional safety standards like IEC 61508 and ISO 26262.

Several forms of interference, all undesirable.

Interference can take many forms. For instance, a component could improperly use file descriptors or flash memory needed by other components. Or it could enter a tight loop under a failure condition and starve a more-critical component of CPU time. Or it could write to the private memory of another component.

You could, of course, run every component on separate hardware. But that becomes an expensive proposition. Moreover, the market trend is toward hardware consolidation, which, for reasons of economy, merges previously discrete systems onto a single platform.

It’s important, then, to embrace software-based separation techniques. These include OS mechanisms to prevent resource deprivation, time starvation, data corruption, and so on. For instance, the adaptive time partitioning provided by the QNX Neutrino OS can ensure that a software component always gets a minimum percentage of CPU time, whenever it needs it. That way, other components can't prevent it from running, either unintentionally or maliciously.

Software separation is as much art as science. In fact, my colleague Yi Zheng goes further than that. She argues that there is as yet no precise methodology for separating system functions. There are no textbooks, no pat answers.

So is separation only a matter of asking the right questions? That would be an oversimplification, of course. Skill also comes into play, as does experience, not to mention a good dose of thoroughness. But really, you should read Yi’s article, “The Art of Separation”, in Electronic Design and judge for yourself.

Oscar-winning Flying-Cam system takes to the skies with QNX technology

Flying-Cam has been at
the forefront of unmanned
aerial filming since 1988.

Ever wonder how film crews manage to achieve death-defying camera angles that take your breath away? Well, wonder no more, because I am about to show you one of the most advanced tools of the trade. It's called SARAH, it runs on the QNX OS, and it recently won a Scientific and Technical Award from the Academy of Motion Picture Arts and Sciences for its contribution to movie making.

The SARAH unmanned aerial system is the brainchild of Flying-Cam, a company founded in 1988 by Emmanuel Prévinaire, who, in 1979, developed the first unmanned close-range aerial camera for motion pictures. SARAH represents the latest generation of Flying-Cam technology and has been in service since 2012 — yet its credits already include Skyfall, Oblivion, Prisoners, Smurfs II, and Mr. Go.

The Flying-Cam SARAH unmanned aerial system in action, filming a scene for Mr. Go. 

So why did the folks at Flying-Cam choose the QNX OS? Several factors contributed to the decision, including flexible architecture, predictable response times, and advanced profiling tools. To quote Tony Postiau, head of aerial robotics engineering at Flying-Cam, "we have been thoroughly impressed with the QNX OS. It works extremely well on our hardware and uses system resources efficiently, leaving most of the hardware processing power available to our application — a crucial attribute that we looked for.”

To find out more about QNX and the Flying-Cam SARAH system, check out the press release that QNX issued this morning.

And for a look at SARAH in action, here's a promotional video that demonstrates how it helps film crews capture angles that would be impossible for full-size helicopters, cable systems, or other traditional camera support devices:

New release of QNX OS closes UX gap between smartphones and embedded systems

Okay, this one is going to be short. I'd love to have you stay, but I'd like it even more if you jumped to the QNX website. Because if you do, you'll get the full skinny on a significant new OS release that QNX Software Systems announced this morning.

But before you go, the back story. Mobile devices (think smartphones) have transformed what people expect of embedded systems (think gas pumps, vending machines, heart monitors, or just about any other device with a user interface). Every time someone uses a smartphone or tablet, they become more conditioned to the user experience it delivers. And the more conditioned they become, they more they expect a similar experience in other systems they use. It's human nature, plain and simple.

People who create embedded devices get this. They know that, to succeed, they must up their UX game. The problem is, a gap has existed between the user experiences that embedded operating systems can support and the user experiences that people want. The latest generation of the QNX Neutrino OS, version 6.6, addresses that gap. And it does so by introducing a new and potent mix of graphics, security, multimedia, security, and power management capabilities.

And just what are those capabilities? You'll have to jump to the press release to find out. :-)


The QNX SDK for Apps & Media — one of many significant new features
in the latest release of the QNX OS.

QNX at Embedded World: three distinct systems, one OS platform

A whole new way to

take QNX out for a spin.

Quick: what do washing machines, bulldozers, and pipeline inspection tools have in common? Simple: they all demonstrate the remarkable flexibility of the QNX OS.

Next week, at Embedded World, QNX will showcase three systems built by three different customers, for three different markets. Each system addresses different technical challenges and targets different end-users. And yet, in each case, the development team behind the system chose the same OS — a testament to the “bend it, shape it, any way you want it” quality of QNX technology.

Of course, not everyone can attend Embedded World. So for anyone who can’t go (or for anyone who plans to go and would like a taste of what they’ll see), here’s a sneak peek of the three systems. Mind you, this isn’t everything we will demonstrate next week — but that’s the subject of another post. :-)

Washing machine touchscreen from Dalian Eastern Display
Imagine a web-connected washing machine that can play your favorite music and videos, provide tips on removing stains, and let you choose laundry settings with the tap of a touchscreen. The system from Dalian Eastern Display lets you do all this and more, and it’s one of many solutions that Dalian is creating for IoT smart appliances.

For instance, this screen lets you quickly choose your fabrics, including cotton, wool, or polyester. It also provides a mixed setting — handy for people who aren’t sure of the difference. Me, for instance.



Once you’ve chosen the right fabric, you can fine-tune the parameters of your wash cycle, including time, temperature, speed, and water level:



Meanwhile, this menu lets you configure everything from your network connection to the system’s sound settings:



Murphy PowerView 780 display for heavy machinery
If you build equipment that has an engine and demands a rugged display, chances are its owners and operators will benefit from a Murphy PowerView 780. Designed for use with electronic or mechanical engines in everything from boats to bulldozers, the PowerView 780 integrates engine, transmission, and diagnostic information into an easy-to-read user interface. The PowerView 780 is built for extreme outdoor environments and features a 7-inch bonded LCD that is readable in direct sunlight. Better yet, it’s easily configurable to application needs. Using Murphy’s PowerVision Configuration Studio™, developers can customize the user interface with their own graphics or display parameters, track maintenance schedules, log operation data and faults, and add OEM branding.



Murphy, the company behind the PowerView 780, is a global supplier of controls and instrumentation for almost any application that involves engines or engine-driven equipment. The company is celebrating 75 years of serving the oil and gas production, engine OEM, construction, irrigation, agriculture, power generation, and work and pleasure boating markets.

LineExporer pipeline inspection system from NDT Global
When it comes to oil and gas pipelines, safety is job one. But to ensure safety, you need to keep pipelines properly maintained — and to maintain them, you need accurate and reliable inline inspection tools. That's where NDT Global comes in. NDT is a leading supplier of ultrasonic pipeline inspection and pipeline integrity management services worldwide, with operations in Germany, Russia, the US, Canada, Mexico, U.A.E., Malaysia and Singapore. At Embedded World, QNX Software Systems will showcase an NDT LineExplorer inline inspection tool for 10" pipelines that can detect and measure corrosion and cracks, depending on the sensor carrier.



For more information on QNX at Embedded World, visit the QNX website.

Striking a balance between reliability and availability

Can you achieve one without

sacrificing the other?

Maybe it's just me, but a lot of people seem to use reliability and availability interchangeably. I often hear people say 99.999% reliability when, in fact, they are referring to availability.

So what is the difference between the two? And why is that difference important? I'm glad you asked. :-)

In a software-based system, availability refers to how often the system responds to events or stimuli in a timely manner; reliability, on the other hand, refers to how often the responses are correct. The distinction can be a matter of life or death. For instance, in some medical devices, it is preferable to have no response (where little or nothing happens to the patient) than a wrong response (where the device harms the patient irreparably). Whereas in other systems, any response of sufficient accuracy or quality may be preferable to no response at all.

But here's the thing. Regardless of whether a system is more sensitive to availability or reliability, it should still take pre-defined (and carefully considered) actions when a dangerous condition arises. For instance, if the control system for a high-speed train fails, it will move to its design safe state, which will probably involve applying the brakes.

So far, so good. The problem is, many systems are components of larger systems. So even when a component is avoiding a genuinely dangerous situation, its behavior may put stress on the larger system and lower that system's availability.

Moreover, the behavior of an overall system when an unanticipated condition occurs can be very difficult to predict, for the simple reason that the system depends on multiple, largely independent, components moving to their design safe states. None of those components, and their safe states, can be considered in isolation. For instance, in 1993, Lufthansa Flight 2904 overran a runway because the reverse thrust deployment system operated exactly to specification. Unfortunately, the system designers hadn't anticipated conditions during a cross-wind landing.

Enough from me. I invite you read the ECN article "Balancing reliability and availability", written by my colleague and senior software developer Chris Hobbs. Chris discusses how it's possible to strike a balance between reliability and availability — and why designing safe software can require the ability and willingness to think from the outside in.

QNX announces support for new Intel Atom E3800 processor family

In 2008, the Intel Intelligent Systems Alliance presented QNX Software Systems with an "Award of Excellence, Most Innovative Software" for its fastboot support of the Intel Atom Processor. Fast forward to this morning, when QNX announced that it will extend its Atom support to include the new Intel Atom E3800 product family, which was created to address the high performance-per-watt demands of medical devices, building automation panels, industrial control systems, in-car infotainment systems, and other smart devices.

Said Sam Cravatta, product line manager at Intel, "Stellar graphics support is crucial for application and intelligent system development. The Atom processor E3800 product family is the first to take advantage of Intel’s Gen 7 graphics, complementing QNX Software Systems’ graphics framework, tools, and runtime components for creating sophisticated displays that feature improved 2D and 3D graphics rendering with little CPU overhead.”

Highlights of the Intel Atom E3800 family include high I/O connectivity, an integrated memory controller, virtualization, error correcting code (ECC), and a thermal design power range of 5W to 10W2.

Read the QNX press release and read more about the E3800 product family.

Six QNX videos more people ought to see

Looking for examples of how people use QNX? You've come to the right place. From outer space to the automotive space, these six videos demonstrate the sheer flexibility and dynamic range of QNX technology. Better yet, you get to hear five users describe, in their own words, why QNX is important to what they do.

QNX in space
First up is Iain Christie of Neptec, the company responsible for creating the SVS and LCS camera systems on the NASA space shuttle. Highlight: when Ian explains the importance of QNX to the shuttle program (1:46). For more on the QNX-based LCS system, see my previous post.



QNX in the clinic
Next up is Vladimir Derenchuk of the Indiana University Health Proton Therapy Center, which uses proton beams to blast difficult-to-treat tumors. Highlight: it's all good, but listen to Vladimir explain why they chose QNX, and how it has helped with FDA approvals (1:34).



QNX in the HVAC
Next up is Hans Symanczik of Kieback & Peter, a German firm that has used QNX in building automation systems for more than 20 years. Highlight: when Hans explains the ultimate benefit of the QNX OS (2:07).



QNX on the air
Next up is Mikael Vest of NTP, a Danish company that supplies QNX-based audio routers to the global television and radio broadcasting industry. Highlight: Mikael himself, who gladly did this interview despite suffering from a flu to end all flus. A real trooper.



QNX on the road
Next up is Rick Kreifeldt of Harman International, a company known in the automotive industry for its ability to push the technology envelope. Highlight: the section where Rick's respect for the QNX team shines through (2:14).



QNX in flight
And last but not least is Thomas Allen from Mechtronix, a company that has developed an innovative, software-based approach to building flight simulators. Highlight: when Allen states that Mechtronix simulators effectively use the same software architecture as the QNX OS (0:45). Years, ago, someone explained to me how the QNX OS isn't simply a well-designed, modular OS; it also encourages well-designed, modular systems. In Mechtronix, we have an example.

Solar Impulse plane completes final leg of cross-America trek

It has the wingspan of a Boeing 777, but weighs only as much as a family car. It has four propellers, but doesn’t sip an ounce of fuel. It's called the Solar Impulse, and it is the first plane designed to fly round the clock using only solar power.

In early May, the Solar Impulse took off from Mountain View, California on the first leg of its journey across America. Last night, it completed the trek, landing at New York's JFK Airport. In between, the plane made stopovers at Phoenix, Dallas, St. Louis, and Washington DC, allowing the Solar Impulse team to meet the public, show off the plane, and promote their vision of renewal energy. (In New York next weekend? If so, you're in luck: you can see the plane in person at JFK.)

Along the way, the plane set a new distance record for solar-powered flight: 1541 kilometers. The previous record was 1116 kilometers, set by — you guessed it — the Solar Impulse team.

QNX Software Systems is the official realtime OS partner for the Solar Impulse project, which uses QNX technology for several of the plane's control and data management functions. For more on the project and the people behind it, see the Solar Impulse website.

But before you go, check out this video, which starts off with some inspiring clips of the Solar Impulse in flight — followed by a cameo appearance by Larry Page wearing Google Glass.

Space-grade technology... in the palm of your hand

What does your phone have in common with planes, trains, automobiles, and space stations? If it's a BlackBerry 10 smartphone, plenty.

When you pick up a BlackBerry Z10 or BlackBerry Q10 phone, you are tapping into OS technology like no other. Technology that hospitals use to defeat cancer. Technology that power plants use to create energy. Technology that skyscrapers use to save energy. Technology that movie studios use to create mind-blowing special effects. And technology that calls for help if your car gets into an accident. In short, technology that makes a difference in my life, your life, everyone's life.

But enough from me. Especially when the video says it so much better...

Can a safety-critical system be over-engineered?

Too much of a good thing?

It's a rhetorical question, of course. But hear me out.

As you can imagine, many safe systems must be designed to handle scenarios outside their intended scope. For instance, in many jurisdictions, passenger elevators must be capable of handling 11 times more weight than their recommended maximum — you just never know what people will haul into an elevator car. So, if the stated limit for a passenger elevator is 2000 pounds, the actual limit is closer to 22,000 pounds. (Do me a favor and avoid the temptation to test this for yourself.)

Nonetheless, over-engineering can sometimes be too much of a good thing. This is especially true when an over-engineered component imposes an unanticipated stress on the larger system. In fact, focusing on a specific safety issue without considering overall system dependability can sometimes yield little or no benefit — or even introduce new problems. The engineer must always keep the big picture in mind.

Case in point: the SS Eastland. In 1915 this passenger ship rolled over, killing more than 840 passengers and crew. The Eastland Memorial Society explains what happened:

"...the Eastland's top-heaviness was largely due to the amount and weight of the lifeboats required on her... after the sinking of the Titanic in 1912, a general panic led to the irrational demand for more lifesaving lifeboat capacity for passengers of ships.

Lawmakers unfamiliar with naval engineering did not realize that lifeboats cannot always save all lives, if they can save any at all. In conformance to new safety provisions of the 1915 Seaman’s Act, the lifeboats had been added to a ship already known to list easily... lifeboats made the Eastland less not more safe..."

There you have it. A well-intentioned safety feature that achieved the very opposite of its intended purpose.

Fast forward to the 21st century. Recently, my colleague Chris Hobbs wrote a whitepaper on how a narrow design approach can subtly work its way into engineering decisions. Here's the scenario he uses for discussion:

"The system is a very simple, hypothetical in-cab controller (for an equally hypothetical) ATO system running a driverless Light Rapid Transit (LRT) system...

Our hypothetical controller has already proven itself in Rome and several other locations. Now a new customer is considering it for an LRT ATO in the La Paz-El Alto metropolitan area in Bolivia. La Paz-El Alto has almost 2.5 million inhabitants living at an elevation that rises above 4,100 meters (13,600 ft.—higher than Mount Erebus). This is a significant change in context, because the threat of soft and hard memory errors caused by cosmic rays increases with elevation. The customer asks for proof that our system can still meet its safety requirements when the risk of soft memory errors caused by radiation is included in our dependability estimates..."

So where should the engineer go from here? How can he or she ensure that the right concerns are being addressed? That is what Chris endeavours to answer. (Spoiler alert: The paper determines that, in this hypothetical case, software detection of soft memory errors isn't a particularly useful solution.)

Highly recommended.