Thanks! One shunt is pretty close to the encoder chip.
I wonder if the magnet will affect the shunt measurement.
Overall, routing is not bad. Decoupling caps are close to the pins and on the same layer, short traces.
Better than original dual motor Odrive 3.6 in my opinion.
It can have some small impact I imagine, it would be worse with hall current sensors.
The 4th half bridge is for dumping energy in a braking resistor, thatās a good board to experiment this for SimpleFOC.
I am still wondering how itās so cheap although it was a STM32F405, DRV8301 and AS5047P. Are they cutting costs on the mosfets ?
[EDIT]
I am biased by the price of the ODESC (63e for the 56V version)
And the Xdrive-S (62.5e 56V)
By the way itās out of stock again lol.
And the original STM not a GD clone. Mosfets are also looks original ON Semi.
I have bought it for $30 with shipping to my country.
Looked up current minimum prices @10k order:
stm32f405rgt6 $7.5
8301 $2.4
AS5047 $4.4
NTMFS5C628NL $0.5x8 $4
So, $19 for only this parts alone.
@multisystem when working with the ODESC v4.1, did you make the USB port work for communication? What did you use to flash the STM32? ST-Link?
@Pablo9026
No, the available USB port is not in use at the moment.
I transfer the firmware with ST-LINK
And I communicate via Serial1 & Commander to drive the āMKS DRIVE MINIā with an M5StickC
Itās the M5StickC that sends commands to āMKS DRIVE MINIā.
@multisystem Did you do a gtihub repository with all your code? If yes please share the link, i would like to see it.
If its not too much to ask, can you upload the simpleFOC library that you created? (So, all the header and .c files that the library uses)
look above and youāll find the link to download the test code in the video on sourceforge ā¦
SimpleFOC_MKS_DRIVE_MINI_V2.zip
I just got one of these today. (FlipSky ODESC v4.2). Is the ST-Link V2 still necessary for this device?
I didnāt realize I needed one since it had a USB port and all the pins, etc. I should have looked into it a bit more first.
Update: I had asked this to the seller on Amazon, and the AI generated answer before I submitted the question said:
āNo, it does not require an ST-Link v2. The ODESC V4.2 uses an STM32F405RGT6 microprocessor that can be programmed via USB without needing an external programmer like the ST-Link v2.ā
Not sure if this is true, or if it comes into play. I was initially using an ESP32-S3 devkit-m with simplefoc-mini, and was going to just replace the foc-mini with this and thought this was just a higher powered driver, and didnāt even realize it was a whole controller on itās own.
Hi
@MostHated, if youāre using Odrive3.6, you donāt need st-link to program it.
However, USB programming is not currently supported by SimpleFOC for this model.
If youāre using SimpleFOC, youāll need to use a st-link for the time being.
SimpleFOC has no requirement for any particular programming protocolā¦ itās just a library, and is compiled into your firmware binary. What tool and protocol you use to program the firmware onto the board is totally outside the scope of the library, and purely a topic of your development environment.
So you can use USB, JTAG, SWD, Serial or any other protocol to program, it just has to be supported by your board.
Big thanks to everyone in this thread for the info. I have finally gotten around to building a new robot and will use 2 of the MakerBase ODRIVE MINI boards. They are cheap and all over aliexpress and seem to be of good quality with encoder and heatsink even. Nice to have a cheap alternative to the 150 AUD boards I have been using (Tinymovr etc - Great boards but I too expensive for me all up with accessories and i prefer SimpleFOC). The info in this thread should help a lot to get started.
what would you use for a communication bus? is the onboard can bus still working?