appreciate the help btw
Printable View
appreciate the help btw
You have been using the tabs I have circled below havent you?
I need to test the O2 sensor feedback and PE vs RPM and see what happens.
I have a voltage I shoot for when tuning. If this works, tuning can get a lot easier. I have a bunch of techniques I have applied in the past that work, now if I can only automate them w/this technology.
I need to setup a CALC PID that should look something like:
(target_mv/02B1S1)+1. Will require >= 5200RPM and TPS=100%.
Gotta figure out how to include those filters and carefully choose coarse/fine adjustments.
THANKS FOR YOUR PREVIOUS HELP.
You would set up a CALC PID to calculate the O2 sensor variance and then use an RTACS filter to exclude the frames <= 5199 RPM and TPS <100.
The PIDs would look something like below. This averages the output of both O2 banks:
Add the 'target_mv' value with your specific value.Code:#==============================================================================
# Add slot definitions here
# --------------------------------
# See sae_generic.txt for more information on "SLOT" formats
#
#Units Low High Fmt Expression
#------------ ------------- ------------- ---- --------------------------------------------------------------
*CLC-01-900
mV 800.0 950.0 0.0 "({GM.HO2S11} + {GM.HO2S21})/2"
*CLC-01-901
factor 0.0 10.0 0.0 "({CALC.O2mV_AVG} / target_mv)
# ==============================================================================
*PRN - Parameter Reference Numbers
# --------------------------------
# See sae_generic.txt for more information on the *PRN section
#
#Code PRN SLOT Units System Description
#------------------------- ---- ------------ ---------------- ---------------- ------------------------------------------
CALC.O2mV_AVG F61C CLC-01-900 mV Fuel "NB O2 average millivolts"
CALC.O2_PEMULT F61C CLC-01-901 factor Fuel "NB O2 PE Factor"
I also added some additional images/clarification to post #8 in the event someone else has the same issues.
Glad you got everything working! :thumb_yello:
Excellent work on post 8. I'm sure somebody new to RR will find that useful along w/the other posts.
You read my mind. One minor problem is my o2 sensors run about 10mV off from each other, but thats ok as they do it consistently. To simplify the math, I can just use S1.
Since I am using LAMBDA in PE vs RPM, would this work also?
"{GM.HO2S11}/target_mv" effectively creating a BEN mult.
Now, about the cal_links.txt:
Is this going to work??
;P.E. Mode Commanded Fuel
B3618.ROW=SAE.RPM
B3618.RRR=CALC.PEMULT
Hopefully, if I only log RPM, TPS, O2S1, PEMULT I can speed up logging and use tighter filters for better resolution near the PE breakpoints.
I didn't get a manual, so I'm not sure about this.
Ah, the fun is in testing.
That would work, below is an example using the average of both banks in a single PID:
That looks correct for the cal_links.txt file.Code:# ==============================================================================
# Add slot definitions here
# --------------------------------
# See sae_generic.txt for more information on "SLOT" formats
#
#Units Low High Fmt Expression
#------------ ------------- ------------- ---- --------------------------------------------------------------
*CLC-01-900
factor 0.00 10.00 0.2 "((({GM.HO2S11} + {GM.HO2S21})/2) / target_mv)"
# ==============================================================================
*PRN - Parameter Reference Numbers
# --------------------------------
# See sae_generic.txt for more information on the *PRN section
#
#Code PRN SLOT Units System Description
#------------------------- ---- ------------ ---------------- ---------------- ------------------------------------------
CALC.O2_PEMULT F61C CLC-01-900 factor Fuel "NB O2 PE Factor"
405HP ZO6....I think you should be getting kickbacks from Moates and EFILive for all of the work your doing.
Well done and thanks.
Thanks Howard, I'm just trying to help out. Documentation is one of the most difficult pieces to create/maintain but is worth it's weight in gold if done correctly.
I'm trying to put together a document with all of the pertinent information required to install/use/tune with the RoadRunner. It's not fun bouncing around all over the place searching for information.