ToM+, das einzigartige 2 in 1 Display für den Twizy

PriusTwizy schrieb: Is it necessary?

Not necessary. The touch is still present, of course.

Someone asked me about the button connection.
The button, which isn't necessary for the usage of the touch display, has a cable which ends with a connector.
You have simply to plug such connector to the box, if you want to use the button.
Nothing else (no need to open or solder anything).
Just plug and go.
.

.
All is meant to keep things as easy as possible.

Interessante Lösung.

Wäre das OVMS dann über OBD2-V-Kabel noch kontaktierbar?

Sure!
I usually prefer an OBD splitter like this , instead of a V-cable.

Resin enclosures arrived. They look very fine.
So, first four units are ready.
I'll contact in private who asked me for a ToM+, following the contact order.

I completed also the new charging page, with 3D layout.

Fabio hat mich gebeten folgenden Warnhinweis in Landessprache zu posten:

Achtung, Vorsicht!
Die ersten ToM+ sind nun auf dem Weg zu ihren neuen Besitzern bzw. bereits schon dort angekommen.
Für den Versand hat Fabio das Vorsatzdisplay in das Standalone-Display eingesetzt, jedoch ohne den rückseitigen Deckel zu montieren.
Wir gehen jedoch davon aus, dass die Mehrheit der Nutzer das ToM+ als Vorsatzdisplay betreiben wird.
Um das Vorsatzdisplay aus dem Standalone-Display zu entnehmen, dieses durch leichten Druck auf die beiden Ecken am unteren Bildschirmrand schräg nach hinten drücken.
Im Anschluss sollte sich das ganze Vorsatzdisplay mühelos nach hinten entnehmen lassen.
Keinesfalls mittig auf den Touchscreen starken Druck ausüben.
Solltet ihr das Vorsatzdisplay dabei verkanten, dann drückt es bitte zuerst wieder von hinten zurück nach vorne und unternehmt einen weiteren Versuch.
Die Entnahme erfordert keinen nennenswerten Krafteinsatz, wenn es richtig gemacht wird.
Sollte tatsächlich jemand dabei größere Probleme erfahren, bitte hier melden bevor der Touchscreen zu Bruch geht!

I have received my ToM+ display, whoop whoop! (I already have a ToM "classic" so I only needed the display)

The display was easy to remove from the stand, it almost fell out by itself. I've already test-fitted the display over the Twizy's original blue display and it fits absolutely perfectly. That is a very smart design. I'm sure that took a few iterations on the 3D printer

Now I need to flash my ToM, and because I've never done that, I wanted to be really careful. I'm on ESP firmware 1.8 right now:



I guess I need to follow this procedure to flash to 2.0, is that correct?

And to be 101% certain, do I just press the grey "UPDATE" button in the "FIRMWARE UPDATE" section in the screenshot above? Or do I need to do something else? Of course the ToM will need to be connected to internet, but mine always is.

PriusTwizy schrieb: I guess I need to follow this procedure to flash to 2.0, is that correct?

No. I opened yesterday a specific topic: this .
For updating OTA, just select the file and press update (DO NOT flag update to special partition), and wait it reaches 100% and....

PriusTwizy schrieb: Or do I need to do something else?

... cross your fingers

PriusTwizy schrieb: I've already test-fitted the display over the Twizy's original blue display and it fits absolutely perfectly . That is a very smart design. I'm sure that took a few iterations on the 3D printer

All the credits go to Snorre: he had the idea and did all the modelling work, with a lot of patience.

Yes it works! And I LOVE it!

I'll explore the features tomorrow, but so far it feels like I'm driving a modernised Twizy!

Sigh... inserting a YT video doesn't seem to work, so here's the link www.youtube.com/shorts/7QTntvLABO8

Thanks for the video.
If you want to fill more the power bar, you can adjust the % in the webUI

I did some Twizy driving today, and here are a couple of findings:

The speedometer indicates the "real" speed, it seems to exactly match the GPS speed Google Maps indicates. Going flat out, it shows exactly 80 km/h.

The clock is showing the exact time (because my ToM+ is always connected to the internet when I'm driving). The autistic part of my brain loves this!

I had one occurance where the ToM+ appeared to briefly "hang". I had just switched from Reverse to Drive, and while driving away (forward) I noticed that it still indicated R. Before I could do something, it caught up and was indicating normally. I don't know for how long it was that way, and if any other values didn't indicate correctly. I'll keep an eye on this.

I need to find the correct icon that indicates "km remaining on current charge". The one I think it is (KM with an arrow below it, pointing at a lightning symbol in a cirkel) indicates something else than the value on the original Twizy display. I think I'll need to read the manual - oh no!

Switching from the ToM to the ToM+ firmware confused my Home Assistant. In the "Twizy km total" entitiy, several entries with +/- 2500km appeared yesterday and today, one at 04:00 this morning. I drove around a bit this afternoon, maybe 15 or 20 km, but after removing the 2500km entries, my "total km" counter now only has 2,76 km for today. In the next few days, I'll keep an eye on this. Maybe it'll behave from now on. Have the MQTT messages changed or should these be the same as before?

Thanks for the report.

PriusTwizy schrieb: Have the MQTT messages changed or should these be the same as before?

No, nothing changed.

PriusTwizy schrieb: I need to find the correct icon that indicates "km remaining on current charge". The one I think it is (KM with an arrow below it, pointing at a lightning symbol in a cirkel) indicates something else than the value on the original Twizy display. I think I'll need to read the manual - oh no!

Sooner or later I'll update the manual.

There are 3 icons for the remaining kms

The first matches the value displayed by the original speedometer.
The second (2) is the alternative way to calculate the remaining Km, introduced since 2.1 fw. You can set the parameters of this calculation in the advanced sets of the webUI, to adapt it to your driving style / trip type.

Sampling time (in minute) it's the frequence for reading the kms you drove after the previuos reading. Sample weight (in %) is the weight for the last reading of driven kms in the calculation algorithm.
If you go at low speed, increase the sampling time and the sample weight.
Starting the trip, the algorithm takes as base the value displayed by the original speedometer.

The third (3) is for the remainin Km, calculated with the media data of the current trip selected.

PriusTwizy schrieb: The speedometer indicates the "real" speed, it seems to exactly match the GPS speed Google Maps indicates. Going flat out, it shows exactly 80 km/h.

It shouldn't be in this way. It's increased by 10%, like is normal for the EU speedometers.

Delvecchio schrieb: Thanks for the report.

PriusTwizy schrieb: Have the MQTT messages changed or should these be the same as before?

No, nothing changed.

OK, I have (partly) found out what happened.

The 2500km entries are general Home Assistant confusion. I've seen this before when changing actual hardware that feeds data into the same HA entity.

The underreporting of the total km is interesting. With the previous firmware, the total km was overreported by a factor of 10. I can't remember how or where, but I think the decimal point got lost somewhere in the data chain. So, in the config of the MQTT sensor, I divided the incoming value by 10 (by multiplying by 0,1 - I have NO idea anymore why I did it this way ):



This has worked fine for the entire time I used the ToM on FW version 1.8. Apparently, with the new firmware, something changed, because yesterday the system reported 2,76 km, while 27,6 km seems quite plausible:



I've removed the "multiply by 0,1" factor, I'll do some driving today, and see if the total km matches the Twizy's odometer. I'm optimistic that this is solved.