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

Thank you all for the great tricks, hints and hidden features, it's such a helpful community here, I'm very happy

Delvecchio schrieb: I attach the fix for the gear letter.
You'll find also a new settings, in the advanced webUI page: "Wheel circumference factor".
It was asked by a very new BigToM owner (he is waiting for the delivery of the device), who has wheels with a little larger diameter and so the speed and driven Km aren't corrected displayed by the original speedometer.
Normal factor is 1,000, if for example, you have wheels with +0,5 cm (= +0,3 %) bigger than standard ones, that means you have to enter 1,003 (it works like a multiplicator factor).
I had no much time to test this features, so, in case you see strange things, please report here.

Two success feedbacks: I did my first OTA update with success, and the small bug with the gear-letter is gone. Thank you!

PriusTwizy schrieb: Interesting symptom: ToM won't connect to my phone anymore:

After a lot of playing around with different phone, different hotspot, exploring wifi/network settings, connecting with multiple laptops to phone hotspots etc I think I've identified the problem. In my phone hotspot I had not defined a password. The hotspot is only switched on when I drive the Twizy, so I considered the security risk minimal. This worked without a problem on FW 2.1.

When I switched on WPA and entered a password, the ToM now connects. I didn't test it further, because I was too happy that it now worked.

However, I have three other problems:

* MQTT connection is very unreliable. After being connected for a couple of seconds, the MQTT icon becomes grey, and MQTT messages stop coming in on my broker. When I click the icon, it sometimes reconnects, sometimes not. This was rock solid on FW 2.1.
* The touch screen occasionally becomes unresponsive. When it happens, touching it does nothing, and then after a couple of seconds, it responds again.
* When trying to clear the two stored DTC errors, I get a "Not found" error. See screenshot:


I'll test it some more when actually driving, I'm willing to give it some more time. But I do already have a question: can I downgrade to FW 2.1? That version was rock solid, and especially the MQTT not being reliable messes up my statistics in Home Assistant, and makes the reducing of the charging power unreliable.

I changed nothing to MQTT, so it's strange.
I suspect, in your case, that the unresponsive screen is related to MQTT connection attempts.
About wi-fi I only changed the lost connection recognition. May be this has side effects on MQTT. I have to check.

Hotspot without password still work (it's the usual way I connect to ToM).

Downgrade is possible, but you must downgrade also the display.

today the display turned black while driving, that was new

I think I will have to relocate the OBD2 into the dashboard, hoping heat is not a big issue there....

No temperature warning before?

I only noticed that the display had suddenly gone dark

Delvecchio schrieb: I changed nothing to MQTT, so it's strange.
I suspect, in your case, that the unresponsive screen is related to MQTT connection attempts.
About wi-fi I only changed the lost connection recognition. May be this has side effects on MQTT. I have to check.

Hotspot without password still work (it's the usual way I connect to ToM).

Downgrade is possible, but you must downgrade also the display.

I made a short test drive last night and, interestingly, it worked perfectly fine. I started up the Twizy, wifi connected to my phone, MQTT established connection, and for the five minutes or so I drove around MQTT data got sent.

As it seemed to work fine, I didn't use the touch screen much, but it appeared to work fine.

Only thing that still doesn't work is that I can't clear the stored errors via the web page. I now tried it on my phone and it gave the same error as when I tried it on my laptop.

I'll keep an eye on it during the next coupe of drives but it appears to be fine now!

I'll look later at the delete error.
May be I miss something.
Is Always the error "page not found"?

Delvecchio schrieb: Is Always the error "page not found"?

Correct. I've tried it three times now, twice from my laptop (Brave, Chrome, Firefox) and once from my phone (Brave) and I got that result very time.

PriusTwizy schrieb:

Delvecchio schrieb: Is Always the error "page not found"?

Correct. I've tried it three times now, twice from my laptop (Brave, Chrome, Firefox) and once from my phone (Brave) and I got that result very time.

I can state this.
Same here.

As a workaround you can delete the errors using the touchscreen.

Ok, this is the fix for deleting error list from the webUI.
My fault: I simply wrote delErr instead of delError inside the code , so the page wasn't found.
I didn't test it due to a lack of technology (no Twizy & no ToM available at the moment.....), but I'm sure it will work.

I made a few trips in the Twizy today, and my ToM is rock solid. I can't explain why it misbehaved just after I updated it to 2.4

The "only connect to the listed SSIDs" option works perfectly, by the way. My Twizy now doesn't connect to the wifi of the supermarket across the street anymore. Really happy with that, because in my driveway, that wifi is stronger than my home wifi but it has a welcome webpage that the ToM can't click past. So when it connects to that it has wifi connection but no internet connection.

A question: I read that the Magicbox can also tune post-2016 Twizy's ( here ). I don't want the extra speed and torque but I would love more regenerative breaking. Is it possible that the ToM could ever do something like this?

PriusTwizy schrieb: ... I would love more regenerative breaking. Is it possible that the ToM could ever do something like this?

In theory: maybe
In real life: probably not

It´s already possible to configure the ToM blackbox as a dual boot system and then install "Twizy-Cfg" in an extra partition.
With "twizy-Cfg" it´s possible to do it with Twizys before ~2016.
As only Rozhkov and friends know how to tune a post 2016 Twizy, it´s impossible for Fabio to implement this feature to ToM.
And even when the secret becomes uncovered it could be possible that addtional hardware is needed.
Yet we don´t know if it is done only by software or not.

In short words:
You´ll better forget it.

Snorre schrieb:

PriusTwizy schrieb: ... I would love more regenerative breaking. Is it possible that the ToM could ever do something like this?

In theory: maybe
In real life: probably not

You´ll better forget it.

All right, that's clear