[Twiz O'Meter / BigToM] Update to firmware 2.1

New firmware update!

I'm back with a "ready to flash" firmware update for ToM & BigToM.
I think the new feature is a very useful addition, because will enable the device to read and delete the Twizy system errors, without struggling yourself for finding a compatible OBD dongle to be used with the well knwon diagnostic apps.

This time I'll start from the end, from thanks giving, because without Snorre, who motivated me from the beginning to look for a way to read the errors, probably this new feature would not have been implemented.
So, special thanks goes to:
=================================
- Snorre who gave me precious help/hints in beta testing, also for forcing the generation of Twizy errors for developping purposes.

What is new in firmware 2.10
=================================
- the device is now able to read and delete the DTC errors of the Twizy!
An error log page has been added to the display. To enter in the error log mode, just long tap on the Alarm icon and, when the Trip log icon will appear, long tap again on it.
The new icon error will appear and you can tap on it for accessing to the error log page.
Remember that no confirmation will be requested for deleting the error list, so errors will be cleared after pressing the trash icon.
Further information (DTC, STATUS, ODO, SOC, speed, B12v) about the error listed is available in the new Diagnostic page of the webUI, where you can also delete the errors.
Conversion to DF error numbering is planned but not yet made available.
- added a new command in the second setup page of the display, intended to manually activate the expansion pin if set as output.
Only one output pin can be controlled, so if you have both pin configured as output, PIN1 will be predominant.
Please pay attention that:
() the on/off slider switch will show the logical state of the pin, not the electric-digital one.
So, if you have set the output as active low, the switch will show the OFF state when the pin is electrically high and viceversa
() the on/off slider switch will follows the rules of the output type you selected: i.e. if, for example, you set the output as "Aux charger" the switch will have effect only during charging
() enabling/disabling manually the output pin will desyncronize it with the Alarm state.
Since the last Alarm state is saved, the alarm won't re-do the same action while the conditions are still satisfied.
So, for example, if you set to ON the pin after the alarm already set it to OFF, the alarm won't switch it OFF again (in the same ToM session), because it thinks the pin has been already set to OFF and that there is no reason to switch it OFF another time.

Bug fixed:
=================================
- in the BigToM speedometer page, the second digit of the speed wasn't displayed over 100 km/h (yes, there is someone among us who wants to break the sound barrier with his Twizy equipped with a BigTom!). Now it is properly displayed.
- some minor bugs and cosmetic graphical issues have been fixed, but I've lost memory of them.

Known bugs:
=================================
- none at the moment , but I'm waiting for your reports!

Updating procedure:
=================================
To install the new fw you have to update both the Blackbox and the 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 1.6 fw.
Please remember that, while the firmware file for the black-box is the same for ToM and BigToM, the display LCD firmware files are different, so choose inside the .zip archive the firmware file designed for your display device.

And please, once again, you have to strictly follow all the mentioned steps!!!

That's all... for now!


A few screen shots of the new features...

Hi Fabio,

...I finally got around to testing it...

The manual control of PIN1 (in conjunction with AUX-Charger) works exactly as it should.
When charging starts, PIN1 is controlled according to the set alarm trigger and can be controlled manually (on the second settings page).
Thank you very much for implementing this – it's about time for a truckload of chocolate to Modena....

Hallo Fabio,

...ich habe es endlich geschafft, es zu testen...

Die manuelle Steuerung von PIN1 (in Verbindung mit AUX-Charger) funktioniert genau wie vorgesehen.
Wenn der Ladevorgang beginnt, wird PIN1 entsprechend dem eingestellten Alarmtrigger gesteuert und kann manuell gesteuert werden (auf der zweiten Einstellungsseite).
Vielen Dank für die Umsetzung – es ist an der Zeit für eine LKW-Ladung Schokolade nach Modena....


LG Tom

Ulli-et-Tom schrieb: it's about time for a truckload of chocolate to Modena....

Today I finally updated my ToM to FW 2.1

• Update of the display works fine with the first try!
• Update of the black box OTA stuck severeal times at 50% or 63%, don't know why.

After restart the Twizy and the ToM (Twizy Ignition zo zero, wait until ToM was down and th *click* from parrot-system came restart Twizy and ToM) two times the OTA update works fine.

The new diagnostiv screen is GREAT - many thanks for this

My Twizy have two errors stored, but as I don't have any problems I am not afraid
With the translation List from ThM (thank you) I knew
DTC 1.37 = DF512, DTC4.21 = DF542
But apparently I'm too stupid to find the complete list explaining what the DF codes mean.
Edit: I‘m really stupid! I found the list in the same thread as listed above
www.twizy-forum.de/ovms/86362-liste-df-codes-dtc?start=0#179755

Searching the numbers in the forum I found

• DF512 = MULTIPLEX-SIGNAL BCB NICHT VORHANDEN
• DF542 = STROMKREIS BREMSPEDALGEBER

Whatever this means

Thanks Andreas for your report.
I'm happy you updated your ToM and shared your experience.

Really interesting the link to the errors description.

Hallo Delvecchio,
seit Sonntag habe ich ein Andrii-BMS im Twizy. Seitdem wird leider die TripHistory mit den Einzelfahrten nicht mehr aktualisiert.
Trip-Data allerdings schon. Ich habe den Trip-Speicher mal geändert von 5 auf 2 und wieder zurück auf 5, aber die History wird weiterhin nicht aktualisiert.
Hast du eine Idee, was das sein könnte?

Ciao Delvecchio,
I've had an Andrii BMS in my Twizy since Sunday. Unfortunately, since then, the trip history with individual trips is no longer being updated.
However, the trip data is. I changed the trip memory from 5 to 2 and back to 5, but the history is still not being updated.
Do you have any idea what the problem could be?

Hi Andreas,
I think the problem is that the kWh value isn't valorized.

Can you verify if the kWh item in the ToM battery page or where you display it, has a value that changes during driving?

Akku61 schrieb: Hast du eine Idee, was das sein könnte?

Das hatte ich vor längerer Zeit auch schon mal.
Du musst ein wenig spielen.
Was letztlich bei mir geholfen hat erinnere ich im Detail nicht mehr.
Während der Fahrt durch die 5 Trip Zähler zappen, eventuell auch mal in die Einstellungen wechseln und wieder zurück zum Hauptdisplay.
Irgend wann sollte der Zähler dann wieder "anspringen".
Im Fahrbetrieb erkennst du bereits nach 100m, wenn der Zähler wieder startet.
Allerdings musst du die gefahrene Strecke im Hauptdisplay anzeigen lassen, damit du die Dezimalstelle angezeigt bekommst.
Lass deinem kindlichen Spieltrieb freien Lauf.
Dann wird das schon wieder.

@Fabio:
I`m quite sure that Andreas will be able to solve the problem by playing around with the different screens.

@Andreas:
Im Austausch mit Fabio hat sich ergeben, dass Einträge in die Trip History nur dann erfolgen, wenn sowohl die Fahrstrecke als auch der Energieverbrauch ungleich Null sind.
Nun scheint es so zu sein, dass das Rozhkov BMS den Energieverbrauch gar nicht oder mit einer falschen CAN ID verschickt.
Schau mal nach, ob im ToM ein Wert ungleich Null während der Fahrt angezeigt wird.

Ich habe mal einen Screenshot von ToM-Webserver vom Bereich "Advanced info & settings" im Stand gemacht.
Auffällig finde ich den Bereich "ADVANCED INFO", da ist alles Null.

I took a screenshot of the ToM web server from the ‘Advanced info & settings’ section.
I find the ‘ADVANCED INFO’ section striking, as everything is set to zero.



Ich setze mich jetzt mal in den Twizy und fahre eine Runde.

-- to be continued --

ok, scheint wohl ein größeres Problem zu sein.

Ich habe mal verschiedene kWh Elemente ins Display geholt. Alle bleiben während der Fahrt auf Null, [kWh] bleibt auf 3,1 stehen.

Die 3,1 kWh stehen auch bei den Battery-Data


Während der Fahrt hatte ich einmal kurz [STOP] und [SERV] aufleuchten, war aber direkt wieder weg und danach den Fehlerspeicher voll .

DTC Nr.	DFCode	Fehler
2.66	192	LBC MULTIPLEXGETRIEBE NICHT VORHANDEN
2.67	193	LBC MULTIPLEXGETRIEBE NICHT VORHANDEN
2.68	313	LBC MULTIPLEXGETRIEBE NICHT VORHANDEN
2.69	314	LBC MULTIPLEXGETRIEBE NICHT VORHANDEN
2.75	318	LBC MULTIPLEXGETRIEBE NICHT VORHANDEN
4.34	330	LBC MULTIPLEXGETRIEBE NICHT VORHANDEN
4.35	331	LBC MULTIPLEXGETRIEBE NICHT VORHANDEN
4.36	332	LBC MULTIPLEXGETRIEBE NICHT VORHANDEN
4.39	430	LBC MULTIPLEXGETRIEBE NICHT VORHANDEN
4.43	150	???

Did the problem started after you changed the BMS?
All was fine before?

Yes, I changed the BMS on saturday 28th September and after this the trip history did not get new data.