finnigan001

Check out the how tos. Lots of great info. It’s where we all started years ago. wiring in a wide band isn’t the hardest thing in the world. But if you’ve not done any auto electrical stuff. Before there is a steep learning curve. You can’t wire the wideband into the ecu. You have to have an external gauge. You either need to weld a second bung or replace the narrow band with the wideband o2 and wire a narrowband output to the 02 input to the ecu. The second option is more complicated and unreliable in my experience. pcmtec can take the wideband info via the DLP anologue converter. You’ll have to purchase and read up on that too. You’ve got a steep learning curve ahead. Welcome aboard, it’s a worth while journey

can you screenshot and post up both requestor tables? spark requestor and other cuts tables. just to see if the spark value may still be doing all the lifting and not allowing use of the other cuts.

hey mate, From the article below: "Or we can disable enleanment/enrichment during traction control entirely by modifying auF0261 and changing the traction control row to 0. This means enleanment/enrichment cannot be used during traction control. In this scenario the vehicle will run the commanded lambda instead. " Same mechanism for the on gear change torque requestor. increase for more farts.

Just curious to know if this shows up in "spark adder average for all cylinders" along with normal knock adjustment from the knock sensors in logging. Or is just seen as a dip in the "total spark" number. Have always wondered and assumed that it was the later.

Yeh that’s it! I must have over looked it if it’s in there.

I find also, if saving a log, do as a csv first before closing the live log.

Just a heads up, your data log is doing the 'show only every 50ms' bug when you save from opening a saved teclog file. You may need to update your version if not currently using the newest version. Also your logging spark mod vct, not sure if you're intending total final spark. i cant remember the tag off the top off my head for it.

hey mate, if you haven't already, this is a good place to try and get your head around stuff. And this one... pay attention to posts by @Romulus

That’s awesome. Cheers Roland

Just on this, this would be possible in the ba-bf easily to access but whereabouts would you be able to hook in to this for fg onwards, being log manifold? Does the wiring exist? might be a silly question

Just a side question. How are you guys powering your flex fuel sensors or are you just doing straight E85 tunes. I ask coz i notice that the voltage to the flex fuel sensor during the switch from acc to on must be low enough for the sensor to turn off and send 0v to the ECU. The gauge etc stays on, but the signal to the ecu drops out causing the 98 tables to be used initially. Once the car starts to crank over then the values come back to the High Slope as voltage slowly returns to 11.5-12v. I think one of 2 things are happening. Either battery is no good and voltage is dropping to low - i have seen as low as 9-10v on startup- not sure if that is normal. Or ecu turns off/reduces voltage to accessories during the switch from ACC to ON. The later will affect me as i just did the ole cigarette lighter power source hack. So just wondering are your gauges wired the same or by a relay etc. If you are using a relay, is there a power source that is constant power during the switch from ACC to ON that remains 12v that can be used as a trigger wire that you've found.

I thank you sir. I've actually not tried the functionality in the new versions assuming this was still disabled/not functioning as desired. I've just retested and compared files and data and they are as expected. I cant express enough how much better this is for me Thanks for taking the time.

What i was talking about is if you've done a log but only saved it as a .teclog closed pcmtec than reopened pcmtec. If you then open the teclog and try to save as a csv then it won't save all the data in the csv. It's not to do with the poll rate. Matt has previously said that its not supported. Happens sometimes when out logging and save and i forget to switch to csv before saving. Just means i can't do anything outside of pcmtec which can be frustrating when making the simple mistake. i left a word out. Default type for log save aka csv, teclog. Wow... well that's disappointing. People doing that, that is. Yeah it would be nice to have the option in a 'preferences' so we could chose. Every time i open pcmtec having to select it is annoying. I know its a little thing, but it is a nuisance that takes away from the whole app. A 'work around' is to leave everything running on the laptop but isn't always practical.

@Puffwagon Just note that if you have already saved and closed a teclog and then reopen and save to csv it will not save all datapoints in the csv. Something like 1 out of 50. Which can be pretty frustrating sometimes when you've logged and saved but not as a csv and then close it to realise later you hadn't selected the drop down. Any chance of a preferences tab? Couple of items come to mind :) default for log save default for whether to open items in new tab or not.

I haven't changed anything other than what i've previously screenshotted. This seem to be the key with post ignition fuelling when cold. I've lengthened the delay as you and roland have mentioned an pretty much eliminated the first stumble after start up. Switching to closed loop must lean it out too much compared to the cold fuel table. Doesn't mean i'm getting commanded but its not leaning out to the point of stumbling/missing. I'll keep plugging away but is much better.