Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Tesla Winds and Elevation Web Browser App

Snowstorm

Active Member
Dec 8, 2016
1,490
1,407
Ontario Canada
Can someone with an S/X please open a browser on the car and go to resizeMyBrowser, take a picture of your screen, and post the picture here. I need to see the "inner window" pixel dimensions of the S/X browser.

Thanks,
Here you go 1160x1396
 

Attachments

  • image.jpg
    image.jpg
    571 KB · Views: 38
  • Like
Reactions: SomeJoe7777

rrolsbe

Member
Feb 18, 2017
220
126
Albuquerque
I posted the following to another thread in the Tesla.com forum. Reading posts in this thread indicate Teslawinds should work on the Model 3.

I had seen Teslawinds before but the website said it was for Model S/X no mention of Model 3. i tried it out on my Model 3 yesterday. The wind speed and direction seemed reasonable and the compass worked; however, the elevation did not work and Ground Speed was all over the map. I drove 10 miles on the interstate with Autopilot set to 71MPH and the Ground Speed was reading speeds between 40 and 90MPH and everything in between. I would think Ground Speed would come from GPS, is GPS data different on the Model 3? The cars speedo meter gives me ground speed and I can add or subtract the head/tail wind speed mentally to get air speed. Better than nothing in Model 3 but it would be nice if everything worked!

Maybe I am doing something wrong? Can anyone confirm or deny my results?
 

rrolsbe

Member
Feb 18, 2017
220
126
Albuquerque
Yes, the layout fits properly on the Model 3/Y screens, but is a bit too wide for the S/X now that the browser is in a window like the Model 3/Y.

So, here is a summary of the bugs/issues I have open right now, and are on the schedule to fix:
  1. Content width on Model S/X
  2. Settings panel comes up, but isn't allowing selections
  3. Investigate GPS errors from browser position, see if I can find a way to smooth out errors so that heading and speed don't jump around.

I'm also taking a look at adding content for the lower half of the screen for S/X. This might be weather data and/or weather map. I did some poking around with the OpenWeatherMap API tonight and there are ways to get the precipitation data and overlay it on a map, but it's not the easiest thing in the world. This is in very early investigative phase and I haven't commited to putting this in the app, but I'm taking a look.

Regarding issue 3 above, does the Tesla API allow access to speedometer data. If so, that could be used in lieu of GPS. I suppose Tesla could be using GPS to display speed on the left side if the center screen?
 

SomeJoe7777

Marginally-Known Member
Mar 28, 2015
2,174
5,601
Houston, TX
Regarding issue 3 above, does the Tesla API allow access to speedometer data. If so, that could be used in lieu of GPS. I suppose Tesla could be using GPS to display speed on the left side if the center screen?

The app works by requesting GPS position from the browser via Javascript. This used to work very accurately until Tesla release the v9 software. Ever since then, the GPS data is very quantized and inaccurate. This results in varying heading and speed displayed in the app.

I have not yet found a way to compensate for this or get the old, accurate GPS data from the browser. The Tesla API does have accurate GPS data, so I could read the GPS data from there and it would smooth things up again, but there are several disadvantages to this approach:

1. There would be a delay in getting the data because that has to be requested over the Internet, and the car has to send the data to the Internet as well.The displayed speed and heading would lag behind the actual speed and heading by quite a bit, probably at least 5 seconds, maybe more.
2. My app would have to request your Tesla login so that it could access the API for your car. Many people are uncomfortable with that, and I'm not keen on accepting the responsibility for handling sensitive data in my app.
3. I'd have to build a new UI for gathering the Tesla login from the user, and since my app intentionally does not use cookies or store data on any server, I'd have no secure way to store the Tesla login between uses of the app, thus the user would have to enter it every time.
4. The app currently will work even if there is no Internet connection in the car, which is important if your on a road trip out in the middle of nowhere. The wind data may be old, but the course and speed will still work. Getting GPS data rom the API means that the app would no longer to be able to do anything without an Internet connection.

I have wanted to speak to the guys who do A Better Route Planner and TeslaWaze, as they may have found a way to get the accurate GPS data, but I have not been able to get in touch with them.
 

rrolsbe

Member
Feb 18, 2017
220
126
Albuquerque
The app works by requesting GPS position from the browser via Javascript. This used to work very accurately until Tesla release the v9 software. Ever since then, the GPS data is very quantized and inaccurate. This results in varying heading and speed displayed in the app.

I have not yet found a way to compensate for this or get the old, accurate GPS data from the browser. The Tesla API does have accurate GPS data, so I could read the GPS data from there and it would smooth things up again, but there are several disadvantages to this approach:

1. There would be a delay in getting the data because that has to be requested over the Internet, and the car has to send the data to the Internet as well.The displayed speed and heading would lag behind the actual speed and heading by quite a bit, probably at least 5 seconds, maybe more.
2. My app would have to request your Tesla login so that it could access the API for your car. Many people are uncomfortable with that, and I'm not keen on accepting the responsibility for handling sensitive data in my app.
3. I'd have to build a new UI for gathering the Tesla login from the user, and since my app intentionally does not use cookies or store data on any server, I'd have no secure way to store the Tesla login between uses of the app, thus the user would have to enter it every time.
4. The app currently will work even if there is no Internet connection in the car, which is important if your on a road trip out in the middle of nowhere. The wind data may be old, but the course and speed will still work. Getting GPS data rom the API means that the app would no longer to be able to do anything without an Internet connection.

I have wanted to speak to the guys who do A Better Route Planner and TeslaWaze, as they may have found a way to get the accurate GPS data, but I have not been able to get in touch with them.

Thanks so much for your detailed response. Having the speed and direction from the weather stations, via the internet, is still valuable. Teslawaze also shows wind speed and direction and seems to use the same weather stations; however, it does not show side winds nor calculate the headwind/tailwind component of such. I assume the Model S/X also have the browser/javascript problem?

Thanks again
 

SomeJoe7777

Marginally-Known Member
Mar 28, 2015
2,174
5,601
Houston, TX
Thanks so much for your detailed response. Having the speed and direction from the weather stations, via the internet, is still valuable. Teslawaze also shows wind speed and direction and seems to use the same weather stations; however, it does not show side winds nor calculate the headwind/tailwind component of such. I assume the Model S/X also have the browser/javascript problem?

Thanks again

Correct, all Tesla's are affected, as the problem is somewhere in the browser implementation. Originally, the web browser was based on WebKit (same rendering engine used in Apple Safari), and the GPS worked perfectly. But the WebKit implementation was of an older build of WebKit, and as such it was slow and did not support modern HTML, CSS, and DOM constructs, thus limiting the types of apps, displays, and pages that it could render properly. The slowness was especially an issue on the Model S/X MCU1 units.

With the v9 software, Tesla fixed this by upgrading the browser rendering engine (I forget whether they did an upgraded WebKit or switched to Chromium), and that's when the GPS problems started.
 

About Us

Formed in 2006, Tesla Motors Club (TMC) was the first independent online Tesla community. Today it remains the largest and most dynamic community of Tesla enthusiasts. Learn more.

Do you value your experience at TMC? Consider becoming a Supporting Member of Tesla Motors Club. As a thank you for your contribution, you'll get nearly no ads in the Community and Groups sections. Additional perks are available depending on the level of contribution. Please visit the Account Upgrades page for more details.


SUPPORT TMC
Top