Jump to content

timslib

Members
  • Posts

    29
  • Joined

  • Last visited

Posts posted by timslib

  1. 3 minutes ago, Adamw said:

    Yeah I think it will need to be powered up whenever the ECU is live.  Part of the CAN standards is an error checking system, if no device acknowledges the messages the ecu is sending it must report a transmit error, once it reaches 255 transmit errors then it goes to "bus off" state.  The bus wont be reset until it is power cycled or you open the CAN screen and hit apply again.

    Roger that. I'll make the changes in the wiring and report back. Thanks again Adam! :)

  2. Hey guys,

    I'm having a bit of an issue with my Link CAN Gauge, sometimes after engine start, it won't receive data from the ECU (WRXLink9) and just shows zeros until I restart the car.

    It's connected to accessory switched, does it need to be on the ignition "ON" position so it retains power during cranking? I'm assuming it must be dropping connection or something.

    any help is appreciated, thanks guys

  3. Hello again gents, 

    So, I went back today and added the data that @Adamw very graciously provided me, thank you kindly! I also made a new idle ignition table, which still needs a bit of tinkering with, but overall, it's idling a million times smoother. 

    I also had a fiddle with the fuel table as I noticed it was idling MUCH (.6 Lambda) richer after adjusting the dead time and minimum PW, and it also seems to rev smoother now too. Idle seems to sit about .920Lambda at idle now.

    Map/log attached for perusal. Thanks fellas.

    idlelog2.0.llg idle2.0.pclr

  4. 1 hour ago, stigc8 said:

    The left side of target error works when idle speed is too high, and right side is idle speed too low.

    Middle is your ign timing with zero error, which is the number that your idle speed was setup to run with without closed loop enabled or ign idle control active.

    Ah roger, my thought process was back to front. Lol. Appreciate the insight there mate. 

    31 minutes ago, Adamw said:

    I agree that the idle ign table is back to front.  But the fuel set up looks wrong all over too - Its never going to idle well at 1.2lambda.

    • The injector size is set to 980cc for fuel 1, it is set to 600cc for fuel 2.  They should flow less with ethanol but that looks like a pretty extreme difference.
    • The idle VE is 22% in fuel table 1, it is 63% at the same point in fuel table 2. 
    • The multi fuel density and temp coefficient appears to be set for E100 but the stoich ratio is set for about E85.
    • The fuel pressure sensor calibration is wrong.  Fuel pressure also doesnt increase linearly with MGP, probably due to the same issue.
    • The min effective PW is set to 0.99ms, this is unlikely correct and will prevent you from achieving the correct lambda when running petrol.  More typical value would be 0.2ms.
    • The injector deadtime of 0.478ms at 14V is pretty unusual, not necessarily wrong but I would be doing some tests to confirm it is right.  
    • Not related to the current issue, but the boost control solenoid on Ign 7 isn't going to work well unless you have fitted your own freewheeling diode.  If not I would suggest moving that to a proper aux output which has freewheeling built in. 

    Roger that, time for a visit to the tuner. That's a big list. 

    The car has been on the street 

    34 minutes ago, Adamw said:

    I agree that the idle ign table is back to front.  But the fuel set up looks wrong all over too - Its never going to idle well at 1.2lambda.

    • The injector size is set to 980cc for fuel 1, it is set to 600cc for fuel 2.  They should flow less with ethanol but that looks like a pretty extreme difference.
    • The idle VE is 22% in fuel table 1, it is 63% at the same point in fuel table 2. 
    • The multi fuel density and temp coefficient appears to be set for E100 but the stoich ratio is set for about E85.
    • The fuel pressure sensor calibration is wrong.  Fuel pressure also doesnt increase linearly with MGP, probably due to the same issue.
    • The min effective PW is set to 0.99ms, this is unlikely correct and will prevent you from achieving the correct lambda when running petrol.  More typical value would be 0.2ms.
    • The injector deadtime of 0.478ms at 14V is pretty unusual, not necessarily wrong but I would be doing some tests to confirm it is right.  
    • Not related to the current issue, but the boost control solenoid on Ign 7 isn't going to work well unless you have fitted your own freewheeling diode.  If not I would suggest moving that to a proper aux output which has freewheeling built in. 

    I'll go ahead and make changes to the boost solenoid wiring, minimum effective PW, and FP sensor calibration. Unlikely to improve everything much until the VE table and multi-fuel tables are setup right, then we'll go back to idle tuning. 

  5. 4 hours ago, stigc8 said:

    I had a quick look, a few things I would change. Set your Idle control to closed loop and fix your idle ignition control, its going the wrong way, something like this.

     

     

    idle.JPG

    Hey mate, I just had another look at this map, and I'm not sure mines backwards. If you retard the timing as the idle is falling, you're moving away from MBT and the engine is making less torque, which won't speed it up. Conversely, if the idle is above target and it ignition is advancing, the engine speed should increase. 

  6. On 1/22/2023 at 10:47 PM, Adamw said:

    C15 & 16 are connected together and both are connected to Aux 7.  This is because the STI has the fuel pump connected to C15 whereas the std WRX pump is connected to C16.

    If your fuel pump doesnt turn off that means your fuel pump relay coil must be "hot fed" (live all the time), this will cause a back feed when the ecu is off.  Anything that is connected to an Aux output must be supplied by an ignition switched 12V supply, not constant 12V.  So you will either have to rewire the supply to that relay, or if you have a spare ignition drive or injector drive then you could use one of those instead of aux 7 as they cant backfeed.  

    3thYZpv.png

     

    Thanks Adam, I ended up rewiring it and making it work. Good to know, appreciate the insight. 

  7. On 3/10/2019 at 7:58 PM, Alex Deyth said:

    Thanks Adam, what pin need to be wired to +14v to power the ecu ? D2-D3 to +14v and C17-A22 to gnd ?
    other pin are for powering something, like solenoids,etc right ?


    there is two Aux7 listed on C15/C16, who is who ?

    Did you ever get an answer to this mate? Currently working on my EZ30 swapped Liberty with this ECU and my fuel pump relay is wired to C-16, but it's apparently Aux 7 which doesn't turn it off

  8. 31 minutes ago, Vaughan said:

    setting the output polarity to high doesn't make it drive high unless it is set to be a high side driver. setting a Low side driver to high just means that it is now floating with a slight pullup to 12V.

    Oh, okay, I didn't realise that, thank you. 

    Is there any issue with leaving the ISC pinned to Aux 3 or should I move it? For reference, this is a factory 02-04 Outback/Lancaster H6 harness used with a WRX9 plug-in.  

  9. 7 minutes ago, Vaughan said:

    The high side drivers can't do pwm, can you rewire it so that you are controlling the low side and have an ignition switched power supply to the high side?

    I'm going to have to take another look. Clearly something's gone amiss. 

    I thought about my process. I switched to Test mode (ON) and the ISC clicked after I drove it high. Then, I went back to PWM test mode and it was responding to frequency. Very possible that driving it high loosened it somehow. 

  10. So, general update. Everything seems to be working. 

    Only little hiccup at this time is that the idle speed controller is, for some reason, wired to Aux 3 which according to the Link contents, should be wired to Aux 5, 6, 7 or 8. So, may need to repin that baddie as it also needs to be driven high, which is a bit confusing for my tuner. Tests confirm that with the ISC driven low, it will not work.

  11. On 1/5/2021 at 5:57 PM, Adamw said:

    As I said earlier:

    Hey Adam, I got the injectors all firing nicely, all sensors working etc. What I'm struggling with on this ECU, is cylinder 5 ignition and tacho output. With the WRX7-9 w/ Ethrottle model, the expansion harness starts with Ign cyl 6, not 5. Supposedly it's used as the tacho output, however that's not listed on the pinouts in the manual. So I have no idea which pin is used for the tacho, the FSM's for the model this ECU supports indicate it would be pin 22 on plug C, which is currently my cylinder 3 ignition. Can you/anyone shed some light on this? 

    Also, I have the tacho wire for my gauge cluster however, it doesn't respond to any output. That may warrant some further investigation. 

  12. Hey again Adam, 

    Thank you for your help so far, you are a legend! I haven't checked the base timing yet but I have confirmed the injectors and coils are wired correctly. I did assume they were given that it is a stock Outback harness, lol. 

    I also completed a better trigger scope for your perusal. 

    Cheers mate! 

    ez30triggerscope.jpg

  13. That's good news! Haven't been nearby the car for a minute so haven't managed to have a tinker. 

    I'll redo the trigger scope when I can and check the base timing. I found that the map has ignition outputs 5 and 6 set to "tacho" and "off" respectively, whereas injection outputs 5 and 6 are set to "engine fan 1" and "IC spray" respectively, also. Will these be corrected on the ECU when it gets turned over? Again, I'll have another look when I'm nearby :D 

    Cheers mate, 

    Tim

    P.S. some questions may seem a bit low IQ, I do apologize

  14. Howdy howdy, we're back again. 

    Made a couple log files, it didn't fire and the trigger scope looked... weird. I logged the standard running parameters and the trigger scope. NOTE: engine temp was high as I had driven the car recently with the stock ECU. IAT sensor appears to be faulty.

    ez30logfile.llg Trigger Scope Log 2021-01-3 8;36;04 pm.llg

    After checking the trigger scopes, it didn't seem to capture anything. Hmm. I'll have to try again.

×
×
  • Create New...