Errata problems and range testing

We have found a few workarounds for the JTAG reset problem but finally none of them are needed since we unfortunately┬áhave to make a new revision anyway and thus we can properly fix the probem. After spending hours debugging the PWM for the motors we finally opened up the errata and found a serious problem with our new version. Like we mentioned before we moved the PWM for two of the motors so we could have one dedicated SPI for the expansion header and not shared with the radio. This was done by moving one of the motors to PB5 (alternative function TIM3_CH2) while also switching to new sensors that use I2C. According to the errata it’s not possible to clock I2C1 (where the MPU6050 is connected) and TIM3 while using TIM3_CH2 remapped and as output (to drive the PWM for the motor).

On a happier note we did some range-testing of the radio since we have now changed to 0402 components in the radio filter on the USB radio dongle and the quadcopter. The measurements shows that we get up to ~65 meters before we start loosing packets and up to ~80 meters before we loose communication completely. The test was done outside and using the 250Kbps mode.

4 comments on “Errata problems and range testing

  • Hi,

    Is it possible to scale your system? To change motor drivers to more powerful ones and mount bigger motors?

    • Yes it is but within limits. The sum of all motor currents are limited to about 4-5A. You would also have to design new motor mounts to fit the bigger motors and propellers.

Comments are closed.