Bitcraze Forums

Hi!

We are sorry for our late reply but we do not have Chinese software and hardware support on this forum. Please repost on the forum with an English subject and explanation of your problem.

Best regards,

Kimberly

Hi Gianni, Let me try to answer your questions to the best of my capability. For the floor, don't go for black or dark colors, and do not go for reflective surface. Apparently a children's play rug is the absolute best, but at my previous lab we used artificial grass which works just fine (just bewa...

Hi Esteban, It is a bit trail-and-error, but I haven't found many surfaces it could absolutely not handle. To really do a proper test, you could have the flowdeck with a mocap system, make it fly over different surfaces and see what the readings are compared to the actual (Mocap-based) motion. But t...

Hi Esteban, Really cool project! First thing you need to know about the Flowdeck and the optical flow sensor it uses, it is indeed not as perfect as it would be using a MoCap or the lighthouse positioning system. The PMW optical sensor is optical based and therefore has its limitations, so it would ...

Hi Na, THat sounds like an awesome platform :D. It seems like you were on the right path with changing the power distribution (power_distribution_stock.c), that could be the easiest solution. The next step could be to define your own motor mapping, but to be honest I don't have that much experience ...

Just to give an conclusion to this forum thread (sorry for the late update). I got a replacement of the flowdeck v2.0 and they were all working fine. It was indeed the connector, and the errors I noticed was just because it was not connecting properly

I was able to sort of trace the problem down to the I2C communication. Unfortunately my gdb debugging on the stm doesn't work so I can't really efficiently debug it any further. However, the following line is quite interesting: EEPROM: I2C connection [FAIL]. If I remove the flowdeckv2, or replace it...

Hi all, I just purchased the new flowdeckv2, however my crazyflie2 has trouble reading it out. It recognize the deck but I get the following readout in the console, along with the 3 times fast blink of M1: SYS: ---------------------------- SYS: Crazyflie 2.0 is up and running! SYS: Build 187:47ee696...

I was able to fix my above mentioned problem by adding the following to the config options of the OpenOCD setup :

-c "stm32f4x.cpu configure -rtos auto"

Nice job:) Were you also able to debug the crazyflie2 firmware with the RTOSfree threads with breakpoints and such? I'm having problems with that myself.