PDA

View Full Version : ROVER MEMS3 LONG CRANK BEFORE START AFTER IMMO OFF



rehtnap2013
13th October, 2013, 08:53 PM
HI
i have done an immo off on a mems 3 rover 45 and although it runs ok after its stood overnight it requires approx 10 second crank before it fires up. drives ok its just asthough it looses the code when stood. any one else had this.?????????

willywonker2010
13th October, 2013, 11:54 PM
diesel or petrol
sound like fuel sipening back
air leak maybe

rehtnap2013
14th October, 2013, 04:25 PM
its a 1.4 petrol. with its original ecu there is no problem but this ecu has been badly water damaged and repaired due to corrosion so i had another ecu from a 1.4 that i did the immo off on. i must admit i dont know the history of the ecu other than its from a same year 1.4, it may have a fault but i thought id see if anyone else has had a similar problem. this morning it started first go but 5 mins later at the shop it needed the 10 second crank again.

willywonker2010
14th October, 2013, 11:10 PM
hmm
change EEPROM over to
ecu or clone ecu
flash and EPROM
at the most

wiseman
14th October, 2013, 11:53 PM
I've had this problem also and seen Other people with the same issue. Had an MG ZR last Month that started fine. Then customer left for 1 week and one day wouldn't start, thought she had ran out of petrol at first.
I think it's a sync issue with the pektron SCU, I
Had not coms with SCU, so removed for a little while and replaced then cranked for 10 secs and started. Been ok since

rehtnap2013
15th October, 2013, 03:33 PM
right i have taken another ecu i know worked on the car albeit with what appears to be rich fueling as i think its from a bigger size engine and done immo off and found it doesnt work when u re solder the eeprom in back to front oooppps but started ok once id corrected that. now left the car to see if it restarts tomorrow wihtout a problem. i tried with galletto1260 to read the ecu but it wont connect it has a seed error so i guess the galletto program hasnt got the correct alogritham in it for some mems3 units.

rehtnap2013
17th October, 2013, 03:22 PM
the replacement ecu works first time and doesnt seem to have the error so im guessung the first one i did may be a faulty ecu. what is interesting is the fact that the second ecu i did was an obd compliant unit and now it wont communicat with obd readers!!!!!!!! so therefore the chip contains the info required to make it obd compliant i guess.

rehtnap2013
24th October, 2013, 02:30 PM
does anyone know if the 93c66 chip just contains the immo info its odd how flashing it with the free run flash has stopped the eobd working???