Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


M1tch last won the day on June 11 2019

M1tch had the most liked content!

About M1tch

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Perfect, thanks Adam, I figured if I set it to Stoich wideband it would work as per OEM narrowband otherwise there would be no real reason to have this option for wideband as you would just use auto.
  2. Thanks for the responses so far - I will only be running a single wideband O2 sensor for the engine - I can see that the changes per second for fuelling in CLL is set higher at lower RPMs. I have previously upped it slightly however I found if it made is really erratic as the fuel correction was changed quicker than the mixture was changing so the idle wasn't stable! I guess the question is - have others passed the emission test with just a wideband O2 sensor running CLL? I have a feeling there must have been!
  3. Hi all, Just working on my mapping in terms of ensuring that I am able to pass the UK MOT emissions test - which tests CO, HC and Lambda - Lambda needs to be at 1, plus or minus 3%. I have a single wideband O2 sensor which I have set to run as auto fuelling compared to the AFR table. I have learnt that the main cat would usually need the fueling to dither between rich and lean as this increases the efficiency of the cat. https://www.crypton.co.za/Tto know/Emissions/catalitic_converters.html I know with the auto fuel option with the wideband sensor the fuelling starts w
  4. M1tch

    Fuel getting hot

    Are you running multiple pumps?
  5. That update to the trigger mode seems to have sorted it! Looks like the VVT offset is also good as well as I checked the offset with the cam test when I got back from a few logging runs.
  6. Thank you so much Adam, I will swap over the trigger mode to 2NZ rather than 1ZZ as it was previously and see if that makes a difference - looks like the arming tables are still set to 2V above 2k rpm. Will go and get my timing light out again and set/check the base timing, I did ensure that I painted up the crank pulley when I had the engine out to make checking the timing easier than before! Shall I set the VVT offset to 50 degrees again as default or just leave it at the current setting? I guess no real harm as its not like its got an offset of 30 degrees or something! Will just g
  7. I have just gone in and removed the battery from the car and checked all earths and wiring both inside the car and out, found a possible issue with what I believe is a signal interference suppressor which wasn't 100% tight on the stud (although still making contact) - will see if I can take the car out tomorrow to see if that has made any difference.
  8. M1tch

    Rpm limiter

    There is a good help file that you can easily find in the PC link software - there are some different limit modes for both hard and soft limits.
  9. I have gone out and got many trigger scopes as requested @Adamw on idle the VVT was set to 0, for the other triggerscopes the VVT was set to 40. I could tell that the engine wasn't happy as it wasn't easy to really hold the RPMs as I would creep up on the RPM, it would hold but then increase again - I could hear the same sort of issue as before and hopefully one or two of the trigger scopes has captured something of use! Here are multiple trigger scopes at between 2.5k, 3.5k and around 4k - there was defiantly some issues at around 3.5k where it would stumble a bit: Trigger Scop
  10. I have an AEM X Gauge LSU 4.9 in mine - have wired mine in as CAN rather than AN voltage - guessing that the Zeitronix ZT3 has the same calibration in terms of voltage vs Lambda as the sensor you are running.
  11. M1tch

    G4 Handheld

    Its not like a PFC hand commander if that's what you mean - the good news is you can run Realdash which connects up to the ECU for various read outs as gauges, its pretty cool!
  12. Sorry Adam, was trying to get as much logged and tried out last night before it got too dark - just wanted to check a few other things to rule them out but rule them out one at a time. I was only able to get one at idle (with 0 cam) yesterday from what you requested - will see if I can drive somewhere to capture a few more at higher RPMs after tweaking the map to give me a 40 degree cam at 3k rpm. I did find that when not under WOT but gradually revving up to the higher RPMs I didn't get a misfire/this issue. Trigger Scope Log 2020-10-22 4;17;05 pm.llg I am going to go through
  13. I have just gone out again with a different dwell time table, here is the previous table: And here is the table I just drove - the issue is still there though: On the last log I had another HUGE spike in dwell time again - voltage at this point was at 13.67v, I am going to go back to the original dwell time setting again I think, although at WOT just before it started to have the issue again dwell time was at around 2.3 vs around 2.5 on the previous settings. I have no trigger errors and the trigger counter is still at 0. Is there any way for the ECU to only use the setting
  14. I have gone back out again and got 2 logs, the first run I basically adjusted the timing down a bit to make sure it wasn't something like knock etc, still had the issue, I then turned off VVT completely to see if it was the VVTi that was the issue or something else - the problem is still there and was quite bad. Hopefully the 2nd log will help to figure out the issue as in the screenshot below I am at 100% throttle but the revs won't increase higher than 5,300 or so, it feels like ignition cut which is why I thought it might be a limiter or something. Coil dwell time is at 2.5ms at this
  15. You download the file, go to the dwell time table, right click, click on 'import/export and then 'import from file' - you then open the file you have just downloaded and it will load in the table for you.
  • Create New...