VisibleTesla

[BozieBeMe2]

Thanks a lot for this! Good job!

Thanks for the link.
I rely on VT to track my battery SOC and my current version wasn't responding after Tesla redid their servers.

 

[Benjamin Brooks]

Anyone else no longer seeing battery current (coming back as NaN in VisibleTesla fields) after upgrading to FW 8.1?
Has the API changed for accessing battery current in FW 8.1?

 

[MarcG]

Anyone else no longer seeing battery current (coming back as NaN in VisibleTesla fields) after upgrading to FW 8.1?
Has the API changed for accessing battery current in FW 8.1?

Yep, battery current is gone as of 8.1

 

[AWDtsla]

Anyone else no longer seeing battery current (coming back as NaN in VisibleTesla fields) after upgrading to FW 8.1?
Has the API changed for accessing battery current in FW 8.1?

#Countergate. You can't know what the battery current is, so Tesla can reduce it as they see fit.

 

[Ulmo]

FYI, I post this information for the use of those who are programming third party programs to interpret MotherShip data, for ideas of how to solve some issues. You should already have figured this out, but this is just for reinforcing clarity, if you haven't already done so or someone is new to it. Here is VisibleTesla's connection to an EVGO Chademo and what's actually happening in the car on the TouchScreen, both pictured below. Note:

• It says "Current" is 0 amps. That is not true.
• It says "Voltage" is 328 volts.
  
• It says "Pilot Current" 48 amps. That's leftover from my home charger (HPWC), which current-limits my home circuit because the PG&E pole has poor wiring and should say 80 amps, and is the last time I used the onboard AC charger.
• It says "Battery Current" "NaN" amps. NaN is the way that VisibleTesla says it doesn't have a numeric value; I don't actually know what type of lack of data it is (such as if it is null, void, error, or some other type of data lack), just that it is a data-lack.
  
• It says that it is a "SuperCharger", which I think may mean DC (rather than AC), which is stupid because it's only 30kW, which is not much more than a 72 amp or 80 amp on 250 volt AC system (19kW - 20kW max).
• It says "Charger Power" is 29kW. That means you could calculate Current from Volts and Power.
• It also has Battery Power which you could track in time to calculate the other things and refine calculated data.

These pictures were taken some minutes apart, so the numbers don't correspond in time. There is the usual amperage loss in both the cord and from my climate system being on, but there is also status change in time. FYI.

 

[MarcG]

@Ulmo Tesla removed batter current from its latest 8.1 firmware releases, so apps like VT can't read that through the API anymore.

 

[serioustiger]

Hi all

Highly random question...can VT get a history of the Energy graph for every time it refreshes? (every 0.1 or 0.2 miles or so in the 30-mile view).

The off the wall reason for this question is music...I was thinking if I could get groups of 256 screenshots of the energy graph as it evolves, I could use them to create wavetables for a synthesiser such as Serum. Could produce some interesting wavetables ("interesting", not necessarily "good", but it would be fun to try).

Or if not VT, is there another way?

I realise I am addressing an extreme niche here...

 

[MDK]

can VT get a history of the Energy graph for every time it refreshes? (every 0.1 or 0.2 miles or so in the 30-mile view).

VT keeps a complete record in the $VIN.pts.data file with each of the values you can graph, plus odometer, speed, heading, latitude and longitude. When it detects the car is moving it refreshes this data every ~31 seconds

Here's some data I parsed from a short trip last night. Is this the kind of thing you're after?

Sun May 14 20:12:39 2017 speed: 65.0 km/h odo: 32587.6 km power:  12.0 kW
Sun May 14 20:13:15 2017 speed: 65.0 km/h odo: 32588.3 km power:  18.0 kW
Sun May 14 20:13:46 2017 speed: 65.0 km/h odo: 32588.8 km power:  14.0 kW
Sun May 14 20:14:22 2017 speed: 65.0 km/h odo: 32589.5 km power:  16.0 kW
Sun May 14 20:14:54 2017 speed: 65.0 km/h odo: 32590.1 km power:   8.0 kW
Sun May 14 20:15:26 2017 speed: 64.0 km/h odo: 32590.6 km power: -16.0 kW
Sun May 14 20:16:06 2017 speed: 52.0 km/h odo: 32591.2 km power:  11.0 kW
Sun May 14 20:16:38 2017 speed: 43.0 km/h odo: 32591.7 km power:  19.0 kW
Sun May 14 20:18:42 2017 speed:  1.0 km/h odo: 32591.8 km power:  14.0 kW
Sun May 14 20:19:24 2017 speed: 32.0 km/h odo: 32592.2 km power:   8.0 kW
Sun May 14 20:20:02 2017 speed: 15.0 km/h odo: 32592.5 km power:  -5.0 kW
Sun May 14 20:20:43 2017 speed: 14.0 km/h odo: 32592.8 km power:   5.0 kW
Sun May 14 20:21:20 2017 speed: 36.0 km/h odo: 32593.0 km power:  -1.0 kW
Sun May 14 20:21:56 2017 speed: 32.0 km/h odo: 32593.3 km power:  17.0 kW
Sun May 14 20:22:27 2017 speed: 30.0 km/h odo: 32593.5 km power: 172.0 kW
Sun May 14 20:23:01 2017 speed: 30.0 km/h odo: 32593.9 km power: -37.0 kW
Sun May 14 20:23:33 2017 speed: 24.0 km/h odo: 32594.1 km power:  -9.0 kW
Sun May 14 20:24:06 2017 speed: 28.0 km/h odo: 32594.4 km power:  13.0 kW

