pcmhacking.net

Thanks VL400 for the 2nd map setup info. Assume B12 A/D input is WB o2 input I should use. What resets the cross count value, end of 100mS sample period?

Canister purging is simple ported manifold vacuum on VN & have checked the canister & all ok. This canister discussion started from the radical ve cell changes I am getting from ve learn & it's still unclear to me why BLM mode should give different results to ve learn mode unless there is something wrong with ve learn process.

I would expect BLM mode not to show such a radical change in ve values anyway, simply because BLM correction range appears to be approx +/- 20% of existing VE table value where as ve learn can change VE table absolute value from 20% to 90%, if I understand the parameter definintions. Although any VE/BLM correlated change I guess would indicate the problem is engine/sensor related & not ecu program corruption.

At this point I will revert to BLM mode with an "un-learned" ve table & see what happens.

mag wrote:Thanks VL400 for the 2nd map setup info. Assume B12 A/D input is WB o2 input I should use.

Its actually pin D8. Need to get antus to update the PDF.

Here is 808 wiring pdf marked with D8 as WB o2 sensor input.

Update: removed due to update of official file.

useing VE learn on an old sensor is fail LOL.they last about 70000km then they are about stuffed fit a new one

Have not been here for a while, the install of SC is taken longer than anticipated, can't find time to take car off the road. Still running v104, my reading of the history says that basic function code is the same for v104 & v110.

Just to confirm, I can migrate v105 cal to v110 cal, put v110 cal into v110 bin & write v110 bin to NVRAM all using flashtool.

Now for my question relating to v104. In last couple of days have had issue where WOT causes engine to choke or stop revving beyond 4000 rpm. First noticed on expressway when trying to overtake, not impressed to say the least. More WOT runs starting at speeds between 60 & 100kph result in auto down shift but engine will not rev past 4000 although when throttle is backed-off, engine response returns & small revs increase occurs with constant throttle. Feels like fuel starvation but cuts in clean like injector pulse too short. Rev limit values all set to 5800 rpm.

Complication is that at higher altitude ie 600 metres, the problem is not immediately apparent although have only done limited testing at high altitude.

Anyone care to offer suggestion. I have no logging data yet, have been eliminating possible mechanical causes first. Will try to get some log data over the next few days.

a log will tell you straight away but to me it sounds like a dying fuel pump. id get a log now. then the log will point you to the mechanical reason. most likely you will find the o2 sensor go full lean at the point it starts dying. make a WOT log of the problem happening and post it up.
can you get your hands on a fuel pressure guage to check the fuel pump?

yes you can do everthing to update to v110 using the flashtool but id do it in this order:
download current cal, migrate to v110 and save somewhere.
click upload bin and upload unmodified v110 bin.
click upload cal and upload your migrated cal.

If I could only type good it would help. Where I typed "migrate v105 to v110" should have been migrate v104 to v110 but assume that process would be the same.

Jayme, unfortunately do not have a fuel pressure gauge but might be able to borrow one. Logging will give me a chance to try out the OSE plug-in in TP5. Great work by all concurned & VL400 also for the continuing development of $12P.

Well, the process is the same. I'd do it Jayme's way too, It saves the step of putting a standalone cal in a bin on the pc .There is no verified automatic way, and your less likely to run in to trouble doing it his way.

Just one question regarding OSE plug-in. I ask this because I initially added the OSE plug-in dll file to TP5, selected COM1, turned on the ignition & hit auto detect & hardware was detected. Did not run the engine to see what real-time functionality I had.

Then I read the update comments for v110 & noticed "v110 supports the OSE plug-in". If this is the case why would the hardware be detected.

I assume I should load v110 into the NVRAM with my v6 cal & then the OSE plug-in will work as intended with the appropriate v110 adx.

its to do with comms speed, dont worry about it...