USB ports disabling with 2019.8.2 #131
Comments
drpotters
changed the title
|
I was having the same issue with the power going out to the USB ports. I resolved the problem by powering the pi via the cigarette outlet. Haven't experienced the issue again since I made that change a few days ago. |
|
Providing another source for power, as @firedfly suggests, appears to work around the problem and my teslausb is once again working. Since the USB ports can deliver up to 2 amps at 5v I'm surprised the car is turning them off while driving. From what I can tell, a Raspberry Pi Zero W should only use 120-230mA of power, and I'm willing to bet there's something that can be done with the teslausb to have the vehicle continue to deliver power. I'm going to contact Tesla to see what, if anything, they might suggest. Anyway, I hope this will help others to more readily identify what's happening. |
|
I'm on 8.3 and I dont have this issue, just fyi |
|
I'm on a 'different version' beyond 2019.8.x cough but have had the same issue. I've noticed a USB hub (that has a Power LED) in front of the Pi seems to help keep it on better. I'm still having some issues, but I think I need to apply the kernel fix everyone is talking about. |
|
Having the same issue as @ScrawnyB, the kernel fix didn't fix it for me either. I went a whole day without issue with sentry mode on for several hours. The issue cropped up again though on day 2 so it does not appear to be fixed for me. I'm also powering the rpi with the 12v. |
|
Im also in the beta program, and having the same issue @ScrawnyB . External power resolves it entirely, but is not a good solution imo. |
|
Some discussion of this here, including an email response from Jeda who is also looking at the problem https://teslaownersonline.com/threads/usb-drives-dying-early-deaths-when-used-for-tesla-dash-cam-videos.11828/page-3#post-221333
Note: I'm on 2019.8.3 and I am not having the issue, although I fully expected to when I updated last week. My rpi stays happily connected, even with long Sentry modes, and has been updating fine when I get home. I am using a USB splitter, the one that came with the Nomad charger, with the 'data' side used for the rpi and the power side to the Nomad. Per the post from Jeda, it appears that that using the splitter may be the reason why I have not experienced this. |
|
My system is now working (with jsvp's fork), but I had to connect the pi to a USB hub which in turn is connected to the car. I also used rpi-update but not sure that fixed anything. |
|
Leofaoro, can you share the USB hub model? Thanks |
Sure this is what I have |
I followed the discussion in #119 and was able to get this working again w/ the newly partitioned cam disk image, until I updated to 2019.8.2 5 days ago.. Since then, I can see the Pi starting up and then it goes dark (no power) with the USB port shutdown. The only way I can get the port active again is to restart the MCU, and I have the same problem if I plug in to the other front port.. It looks to me like the vehicle is detecting this as an attack/problem and it disables the port.
At first I noticed my CAM image had mismatched FAT's (repair in windows, and in the device itself didn't make a difference), so today I made a new filesystem on it. Now that there's no mismatch I'm seeing my vehicle disable the USB port quickly, much faster than it did when my Pi had to "repair" the CAM image each time it booted..
The text was updated successfully, but these errors were encountered: