TechOnline India Header
Most Popular
Top 5 Courses
  • Fundamentals of PCB Design
  • Paralleling DC-DC Converters
  • Fundamentals of x86 Architecture
  • Analog Devices' SHARC 32-Bit DSP
  • Analog eLab - Improved INA Input Filter
    Most Popular
    Top 5 Technical Papers
  • ARM Platform Technical Overview
  • Using C++ Efficiently in Embedded Applications
  • Top 10 Drivers for Embedded Android
    Most Popular
    Top 5 Webinars
  • Designing embedded HMIs and connecting them to hardware
  • 2009 Embedded Market Study
    All Articles Products Courses Papers VirtuaLabs Webinars
    Top Search Items
    C


    Techpaper Spotlight

    Wind River
    Accelerating the Development of Embedded Linux Devices with JTAG On-Chip Debugging
    /
        Login | Register | Welcome, Guest

    Topics
    POLL
    How much code have you produced in your career?
    A few KLOC
        38%
    100s of KLOC
        44%
    Millions of LOC
        11%
    A trillion
        7%
     



    Opinion: Computer overload threatens auto safety
    Automotive DesignLine

    As one who reviews lots of embedded software looking for safety issues, I have been intrigued by the Toyota recall, and am anxiously awaiting the verdict on the computer controlled throttle issue.

    Having been around nearly half a century, I have owned cars that ran the gamut when it comes to electronics. My first car contained NO computers and used the old tried-and-true point/condenser ignition.

    My second car had electronic ignition which I was wary of but came to appreciate for its 100-percent reliability and no parts needing replacement (GM's HEI ignition control did not contain an embedded computer however).

    My third car used a carburetor coupled to an early engine control computer (ECC) to lower emissions and increase efficiency. Engine sensor data processed by the computer resulted in a pulse train output to solenoids that moved needles in or out of the carburetor's "jets to richen/lean the mixture. It was a rather crude system by today's standards that had a fail-safe mode of fully retracting the needles from the jets in case of failure.

    In the 100,000-plus miles I drove that car, the computer entered fail safe only once, resulting in only slightly degraded drivability albeit worse gas mileage. That problem cleared itself after the car was shutdown and restarted. I never saw it again.

    My fourth car had an ECC coupled to fuel injection which made for optimum economy and easy starting in cold weather (the throttle still connected my foot to the butterfly valve in the intake system by a cable, though). In the 180,000 miles that I drove it, the ECC performed flawlessly, and was still going strong when I finally sold the car last year. That was a 1992 model, and it had only an ECC, no antilock brakes or other items requiring embedded computers.

    With the purchase of a 2008 Mustang GT, I have finally entered the age of computer-controlled "everything" in my automobile.

    I have to say that, as one who analyzes software for safety issues for a living, I do NOT like the concept.

    I think we have passed the point of ridiculousness in applying embedded computers to cars.

    Why use an embedded computer to control a conventional analog-style instrument panel, or a manually controlled heat and air conditioning system, or for electric windows and locks or, anything else that was available on a vehicle before the advent of computers?

    I think the ultimate in idiocy in this regard is the electric windows in new Mustangs. In my car, when one opens the door, the computer lowers the window about one-quarter of an inch before allowing the door to fully open, and keeps the window there until the door is fully closed, at which point the computer raises the window to its fully closed position.

    I understand why Ford does this, but we had frameless windows in the era before computers, and the windows sealed just fine. So why introduce more unneeded complexity and failure modes into the system now?

    1 | 2 NEXT >
     
     
    Latest Webinars
    · The Next Generation of Ethernet: How the New IEEE Standards Enable Energy Efficiency and Quality-of-Service
    · Simplified Physical Layer Receiver Test of Re-timed Architectures Such as USB 3.0, SATA, SAS, PCIe 2
    · How to solve the most common high-speed bus issues in embedded design on a budget
    · Early access to ARM Core Technology with Fast Models from ARM
    · Latest MIPI Standards: PHY and Protocol Testing Guidance
     
    Member Company Spotlight
    Silicon Integration Initiative (Si2)
     

    Read the latest white paper from Si2, "Using OpenAccess 2.1 as a Development Platform for New EDA Software". This paper discusses the issues, pros, cons and experiences in developing a new EDA company using OpenAccess database. View the paper here.


    Member Companies