You need to be a member of diydrones to add comments!

Join diydrones


  • Hi!
    I'm using free standard c32 compiler with free mplabx ide and a pickit3 prog/debug
    I will show it on my next post about OSD feature.
  • Are you guys compiling - free - standard or pro C32 compiler for firmware?

  • Moderator

    I remember years ago, when Sun said computers would be just a bump in the network cable.  I think you are coming close to that!

  • A very nice looking board.

    I've used I2C often over many years and read of problems more recently. It's not the fastest but when working is reliable. I think many problems are due to poor interface code. Some were using libraries that I suspect are buggy or just don't play nice with other functions. These problems can be very difficult to correct.


  • All,

    Thank you very much for your comments, that's very nice.

    @Nick: Thank you very much for your ideas

    1: Absolutely right for this shitty connector... My assembler was wrong when he assembled it. With the right way, it should be more beautiful and useful. The black plastic part should not be attached to the PCB...

    2: You're right again for the GPS connector that is not soldered yet, especially because of my answer N°1... (as you can see, it's the first prototype).

    3: don't really see the troubles between GPS and MAX but i didn't design the PCB with the GPS soldered on it. So the objective is to be able to have a jumper to place the GPS far from the PCB (also for having it on the top of an airplane for example)

    4: I know the "big debate" about the I2C and SPI but all parts are designed for a 400KHz I2c speed and the ODR of the sensors are about 100-500 Hz. To be honest, i don't see the need for having a very busy SPI bus for such a refresh rate. And for the usual calculation (quaternion, kalman, PID, etc...) i tested i2c with other boards and it's largely enough, especially for a final output of 40-50 Hz (servos).

    5. Of course i'm sorry for the mistakes in my written english...

    Thank you again, feel free to continue the debate!! :))

    Best Regards,


  • [Comment deleted for violation of site TOS]

  • Moderator

    @R, here's a link that might be informative:

  • Developer

    I2C is horribly slow.

  • VGR guys,

    If you really want to squeeze the max of your AP, do have a look at MAX21000 instead of L3GD20!

    Good luck!


  • Hi Robert,

    The guys are using a powerful engine along with a narrow bandwidth and unreliable I2C for the IMU....why?

    I know it is easier to hang all devices on an I2C and route just 2 wires, but......

    By the way, what about the low MRF ( mechanical resonant frequency ) of the ST accelero and gyro?

    Even their latest L3GD20 has an MRF < 10kHz....still too low for the purpose.

This reply was deleted.