It may not be shocking for Ford to see Open XC alterations to its Mustang line, but it is a new and interesting twist to an old tradition. The Mustang represents the whole history of the Ford company, in its most glamorous and fast-paced light. To bring that together with technology is a powerful thing.
I would still bet that there are lawyers at Ford that had to be shouted down or bypassed to get this one out the door. I would be very curious to see a description of the interface and exactly what data can be had from it. It may just be what is already available from the OBD-II interface that is already mandated on vehicles.
@Larry, exactly. The issue is what data can be exactly had from this interface. So...what sort of things are already available as "mandated" as you say form the OBD-II interface today, and what are not?
There are a set of generic codes which are published and additional codes that automotive manufacturers have held as proprietary. The proprietary codes are usually available to scanners by or under contract to the manufacturers and very expensive. The scanners that are buyable for reasonable cost at automotive stores have limited or no access to the proprietary codes. In my opinion, this is silly and eliminating that silliness would be a good step towards increased openness. Why is it that way? To give their repair shops an advantage in repair business.
@Larry, thank you. It's interesting and 'silly' as you say that they limit the access to code because they want to give an advantage to repair shops. Meanwhile, I thought it was for the sake of 'security' of a car. Have I been misled?
I've been servicing all my cars for the last 50 years. The OBD have certainly been useful for diagnosing engine sensor/system problems.
Unfortunately, you have to spend over $3,000, even on third party scanners, to get the useful brake and chassis scanners. After replacing all the brake lines on a 2006 Buick Lucerne, I discovered that you needed the expensive scan tool in order to bleed the ABS controller. Fortunately, I had a mechanic friend who dropped by with his and we bled the brakes. To the average backyard mechanic, this would require a tow, unless you want to drive to your friendly service emporium with no brakes. In my experience, the expensive scanner will also identify an intermittent wheel speed sensor. It's also necessary to diagnose transmission problems. It will also read your AC pressures among a host of other parameters.
The issue is the old charging what the market will bear. Let's face it, the added cost of a large enough flash to store all the additional codes wouldn't be more than 10% of the price of the cheap scanners.
Giving access to the car's buses will probably result in many inadvertent code changes, necessitating an expensive trip to the dealer to set things right by changing expensive modules - a great new profit center.
I'll be watching Ford closely to see if they end up with a serious hacking problem. This is a decision that has the capability of destroying the company. After all it would be viewed as a challenge to hackers around the world. Would you continue driving a Ford if suddenly they were going out of control and crashing all around you?
Hey Larry, the data available is listed here, through a link in the Ford-specific section: http://openxcplatform.com/hardware/vehicles.html and there is lots of information on the supported hardware interfaces (including open source hardware options): http://openxcplatform.com/vehicle-interface/hardware.html
@peplin, thanks much for the reference! It looks like they are in fact using the OBD interface but are documenting it more fully. I wish I would have had something like this for my Corvette. On that car and on my wife's Chrysler van my scanner only interprets the generic codes. It certainly doesn't provide programming information as does this site for the Mustang.
Great move from Ford. Only an american company could have been the first to do such a change in the global way of thinking. I hope the other car makers will follow. I also hope it will not be limited to the usual ODB Codes that everybody already know. It could be extended to diagnostic control codes, calibration procedures, options/extensions configuration and these stuff that remain closed today.
It is a great move but a lot of car lovers are already changing computer data to improve engine power and twist the performance of the car. In addition, if general public can start twisting performance of an engine w/o enough understanding, there might be concern to not only Ford Motor but also to the safety of road users.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.