Hyper

hm... so you are saying there is no way to setup PWM output that would inhibit value under knock event? or, if the ECU is equipped with knockboard capability, you won't be able to inhibit knock correction as the event to output PWM signal?

Thanks Simon, I do also have the Vipec knock amplifier kit, how can it be wired in and setup for closed loop knock control with my board?

got it, waiting on Simon then there are few bugs I am working on with the wiring, so I can't fire it up to check yet, and I was hoping to get all info so that I can make all the re-wiring accordingly before I plug it in and one other thing - I can see I can enable DBW in the software, does this mean that I can adapt DBW manifold/TB and the board uses IAC input/outputs that can be rewired into DBW to control it?

Adam, can you confirm or deny this particular board supports OEM knock sensor operation?

Attached pics of the board, and cal file I am setting up for the shift light I am using PWM ECU output, and 30-40% duty so it blinks rapidly Bastard_rev01.pcl

for the PWM shift light I need to look at what I have set in SM4, but I believe its somewhere around 40-60, its a LED so it doesn't need much the warning light is the dash light that indicates low oil pressure, ground switched - I use it to indicate when the oil temp is below 40* or above 110*

Sure This is the pressure sensor https://www.digikey.ee/product-detail/en/ssi-technologies-inc/P51-100-S-B-I36-4.5V-000-000/734-1087-ND/1665849 Data for the temp sensor attached in the zip file so only two outputs to choose from, eh?... oh well, I guess I will ditch one of the lights Can you guide me how I can repurpose Aux 8 for the shift light and Inj 6 for the on/off cluster light? Temperature Sensor Calibration.zip

