Bitcraze Forums

Have you made cfheadless and xbox360 executable via chmod a+x?

Never mind, you have according to the screenshot. What does happen when you call /root/bin/cfheadless directly yourself?

What output does "echo $PATH" generate? Also, have you tried opening a new terminal / shell after changing bashrc?

The controller doesn't have anything to do with that, I'm sure. Have you also tried "rebooting" the CF itself? Communication issues can be caused by Wifi on the same channel, plus there was also a case of a broken antenna. Try changing the CF to a different channel via the bootloader menu....

Could you post a close-up picture of the PCB, Q1's side up?

I can't say anything about the specifics of using a PS3 controller in your case (I run neither XP nor use a PS3 controller), however, if some error like yours appears in the future, you should 0. Make sure the controller works (whatever steps this entails on your specific platform and with your spec...

Dr. B, to reiterate: Do not look at "C:\Program FIles\Crazyflie client\cfclient\configs\input" but please instead open "%APPDATA%\cfclient", as the latter is the place where your config files are actually located (the ones at the other location are just the "blueprints"...

I'm not sure if that works on XP, but you could try to enter %APPDATA%/cfclient into the addressbar of your Windows Explorer. If this can be resolved it's probably the folder you are looking for (%APPDATA% is just a variable containing the Path to the current user's application settings folder).

... at least not without a ham radio license. Maybe it's time to look into that again...

Just saw the post that it's now enabled, tried it, works, awesome, thanks!

The "Simple Code Example" directly following that section seems to explain it... If I understand that correctly, you'll need to register your "connected" callback with the crazyflie module: from cflib.crazyflie import Crazyflie crazyflie=Crazyflie() # ... crazyflie.connectSetupFi...