Author Topic: What uC to use in Automotive application  (Read 22814 times)

0 Members and 2 Guests are viewing this topic.

Offline nctnico

  • Super Contributor
  • ***
  • Posts: 27886
  • Country: nl
    • NCT Developments
Re: What uC to use in Automotive application
« Reply #50 on: July 07, 2012, 03:09:17 pm »
In many cases the diagnostic error code of a car tells absolutely nothing about the real problem!

A few weeks I ago my car wouldn't start. The diagnostics said that the fuel injection timing valve needed to be replaced. In reality the timing belt was broken. If the ECU had more horsepower it could be made smart enough to see the injection pump wasn't rotating but the camshaft was so it could say something about the timing belt. That would have been a meaningfull error.
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Offline yyrkoon

  • Newbie
  • Posts: 6
Re: What uC to use in Automotive application
« Reply #51 on: August 23, 2012, 03:55:09 am »
ARM is consumer/high volume stuff. I'm not saying it's bad. Just not designed specifically for automotive.

http://www.ti.com/lsds/ti/arm/hercules_arm_cortex_r_safety_microcontrollers/overview.page

No hands on or personal experience with it. But they are being touted as safety MCU's. Have some experience with the Stellaris Cortex M3 line. Which is buggy. Though the more I look at the C2000 line, the more I like. A piccolo seems like it could handle the job easily. Would it last though ? No idea.
 

Online NiHaoMike

  • Super Contributor
  • ***
  • Posts: 9205
  • Country: us
  • "Don't turn it on - Take it apart!"
    • Facebook Page
Re: What uC to use in Automotive application
« Reply #52 on: August 24, 2012, 02:48:14 am »
In many cases the diagnostic error code of a car tells absolutely nothing about the real problem!

A few weeks I ago my car wouldn't start. The diagnostics said that the fuel injection timing valve needed to be replaced. In reality the timing belt was broken. If the ECU had more horsepower it could be made smart enough to see the injection pump wasn't rotating but the camshaft was so it could say something about the timing belt. That would have been a meaningfull error.
Wouldn't a broken timing belt prevent the camshaft from turning?
Cryptocurrency has taught me to love math and at the same time be baffled by it.

Cryptocurrency lesson 0: Altcoins and Bitcoin are not the same thing.
 

Offline poorchava

  • Super Contributor
  • ***
  • Posts: 1673
  • Country: pl
  • Troll Cave Electronics!
Re: What uC to use in Automotive application
« Reply #53 on: August 24, 2012, 06:21:39 am »
Timing belts most of the times function well and then suddenly they tear break causing massive damage to valves and pistons, because everything loses synchronisation and pistons hit valves when they are open. Some engines are engineered in such way that this is not possible (eg. GM\Opel\Vauxhall\Holden C20NE).

But such failures that the belt doesn't break completly, but rather stretch are also found. it causes marginal timing change, but i guess if it was en extreme case it could affect vehicle performance.

Timing belt can also get damaged if one pulley or another breaks and belt can touch some static surface (eg waterpump or engine block). It becomes thinner and thinner and in the end will break prematurely.

such things happen, but a tech with 3 month of experience probably won't know that and will only rely on what diagnostic interface says.
I love the smell of FR4 in the morning!
 

Offline T4P

  • Super Contributor
  • ***
  • Posts: 3697
  • Country: sg
    • T4P
Re: What uC to use in Automotive application
« Reply #54 on: August 24, 2012, 12:11:52 pm »
Always trust your eyes! Not your diagnostics ...
 

Offline SeanB

  • Super Contributor
  • ***
  • Posts: 16362
  • Country: za
Re: What uC to use in Automotive application
« Reply #55 on: August 24, 2012, 03:41:54 pm »
Mine said Idle adaptation was outside normal range. Solution? Change the fuel filter, as it was restricted.
 

Offline nctnico

  • Super Contributor
  • ***
  • Posts: 27886
  • Country: nl
    • NCT Developments
Re: What uC to use in Automotive application
« Reply #56 on: August 26, 2012, 09:36:18 pm »
In many cases the diagnostic error code of a car tells absolutely nothing about the real problem!

A few weeks I ago my car wouldn't start. The diagnostics said that the fuel injection timing valve needed to be replaced. In reality the timing belt was broken. If the ECU had more horsepower it could be made smart enough to see the injection pump wasn't rotating but the camshaft was so it could say something about the timing belt. That would have been a meaningfull error.
Wouldn't a broken timing belt prevent the camshaft from turning?
Yes (ofcourse  ;) ). But my engine has a rotation sensor on the injection pump (which is also driven by the timing belt) and the crankshaft. The engine even runs fine if only one of these two sensors is working. It would have been a small effort to check whether the sensors are connected and point into the direction of the timing belt and not a very expensive part (€ 400) which almost never goes bad. Anyway, the engine in my car has been engineered to sacrifice the rocker in case the timing belt breaks. Replacing the belt and a rocker fixed it without having to remove the cylinder head.
« Last Edit: August 26, 2012, 09:37:51 pm by nctnico »
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf