Bitcraze Forums

I have had a bit bumpy start with the crazyflie. Upon the first attempt an arm broke due to ridicoulus defaults in the thrust sensitivity settings.

Now I fixed it and decided to calibrate my input device. Unfortunately, my version of the client (2013.4.1) writes broken JSON files that can not be read again after restarting the software.
Specifically, the issue seems to be in the id field

Format written by the software :

"id": "Input.AXIS-3"

Format that comes in the original configuration file:

"id":0

Output in the console window

WARNING:cfclient.utils.input:Exception while parsing inputconfig file: %d format

Edit: In the meantime I found out that my issues were caused by extreme drifting that required trimming. See other post. The software bug is still there, but unrelated to my issues.

Hi,

I think that this issue has been reported before but I was never able to reproduce it. Could you have a look at this issue and see if it matches your problem?

What input device are you using? Are you starting with a new configuration or are you "reusing" an old one by loading/editing/replacing it?

/Marcus

For what it's worth, I'm experiencing a similar problem. Using cfclient 2013.4.1 to configure a PS3 controller results in the creation of a config.json file that seems unusable. I haven't investigated it thoroughly, but my sense is that the problem is with config.json ,not input/[profile].json.

Would it make sense that a working config.json would include:

"device_config_mapping": {
"": "Generic_OS_X",
"MotioninJoy Virtual Game Controller": "Generic_OS_X"
},

while a faulty one would include:

"device_config_mapping": {
"MotioninJoy Virtual Game Controller": "Generic_OS_X"
},

Please let me know if I can be helpful in replicating/debugging this.