A new Twizy display project

I just added to my Twizy a selfmade touch-display, to show many usefull informations about battery, motor and other data.
I enclose just a preview of a single page.
For now it requires the presence of the PowerBox BT to work, but I planned to realize in the next month also a new prototype that isn't Powerbox dependent.
I think the project could be of interest to other Twizy owner, which are claiming other displays are not available.
In case, I could realize some pieces (only a few, because I'm just an hobbist) in the free time.

Can I show the project in the forum (unfortunatly only in "english" because I have difficulties also to write in such language....)?

that looks very interesting. a version without the power box would be very interesting for me.

do you know the twizyplay? this is/was something similar. Unfortunately, this is no longer available because individual parts are no longer available.

Greetings, Johannes

First, thank your for the welcome msg.

I knew about TwizyPaly just some hours ago, reading this forum.
For what I understood the idea is similar.
In my project, I used a touch screen to change each page at my taste. In other word, by tapping on the icons I can bring the value in first plane (in the right part), and I can choose what value has to be showed in each page, what is the start page at power on... and so on.

I'm looking for an additional information to make a canbus based prototype: how to retrieve istant torque (nm) from OBD. I read the dexter sheet, but I didn't find what PID is involved. May be for language misunderstanding...

Delvecchio schrieb: …
Can I show the project in the forum (unfortunatly only in "english" because I have difficulties also to write in such language....)?

For sure you can show your project to the forum even if you write in english. If you write in an easy way, translation software as www.deepl.com has fewer problems.
I moved your thread to the „project“-branch in the Twizy region of the forum.

Wonderful!
In the next days, I'll take some pictures of the device and I'll write a deeper description of the project.

And so, I show my Twizy display project, called

Twizy o'meter


Let's start with a brief introduction....
I'm an happy owner of a Twizy 80, boosted by the PowerBox BT.
Due to the limitations of the original gauge, I decided to involve myself in the construction of an alternative gauge, able to show in real time some important parameters about motor and battery.
Thanks to Kenneth Nilsen, who shared the Powerbox android app sources, I found the way to retrieve from his Powerbox the relevant data I was interested in, via bluetooth connection.
This is the way my "Twizy o'meter" project born.

The device is based on a 2,8" resistive touch display, driven with an ESP32 board, with the adding of a gyroscope module.
It can display, in realtime, these parameters:
- battery state of health (SOH)
- battery state of charge (SOC)
- remaining battery charge in kwh
- instant battery consumption
- instant motor torque
- motor temperature
- motor rounds (rpm)
- battery cells voltage
- total battery voltage
- battery modules temperature
- total battery temperature
- trip timer
- lateral inclination
- frontal inclination
- acceleration
- internal temperature
Parameters are organized in four main pages, one with three subpages.
With default settings, in the first page are showed main battery values (SOC in first plane, SOH, KWH, AH, Temp in second plane).
In the second page are showed motor main values (RPM in first plane, SOC, Nm, AH, Temp in second plane).
In the third page and its three subpages are showed cells specific values of the battery (voltage and temperatures cells in second plane, and total Temp/Voltage in first plane).
In the fourth page are showed gyroscope/trip values (acceleration in first plane, frontal inclination, lateral inclination, internal temperature, trip timer in second plane).
There is also a fifth page (three dots icon), for settings (values to be showed in each page - except info cells page, start page at power on, display brightness, and gyroscope calibration).
Settings are stored in memory, to be manteined after power off.

Each value has both a numerical and a graphical rappresentation.
The graphical rappresentation is given by an arch bar, with 32 segments, for first plane value, and by an orrizontal bar, with 16 segments, for each value in second plane. The bars are scaled in accordance to values range.
The touch capability let the user to change the value showed in first plane (just tap on the icon of the value to bring in first plane, and it will be swapped) and to gain acces to all gauge functions.

Hardware is boxed in two separate parts, the ESP32 CPU and other modules in a little tiny box I placed on a flat and plane surface (I choosed the steel square tube under the wheel) and the LCD display in a plastic cover, with stands, I placed on the dashboard.

In the near future (may be within the end of next month) I want to realize another prototype, which could work without Powerbox.

Suggestions and comments are wellcome, negative ones too!

That's all, for now.

Another information: as I wrote in the first post, if someone of you is realy interested in this device, I could manufacture some pieces (only a few, because I'm just an hobbist...).

Very nice. If you make some I would be interested. I am sorry I am not able to help you with the technical part, but you seem to be doing quite well.
Regards
Thomas V

villadsen schrieb: Very nice. If you make some I would be interested. I am sorry I am not able to help you with the technical part, but you seem to be doing quite well.
Regards
Thomas V

Me Too

Great work!
Congratulations.
It seems to me that your display project could be a legitimate replacement to the Twizplay project .
How do you want to get the data you need without the Powerbox?
Using a OBDII-Dongle or a OBDII cable instead?
It would be great when your display project could provide the possibility of firmware updates by the users.
The Twizplay is a great piece of hardware, but it has no option for firmware updates by the user.
So its software isn`t uptodate anymore.

Thanks to all for your appreciation of my project.

Snorre schrieb: How do you want to get the data you need without the Powerbox?
Using a OBDII-Dongle or a OBDII cable instead?

Yes, via CANbus. I'm waiting the CANbus module for today, to start the experiments.

Snorre schrieb: It would be great when your display project could provide the possibility of firmware updates by the users.
The Twizplay is a great piece of hardware, but it has no option for firmware updates by the user.
So its software isn`t uptodate anymore.

Sorry, I forgot to mention.
Both LCD and CPU firmware are upgradable, in an easy way. First one by microSD, the second one via usb. LCD has a specific firmware because it's a HID display.
Firmware are in continous development by me. I was working (before thinking to the CANbus prototype ) to add some little icons on the bottom side of the display, like the ones in the notification tray of an android phone, for warning purposes (motor/battery overheating, connection lost, low battery charge, etc...).

Delvecchio schrieb: Sorry, I forgot to mention.
Both LCD and CPU firmware are upgradable, in an easy way. First one by microSD, the second one via usb. LCD has a specific firmware because it's a HID display.
Firmware are in continous development by me. I was working (before thinking to the CANbus prototype ) to add some little icons on the bottom side of the display, like the ones in the notification tray of an android phone, for warning purposes (motor/battery overheating, connection lost, low battery charge, etc...).

It seems to me, that your project will be able to become a great piece of hard- and software.
I'm looking forward to your next reports.

I'll have one, where can I order
Seriously, I really want one. It's exactly what I've been looking for since Twizplay isn't available anymore.

Snorre schrieb: The Twizplay is a great piece of hardware, but it has no option for firmware updates by the user.
So its software isn`t uptodate anymore.

This is not correct, you can update the firmware by yourself with an extra programmer
twizplay.de/firmwareupdate.html
and the Source-Code is available.
twizplay.de/software.html

@delvecchio: your project look very cool and im very fascinated about your ideas.

Akku61 schrieb: This is not correct, you can update the firmware by yourself with an extra programmer
twizplay.de/firmwareupdate.html
and the Source-Code is available.
twizplay.de/software.html

You are right.
For sure, I knew about this fact.
But this is just theory.
Do you know any person, that updated its Twizplay firmware?
Do you know any Twizplay firmware that is newer than 2015?

Then I will tell it like this:
As it is very difficult to update the Twizplay firmware for end users and the developer of the Twizplay was not interested in providing updates, the Twizplay project died.
Nobody else than Uwe had the capabilities to develop new firmware versions.

Firmware updates to the OVMS V2 hardware were difficult to do as well.
Now with OVMS V3 it is much easier.
To me, this is the reason that the firmware development is still in progress.

Just a report about work in progress.
I completed successfully my test with CANbus module.
I'm writing the code to parse the data read via CANbus.
I think the CANbus prototyte of the Twizy o'meter will not remain just an idea!.
So, stay tuned....