-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Jays200
Member
vrykolas
Member
It's Google wifi (app & device) which allows easy/automatic teaching of data usage per device in real-time or over a period of time
Xenius
Active Member
+1 for google wifi. I really need to see if I can isolate the tesla on mine to see this kind of data.
Cirrus MS100D
Member
I don't have a pretty chart like that, but my home WiFi (TP-Link) does show a similar pattern:
8-21-17: >5MB
8-22-17: >10MB
9-3-17: 7MB down / 358MB up
9-3-17: 6MB down / 100MB up
9-4-17: >5MB
Interestingly, the only driving done on 9-3 was a round-trip to/from home to EWR airport (about 130 miles total.) A majority of the drive to/from was done using Autopilot on Route 195 and 95/NJ Turnpike.
8-21-17: >5MB
8-22-17: >10MB
9-3-17: 7MB down / 358MB up
9-3-17: 6MB down / 100MB up
9-4-17: >5MB
Interestingly, the only driving done on 9-3 was a round-trip to/from home to EWR airport (about 130 miles total.) A majority of the drive to/from was done using Autopilot on Route 195 and 95/NJ Turnpike.
It's not terribly hard to do. It'll show up as an unidentified device(just an IP address), where most other things on the network show up as named in some way. So turn off as many wifi devices as possible, connect the car to wifi and see what shows up. Then you can edit the name to whatever you want.
On the general thread: I went back and looked at my stats and, sure enough, massively increased uploads. Looks like Karpathy is doing his job.
DaddyP713
Member
Holy crap, that's impressive! 3.3 GB...mine averages a few hundred MB, but I'm a few releases back...
Hugh Mannity
Mediocre Member
Looks like it's data the car is sending to Tesla (or somewhere). Not data the car is downloading.
thecloud
As rhythm raced inside, the ship came alive
"Uploading" means the car is sending data to Tesla, not receiving data from Tesla.
Hugh Mannity
Mediocre Member
One theory I'll propose:
Take a look at the TeslaFi breakdown for AP2: Around 20% are still on some form of 2017.28, 45% on 2017.32.x, and 13% on 2017.34. And the rollout of 2017.28 -> newer has basically stopped for AP2 (the most 2017.34 reports are from people with 2017.32.x or who had a SvC appointment).
Given that 2017.34 has increased the telemetry parameters for snapshots, I strongly suspect they have placed multiple control strategies in the field and they are trying to gather data on which works the best, before they upgrade everybody to a newer version.
Take a look at the TeslaFi breakdown for AP2: Around 20% are still on some form of 2017.28, 45% on 2017.32.x, and 13% on 2017.34. And the rollout of 2017.28 -> newer has basically stopped for AP2 (the most 2017.34 reports are from people with 2017.32.x or who had a SvC appointment).
Given that 2017.34 has increased the telemetry parameters for snapshots, I strongly suspect they have placed multiple control strategies in the field and they are trying to gather data on which works the best, before they upgrade everybody to a newer version.
There are also another more mundane explanations.
Every time an autopilot process crashes, a crashdump is uploaded to Tesla.
The random snapshots are controlled independently of software version so should not depend on a particular version.
It's possible they started to collect more data that is car/firmware originated of course (e.g. they used to collect FCW snapshots and then stopped), I guess I'll try to verify this once I get my hands on this release.
Curious….. That makes me wonder instead if this new build is just crashier than previous ones and that's why it's generating more traffic.
BTW, with root, are you able to control what firmware gets installed on your car? I recall one of the previous tinkerers saying that he found a way to do so but won't say any more than that for fear of it going away….
Even without root as long as you have the actual firmware file you can ask the car to install it. Now getting that firmware file somehow is a totally different matter.
So.... I got this release installed and did a short two minute trip and...
in fact I have a whole bunch of them as it turns out. All from Vision task, about 2M each. I'll try a longer drive soon to see the accumulation rate, I guess.
Code:
2017-09-07_13:40:08.xxx-0700 Trigger core dump snapshot
2017-09-07_13:40:08.xxx-0700 I0100 00:00:00.000000 2935 snapshot_task.cpp:264] RAW: OneShotRequest available in queue
2017-09-07_13:40:08.xxx-0700 I0100 00:00:00.000000 2935 snapshot_task.cpp:771] RAW: Calculated xxx free bytes on disk
] RAW: Uploading archive: anonymize = 0
2017-09-07_13:40:08.xxx-0700 I0100 00:00:00.000000 2935 snapshot_task.cpp:639] RAW: Wrote /home/telemetry/snapshots/snapshot-119ce422-f5b0-4f15-8e9e-c46cc2440823-0000.tgz, requester: core-dumpin fact I have a whole bunch of them as it turns out. All from Vision task, about 2M each. I'll try a longer drive soon to see the accumulation rate, I guess.
Last edited:
Similar threads
