• Hello ES! We could use some help to get us past the finish line on building the new knowledgebase for the forum.
    Can you donate? Please see our fundraising page. Thank you!

VESC for Bafang M560

Status
Not open for further replies.
But that's truth. If the truth is not what you want it to be go ahead and be mad.

Does it make someone mad? Probably.

Is it a trademark infringement? No.
 
Last edited:
It looks like the thread survived the last weekend! I recommend you to use this opportunity to download the new archive with the files. I added the new firmware with throttle calibrated for full stroke and removed regenerative braking (the default Luna firmware on this controller activates regenerative braking when throttle is below the middle position because of there is no voltage on the pin PB0 because of the circuit connected to this pin is for torque sensor now. With default Luna firmware it acts like partially engaged regenerative brake). This firmware is throttle only.

[ trademark infringing archive removed ]

1764044413054.png
 
Last edited by a moderator:
Sorry, there are thousands of tutorials out there, how to use github. I'll give some last hints, but I will not explain any little click ;)

As written, first fork benjamins projekt to you own account:
View attachment 380686
Then you will have a copy of the project as a repository in your own account.
click on the green button to download the project as a zip compressed archive, or use an app like Github Desktop on your PC to clone the repo to your local drive.
CubeMX has an implemented Git Plugin also.
View attachment 380688

After importing the project to CubeMX like described, you will be able to edit, compile and flash the firmware directly from CubeMX by a STLink. You have to compile with the M600 hardware configuration, see step 6 of my notes.
Don't forget to commit your changes to your fork at github, so the community can benefit from your work! ;)

View attachment 380690

You mean STM32CubeIDE, not CubeMX?

So I forked the "bldc" folder (or project?) to my github account. Then I downloaded that "bldc" folder zip file to my computer. Then I unpacked that zip folder.

Then I downloaded the STM32CubeIDE v1.8.0 application following this




Then I installed the the STM32CubeIDE v1.8.0 application following this


Then I imported the "bldc-master" folder as project from that "bldc" folder from GitHub through "Import project" function in STM32CubeIDE application.

Then I try to set the hardware as "Luna M600" in the "conf_general.h" file following this instruction but there is no Luna word at all


1764112219218.png


I also attempted to follow the instructions you linked but the STM32CubeIDE shows just empty window after I do "4. file-->new-->Makefile project with existing code"

1764113714190.png
 
Last edited:
Then I try to set the hardware as "Luna M600" in the "conf_general.h" file following this instruction but there is no Luna word at all

There is a Luna folder inside the hwconf folder, the .c and .h files to edit/compile are in there.

cube.png

The instructions to compile are fairly clear on GitHub - vedderb/bldc: The VESC motor control firmware
I was able to compile using the instructions there.
 
Last edited:
But it does no tell anything about STM32CubeIDE program. Can I use STM32CubeIDE program?

If I browse to the "bldc-master-->hwconfig-->luna-->m600" folder and click the hammer icon to build the firmware it gives me an error message "Program "make" not found in PATH"

1764122884162.png
 
Last edited:
It looks like the thread survived the last weekend!

I've been slammed at the shop for too many days in a row and i don't have the energy.
VESC & co have not put expectations of timelines on things.

Please carry on until further notice.
 
OK guys, we better hurry up with firmware since the forum administration gives us such generous opportunity!

But I think the issue is over, mxleming joined the effort and teamed up with us, so now we are officially VESC Labs!
 
But I think the issue is over, mxleming joined the effort and teamed up with us, so now we are officially VESC Labs!

It's pretty strange if this was true because i was told today to take the content down asap.
You are lying and showing that you have malicious intent toward this website and an open source project we rely on.

I will not argue with you more since you are uncooperative and uninterested in solving the legal problem you created for us.

I have censored the thread, unfortunately.
Further problems of this nature may result in a ban.
 
Last edited:
Status
Not open for further replies.
Back
Top