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

[d3drturner]

If you look at the generic VESC schematic in Benjamins repo, you will find pins PB11 and PC7 for UART Rx, both are 5V tolerant.

Flipsky is using PB11 also.

View attachment 384916
View attachment 384917
View attachment 384918

thanks for that info; I gather FT means 5V tolerant, which makes sense as my board still seems to function;
I have a question about the Tx to Rx paths:
Schematic-6.png shows
RX is PB10
TX is PB11

on VESC_BLDC\hwconf\flipsky_official\flipsky_v6\hw_flipsky_60_core.h
HW_UART_TX_PIN is B10
HW_UART_RX_PIN is B11

They are crossed, which is correct, right?

I have ekd01 RX going to TX on the flipsky

but you are showing 5 as being TxD going to TX?




on the EKD01 the manual shows Rx and GND on the same side which you also show (but mirrored) but then you have Rx going to Rx?
(manual that came with the EKD01)


but then there is this Varstrom EKD 01 HMI for BAFANG TONGSHENG VARSTROM Conversion Kits which shows GND being on the TxD side, like yours if your pin 3 which is connected to Rx is actually Tx

anyhow, something is interfering with the messaging when the emulator gets connected or I configure the input in VESC tool.
until I do that there is no err30. And the rest of the hardware seems to work; motor spins and detects and spins up on app setting of "no app" with the duty, current or erpm sweeps.
On configuration of the input from the emulator, it shows expected oscillations of 2.5 v to 0.5 volts but the PAS signals do not seem to be getting to Hall1 and 2.

 

[stancecoke]

but you are showing 5 as being TxD going to TX?

This is the controller connector view. Don't worry, if the display works, it is connected correctly.

the PAS signals do not seem to be getting to Hall1 and 2.

Can you show a wiring diagram, what have you connected where? Have you tried to swap PAS1 and PAS2 to test the right rotation direction?

 

[d3drturner]

This is the controller connector view. Don't worry, if the display works, it is connected correctly.


Can you show a wiring diagram, what have you connected where? Have you tried to swap PAS1 and PAS2 to test the right rotation direction?

