Hi all
I'm a new happy owner of a crazy fly.
And with my workstation (Win7 x86) it works fine, but it's not good to start fling in my small office.
So I installed the software on my notebook.
Here I have the following Error message when I select the input device:
Traceback (most recent call last):
File "cfclient\ui\main.pyc", line 379, in device_discovery
IndexError: list index out of range
Traceback (most recent call last):
File "cfclient\ui\main.pyc", line 333, in _inputdevice_selected
KeyError: 'MotioninJoy Virtual Game Controller'
I already reinstalled the client, but doesn't help.
Tnx for your help
tdc
[SOLVED]Input Device Error
[SOLVED]Input Device Error
Last edited by tdc on Tue May 21, 2013 7:03 pm, edited 1 time in total.
Re: Input Device Error
the problem comes when you change open the "configure device mapping" and change the Pitch setting (doesn't work, always 0).
and now I also can't start with my workstation too...
"Error while opening/initializing input device"
Traceback (most recent call last):
File "cfclient\utils\input.pyc", line 255, in startInput
ValueError: u 'Generic_OS_X" os not in list
hopefully this helps
and now I also can't start with my workstation too...
"Error while opening/initializing input device"
Traceback (most recent call last):
File "cfclient\utils\input.pyc", line 255, in startInput
ValueError: u 'Generic_OS_X" os not in list
hopefully this helps
Re: Input Device Error
The error referring to a bug in the client, see wiki for the problem,
"Please note!! In the 2013.4.1 and previous versions there's a bug where the loading of a previous configuration will not work correctly. The values are not loaded but the configuration call still be saved. This results in a configuration file that will not work and an error will be shown when trying to use it. In order to fix this manually delete the contents of the user config folder (win: C:\Users\your_user\AppData\Roaming\cfclient, linux: ~/.config/cfclient) and create a new configuration from scratch as described above"
So you need to delete the user config folder.
"Please note!! In the 2013.4.1 and previous versions there's a bug where the loading of a previous configuration will not work correctly. The values are not loaded but the configuration call still be saved. This results in a configuration file that will not work and an error will be shown when trying to use it. In order to fix this manually delete the contents of the user config folder (win: C:\Users\your_user\AppData\Roaming\cfclient, linux: ~/.config/cfclient) and create a new configuration from scratch as described above"
So you need to delete the user config folder.
Re: [SOLVED]Input Device Error
I tried this 50 times and never got it to work. I was not happy.
I had this Crazyflie for 2 weeks now and I still can't spin the motors!
How can this be SOLVED when I still can not get it to work?
So I thought how can anybody ever use this thing.
I tried opening the PS3 mapping mode 2 and it was mapped (lets say) poorly so I could not use it.
When I load PS3 mode 2 the SAVE shows up. So I can SAVE the configuration I have.
That SAVE will be corrupted and cause the Input Device Error described. So don't do that!!!!!!
I could not get the SAVE to enable any other way.
It turns out you have to do a detect on every option and then the SAVE shows up. Where is that written down!!!!
Then the configuration MAP saves properly and works.
Seems to me the detects should all be defaulted so this doesn't happen in the first place.
I had this Crazyflie for 2 weeks now and I still can't spin the motors!
How can this be SOLVED when I still can not get it to work?
So I thought how can anybody ever use this thing.
I tried opening the PS3 mapping mode 2 and it was mapped (lets say) poorly so I could not use it.
When I load PS3 mode 2 the SAVE shows up. So I can SAVE the configuration I have.
That SAVE will be corrupted and cause the Input Device Error described. So don't do that!!!!!!
I could not get the SAVE to enable any other way.
It turns out you have to do a detect on every option and then the SAVE shows up. Where is that written down!!!!
Then the configuration MAP saves properly and works.
Seems to me the detects should all be defaulted so this doesn't happen in the first place.