MagicMike

Any other work done to the car while the ecu was not connected?

There is a test procedure in the service manual that states the readings required. It looks somewhat 3 position like (empty/half/full). I have also seen posts stating that using the factory sender is troublesome, as the float moves around with sloshing. Somehow the factory circuit dampens this. Worth a try though. Worst case, there are plenty of aftermarket level sender kits you could use. In the end, I left the fuel gauge and the temp gauge working, and removed the tacho and speedo for a screen.

Good in theory, but it becomes a restriction obviously

Interesting that this took so long to find

Do you have a damper?

I took the laptop down to the shed last night, worked straight up, no mess no fuss.

I pulled the sensors out and wiped all the carbon build up off them. Haven't had an issue since.

I did. What I didnt try, is turning off the autorun pclink on startup so it never has the chance to connect at all (as opposed to shutting it down). Will give that a try

That's strange, as I'm using the same in-car pc I use for tuning also haha On about the 3rd screen of connection settings, I have 2 choices to pick 'Link ECU (com3)' or the 'PC name'. Tried both, without any luck. Did you get a similar choice? Plugged in my android and it just worked.

Any tricks for win10? Worked straight away on my note8 android tonight. No luck with windows still

I couldn't even get it to connect in the hour I mucked around with it on the weekend. Haven't tried android yet, but no luck with win10. Kept on saying 'connecting to Link ECU' but never actually 'connected'.

I have noticed same behaviour recently aswell while tightening up the thresholds.

Lambda 1 hardly worked at all on the ~60min drive home yesterday... Worked pretty much all the way in to work this morning though. I have also contacted Ecotrons support and provided the data to them.

Ok cool, will see what happens. Thanks mate

Funny you should mention that... When I first went to set up the Ecotrons, that existing channel was already there and I had no idea what it was for so I just left it. Certainly nothing else connected other than the Ecotrons. Can't recall if I did put a resistor at the other end, don't think I did as the run is quite short. I'll try removing the first channel on the way home today and see what happens. It has only started happening this week, nothing has been changed on the car for at least a few months. No sign of this in any old logs. Could be sensor dying?

This morning I thought I'd try re-setting up lambda 1 CAN, which cleared the errors. But within 10 mins of driving to the servo they were back again. So no one has seen this before?

Since my last post, I have still been dailying the zed, and noticing that lambda 1 is freezing on 1.02 for a period of time, then like magic, it comes good again. I have a few logs showing this, and can see 'Stuff Error', Acknowledge Error', 'Error Passive' and 'Bus Warning' in the CAN tab of runtime values. Can anyone explain these errors to me? Or make tell me how to make them stop? https://www.dropbox.com/s/vgx266go5t920ke/weird.llg?dl=0 https://www.dropbox.com/s/y3ecn5gdpmkl6w9/inj tiiming.pclr?dl=0

Wondering if anyone can have a look here, and offer some suggestions on why my bank v bank lambda are so different, seemingly only over a very narrow injector pw range... Looks most prevalent between 0.5 and 0.7/8 ms (effective). I'm a bit confused because they are quite close at idle which is less pw, and then come close again about 1ms or slightly more throttle, above about 10% Could be actual injector linearity? Could be throttle bodies not synced? I have no values in the short pw adder table, I've considered punching some values in there to bump up the areas identified a little. Have considered adding a few % to each cyl on that the lean bank but trying to avoid that. Am I missing something that stands out as an issue? I have CL fuel on in these files (motorbike is broken so having to commute in the zed, scary stuff) but the behaviour is the same with CL off. https://www.dropbox.com/s/q5lg98wcua2984q/cl5.llg?dl=0 https://www.dropbox.com/s/cp3m17a4h240y88/VG30 part tune6.pclr?dl=0

If you are using different wideband in a different location, anything is possible.

Ok thanks Adam. Wish I could explain the wavy rpm signal. So if it isn't a triggering issue, it could be a tuning issue? It is still very rich up top and that is where the biggest ups and downs are. Something to keep an eye on I guess.

Log file and tune file below. Appreciate any feedback https://www.dropbox.com/s/gtu34cxumatbwo9/Log 2018-05-16 11%3B02%3B39 pm.llg?dl=0 https://www.dropbox.com/s/invymte1994af88/VG30 part tune.pclr?dl=0

Hi again, Can I have your thoughts on snippits of my log file, specifically looking at the engine speed ROC, and what is 'normal', what is not normal, and where mine fits in? I have zero trigger errors, ever, engine runs nice, ignition angle is very smooth. https://www.dropbox.com/s/gyvfc7lmhhjzd3q/RPM ROC Wide.JPG?dl=0 https://www.dropbox.com/s/nw47l37iavw6npm/RPM ROC Narrow.JPG?dl=0 https://www.dropbox.com/s/m4481o53w61fhox/RPM ROC Narrow 2.JPG?dl=0

I suspect as much. Probably happens alot more often than this one time but gets lost in the data, and I can't say i have compared mixture maps before so haven't had something side by side, like for like on screen before. .81 v .76 was the case, 5500rpm and 100kpa mpg. 40% cell center.

Have another question I need to ask after reviewing some data from the weekend... I think I know the answer, but can someone please confirm... The target value that appears in each cell of the mixture map, is this value the average target of the samples that fit per the filters? Ie, the target is NOT taken directly from the lambda target table? I have a scenario where I have 2 log files, exact same tune file, exact same filters, and I am seeing different target values in the same cell in the mixture map.

I have noticed the same lag in making up/down adjustments to blocks of cells. Only when connected to the ECU.