Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


TimmyD last won the day on May 15

TimmyD had the most liked content!

About TimmyD

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. TimmyD

    Subaru knock problem

    For what it's worth, I wrote up my experience of setting up knock control on my Impreza STI 2007. It's all based on the Link help files... I believe what I have done is correct (comments welcome!) Feel free to have a look at the attached word doc... BTW, I found the sound levels of each cylinder to be quite 'noisy', so had to have a fairly large headroom in threshold to prevent false knock detection. Knock Setup.docx
  2. TimmyD

    Subaru knock problem

    Just an idea... Perhaps you could try logging to ECU at 100 Hz, only logging the relevant parameters at this rate though. Might help to understand whether the PC just can't display/log data fast enough (as Adam was suggesting)?
  3. TimmyD

    Subaru knock problem

    Hi, I only skimmed through this post, apologies if you've already fixed this...
  4. TimmyD

    Knock control and Motorsport settings

    Thanks Adam, you've answered all my questions - amazing tech support as always.... :-)
  5. TimmyD

    Knock control and Motorsport settings

    Thank you for the fast response Adam. Just to check I understand you correctly: 1. FFS... set "RPM High Lockout" for knock control to a value just below the RPM that I'd change gear? 2. if antilag is active when TP is 30%, set "TP Low Lockout" in Knock Setup to be, say 31%? Re your advice on antilag, thank you, I have it set to give around 70 kpa at most when off throttle, so still have some vacuum for brakes. Turbo lag is reduced, but I guess it's not what you'd call 'proper antilag' ? I don't have an EGT sensor, so am cautious of overdoing it!! Would appreciate your comments on this one? Thanks
  6. Hi - please could I have some guidence on knock control with motorsport options... (would you ever use both together?) I have setup knock control, which I have verified works perfectly. I also have Launch Control and can see from "Knk System Status" copied here: 0 = Active 1 = Lockout - RPM Low 2 = Lockout - RPM High 3 = Lockout - TP Low 4 = Lockout - TP Delta 5 = Lockout < 500 RPM 6 = Err: DI Feedback 7 = Startup Lockout 8 = OFF 9 = OFF: DI5 Pullup. 10 = Lockout - Launch Control that knock control is disabled during Launch, which makes sense due to the increased sound levels that would otherwise cause false knock detection. But what about Flat Foot Shifting, would you not want knock control disabled for the duration of this? And finally, although setup quite conservatively, Anti Lag. I set this up thinking that it would be beneficial for short sprints and hill climbs (no more than 1 mile!). It's currently setup to reduce lag, rather than create lots of low down power. Any tips welcome, I'm no expert! Thanks
  7. TimmyD

    CAN BUS Output configuration question

    I found this an interesting thread as I have been working on an MBED version of what Markus describes. I send 7 frames (one after the other) with an identifier in the first byte of the stream and another identifier at the end, which enables me to resync if corruption occurs. It doesn't cater for corruption in the middle of my data stream, which so far I've not resolved. Apart from using an oscilloscope to check the signal integrity, I'm not sure what to do? I had wondered about splitting my stream into smaller messages and use multiple IDs. Any ideas welcome?
  8. TimmyD

    PCLink Crashes While Logging

    Interesting, I have been through this process to hone mine too. I also found that PC log files grow in file size very quickly if you log all ECU parameters. Instead, I found that logging only what you need results in much smaller files (and faster laptop operation). Do you have internal ECU logging configured, that might be a way to retrieve your 90 minutes worth of data? In my opinion, it's a good thing to have set up and running anyway. Just make sure the ECU is logging the parameters in your mixture map filters (eg ECT, Overrun Fuel Cut, TP...). I had great results using this method. As for your original question, I'm afraid I don't know :-( I guess you've searched for *.llg ?
  9. TimmyD

    CAN Lambda Error 54 Excess pump current

    Clint, Thanks for your advice, the new Lambda sensor did the trick, Lambda is spot on again! Great service from BHP too.
  10. TimmyD

    CAN Lambda Error 54 Excess pump current

    Thanks very much for the speedy response, I will try that. The sensor is only a couple of years old, but I do a lot of short trips, so I guess it's running rich a lot of the time!
  11. Hi, please could I have some help, I have a Closed Loop CAN Lambda on my Subaru Impreza, but have run into a problem. I now see "CAN Lambda Error 54 Excess pump current" and the Lambda goes to 10.119 shortly after starting. Not sure if this is an error I have somehow introduced as I have been looking into CAN streams and adding a custom dash. So far, I have only configured a CAN stream on CAN Module 2, at ID 1300, believing that this would have no interaction with CAN Lambda Module 1 at ID 950. I have not got as far as connecting anything to the ECU as yet. I have since loaded a previous know good tune but the problem persists. The CAN status is all good (green) in PC Link, see pictures below... Help?
  12. Hi Tiago, interesting, it looks like after the throttle blip, the idle rpm is above the idle control range, so never recovers. Perhaps you could try adding Idle Ignition Control? I've modified your .pclr file and attached it. I think this will bring the idle rpm back within control, but I'm sure you'll have to experiment with the settings! 5a50b36525517_SubaruTypeRAV6_IdleIgnition.pclr
  13. Regarding your item 2 - When I start the engine (hot) the idle stay at 900 rpm but if I depress the accelerator it's going to 1500 and stay around this value... Could you post a log file that includes the 'good idle' ie before you blip the throttle? This might show what the cause is (maybe!)?
  14. TimmyD

    mixture map filter

    This confused me too, so this is my interpretation... The above represents one cell (divided into 100), the green bit extends 50% towards the cell edge, hence in this example, it is 50%. Based on this, a value of, say 10% would be more stringent and get more precise results.
  15. TimmyD

    Missfire on idle

    Hi, I have been looking into this as I spent a lot of time refining my idle control. I'm not an expert, but here's some comments for consideration: 1. The idle ignition table has an ignition timing of 8 degrees at zero idle error. I think this should match the main ignition timing table of 12 degrees at idle rpm. This is to give a smooth transition between the two tables. 2. The fuel table has 14.0% in the top left block, is this for the purpose of diagnosing this fault (it looks unusual). 3. At the point in the datalog that you mentioned (8.40.525) the idle rpm drops before the lambda goes lean. Does this suggest that the lambda 'glitch' is a result of some other event (or engine load) rather than the cause of it?