Clock speeds of any/all boxes**.
-
MatthewArrat
Clock speeds of any/all boxes**.
What would happen if someone intentionally overclocked an EEC-V processor to double its stock clock speed? Would it unlock hidden performance potential, or would it just fry the ECU and leave you stranded with a bricked car? Has anyone ever tried this, and if so, what were the results?
-
Luis5.oh
- Posts: 68
- Joined: 2021 Mar 30, 12:27
- Location: Culiacan, Sinaloa, Mexico
- Vehicle Information: ---------------------------------------
*1995 Mustang GT - U4P0 - CBAZA
-95 Cobra manifold
-Siemens Deka 80's
-Explorer 4R70W (95 Mustang TCC Solenoid)
-Saleen racecraft lowering springs
-Moates quarterhorse
---------------------------------------
*2003 CTS base
-LS swap
---------------------------------------
*2008 Mustang GT
-Coyote Swap
Re: Clock speeds of any/all boxes**.
I think it does many things based on the speed and overclocking it would make everything a mess.
-
decipha
- Posts: 6471
- Joined: 2021 Feb 15, 12:23
- Location: Metairie, LA
- Vehicle Information: Work Truck
'25 F-150 5L
Re: Clock speeds of any/all boxes**.
everything is time based but its easy enough to update the timer table
no benefit as the clock speed far exceeds whats needed
no benefit as the clock speed far exceeds whats needed
-
wwhite
- Posts: 413
- Joined: 2021 Feb 16, 15:53
- Location: Victoria, BC, Canada
- Vehicle Information: 1994 Flarside, XLT, 351w E4OD
SD48b, Quarter Horse, Burn2
Re: Clock speeds of any/all boxes**.
Doubling wouldn't work, the memory chips and other chip components on the board need to sync, going too fast you get erroneous data.
Heat is the problem with overclocking, a couple Mhz maybe, not doubling.
Zero benefit unless you need to go 10-20,000rpm, lol.
Heat is the problem with overclocking, a couple Mhz maybe, not doubling.
Zero benefit unless you need to go 10-20,000rpm, lol.
-
tvrfan
- Posts: 130
- Joined: 2023 Oct 22, 22:13
- Location: New Zealand
- Vehicle Information: Several Kit cars, Ford (Europe), EEC-IV, TVR Vixen, Tasmin (a.k.a Wedge),
Engine - Cologne 2.8 V6 (Europe) catch code 'AA'.
EEC_Disassembler https://github.com/tvrfan/EEC-IV-disassembler
Re: Clock speeds of any/all boxes**.
(as Decipha says)
From what I understand, if you could overclock it hardware-wise, for software/code you would only have to change a few fixed params to get timing to work right. Every bin has to convert CPU I/O Ticks (main clock/16 or 28 for 8065...or something like that) to milliseconds. Code (almost) always uses a 32 bit long divide. Once this is done, I think everything would work ? Not entirely sure.
Hardware is the limit I reckon (as already said).
Also not if there is some stuff driven directly from clock or IO ticks though, probably RAM, any special chips, etc. but it's all Hardware.
Also overclocking would produce more heat, and so there is probably a risk you would fry something.
I don't think it would improve anything engine-wise. In CPU terms (even the old ones), there's about 2 weeks elapsed between each spark.
From what I understand, if you could overclock it hardware-wise, for software/code you would only have to change a few fixed params to get timing to work right. Every bin has to convert CPU I/O Ticks (main clock/16 or 28 for 8065...or something like that) to milliseconds. Code (almost) always uses a 32 bit long divide. Once this is done, I think everything would work ? Not entirely sure.
Hardware is the limit I reckon (as already said).
Also not if there is some stuff driven directly from clock or IO ticks though, probably RAM, any special chips, etc. but it's all Hardware.
Also overclocking would produce more heat, and so there is probably a risk you would fry something.
I don't think it would improve anything engine-wise. In CPU terms (even the old ones), there's about 2 weeks elapsed between each spark.