When reporting any s300 problems, please include:
- the calibration (as an attachment) - Attached
- a datalog of a problem (as an attachment) - N/A
- what sort of vehicle you have - 91 CRX B18c1 mostly stock
- what sort of ECU you are using - P06
- anything about the car which has been modified from stock which may affect the ECU (don't include what sort of rims you have nor stereo etc). - Lambda logging via AEM EUGO on D10 ELD.
- a specific description of the problem:
As subject states, Options\Settings\Sensor Overlay does not work if throttle condition are set to anything other than 0% (currently set to 0-120%, and working).
Problem has been evident on version 1.4.4.1 and 1.4.5 that I can remember, however I thought I saw this working in the past. It could be my setup, but who knows. I thought a new version would fix it and it didn't, so I decided to make a post. I'll try a different laptop tomorrow.
Sensor Overlay 1 not working when condition <> 0% thtl
Sensor Overlay 1 not working when condition <> 0% thtl
You do not have the required permissions to view the files attached to this post.
Sensor overlay not working when condition <>0 thrtl (u
Update:
First, thanks "spunkster," "hondata," Doug, and whoever always responds to my posts. In one night I have 30 views on a minuscule post about a lambda overlay issue with a prompt response from "hondata", so I know two things:
1.) You have good visibility external to your company.
2.) You have good response time on questions in the forum.
I'm curious, so who is it that I'm talking to most of the time?
Real update:
Two (cold-engine) datalogs attached but I doubt they'd provide as much insight as the following (run on) sentence:
I just datalogged a few seconds showing working and non-working lambda overlay as described above, however, I noticed datalogging is working fine regardless, and it's whenever I change the setting throttle condition back to 0 that I gain visibility to what lambda overlay I've logged.
For example, in my two attachments, I've logged one with 0-120% throttle condition for lambda overlay prerequisite and one with 3-120%, and as I suspected the 0-120 showed overlay values and 3-120 did not. *What's interesting is that when I loaded EITHER datalog I could not see the overlay values if I changed Options\Settings\Lambda Overlay\throttle min >0, but I could see BOTH datalogs (with respective condition's met) if I changed throttle min back to 0.
I hope this helps. Also, I tried this on an additional laptop with older OS and older version of Smanager and same issue. (XP + 1.4.2.0 vs yesterday's post with Win7 Ultimate + 1.4.5.0 and 1.4.4.1).
As always, thanks.
Mike
Green Bay, WI
First, thanks "spunkster," "hondata," Doug, and whoever always responds to my posts. In one night I have 30 views on a minuscule post about a lambda overlay issue with a prompt response from "hondata", so I know two things:
1.) You have good visibility external to your company.
2.) You have good response time on questions in the forum.
I'm curious, so who is it that I'm talking to most of the time?
Real update:
Two (cold-engine) datalogs attached but I doubt they'd provide as much insight as the following (run on) sentence:
I just datalogged a few seconds showing working and non-working lambda overlay as described above, however, I noticed datalogging is working fine regardless, and it's whenever I change the setting throttle condition back to 0 that I gain visibility to what lambda overlay I've logged.
For example, in my two attachments, I've logged one with 0-120% throttle condition for lambda overlay prerequisite and one with 3-120%, and as I suspected the 0-120 showed overlay values and 3-120 did not. *What's interesting is that when I loaded EITHER datalog I could not see the overlay values if I changed Options\Settings\Lambda Overlay\throttle min >0, but I could see BOTH datalogs (with respective condition's met) if I changed throttle min back to 0.
I hope this helps. Also, I tried this on an additional laptop with older OS and older version of Smanager and same issue. (XP + 1.4.2.0 vs yesterday's post with Win7 Ultimate + 1.4.5.0 and 1.4.4.1).
As always, thanks.
Mike
Green Bay, WI
You do not have the required permissions to view the files attached to this post.
It will graph with a minimum throttle of 0%. If will not show anything with a minimum throttle of 3%, because there is a 'transition delay' (default 1 second) which allows the lambda to settle after any of the conditions is met. If you drive for a shirt distance with a throttle constantly over 3% it will work for you.
Hondata
Sure as shit, I'm an idiot. I forgot about the transition delay.Hondata wrote:It will graph with a minimum throttle of 0%. If will not show anything with a minimum throttle of 3%, because there is a 'transition delay' (default 1 second) which allows the lambda to settle after any of the conditions is met. If you drive for a shirt distance with a throttle constantly over 3% it will work for you.
Thanks for looking into.
Mike