INSW20

This seems to work decently well on my 5sgte. I am running a coil-on-plug setup, which is how I have individual trims and gains on a g4+.

I tried running my 3sgte and another 3sgte on the stock sensor and it saturates the input (aka knock control becomes useless after a certain rpm and MAP). Swap to a Bosch donut for more reliable and useful knock signal. http://www.bmotorsports.com/shop/product_info.php/xrf/gshp/products_id/4518?gad_source=1&gclid=CjwKCAjwuJ2xBhA3EiwAMVjkVNdLZLrzikQx3wQzBTUnt02IC3R80bi5IamVGhI2KTR8Z4DgRlankRoC5_4QAvD_BwE I wired it to the single knock signal wire and then to the stud for ground. Maybe not perfect, but seems to read well, and consistent.

Yes, stock Toyota sensor on 3sgte. Global gain set to 1 already. Thanks! Looks like a donut is in my future.

I have been looking at logs recently, and noticed that even when Knock Global increases, Knock Level is capped at exactly 1000*Knk Level Gain. In this case, the gain is at 0.53, 4cyl using a distributor. Is this normal? The car is currently running 100 octane race gas, with what should be fairly reasonable ignition timing for 91 pump gas.

Why is TP main ramping up during cranking? E-throttle? Can you attach a copy of your tune?

Yes, I should have mentioned I also pulled out almost all hot pre-crank prime and reduced hot crank enrich. That also helped a lot. Thanks!

Update: seems like injector timing was a big part of my issue. I have since updated to the following: Cold starts are still great, and hot restarts are very nearly as good; a HUGE improvement. I am now blending down and testing "warm" 130-140F restarts, but seems like it's moving in the right direction.

Yep, that does help, I guess I was hoping for clarification where it says "the first time the key is turned to the start position." If I leave the key in the "run" position after it dies, does it prime again when I go to "start" or does it skip that since it's no longer the first time the key is turned to the start position on that key cycle. I ended up removing basically all of the pre-crank prime when hot and it seemed to like that a lot more. Thank you!

Does pre-crank prime only occur on the first crank after a key-on? So if I key-on a hot engine, then go to crank, it primes, then chugs to life, dies, and then I crank again, there is not a second pre-crank prime?

9.13.2023 - hot restart in garage.llg5sgte - 9.13.2023 - playing with hot restart.pclr9.13.2023 - hot restart in garage number 2.llg Added a couple heat-soaked logs and my latest tune file. It "seems" like it kind of wants more prime pulse and crank enrich, but I would appreciate any input you folks have. My cold starts are AWESOME. My hot restarts it kind of chugs to life, sometimes it will die and then start right up on the second cranking attempt.

I'm struggling to wrap my head around the best strategy for hot restart. IAT sensor is about 3" pre-throttle body in my charge piping. I had read previously that enabling IAT fuel trim and adding fuel in the 0% TPS "hot soaked" cells would help significantly with hot restart, but I'm still struggling. More recently, someone commented that charge temp approx is a much better method for fueling hot restarts. Any suggestions appreciated. It seems to me like it wants more fuel on hot restarts. 5sgte - 8.17.2023 rev1.pclr

Yep, that seems to have fixed it. Per usual, it's user error on my part. =)

My Gear Status seems to drop out frequently, especially during acceleration. My road speed seems to show consistently, so I don't think it's a sensor dropout, but I've been wrong before. 5sgte with E153 transmission, using a hall effect cruise sensor wired to DI4.

I think I was experiencing the driver issue. I ran the driver installation program and it connected immediately. I also was using the Belkin adapter, which I'll leave in the car now.

I recently got a replacement laptop that has only USB-C ports. I tried the Dell adapter (USB/HDMI combo adapter) and just tried this Syntech adapter: https://www.amazon.com/dp/B07CVX3516?ref=ppx_yo2ov_dt_b_product_details&th=1 Neither will allow for ECU communication, but at least using the Syntech, the ECU shows up in hardware: What am I doing wrong? Or do I need a different adapter?

You are 100% correct. Sorry, user error on this one. I had a couple different 22psi dyno run logs and opened the wrong one.

EDIT: user error. disregard.

If needed, I can try to replicate the issue during PC logging this weekend, if the log on my google drive isn’t useful. Thanks!

https://drive.google.com/file/d/1azd1aS62p5CD-drrNCbXlb7Neb1oWWAD/view?usp=sharing Full log file attached.

I have oil pressure logged, at the blip attempt oil pressure is at 45psi, puts the limiter at about 5000rpm. Hot idle oil pressure is about 26-28psi at 1000rpm. Unfortunately my ECU log doesn't have GP limit 1 or Ign cut logged.

Am I sucking too much fuel off the port walls before I blip my throttle? Or what else am I doing wrong? Usually my blips are just fine, but on my drive home today (~40 miles) I had two instances after some engine braking where I had no throttle response. Tach stayed running the entire time, so I don't think it was trigger related. First time I was engine braking down a hill, got to the bottom and eased back onto throttle and had zero response. (no log available, ECU log filled up) Second time I was trying to blip for a downshift and had a dead pedal. Engine didn't try to die, just didn't pick up. Pretty sure this spot in the log was it. 5sgte - 2.13.2023.pclr

To close the loop on this one, I wired in my cruise sensor to DI4, and ended up turning pullup On to get it to read, for anyone else considering doing this. Now I just need to calibrate against GPS. So far so good!

After a minor issue, wires are swapped, and updated the arming threshold to 0.5V during cranking. Does this all look good now? Thanks! Trigger Scope Log 2023-01-5 9;07;33 am.llg

Before.... =( I'll go try it again and only click capture while cranking Turns out I'm a rookie. So while we're here, how does this all look? A friend suggested my polarity might be backwards on my crank trigger. Trigger Scope Log 2023-01-4 9;43;51 pm.llg