Jump to content

Brad Burnett

Dealer
  • Posts

    792
  • Joined

  • Last visited

  • Days Won

    38

Posts posted by Brad Burnett

  1. 1) Move 19 to 34 don't need to reinstall 34 into 19

       wide band can go into either 29 or 55.

       oil pressure signal can go to which ever was not used for wideband.

      both aem signals will need config in ecu.

    2) as long as power and grounds are in the appropriate locations power up should be ok.

    3) yes you can trigger a 70amp relay with the ecu.  All the ecu is doing is grounding the coil in the relay, not carrying any real load.  Yes this could go to pin 19

    4) just hook the solenoid up to the factory boost solenoid connector.  Power and ground can be either way. will need to be set up on aux 1 as wastegate solenoid

     

  2. If you download the PCLink software, open the atom base cal, and look in the motorsports tab it only has "gear shift control".  Gear shift control is the "flat shift" config.

    The atom is the stripped down entry level ecu.  Some of the motorsports features such as launch control and antilag are removed from the unit to make it more affordable.

    To do launch control you will have to have a GP Rev limit configured.  There will be a bit of imagination required to make it optimal.  

    My recommendation would be to go with a high level ecu such as the Monsoon or the Storm to get all the features that  you are after.

  3. based on the cal the that you loaded, you have only set the 0 rpm column to .96 lambda.  That will do nothing for you at idle considering that your idle speed is roughly 900rpm.

    You will need to set that value from zero to at least 1000 rpm and span that from 20kpa to at least 60kpa as the idle MAP is roughly 50kpa.

  4. Lambda looks pretty solid in all areas except where you are blipping the throttle. 

    You could always richen up idle a bit via the AFR target table  and some slight massaging of the main fuel table.  

    I have even setup the latency table to be 3d with battery voltage on one axis and rpm on the other and played with latency at idle to get the idle a bit smoother in the past.

    I don't think that it is actual misfire.  I think you have a bit more tweaking to do in order to get it optimal for your preferences.

     

  5. Based on the log and the attached cal file, it appears there may be something a miss in your ethrottle set up. 

    If you look at the AP% main it looks like you are sitting there blipping the throttle the entire time during the log and the ethrottle is reacting and opening the throttle as it should when it sees throttle pedal input.

  6. You can make it work.  I have looked at the pinout in the help file and you are only missing the 12 pin connector on the ecu.

    All the other connectors have the same pin number count, so moving pins around to match would be a very viable option.

    I'm sure if you whisper sweet nothings into either @Adamw or @Simon ears, they may be inclined to send you their internal ecu pinouts to aid in the adaption.

  7. It depends  how you have the engine wired up.  But I tend to wire it up with cyl x inj and ign going to cyl x on the engine based on position, then set firing order in ecu.  Some ecus suggest wiring cyl 1 from the ecu to the first cylinder to fire and cyl 2 to the second in the firing order.

    Ecu doesn't have the ability to trim fuel based on O2 sensors for specific cylinders.

    Attached is a screen grab from the fuel tab in the run time values.  The individual cylinder trims are from individual cylinder fuel trims applied by the tuner to compensate for afr imbalance from slight inconsistencies due to ITBs.

    link runtime values fuel.jpg

  8. to convert lambda to afr, simply multiply the lambda value by the stoichiometric value.

    ex:

    lambda of .9x14.7 = 13.23 afr gasoline.

     

    It is much easier with the link ecu fuel equations to just deal with everything in lambda, especially if you are using multi fuel equation. This is be cause lambda is the same across all fuels, while the actual afr scale varies greatly.

  9. Funny story, one of the first link units I ever installed, some 8-10 years ago,  customer had a ej20 Subaru.  Guy was picking up his buddy, so instead of calling him or honking the horn, he decides to stand on the launch limiter to get him to come out.  Stood on the limiter long enough that the valve train got unhappy and spit a shim.

  10. 2 Bar should be fine but I believe link offers a 2.5bar unit.

    I ran a 3.5 bar Map sensor on my 1uz NA for a long while.

    I would recommend to of the link units as packaging is much nicer, but 2 AEM xseries will be fine as they can also work over CAN.

     

  11. 1) yes it can retard timing in the instance of knock once configured correctly.

    2)Yes it has injector scaling and VE map

    3)I would assume that the latency for those injectors would be very similar to the yellow 550cc Subaru Sti injectors.

    6v 4.9ms

    9v 1.72ms

    12v .88ms

    14v .67ms

    16v .48ms

     

     

     

  12. It is possible to burn all coils at the same time.  Some other individual on this forum had that happen do to incorrect spark edge selected, but yours is correct.

    But now after looking further at your calibration, I do think your dwell might be a bit high for the coils.  I would be running about 1ms less at operating voltage.

  13. You need to lower your cam sensor arming threshold down low.  It doesn't rise past +0.48ish and your threshold is 0.5 at 0 rpm.

    Also there is a ton of noise on the cam sensor.  Is this a harness that you made from scratch or is this a stock MR2 harness?

    If stock, I would suggest running the crank/cam wires externally to the harness with new quality shielded cable.

×
×
  • Create New...