i think i'll just put a copy to clipboard button right below the ve and maf correction tables for you. i can't see any need to select/copy ranges for this use case.
i think i'll just put a copy to clipboard button right below the ve and maf correction tables for you. i can't see any need to select/copy ranges for this use case.
Hi Steveo:
Just been looking through a log and wondered on the best way to filter out erronous logs.
At 5500 rpm I let off the throttle and map drops to say 20 , afr hits 11.5 briefly due to the lag in the data log. I'm currently averaging this into my figures.
How would you filter that out, say every log should be with 10% TPS of the previous log? or only use logs within 10% of the target AFR ?
Mitch
Terminal_Crazy
'95 Z28 M6 -Just the odd mod.
'80 350 A3 C3 Corvette - recent addition.
noise like that is usually rejected or at least softened by your averaging if you have enough data.
if your analysis algorithm allows you to reject surrounding records you could just say reject all records within a few rows of map < 25 or something.
Just wanted to drop in here and say thanks again.
I compiled the latest version on linux. Seems to work fine, no issues to report as of now.
Haven't been doing much with the car because driving without 3rd and 4th gear puts a damper on things.
Got a new transmission in and ready to drive this thing!
1994 LT1/4L60E Formula
Thanks again for the great work Steveo and others that put in work. Still use it almost every time I drive the car. I wanted to add that I ended up getting the PLX DM-6 Touchscreen + SM-AFR Wideband combo kit. I used Pin D27 and Innovative config tab in EEHack. After fully warm it's only about 0.5 lower than gauge though at times dead on as far as I can tell. The WB gauge is more steady than on EE that changes more rapidly. Not complaining just talking. Why didn't I buy a WB a long time ago. Probably one of the most useful things I've installed but EEHack is by far the most useful. The WB really does let me see exactly where I need adjusting.
Had about 60 errors today while flashing during the write period but double checked the bin after this and it had written everything needed. I was sweating buckshot because I just bricked my last one last month due to the battery literally took a crap in the middle of a flash. I will be connecting the charger for now on. Thanks again for everything!
widebands usually reduce sample rate by averaging internally, while their analog outputs are real-time, but the average of the analog output should be similar to what the gauge displays (this is why eehack has a smoothing option for the wideband in its settings)...
Per our discussion in the trimalyzer thread, can you speculate why eehack isn't discarding trashed frames?
Am I correct to assume that's what's supposed to happen here in aldl_read_reply()?
Here are three adjacent frames from a log taken this morning. Note how knock count "jumps" in the middle. This one is actually pretty subtle but I've found frames like this where VSS will be 255mph and there are three or four trouble codes, MAF reading 400g/s, etc.Code:// look for bad checksum if(checksum_test() == false) { serial_error_occurred(); pkt_fail_counter++; return 0; }
frame-37168.png
frame-37169.png
frame-37170.png
This is by no means a huge problem, but I've been chasing my tail on false knock and the huge knock events these generate make it really hard to see the "real" false knock.
BTW, I have some patches I want to send you relevant to the knock scope that adds the timestamp to the tool tip bubble. Will try to push to git today.
Bookmarks