Mario Schneiderbanger

And lastly would i need to replace both cam and crank triggers for this to work or would just using the newer crank trigger and leaving the odd cam trigger be doable?

What if i switch to the AP2 trigger wheels? would that help? Photo attached I also found a thread where they opted to grind off 2 of the 3 cam trigger teeth to get the same result. Last few posts here: https://www.s2ki.com/forums/s2000-engine-management-231/crank-trigger-wheel-interchange-ap1-ap2-1177340/

I’ve been trying to optimize how long it takes for my engine to fire. I’ve attached a log. 03 S2000 F20C all stock. If you turn on the following parameters: RPM DI2 - Starter Switch Crank Enrich Prime Pulse Inj Pw Trigger 1 Trigger 2 You will see at 9.4 seconds my ignition switch goes active and prime pulse does as well. By 9.6 my triggers show active but the injector PW doesn’t show anything till 10.4 seconds. A full second after hitting the starter. ALSO you will see that RPM doesn’t start reading 200rpm until 10.4seconds. Is this normal and is there a way to decrease this because if that’s as good as it gets then that’s fine but if the injectors were to start pulsing right as the triggers arm as I thought they would then the engine would start a whole second faster. Ive been chasing faster starting by working on the Start fueling for a couple days now but Im thinking now that this is as good as it gets. Thx Mario Startup-log-s2000.llg

What if you started with stock injectors in traditional mode and have a solid calibration and now you’re switching to ID injectors and want to use Modeled fuel? Anything else besides the obvious: -flow rate -dead times -short pulse

Update: I was able to Use 3 Virtual outputs with ECT based conditions to vary the cluster output. It doesnt make use of all the bars since im out of conditions on the Physical Aux but its enough to know when the engine is warmed up. and overheating. May be able to add another Virtual aux to expand 2 more variables.

speaking of. Adam, when i use closed loop idle control and raise the AC step value, nothing happens. so i’ve been using open loop control cause i can’t figure out what i’m missing

Great news Once i figured out theres a 11 second delay before a bar will show up on the cluster each time a new bar gets added I came up with this. 1.25s is 1 bar 1.00s is 2 bars 0.75s is 3 bars 0.50s is 4 bars 0.25s is 5 bars 0.18s is 6 bars 0.10s is 7 bars Are we able to create a Table with ECT on one axis and SwOffTimer on the other?

Unfortunately no, maybe you can get some idea on what happens on the manuals section of the modifry converter. https://www.modifry.com/index.php?route=product/product&path=18_59ap2.htm&product_id=233

i’m open to try whatever the least complex solution would be. I’m not even against purchasing the converter box that already exists from Modifry products but for sake of other people wanting to run a link on their s2000 i think it would be good to have a solution to this.

Mine is AP1, I have a small amount of vague info from the guy who makes the converter box which was used to make the gauge work with older AEM Series one EMS but i don’t know how much help it will be. I asked why the instructions to his converter box ask what ECU you are using “stock or AEM series 1” his reply: “The ECT sensor bias resistor in the AEM is different than the resistor in the stock ECU, which causes the sensor voltage/temperature curve to change. For AEM, the set point for each gauge segment is lower than for stock, which is accounted for in the programming. The module itself is the same for all of our ECT products, the only difference is the initial programming for a specific application.” I then looked how AEM series 2 controls the gauge and it is done via a low side driver so I asked him the following: “One more question and you may chose not to answer. I know aemv2 and up as well as haltech already have the ability to output the proper signal directly to the cluster. AEM is using a low side driver at the frequency of 1-4hz with a duty cycle or 92-99% I tried to do the same thing with the link ecu but it has a software limitation to where i can only drop the frequency down to 10hz. Is 1-4hz the only way to drive the signal?” His response was: “It's the spacing of the pulses (Hz) that the gauge uses to decide how many segments to illuminate, and it's actually a little wider range than 1-4Hz, though the gauge isn't usually configured to distinguish those temperatures.” Hey richard, this works perfectly fine to drive the RPM portion of the stock cluster but it does not work with the ECT.