Ok, tell me again why NC is so far* away from Montreal? I'd really like to see that in person!
*Just checked and looks like it would take me just over 17h to get there (EVTripPlanner), not too bad.... and free 
Come on down!
Well, been investigating some stuff with my car's dev mode a little. Found something I found pretty interesting.
So, I set the cruise at 55 MPH on a road. With range mode OFF the car is not using the front motor at all. The front motor is sleeping. If I flip to range mode, the front motor takes over and the rear motor sleeps. Like, pretty much instantly and is imperceptible. In range mode the rear motor barely comes alive even during full regen where I saw the front motor alone putting out 72kW at one point today. During initial acceleration, unless it's very light, the rear motor will kick in for a short bit then go back to sleep. But in range mode ON the majority of the time it appears just the front motor is used and in range mode OFF the rear motor is mostly used. Kinda cool, and weird I guess.
Good to know in any case.
Also, engaging max battery power changes the battery pack heating target to
48C. It also bumps the passive and active cooling targets to 50C and 52C from 30C and 50C respectively. That's pretty crazy. Definitely not going to use this feature for much of anything. Definitely would not suggest it for pre-heating the pack like some have suggested. Additionally, if range mode is on the car will not actively heat the pack even in max battery mode.
Got this nifty debug screen to show:
And I found the option I wanted, which was the only reason I actually allowed the car to update to 7.1... (yes, I went through the staged binaries a bit before updating).
This really needs to be an exposed toggle in the UI. In case it isn't obvious, this is the toggle that disables the stupid speed limit + 5 MPH autosteer restriction they just added (which was hard limited at 45 MPH initially in the betas apparently). Some proof of someone speeding in my P85D (I plead the 5th...):
The little "Dev Readouts" dash app is actually not made for the dual motor cars and doesn't seem to have ever been updated, so some of the data is wrong. I'll probably make my own eventually.
I've got cross-compiling working and can run compiled code on the CID and IC now.
Code:
root@cid:/home/wk057# cat hello.c
#include <stdlib.h>
#include <stdio.h>
int main() {
printf("Hello Tesla World!\n");
return 0;
}
(--cross-compile on dev machine--)
root@cid:/home/wk057# ./hello
Hello Tesla World!
root@cid:/home/wk057#
And since the GUIs run on Xorg, pretty simple to overlay stuff on top of the Tesla UI. Especially on the IC where there is no input. I'll probably work on that at some point, but I did a hello world X version to make sure it worked and it works fine.
Let's see... what other goodies...
Can enable Spotify from the diagnostic screen. It replaces Slacker, which sucks. And the quality is terrible compared to Slacker. Terrible. I'm not one for being picky on sound quality, but, they definitely have Spotify set to a much lower bitrate. I didn't keep it enabled. I like Slacker better still. It should probably be an option, though, even for us USA folks. The Spotify search interface is certainly way cooler:
That's about it for now. Still working on parsing some more CAN messages, too.
