VESC - Flipsky 75100 V2 with Bafang Display and T15/T17 BB-Torque Sensor

Sandroforms said:
Regarding the VESC application for smartphones, despite using a different firmware, is it still compatible or does it need some modification?
Click to expand...
I'm not familiar with the VESC in detail. But I guess the smartphone app would need a Bluetooth module attached to the UART connector. I'm not sure, if you can set the UART connection to the Bluetooth module with the USB connector and the PC tool. By default, the UART is set to the Bafang protocol.
Perhaps you could ask in the VESC tuning thread.
 
stancecoke said:
Não estou familiarizado com o VESC em detalhes. Mas acho que o aplicativo para smartphone precisaria de um módulo Bluetooth conectado ao conector UART. Não tenho certeza se você pode definir a conexão UART para o módulo Bluetooth com o conector USB e a ferramenta de PC. Por padrão, o UART é definido para o protocolo Bafang.
Talvez você possa perguntar no tópico de ajuste do VESC.
Click to expand...
I have a lisp script so that a simple 3-wire PAS sensor works perfectly with the vesc, I will post the download link here on the forum, this script uses the ppm input to make the connection with the sensor
 
posted! now it is possible to use a 3-wire cadence sensor using the ppm input! I left the link to download the lisp file in the description of the video tutorial
 
stancecoke said:
The Flipsky 75100 is available at a very reasonable price and in a pedelec-compatible housing. However, the VESC is hardly suitable for e-bikes due to the lack of display and torque sensor support. This has challenged my tinkering instinct ;)
Luna Cycle has already implemented the Bafang protocol for its BBSHD controller, so I “only” had to port it to the Flipsky hardware.
For the torque sensor I put the PAS signal on the servo input and the torque signal on ADC2.
The VESC tool still works for setting up the motor, but the app setting must not be done with the VESC tool at the moment, as it does not (yet) know the new functions.
Currently it only runs on the test bench, the torque sensor signals are emulated by a blackpill board.
Next I have to install the controller in my tinker bike and do a real test ride :cool:
Commits · stancecoke/VESC_BLDC

Flipsky%20wiring.PNG

A little teaser on Youtube:

regards
stancecoke
Click to expand...
I downloaded the .hex file, I did exactly as the tutorial, but the fw upload status does not change, it stays at 0%, what could it be? I right-clicked on download, the file downloaded with the .hex extension, am I correct?
 
stancecoke said:
Yes, for me it works this way. Which version of the VESC tool are you using?
Click to expand...
I managed to update the firmware, but a message appeared saying that my vesc will work in a limited way, and I realized that it is not detecting the engine and input, what can I do?
 
Could you tell me which version of the firmware you used to make sure that there were no problems after updating the custom firmware? I believe that the VESC you used is the same one that I have 75100, could you tell me which firmware model, I tried to change using version 75100v2 .bin, I couldn't, after that I changed to 75300.bin and I could, however, it is not possible to change the parameters in the VESC tool (v6.02) do you have any tips? Thanks for helping!
 
Sandroforms said:
Could you tell me which version of the firmware you used
Click to expand...
I started the firmware from the commit 05aeda0 at github from Sep 1, 2024.
I used the corresponding VESC-Tool BETA, downloaded on Sep 8, 2024

I compiled from the hw_75_100_V2.h hardware configuration.

regards
stancecoke

1736269159746.png
 
I believe the problem is the bootloader, because I have the latest version of vesc tool 6.05, and I'm using the original firmware of my vesc 75100 v2, and the .hex file is not read, however, version 75300 has a bootloader that accepts uploading custom firmware in .hex. I'll look for a custom bootloader for firmware 75100v2.
 
Sandroforms said:
however, version 75300 has a bootloader that accepts uploading custom firmware in .hex
Click to expand...
I can provide the .bin file also, if that helps. It is generated anyway during compiling.
But I had no problem with flashing the .hex file with the 6.06 BETA VESC tool.

regards
stancecoke
 
I would appreciate it if you could generate the file in .bin, they removed version 6.06 for testing, leaving only version 6.05v2 on the vesc project website unfortunately....
 
Sandroforms said:
thanks for being patient and helping me!!
Click to expand...
Now I managed to upgrade the firmware, but even using the test version of vesctool 6.05v2, it only works in limited mode and so you can't configure the accelerator and motor, this also happens with the vesc tool 6.05 version... what could you advise?
 
Sandroforms said:
what could you advise?
Click to expand...
I just downloaded the vesc_tool_BETA_ALL.zip from VESC Project again.
For me it's still V6.06 Testversion 2, but from a newer git commit. I guess, it will still work with my firmware.
So please try to log in to your account at VESC Project, go to the "Purchased Files" area and look for the Beta version in the "Files" tab.

regards
stancecoke

1736431702087.png
 
I installed vesc tool 6.06 but it does not save the engine information, a message appeared saying that new interactions were made in the test version and it is necessary to update the firmware.
 
Sandroforms said:
a message appeared saying that new interactions were made in the test version and it is necessary to update the firmware.
Click to expand...
That's bad. So I have to merge my fork to the next official release, when it's published. Meanwhile we need a workaround.

regards
stancecoke
 
I have a question, when you did the test in the vesc tool did you notice that the speed was well below the real one? Is this normal or should I just consider the speed on the display? I ask this because I noticed that the speed was now only recognized by an external sensor, but in the vesc tool, when real time is activated, it is very different. Could it be that the programming is in mph? Would it be possible to change this?
 
I'm using the same 2-pin sensor you used, and my vesc tool is in kmh, and the speed shown on the vesc tool is very unrealistic, very low.
 
Sandroforms said:
my vesc tool is in kmh, and the speed shown on the vesc tool is very unrealistic, very low.
Click to expand...
I recognised the difference in the speed displayed in the VESC tool and in Bafang display, but it doesn't bother me, as on the bike I have only the Bafang Display. We would have to analyse the code to see, why the VESC tool shows a wrong speed, but I have no motivation to do that, as I need the VESC tool only for setting up the motor parameters. 🤷‍♂️
 
I found out, I did tests, even with ST Link connected there is no connection, that is, the main ST32 processor of the VESC is burned, I believe that what may have been the connection between the display power supply directly with the 48V output of my battery, somehow it burned out, that could be it. There is no 3.3 volt signal at any point on the board, and the 3.3V output of the processor is also shorted, unfortunately it did not work here, now, I will go back to my old project with a common controller. Thanks for your attention!
 
Sandroforms said:
I believe that what may have been the connection between the display power supply directly with the 48V output of my battery
Click to expand...
Hm, maybe not a good idea to use that very cheap DZ40 display. I had no problems with the SW102 so far! :unsure:
 
You must log in or register to reply here.
Back
Top