Jump to content

Brad Burnett

Dealer
  • Posts

    792
  • Joined

  • Last visited

  • Days Won

    38

Posts posted by Brad Burnett

  1. I recently did a ez30 from a legacy r in a impreza.  Worked out sweet.  from memory i had the vvl activation based off coolant temp, TP, and rpm.  Would only activate above 70 deg C, 60% TP,  and above 3000 rpm.  I tried to utilize the oil pressure switches that are one the heads as part of the strategy but it was flakey so I just bypassed that aspect.  It is purely just on or off.  

    As for your AVCS, you need to bump the PWM frequency to 250hz.  And from looking into your cal, did you  run the cam angle tests to get your tooth offsets?  I compared to the one I did and yours are a fair bit different.

  2. I didnt look at the cal posted here.  But when i was facing the issue a couple weeks ago, my cal did have APS main on the ethrottle table and the issue persisted.  Even though it would show the "h bridge polarity reversed" fault, it would still set the appropriate TPS main/sub voltages and i just had to verify the TP sub 100% value.  The ethrottle would work but had some very weird drivability issues that appeared to stem from a very noisy TP signal.

  3. 27 minutes ago, ScherzDaddy said:

    I will take a look at this. I do have multiple throttle bodies on hand, and I've tried to run this on two different units. Regardless of what throttle body I connect to the ECU, it gives me the same result. This leads me to believe its still a wiring or config issue. 

    Just to verify, you do only get the error during calibration at the very last step of the calibration process when the ecu is trying t close the throttle correct?

     

  4. I ran in to this problem very recently.  I would get the same error during the calibration process.... 75% of the time.  Sometimes it would calibrate with out issue.  I didnt have ample time to spend with the vehicle to sort it out, but it wasnt a h bridge issue.  I want to say it is a throttle return spring issue.  The fault would only occur at the very end of the calibration process and it would act as if the throttle is hung open while the ecu is commanding it to close.  If i had one of these throttles on hand i would play more with it on the bench and get to the bottom of it.

     

  5. 11 hours ago, David Marsh said:

    Which ecu to buy, a 4g+ thunder, or a 4gx extreme,when i am ready to buy a new ecu ,as i have a vipec v88, i am getting my engine built at the moment which is 4g63.

    David, the G4x extreme is light years a head of the v88 ecu.  Would be a direct swap and just need remapping.  If you need more IO would be the primary reason to move to a Thunder, but Im sure you could alleviate some IO constraints with some CAN integration via a dash or some form of expander.

  6. Im in Stuart just north of west palm.  I used to do a ton of subarus a couple years ago.  These days I do anything that pays, but prefer its on a Link.

    Hit me up if you need assistance.

  7. Yes it is possible.  

    Sounds more like a tuning issue from glowing cat and vibration described.

    I would verify Sync of the triggers.  Might have it set 360 deg out or mechanical timing issue.

    You should be able to get a good running engine with the dizzy.

  8. On 12/23/2020 at 10:29 AM, VtrSp1 said:

    @Adamw , i start the car and run perfect!

    I have only an issue,only  when i shut down the ignition  , the ecu have an error code 84  , Over-Current/Over-Temperature warning from the electronic Throttle Control hardware contained inside the ECU.

    I have connected the E-Throttle Relay 30 to the Main Rele 30 and the E-Throttle relay 86 to a Ignition Switch signal.

    02-Caterham485R ITB DBW SequentialBox.pclx 425.02 kB · 7 downloads

    @VtrSp1 I experience similar issues with the code 84.  I typically notice this upon initial key on before the engine is even started.  If you configure the DBW system to have "when stalled" setting set to "quiet" it will not happen as frequently, but still occurs.  It typically doesnt really cause any ill effects on operation, just an annoyance.  

  9. Ignition table 1 doesnt give me any issues.  But Ignition 2 is the primary one that started to irritate me.  This is while configd as dual ign tables that interpolate between.  Fuel tables configd the same does not produce the same results.  

    Other tables that do the same, just quickly looking through: GP PWM 1 DC, lambda target table 2 

    I think its pretty much that if you initially open a 3d surface view and the view is all wild and underneath, it will reset every edit.

  10. This is the second instance of this happening to me:

    When trying to edit Ignition table 2 in surface view, every single change i try to make resets the surface view to some inconvenient view.

    This is in modelled multi fuel equation with both fuel and ignition having 2 tables that interpolate between the 2.

    Any pointers on how to remedy this?

     

    Update, Im finding more and more 3d tables that constantly reset the surface view after even the smallest edit.

×
×
  • Create New...