New Beta release 5.8.41 - Standalone Version

Synoptic

#1 โ—ˆ 2019-10-15

Ok, I may have fixed the TPS setting for logging to the file, but i'm not sure.
and I may have fixed the hanging in the logging too. See first post.

White_Teg

#2 โ—ˆ 2019-10-15

Didn't have much time to test, but the TPS setting woked fine. It was still hanging though. It seems to happen after 100-150 lines of logging. Is anyone else testing this, and if so are you having the same thing happen? Could this be a memory issue? If I have time tomorrow night, I'll boot my laptop with the bare minimum and see what happens.

Synoptic

#3 โ—ˆ 2019-10-15

No body tested the new .37 version ?

Synoptic

#4 โ—ˆ 2019-10-15

Common guys, tell me if the 5.7.37 works well or not !!

jonnyvtec

#5 โ—ˆ 2019-10-15

Ill try it 2moz for you. Ill have my wideband in too aswell so can directly compare the raw voltage readings.

White_Teg

#6 โ—ˆ 2019-10-15

OK, I just found out why logging is hanging. I had task manager up and noticed that ECU Control is using 95-100% of the processor while logging, and when the processor is maxed out for more than a second or two the logging hangs. If I raise the Log Int to 50 or higher it will only hang for a few lines every now and then. Is there anything I can do to fix this on my end or do I just have to use the slower settings? Don't know if it matters or not, but my laptop is a Celeron 2.6Ghz with 768Mb RAM.

Synoptic

#7 โ—ˆ 2019-10-15

hmm ithink i have maxed out the VB code then.

yah cpu usage is lame. I should code it in another language.

i dont get those hanging here. but besde the hanging, is it ok ?

White_Teg

#8 โ—ˆ 2019-10-15

It looks good. I can't verify the o2 voltage right now cuz I'm using the stock sensor, but it is consistant with the numbers using the stock sensor option. The VSS is about 1.5 times faster than actual speed(MPH), if I remember correctly it has been that way for a while though. If I ever get my WBO2 back I will be able to verify the voltage for ya.

Ltdannear

#9 โ—ˆ 2019-10-15

White_teg.

Sounds like you're reading KPH... Maybe there's a software setting you missed? Is the gauge set to MPH or KPH?
Should multiply the results by .61 to get MPH reading..

Synoptic

#10 โ—ˆ 2019-10-15

Dan, does your logger makes the CPU 100% ?

I just fixed the VSS bug and the Unit selection bug too. See first post.

on my side, ecucontrol doesnt hog the CPU..

P4 3.2 1GB RAM.

jonnyvtec

#11 โ—ˆ 2019-10-15

37 worked fine on mine in terms of showing raw volatage, was sat around 2.4 - 2.5 at idle which is perfect on my LC1. Logged fine to the table aswell.

Ltdannear

#12 โ—ˆ 2019-10-15

On a P4 centrino (1.6?) I see 30-50% CPU go to FreeLog.. 20megs memory allocated.

I don't have any log intervals, either... I log the data as fast as I can and handle the math between each interval. I see about 20ms average between intervals ( all 26 commands in one interval)

Synoptic

#13 โ—ˆ 2019-10-15

New Update 5.8.41.

White_Teg

#14 โ—ˆ 2019-10-15

The cleaned up code helped my CPU usage(only peaks at 90%), I guess that this is another reason for me to find a P4 to put in it :lol: . Logs great, VSS is still off for me(yes it is in MPH), shows about 1.4 times faster.
Here is a save of a run I did in 5th, I added a colum for actual MPH(calculated from RPM/gear ratio formula) and a colum for logged/actual MPH.

Synoptic

#15 โ—ˆ 2019-10-15

I need someone to tell me if the Speed in KPH is good or not.