Manual chipped p28 throwing code 19.. Yes it's a MANUAL ecu
I originally posted this in the 92-00 civic forum but after no responses I realized that was definitely not the correct section to post my issue. Here goes:
Went to the dyno today with a chrome basemap installed in my chipped p28 (manual) and as soon as he hooks up the laptop to the socket to make changes it throws code 19 for auto ecu and will not engage vtec. I have double checked and triple checked it IS a manual ecu. And when he puts my basemap chip back in it no code and vtec engages. Any help would be greatly appreciated.
Also here is the link to my original post with a little more info:
https://honda-tech.com/forums/showth...6#post47211046
Went to the dyno today with a chrome basemap installed in my chipped p28 (manual) and as soon as he hooks up the laptop to the socket to make changes it throws code 19 for auto ecu and will not engage vtec. I have double checked and triple checked it IS a manual ecu. And when he puts my basemap chip back in it no code and vtec engages. Any help would be greatly appreciated.
Also here is the link to my original post with a little more info:
https://honda-tech.com/forums/showth...6#post47211046
My guess... Your ecu may not actually be a manual...?
Open the ecu and look at the bottom where the chip goes... RP17 should be empty and you should have a 0 ohm jumper not a resistor in RP18.
Open the ecu and look at the bottom where the chip goes... RP17 should be empty and you should have a 0 ohm jumper not a resistor in RP18.
Yes sir it's exactly as you described. Like I said, I double and triple checked. It's most definitely a manual.
If you're sure it's been converted to manual (RP17 completely removed with nothing in it's place and no solder bridging the gap), then you've likely miscounted the code it's throwing. 
Option 1: Read your chip in then upload that to the emulator and work from there.
Option 2: Disable the main options on the new basemap and see if it still occurs. Likely something is enabled on this map that isn't enabled in your basemap.
Option 3: Recount the code it's throwing.

Option 1: Read your chip in then upload that to the emulator and work from there.
Option 2: Disable the main options on the new basemap and see if it still occurs. Likely something is enabled on this map that isn't enabled in your basemap.
Option 3: Recount the code it's throwing.
It was most definitely code 19. And another issue was the tuner could not get his laptop to read the basemap so he had to start from scratch. I'm stumped. I honestly think it is something that is set wrong on his chrome software. We shall know if another ecu works come Monday at 1:00. I have confidence in my tuner. They usually do spot on, top notch work and they are really nice people.
Are you sure it's not code 10 and 9? Try a fresh basemap, I can send you a working file. Otherwise you're obviously experiencing circuit damage. Try removing J1 and see if it's a stock side issue first, if you still want to troubleshoot this ECU.
Thread
Thread Starter
Forum
Replies
Last Post
jonathan13
Honda Civic / Del Sol (1992 - 2000)
2
Apr 20, 2012 09:36 AM
delsol242
Honda Civic / Del Sol (1992 - 2000)
1
Mar 13, 2012 10:16 AM
Preludepradit
Engine Management and Tuning
5
Jun 11, 2008 08:59 PM
Cuda
Honda Civic / Del Sol (1992 - 2000)
5
Apr 9, 2008 02:03 AM





