Jump to content

Vaughan

Moderators
  • Posts

    2,103
  • Joined

  • Last visited

  • Days Won

    74

Posts posted by Vaughan

  1. that scope looks like you clicked capture before you started cranking instead of while you were cranking but it caught some teeth right at the end.

    Change your Trigger 1 arming voltage table 500RPM cell to 0.2V as your tooth voltage is pretty low.

  2. Your trigger settings are wrong, it never syncs properly.

    To confirm do you only have a 36-2 trigger wheel on the crank connected to Trigger 1 and nothing connected to trigger 2?

    How many wires does your trigger sensor have? 2 or 3?

    Do a trigger scope and attach it here, ecu controls -> Trigger scope and then press capture once the engine is cranking and keep cranking until the trace shows up, save it and attach here.

    Your more recent log does seem to show it syncing but I still want to see an actual trigger scope.

    You can test your timing light by doing an ignition test as this will just continually trigger the coil without needing to crank the car

  3. I can see Closed Loop Lambda maxing out, I suspect you have an exhaust leak upstream of the wideband which causes it to read lean and then the CLL tries to correct by adding a bunch of fuel which makes it run badly.

  4. The trigger scope is the correct way to check trigger sensor outputs, multimeter will just show you an average voltage over a reasonably long time, not the actual waveform. Have you seen the engine speed in PCLInk drop to 0 while holding it at a high RPM? do you have any logs of this? if so attach a log showing this and a copy of your basemap.

    In terms of the PCLink connection issues what spark plugs and ignition system are you using? PCLink connection issues at higher engine speeds can often be attributed to ignition noise.

    There were also some hardware improvements made for improving PC comms which early plugins don't have, attaching a picture of the ECU's top board and the serial number would let us confirm if your ECU has these modifications or not.

  5. There is some trigger and firing order info in the PCLink help file (as pictured below), if using factory injectors you could use a traditional based fuel tune with a master fuel of maybe 10-15ms to start with, other than that generic fuel and ignition tables from one of the EVO sample maps should be enough to get it started and running once you have tested your wiring and found the correct trigger offset with a timing light.

    Capture.PNG

  6. The ECU output isn't PWM, it is synchronous to the engine speed where it turns on and off at very specific angles relative to the specific cam the pump is on, if your PDM can do peak and hold control and you can guarantee a consistent and small deadtime between the ECU output and the PDM output then yes you could do it with the PDM. If you want to try running a constant but higher current through it then maybe a FET or a solid state relay with a smaller or no ballast resistor would work.

    Just to reiterate from memory the Life setup had ~6A of peak current and 2.68A of hold current. To make it move you most likely require close to that 6A of peak and so if you ran a FET or solid state relay with appropriate ballast resistance to get 5-6A you could just run it at that full current the whole time and then keep an eye on whether or not you overheat the pump solenoid.

    Alternatively we are in the testing phases of our DI drivers which include a pump driver but I'm not sure when they are going to be available for purchase.

  7. Given that your fuel table is doesn't seem to get above 41, apart from 3 weird cells in overrun, you might be better off with a master fuel of 8ms and doubling the values in the fuel table. This will give you more resolution to play with.
    Also I suspect those weird fuel table values in overrun are due to it misfiring because of very low vacuum and so reading lean.

  8. I'm not the most knowledgeable with Subaru's but yes it looks like earlier vehicles get AC Request through a physical pin and later vehicles through the CAN bus, I have clarified this in the pinout diagrams.

  9. Your E-Throttle is jamming shut, in the 2nd log you do a blip and when it goes to shut the throttle it overshoots and goes all the way to 0% where it stays. A lower minimum clamp would reducer how hard it closes it but I would say you need to visually inspect your throttle to see why it is staying jammed shut even when you are trying to open it as hard as possible.

  10. 28 minutes ago, don17 said:

    is there anything i can do with the minimum frequency to stop it jumping up so fast? its not a big deal tho

    As far as I'm aware it is a hardware limitation on the G4+ ECUs

  11. 45 minutes ago, don17 said:

    That is a basemap(.pclr) file not a log (.llg) file, you made the same comment earlier.

    The Multi of 0.83 I provided earlier was based on your other thread where you said you were doing 120 when it said 100.

    DI 1 has a calibration value of 200 so 10Hz input is about 18kph and from memory G4+ PWM outputs have a minimum frequency of 10Hz so that would explain why it is jumping to ~20kph immediately.

  12. 1 hour ago, don17 said:

    I really don't know what these values should be I'll try that today tho and get back to you

    Help manual explains what each of them do, just single click on one of them and press F1

×
×
  • Create New...