ODESC v4.2 info

1

Hello, I found this board on Amazon and it seems like a really nice integrated controller+drive+powerstage platform for FOC development.
A couple questions:

1-I can’t find any info on IO routing, like which IOs from the STM32 chip go to the driver and such. Is a schematic available? A demo project for PIO, CubeIDE or whatever?

2-What software comes loaded on this thing from the factory?

3- Anyone have experience with the board? Is it any good? Any issues?

2

That’s an odrive clone, same as all the rest of em.

3

I looked at every ODRIVE and there’s not one remotely resembling this (STM32F405/8301/no position sensor)

image
image954×798 124 KB

The closest thing I found is 1/2 of the dual motor ODRIVE v3.5, which uses the F405+DRV8301. However this doesn’t help me with IO assignments at all.

How frustrating. Am I supposed to just guess at the IO assignments and risk blowing the board up?

4

There would be two “easy” options to get at the pinout:

  1. ask the vendor for the schematics or the pinout diagram, perhaps they can provide them or point to a GitHub

  2. get the source code for the default firmware (assuming it is open) and copy it from that

If you can’t do those then it’s a painstaking reverse engineering by probing the connections from the MCU pins to various headers, chips, etc

5

The manufacturere is flipsky,who are a fairly large company.

But U’m really struggling to understand who they’re marketing this board to,… The factory firmware is supposidly not compatible with the ODRIVE tools, and the don;t say a single word about what (if any) firmware is even loaded on this thing, and they don’t give any information abou the internal IO mapping??? So I guess point-piont testing is the oonly way. What a joke and what complete garbage support from this company.

6

It’s probably that or close enough to that, but I’m assuming. I’m not sure why you think some fly-by-night is a large company, but I assure you they are not. Those guys probably don’t know the answer to your question, all they know how to do is copy someone else’s work. When o-drive intentionally bodged the thieves it became the end user’s responsibility to make it work, so you’re gonna need to be good at figuring stuff out if you stick with that kind of hardware.

7

Yep, that looks very promising thanks!

Regarding Flipsky, I don’t know, I guess I’ve just heard the name quite a bit

8

Hi! I made a guide for very similar board, I think the only difference is onboard encoder. https://youtu.be/yRx7dsJmNvU

1 Like
9

I just watched this couple of times. You dont know how much I appreciate it :slight_smile:
Could you be so kind and answer me some questions? I would like to use this to build a gift for my brother!

  1. It seems after initial configuration, that firmware on the board can be fully “configured” through the CAN. E.g. your arduino library basically does that over TWAI. Am I correct?
  2. The firmware attached to your git is basic one that you also used for your youtube video?
  3. Do you see any limitation with power supply and tuning? I used my own tuning and SW in the past and burned 3 350W PSUs already

Thank you SO much! If its a hassle to answer, I get it :slight_smile:

10

Thanks for watching! Of course I can answer:

  1. Yes, you can send parameters and change PI tuning for example to make it more rigid or more bouncy. I think you can change all params via CAN
  2. Firmware I attached is dumped from controller just in case you brick it with update, when you get your board it will have same firmware.
  3. Yes, you need to enable breaking resistor and use PSU with protection, my PSU throw an error every time motor brake too hard
1 Like