Slashdot Mirror
Japanese Auto Makers Teaming Up To Create Standard OS
CNet is reporting that Japanese car manufacturers are teaming up to develop a standard automotive operating system. "Just as computer operating systems [...] allow multiple applications to communicate with one another, an automotive operating system enables different driving systems to work together. The standard automotive operating system from Japan will include everything from fuel injection, brakes and power steering to power windows. Currently, certain mechanical car parts are interchangeable from model to model. Smart car parts that operate off a common software standard would enable that kind of convenience to continue, while allowing them to communicate more easily with other smart components in a car."
But will it run rinux?
According to another Yomiuri article, BMW, DaimlerChrysler and other European automakers are jointly developing a next-generation OS and are expected to complete a prototype in 2008. ...a year earlier.
Imagine a Beowulf cluster of those!
Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
Your car gets 1000 miles to a single tank of gas?
That's awesome.
Hey, maybe the American auto manufacturers will adopt Win-ICE for you. (FORD - Fix Or Reboot Daily).
"A government is a body of people, usually notably ungoverned." - Shepard Book Quoting Malcolm Reynolds
Hehe, that would be amusing... and neato at the same time actually. Who knows how many useful & dangerous apps could be made...
TRON is an embedded OS that Japan tried to use as a general-purpose desktop OS as well back in the late '80s, but was stopped from doing so by a Federal Government lawsuit claiming it was anti-competitive:
http://www.tron.org/index-e.html
Or is this an extension to TRON? (The article is really slim), though it seems to be about OSEK:
http://www.osek-vdx.org/
William
Sphinx of black quartz, judge my vow.
Microsoft has announced that it is partnering with a Japanese automaker to incorporate Windows Vista Auto Edition with all of their car systems.
In other news, family of 4 dies as their Japanese car careens off of a cliff after experiencing a BSOD in their Microsoft Windows Vista Auto Edition software.
And they said zombies weren't real!
"We don't want you tinkering with the cars you buy from us."
Wow, this is truly going to be revolutionary, allowing automakers to finally produce truly interchangable parts. [/sarcasm] Anybody else feel pretty certain they'll still change the shape and size and mounting locations on every single part every year so that there will still be almost no compatibility between models and years and so forth? What does this really buy us?
No, but it will run some sort of common OS, according to this article. Also, the reply to this post makes a good point.
"The wonderful thing about standards is that there are so many of them..."
-ubuntu others as you would have others ubuntu you.
Does this mean your car can get hacked? Wonder what the complications might be.
Can someone explain this article to me using a car analogy?
You seem to be under the illusion that your car doesn't already have one. Unless it was made before 1995 or so, it does. If it was made before 1995, it still might, depending on the make/model. It's not until you go back to about 1980 that you'll find a year where all cars had mechanical stuff instead of ECU's.
Basically, if your car has EFI, it has an OS. If it has a carburetor, maybe not.
It would bring a whole new meaning to "blue screen of death"
It is by the juice of the coffee bean that thoughts acquire speed, the teeth acquire stains. The stains become a warning
This topic sounds very interesting, but I just can't face this thread and the millions of "if Microsoft made cars" jokes that I'm sure are coming.
Prov 9:8 Do not rebuke mockers or they will hate you; rebuke the wise and they will love you.
I really hope they don't go the "OS for battleships" direction and just take a regular OS and tailor it for cars. An OS that is going to help operate a car should be built using signal logic and work like a low level state machine. Like this: http://www.rebelscience.org/Cosas/COSA.htm or at least build it around a functional lambda calculus based language like haskell or erlang (see wikipedia). The last thing we need is random segfaults while we're driving.
as an aside-- please don't critize my suggestion without at least first reading up on functional lambda calculus based programming languages and COSA.
Its already been done by others, hell even microsoft made some Windows CE modifications to make it automobile friendly. This is really only useful if they all actually USE the same protocols across the board. If everyone comes in and makes their own unique way of controlling each individual component it won't be real helpful.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
At one time i was afraid they should take some general purpose OS and cram into cars.
HTTP/1.1 400
Don't be so naive, Every production model of car for the past few years has an embedded operating system. Many people improperly compare their car's OS to that of Windows desktop. There's a major problem with that comparison though. The software is made specifically not to crash and to be fail proof at (almost) every conceivable pitfall it may encounter. A better comparison would be to medical devices to keep people alive. When lives hang in the balance, a little more attention is paid to the details.
Well, back to rejecting software patent applications.
A mechanical engineer, an electrical engineer, and a software engineer are driving along when they start heading downhill. The brakes go out, and as the passengers panic, the driver manages to just barely swing the car to safety, narrowly averting a short trip off of a tall cliff.
With the car stopped, the engineers all get out and discuss what must have gone wrong.
The mechanical engineer says "we must have lost a brake line or something."
The electrical engineer suggests there was a problem with the ABS system.
The software engineer suggests they all drive back up the hill and go back down to see if it happens again.
The Slashdotter tied up in the trunk mumbles "I, for one, eagerly await our new standard OS overlords."
Currently, certain mechanical car parts are interchangeable from model to model.
Currently? Back in my teens, in the 80s, I hung out with a family that built street machines. There used to be this company called GMC and it had others called Chevrolet and Pontiac, et al. We could take a bell housing off a 66 Pontiac whatever and fit it perfectly to a 68 Chevrolet whatever. ALL water thermostat housings between all of these makes were the same. I can remember helping my dad with his 69 Ford Bronco to replace a cracked thermostat housing, and when we went to the junkyard the dude pulls out a huge box of ford thermostat housings -- even between Ford cars they were different. You could fit a Nova front-end to a Ventura and all the bolts matched. Anyone toying around with American cars from the 60s learned to love the GMs, especially Chevys....
GMCs, and especially Chevys, from the 60s, were God's gift to cars and auto mechanics and it was all interchangeable. Couple this with the raw power of those cars (yes yes, environment concerns and all that) and those are some of the best memories of my life....
Hehe, currently.... Reminds me of my daughter saying, "way back in the 90s...."
"All great things are simple & expressed in a single word: freedom, justice, honor, duty, mercy, hope." --Churchill
No, I am not under that illusion, just because my car has an OS, doesn't mean I don't think it's a stupid idea.
34486853790
Connection too slow for X forwarding? Try "ssh -CX user@host"
I would bet this is more likely:
To prevent newer and compatible parts from working in older systems to force you to upgrade your whole vehicle.
Maybe they are catching on that we're catching on that all they offer from year to year are different cup holders, body panels, and paint jobs.
Ha ha, crash? Crash? Get it? I think I'll punch myself in the face so that I can sleep through the next few retards that respond with the same lame ass joke.
If we can get all the cars to use a common language, doing diagnostics could be made much easier. OBD2 that all cars sold in North America currently have, can be useful, but is quite limited in what it can do.
...only if there's a button on the steering wheel that transforms the car into a 20 foot tall battle robot. Or a sexbot. Or both. At the same time.
The Toyota Unicron. Yeah, yeah, gimme some of that.
Main competitor? The Kia GoBot.
Ha ha ha ha! Go-bots....
This will make chipping easier, the firmware in some cars is restricted for various reasons. Often it's a compromise of all the regulations for each country where it is sold.
I think you mean a RED screen of death...
My PC's motherboard maintains a constant voltage from the PSU and, indeed, the on-board battery.
I guess I need to disconnect the PSU and pop out the MB battery to reboot my pooter.
I *do* hope you're a girl (or gay and proud)...
Quack, quack.
The development of a standard operating system for cars is not exactly groundbreaking news. OSEK-VDX, a cooperation between German and french manufacturers, exists since 1995. AUTOSAR is a newer set of standards for automative software where European and American (Ford, GM) companies have teamed up. As mentioned in a previous post, first implementations of AUTOSAR are expected for 2008. Both OSEK and AUTOSAR are not operating systems itself, but standards and specifications (like POSIX and TRON, correct me if I am wrong). Actually I'd be surprised if there were not something similar already in use by Japanese manufacturers. As for TRON, I always thought it is used mostly in consumer electronis.
Thought almost ALL cars around the world used VxWorks for their embedded systems.
Japan has used the uTRON RTOS specification for ages. This can be though of as similar to a light-weight POSIX specification that allows code to be ported relatively easily across RTOSs that have uTRON interfaces. This makes it realtively simple to interface code at the task level.
Remember folks that cars these days are packed with CPUs and are really just networks on wheels.
This exercise is more about setting a standardised architecture and set of interfaces that allows better integration of more complex elements.
Engineering is the art of compromise.
An annoying side-effect of all the electronics in current cars is that it's become impossible to replace the sound system (or at least the head unit): all too often, the head unit is linked to the satnav display, and on more expensive cars, the stereo is a main interface element for the entire car (BMW iDrive and similar systems). Also, the HU is built into the dashboard, instead of being in a DIN slot.
This means you're stuck with the limited quality and features of the headunit, and adding things like an amplifier, CD changer, MP3 player and extra speakers (e.g. a subwoofer) are hard or impossible.
With a standard OS, it should be possible to separate the head unit from the rest of the car, and still use the HU to interface with the car.
True, but more like since the mid 80s, not just the past few years.
To extend your point... the article isn't about inventing the idea of an OS in your car, which has been around for a long time. What they're talking about is standardizing the various OSs that already exist. In the US today Chevy, Ford, etc all have computers in their cars that manage the engine, transmission, emissions, etc, but they're not interchangeable. If your Chevy ECU needs replacement you can't put a Ford ECU in. Same thing with sensors/parts that work with the ECU. Even within the same manufacturer you often need to match up the specific engine type, or even the specific engine year. All the article is talking about is coming up with a standard for the computers so that it's more convenient when repairing/upgrading the vehicles.
All of the "oh my god, my car running on windows?" jokes may be amusing, but that's obviously not what this is about.
Unix is user friendly, it's just selective about who its friends are.
This happened in Phoenix, Arizona.
Many years ago, when I was in college and poor, I bought a truly beat to death VW Baja for $800. It had tiny little wheels for drag racing for some odd reason, and great big sand wheels up front. The front end and the back end were fiberglass, with all the sheet metal cut off roughly with a torch; the front bumper was, I kid you not, the GAS TANK. I had to buy some new seat belts out of a wrecked beetle to bolt in because the originals had been cut out. The car sounded like a helicopter, you could barely hear yourself think. It had a souped-up 1800cc engine that was the greasiest, ugliest thing I'd ever seen in my life.
I really liked that car. It was fast as hell and totally terrifying to drive.
One time, my ex girlfriend tried to make fun of my car by flying past it in her mustang (over Camelback Mountain). I let her get just past me and I stomped on the gas; I flew past her and got the thing up over 100 mph before making the crest of the mountain (this was on the upward side, mind you).
Even better, one time I was sitting at a stoplight and this creepy ASU kid and his girlfriend were making fun of my car from their convertible. I looked over at them, and when the light turned green, stomped the accelerator and popped the clutch. The damn thing popped a wheelie and I almost had a heart attack. But it was worth it, the kid was so surprised he forgot to go and got cut off by traffic.
Still... I ended up selling it for the same 800 bucks to another college kid. He took it out in the desert, floored it, shot off the top of a sand dune, and obliterated the car. Amazingly, the kid survived and called me up to ask for his 800 bucks back! I said "what are you, nuts? Consider it a stupidity tax" and hung up.
Sigh... Poor car...
Obviously some kind of emoticon might have prevented your trollification <:o)
But what do I know, we seem to be entering an era of anti-anti-microsoft bashing...
--
Resistance is futile
Oh no, I know they're there....but, I'm just that comfortable with it frankly. I was a little weird on my Vette when they came out with the C5. The salesman was taunting that the accelerator was 'drive by wire'. Frankly, I'm just a bit more comfy with mechanical control...I know how computers can blow up and be buggy.
My car after that, was an '86 911 Turbo...not a lot of computer on that one, and I really enjoyed it. It just felt more connected to the road being more mechanical.
But, alas, those are the things of yesteryear. With the damned stringent emissions getting more and more tight, about the only way you can wring out decent power in a car is with computer management. I know that ABS helps you stop better, but, I can't stand the damned things. I'd much rather brake mechanically...I know how to adjust for slide, etc if I lock it up.
I don't like that so much computer control takes a lot of wind out someone wanting to become a real shade tree mechanic. It is difficult to do these days. Back in the day, a person could get some basic tools, and do mods to their own cars to get performance, etc. Now, well, you need a lot more equipment and knowledge than simple mechanical know-how, and it makes it difficult for the avg. Joe Sixpack to power up/customize his car.
But, since this is the way we're going...if they could make a common OS for the car, common non-propietary methods of component interaction, at least it would help it in todays world, for the new shade tree mechanic to be able to work on, mod and customize his car. If it were an open source type system...there could be a sourceforge type site for people to work on mods for cars. Download a module....and redo the powercurve and air/fuel mixture so you could get more power, and not be as restricted by factory environmental settings.
Light travels faster than sound. This is why some people appear bright until you hear them speak.........
Once these things start connecting to smart phones and laptops, and are thereby connected to the outside world... viruses!
I think a particularly funny one would be to lower the windows and make them unable to go up as long as the windshield wipers are on.
I think a particularly not funny one would be to somehow mess with the steering/breaking/stability systems to deliberately cause people to drive off the road.
I can see every major component being connected with a TCP/IP stack. Everyone can write whatever calls they want to be available & manufacturers could choose the ones they want.
However I can also see the case (of my 1996 Mitsubishi Eclipse spyder) that I can't get through inspection because it won't complete a drive cycle... (For example: I have to cold start, then drive at 60MPH without sloshing the fuel for the EVAP test. Considering I live in the middle of a city & have to drive 20min before hitting a highway where I can drive 60 - this is a problem...)
It is great that the software in cars will be standardized, but how about the driving experience.
I drive different rental cars every week and I am amazed at how dissimilar the controls are.
I suggest that the automakers, or our government, make the controls and indicators for:
gear shifter, emergency brake, lights, turn signals, wipers, speedometer, fuel gauge, pedals, gas cap, side mirrors, window controls, emergency flasher, panel dimmer, power locks and cruise control, standardized on all cars.
How many accidents have occurred because the driver was looking for or trying to use a control incorrectly.
machinator omnis sine licentia
I was hoping the headline was going to read "Flying Cars."
Well, then, Einstein, tell us how to run traction control, fuel injection, ABS, adaptive shifting, real-time diagnostics, etc., *without* an OS.
I suppose that you *could* hack it all together with discrete logic chips and the passives that accompany them, but your part count would be in the tens of thousands, which alone would cut your reliability. And you'd be accomplishing the same thing, you'd just do your "programming" in traces instead of C or assembly.
I dunno about you, but I'd rather debug C or assembly, then re-flash a new firmware than sit around with a scope and logic probe trying to figure out why things are bad, then produce an entirely new board. Maybe I'm crazy. Or, maybe that's the reason that virtually the entire electronics world has replaced discretes with microcontrollers any place that they can.
Oh, you're not stuck, you're just unable to let go of the onion rings.
Windows Automotive is Microsoft's entry into the car OS field. Its not XP or Vista based, but based on Windows CE, pretty much a totally different OS (intended for embedded use), only sharing the name Windows.
IMHO, its not too bad, Windows CE is maturing and is standing up well to the test of time, so Windows Automotive 5.0 shouldn't be as bad as people think. However, time will tell. Also, Windows Automotive doesn't appear to be for the critical controls of a car (if stuff is drive-by-wire), but more for powering and controlling the car's gadgets (radio, A/C.) For critical control of a vehicle, I'd much rather go with an embedded OS that has done its time in life safety areas(Green Hills Integrity RTOS for example)
Maybe this is something MS should look into (and I'm not being sardonic, as any research in this field where even a single bug can kill or cause tremendous damage is good research), making a version of Windows CE that is intended for safety applications.
There was talk a while back about Ford using embedded Windows for managing engine functions and other operational systems in the vehicle (with the exception of the most critical parts, although that was not clear from reports). I don't know if they actually decided to follow through with it, but if they did then that would be yet another blow to the quality of the American automobile against the Japaneses and European makes. It is probably better that they (the Japanese auto makers) are developing this OS fram scratch since neither Windows or Linux is really designed to be a real-time OS for critical applications (i.e. avionics and flight systems, engine management, and nuclear power plant controllers). Those systems which do exist in this arena tend to be highly specialized anyway so it probably doesn't make sense to try and adapt the avionics or flight control systems of airliners to managing an automobile engine.
So, if the OS is not free, then will that mean that RMS won't ride in these vehicles? I see a new GNU project on the horizon!
Let's play video games with mailmanZERO
As many have already pointed out, you car more that likely DOES have an embedded OS (unless of course it is pre mid 80's). Unlike a OS like windows/linux, the ones in vehicles have failsafes built in incase of failure. All the systems are programmed with a default setting, if a system fails, it reverts to default. My Acura Legend had a problem with the ABS. One of the sensors failed, so of course, ABS failed as well. Good news, it reverted to default programming (no ABS). Same with the fuel managment, traction control, braking, etc. All the systems still have a failsafe, and generally it involves a mechanical alternative. Abs fails, no ABS. Traction control fails, no traction control. Drive by wire accel failes, no accel. Entire system fails? Your car stalls, you throw it into neutral, and coast to the side of the road (PS, you breaks will still work, just have to push harder)
Oh yeah, not dangerous huh? Try googling for 'chrylser BCU headlights' or 'wipers'. The Body Control Computer goes bonkers and people lose their headlights/running lights and/or wipers, OR get really crazy, intermittant behaviour of these devices. If you don't think thats dangerous at night on wet roads...
Dealers do not like to replace these items because Chrysler cleverly put the odometer in there too. How hard it is to recode the odometer I don't know, its probably 4 bytes in a eeprom.
A better comparison is definitely NOT to a medical device.
They Live, We Sleep
Could I say that Linux powers my windows?
By law, they have to support OBD2 diagnostics; this spec provides a limited number of diagnostic indicators that (theoretically) can be accessed and interpreted the same on all vehicles. The OBD2 spec is even available - not officially, but Google is your friend.
So far so good - some standardization, albeit government enforced. But there's more; there's a lot more useful diagnostic information available from the vehicle systems than OBD2 shows. So the manufacturers extend the protocol and define other trouble codes and ways of accessing them. These extensions aren't documented, and they're often designed to be as obscure and impenetrable as possible. Every manufacturer has different proprietary extensions and they change them at whim.
The dealership service departments have the dedicated computer that talks to that manufacturer's cars; it knows all the codes. But independent service shops don't have those dedicated machines or any information about how to read the extended codes from a vehicle. The manufacturers refuse to provide any information to anyone at any price; you can't even buy the diagnostic machine from them unless you're one of their dealers.
They've been doing this for years; various lawsuits have come and gone but the manufacturers still won't share the information that mechanics need to service their cars effectively. The manufacturers like it this way; it drives more business to the dealership service departments and prevents third-party parts companies from making less-expensive replacement parts. This is the status quo; even the Japanese manufacturers play the same game.
So let's consider the possibility of a standardized automotive operating system or architecture. Would the manufacturers use it? If it offered greater reliability or reduced build costs they'd go for it. But before it hit the dealers they'd "fix" it so that their parts and service divisions would continue to enjoy their competitive advantages...
When it was discovered that some Chevy built engines were put into Cadillacs they sued the hell out of GM.
Just because it has a microprocessor and is programmed in c or assembler doesn't mean it
needs an OS, lots of embedded systems run just fine without.
A friend of mine build and sell an ECU that has no OS, it programmed entirely in assembler, it does ignition, injection, drive by wire, cruise control, traction control, turbo antilag and much more, dashboard etc. via CAN.
Everything is done with hardware timers, interrupts and a main loop
-L
Why does every potential problem have to have a "government enforced" solution? Why not have some personal responsibility for your own actions instead? Are you that stupid that the government has to make each and every decision for you so you don't hurt yourself?
Creative Demolition
I'm a mechanic by hobby and an IT guy by trade. I don't want those two to combine. Besides, do we really need more shit to worry about under the hood?
The game.
http://www.fia.com/resources/documents/198095623__ 05_07_2006_wmsc_decisions.pdf
... Hmm - I think that last paragraph might already be covered, no?
PRESS RELEASE
WORLD MOTOR SPORT COUNCIL
The World Motor Sport Council met in Paris on July 5, 2006. The following decisions were taken:
FORMULA ONE WORLD CHAMPIONSHIP
Bridgestone has been selected as the official tyre supplier to the FIA Formula One World
Championship in 2008, 2009 and 2010*.
Microsoft MES has been selected as the official ECU supplier to the FIA Formula One World
Championship in 2008, 2009 and 2010.
Due to a significant increase in cornering speeds in Formula One this season, the World Motor
Sport Council agreed to consult with the Formula One Technical Working Group regarding possible
measures to slow the cars.
For those of us that happen to be happy with the stereo that came with the car, the upside is no more having to take the thing apart and hide it every time you leave the car somewhere and no more smashed windows and some wires hanging out of your dash when you come back to it...
I, for one, welcome our new fully integrated un-steal-able car stereo overlords!
My coworker recently had an issue with a brand new Jeep. His wife was driving it only at about 5 mph and the brakes suddenly locked up. The brake pedal flew forward and would not press/release. Pushing the clutch down made the car roll backward. Fortunately the emergency brake was still working. After about a minute, the brakes reset and were functional again.
So a word of caution, the engineering isn't always perfect so don't rely on the system defaulting to a "good" mode.
As an experienced automotive embedded software engineer, I can say for sure this OS standard will bring nothing to the industry that isn't already in place. There are extensive standards for diagnostics, operating systems, safety systems, and pretty much everything else you can think of. I think the enthusiastic nature of many of the replies to this thread is an indication of a larger problem with how the US automakers are portrayed. Most people assume that it's good simply because the Japanese are doing it. Had a US automaker come out with this announcement, they would have be destroyed for being so far behind. Over and over again the media gives the Japanese and Europeans credit for technologies/strategies that have been in place for years. While they do bring a great deal of new technology to the table, no one gives US automakers credit for their contributions. For example, those of you BMW drivers (me included), your transmissions are most likely GM hydra-matics (http://prnewswire.co.uk/cgi/news/release?id=21160 ). BMW also has widely used Chrysler developed engines in the past (http://en.wikipedia.org/wiki/Tritec_engine). Mercedes drivers might be interested to learn that Mercedes does not even have an engine software department. Nearly 100% of this task is outsourced to Bosch, who supplies the same software to numerous other auto manufacturers (as well as the electronics to go with it). This trend of sharing and partnerships is present all throughout the industry and the framework for interchangeably sharing software has existed for years. In short there is really no technology gap from one auto manufacturer to the next (the exception being hybrid development at Toyota and fuel cells at GM). Everyone is buying the same systems from the same suppliers.
The quality difference comes from US executives looking to increase the per vehicle margin by saving 5 cents here and 10 cents there at the cost of long term quality. In fact most of you would be interested to know that your 2007 Toyotas have powertrain electronics technology dating back to 1997. This is not a bad thing as it leads to high reliability, but don't be fooled into thinking that something is high tech just because it is Japanese. The bottom line is that whether its BMW, Toyota, GM, Ford, etc...most vehicles share many of the same parts and it's the cost reduction mindset of US executives that leads to the quality differentiation.
That would be terrible. ODB2 is based on CAN which was designed specifically for cars. Replacing CAN with a less rugged, higher latency, master/slave layer like USB would be dumb.
Perhaps you could put some more smarts into each car talking to the components under the hood via CAN and then have it spit out a detailed message over USB or even print it on an LCD. But then your adding cost and have to decide how much it's really worth.
Really, why would different manufacturers want to make things more interoperable? This would in the long run reduce the need to buy particular brands, especially for repair parts, and cut into thir bottom lines.
---- Booth was a patriot ----
Sounds like brake assist, could she have done something that made the computer think she was doing an emergency stop?
It's not a bug, it's a feature...
Attack its weak point for massive damage!
100% mechanical ABS has been around since at least the early 30s in aircraft, and the late 60s Austins had mechanical ABS as well.
Adaptive shifting? Continuously Variable Transmissions have been around since the late 1800s, extensively used in power generation in planes, and I think in Volvos since the 1950s.
Real time diagnostics? See through fuel filters and flow indicators are de riguer in many racing/drag circles, since many restrict the use of electronics.
Now, I agree that it CAN be easier with an OS to do many things, but that doesn't mean it can't be done, and has not been done reliably, affordably, and efficiently in the past without an OS. And no, it's not troubleshooting a board full of PLDs or discretes; it's looking at a set of belts, gears, valves, and springs, most of which are pretty easy to see the status of with a quick visual inspection.
And for the record, I much prefer working on my 1963 Mercury Comet with the original numbers-matching 260 V8 and Merc-O-Matic tranny than servicing my 1999 Ranger or 2002 Taurus. The old Merc can have just about anything fixed with your choice of a flat blade screwdriver, cresent wrench, or hammer...:)
Browsing at +1 - no ACs, I ignore their posts. So refreshing!
I've never been in an accident, I take responsibility for my actions, and I take exception to being called stupid, by some self-proclaimed NEO-"pathological-techno-fetishist-with-social-def icit", who probably doesn't have anything more than a driver's permit.
If a majority of the population sees the value in such a proposition, and convinces their administration to create driver UI standards, than this is probably for the greater good. Whereas you would probably apply your anarchistic rant to driving on the same side of the road as everyone else.
machinator omnis sine licentia
You can't even compare it to embedded Linux -- which is generally rock-solid and capable of running in almost anything -- because Linux is not real-time. (Neither is Windows or OS X or BSD, by the way.)
I mean, sure, there are plenty of so-called "real-time" applications that these OSes work perfectly well for. Audio, for instance -- Protools, Ardour, etc. But it's a bit like Java -- while on average, you know how long something is going to take to process, you don't have any guarantees. (In Java's case, the garbage collector might decide to run at exactly the moment you need something important to happen.)
"real-time" means that you can actually guarantee, often with mathematical proofs, that a given thing will happen by a given deadline, and usually the deadlines are much shorter than anything a modern desktop OS can handle. It means you can say things like "If the sensor reads foo, I need a shutdown command sent to the nuclear reactor within 20 milliseconds." Done properly, you can actually guarantee beyond a shadow of a doubt that this will happen -- and in 20 milliseconds, not 21. On a desktop OS, there's just no guarantee -- for all you know, a filesystem driver, of all things, could lock the whole IO system up for half a second.
That's not to say that you can't make Linux realtime -- there are projects to do so. It's also not to say that you can't build a desktop out of a realtime OS. But right now, as far as I know, there are no real-time OSes which are used for anything other than embedded apps which actually need the real-time capability.
Don't thank God, thank a doctor!
Understand, there's software and then there's software. There is actually a company which specializes in test-driven development to the point where they actually will develop a product in the same amount of time, but charge twice as much for it, because there will be NO bugs (or "defects") at release. Other companies would spend half their time developing, and the other half testing and squashing bugs, and there would still be a dozen bugs there.
So, the level of software that will be directly controlling the car will be pretty much un-crackable.
Now, the smart phones and laptops, maybe, but those won't be connected directly to steering and such. As much as everyone wants to have the James Bond car, which you can drive by remote control, I'm fairly sure auto manufacturers have thought of what you just did, and really, really don't want to be held liable for that kind of bullshit. So basically, no James Bond cars until the industry as a whole moves to that level of stability and security.
Don't thank God, thank a doctor!
In Soviet Russia car networks YOU!
My car may have an OS. I want it to play nice with my other OSes. All I want is a USB port next to the ignition that I can plug my laptop into. I want the car to then tell me exactly WTF is wrong with it, how to fix it (with pictures), what parts to order, etc. If it's too difficult I'll take it to the shop.
In years past I had talks with Ford to develop a new operating system for all Ford vehicles, but it didn't work out. At the same time, Ford had their own project exploring a vehicle based on interchangeable components, which is just as stillborn.
The sad truth of the matter is major players have no interest in competition-enabling standards. In fact it's a little surprising that Japan is considering it, considering the massive vested interests of their own. Dynamic change like this is going to be driven by the Yugos and Hyundai's of the world, if nothing but for the simple fact that they have the least to lose.
Tart!
:)
Quack, quack.
So, I'm sorry, but your desire to tweak your car comes a very distant second to my desire to have safer air.
Any sufficiently advanced technology is indistinguishable from a rigged demo
--Andy Finkel (J. Klass?)
a Beowulf cluster of this ?
{{.sig}}
You say its vanished? Then why are auto parts stores one of the fastest growing industries and they are putting stores on nearly every street corner?
Agreed, actual shops that do the repair for you are dwindling, but are being replaced by DIY parts stores.
Personally i think its partly the economy: People have less cash so are forced do more things themselves more instead of taking it to a repair center, but that's just a guess.
---- Booth was a patriot ----
Another AC post, I should have stopped reading at 'Coward'. My karma is already 'Excellent' according to the website here, I don't have a need for karma. My intent was a subtle bash at Microsoft.
I didn't expect my post to be modded funny honestly, but what pissed me off was that the obviously offtopic, admittedly creative post about how my post wasn't funny got modded up...
*shrug* I still don't give a shit, but if you're going to criticize, have the balls to post as yourself. Posting anything as an AC is the same as karma whoring in my opinion... too afraid that you might lose precious karma points at yet another offtopic post.
And they said zombies weren't real!
lucky for you its 2017 ;) the computer's clocks can't handle dates past Jan 1st, 2018 ;)
hang in there bro!!!!!!!!!!!!!1