I'm more curious about the VIN issue that the actual problem at this point.Even NHTSA does not recognize that VIN
Looks invalid for a US Bronco Sport
Sponsored
I'm more curious about the VIN issue that the actual problem at this point.Even NHTSA does not recognize that VIN
Looks invalid for a US Bronco Sport
the decoder shows an error in the 9th digitI just decoded the VIN here.
https://vpic.nhtsa.dot.gov/decoder/Decoder?VIN=3fmcr9c61mra35262&ModelYear=
Same. The VIN suggested by PTS pulls up, but I don't think it's his truck based on warranty history not matching up with his prior issues and the fact that VIN is for a truck not being driven, so it is not reporting data to the cloud since 5/28(see second screenshot).This probably is OPs VIN
3FMCR9C64MRA35262
@rugedraw want to see if you can find anything on this VIN
I checked the vin number on the car and I apparently made the mistake. The last 2 numbers of my vin is 52 not 62. Sorry as I have had an eye issue lately or a typing issue. lolI'm more curious about the VIN issue that the actual problem at this point.![]()
Ok, so here's the culprit. The last time this code was recorded reporting a hard fault was on 7/24. Notice the characters circled in red. That is the status byte of the code. If it ends in 8 like the green circle, is a stored code and not an active fault. If it ends in pretty much anything but an 8, it is an active fault.I checked the vin number on the car and I apparently made the mistake. The last 2 numbers of my vin is 52 not 62. Sorry as I have had an eye issue lately or a typing issue. lol
Not sure what that means, but if you're flirting with me, it's working.It's nice to have someone on the inside. Should change your username to Deep (Tail) Throat...![]()
Don't worry, it's an exhaust thing, not intake. Not sure if that make it any better...Not sure what that means, but if you're flirting with me, it's working.![]()