After confirming with a bunch of prints on the serial console that I have tx and rx wired correctly,
I connected a throttle and confirmed everything is working. (although not sure why the mph range is from 0 to 19 mph, I guess that's the next thing to look at). Watt doesn't register except on surges because it's just spinning under no load.
I have
pa8 torque to adc2
pa9 to to hall1
pa10 to hall2.
I have tried swapping them. Also using a level converter to 3.3, although that may not be necessary.
The whole system is very finicky in that any extra debugging may start generating err30 and the throttle didn't work until after several restarts and reconfigurations.
I really do need to test with the thun sensor in the emulator to isolate whether my hardware sensor works.

 

[stancecoke]

pa9 to to hall1
pa10 to hall2.

What do you think PA9 and PA10 belong to on the connectors? I can't find any usage of them in the Flipsky hardware config...

bldc/hwconf/flipsky_official/flipsky_v6/hw_flipsky_60_core.h at master · vedderb/bldc

The VESC motor control firmware. Contribute to vedderb/bldc development by creating an account on GitHub.

github.com

For a Flipsky V6 MK5 I find this pinout:

The only usable pins for the PAS1 and PAS2 signals are the motor hall inputs with this hardware. But then you have to run the motor sensorless. And I don't know, if the VESC code will throw any kind of error, if there is an unplausible motor hall signal even if the commutation is set to sensorless.

So you can try to use PC6 and PC7 for the PAS signals and set the motor control to sensorless in the VESC tool.

pa8 torque to adc2

ADC2 is on PA6 if you look at the hardware config file.

 

[d3drturner]

What do you think PA9 and PA10 belong to on the connectors? I can't find any usage of them in the Flipsky hardware config...

bldc/hwconf/flipsky_official/flipsky_v6/hw_flipsky_60_core.h at master · vedderb/bldc

The VESC motor control firmware. Contribute to vedderb/bldc development by creating an account on GitHub.

github.com

For a Flipsky V6 MK5 I find this pinout:
View attachment 385172
The only usable pins for the PAS1 and PAS2 signals are the motor hall inputs with this hardware. But then you have to run the motor sensorless. And I don't know, if the VESC code will throw any kind of error, if there is an unplausible motor hall signal even if the commutation is set to sensorless.

So you can try to use PC6 and PC7 for the PAS signals and set the motor control to sensorless in the VESC tool.


ADC2 is on PA6 if you look at the hardware config file.

sorry, was talking emulator to board with
emul pa8 torque to adc2
emul pa9 to to hall1
emul pa10 to hall2.
On flipsky, as you say adc2, hall1 and hall2 are PA6, PC6 and PC7
I am running motor sensorless
fault in VESC tool is always "none"
now it is working because I had to change pas level from 0

 

[ivannnivano2000]

What do you think PA9 and PA10 belong to on the connectors? I can't find any usage of them in the Flipsky hardware config...

bldc/hwconf/flipsky_official/flipsky_v6/hw_flipsky_60_core.h at master · vedderb/bldc

The VESC motor control firmware. Contribute to vedderb/bldc development by creating an account on GitHub.

github.com

For a Flipsky V6 MK5 I find this pinout:
View attachment 385172
The only usable pins for the PAS1 and PAS2 signals are the motor hall inputs with this hardware. But then you have to run the motor sensorless. And I don't know, if the VESC code will throw any kind of error, if there is an unplausible motor hall signal even if the commutation is set to sensorless.

So you can try to use PC6 and PC7 for the PAS signals and set the motor control to sensorless in the VESC tool.


ADC2 is on PA6 if you look at the hardware config file.

Hello! Could you create a firmware update for the CAN display? I happen to have an MK5 controller.

 

[stancecoke]

update for the CAN display

It should be quite easy to port it from the Luna M600 files. But I have no interest in putting any effort in this topic, sorry.

 

[ivannnivano2000]

It should be quite easy to port it from the Luna M600 files. But I have no interest in putting any effort in this topic, sorry.

If you have a little free time, it would be great if you could do this. Unfortunately, I know absolutely nothing about programming or compiling files! I'm counting on you!

 

[stancecoke]

I'm counting on you!

You better count on the big VESC community
I'm not a big friend of the VESC, I prefer to write a custom firmware for OEM controllers!

 

[kro3]

I've tried your firmware with my sw102 but i can't manage to make it work because i get error 30. Has someone had the same issue and can help?

I've also got a flipsky 75_100_V2

 

[stancecoke]

Has someone had the same issue and can help?

@d3drturner had E30 too and solved it, but he never told us how

I got the err30 resolved

 

[prozyc]

I

I've tried your firmware with my sw102 but i can't manage to make it work because i get error 30. Has someone had the same issue and can help?

I've also got a flipsky 75_100_V2

I had the same problem, I tried diffrent vesc controller (75100, 75200, 6.7, mkesc) and diffrent sw102 always was error30

 

[stancecoke]

always was error30

Difficult to debug, as it works for me

@qwerkus reported, that his hardware had an issue.

had to get a logic analyzer to be sure, and I found out what the problem was in case you are still interested: the series resistors on my spintend rx and tx line proved faulty, which made uart erratic. So nothing to do with your code

 

[d3drturner]

@d3drturner had E30 too and solved it, but he never told us how

Hi,
How solved was by logging all the traffic and trying different strategies of replies.

Because I had many changes specific to ekd01 and v6 mk5 and my code is a mashup of Stancecoke's and the latest vesc repo resulting in about a 1000 changes I put fork here:

GitHub - d3drturner/VESC_BLDC at ekd01_v6_mk5

 

[boytitan]

I found a display very close to want you want. Has lap times, bms connectivity, different modes, center mounted but has a hand control's on the left side as well, I believe at least water resistant. Even has different display modes to change info shown. Problem is its fardriver protocol though, and I've got no clue where to source just the display. I learned about it because it comes with VTB ventus one emoto, or their controller for surron bikes, if you want to look more into it. I'm not smart enough to figure out how to get it to play nicely with VESC but I wish someone could. I asked EBMX (vesc surron controller company) and they said they actually considered using that display but passed it up. I really hope they would reconsider as its by far the best display I've seen for any ebike. Probably will try to get ebmx to reconsider supporting it for their controller. View attachment 360603

Old thread but I found the display on aliexpress. https://www.aliexpress.us/item/3256810082955103.html The buttons have been changed a round a bit in it's retail version.

 

[ddm5]

Just recently found this thread while looking into a 72v upgrade for my BBSHD....

I ordered the 75200 Pro V2 thinking it would be better for not overheating etc. Would the firmware provided in here work with the 75200 or would I have to try to rebuild it specifically for the 75200 using the commit history etc?

It hasn't been delivered yet and I'm trying to get everything ready for it's arrival, so any info would be greatly appreciated.

A working display would be great, but tbh i'm not too bothered about that, although I do like the idea of brake sensors and a wheel speed sensor though.

 

[ivannnivano2000]

Hi,
How solved was by logging all the traffic and trying different strategies of replies.

Because I had many changes specific to ekd01 and v6 mk5 and my code is a mashup of Stancecoke's and the latest vesc repo resulting in about a 1000 changes I put fork here:

GitHub - d3drturner/VESC_BLDC at ekd01_v6_mk5

Have you noticed that this controller is acting strangely? I have a Bosch 4 with Hall sensors spaced 120 degrees apart! And when the motor is detected, the observer gain reads 51.7, which is way too high. I'll try disabling the phase filters—maybe they're messing everything up!

 

[ddm5]

Managed to get it all working, but destroyed my nylon gear after 100 miles of high power (2200 miles total) aggressive riding.

The difference with the FOC controller is wild, so much torque, everywhere in the rpm range.

 

[ak136]

Craaazy driving hahahhaa

How did you do this video montage with the power, speed and amps displaying?

 

[ddm5]

Craaazy driving hahahhaa

How did you do this video montage with the power, speed and amps displaying?

I made a website to view VESC logs in a similar way to VESC tool (better IMO), and added a feature to export a transparent overlay video you can edit together with riding footage to get this result.

You can achieve similar results with software like RaceRender etc.