-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
MCU_w004 - touchscreen unresponsive
- Thread starter brkaus
- Start date
Art VandeIay
Attractive Membrane
My wife's Raven Model X started having this issue since firmware 2021.32.22, along with an intermittent "Park Assist Unavailable" error.
We took it to our local Service Center for both these issues and a very weird GPS problem we have since around June, which changes the vehicle's location to another neighborhood after the vehicle goes into deep sleep, but as soon as it gets rolling again, the location corrects itself after a few feet of driving. (Issue documented here).
But anyway, out of the 3 issues we had, the Service Center was only able to fix the "Touchscreen unresponsive" error.
After escalating the issue with Fremont's engineering team, they mentioned that starting with the 2021.32 branch, some MCU's are having trouble allocating the correct firmware drivers for the touchscreen in the correct folder, so the drivers get duplicated.
They said it's not a big issue since the touchscreen remains fully functional, but it keeps throwing the error pretty frequently.
They were able to delete the duplicate files and redeploy the firmware, and we haven't seen the error again. My guess is that it will probably get fixed for the whole fleet on the next firmware update.
The engineering team also highlighted that they are well aware of the "Park Assist Unavailable" error but are still working on a fix, "as the last 2 attempts didn't quite work"
.We were sent back home with the GPS error still at full force, but with no way of solving it in the horizon
...I was experiencing the W004, Touchscreen Unresponsive, errors every hour when car was not being used after installing 2021.32.10. My problem was resolved by reinstalling 2021.32.10 with all USB devices removed.
Huachipato
Member
I'm starting to have this issue. But my screen actually went unresponsive to touch tonight while otherwise working ok. 2021.36 is when it started for me. A reboot gets it up and running again temporarily. I'll open a service ticket...
Huachipato
Member
I got the 2021.36.5 update yesterday and the error messages seem to have stopped. The suggestion of a driver issue seems to fit this issue, and a new update correcting it. I have an appointment for a mobile tech to come out on Friday which I'm tempted to cancel now. I'll keep an eye on it today, but it seems to all be working correctly now.