Announcement

Collapse
No announcement yet.

ZWBEG and ZWOUT

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Well, on the V8 the knock control is done by different chip and totally differently. One that does not use an external memory.
    So I don't know - I can't tell you, I never reversed this.

    On 2.3.2 the signal from the main processor is sent as-is to the knock processor and the knock processor simply sends it to the correct cylinder (solid state distributor) and introduces a delay into the signal when knock control requires it. This delay is logged with prjmod per cylinder to output knock data.
    http://tuner.ee - http://www.facebook.com/tuner.ee

    Comment


    • #17
      At the moment I didn’t catch how the ZWOUT is impacted to this behavior.

      I can only guess. Need to spent more time to understand the code.

      I will investigate the second cpu binary too.
      I hope I don’t have to create communication between both CPUs to get a merged datalog..

      At the moment I’m happy how the engine is running.

      Next steps will be to read out the MCU, to check the schematics - possible one port is used for knock control on/off too and more testing with different fuel.

      One thinking is, ignition isn’t always knock limited, sometimes more advanced ignition produce less power - to find a was way to understand how much ignition is enough. Access to a Dyno isn’t easy possible. When do I improve fuel economy and when I worse it (part load).
      Full load I can check for the delta engine speed on the same road. Some full load pulls and I can check for the acceleration.
      At constant load I have to think about if load and tps are a proper way...

      Comment


      • #18
        Well yes, you can see how the merged datalog was created with prjmod.
        I can say it took a LOT of work to get the timing right and I am quite proud of it actually.
        http://tuner.ee - http://www.facebook.com/tuner.ee

        Comment


        • #19
          I’m sure that’s a lot of work!
          May some of the 5banger boys could make a datalog with RAM_53 and RAM_54 and we could compare :-)
          It’s nice to see how fast the fast path idle control works via ignition angle and also the other ignition impacting functions. :-)

          Comment


          • #20
            Fast path idle is simply a single map that gets activated when throttle is released, It's in the main ign angle.
            http://tuner.ee - http://www.facebook.com/tuner.ee

            Comment


            • #21
              You are speaking about code_2118 or code_44F1 (RS2 with prjmod)?
              The impact via code_44F1 you don't see at RAM_54.
              idle.JPG
              Last edited by Acki; 5 April 2018, 12:23.

              Comment


              • #22
                Has been too long for me to remember.

                Feel free to fix the logger though and update the wiki xD
                http://tuner.ee - http://www.facebook.com/tuner.ee

                Comment


                • #23
                  Ignition Angle = (Z-(Y-X))*0.75
                  Z = BM - XRAM_5F
                  Y = Ignition - IRAM_54 (ZWBEG)
                  Z = Idle correction angle - XRAM_167

                  I wouldn't say "fix" - I'm sure a lot of people didn't care about idle control ignition correction

                  I can write something into the WIKI but I'm a little bit reserved cause I don't drive a 5 cylinder or prjmod firmware...

                  /edit:
                  Idle ignition angles

                  ZWIdle.JPG
                  Last edited by Acki; 9 April 2018, 22:05.

                  Comment


                  • #24
                    knock.JPG
                    That's the "very" simple knock control of the V8 :-D

                    This knock control needs modifications ;-)

                    Comment

                    Working...
                    X