Jump to content

Simon Kribstock

  • Content Count

  • Joined

  • Last visited

About Simon Kribstock

  • Rank
  • Birthday 12/28/1988

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
  • Interests
    IG: STi_SIMER, Rally, Rallycross, Autocross Snowboarding, Guns, Photography,

Recent Profile Visitors

194 profile views
  1. Haha ok that is what I should’ve asked; if the clutch even sends a signal to the ECU on a standard Subaru. I was thinking it was a pre-wired input like the power steering switch, ac request, etc. I must’ve entered it with the intention of wiring it to DI5. Thanks Adam.
  2. no, it doesn't change. tune attached 4bar MAP, quick spool, popping flames flat boost.pclr
  3. 99 STi plug-in g4+. Setting up my launch control. Would like to use, or at least try, my clutch switch as the activation control. I believe DI5 was the default input but I'm not 100% sure. It doesn't respond in the runtime window so it obviously won't arm. I know the switch works because I originally had it bypassed for no-clutch starts and now it won't start unless depressing the clutch. Any ideas?
  4. What does compressor surge look like on a data log graph? At about 7000rpm, my MGP/MAP spikes, fuel leans slightly (despite adding fuel) and power falls off. No knock or fuel/ign cut. Turbo is a VF48 with a billet compressor wheel.
  5. I suspect a sticky or failing valve as well. Firmware is Here is my tune. I'll have to make an idle log. 60 degree idle map with idle ignition ... cl idle.pclr
  6. Having this same problem. This is frustrating as my engine idled just fine with a standard ECU. Is buying a new IACV the only solution that has worked for everyone?
  7. Attempting to tune my idle base position table in open loop. I follow the OL procedure, achieve a suitable idle, save and store. But when I turn off and restart the engine, I have to completely change the idle base map values. Car is a 1999 Subaru STi with a stepper idle valve.
  8. Lock/unlock issue has been resolved. Could updating the firmware after unlocking the ECU cause it to request unlocking again? Either way, it's good now. I also resolved the the 5v supply error as well by properly pinning my MAP sensor Thanks Adam
  9. Subaru v5 STi, WRX6 Plug-in ECU I have disabled the ANv4 (n/b o2) Error low fault detection (set to 0v) but the ECU is still throwing fault code 20; below error low value. Any ideas?
  10. PCLink v5.6.5.3338, Firmware I have unlocked it once I noticed tonight I had a fault code 74: analog 5v supply error. Not sure why I didn't see that yesterday. Checked the runtimes screen and it was fluctuating below 1volt. Only wiring modification was s 01-07 WRX STi Omni 3bar MAP sensor so I disconnected it and everything seemed cured. I may have used some bad pinout info from a unnamed forum . I'll re-pin tomorrow and see how it works.
  11. I set AN temp 3 to IAT and sure enough it works. Matches ECT +/- 2 degrees. With that said, I’ll wire my GM IAT, mounted just prior to the TB, using the OEM IAT circuitry; unless otherwise advised. I’m curious about AN temp 3 on my expansion connector now. How will that input work?
  12. My IAT sensor is separate from the MAF. I have an RA Limited STi; maybe that’s the difference?
  13. Erratic sensor readings .MOV Just plugged in my WRX6 plug-in ECU for the first time. Upon switching the ignition to "on", engine "off", I immediately heard my IACV cycling. I connected to my ECU via PClink, and noticed erratic readings. I updated the firmware and readings remained. I flashed a tune with the proper calibrations for my MAP sensor, injectors, etc. and performed a TPS calibration. Erratic sensor readings remained and now included an erratic TPS signal. Another issue I'm running into is a repeated request to unlock the ECU. Any ideas? Attached is a video screenshot. Please excuse my post edits haha. Haven't figured out how to remove dupilcate videos
  • Create New...