:::RHMT::: Real Home Made Turbo

Please login or register.

Login with username, password and session length
Advanced search  

News:

ApexSilver06MR/Jason YOU WILL BE MISSED, RIP (link)  :'(

Pages: [1]   Go Down

Author Topic: Crome on p28 issue  (Read 4305 times)

AWDstylez

  • Full Member
  • ***
  • Offline Offline
  • Posts: 124
Crome on p28 issue
« on: October 27, 2011, 11:46:30 AM »

Ok so I've got a p28 in an eg running an ls/vtec. The car came with a mostly stock p72 base chip made with crome. However, like the rest of this minority built shit pile, it was hack and was running with every thing possible disabled and debug mode enabled. Obviously the car got crap fuel mileage and just generally didn't run smooth.

So I tried to fix it. The no brainer move seemed to be to take a stock p72 base from crome, disable knock sensor for the p28 to be happy, do the remove check sum routine, and profit.  However this resulted in all kinds of issues. The car has hesitation, bog, amd surge spots all over the place. I breaks up horrifically at low rpm when cold, but runs decent when warned up. It had no check engine light until I drove it to the mall yesterday, it ran alrighton the way there, but took a long time crank and start, threw a check engine light and refused to idle. I tried to drive it but it had no power and was breaking up like crazy.  I had nothing to use to jump the service connector so I don't know what the light was for, but I pulled the j1 jumper and drove home on the stock p28 map without a problem. When I got home I reconnected j1 and the the check engine light was gone so it'll remain a mystery what it was for.

Any ideas on why this map refuses to work? Am I missing something? Does something other than the knock sensor need to be disabled on a p28?
Logged

92CXyD

  • Twincharged Smeghead
  • Global Moderator
  • Certified OG
  • *****
  • Online Online
  • Posts: 6789
  • I look around and all I see is Smegheads
Re: Crome on p28 issue
« Reply #1 on: October 27, 2011, 11:55:57 AM »

Is the base map a modified P30 w/ a P72 base on it?

If not make a new map w/ P30 and put a LS/Vtec (GSR) on it or go here:

http://www.xenocron.com/bins/index.php?&direction=0&order=&directory=Crome/B-Series

Chose the closes or just.

I know it is a xencron site but I know of any other bins.


Another route would be load a P30 map w/o boost then fatten the fuel for everything 20% then modify from there.

I'm sure someone on here will chime in.  :noel:

AWDstylez

  • Full Member
  • ***
  • Offline Offline
  • Posts: 124
Re: Crome on p28 issue
« Reply #2 on: October 27, 2011, 12:40:27 PM »

No, at the moment it's a straight p72 base. So you're saying start with a p30 base and copy over all settings from a stock p72 just so it'll run p30 code? I did see that recommended in other places, but it made no sense to me to have all untouchable low level calibrations tuned for a different motor. I'll give it a try though.
Logged

Joseph Davis

  • Verbal Assault Technician
  • Moderator
  • Certified OG
  • *****
  • Offline Offline
  • Posts: 34733
  • Eugenics prevents retards like widebody93
    • TURBO THIS
Re: Crome on p28 issue
« Reply #3 on: October 27, 2011, 05:17:23 PM »

Codebase shouldn't make a difference, it all runs interchangeably.  Do try a different codebase in case your .bin, the packaged .bin with your version of Crome, or one of the plugins has gotten corrupted.  But using P30 codebase is not the fix.

OBD1 ECUs are getting old and shitty, PCBs are a chemical composite that degrades with time.  Tick tock tick tock.  All socketing jobs are far shittier than the way the ECU was manufactured, and hasten the ECU's dying.  I'd try a different ECU.  That hard start/poor idle shit makes me think TDC sensor issues/H1C1/etc, although it could be a LOT of things.

Also, you're a bright guy.  Get a datalogging cable and see what the ECU sees.  Freelog will do all you need for general fix and repair.

PhilStubbs

  • Certified OG
  • *****
  • Offline Offline
  • Posts: 5885
  • Teh Secksy.....I has it
Re: Crome on p28 issue
« Reply #4 on: October 27, 2011, 05:56:01 PM »

check ignition timing. you can sorta tune a car with bad cam timing to run decent. if you have a map that says 16* at idle and ignition timing is way off then your cam timing is off.
Logged
obd1>gtgtall

 fucking box started smoking and i saw a flame start up so i grabbed a bucket of water and splashed it on the breaker box.

AWDstylez

  • Full Member
  • ***
  • Offline Offline
  • Posts: 124
Re: Crome on p28 issue
« Reply #5 on: October 28, 2011, 05:42:37 AM »

Codebase shouldn't make a difference, it all runs interchangeably.  Do try a different codebase in case your .bin, the packaged .bin with your version of Crome, or one of the plugins has gotten corrupted.  But using P30 codebase is not the fix.

OBD1 ECUs are getting old and shitty, PCBs are a chemical composite that degrades with time.  Tick tock tick tock.  All socketing jobs are far shittier than the way the ECU was manufactured, and hasten the ECU's dying.  I'd try a different ECU.  That hard start/poor idle shit makes me think TDC sensor issues/H1C1/etc, although it could be a LOT of things.

Also, you're a bright guy.  Get a datalogging cable and see what the ECU sees.  Freelog will do all you need for general fix and repair.


Thing is though, I find it hard to blame the ECU when I can pop in the chip that the car came with and it'll run fine (minus horrible gas mileage and generally just not smooth) and CEL free or I can pull the J1 jumper and the car will run fine and code free on the stock P28 ROM.

I tried simply burning a new chip, since Crome has always given me issues getting chips right the first time.  I disabled injector test circut and atmos sensor just for the fuck of it and because I noticed whoever socketed the ECU didn't do the little electrical tape mod over the atmos sensor, not sure if that even matters though.  Seems to be running alright after a trip around the block.  No low RPM breaking up when cold, which the other chip did immediately.  All the other issues cropped up over time, so I'll drive it for the weekend with this chip and see what happens.
Logged
Pages: [1]   Go Up