Originally posted by Rockies67
View Post
Announcement
Collapse
No announcement yet.
No crank, no start issue - need help!
Collapse
X
-
Originally posted by Rockies67 View PostAre you thinking that key # 5 is somehow corrupting the EWS? If so, if/when it begins starting again should I leave that key behind and switch to only using # 4?
Next time when engine runs again, then shut off and read the key with AK90; read the key after it fails to crank and I think its data was wiped out.
Comment
-
Okay car started working again this evening. I had put the EWS into the freezer over night to test out a theory about potential microcracks in the EWS soldering. EWS went into the frezer not working and when it was put into the car it worked right away.
Took the opportunity to start the car with key # 5. Removed the key and read the key data with the AK90. The data is still blanked out (no VIN nor KM).
Also put key # 4 into the car and started the car to see if the KM data would get updated since I have not used this key during any of the test drives the other day. The KM was at 349648. Key was updated to 349654. Interestingly, the actual KM on the odometer is 349643. Not sure what to make of that?
Let the car run for a 10-15 minutes with a heater going to see if we could see the INPA actual key data (identification, code, or password) fail in real time. Eventually gave up on this as the data was really solid and not doing anything.
One thing we did notice though is that in comparison with previous times of watching the actual key data that the idenitication did not occassionally flicker from No to Yes today. I wonder if this is a clue to what is happening when the car fails to start. Any thoughts on what would cause the Idenitification to flicker between the two states?
Comment
-
“Key was updated to 349654. Interestingly, the actual KM on the odometer is 349643. Not sure what to make of that?”
it makes sense that the nonvolatile memory in the cluster not getting updated with odometer too often, and so its actual km is lagging compared to actual value in the EWS.
only use #4 key from now and see what happensLast edited by sapote; 11-07-2024, 03:50 PM.
Comment
-
Originally posted by sapote View Post“Key was updated to 349654. Interestingly, the actual KM on the odometer is 349643. Not sure what to make of that?”
it makes sense that the nonvolatile memory in the cluster not getting updated with odometer too often, and so its actually km is lagging compared to actual value in the EWS so
only use #4 key from now and see what happens
So a car that had say 11 kilometers like OP his car, when it was sold new the dealer would reset the odometer back to 0, and this value is stored and always subtracted from the displayed odometer.
The maximum value for this offset is 0xFF, so 255 kilometers.E46 ///M3 • 12/2002 • phönix-gelb • 6MT
E39 ///M5 • 12/1998 • avus-blau • 6MT
E60 ///M5 • 11/2006 • saphir-schwarz • 6MT
Comment
-
Originally posted by Rockies67 View PostCar started and ran nicely for 7 separate starting sessions (spaced out over 30 hours) with key # 4 and then stopped on the 8th attempt - all the same symptoms. Checked AK90 data for key # 4 after the fail to start and it is all there, no problems.
Comment
-
Originally posted by bmwfnatic View PostSo a car that had say 11 kilometers like OP his car, when it was sold new the dealer would reset the odometer back to 0, and this value is stored and always subtracted from the displayed odometer..
you meant Added to?
So the CPU reads the miles from the cluster and then adds (not subtracts) 11km offset before writing into the EWS? So the EWS has the actual mileage of the car?
Comment
-
Originally posted by bmwfnatic View Post
No, the clusters have a mileage offset that could be set once when they were new.
So a car that had say 11 kilometers like OP his car, when it was sold new the dealer would reset the odometer back to 0, and this value is stored and always subtracted from the displayed odometer.
The maximum value for this offset is 0xFF, so 255 kilometers.
My experience is LCMs don't count past 300,000km.
'09 HP2S, '12 R12GSA, '00 Black 323iT, '02 Alpine 325iT (Track Wagon), '02 Alpine 330iT
Instagram @HillPerformanceBimmers
Email to George@HillPerformance.com
Comment
-
Originally posted by George Hill View Post
I've PDI'd a bunch of E46s and we never reset the cluster mileage to 0. What it came with off the truck and after the PDI test drive is what it was sold with.
My experience is LCMs don't count past 300,000km.E46 ///M3 • 12/2002 • phönix-gelb • 6MT
E39 ///M5 • 12/1998 • avus-blau • 6MT
E60 ///M5 • 11/2006 • saphir-schwarz • 6MT
Comment
-
Originally posted by bmwfnatic View Post
Maybe only the miles driven on factory grounds/testing were reset this way, but the mechanism definitely exists, my personal one has 9 kilometers “hidden” via this system.
Whenever I zero out a cluster eeprom they don't always read true zero, sometimes its positive a little and sometimes negative. Also, when we replaced instrument clusters (at the dealer) with brand new never been messed with cars and clusters they didn't always read the mileage that they came in, which I assumed was something to do with how the cluster and LCM sync AND stored their respective mileages. They almost always were close enough that after a test drive they would be higher than they came in with. But I do recall I had one that was significantly less after and this was a problem because the repair order system and key read were not equipped to show a negative out mileage and it was a bunch of work to get it passed through warranty with the mileage being less than before. So maybe that's related to what you are referring to as a new cluster wouldn't have this offset when the original did?'09 HP2S, '12 R12GSA, '00 Black 323iT, '02 Alpine 325iT (Track Wagon), '02 Alpine 330iT
Instagram @HillPerformanceBimmers
Email to George@HillPerformance.com
Comment
-
Update:
Three days ago I decided to "touch up" the bottom side solder on all of the through hole components on the EWS. The thinking here was that one of the lines in the EWS related to the INPA key data (identification, password, code) is glitching in/out and causing the no crank condition.
Since then the car has consistently started on over 25 separate times (note some times I just started the car and other times I drove it around) using key # 4 (note key # 5 has been left behind and will not be used on the car moving forward) with no instances of not starting. I also removed and reinstalled the EWS after about 20 starts to test it on the AK90+. All error codes were erased before the resoldering and no new error codes are present at this time.
I plan to continue to start and drive the car short distances until I feel confident that this is not a temporary phenomena--but so far, so good!
- Likes 1
Comment
Comment