Jump to content

Rob W

Members
  • Posts

    106
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Rob W

  1. Wow Billy. I have been chasing the exact same issue on and off and doing exactly the same thing chasing the idle up to 90*c.

    I now have a clamp on every possible boost leak point and have a clean valve. This has been frustrating the hell out of me although it is fine at the moment.

  2. Ballenger AFR500v2 with NTK sensor. Little bit more expensive then the Innovate and AEM  but you have a choice of several sensors and you can have it configured to read Lambda or AFR.

    I had an innovate with 4.2 sensor for 6yrs and no issues other than replacing a sensor and a guy had his Haltech gear on my car and said my Innovate was reading rich which I couldn't afford so eventually changed to the Ballenger.

     

  3. I have a Ballenger AFR 500 Wideband here to install.

    Can anyone tell me what this should look like in the Cal Table

    Lambbda (.618-1.098) = 0.618 +V out x 0.096

    It has a linear output where 0v is equal to .618 and 5v is 1.098

    So is it simply a matter of Input Value A =0v, Output =.618 : Input B 5v, Output 1.098

     

  4. To do a COP conversion on a '99 wrx do I use the Aux  Output Ignition Drives?

    1&2 are currently ignition. 3&4 are engine fans. Would I change 3&4 to ignition drives and reallocate the fans to 5&6 and would the fans then work?

    Can I then change from wasted to direct spark?

    Where would the signals to the coils be wired to?

  5. I logged to the ecu at 100Hz and yes there were some spikes over the 500 threshold. However there were still some instances where timing was pulled below  the set threshold.

    I'm going to update the firmware as suggested this week.

  6. On ‎7‎/‎15‎/‎2018 at 7:30 AM, Stevieturbo said:

    It would be nice if these base tables could self populate whilst performing a known "safe" run to fill in the base tables with a background noise level. Then simply add the 10-20% to those values

    the table could average over a few pulls if need be.

    That would be awesome Steve.

    My problem is at the moment is I can't get a known safe run with these little spikes of timing coming out.

    I pulled the plugs on the weekend and no signs of any det. I didn't get a chance to get the car out but I'll log it to the ecu and report back as soon as I can.

  7. 2 minutes ago, Adamw said:

    Looking at one of your screenshots above it looks like you might be using an old version of PC Link?  Make sure your ECU is running 5.6.5 firmware, there were big improvements made to knock control in 5.6.4 & 5.6.5.

    >logging>ecu log file download

    Thanks Adam. Last time I updated the firmware I had some issues with the tune so I went back to this version. Will the compare function show me what changes. Eg - The TPS needed to be reset.

  8. Not yet Adam. Probably tomorrow. We did a lot of logging last weekend with some ears on it with nothing audible.

    It seems to be happening so quickly I can't even hear it, maybe why the logging isn't picking it up. When it did knock on a separate occasion, I was able to hear a crack even as the system took over and pulled timing.

    I'm going to pull the spark plugs today and have a look at them. And I'll get some logging done at 100Hz to the ecu and see what that says and report back.

    How do I look open log files out of the ecu?

  9. On ‎7‎/‎9‎/‎2018 at 6:42 AM, motomattx said:

    How about putting a volt meter on the output of the knock sensor to see if its actually putting out voltage and if you see it spike at all when your doing a pull?

    I'm no expert on how the ecu, knock sensor is interfaced/works mate but if it's not putting out a voltage how would I be able to log it as I have?

     

  10. Thanks Timmy, I'll try logging to the ecu at 100  Hz.

    I had the car on the road with a driver today, I turned the ign trim back to 0.5Deg with some det cans on it. It was still pulling small amounts of timing without anything audible.

    I've been looking at the spots on the I trim tables where it is occurring it's at half of the threshold and no audible knock

  11. 18 hours ago, TimmyD said:

    Hi Rob,

    Firstly, my experience is limited to my own car only... but I was puzzled why you were only logging/showing knk level for 2 cylinders?  I understand wasted spark, but surely you need to monitor cylinders 2 and 4 to set the gains in the same way as you have for 1 and 3?  Otherwise these may be exceeding your threshold and causing timing to be pulled?

     

    Hi Timmy,

    It's because with the cyl allocations set up like that the numbers for each pairing are exactly the same when I log them.

     

    Rgds Rob W

    Capture.JPG

  12. 12 hours ago, Adamw said:

     

    In this case I think you probably are exceeding the threshold but just the logging is too slow and doesnt show some small/short spikes above the threshold.  What frequency were you logging at?

    6kHz. It shouldn't be I pulled 3deg out of the positive kPa MAP across the board to set it all up. I've got a driver today so I'll turn the whole thing off and have a better listen to it and report back.

  13. Thanks for the replies. Thanks Adam, that clarifies the allocations and gains.

    I am logging  "I Trim cyl1 &3". The threshold setting is at a flat 500 for getting the gains and noise profile set up. I have had ears on it but haven't turned the Ignition Retard limit back to zero as I wanted to see what it is doing. Just trying to get my head around why the I trim is showing retard below the threshold. I'll attach a log screenshot and set up shot below.

    Knock set up2.JPG

    knock set up.JPG

×
×
  • Create New...