Jump to content

Iguanapeluda

Members
  • Posts

    43
  • Joined

  • Last visited

Posts posted by Iguanapeluda

  1. On 1/31/2021 at 10:12 AM, Adamw said:

    I havent looked at your log, but it doesnt look like you are too far off.  Your noise looks a little more erratic than Im used to, whats your frequency channel and start/window set to?  Does your engine still have the stock 2 tooth crank wheel?

    Your noise levels increase quite a bit during transients so your delta threshold gains need to be a bit higher (so the threshold steps up higher during transients).  It also looks like your normal threshold may need to come up to about 2.5 to get it above the odd bit spike of noise you have.

     

    Thank you Adam for your time!

    I have OEM tooth crank wheel, and i have upgrade the knock sensor for a Bosch sensor. I will modify the threshold gains for the following log´s.

    My configuration is the following (now)

    image.png.b4a1bce43123200cd4f018591a29e5cb.png

     

  2. On 12/5/2020 at 3:21 PM, mapper said:

    I've helped with development of the new knock normalised mode and done lots of Beta testing. 

    The Knock Normalised Mode has the big benefit that it will adapt to increased noise level, when your engine wear over time and consequently produce more background noise. In tradional mode this will lead to false knock detection. In general speaking Knock Normalised mode will  adapt to changing background noise levels and should need less adjustment from engine to engine, once you have a good basemap worked out. It also allows better adjustment how much ignition retard is applied, based on knock level detected. 

    It is meant to use all the tables, which are shown in PC LINK in this mode.

    I would start with a small Knock Target Table. Break points every 1000rpm and on y-axis every 50kpa (boosted engine) should be sufficient. A filled table of 2.0 should be a good to starting point.

    During transient engine operation the knock levels are going higher. In the tradional mode lockouts for delta rpm and tps where set. In Knock Normalised Mode it is meant to use all the Knock Transient Tables to keep knock control active all the time. The Knock Normalised Levels will increase even more, during transient operation, than in traditional mode. The idea with all the transient threshold tables is to increase temporarly the knock treshold, instead of just deactivating knock control. 

    As a starting point fill the Knock Normalised MAP and RPM Delta Level tables with factor 1.5. 

    The Knock Normalised Delta RPM and RPM threshold defines when the knock multiplicator above is applied. Setting is very dependand how stable your knock engine speed ROC and knock Map Delta channels are. If there are too noisy you can apply more filter to get this channel(s) smoothed. 

    I recommend the following order for setup and tuning. 

    1. setup function as suggested above

    2. adjust knock noise filter (same process as in tradional mode)

    3. calibrate knock target table in steady state conditions

    4. calibrate all knock transient tables, so knock target is little above knock levels in all knock free transient condions. 

    Notes: 

    - you can calibrate knock input filter also in tradional knock mode. This setting will be the same in both modes. 

    - it is normal behavior that knock normalised levels go higher during transient than in steady state operation

    - as always when you calibrate knock detection system use knock ears! 

    - Important knock level detected must be logged with internal logger with at least 200hz (better more) to show peak values correct in PC Link

     

     

    Thank you for this explanation, today Yesterday I have make a log with my lancer evo ix, with your guide, but now....I have a hard time interpreting it..

     

    image.thumb.png.4b15205514f1411640cf4240b29688dd.png

    I don´t know if I have well configured:

    image.thumb.png.a350d198319b527483ce1a41d2d09f9d.png

     

    PC Datalog - 2021-01-29 7;42;05 pm.llgx

  3. 15 hours ago, Adamw said:

    Sorry for the slow reply.

    We dont allow cyclic idle to be enabled when engine type is "Rotary".  This is because the unique cutting sequence that a rotary requires will not allow cyclic idle to work as intended.

    Thank you for the replay. I Understand that the cyclic idle DON'T work's good with 2 rotors..

    Javier

  4. 3 hours ago, Grant Baker said:

    If you send me your tuned file I will alter some settings to get you some pops and bangs if you like?

    I am interested too!!

     

    I attach my 3 cars with link, EVO IX (pre_cut), Nissan 300zx Z32, (llamas_iguana), Rx7 FD3s (arranque_frio_link).

     

    If you can make any change, I will very happy, because I don´t have too pop and bangs.

     

    thank you.

    LLamas_iguana.pclr

    Arranque_frio_link.pclr

    Pre_cut.pcl

  5. Hi!!

     

    I have a Rx7 with StreetPort and I have a smooth idle...your problem I think that is the diference of values around the idle rpm..

     

    Try to modificate and put the same value of fuel and Ignition at the idle island..like this:

    image.thumb.png.9974ee1d3a2074a9d15f78c6076dcb2a.png

    And the fuel table.

    image.thumb.png.5caac2da151a1f292a1626d10f0fdb11.png

  6. Hi!, 

     

    I have a Mazda RX7 Series 6 with a Link G4+ plugging.

     

    I try to Activate cyclic idle and Antilag and the systems don´t activate, I put a Screenshoot.

    image.thumb.png.f114da8f5173a43b89cd953bbd9d86f4.png

    Then, I will accelerate up to 1500rpm and TP of 2% and the system don´t army.

    image.thumb.png.cc03344971fcce39b905fe73f1212086.png

     

    I have another LINK G4 + installed in a Nissan 300zx and Mitsubhisi EVO IX and they works with antilag with this settings, I think that is not activate to Rotary engine???

     

    Thank you.

     

    I attach my log and my map.

    link.llg

    Arranque_frio_link.pclr

  7. Hola,

    I noticed in the photos above that you have DI 1 set to Inlet /LH. However you also have Trig 2: VVTi set to Inlet / LH.

    You should only have one of these set to Inlet /LH. On our EVO 9 plug-in ECU a digital input is used for Inlet /LH position and the Trig 2: VVTi is set to OFF.

     

    Hi Scott!!!

    Thank you for the information, today I have modify the map in my EVO setting OFF the VVTi "trig 2" and the error pulses don´t up the counter..

    Javier.

  8. Hello!, I am from Spain, I have a Evo IX RS with LINK G4 and I am starting in this world....

    I have vievew that I have in the VVT menu the Error Counter because there are extra pulses.

    6zo3ms.jpg

     

    Then, I have make the test of the pulses of the trigger and tell me the following with (6 Pulses), (42.7º).

    308yxib.jpg

    Then, I have changed the offset and the counter increase another one..

    2ir83dc.jpg

    14ih4xl.jpg

    And I have make a video in youtube with 40º and then with 42.7º, and if you view that, the solenoid make 100% and the position don´t move...

     

     

×
×
  • Create New...