This is an old revision of the document!
Table of Contents
Hi folks. You are here maybe because you are very close to the goal… but you experience problem. Do not give up ! Here are some help to debug your configuration.
Sorry for Windows users, debugging is only available for Linux users for now. Install GNU/Linux, it's free as in free beer ;), and you'll be free as in freedom !
Debugging Arduino
You uploaded your first config file in your arduino ? Wants to understand a bit more ? Install “cu” : Debian based :
apt-get install cu
Launch cu to listen to your USB Serial port :
cu -l /dev/ttyACM0 -s 9600
Now if you hit a portion of your board, or if you use a paper clip on your arduino to join two inputs, some symbols should appear on your screen. That works !
Kill cu from another terminal with :
killall cu
Debugging your pydarts config file
If you want to debug pyDarts and your configuration file, particularly the “SectionKeys”, launch your pydDarts from console :
Delete pyDarts config file and then launch :
pydarts --debuglevel=1
Hit parts of your dart board, and if something appear on your screen, you're done !
Debugging pydarts software
With version v0.9 and above :
pydarts --debuglevel=1
or
pydarts --help
Note that there is a file named KNOWN_ISSUES in the pydarts package that summarize all the problems already encountered by any of us.
My issue is still there !
Please post a message on the sourceforge discussion channel. Please give minimal information to help the community debugging :
- your pyDarts version (displayed when you launch the soft, or when when you downloaded it)
- the output of pydarts with option “–debuglevel=1”
- your configuration (Arduino type, Raspberry if relevant, etc)
- a good description of your issue
Enjoy !
