[Twiz O'meter/BigToM/ToM+] Update to firmware 2.4

Akku61 schrieb: You think, the settings of the rozhkov BMS and the settings of ToM get in conflict

Not the settings, but since ToM switches on/off following BMS/charger handshaking, I suspect there is something which doesn't match there.
If ToM won't switch off after charging with the good-bye animation, this will be the proof.

In Germany, we have a saying: "a watched pot never boils!"
The logs from the test today were stored, even the charging from 76% to 100% (log 3, which hasn't been completed since days)!
In Deutschland gibt es ein Sprichwort: „Ein beobachteter Topf kocht nie!“
Die Protokolle vom heutigen Test wurden natürlich gespeichert, sogar das Protokoll vom Ladevorgang von 76 % auf 100 % (Log 3, welches seit Tagen nicht abgeschlossen wurde)!


The "goodbye-animation" was showed.
I recorded a video you can see here:
Die „Abschied-Animation“ wurde angezeigt.
Ich habe ein Video aufgenommen, das ihr hier sehen könnt:
www.iamscout.de/video/goodbye.mp4 (6MByte)

I also recorded a short sequence where you can see the charging power jumping up and down:
Außerdem habe ich eine kurze Sequenz aufgenommen, in der man sehen kann, wie die Ladeleistung hoch und runter springt:
www.iamscout.de/video/jumping.mov (6,7 MByte)

One thing I changed before: i completely disconected the ToM from the OBDII-plug for 20 seconds to be sure ToM will make a restart with the next wakeup.
Eine Sache habe ich zuvor geändert: Ich habe das ToM für 20 Sekunden vollständig vom OBDII-Stecker getrennt, um sicherzustellen, dass das ToM beim nächsten Aufwachen einen Neustart durchführt.

I'll keep an eye on the charging logs and report back.
Ich werde die Ladelogs weiter im Auge behalten und wieder berichten.

Akku61 schrieb: In Germany, we have a saying: "a watched pot never boils!"

In Sicily they have an identical proverb:

"La pignata taliata un vugghi mai."

Never used in northern Italy.

Thanks for the tests and for the detailed videos.
Happy my suspect was unfounded.
I'll add some extra controls to avoid "frozen" entry in the charging history.
As soon as finished, I'll post the update here.

Delvecchio schrieb: Ok, this is the fix for deleting error list from the webUI.
but I'm sure it will work.

It took me a few days before I could update and test, I was away for a few days, but I can confirm: this now works as it should. I was able to delete the historic errors, and the little ERR icon disappeared.

Interesting. My ToM doesn't seem to always store the KWH and KWH/100KM fields:



I upgraded to 2.4 on July 24th, but it doesn't seem to have anything to do with that. It happened sporadically before, but over the last four drives it didn't register those at all. Any idea what could cause this?

It's not a big issue for me, I store all drive data in Home Assistant, but it's odd.

These history logs are giving me a terrible headache.

I did not mean to give you a headache

I don't look at at page often, that's why I only noticed it now. And like I said, the information I actually want to collect, I get from Home Assistant. And that works great!

A question about wifi: there's an ESP32 inside the box, right? Does the ESP32 have one of these tiny coaxial connections for an external wifi antenna? I still have reception problems when the Twizy is parked in my driveway. My home wifi is barely strong enough at that location. Adding an external antenne might improve that.

PriusTwizy schrieb: Does the ESP32 have one of these tiny coaxial connections for an external wifi antenna?

No, sorry. The antenna is integrated in the chip modulo è.

@Delvecchio So far the latest FW has shown no anomalies or bugs for me, I like it!

But I like to request a small optimization on the main display: while driving in bright daylight it is very hard to see the red part of the power bar. For the naked eye the difference between the black background and the dark red are barely visible. Of course in the dark it's well distinguishable. Could the red please be a bit brighter, more "alarming"?
From a GUI perspective the "segments" on the original screen are clearly on and off, the new and better display should keep that idea in mind and the show it equally well visible.

Thanks a lot for your great work and constant support, Fabio

Thanks for the report: I'm happy you like the new look!

kengelbr schrieb: I like to request a small optimization on the main display... Could the red please be a bit brighter, more "alarming"?

No problem, I'll do it.
I had a similar request also for the orange font (the one used, for example, for battery temperatures in the info battery page) and the optimization is already running in the beta fw I'm running in my device.
So, I'll add both in the next fw release.

Thank you very much!

Delvecchio schrieb: Thanks for the report: I'm happy you like the new look!

kengelbr schrieb: I like to request a small optimization on the main display... Could the red please be a bit brighter, more "alarming"?

No problem, I'll do it.
I had a similar request also for the orange font (the one used, for example, for battery temperatures in the info battery page) and the optimization is already running in the beta fw I'm running in my device.
So, I'll add both in the next fw release.

kengelbr schrieb: Thank you very much!

Can you try and tell me if the red is enough lighter?

Delvecchio schrieb:

kengelbr schrieb: Thank you very much!

Can you try and tell me if the red is enough lighter?

Thank you!
I just updated the TFT (flawlessly!) and turned a round with the Twizy. It already looks much better/brighter, but I'll have to see it tomorrow in the sun during my lunch break to give you a final feedback.

Hmm, today the colour looked unchanged, as if the display somehow did a reset. Is that possible?





Is there something I did wrong while updating the display?

Another thought, which just came to my mind: my Twizy is one of the models which has the light turned on the moment the key is turned. And I know the Twiz-o-meter dims the display when the light is turned on... could that be the reason why it looks rather unchanged, is it really just a dimmed backlight or even a different colour pallette?

kengelbr schrieb: Hmm, today the colour looked unchanged, as if the display somehow did a reset. Is that possible?
Is there something I did wrong while updating the display?

No, not possible and you did wrong nothing.

kengelbr schrieb: Another thought, which just came to my mind: my Twizy is one of the models which has the light turned on the moment the key is turned.

This is probably the cause, but it's easy to fix/verify.
With my display you can both disable the auto-dimming and set the percentage of dimming brightness.
Access the webUI and go to the "advanced setting" tab, where you'll find the dimmer settings.