Crome pro v1.6.9 cel code 22 and code 26
I have a socketed p28 that I purchased from a hondata dealer some years ago.
I've used it with their s200, and now with crome pro.
Currently I'm street tuning my EF:
B18c5
Jrsc @ 7.8psi
Gsr / itr cam combo
550cc RC injectors
Bolt ons
History is that this was a big cam itb setup, but I bent some valves and replaced the head, and switched to a jrsc for autox.
I've been tuning the low cam maps without issue so far.
I start the car, and no cel lamp comes on at the dash light, but in the crome data logging window I get a cel ON and the code is 26: unknown ?!
This doesn't seem to affect tuning nor drivability, and I didn't really even notice until yesterday, because...
If I try to hit VTEC, it gives a solid cel on the dash, and crome shows a code 22: VTEC oil pressure sensor ?!
Now here's the funny thing, if I go to options and disable the following:
- VTEC speed check
- VTEC coolant check
I still get those same cel's.
BUT if I check this box:
- Enable debug mode
Then the code 26 goes away.
I still get VTEC oil pressure sensor code when trying to crossover VTEC though, so I'm going to test the sensor / solenoid to troubleshoot that.
Why does that code 26 come up, and why does debug mode fix it?
Is it because I'm using p30 code?
Is it because the hondata p28 was originally another ecu they converted to a p28?
And of course any suggestions on troubleshooting the VTEC oil pressure code would be appreciated.
Yes, the engine oil level is topped off.
I've used it with their s200, and now with crome pro.
Currently I'm street tuning my EF:
B18c5
Jrsc @ 7.8psi
Gsr / itr cam combo
550cc RC injectors
Bolt ons
History is that this was a big cam itb setup, but I bent some valves and replaced the head, and switched to a jrsc for autox.
I've been tuning the low cam maps without issue so far.
I start the car, and no cel lamp comes on at the dash light, but in the crome data logging window I get a cel ON and the code is 26: unknown ?!
This doesn't seem to affect tuning nor drivability, and I didn't really even notice until yesterday, because...
If I try to hit VTEC, it gives a solid cel on the dash, and crome shows a code 22: VTEC oil pressure sensor ?!
Now here's the funny thing, if I go to options and disable the following:
- VTEC speed check
- VTEC coolant check
I still get those same cel's.
BUT if I check this box:
- Enable debug mode
Then the code 26 goes away.
I still get VTEC oil pressure sensor code when trying to crossover VTEC though, so I'm going to test the sensor / solenoid to troubleshoot that.
Why does that code 26 come up, and why does debug mode fix it?
Is it because I'm using p30 code?
Is it because the hondata p28 was originally another ecu they converted to a p28?
And of course any suggestions on troubleshooting the VTEC oil pressure code would be appreciated.
Yes, the engine oil level is topped off.
I haven't seen this issue personally, but maybe try to go back to v1.6.5 and see if the problem persists. There is always the possibility of having a corrupt BIN file as well.
Is it possible crome pro doesn't like copy and paste of fuel cells?
I did that to build my base map for VTEC.
Maybe it doesn't like that?
I did that to build my base map for VTEC.
Maybe it doesn't like that?
No way to know for code 22 - I haven't tried to hit VTEC with my base map bc it was so damn rich, so I just did part throttle and wot tuning up to 6k rpm - didn't try to hit VTEC until now.
Vtp disable?
I did disable VTEC speed check and VTEC coolant check, but still got the code when hitting crossover.
Vtp disable?
I did disable VTEC speed check and VTEC coolant check, but still got the code when hitting crossover.
VTP = VTEC Pressure Switch
I haven't had any problems with copy and pasting tables personally, but I know you can cause issues if you modify the scalars. I ran into this issue a few times so I just start with the map that gives me the best scalars and then copy and paste tables in for a base map.
I haven't had any problems with copy and pasting tables personally, but I know you can cause issues if you modify the scalars. I ran into this issue a few times so I just start with the map that gives me the best scalars and then copy and paste tables in for a base map.
Trending Topics
Code 26 is Vtec Malfunction.
You need to start with a fresh base. This commonly happens when the file becomes corrupt. I'm not sure why you're not using a gold file, Crome tuning isn't reliable on P30 code.
If you still experience the issue then it's very possible your ECU is at fault, or you just have low oil pressure.
You need to start with a fresh base. This commonly happens when the file becomes corrupt. I'm not sure why you're not using a gold file, Crome tuning isn't reliable on P30 code.
If you still experience the issue then it's very possible your ECU is at fault, or you just have low oil pressure.
Code 26 is Vtec Malfunction.
You need to start with a fresh base. This commonly happens when the file becomes corrupt. I'm not sure why you're not using a gold file, Crome tuning isn't reliable on P30 code.
If you still experience the issue then it's very possible your ECU is at fault, or you just have low oil pressure.
You need to start with a fresh base. This commonly happens when the file becomes corrupt. I'm not sure why you're not using a gold file, Crome tuning isn't reliable on P30 code.
If you still experience the issue then it's very possible your ECU is at fault, or you just have low oil pressure.
Really? 26 is vtec malfunction?
I found this when searching:
22 VTEC Oil Pressure Switch defective circuit or unplugged / defective oil pressure switch
* invalid code for non-VTEC engine
I'm not using a gold file because I only purchased crome pro some years back.
I thought gold was only for dealers who had purchased the license.
Here's my current.bin and a couple datalog files in case anybody wants to have a go at it (same thread posted on pgmfi.org):
http://forum.pgmfi.org/viewtopic.php?f=35&t=23909
VTP = VTEC Pressure Switch
I haven't had any problems with copy and pasting tables personally, but I know you can cause issues if you modify the scalars. I ran into this issue a few times so I just start with the map that gives me the best scalars and then copy and paste tables in for a base map.
I haven't had any problems with copy and pasting tables personally, but I know you can cause issues if you modify the scalars. I ran into this issue a few times so I just start with the map that gives me the best scalars and then copy and paste tables in for a base map.
Oh I see what you mean:
There is an option under plugins, enhancements, vtp + vts remover.
I will try that and let you know the results.
Won't I need to ground the wire then?
Yes - I thought that was part of the routine checklist like removing check sum routine haha. IIRC You wouldn't need to ground the VTP switch but you still need to wire up the VTS (VTEC Solenoid) for VTEC to work.
Hrm well I changed chips and burned the same bin file with just a couple tweaks to the low cam map and no cel and apparently VTEC kicks in - but I can't hear it cross over like when it was NA.
I'll play with it some more tomorrow - I hope that was it.
I'll play with it some more tomorrow - I hope that was it.
Thread
Thread Starter
Forum
Replies
Last Post
integracivic94
Honda Civic / Del Sol (1992 - 2000)
2
Aug 22, 2004 08:42 AM




