NikeWings
Active Member
Just like our cars.Just my luck to have my firmware be outdated the day after installing a new one ;-)
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Just like our cars.Just my luck to have my firmware be outdated the day after installing a new one ;-)
The teslafi software notifications are just notifications that a car in the teslafi fleet has been upgraded to an unseen new version. There's only one X90D reporting the .100 release so far. I added the feature since I like knowing when a new software update is out there. It doesn't necessarily mean your car has the update, you'll be notified via in app or in car if you actually receive the update. The update log on teslafi.com will also show you the history of updates since you signed up. Hoping to make the software update page publicly viewable soon so people can track updates without being a member.Got the .100 today based on TESLAFI notification. Haven't driven the car yet. Been having AP problems, hoped it fixes it.
I don't get this voodoo ritual. What makes everyone think the MCD doesn't reboot on its own when a software update is applied? It would be very difficult to update the software without a reboot.Boot to your heart is content. Some other previous posters have said they do it as standard action after each update.
I believe there is a reboot at least most of the time -- but at least 3 firmware updates since I've taken delivery about 11 months ago, my CID is either frozen afterwards or I have slow/odd problems which are resolved with a reboot. I don't manually reboot as a habit after each update as some suggest, but I'm running about 30% failure rate to-date where a manual reboot after notification of "firmware update is complete" gets me going again.I don't get this voodoo ritual. What makes everyone think the MCD doesn't reboot on its own when a software update is applied? It would be very difficult to update the software without a reboot.
Same here except due to the unpredictable slow/odd problems I just do it as a matter of course while its in my garage rather than dealing with the problem on the road. I'm not sure it makes a difference but I hold the buttons down until the "T" comes up on the screens. I don't remember if I read about that method on TMC or if a Service Technician told me it was like a "cold reboot" as opposed to the regular "warm reboot". I was also told by someone that Tesla had them put their foot on the brake in addition to the "cold" boot for some reason. In any case it doesn't hurt anything.I believe there is a reboot at least most of the time -- but at least 3 firmware updates since I've taken delivery about 11 months ago, my CID is either frozen afterwards or I have slow/odd problems which are resolved with a reboot. I don't manually reboot as a habit after each update as some suggest, but I'm running about 30% failure rate to-date where a manual reboot after notification of "firmware update is complete" gets me going again.
Update and Observation:
Finally got behind the wheel since being upgraded to 32.23.......I usually notice no differences on upgrades and then only if an obvious one is pointed out. But I did notice a change in AP, immediately and it was visual. The neon blue lane lines seemed narrower. The side mirrors of my virtual car were almost riding the lines on each side. So I disengaged it, and the lanes were back to the prior sized images. Ummmm....then I re engaged and after a few traffic ridden miles my car was providing me greater driving confidence, especially when oreo'd by trucks. Maybe there has been some recalibration inwards to control the car in a smaller frame of reference? The visual impact of the narrower blues was instantaneous, not something to over analyze, but a steadier drive was a welcomed result. BTW, I found no material improvements in the UHFS Dolby sounds. Still tweaking the heck out of the equalizer to avoid the tin can.
I just stopped by my SvC today and got 2.32.100. The install was about 5 minutes longer than my last one 2.30.33.Hopefully @Ingineer tells us what changed in .100!
(getting real tempted to drive by a service center)
I just stopped by my SvC today and got 2.32.100. The install was about 5 minutes longer than my last one 2.30.33.
Charged at LAFAYETTE several times. I've only seen other Teslas once or twice.Any idea how many folks stop by the Lafayette Supercharger?
It was a little over two weeks since the last time I got one there if that helps.I stopped by the SvC about an hour ago and haven't gotten anything yet. I suspect that it'll take another week before I get an update
(I also suspect that a day after I get it, 2.32.150 will be out!)
It was a little over two weeks since the last time I got one there if that helps.
Is teslafi.com safe? I get very nervous about my user id and password. Any way to get the token from an official Tesla site?Ok, folks, I've spent the day enhancing EV-FW.com to allow you to add a Tesla API token to your account, and then assign cars from your MyTesla account to the cars on EV-FW.com. You'll need a valid token from some other site (or yourself, if you know how) to add to the site. EV-FW does not ask for your MyTesla login credentials. There are enough sites that do that already.
It's all in "beta" for now, but if you add your token AND assign a car to each record (just "edit" your car and save), the routine will run every few hours to check your firmware version, and update your records accordingly. The program assumes a "wifi" connection, but really that's not an attribute we're tracking much anymore, so it doesn't really matter.
When the system detects a new firmware version, you should get a PM on the forums with a notification. I can't really test this because you can't talk to yourself on Xenforo like you could with vBulletin.
So please try it out and let me know if you have any problems. You can get an API token from TeslaFi.com.
edit: If your token looks like this with three dots in the middle: df75f611f2d94...9c9ee020600a -- it's not a valid token. I've asked Teslalog.com to fix this. Proper tokens are displayed on Teslafi.com
thanks.