1BYTE load going from 330 to 20? Logging rate Hz?
1BYTE load going from 330 to 20? Logging rate Hz?
I know there is some multiplication factor in Evoscan and EcuFlash to change the load calc. I don't remember where the thread is that explains how to fix this... I couldn't find it. Can someone tell me how I can keep my load from resetting back at zero after I've gone "off the top?" I'm hitting a 1 byte load of 360-370, but it's resetting after 330 load. Moderately annoying, but I'd like to fix it.
Also,
what dictates my maximum logging rate? I'm currently logging at approximately 200ms (5Hz) which is QUITE SLOW. I'm buying a new computer now and I need to know what I should "load up" on.
RAM? Processor Speed? Hard Drive memory?
Thanks in advance!
-Eric Urness
Also,
what dictates my maximum logging rate? I'm currently logging at approximately 200ms (5Hz) which is QUITE SLOW. I'm buying a new computer now and I need to know what I should "load up" on.
RAM? Processor Speed? Hard Drive memory?
Thanks in advance!
-Eric Urness
Processor and then RAM (but only if you don't have enough)
Change your 1 byte load factor from 1.3 to 1.4 in both the rom and evoscan. This will get you up to 357 load (255 * 1.4)
http://evoecu.logic.net/wiki/TephraMod#1_Byte_Load
and 1000x in all of the tephramod threads
Change your 1 byte load factor from 1.3 to 1.4 in both the rom and evoscan. This will get you up to 357 load (255 * 1.4)
http://evoecu.logic.net/wiki/TephraMod#1_Byte_Load
and 1000x in all of the tephramod threads
As explained in the link, this is a scaled version of the load value.
Each logged item carries a value 0-255. You multiply by your scaling factor (1.4) to get the extrapolated value.
Ergo, your resolution will be in increments of 1.4 load units.
Each logged item carries a value 0-255. You multiply by your scaling factor (1.4) to get the extrapolated value.
Ergo, your resolution will be in increments of 1.4 load units.
Thread
Thread Starter
Forum
Replies
Last Post
roger smith
ECU Flash
11
Aug 31, 2009 10:07 PM




