*** Restricting New Posts to SD Premium Members ONLY *** (09 May 2025)
Just made a new account? Can't post? Click above.
A place to discuss hardware/software and diagnostic procedures
xTool D7 not consistent
- coolmoss
-
Topic Author
- Offline
- New Member
-
1 year 8 months ago #64893
by coolmoss
xTool D7 not consistent was created by coolmoss
Hello, my first post, hope I'm putting it in right place 
I scanned a 2005 Chrysler 300 with my new xtool d7. It automatically read the vin # correctly. I did a scan and it returned perhaps a dozen DTCs. Car wouldn't start. Turns out a mouse got at the pcm wiring harness. I carefully examined the harnesses as best I could, fixed all the chewed through wires. Car now starts and runs fine.
The weird thing is, after the repair, I went to do a scan to make sure all is okay. But now the vin# won't automatically read. Pehaps it doesn't matter, but it's driving me crazy, wondering what's going on. I did have the battery disconnected for a week, but I didn't think that would effect the hard coded data in the pcm.
Any thoughts?
I scanned a 2005 Chrysler 300 with my new xtool d7. It automatically read the vin # correctly. I did a scan and it returned perhaps a dozen DTCs. Car wouldn't start. Turns out a mouse got at the pcm wiring harness. I carefully examined the harnesses as best I could, fixed all the chewed through wires. Car now starts and runs fine.
The weird thing is, after the repair, I went to do a scan to make sure all is okay. But now the vin# won't automatically read. Pehaps it doesn't matter, but it's driving me crazy, wondering what's going on. I did have the battery disconnected for a week, but I didn't think that would effect the hard coded data in the pcm.
Any thoughts?
Please Log in or Create an account to join the conversation.
Time to create page: 0.240 seconds