Open-BLDC status report

Hi!

It has been a pretty long time since my last post. But do not worry there is happening a lot “behind the scenes”. Well not so much behind them because I commit everything I do to the github repository (http://github.com/esden/open-bldc). If you want to follow the progress you can also subscribe to the commit mailinglist and/or the discussion mailinglist. Feel free to write on the mailinglist if you have any questions or just catch me on #uavp channel on the freenode network. (I think that are enough channels of communication 🙂 )

Ok back to the topic. Last week I was able to turn a bldc motor the first time using the bread board prototype of the power stage, the STM32 Olimex H103 evaluation board and firmware that you can find in the repository. The basic PWM scheme that is used by most controllers is implemented and works pretty well. I am also trying out other PWM schemes that may improve efficiency. You may ask why I am doing it now and not after I made a real hardware prototype of the system. The answer is pretty simple. I have to see if and how it is possible, to make sensorless commutation detection, when using different PWM schemes. I had to realize that the schemes have a big influence on the signals that can be captured.

As soon as I have more results I will make a video showing the current state and how the controller behaves when using different approaches. So stay tuned!

Cheers, and I hope hearing from you too in the comments! 🙂

3 thoughts on “Open-BLDC status report

  1. BenBois

    Well done Esden!
    Hope I’ll be used your open-BLBC with my NG 😉
    See you on IRC

    Ben

    Reply
  2. esden

    Thanks for your comments guys!

    @Ben I really hope that there will be soon something you can use for NG. I am really near to making the first etched prototype. But just not there yet.

    @fake I am working on it. Sadly I do not have a video camera myself so I have to wait for people having one cross my road of life. ^^

    Reply

Leave a Reply to BenBois Cancel reply

Your email address will not be published. Required fields are marked *

Question: *