Hi guys,

I'm having a bit of an issue, my logs are not showing me the correct load values. I switched to the OMNI4Bar a couple weeks back and it worked great, it logged 1byte load no problem but now it spikes up to around 320 load and then it just completely drops and stays around 19-30 load for the rest of the RPM. Could it be that the sensor got a little lose or is it something with the software???

Thanks for the help guys

 

anybody

 

Did you max out 1 byte load? Are you using the "1 byte load factor" ?

If so, you may need to change it from whatever you get stock (1.2 or 1.3) and bump it to say 1.4. You need to make that change in both the rom *and* evoscan.

You may want to log 2 byte load just to verify that's what is happening, because you won't top out 2 byte load.

Check out this thread.

https://www.evolutionm.net/forums/ec...g-load-v7.html

 

Im pretty sure i wasnt, the load on ECuFlash was 1.2, I changed it to 1.4, the one on Evoscan was 1.3 I changed it to 1.4. My log was reading up to 330 no problems until recently. Btw since I changed the load factor is that going to affect my tune in anyway???? Like now the load will be lower or higher for the same cell?? let me know I really dont want to mess something up

thanks

 

Yes and no. Changing these values has no impact on what the computer is doing, so no the tune isn't different. It will still run now like it ran before.

Yes because you had mis-matched loads before. You had 1.2 on the rom and 1.3 in Evoscan, which means the load you saw in Evoscan was wrong. It would have displayed load values higher than they really were.

If you tuned using Evoscan as your logger and using 1 byte load as your load reference, your tune is off because your point of reference was wrong.

Now that they're both 1.4, what you log for load will be lower, but it will actually be accurate to what the real raw load is.

 

Thanks bud youve been a big help, I logged now and its perfect

 

Awesome! Glad to hear it