QNX CAR Platform Powers Infotainment System in New Mercedes-Benz Concept Car
"Mercedes-Benz Concept S-Class Coup features all-digital instrument cluster and head unit
FRANKFURT, IAA Cars International Motor Show, September 12, 2013 QNX Software Systems Limited, a global leader in software platforms for in-car electronics, today announced that Mercedes-Benz has selected the QNX CAR platform to power the infotainment system in the Mercedes-Benz Concept S-Class Coup, an exciting new concept vehicle created to showcase Mercedes-Benz latest advancements in user experiences for the car.
The concept cars infotainment system brings the Mercedes-Benz design philosophy to life with a fresh and refined approach to the all-digital instrument cluster and head unit. The digital dials are functional yet sensual in the use of 3D and light, complementing the new interior. The use of particle effects conveys a sense of emotion to the head units main menu and mood-based selection of music, while the new Garmin map strikes a balance between form and function so that you arrive in style.
Visitors to the IAA Cars event, popularly known as the Frankfurt Motor Show, can see the concept car first hand at the Mercedes-Benz booth in the Festhalle.
QNX Software Systems has been working with Mercedes-Benz Research Development North America, Inc. MBRDNA for more than a decade, providing the group with advanced technologies for the specification, demonstration, and prototyping of next-generation vehicle electronics concepts. In fact, Mercedes-Benz was the first automaker to take advantage of the QNX OEM Innovation Labs OIL Program, which QNX Software Systems created to assist automakers with research planning and development. The infotainment system in the new Mercedes-Benz concept car is the latest result of this long and fruitful collaboration.
It is a thrill to see how an industry leader like Mercedes-Benz, with its phenomenal sense of automotive design, can leverage the flexibility of the QNX CAR platform to create a unique and compelling driving experience, said Andrew Poliak, global director, automotive business development, QNX Software Systems. When you look at this car, you are looking at the near future of automotive connectivity and infotainment. Its been a privilege to support our colleagues at Mercedes-Benz Research Development North America on this project.
The QNX CAR platform for infotainment systems is based on QNX technology proven in tens of millions of vehicles. Designed for flexibility, the platform provides automotive companies with a rich suite of pre-integrated technologies for building connected infotainment systems that can keep pace with innovations in mobile apps and devices while maintaining automotive-grade reliability.
We designed the infotainment system for the Mercedes-Benz Concept S-Class Coup to be a seamless extension of the digital lifestyle, enabling consumers to leverage existing mobile and cloud-based services to choose destinations easily and simply, in a way that is appropriate for the automotive context, said Johann Jungwirth, president and CEO of Mercedes-Benz Research Development North America, Inc.
About QNX Software Systems
QNX Software Systems Limited, a subsidiary of BlackBerry NASDAQ:BBRY; TSX:BB, is a leading vendor of operating systems, development tools, and professional services for connected embedded systems. Global leaders such as Mercedes-Benz, Cisco, General Electric, Lockheed Martin, and Siemens depend on QNX technology for vehicle infotainment units, network routers, medical devices, industrial automation systems, security and defense systems, and other mission- or life-critical applications. Founded in 1980, QNX Software Systems is headquartered in Ottawa, Canada; its products are distributed in more than 100 countries worldwide. Visit www.qnx.com and www.facebook.com/QNXSoftwareSystems, and follow @QNX_News on Twitter. For updates on the companys automotive work, visit qnxauto.blogspot.com and follow @QNX_Auto
2013 QNX Software Systems Limited. QNX, QNX CAR, Momentics, Neutrino, and Aviage are trademarks of BlackBerry Limited, which are registered and/or used in certain jurisdictions, and are used under license by QNX Software Systems Limited. All other trademarks belong to their respective owners.
QNX Software Systems Limited QSS is a subsidiary of BlackBerry Limited. Forward-looking statements in this news release are made pursuant to the safe harbor provisions of the U.S. Private Securities Litigation Reform Act of 1995 and applicable Canadian securities laws. When used herein, words such as expect, anticipate, estimate, may, will, should, intend, believe, and similar expressions, are intended to identify forward-looking statements. Forward-looking statements are based on estimates and assumptions made by QSS in light of its experience and its perception of historical trends, current conditions, and expected future developments, as well as other factors that QSS believes are appropriate in the circumstances. Many factors could cause QSSs actual results, performance, or achievements to differ materially from those expressed or implied by the forward-looking statements, including those described in the Risk Factors section of BlackBerrys Annual Information Form, which is included in its Annual Report on Form 40-F copies of which filings may be obtained at www.sedar.com or www.sec.gov. These factors should be considered carefully, and readers should not place undue reliance on QSSs forward-looking statements. BlackBerry and QSS have no intention and undertake no obligation to update or revise any forward-looking statements, whether as a result of new information, future events or otherwise, except as required by law. QSS is not responsible for and assumes no obligations or liability and makes no representation, warranty, endorsement, or guarantee in relation to any aspect of any third-party products or services."
05.06.2011 Understanding MeeGo Disclaimer: I'm a software developer with a background in Nokia's Maemo mobile Linux ecosystem. I've built both software and community services for it. As a Maemo enthusiast, I've also been following MeeGo with interest, and am helping to build some of the project infrastructure there as well. But I do not speak with the authority of the MeeGo project, and what is written below is my personal view into what MeeGo is. After the recent San Francisco MeeGo Conference there has been surprisingly much negative reporting about MeeGo, mostly centered at Nokia's MeeGo story. While Nokia's strategy cha...12.09.2016 A circle closes… At Desktop Summit 2011 in Berlin I did my first presentation on Wayland and presented the idea of Wayland to the KDE community and explained to the KDE community how we are going to port to Wayland. This year at QtCon in Berlin I was finally able to tell the KDE community that the port is finished and that our code is ready for testing. In 2011 I used a half hour slot to mostly present the differences between X11 and Wayland and why we want Wayland. In addition I presented some of the to be expected porting steps and what we will have in the end. This year I only used a 10 min lightning talk s...22.04.2009 Aaron Seigo (aseigo): kaizen and kakushin I read Mark Shuttleworth's blog entry about meta-cycles this evening and was taken back in my mind to an entry I wrote in September of 2007 about Toyota.My issue with the "6 month cycle" has always been three-fold: the number 6 is a project specific detail and should not be pushed on every project because it won't fit every project (Mark notes he works on projects with 1, 3 and 6 month cycles; other cycle are also possible, of course); what we're really talking about it timed releases made with a relatively high level of consistencyThe discussion is often coupled with the idea of coordinating ...04.01.2010 Aaron Seigo (aseigo): ++2009; The first decade of the millennium (by our calendars, anyways :) is officially over and we're all going to have to get used to writing 2010 on things. I spent the last couple of weeks of 2009 taking a few personal days around the holidays as well as considering where we, KDE, have been and where we might be going. I wrote some notes at the end of it, and I thought I'd share some of it with all of you.We accomplished a lot in the last year, both as a community as well as personally. I'll leave the personal events, positive and difficult, to those who were involved, but try and cover some of the...23.01.2010 Aaron Seigo (aseigo): key quest: webkit The list of "Key Quests for 2010" was alphabetical. It was a sensible ordering and it prevented me from having to prioritize them in some linear fashion that could never be definitive anyways: all the points are important, though often in different ways, for different reasons and even with different key audiences. So, alphabetical ordering it was! This meant that WebKit was going to be the last topic, and now here we are. (Honestly, I'm glad I'll be able to get back to more "stream of consciousness, spur of the moment" blogging! :)The topic of WebKit is not the easiest one. It's had its share ...24.01.2010 Lim Yuen Hoe (moofang): The Web, the Desktop, and the Google between I haven’t written a proper tech article since before I (re-)started this blog, so I thought it was high time. Besides, I’ve been wanting to write this post ever since I read some articles on Google’s Chrome OS, around the time right after my old blog vaporized. So there’s a couple of buzzwords to hopefully sucker you into clicking the ‘more’ button and actually reading the article – It’s about Google’s upcoming Chrome OS and it’s implications for the web, the desktop and the browser, as well as why desktop evolution can take an altern...20.12.2012 KDAB contributions to Qt 5.0 (part 1) Yesterday Qt 5.0.0 was released. It is the culmination of huge amounts of work since the announcement of and start of Qt 5′s development. This is the first major release of Qt since the launch of open governance in Autumn 2011, when it became much easier for external individuals and companies to contribute to Qt in terms of code submissions, code reviews, design, and maintenance. As KDAB benefits from a successful Qt, we have made investments to contribute to the long-term health of the frameworks. There are over 1100 commits from KDAB in the qtbase git repository alone, and many others ...02.08.2010 Aaron Seigo (aseigo): writing a plasma shell I'm a hobbyist writer of fiction and poetry, which is to say that I write for the purpose of enjoying the pleasure the activity itself brings and for little other purpose. Sometimes I'll go back and read something I wrote some time ago, perhaps years ago, maybe even a decade or more. Sometimes when doing so a fairly odd thing will happen: I'll suddenly realize something that I was trying to say, something which was quite plainly there in what I had written, but which I was blind to at the time of writing. I've heard similar experiences from other writers, and if you are a writer you may have e...11.01.2012 Architectures and ABIs detailed Yesterday I wrote about instruction set and ABI manuals. Today I’d like to go into details about the ABIs I listed there. This was done mostly as a summary for me: it’s tiresome to search for the information in the manuals, especially since some of the manuals are PDFs without links. For example, I never remember what is the order of the registers used in parameter passing on x86-64. So what you’ll find here is a listing of what I found interesting for when I might need to read or write assembly code.As a bonus for you, dear reader, I added a few words about each platform.Fir...24.10.2013 publishing content with bodega The other day I wrote about Bodega, an open market for digital content. It was impossible to get everything into one blog entry, however, as Bodega engages with people in three different ways: as consumers, as creators and as distributors. In that previous entry, I focused on what Bodega is to you when you are interacting with it as a consumer. Today we'll be exploring Bodega from the perspective of a content creator.Warehouses and StoresAs a creator, Bodega strives to empower you. Most of the digital content systems that currently exist have you give your content to a publisher then cont...