Has anyone else experienced this: Last Thursday I paid for the MCU Upgrade to MCU_2 and everything seemed fine until arriving at home and I couldnt see my WiFi from my parking spot. WiFi Search was spinning and spinning... Never had this issue with MCU 1 over the last 3 years. Also from what Ive read, the 5 GHz band should also be supported - I do not see either of my 5 GHz radios when WiFi searches. I went to show my wife video streaming an I cannot even stream Netflix or Youtube sitting in my driveway next to the house.
So I turned the car around so that the passenger's side mirror was next to the house (4' from the wooden house, not metal, not brick...). could see 1 bar and could then connect to my WiFi that was in the house literally 6' in a straight line from the wall. I am not at the latest FW revision.
Using a WiFi Signal power meter, I could see that the signal at the car, and all around the car was typically better than -64 dBm, ... what this means is that there is absolutely no reason why the WiFi Rx in the car is not able to connect.
Here is a table that shows WiFi signal strengths / power levels vs achievable (loosely) data applications:
View attachment 561653
I am a bit shocked that a new radio module in a new MCU would suffer this sort of issue as it appears to be very similar to Apple's "Antennagate".: Summary (in radio designer language): Crappy receiver performance.
SC says they will speak to engineering - I expect that I am not the only one seeing this issue.
What I would like Tesla to do is to properly trouble shoot the issue (and fix) for: bad or unmatched antenna, 2.4/5 GHz antennas swapped, bad RF front end switch setting, ... is Tesla able to see what is the RSSI (Receive Signal Strength Indicator; one of the most basic radio specs), the power level that the WiFi radio thinks it's receiving? This would be very helpful since if the receiver thinks its getting -85 dBm, but we can clearly measure 20 dB higher around the car then something is seriously wrong and needs to be addressed.
So I turned the car around so that the passenger's side mirror was next to the house (4' from the wooden house, not metal, not brick...). could see 1 bar and could then connect to my WiFi that was in the house literally 6' in a straight line from the wall. I am not at the latest FW revision.
Using a WiFi Signal power meter, I could see that the signal at the car, and all around the car was typically better than -64 dBm, ... what this means is that there is absolutely no reason why the WiFi Rx in the car is not able to connect.
Here is a table that shows WiFi signal strengths / power levels vs achievable (loosely) data applications:
View attachment 561653
I am a bit shocked that a new radio module in a new MCU would suffer this sort of issue as it appears to be very similar to Apple's "Antennagate".: Summary (in radio designer language): Crappy receiver performance.
SC says they will speak to engineering - I expect that I am not the only one seeing this issue.
What I would like Tesla to do is to properly trouble shoot the issue (and fix) for: bad or unmatched antenna, 2.4/5 GHz antennas swapped, bad RF front end switch setting, ... is Tesla able to see what is the RSSI (Receive Signal Strength Indicator; one of the most basic radio specs), the power level that the WiFi radio thinks it's receiving? This would be very helpful since if the receiver thinks its getting -85 dBm, but we can clearly measure 20 dB higher around the car then something is seriously wrong and needs to be addressed.
