Jump to content

essb00

Members
  • Posts

    367
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by essb00

  1. You can make a time plot and parameter list. You can see the lambda status as you move the time plot slider (like below). *Check the fault code descriptions in the help file.
    image.thumb.jpeg.5a8eecc5fa3b6b4f4cd18ce077cd1946.jpeg



    You may be able to get around it by changing your COPs to wasted spark instead to free up two ignition channels and use them for VVT and fuel pump. You need to use a dedicated aux output channel for tach signal.
    Which pin on the 34-pin connector is that spare connected to?

  2. Up to this... Sorry for hijacking this thread...

    I was able to make the fue level work (adjusted with the components I have available as in the below pic) --- I got the high level (as of the moment the tank is full) but I have to wait for the actual reading of the empty level to adjust my linear calibration. The full sweep of the floater seems to read 0.675V to 4.900V.
    *Vehicle also on 4-120 Ohm unit.
    *10SQ050 Schottky diode for isolation added - as the stock gauge 12V fuel level sensor is still connected in parallel.

    Edit: Too much fluctuation on fuel sloshing in tank. I changed the 10K to 100K Ohms. 

    image.png.09da99dcede2e7904222bdbffcdca875.png

    @Adamw Ummm... I have the fuel level assigned to 'MAF Meter' to make it show in OBD2 (just changed the label on the app, but I cannot change the unit showing). I'm wondering if there's any better option - while there's no dedicated analog input for 'Fuel Level'. B)

  3. 4 hours ago, Adamw said:

    You dont have CAN Aux 1-4 assigned to anything in your map so they will be outputting a "2" via CAN.  When you set it to test they will be outputting a 1.  

    So most likely the ECU master device considers anything >0 to be "on", so you wont see any difference between the two states that the ecu is sending and the switchboard wont handle "Off" or "Fault" statuses correctly. 

    If you actually assign CAN aux 1-4 to the function you want to use them for then the inactive/active states will at least work correctly.  

     

     

    Oh, wow... You're absolutely right... :o After I assigned a function and did the test from there, all 4 CAN Auxiliaries worked as they should.
    Thanks! :lol:

  4. CAN Aux 1 works as it should with this setup - has 'High' at inactive state, 'Low' in active state,
    ....but not CAN Aux 2, 3, 4 (inactive states are in 'Low' --- quite complicated, more described below).

    image.thumb.png.e81a3d6834226de2058446a087016610.png

     

    Some combinations I've tried and the outcomes: CAN Aux 2, 3, 4 (inactive states are in 'Low')
    Whenever CAN Aux 2 'Test' is turned to 'On", CAN Aux 3 turns 'High'.
    Whenever CAN Aux 3 'Test' is turned to 'On', CAN Aux 4 turns 'High' --- and CAN Aux 3 turns 'Low' (when is already on 'High').
    Whenever CAN Aux 4 'Test' is turned to 'On', CAN Aux 3 turns 'Low' (when is already on 'High')

    Confusing, isn't it?

  5. Hi...
    First time setting up ECUMaster CAN Switch Board V3.

    I just finished all the soldering and have tried to connect and test.
    All 8 CAN Analog Inputs and all 8 CAN Digital Inputs have been tested working. However, all 4 CAN Auxes do not work -- they constantly read +12V even with the CAN Aux Tests.

    Did I miss anything? :blink:

    Thanks...

    image.thumb.png.481740edf3165ad5b827fad89b805991.png

     

    image.png.9f620693cdf3b95a67a4738ac13e2ca0.png

  6. 18 hours ago, Oprah_152 said:

     

    Virtual Aux

    I don't see the new virtual aux channels 9-12 available for use when I go to choose these parameters. (not on my critical path, just observed this.)

     

    You might have gotten confused... GP Output 9-12 were added in the latest firmware, but nothing was mentioned about Virtual Aux 9-12 in the release notes..

  7. Stalling has more to do with the idle control trying to go to min clamp while you're on engine braking (no speed lockout).
    Oscillation is because of both idle speed control settings and too early overrun fuel cut.

    Overrun fuel cut activates too early - due to no activation delay.
    Put ORFC Activation Delay 1.0s, Torque Reduction/Introduction Time 1.5s

    Ide Speed Control
    Speed Source Lockout - Driven Wheel Speed
    Speed Lockout - 10 kph
    APS/TPS Lockout - 0.5 %
    RPM Lockout Above Target 500rpm

    Integral Gain 0.3

    Try those, then do another log, then upload including the updated tune file.

  8. On the last log, I can see that your lambda dips on closing throttle and takes too much time before recovering. You at least have to tune your fuel table to the idle regions before fine tuning the idle.
    Plus, I recommend put maybe 10-20% for Wall Wetting Compensation.

    Closed loop lambda low rpm lockout change to 500rpm.
    AFR Target table at least put 14.7 for idle regions as well. Are you using pure gasoline (no ethanol)?

×
×
  • Create New...