×

Sale ends todayGet 30% off any course (excluding packages)

Ends in --- --- ---

Comparison between ECUs

General Tuning Discussion

Forum Posts

Courses

Blog

Tech Articles

Discuss all things tuning in this section. News, products, problems and results. 

= Resolved threads

Author
341 Views

How many times does a Haltech elite ecu update fuel and ignition calculations per second ? How fast is the main processor ? I want to compare it with other ECUs on the markets like Maxxecu as they say they have the fastest ecu on markets. Do these calculations affects on engine operation, response and how fast it is revving ?? If not, then what would be the effectiveness on ?

All of the modern ECUs are calculating plenty fast enough for quick engine response. Typically the calculations are done on at least a per cycle basis. Engines are really very slow compared to embedded computer processing speeds.

Thanks brother. So, what are they trying to refer to when they talk about the high speed of their processors? What is the real and tangible benefit?

Perhaps that gives them the capability to process more variable cams, or other closed-loop controls (4 DBW throttles anyone?). Maybe their processor can handle V10's at 20,000 RPMs. Maybe they can handle more CAN bus communications, more channels of data logging, execute more strategies like sequential gear box control, etc. But do you need that?

A faster processor, may allow it to do the normal processing quicker, so it spends more time idle (thus runs cooler).

I suggest you ask them what the benefit it, and why it should be important to you.

As David said, they can potentially process more information in the same amount of time. I say 'potentially' as the CPU is just part of the whole ECU device and, if the rest of the device isn't designed to support that potential, then the ECU may even be slower in actual operation than a more efficiently designed ECU with a slower processor.

As David also said, with most applications and ECUs, the processing to run engine is putting a relatively low demand on the processor, especially if the software is well written, but other tasks may benefit - even allowing two or even three CANBUS's to be supported, higher data acquisition rates, number of channels, or a combination of these.

It's more important you carefully review what you want from the ECU, what you don't want, and what it would be nice to have, when selecting the ECU. It's easy to end up paying a premium for something you may not actually need, when there may be a better fit that's even PnP with your current loom.

It's similar to sometimes when you see pre-built computers advertised as having a CPU that runs at **** speed, but when you look at the full spec'n it will have a lower amount of and/or slower clocked RAM, poor motherboard design, a slower hard-drive, etc. that may cripple the PC compared to a more balanced build with a slower CPU sold at the same price point.

Fast is relative and everything these days is more than 'fast' enough. Maxx and many (most?) other ECUs that are running ARM based processors run a discrete processor for crank positioning and timing and ancillary CPU(s) for less mission critical items. Some of the older guard it seems are holding on to Motorola CPUs but are also running discrete CPUs for the different tasks based on how how fast and accurate things need to be. Syvecs for example has 3 in their newer products but I'm not certain that the third is actually in use or if its still beta-y for custom applications.