teslausb
teslausb copied to clipboard
marcone
USB Device Malfunction - Center Console Port
After 2020.48.26 I started getting this error in my Model 3:
https://imgur.com/lS9PRoG
And, now that I have my Model X back, I can confirm I get it on my Model X as well, after 2020.48.30.
In both vehicles I'm using a Raspberry Pi 4. The fix is enough enough, unplug and plug it back in again. Not sure if it is because there's a point in time where it starts drawing too much power or something, but it is a noticeable issue.
I don't have a PI Zero to determine if there's an issue with this there now too.
I’m only a recent user of TeslaUSB, i’m using a Pi Zero W and was getting this exact issue.. resolved it by changing to a better quality micro USB cable. Haven’t had it since.
Here you go https://www.anker.com/products/variant/powerline-4-in-micro-usb/B8135011
I get the same error message after about an hour of driving. I tried removing my hub and everything and nothing helped.
Same. This same setup (Pi Zero W, center console port, Model 3 from a few years ago) has worked since for ages, and my wife started noticing this error about once a day since the 2020.48.30 update. The Pi is on a battery backup (I have a battery connected to the microUSB power port, in addition to the cable on the data port) - not sure if that's a common factor or not with the other reports.
The only times I've seen "USB device malfunction" was when the Pi was drawing too much power (the car seems to complain when there's a high load on the USB port for more than a few seconds, like for a Pi4+SSD booting up), or when I unplugged a (battery powered) Pi0 from the car immediately after getting in to the car.
It seems to happen when the Pi loses WiFi (e.g., when about a block from the house) - Is there anything that happens in the archiveloop when that event occurs?
I'm seeing the issue after about an hour of driving. Pi0, with or without hub / phone chargers / other usb devices plugged in. It has persisted through at least two fw updates and a complete reinstall of tesla USB
I'm seeing the issue after about an hour of driving. Pi0, with or without hub / phone chargers / other usb devices plugged in. It has persisted through at least two fw updates and a complete reinstall of tesla USB
Have you tried it on 2020.48.35.5?
The only times I've seen "USB device malfunction" was when the Pi was drawing too much power (the car seems to complain when there's a high load on the USB port for more than a few seconds, like for a Pi4+SSD booting up), or when I unplugged a (battery powered) Pi0 from the car immediately after getting in to the car.
My Pi4 has no USB attached. Just an SD card. Admittedly, Pi4 versus Pi0, so more power hungry to start.
I am not 100% sure this is TeslaUSB though. Someone on the Tesla Discord server mentioned getting the same error with a flash drive. He said his car was being brought in to have a working session with the Tesla engineers on the phone.
Same error, but different circumstances.
Yeah. Still saw it a couple times already unfortunately.
Damn. I haven't driven with 2020.48.35.5 installed yet, was hoping this was one of the bugs.
I did report the issue to Tesla via the support chat. But they stated TeslaUSB wasn't supported, so they don't appear to be giving the complaint too much weight.
Not sure if others want to report the issue as well, see if we can it sorted through a volume of complaints.
Same issue here. Details below:
- PiZeroW
- Happens intermittently - sometimes continually after parking and getting back in, sometimes halfway through a drive, sometimes at the end of a drive
- Is not related at all to Wifi capability as it often happens or starts some times when im not even in range of Wifi that it can connect to (aka my home)
- Am on the latest release of software my car can take: 2020.48.35.5 - been happening for a few versions now as well
- Not a cable issue as I have also tried a different cable
- Also not related to other devices plugged in or not as I’ve tried variations there as well
EDIT:
- No power bank involved - direct USB to the Car
I've had the same problem and error messages using a few of the latest car firmware versions including 2020.48.35.5
But earlier i used a power bank connected to the pi to supply backup power. Disconnected the power bank, no more error messages. 👍😃
@JohPePe Isn't that solution amounting to "reboot the Pi when the car comes out of sleep"? (I have my PiZeroW connected to a battery bank as well, so I can SSH into it "whenever", not just when the car is awake)
Same here. Sucks though as this is probably a car issue, not a Pi issue.
Same issue here, happens randomly and regularly since late December 2020. Pi0, SD card only connected.
Getting the error but it's still working fine. More annoying than anything. The irony is that my car is MIC so the pi zero is in the glovebox, but it still says central console.
I removed the battery that was driving my PiZeroW (per the above discussion), and didn't have any change in behavior. There's still the more-or-less random failure, and associated noise and message on the screen. Looks like I have to reboot the Rpi (aka, unplug/replug the microusb connector) to get the car the recognize it again.
This is super annoying. :-/
For what it's worth, I moved over to a RPi4 and the problem disappeared.
For what it's worth, I moved over to a RPi4 and the problem disappeared.
How do you power a RPi4? I’d do it in my Model 3 if I could figure out how without taking console apart.
@miles267 I deleted my previous comment because I had my mind all messed up haha. Basically just get a USB-Y cable and plug the data side into the Pi's front USB ports, and the power side into the USB-C connector (you'll need an adapater). Then just plug it into the console's port
@miles267 I deleted my previous comment because I had my mind all messed up haha. Basically just get a USB-Y cable and plug the data side into the Pi's front USB ports, and the power side into the USB-C connector (you'll need an adapater). Then just plug it into the console's port
I just ordered the two cables you had previously linked. Are there others that are recommended instead?
(Am sure I’ll use those prev 2 cables for another project sometime in future anyway; won’t hurt to have them on hand)
@miles267 I was thinking about it wrong and the ones I linked are the wrong gender, if I remember right.
@miles267 I was thinking about it wrong and the ones I linked are the wrong gender, if I remember right.
If you wouldn’t mind linking the appropriate cables it use it would be greatly appreciated. Will definitely grab them and try a RPi4. Also like the benefit of 5 ghz WiFi as my RPi Zero is only 2.4 ghz. I have one sitting, unused.
Also, I’ve found that if I turn on Sentry Mode at home it keeps my USB powered in the console and the car doesn’t go to sleep. That caused my errors to go away. It confirms they were happening since teslausb isn’t keeping the car awake.
@miles267 Now that I'm thinking about it, use that Y-cable I linked, and plug the data side (all black) into the RPi4's USB port. Plug the USB OTG cable into the charge-only side (the red/orange side). Then use this (link) to plug the Y-cable into the car.
And yeah, that makes sense. I keep sentry on here at home too. I did, however, get random disconnects while driving with the PiZero.
I'm getting the same random failures on my 2021 Model 3, using a Pi0 with an SD card, and a single USB cable from the Pi0 to the glovebox USB slot. I'm using sentry mode all the time/everywhere.
I'm also missing some video clips from time to time, and I guess it's related. In a sentry-folder, there is usually about 10 minutes of footage, from 4 different camera's, so about 40 files (all 1 minute long), but I'm often missing a few of those minutes, making the footage unusable. I thought it was a CIFS/rsync issue, but it looks like the files just are not on the SD-card to start with, which makes sense if the car and Pi0 lose connection from time to time.
Any hints on how to start debugging this? Maybe I should write a script with some Pi0 debugging data, such as the power it's drawing, or the read/write bandwidth etc, to find out what could be causing this?
@miles267 Now that I'm thinking about it, use that Y-cable I linked, and plug the data side (all black) into the RPi4's USB port. Plug the USB OTG cable into the charge-only side (the red/orange side). Then use this (link) to plug the Y-cable into the car.
And yeah, that makes sense. I keep sentry on here at home too. I did, however, get random disconnects while driving with the PiZero.
Thanks. It looks like I also need to get a "coupler" adapter to connect the male USB-A end of the OTG cable to the Y adapter. Didn't realize that. I'll find one. You're not having any issues supplying enough power to the RPi4 this way?