In the previous post we took a look at how the initial just-for-my-own-car implementation was refactored into a version that supported many cars using a database instead of hardcoded values. It also showed that the LogicApp based implementation lost its merrits, and everything was moved into Java code. In this part we’ll take a look at the Tesla API that is used to make the car do things.
Some time has passed since my previous post about fixing the issue that a Tesla does not allow scheduling preconditioning (de-icing) the car prior to a drive in the winter. The original post used an Azure Logic app as its core.
What you see above is a Logic app for my car only; the first step “When an event starts” is linked to a Tesla calendar in my personal Google Calendar. The “StartHVAC” and “EndHVAC” call out to serverless functions that hardcoded contain the data for my personal car. And the emails go to a hardcoded email address of mine. Totally not reusable, but working.
After publishing that post, people started to ask if they could use the same functionality as well. Ahm, I did just say it was not reusable, didn’t I? But being a good friend, I ventured out and rewrote the whole thing to support multiple calendars and cars.
After the (some still present) rattles, the broken rear view camera, the broken LTE modem, and the decorative yellow band around my screen, my car had another surprise for me…
The ‘going electric’ will be different blogs from my usual beat. Not only because they will not be related (directly) to software development, but also because they are opinionated and personal reports; editorials about switching over to an electric car. They will list my personal joys and annoyances about the switch, but I’ll try to be fair and balanced.
After almost a year of driving electric, I’m about to do the one year look back. And it is a two side one. It really is.
Java 9 introduced a major change in the way Java programs are written, because of the Java Platform Module System (JPMS). And that is not something you can ‘skip’ by moving to a higher Java version; upgrading your software to any version after Java 8 means you have to deal with JPMS.
That is the reason a lot of companies are still stuck at Java 8, but at some point in the future they and everyone else will need to upgrade. Java 11 is the first Long Term Support (LTS) version of Java, and that seems to be the version of choice for a lot of migrations.
Upgrading my open source project, JFXtras, to Java 9 a few years back was a breeze. I have had more problems with the build tool (Gradle) than with the modularization of the code. But that is because the code is fairly new and already modularized using Gradle (Maven) artifacts. But in the last weeks I’ve tried to upgrade a 15+ years old custom made ERP system to Java 11… That turned out not to be a breeze.
The ‘going electric’ will be different blogs from my usual beat. Not only because they will not be related (directly) to software development, but also because they are opinionated and personal reports; editorials about switching over to an electric car. They will list my personal joys and annoyances about the switch, but I’ll try to be fair and balanced.
The whole topic about charging at home is confusing when you do not own an electric car, and to be honest I still don’t get it 100%. You can charge from any 220 volt socket, but that does not charge very fast, because that power group may be shared with other appliances. So at least it would be wise to dedicate a single 16 amps power group to charging your car. A single dedicated group should put about 40 km of range per hour in your battery pack. Some simplified math then tells us that a 400 km pack will take about a full night’s to charge (I know it’s not linear, but let’s keep this simple). And even though that will suffice for 99% of the use cases, 10 hours for a full charge is quite some time…
The ‘going electric’ will be different blogs from my usual beat. Not only because they will not be related (directly) to software development, but also because they are opinionated and…
The ‘going electric’ will be different blogs from my usual beat. Not only because they will not be related (directly) to software development, but also because they are opinionated and personal reports; editorials about switching over to an electric car. They will list my personal joys and annoyances about the switch, but I’ll try to be fair and balanced.
So my model S needed to go to the workshop; it seems my headlights were set a bit high (got a lot of flashes and my g/f complained when I was driving behind her), and there is a faint torquing noise coming from the right A-pillar when I drive on uneven roads. First world problems.
But while waiting on the intake on my S, I was asked if I wanted to take a peek at the Model 3. It has been on tour through Europe lately, but I missed the opportunity when it was at my local Tesla shop. So I was quite pleased with his suggestion and eagerly said yes.
The ‘going electric’ will be different blogs from my usual beat. Not only because they will not be related (directly) to software development, but also because they are opinionated and personal reports; editorials about switching over to an electric car. They will list my personal joys and annoyances about the switch, but I’ll try to be fair and balanced.
The weather is getting colder, it is now around freezing in the morning, and I already start to notice serious differences in predicted and actual range. Charged to 85% my Model S75D has a predicted range of 341 km. But after I drove to work this morning, which is a distance of 92 km, the remaining range was 217 km.
Before 2004 the defacto standard build tool for Java applications was ANT. It was a step up from the make-based way of building Java software; it featured standard tasks, like compile and jar, that you needed in most projects. It was a first attempt to make building java applications more declarative.
But as time moved on, and projects become ever more complex, so did the ANT scripts. You ended up with scripts calling scripts, calling scripts, calling scripts, … And soon building an application was just as complex as the average nuclear fission paper. Not even mentioning trying to assemble the right versions of all the dependencies into the libs folder.