Search results

So it seems rebooting the APE fixes this but it takes a hard power cycle. No amount of hard/soft reboots or pulling 12V reboots the APE. I finally pulled a panel and unplugged the blue connector on the APE and plugged it back in. Autopilot and backup camera immediately started working.

I see you are on HW3 as well. Did your backup camera die too? Those on 2.5 are not seeing backup camera failure.

The security on the Model 3 is incredibly improved compared to MCUv1 on the S/X. It will likely be some time before I am able to obtain root again. Additionally the ethernet on the 3 is a 2 wire automotive variant that requires special hardware.

That's why I asked specifically about your backup camera, as your post said cameras were working fine. My backup camera is dead and USB recordings are basically empty. Assuming its a slightly different failure state of the APE, but same effect. Do you know if you are on AP2.5 or HW3. Just...

Does your backup camera work?

There is an existing thread on this... Firmware 2019.12.1.2 - Auto Pilot and Auto Steering Unavailable The lack of notice that things like FCW are not working, is something that should likely be report to the NHTSA.

It would appear that when this occurs, standard safety features like FCW are unavailable, but there is no warning to the driver. I've reported the concern to Tesla engineering.

This happened to me this morning as well with 12.1.2 on HW3. Was told they’d sent the issue off to engineering.

While the MCU runs the same firmware now, there is a separate AP2/AP2.5/HW3 firmware that's pulled down from the mothership and applied to the AP unit depending on which of the 3 you have.

Given your version number you almost certainly have HW3 rather than AP2.5, and are on a different "branch" of sorts from everyone else. Given the ever increasing number of cars being delivered with HW3 it's likely you will start seeing more frequent updates. I am guessing they were previously...

Another thread is stating that 2019.7.X is an indicator of HW3. Any recent deliveries want to give the first three of their VIN and SW version.

The hw3 firmware is definitely present in versions as new as 2019.12, but they may be holding it back for some reason. I have a 325XXX VIN scheduled for delivery tomorrow so curious if folks when any lower VIN’s are on the version. Told it was produced the 11th.

Not necessarily, as your order may be matched against a vehicle already in inventory that doesn’t have HW3.

I've so far been unable to get an adjustment for AP or paint.

The vehicle was physically inspected, and Tesla took over two weeks for internal approval on the offer.

In most states an e-mail agreement where one party offers another money for a product or service, and both parties mutually agree, its considered a binding contract.

Has anyone ever had Tesla take back a trade in offer claiming it was a mistake. After several months of negotiation I received an acceptable trade in offer on my Model S, via e-mail, and placed an order for a Model 3 the same day. I had several e-mail exchanges with Tesla that included the trade...

Looks like there is a shortage of built LR RWD vehicles. There were unable to locate any in Florida that matched the color I was looking for and had to look to other states for inventory. It sounded as if more are not going to be produced at this point.

I ordered via the website but I've been dealing with a local sales advisor who I e-mailed about a price adjustment. Thanks for the info.

I placed an oder for a LR RWD, Red, AP and FSP, for $55k yesterday (4/11/19). It's hard for me to tell if there should be a price adjustment with the new changes since this model is no longer offered. At the moment, its showing for the same price online and a VIN hasn't been assigned.

I've tried it without success.

This is definitely going on. I've previously been told my vehicle is on a "list" an in fact normal service techs are not allowed to remotely access the car without "speaking with the CID development team" first. My local ranger had to be "read in" before he could speak to me about the car and do...

Appears things are being capped at 256kb/s based on CURL download tests on the vehicle itself.

I specifically complained that this didn’t happen and was effectively told too bad. Since the owners manual doesn’t say it’s supposed to work, they don’t consider it a problem. Promises made don’t have to be met ever. Quite disappointing response that I actually got today.

I have to disagree with your statement. Traffic from the CID to services like Spotify and Slacker, go direct through the carriers LTE network to the providers. The traffic does not go through Tesla. The car maintains an OpenVPN connection over either WiFi or LTE back to Tesla for communicating...

There have been no changes to the AP1 firmware since the end of 2016.

Not normally available unless you can manually edit the UI config in the car. Just saying it's not a provider specific issue.

This is not limited to TuneIn and Slacker. It happens on Spotify in the US as well, if you are able to get it enabled. I have to suspect it is actually related to LTE throttling.

It's based upon libQtWebKit. They have just wrapped it with a thin UI to handle things like location approval, etc...

I believe the memory leak is now fixed. Had some detached DOM objects.

Good suggestion. Thanks for the heads up. Probably something to do with adding and removing markers on updates. I will take a look.

This is a problem with the actual data coming from Tesla. The in car view has the same issue. wk057 has made some attempts to work around it, but can only do so much. In some cases I am now saying "at least X of X" stalls available, or "X more possibly" when there is reason to believe more are...

Real-time traffic, accidents, hazards, and police from Waze are now shown when zoomed in at or above level 10 on the map. Additionally the amenity icons are now fixed. No one realized they were showing completely bogus data.

Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key The browser is also restricted from hitting any hosts over the VPN, or the CID itself or the other local devices like the IC and Gateway.

Unless Tesla is publicly saying these sites are open I am hesitant to show them.

I've made a number of updates to the Realtime Supercharger Map Today - Tesla Supercharger Realtime Availability Map - EV-Prices - Tesla Price History & Modeler UI Cleanup Responsive AutoSize for large screens Saves position and zoom in URI fragment to maintain state after Refresh or in BookMark...

Historical data will be added to the map info windows soon. Last updated information was added today.

May I suggest contacting me rather than trying to scrape the data from the site.

The car is polling for updates. It is not being pushed so sometimes it will be lagged and other times not depending upon where in polling cycle it is.

It should be identical.

Possible means there are likely more stalls open based on data available. It's a little fuzzy.

History on CPO has been broke since Tesla redid website. I'll get it fixed. You need need to sign up for the new Supercharger maps.

This can certainly be done over the air. There is a remote command they can hit to enable it, and it updates the configuration on the gateway to entitle you for AP. Just need to call them.

If you had the clock before upgrade, turns into Readouts after upgrade.

Site is back up now. Sorry for the downtime.

Fixing it now. Sorry about that...

I haven't noticed this but definitely will check. I am on 8.0 and have my dash cam wired that way.

Great news. Thanks for the update.

There are no ads present when manually enabled in the US firmware. Tesla provided premium credentials are auto populated, but you can enter your own.

Recognition doesn't even seem to be working. When in debug mode the Stop Light / Stop Sign monitor never enters any state except "NONE".