I know that my computers and smartphones require a periodic reboot to function properly.
Are all the computers in cars designed to reboot at startup? I know that the clock keeps running even when the car is turned off, I hope that the designers will resist the temptation to include the clock as an application running within a larger CPU that then runs without ever rebooting.
Meanwhile is there any evidence that cars which run for very long times without powering off (being improperly refueled on long trips with the engine running) encounter computer problems? What steps are automotive engineers taking to prevent computer glitches in cars (certain brands certainly have reputations for unexpected electrical system problems - to date in non-mission critical areas).
WRT the configurable displays, analog is in at the moment. There was a time in the early 80's when novel digital dislays were the craze. But even though displays are largely digital, most are equipped with analog gauges. And I must admit that they are easier to decode with a quick glance... Expectations are high (at least for me) for the level of sophistication in autos these days, given the level of sophistication in every other areas (laptops, mobile phones, cameras, etc.)
Automobiles are turining themselves into an entertainment homes with complete electronic devices and controls. Even the engine controls and the brake controls are already gone elctronic. If LED's can be used as alternatives for the head light, large power savings. But can it be done?
The modern automobile is turning into a rolling touchscreen tablet, complete with in-dash apps! Because of concerns over keeping hackers from penetrating automotive systems, special security algorithms are in place to make sure apps perform as advertised. But what I think is most cool about advanced automotive processors is the possibility of reconfigurable instrument panels, for instance allowing you to put the tachometer front-and-center if that's the way you like it.
A Book For All Reasons Bernard Cole1 Comment Robert Oshana's recent book "Software Engineering for Embedded Systems (Newnes/Elsevier)," written and edited with Mark Kraeling, is a 'book for all reasons.' At almost 1,200 pages, it ...