-
Featured
- Staff 🛡️
- #801
- Jun 25, 2021
- 10,938
- 20,577
- 22MY F250 Star White Lariat Tremor
- 22MY Winnebago Voyage 2831RB
I previously read on Forscan.org forum that people have experienced this type of "lock" situation. The recommendation was to remove Forscan, reinstall, and try again. Also, ensure you have the latest release and your license is active...Okay, so went in today to do a few upgrades. Plugged in, connected, all good. Selected the module I wanted to tweak, then hit write. I was only changing one thing. 50% into it, Forscan appeared to stop writing. It wouldn't move anymore. It was stuck at 50%. But, I was able to still move around the program. So I hit the stop service button, and the button went dark, as to show it wasn't able to be pressed again. But nothing else happened. I couldn't do anything else. I waited a few more minutes, and nothing would happen. I wasn't sure what to do, wasn't sure if it was even writing or doing anything anymore, so, for better or for worse, I just unplugged the OBD reader. Disconnect warning popped up, so I cleared them, shut down Forscan, and restarted it. Plugged in, and now, it won't connect to the car. I started up and drove around a bit, and I have no obvious issues. My banks pedal and e-venture is still reading through the OBD port (I checked by putting the truck in reverse, and the pedal monster identified it as being in reverse). I waited 20 minutes, and let the truck sit for a bit, then tried again - it still won't connect. I'm at a loss of what to do. On the main Forscan log screen, it just says "unable to connect. Make sure car is on". When I go to the log tab, it says "CAN failure 3%, BUS failure 3%". So I assume it's not reading, and something is "jammed up" in the communication loop. How do I unjam this? Hope this made sense
Not real techy, but I would also reboot the laptop...

