Curious to see a comparison on how fast different ECU's are able to start an S2K. Seems like with OEM and Hondata it's 3 cranks and a split second and it fires off. With AEM Infinity, so far what i've observed is about 14 cranks and about 2 seconds. I'm wondering if there's anyway to make the engine start any faster, I don't see any setings that would let it fire off faster. I wonder why it takes abit longer than OEM or Hondata.

 

I don't mind the slower start from the sync state from some of the ECU's. It give a little more time for oil to start moving. If my car sites for awhile, which is normal, I hold the throttle down and crank until the oil pressure light goes out. I've never had a slow start from the Infinity, but the V2 definitely needs some rotation to sync.

 

Standalones usually have a generic starting strategy (which can’t be changed on AEM). Whereas the OEM ECU knows all the specifics of the f20/22 and don’t have to worry about working on other types of engines so they make a lot of assumptions and can sync sooner

 

With the infinity you can set targeidle offset to a few rpm higher when first starting for a few seconds (has same effect of starting a car with throttle crackednopen to allow engine to breathe better)

I noticed the infinity is set by default to have cranking spark timing to about 1 degree. I will add a few degrees and see if that helps (more timing should make more torque and make the engine spin and start faster, Is my theory anyway).

Now im curious what cranking ignition timing is on OEM or hondata ECU if anyone knows thatd be great info to compare.

 

Start-delay is a feature on some higher end ECUs, to build up oil pressure, I know we all want that crisp start (including me) but just food for thought there.

Also, it is not until cam and crank signals are in-sync that AEM infinity fires-off. AEM was very up front about this (although it took time for them to respond on the forums) that this was not designed for street/oem like start.

I will post my start results soon on this thread, as I kept trying to shorten them in NE freezing cold weather. I am also looking forward to updating my firmware to the latest and seeing if that helps.

 

Seems like it takes 2 seconds to start. 1 second to 'Sync' and then 1 more second after synced. If any progress is to be made it seems we can work on a faster start right after it's synced.

 

This is a nice new feature, seems like we can add fuel before the ecu even syncs, i'll be trying this for sure. I run E85(always 80%content around here) so think i'll dump a bunch of fuel and see if there is any difference in start time after ecu has syncd

 

So this was one of the biggest reasons I moved from the AEM Infinity a Haltech Elite 1500. The starting with the AEM was ridiculous at times, like the OP said 14+ cranks, and that's if it didn't kill the battery. With the Haltech, it's 4-5 cranks every single time.

 

Anyone looking to share their datalog of the car starting set your engine rpm range to show from 0 to 600 and thats how you can basically see and count how many cranks it takes. It does not inspire confidence having the car take so long to start but aslong as everything is on sync while the engine is running im happy for the most part. If any hondata guys have access to the oem spark timing while cranking that would be great info to plug in and compare. Infinity ecus basically set all crank timing in their basemaps to about 1 or 2 degrees. Also there is a new option with the new version of Infinity

Cam Error Ignore function added for using the cam signal for sync at low RPM and ignoring potentially noisy cam signals at high RPM

 

I checked an old datalog with a 6 year old needs to be replaced battery and my infinity takes 1.1seconds to get syncstate =1 and then another 0.6 seconds for RPM > 600

14+ cranks sounds way too long but I can't say I've ever sat there and counted the cranks