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

This firmware release is just to wish a Merry Christmas to all Twiz o'meter friends .

What is new in firmware 2.2
=================================
- added the possibility to show DF error numbering and error decription both in the display and in the webUI. In the display, tap on the DF number for showing the description.
Since the origin of this data is not clear (the data has been shared in a post found in internet), enabling this function is up to you and under your responsibility.
In the "password 4" field, enter GIVE_ME_DF! (exactly as wrote here, also with underscore and exclamation mark), and press OK
- added timezone settings, in Time & Date page of the webUI, so also foreign owners outside EU can properly set the time and date
In the timezone fields enter the desired posix string. You find the strings, for example, here: github.com/nayarsystems/posix_tz_db/blob/master/zones.csv
- added the possibility to wake-up ToM in case of Twizy system error. Press the control button and keep it pressed while you switch ON the OBD switch.
In this way you can read the errors, also when they prevent your Twizy to be switched to GO
- added a new pref in "Advance info & settings" of the WebUI, for customizing the brightness in dimming mode
- added a new pref in BigTom/ToM+ prefs, for choosing if you want the speedometer page to show the real speed or not (in this case it will be increased by 5%, like the original speedometer does)
- added a new pref in BigTom/ToM+ prefs, for skipping the welcome animation, so to improve the driving exerience
- for BigTom/ToM+, now the power bar is multicolor, with the last steps in yellow and red, when you are reaching the maximun value

Bug fixed:
=================================
- fixed a problem in the Json mqtt payload, with total mileage value
- increased a little the delay for the auto-dimming intervention, to avoid flickerings of the brightness. Really, this wasn't a bug of ToM fw/hw, but a problem of other devices. So this is just a workaround to avoid the issues caused by these devices.
- removed in the WebUI some Advanced informations unavailable when an alternative BMS is installed
- some minor bugs and cosmetic graphical issues have been fixed

Known bugs:
=================================
- awaiting for your reports!

Special thanks goes to:
================================
- Snorre, always ready to give me his help and his precious contribution. Like I already wrote elsewhere, ToM+ wouldn't be born without his perseverance.
- Binkino for providing me an useful canbus log and some specific informations which helped me in bug fixing
- PriusTwizy for pointing me, with his mqqt tests, to find the solution of the Json mqtt payload problem with total mileage
- our new friend Hiko_taka who suggested a few ideas to make the device more "japanese friendly"

Updating procedure:
=================================
To install the new fw you must update both the Blackbox and the screen display as explained in detail in ToM manual except for these further instructions:
- coming from 1.4 fw (and later), the Blackbox can be updated also via OTA, without flashing
- coming from previuous versions (1.3 or 1.2) you have to update before to 1.4 (or 1.45) fw version, following the specific instructions reported in 1.4 / 1.45 topic, and only then to 2.2 fw.
If you won't update also the screen firmware you'll experience impredictable issues.
ToM+ owners are suggested to use the little micro-SD extension for performing the update. This extension will make easier to insert/extract the microSD.

Please remember that, while the firmware file for the Blackbox (ESP32 file) is the same for ToM, BigToM and ToM+, the display LCD firmware files are different, so choose inside the .zip archive the firmware file designed for your display device.


That's all... for now!

---

Akku61: changed the zip-file to the fixed version

Buon Natale Fabio and again many thanks for your work for our Twizys. Thanks a lot also for all users who are supporting you for improving our ToM.

Today I've updated my ToM and everything works fine. Unfortunately I'm not quit sure how to deal with this information to activate the DF translation.

Delvecchio schrieb: ...
What is new in firmware 2.2
=================================
- added the possibility to show DF error numbering and error decription both in the display and in the webUI. In the display, tap on the DF number for showing the description.
Since the origin of this data is not clear (the data has been shared in a post found in internet), enabling this function is up to you and under your responsibility.
In the "password 4" field, enter GIVE_ME_DF! (exactly as wrote here, also with underscore and exclamation mark), and press OK
...

Do you mean the key 4 field in the WiFi settings? If yes must it be done in the webUI or in the ToM-display? And must something be inserted in the ssid 4 field?

Thanks for you comment.

About DF activation, you are right. I wasn't so clear before.
"password 4" is "key4" field.
It works only from the display (not webUI), like a "back-door" for special configuration commands.
No need to modify ssid4.
If you already configured ssid4 and key4, your settings won't be affected, but only if you enter the correct command string.

Ah, okay, that's why I was confused.
For me, the settings were exclusively for the Wi-Fi connection...
Then my email to you has already been partially taken care of.


Ah ok, deswegen stand ich auch "auf dem Schlauch"
Für mich waren die Einstellungen ausschließlich für die WLAN Verbindung...
Dann hat sich meine Mail an dich schon teilweise erledigt.

LG Tom

I received a report of a bug which affect only ToM display (not BigToM or ToM+).
If you activate the DF & error description, the last (seven) row in the trip and alarm log is missing in the first page.


Thanks to Akku61 for making the above image to clarify me the problem!

Furthermore, deleting error from the webUI seems not working.
So I release here a fix for both the problems.

In the meanwhile, I took the opportunity to add an extra feature for speedometer page. Now the speed limit alerts are three: green for low limit, yellow for medium and red for high.
If you don't need one, you can set it to 0 (then it will be auto-set to 150, which means disabled). All the limit alerts have min 0 kmh and max 110 kmh possible values.
They will be processed in this order: high, medium and low limit. So, the fw will display the first alert which satisfies the speed condition, according to that order.
In this way, if you set, for example, the medium limit higher than the high limit, the medium will never take effect (this is the reason why I set the unused limit to 150 kmh).

Everything is going perfectly! Thank you, Fabio!









LG Tom

The pictures were taken on a private road, of course.

Thanks for the report.

Is minion Kevin the ToM's guardian?

A suggestion: if you want the powerbar to be more reactive, decrease the values in the blue square.
Set, for example, the up section to 50% (it's the green part of the bar), and the down section to 30% (it's the blue part of the bar).

Delvecchio schrieb:
Is minion Kevin the ToM's guardian?

Banana, banana...

...he feeds the ToM...

Until I find the right size Doozer...

LG Tom

Tom: Is windshieldheater enabled? To much energy in the traction battery? Or switch just enabled?

Happy New Year

kloetzle schrieb: Tom: Is windshieldheater enabled? To much energy in the traction battery? Or switch just enabled?

Happy New Year

Yes, I just activated it...

Happy New Year

LG Tom

Gibt es ein Anleitung hier? Ich blicke da nicht durch. Ich weiß garnicht was mein Big kann oder eben nicht. Vielleicht habe ich auch nicht korrekt gesucht. Aber das Display ist sehr nice!!!!!

You can start from the normal ToM manual here .
Except for the adding of the speedometer page, the function are the same.
Unfortunatly the manual isn't updated to the features added after. For these, you can look at the change log of the last fw.
I'll take care to update the manual sooner or later.

Daaaanke