Joined:Jun 13, 2015
Messages: 1

I always enjoy seeing long-term lurkers come out of hiding. 23 months is an excellent effort

 

[serioustiger]

Thanks MDK

I think that's something I can work with, thank you.

I would love to say I've been lurking these past two years but the truth is I joined in advance of delivery of my S, and haven't been back since until I wanted something

 

[Siggy101]

Hi all,

My first post here since I bought my S90D.
I have installed the windows version of VT and logged in but I seem to get a different VIN/car showing on the overview page.
My VIN starts with 180xx but I get a VIN showing P08714. Even stranger is that it has no wheels (unlike my car), a sunroof (unlike my car), a 60kW pack (unlike mycar). Basically, it is not connected to my car.

Can anyone advise what's up? I have tried logging out and back in as well as clicking refresh. Weirdly, the odometer and estimated range are correct for my car.

 

[msnow]

Hi all,

My first post here since I bought my S90D.
I have installed the windows version of VT and logged in but I seem to get a different VIN/car showing on the overview page.
My VIN starts with 180xx but I get a VIN showing P08714. Even stranger is that it has no wheels (unlike my car), a sunroof (unlike my car), a 60kW pack (unlike mycar). Basically, it is not connected to my car.

Can anyone advise what's up? I have tried logging out and back in as well as clicking refresh. Weirdly, the odometer and estimated range are correct for my car.

It's very old and hasn't been supported in years. In addition the Tesla API has had significant changes. I don't know how useful this would be anymore. Take a look at Teslalog and TeslaFI. Cloud-based and supported but not free.

 

[Siggy101]

Ah hah. Thanks for the info. I was a bit confused as to why it didn't have the 90D in there too and that all makes sense now.
It's a shame that it seems to cost about $5 a month for this sort of info now. Maybe I will just drive the car and enjoy it.

 

[smilepak]

I downloaded and follow instruction

Installing and Using the Windows Package
Using the VisibleTesla package for Windows is pretty easy:

1. Download VisibleTesla.zip to your Downloads folder by clicking here.
2. Double click the zip file and a window will pop up showing you a single folder named something like VisibleTesla 0.30.00. The actual numbers will vary - that's the version number.
3. Drag that folder to your Desktop or anywhere else you'd like, and open it up.
4. Double click the file named Make_Windows_Shortcut and you'll see a VisibleTesla icon appear on your Desktop.

That's it - you're ready to go. Just double click the VisibleTesla icon on your Desktop any time you want to run the app.

I keep getting login failed. Any idea?

 

[Duma]

Sadly, the developer of this application stopped supporting it about two years ago. While the source code is available, no one else has stepped forward to take over support. There is some discussion around January 2017 a couple of pages up in this forum about what is involved.

As mentioned in several posts just above, the application does not understand, and therefore display, the feature codes for post 2015 Tesla's, so it is likely not worth the effort to get the app running if you have a newer Tesla. You might want to consider a newer cloud hosted version at TeslaFi.com Tesla Model S X Data Logger.

Judging by your TMC membership date you may have a 2015 Tesla and are just late getting to VisibleTesla. If you want to soldier on, your first problem is that it appears that you downloaded the version of the app from the link at the beginning of the forum. This old version does not work at all because the Tesla changed the API used to get information from the Tesla server. Here is a link to a recent post that includes a further link to the most recent version: VisibleTesla.

You may also want to know that the Tesla API is real time only - no access to historical data. If you are using VT to collect data, you need to keep it running all the time.

 

[smilepak]

Thx

 

[Jonas_man]

is there any interest in a desktop app for Tesla? Isn't ppl nowadays just using mobile apps?

 

[Tam]

is there any interest in a desktop app for Tesla? Isn't ppl nowadays just using mobile apps?

I prefer desktop more than mobile.

It's bigger, easier with a keyboard. I can see better and multi-task with different windows...

 

[dpskipper]

I'm working on my own windows app. Its been in development for almost a year but I'm not ready quite yet to make a post on TMC and let everyone know about it. If you would like the URL to the website and download v.1.0, send me a PM.

 

[CdnRedRocket]

Am I the only person who would like a Windows 7 desktop app? I don't have any Windows machines above Windows 7.

 

[scaesare]

I'm working on my own windows app. Its been in development for almost a year but I'm not ready quite yet to make a post on TMC and let everyone know about it. If you would like the URL to the website and download v.1.0, send me a PM.

awesome thanks... PM sent.