Hondata

Just got car running again on turbo setup and drove over 200 miles, throttle response not the best but seemed to run fairly strong. After hooking up boost pipes ran another 100 miles and car seemed to cut spark or something whenever the car at WOT.
Next thing car starts dying in middle of the road and will not start, just cranks similar to if a ignition coil had gone bad.
Managed to get car back but coasted into driveway.


Car seems to be throwing a 6 and 21 code VTEC spool i think tried reflashing with spool error check disabled but car still wont start.
The main relay seems to be good as fuel pump comes on everytime the key it on and I changed ignition coil already as well.

Has anyone experienced this condition, I just upgraded to S300 and was having a similar issue before.

Thanks

Has the car been tuned? What engine? What size injectors? Are you running a wideband?

Everyone is going to ask you to post your calibration and a log of the issue.

You'll need to check the wiring to your ECT and your VTEC solenoid.

Using tune for this setup from before upgraded to S300. B18C, 650cc No wideband.

Im new to S300 and coming up to speed on how to datalog and record and save the file. Tried reading the CEL codes through S300 error area tab but nothing ever showed up yet the CEL flashes.
Where is a good place for tutorial on how to read error codes and save the issue once you have datalogged?

A faulty VTEC Solenoid should not stop a car from starting though.

code 6 is coolant temp sensor. And if that is bad it can definitely cause a no-start condition, especially if the tune is not dialed in correctly (professionally)

Attached is the no crank start.

The check engine light is flashing codes 6 and 21, however no code is being shown in the error section of the S300 software.

Anyone else experienced this?

What MAP sensor are you using?

The stock one, it has never been changed.

My understanding is the stock MAP sensor could handle alot of boost, but is 11 psi too much for stock MAP ?

Why would S300 error window not show any check engine codes yet the MIL flashes as if I have it jumped out?

You need to post the calibration used to make the datalog.

Here it is.

Try creating a new calibration as I can see -100% ECT and IAT corrections up to and during cranking.

I created a new calibration from the B18 supercharged just to determine if it would start and idle. It started up and idled running good at normal operating temperature but then stalled. After this it would not start only intermittently and now it almost starts sometimes but only when turning the key back from the crank position. The car actually almost starts in between the (ON) and Crank key positions.
No spark when cranking (used timing light and no spark except when turning key backwards) except when it tries to start in between ON and crank positions, just changed to new ignition switch and lock cylinder too so does not behave any different than with the original ignition switch and lock cylinder.
Getting voltage at fuel injector connector and plugs and car smell of strong fuel after trying to crank several times. Things seem to be worse as car wil not start at all with 650cc injectors and turbo on.
Only error getting is code 15 but does not always show up when datalogging.
Also car will start and run in past on stock computer so I starting to think this is Hondata ECU issue.
Additionally, with stock injectors and NA the car runs fine on stock computer.
Before sending S200 in for upgrade to S300 cut J1 and car also ran fine NA.
Attached is another datalog with supercharged calibration.

Can you post a datalog showing it running and the error codes that it gets?

Just used stock ECU and car started just fine even with oversized injectors and turbo on. With upgraded S300 will not start.

It will not start seems like code for 15 Ignition output seems to be coming back often though when attempting to start.

The computer reads rpm when the car is not even being cranked.
I've attached an attempt a datalog when attempting to start car.

You have only attached the calibration, and not the datalog showing what it is doing.