Hi guys, In the past I've ran Vipecs on my rally cars, but now I am considering swapping SM4 plugin for the V7-9 Vipec Plugin that I have in my street car. I love the SM4 and what it can do, but in terms of fine tuning for a street car it becomes a real nightmare, primarily the issues I have always had is a charge temp table that affects fueling, minimal crank syncs required to start the car, stalling and starting (the ECU has a mind of its own when it comes to starting the car based on how it was shut down), and closed loop corrections affecting the whole table, rather than only the cells that need on-fly adjustments. Now, I have never fine tuned Vipecs before (since rally cars don't need all that), but I hope it will be easier I have started building an excel file, listing the wiring modifications that need to be done (since I have some custom sensors added through existing harness), which is simple. I have also started working on the base cal file to address all my custom bits and pieces, and while I understand where I will have the aux sensor assigned, there is something I wanted to discuss: 1. is it possible to calibrate pressure sensors to show Bars instead of PSI/Kpa? Assuming the base fuel/ign tables don't have variables in the load calculations, this would address those tables as well as aux pressure sensors. Also, what is V9 MAP sensor rated at? I heard somewhere it can read up to 2 bars 2. aux sensor calibration - I can't change the predefined axis calibration for some reason, and I need to calibrate aux temp and pressure sensors (one is based on a linearization table, another is just linear with span an offset) - how do I approach this properly? 3. I have 3 different outputs that I need to transfer to Vipec, all of them are simple on/off lights. One is a ground controlled that activates one of the warning lights in my cluster, another is a LED shift light controlled by PWM signal (GC8 don't have the fancy shift light in the cluster like the later STIs), and the third one is a LED that represents knock light. How do I assign all of them and to which ECU pins without the extension module? 4. knock control. Can the V7-9 plugin operate the knock control system? I can see it can be enabled, but does it interact with the stock knock sensor, or does it require something else? If not, I do have the Vipec external knock box that I used as an external tool when tuning, theoretically I can integrate it in the car as well (although relying on stock knock sensor would be sufficient for me if the board can do that) 5. closed loop control. can you confirm the changes made during the ongoing closed loop control only affects the cells modified, and not the whole table? 6. I am using TechEdge wideband controller, by a chance is there any predefined calibration that can be used for it? I think this is it for now, more will probably follow as I go through the process

my firmware version is 4.10.2.0, so I can't go beyond that and VTS V4.10.2.1784 didn't work with the ECU

Subaru V10 plugin, latest firmware updated for some reason I am only able to connect to the board using older PCLink 4.10 software, and I can't find a very useful option that I used in Vipec, where I would just drive the car which logging in the background, if would record all fuel cells incorrections and then just by clicking them the software would calculate the proper value for the fuel table in the Link, I only found manual or auto tune which requires me to stay in a given cell for a certain amount of time to auto-correct it, great thing on a dyno, but not when you are trying to dial in a base fuel map on the road Is there a way to use this function on PCLink, or perhaps a bypass to force the board work with Vipec software?

confusing at first, but after re-reading it few times I got it I sorted it out, turns out I had a loose connection somewhere (for no reason) - I traced all wires from the DBW to the ECU and one signal was missing, I assume there was a loose connection in the plug on the strut tower which goes to the throttle, pinned out, pinned in - started working as always, thanks for clarification Adam!

unfortunately my problems continue, I am stuck with error code 5 upon TP calibration... read the manual, it states: Error Code 5 – Max 80% DC & TPS(Main) Movement zero. The motor has reached 80% DC and the TPS(Main) has recorded no throttle plate movement/change in voltage. Cause(s) of Error Code ·TPS(Main) not connected, faulty or has incorrect fault levels set. ·E-Throttle Motor not connected to the ECU. Everything is connected, I ended up removing the DBW, cleaning it and is started working. After a short while the problem poped up again and never went away, so I can't get the DBW to work I looked into wiring, and made a table of Link wiring/pinout VS OEM wiring, here is what I found: PCB V1.x (Plug-in)Subaru V10 WRX/STiECU Pinexplained Aux 4EThrottle Signal 1B26/27???speed signal/fuel pump controloem diagram says D5, but link manual says D5 is Aux10 which is not presentAux 9EThrottle Signal 2D4throttle motor (-) duty form An Volt 2TPS (Main)C18throttle main An Volt 3TPS (Sub)C29throttle sub An Volt 9FPS (Sub)C28pedal position sensor sub An Volt 10FPS (Main)C17pedal position sensor main as you see, Aux 4 is what I don't understand - it links to B26/27 depending on jumper, but none of them go to anything throttle related, as the OEM manual says D5 is Electronic throttle control motor (+), Duty waveform, frequency 500Hz Link manual, however, says D5 corresponds to Aux10 which is not even present in the software what's even worse, is that now I even have a trouble code if I pop the stock ECU back in, P2109, which makes me think that I might have done some damage with the Link please advise, I ran out of options already fighting with this over past 2 weeks

I would have never guessed that anyway, I tried it tonight - seems it did the trick! I also noticed that if I try the TPS calibration, it offsets the FP/TP settings and throws me errors again, so I assume TPS calibration is for DBC cars only looks better now, thanks Adam! now back to my LC1 experiments... Log 26-04-17 2;05;14 am.llg

yeah I read in the manual it would throw a code if the error margin is above 3% if I recall question is - how do I solve that? as I mentioned, TPS calibration doesn't help

I went through everything again today, it seems I narrowed down the problems to E-throttle only, no other faults I re-loaded the pcl file again (attached in my OP), stored it, turned engine on - the ECU seemed to be seeing the throttle, yet when I started the car the pedal would not respond after that I did the TPS calibration, the ECU was seeing the throttle and then all of a sudden it would loose it again throwing the 77 code - before it happened I heard a relay click inside the ECU, hmm..... so I shut down the car, turned key on (engine not running) and started another log (called engine_off_relay_clicks, attached) while playing with the throttle pedal - I could hear the throttle butterfly moving in the engine bay, then all of a sudden again a relay clicks inside the ECU and I loose control over the throttle (it happens on 54th second of the log, throttle just goes to limp mode 7% with no response) Log 23-04-17 4;19;13 pm.llg engine off_relay_clicks.llg

hi guys I am in the process of installing V10 Subaru plugin (4 plug ECU) in my rally car and stumbled across few problems I am not sure how to sort out... the car is a stock 2005/6 USDM STI with regards to wiring, no issues on stock ECU I pulled out I set the jumpers for proper year/wiring, based on the instructions loaded base map, made some minor adjustments for my boost solenoid/avcs targets and left all triggers and settings untouched (attached the pcl file), yet here are the fault codes I am getting: code 14 code 17 code 19 code 43 code 46 code 75 code 77 code 11 thus, I have no control over my throttle... went into the manual, read on the fault codes, followed the procedure of TPS calibration 4 times - no effect. What is also odd, in the logger after I calibrate my TPS - TP main doesn't not move at all, yet I can see the EThrottle target move based on the pedal position. TP Main would also occasionally jump from 0 to 100% and back ECU is running in........NORMAL MODE Current ECU firmware information ----------------------- ECU firmware version : 4.10.2.0 Bootcode Version : 1.4 Board S/N : 13817 ECU type : 25 rev1.pcl

should I? ignition cut should give me enough boost to launch on gravel, I think?

I don't have a free DI though, and I was hoping to get away without additional wiring, hence I set it to "always on"

thanks for the input dave, will give it a shot

understood I need LC as this is a rally car, so I will just change it to Mode 1 will these settings work? meaining the LC will deactivate after 15 km/h despite the launch RPM table values?

Whenever I went WOT (TP 100%) I would hit 4000 and stay there, which felt like I hit a brick wall, this didn't happen under SAME loads but with throttle below 100% (50-80), so we thought it was ignition related issue and changed coilpacks, spark plugs, rechecked all sensors in the end, we traced the issue to be LC, however I looked over and over and I don't understand what I've setup wrong, can you guys please take a look? Perhaps I mixed up some settings, but I was under impression the LC was activated, but not set to any given RPM (hence Launch RPM = 0)

oh yeah, its a dedicated rally car, the only time it sees street is during transit stage to stage this is why I don't want to spend time going something that is not required for a normal operation

Subaru V7-9 plugin I plan to run ALS which will be enabled through a dashboard switch (wired to a proper pin now, after my last experience with frying the board ) and activated per the software conditions My question is, since cyclic idle will be used, do I need to dial in my ICS? Due to lack of time, I just raised the values so that the car idles around 1500 RPM all the time, and I don't want to do monkey's work if these settings will become irrelevant once cyclic idle comes to replace it

bumping an old thread, but can anyone share a base map for GRB STI i88 VIPEC? Mine is EDM, but I don't think it should matter much

Hi Simon, I am actually using V7+ plugin which is able to control AVCS at the moment though, AVCS is not active (hardware-wise) as the motor has non-avcs heads with cam sprockets set to max advance so all the pins from the stock wire harness are occupied and I have to use something like AC input? It's an option, since it has been removed, however I would have to redo some wiring as the stock Subaru AC switch on my dash is very inconvinient