rik/jlibwiiscan
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Convert documentation to markdown

Browse Source
This commit is contained in:
Rik Veenboer
2014-10-13 22:23:04 +01:00
parent 4e06cbc46c
commit dc9a325151
13 changed files with 354 additions and 1472 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
README.md Normal file
View File

@@ -0,0 +1,31 @@
Fork of <http://wyxs.net/web/wiiscan/>.
----------
Copyright © 2008 MergeIt, Aps.
License GPLv3+: GNU GPL version 3 or later <<http://gnu.org/licenses/gpl.html>>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Permission to use, copy, modify, and distribute this software
and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation.
**WIISCAN**:
a connection utility for wii console remotes
**VERSION**:
0.9
**INSTALL**:
just run bin/Release/wiiscan or bin/Release/wiiscantray
**PREREQUISITES**:
.NET framework 3.5
Windows XP or above.
Microsoft Bluetooth stack.
**NOTE**:
1. Modify the Release/wiiscan.ini file according to the USB hub device remarks in the documentation before runnnig wiiscan!
2. If you are running a non-Microsoft Bluetooth stack (like Widcomm ), you must follow the procedure found in the document doc/CHANGEINGBTSTACK.rtf

30
README_FIRST.rtf
View File

@@ -1,30 +0,0 @@
Copyright © 2008 MergeIt, Aps.
License GPLv3+: GNU GPL version 3 or later <http:\/\/gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Permission to use, copy, modify, and distribute this software
and its documentation for any purpose and without fee is hereby granted, provided that
the above copyright notice appear in all copies and that both that copyright notice
and this permission notice appear in supporting documentation.
WIISCAN:
a connection utility for wii console remotes
VERSION:
0.9
INSTALL:
just run bin/Release/wiiscantray
PREREQUISITES:
.NET framework 3.5
Windows XP or above.
Microsoft Bluetooth stack.
NOTE:
1: Modify the Release/wiiscan.ini file according to the USB hub device remarks in
the documentation before runnnig wiiscan!
2: If you are running a non-Microsoft Bluetooth stack (like Widcomm ),
you must follow the procedure found in the document doc/CHANGEINGBTSTACK.rtf

57
doc/CHANGEINGBTSTACK.md Normal file
View File

@@ -0,0 +1,57 @@
**CHANGING** the Widcomm BT stack to Microsoft BT stack
[From <http://forum.eeeuser.com/viewtopic.php?id=38533>]
After making my post in the 1000H post I thought it probably best If it here as I don't see why it wouldn't work on the 901 models either...
Basically it's all to just to change from using the Widcomm stack for using bluetooth connections to the built in Windows stack, it's fairly simple to do and should be a performance boost as Widcomm runs fairly sloppy.
basically if you follow a guide similar to this: <http://www.x-setup.net/forum/showthread.php?p=4762>
Open file 'C:\Windows\inf\bth.inf' in notepad, (The inf folder is hidden by default so using Explorer go to Folder Options and change it to show all hidden folders)
(A good time to back up the bth.inf file if your worried about editing stuff wrongly but it's only like 3 lines worth)
Now you should have the section like this...
[Manufacturer]
%Microsoft%=Microsoft
ALPS=ALPS, NT.5.1
Belkin=Belkin, NT.5.1
Brain Boxes=BrainBoxes, NT.5.1
Broadcom=Broadcom, NT.5.1
Cambridge Silicon Radio Ltd.=Cambridge, NT.5.1
Dell=Dell, NT.5.1
FIC=FIC, NT.5.1
GVC=GVC, NT.5.1
HP=HP, NT.5.1
IBM=IBM, NT.5.1
Microsoft=Microsoft, NT.5.1
Motion Computing=MotionComputing, NT.5.1
Silicon Wave=SiliconWave, NT.5.1
Sony=Sony, NT.5.1
TDK=TDK, NT.5.1
TOSHIBA=Toshiba, NT.5.1
Wistron NeWeb=Wistron, NT.5.1
Zeevo=Zeevo, NT.5.1
Now add a line to the that section a line such as (without quotes of course): 'Azwave=Azwave, NT.5.1 '
There should then be sections below this one that starts with:
;------------- Device section - Start -----------------------
Then insert a section that looks like this (Please note that you can check that the Vid and Pid are the same as your card by using device manage and looking at the properties of the device, and then the details tab, if not edit the following values, keeping the same format):
[Azwave.NT.5.1]
BT253= BthUsb, USB\Vid_0b05&Pid_b700
Then save and close the notepad.
Then just either do a 'I'll choose from a list of drivers install' or if you haven't installed the drivers yet do a disable and enable of the bluetooth and it should install it automatically. The driver won't be signed so continue with it anyways.
I've now tested it with receiving a file from a phone and as such it seems to work absolutely fine.
Updated due to my own incompetence, don't worry this fix still works great.
Last edited by Sly (2008-08-30 8:51:54 pm)

57
doc/CHANGEINGBTSTACK.rtf
View File

@@ -1,57 +0,0 @@
CHANGING the Widcomm BT stack to Microsoft BT stack
[From http://forum.eeeuser.com/viewtopic.php?id=38533]
After making my post in the 1000H post I thought it probably best If it here as I don't see why it wouldn't work on the 901 models either...
Basically it's all to just to change from using the Widcomm stack for using bluetooth connections to the built in Windows stack, it's fairly simple to do and should be a performance boost as Widcomm runs fairly sloppy.
basically if you follow a guide similar to this>>> http://www.x-setup.net/forum/showthread.php?p=4762
Open file 'C:\Windows\inf\bth.inf' in notepad, (The inf folder is hidden by default so using Explorer go to Folder Options and change it to show all hidden folders)
(A good time to back up the bth.inf file if your worried about editing stuff wrongly but it's only like 3 lines worth)
Now you should have the section like this...
[Manufacturer]
%Microsoft%=Microsoft
ALPS=ALPS, NT.5.1
Belkin=Belkin, NT.5.1
Brain Boxes=BrainBoxes, NT.5.1
Broadcom=Broadcom, NT.5.1
Cambridge Silicon Radio Ltd.=Cambridge, NT.5.1
Dell=Dell, NT.5.1
FIC=FIC, NT.5.1
GVC=GVC, NT.5.1
HP=HP, NT.5.1
IBM=IBM, NT.5.1
Microsoft=Microsoft, NT.5.1
Motion Computing=MotionComputing, NT.5.1
Silicon Wave=SiliconWave, NT.5.1
Sony=Sony, NT.5.1
TDK=TDK, NT.5.1
TOSHIBA=Toshiba, NT.5.1
Wistron NeWeb=Wistron, NT.5.1
Zeevo=Zeevo, NT.5.1
Now add a line to the that section a line such as (without quotes of course): 'Azwave=Azwave, NT.5.1 '
There should then be sections below this one that starts with:
;------------- Device section - Start -----------------------
Then insert a section that looks like this (Please note that you can check that the Vid and Pid are the same as your card by using device manage and looking at the properties of the device, and then the details tab, if not edit the following values, keeping the same format):
[Azwave.NT.5.1]
BT253= BthUsb, USB\Vid_0b05&Pid_b700
Then save and close the notepad.
Then just either do a 'I'll choose from a list of drivers install' or if you haven't installed the drivers yet do a disable and enable of the bluetooth and it should install it automatically. The driver won't be signed so continue with it anyways.
I've now tested it with receiving a file from a phone and as such it seems to work absolutely fine.
Updated due to my own incompetence, don't worry this fix still works great.
Last edited by Sly (2008-08-30 8:51:54 pm)

48
doc/CHANGELOG.md Normal file
View File

@@ -0,0 +1,48 @@
Copyright © 2008 MergeIt, Aps.
License GPLv3+: GNU GPL version 3 or later <<http://gnu.org/licenses/gpl.html>>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Permission to use, copy, modify, and distribute this software
and its documentation for any purpose and without fee is hereby granted, provided that
the above copyright notice appear in all copies and that both that copyright notice
and this permission notice appear in supporting documentation.
**WIISCAN**:
a connection utility for wii console remotes
**VERSION**:
0.9
**Added**:
* wildcard matches on wiimote addr.
* changed wiiscantray to hook into wiimotelib poll (major change).
* allowed for seamless connection with wiiscantray.
* (numerious minor changes, fixes)
**VERSION**:
0.8
**Added**:
* Minor code refactoring.
* Configfile entries for all options. Change the order of parsing options, first look in configfile, then read the command line (that eventually overrules the configfile options).
* Modified wiiscan.ini file to be more versatile.
* Added logging class, rewritten logging method.
* Changed calls to System, to CreatProc, that do not display a console window (for win trayicon mode).
* Changed project settings, links with MT lib instead of MT DLL; fixes strange MS bug when not being able to find msvcp90.dll and friends.
* Added hardware support for USBmicro IO board; power-control now possible with this board instead of the USB controller.
* Added USBio up/down functionality.
* Added usbmsleep, postsleep after USBmicro up/down cycle.
**Fixed**:
* Fix of defect "1: restart pop-up": the 'Change of system settings ... Do you want to reboot now?' popup, happens only when the program runs for longer than 19 seconds. Keeping the connection time within 19 sec seems to cure the problem, Adding a sleep at the end of the program, say Sleep(20000) will eventually bring up the dialog again. The dialog can anyway safely be ignored!
* Fix of defect "2: discoverable mode fast shutdown": Initialization of wiilib has been rewritten, making it recall the HID initialization routine. Code for testing the wiimote connection has also been introduced.
* Fixed defect "15: BluetoothFindFirstDevice() stalls".
**VERSION**:
0.7
First published version.

59
doc/CHANGELOG.rtf
View File

@@ -1,59 +0,0 @@
Copyright © 2008 MergeIt, Aps.
License GPLv3+: GNU GPL version 3 or later <http:\/\/gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Permission to use, copy, modify, and distribute this software
and its documentation for any purpose and without fee is hereby granted, provided that
the above copyright notice appear in all copies and that both that copyright notice
and this permission notice appear in supporting documentation.
WIISCAN:
a connection utility for wii console remotes
VERSION:
0.9
Added:
* wildcard matches on wiimote adr.
* changed wiiscantray to hook into wiimotelib poll (major change).
* allowed for seamless connection with wiiscantray.
* (numerious minor changes, fixes)
VERSION:
0.8
Added:
* Minor code refactoring.
* Configfile entries for all options. Change the order of parsing options, first look in configfile, then read the command line (that eventually overrules the configfile options).
* Modified wiiscan.ini file to be more versatile.
* Added logging class, rewritten logging method.
* Changed calls to System, to CreatProc, that do not display a console window (for win trayicon mode).
* Changed project settings, links with MT lib instead of MT DLL; fixes strange MS bug when not being able to find msvcp90.dll and friends.
* Added hardware support for USBmicro IO board; power-control now possible with this board instead of the USB controller.
* Added USBio up/down functionality.
* Added usbmsleep, postsleep after USBmicro up/down cycle.
Fixed:
* Fix of defect "1: restart pop-up": the 'Change of system settings ... Do you want to reboot now?' popup, happens only when the program runs for longer than 19 seconds. Keeping the connection time within 19 sec seems to cure the problem, Adding a sleep at the end of the program, say Sleep(20000) will eventually bring up the dialog again. The dialog can anyway safely be ignored!
* Fix of defect "2: discoverable mode fast shutdown": Initialization of wiilib has been rewritten, making it recall the HID initialization routine. Code for testing the wiimote connection has also been introduced.
* Fixed defect "15: BluetoothFindFirstDevice() stalls".
VERSION:
0.7
First published version.

136
doc/INSTALL.md Normal file
View File

@@ -0,0 +1,136 @@
# INSTALLATION #
**Version**: 0.9
Procedure for wiiscan or wiiscantray:
## Prerequisites ##
1. unzip the wiiscan zip file(s).
2. if you are not running a Microsoft Bluetooth stack, then change it from Widcomm, Bluesoleil or whatever you are using. See the file CHANGINGBTSTACK.rtf.
## Running ##
1. GUI version, run "wiiscantray.exe" in bin/Release or bin/Debug directory.
2. CLI version, run "wiiscan.exe" in bin/Release or bin/Debug directory from a command prompt.
## User optimizations ##
- Tune scan speed by giving wiiscan your specific wiimote address. Run "wiiscan -s nintendo" from a prompt to find the address, or use the windows system setting.
- Replace the "allowed_wiimote_adr=00:00:00:00:00:00" by our specific addres in the wiiscan.ini file, and lower the value of "option_timeout" to 1000 or 2000.
- Avoid annoying baloon tips by running: "popup_disable.reg" found in src/wiiscan-0.9.zip, under Tools.
- Avoid annoying crash reports from the Wiimote library by running: "no_error_report.reg" found the same place as above.
**ENJOY**
Mar 26 2009
Carsten Frigaard,
MergeIt ApS, Kongsvang Allé 37, DK-8000 Århus C, www.mergit.dk
# INSTALLATION
**Version**: 0.8
Procedure for wiiscan or wiiscantray:
## Prerequisites ##
1. unzip the wiiscan zip file (wiiscan-0.8.zip, wiiscantray-0.8.zip or wiiscan-0.8-release-1.0.zip)
2. if you are not running a Microsoft Bluetooth stack, then change it from Widcomm, Bluesoleil or whatever you are using. See the file CHANGINGBTSTACK.rtf.
## Testing the exe files ##
- run the wiiscan.exe --- if it terminates with an error indicating that it can not run the executable, you will need to recompile the .exe from the source code, or install .NET framework 3.5 SP1.
**Note**: even though the executable is a primitive console app it apparently needs a .NET framework! You can install .NET framework 3.5 SP1 or just install the Visual Studio C++ Express compiler (that also installs the needed framework).
## Rebuilding the source code ##
- Install VS express form http://www.microsoft.com/express/vc/ [version: Microsoft Visual C++ 2008 Express Edition with SP1 ENU]
- Open the wiiscan.sln and rebuild the executable.
- Re-try to launch wiiscan.exe (as in 2).
Finding and testing the +5V power in the USB controllers [do this, only if USB Hub power control is needed, that is the case of no USBmicro device hardware]
- download free, but non-redistributable, device console program, devcon.exe, from http:support.microsoft.com/kb/311272
- unzip devcon.zip and copy devcon.exe (i386/devcon.exe) to path (say copy it into c:\WINDOWS\ directory)
- Some USB controllers cannot do a power-down; it seems that ICH7 controllers are not able to cut the power while ICH9 controllers can.
On an ASUS eee PC the controller version reads
"Intel(R) 82801G (ICH7 Family) USB Universal Host Controller"
"Intel(R) 82801G (ICH7 Family) USB2 Enhanced Host Controller"
On a Lenovo R599 the controller version reads
"Intel(R) ICH9 Family USB Universal Host Controller"
"Intel(R) ICH9 Family USB2 Enhanced Host Controller"
where only the later (ICH9) is usable for the wiimote auto-power procedure here. Check our system specification, before proceeding.
- Find the id of the USB hubs on the system, open "Control panel | System | Hardware | Device management" and look for USB-controllers.
- Open the USB-controller tap and write down the address of all the USB Universal host controllers, and USB2 Enhanced host controllers.
The id of the controllers are found by right-clicking on the device, selecting "Properties | Details"
On my eee PC I have four Intel controllers
PCI\VEN_8086&DEV_27C8&SUBSYS_830F1043&REV_02\3&11583659&0&E8
PCI\VEN_8086&DEV_27C9&SUBSYS_830F1043&REV_02\3&11583659&0&E9
PCI\VEN_8086&DEV_27CA&SUBSYS_830F1043&REV_02\3&11583659&0&EA
PCI\VEN_8086&DEV_27CB&SUBSYS_830F1043&REV_02\3&11583659&0&EB
and one USB2 controller
PCI\VEN_8086&DEV_27CC&SUBSYS_830F1043&REV_02\3&11583659&0&EF
Try to manually disable all the controllers by
> devcon status "@PCI\VEN_8086&DEV_27C8&SUBSYS_830F1043&REV_02\3&11583659&0&E8"
or, if possible, you could use a pattern match to select all the devices...for my particular system the following expression works
> devcon status "@PCI\VEN_8086&DEV_27C*&SUBSYS_830F1043&REV_02\3&11583659&0&E*"
Then disable all devices
> devcon disable "@PCI\VEN_8086&DEV_27C*&SUBSYS_830F1043&REV_02\3&11583659&0&E*"
and check the result in the windows device manager (or manually disable all the USB controllers here)
Finally, pick an active controller and put its address into the wiiscan.ini file, for my particular setup the file then reads
% Configfile_begin
% config file for wiiscan
all_usb_hubs="@PCI\VEN_8086&DEV_27C*&SUBSYS_830F1043&REV_02\3&11583659&0&E*"
active_usb_hub="@PCI\VEN_8086&DEV_27C8&SUBSYS_830F1043&REV_02\3&11583659&0&E8"
allowed_wiimote_adr=00:00:00:00:00:00
whiteboard_software="d:/WiimoteWhiteboard/WiimoteWhiteboard_v0.3.exe"
% Configfile_end
It is not that important to choose a particular USB controller as the active one, important is that power is only cut to the USB when ALL controllers are disabled, and on when just a single controller is enabled.
**Note**: the use of other USB devices may be troublesome, when powering the wiimote over USB as here. It is not recommended to use USB devices together with this procedure!!
Add the addresses of your wiimotes to the .ini file
- To enable faster an more robust connection, find and add all wiimote addresses to the .ini file in the form of a single address or a list, say
allowed_wiimote_adr=00:19:FD:CC:60:61 00:19:1D:D6:65:E5
- Test an automated, unattended connection
- Re-run the wiiscan.exe in a console. If it still fails try to give it a -v option for verbose output, tune the timing parameters (-b,-t,-u,-w), or mail all the results to me: carsten AT mergit.dk
Run the wiiscantray GUI version
- Run wiiscantray.exe,
- click on "Rescan for wiimotes" to connect.
- click "Start whiteboard..." to start the whiteboard executable. Use the option "option_startwhiteboard=1" in the .ini file to start the software after a successful connection.
- click "Display log..." to show the log output, enable and control the log via the options "option_logfile=wiiscan_log.txt" and "option_debug=1
- use "Reset log..." to clear the log.
**ENJOY**
Feb 12 2009
Carsten Frigaard,
MergeIt ApS, Kongsvang Allé 37, DK-8000 Århus C.

153
doc/INSTALL.rtf
View File

@@ -1,153 +0,0 @@
INSTALLATION
Version: 0.9
Procedure for wiiscan or wiiscantray:
Prerequisites
1a: unzip the wiiscan zip file(s).
1b: if you are not running a Microsoft Bluetooth stack, then change it from Widcomm, Bluesoleil or whatever you are using. See the file CHANGINGBTSTACK.rtf.
Running
1a: GUI version, run "wiiscantray.exe" in bin/Release or bin/Debug directory.
1b: CLI version, run "wiiscan.exe" in bin/Release or bin/Debug directory from a command prompt.
User optimizations:
Tune scan speed by giving wiiscan your specific wiimote address. Run "wiiscan -s nintendo" from a prompt to find the address, or use the windows system setting.
Replace the "allowed_wiimote_adr=00:00:00:00:00:00" by our specific addres in the wiiscan.ini file, and lower the value of "option_timeout" to 1000 or 2000.
Avoid annoying baloon tips by running: "popup_disable.reg" found in src/wiiscan-0.9.zip, under Tools.
Avoid annoying crash reports from the Wiimote library by running: "no_error_report.reg" found the same place as above.
ENJOY
Mar 26 2009
Carsten Frigaard,
MergeIt ApS, Kongsvang Allé 37, DK-8000 Århus C, www.mergit.dk
INSTALLATION
Version: 0.8
Procedure for wiiscan or wiiscantray:
Prerequisites
1a: unzip the wiiscan zip file (wiiscan-0.8.zip, wiiscantray-0.8.zip or wiiscan-0.8-release-1.0.zip)
1b: if you are not running a Microsoft Bluetooth stack, then change it from Widcomm, Bluesoleil or whatever you are using. See the file CHANGINGBTSTACK.rtf.
Testing the exe files
2: run the wiiscan.exe --- if it terminates with an error indicating that it can not run the executable, you will need to recompile the .exe from the source code, or install .NET framework 3.5 SP1. Otherwise goto 5.
Note: even though the executable is a primitive console app it apparently needs a .NET framework! You can install .NET framework 3.5 SP1 or just install the Visual Studio C++ Express compiler (that also installs the needed framework).
Rebuilding the source code
3a: Install VS express form http://www.microsoft.com/express/vc/ [version: Microsoft Visual C++ 2008 Express Edition with SP1 - ENU]
3b: Open the wiiscan.sln and rebuild the executable.
3c: Re-try to launch wiiscan.exe (as in 2).
Finding and testing the +5V power in the USB controllers [do this, only if USB Hub power control is needed, that is the case of no USBmicro device hardware]
4a: download free, but non-redistributable, device console program, devcon.exe, from http:support.microsoft.com/kb/311272
4b: unzip devcon.zip and copy devcon.exe (i386/devcon.exe) to path (say copy it into c:\WINDOWS\ directory)
4c: Some USB controllers cannot do a power-down; it seems that ICH7 controllers are not able to cut the power while ICH9 controllers can.
On an ASUS eee PC the controller version reads
"Intel(R) 82801G (ICH7 Family) USB Universal Host Controller"
"Intel(R) 82801G (ICH7 Family) USB2 Enhanced Host Controller"
On a Lenovo R599 the controller version reads
"Intel(R) ICH9 Family USB Universal Host Controller"
"Intel(R) ICH9 Family USB2 Enhanced Host Controller"
where only the later (ICH9) is usable for the wiimote auto-power procedure here. Check our system specification, before proceeding.
4d: Find the id of the USB hubs on the system, open "Control panel | System | Hardware | Device management" and look for USB-controllers.
Open the USB-controller tap and write down the address of all the USB Universal host controllers, and USB2 Enhanced host controllers.
The id of the controllers are found by right-clicking on the device, selecting "Properties | Details"
On my eee PC I have four Intel controllers
PCI\VEN_8086&DEV_27C8&SUBSYS_830F1043&REV_02\3&11583659&0&E8
PCI\VEN_8086&DEV_27C9&SUBSYS_830F1043&REV_02\3&11583659&0&E9
PCI\VEN_8086&DEV_27CA&SUBSYS_830F1043&REV_02\3&11583659&0&EA
PCI\VEN_8086&DEV_27CB&SUBSYS_830F1043&REV_02\3&11583659&0&EB
and one USB2 controller
PCI\VEN_8086&DEV_27CC&SUBSYS_830F1043&REV_02\3&11583659&0&EF
Try to manually disable all the controllers bu
> devcon status "@PCI\VEN_8086&DEV_27C8&SUBSYS_830F1043&REV_02\3&11583659&0&E8"
or, if possible, you could use a pattern match to select all the devices...for my particular system the following expression works
> devcon status "@PCI\VEN_8086&DEV_27C*&SUBSYS_830F1043&REV_02\3&11583659&0&E*"
Then disable all devices
> devcon disable "@PCI\VEN_8086&DEV_27C*&SUBSYS_830F1043&REV_02\3&11583659&0&E*"
and check the result in the windows device manager (or manually disable all the USB controllers here)
Finally, pick an active controller and put its address into the wiiscan.ini file, for my particular setup the file then reads
% Configfile_begin
% config file for wiiscan
all_usb_hubs="@PCI\VEN_8086&DEV_27C*&SUBSYS_830F1043&REV_02\3&11583659&0&E*"
active_usb_hub="@PCI\VEN_8086&DEV_27C8&SUBSYS_830F1043&REV_02\3&11583659&0&E8"
allowed_wiimote_adr=00:00:00:00:00:00
whiteboard_software="d:/WiimoteWhiteboard/WiimoteWhiteboard_v0.3.exe"
% Configfile_end
It is not that important to choose a particular USB controller as the active one, important is that power is only cut to the USB when ALL controllers are disabled, and on when just a single controller is enabled.
Note: the use of other USB devices may be troublesome, when powering the wiimote over USB as here. It is not recommended to use USB devices together with this procedure!!
Add the addresses of your wiimotes to the .ini file
5: To enable faster an more robust connection, find and add all wiimote addresses to the .ini file in the form of a single address or a list, say
allowed_wiimote_adr=00:19:FD:CC:60:61 00:19:1D:D6:65:E5
Test an automated, unattended connection
6; Re-run the wiiscan.exe in a console. If it still fails try to give it a -v option for verbose output, tune the timing parameters (-b,-t,-u,-w), or mail all the results to me: carsten AT mergit.dk
Run the wiiscantray GUI version
7; Run wiiscantray.exe,
* click on "Rescan for wiimotes" to connect.
* click "Start whiteboard..." to start the whiteboard executable. Use the option "option_startwhiteboard=1" in the .ini file to start the software after a successful connection.
* click "Display log..." to show the log output, enable and control the log via the options "option_logfile=wiiscan_log.txt" and "option_debug=1
* use "Reset log..." to clear the log.
ENJOY
Feb 12 2009
Carsten Frigaard,
MergeIt ApS, Kongsvang Allé 37, DK-8000 Århus C, www.mergit.dk

674
doc/LICENSE.rtf
View File

@@ -1,674 +0,0 @@
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
<http://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read
<http://www.gnu.org/philosophy/why-not-lgpl.html>.

173
doc/MANUAL_wiiscan.rtf → doc/MANUAL.md
View File

@@ -1,31 +1,32 @@
wiiscan(1) wiiscan(1)
wiiscan(1)
NAME
wiiscan - a connection utility for wii console remotes
## NAME ##
SYNOPSIS
wiiscan - a connection utility for wii console remotes
## SYNOPSIS ##
wiiscan <-a <device> | -c <device> | -d <device> | -r | -s | -usbup |
-usbdown> > [-cf <file>] [-lf <file>] [-b <sleep>] [-t <sleep>] [-u
<sleep>] [-p <sleep>] [-w <sleep>] [-q <usbradio>] [-f <removemode>]
[-m <powermode>] [-l <wiilibrary>] [-wb] [-v]
OVERVIEW
wiiscan is a canvas function for a number of different scanning and
## OVERVIEW ##
wiiscan is a canvas function for a number of different scanning and
connection utilities. It can detect build-in bluetooth radios, scan for
nearby bluetooth devices, connect to a specific device and remove that
device again from the hardware.
The main feature of wiiscan is to automatically connect to a wii remote
The main feature of wiiscan is to automatically connect to a wii remote
(wiimote). This can be quiet cumbersome on a Windows system, and the
nesseccary steps for doing a robust, working connection is done by
Delete wiimote hardware HID bluetooth entry:
Delete wiimote hardware HID bluetooth entry:
delete old entries of the wiimote in the bluetooth hardware. On
some windows system the wiimote is readily detected, after the
first manually installation. Pressing the "1-2" makes the
@@ -36,7 +37,7 @@ wiiscan(1) wiiscan(1)
this feature.
Cycle USB bus:
Cycle USB bus:
the wiimote can be switched automatically to discoverable mode,
if the power is briefly cut from the device. This can be done
on a wiimote powered by the USB +5 volt (with a proper voltage
@@ -46,7 +47,7 @@ wiiscan(1) wiiscan(1)
by say some tape or gaffa!.
Scan for wiimote:
Scan for wiimote:
now comes the main part of the connection; scanning for a
wiimote. This includes bringing up the bluetooth radio device,
initialize seek parameters, scanning and matching for a device
@@ -76,10 +77,10 @@ wiiscan(1) wiiscan(1)
Power control over USB hubs is dependent on the particular hub
devices, and disabling the power may not be possible for a sin‐
gle USB port only. wiiscan uses a trick of disabling all USB
gle USB port only. wiiscan uses a trick of disabling all USB
hubs and then only enable and disable a singe hub.
Disabling all hubs is a precondition to running wiiscan and it
Disabling all hubs is a precondition to running wiiscan and it
can be accomblised by either going into "Control Panel | System
| Hardware | Device manager", and manually disable all USB hubs
or by using "devcon", say (careful, these commands applies only
@@ -118,29 +119,29 @@ wiiscan(1) wiiscan(1)
power cycle may cause severe interfere with the device.
DESCRIPTION
-a <device>
## DESCRIPTION ##
-a <device>
auto-connect to a device.
-c <device>
-c <device>
connects to a device.
-d <device>
-d <device>
deletes a device, clears HID and bluetooth registry entries.
-r looks for active internal bluetooth radio devices.
-r looks for active internal bluetooth radio devices.
-s scans for external bluetooth devices.
-s scans for external bluetooth devices.
-usbup turn the USB hub on.
-usbup turn the USB hub on.
-usbdown
-usbdown
turn the USB hub off.
@@ -150,69 +151,69 @@ wiiscan(1) wiiscan(1)
Note: "nintendo" is a shortcut for "Nintendo RVL-CNT-01"
OPTIONS
-cf <file>
## OPTIONS ##
-cf <file>
load a specific configuration file.
-lf <file>
-lf <file>
specify a distinct logfile.
-b <sleep>
-b <sleep>
auto-mode bluetooth connection sleep in milliseconds.
-t <sleep>
-t <sleep>
bluetooth scanning interval in milliseconds.
-u <sleep>
-u <sleep>
auto-mode USB connection sleep in milliseconds.
-p <sleep>
-p <sleep>
automode usbm post-connection sleep in milliseconds.
-w <sleep>
-w <sleep>
timeout for wiimote in milliseconds.
-q <usbradio>
-q <usbradio>
use bluetooth radio with this address. Note, this functionality
is not working yet.
-f <removemode>
-f <removemode>
pre-remove mode of device, 0=remove if not connectable,
1=always remove, 2=never remove
-m <powermode>
-m <powermode>
choose USB powercycle mode, 0=no power cycle, 1=use USB hub,
2=use USBm IO hardware, 3=use USB Delcon IO hardware.
-l <wiilibrary>
-l <wiilibrary>
use specific wiimote library, lib can be one-of
(wiiuse,wiimotelib).
-y scan retries in automode.
-y scan retries in automode.
-wb start whiteboard in auto-mode
-wb start whiteboard in auto-mode
-v enable extra debugging printouts
-v enable extra debugging printouts
FILES
wiiscan looks for a file names wiiscan.ini when executing in the auto‐
## FILES ##
wiiscan looks for a file names wiiscan.ini when executing in the auto‐
mode. See detail in the file.
TIMING
## TIMING ##
Various timing parametes can be set on the command line or in the
inifile. The process of connecting is
@@ -246,7 +247,7 @@ wiiscan(1) wiiscan(1)
option_wiitimeout.
EXAMPLE
## EXAMPLE ##
Scanning for devices nearby:
wiiscan -s
@@ -264,40 +265,40 @@ wiiscan(1) wiiscan(1)
wiiscan -usbup
COMPILING
## COMPILING ##
The source code can be compiled with MS Visual C++ Express 2008
(http:www.microsoft.com/express/vc/) or similar. It also needs wiiuse
dlls (http:www.wiiuse.net/). If wiiuse is to be compiled by it self it
needs Windows SDK and DDK, but running wiiscan with just the wiiuse
needs Windows SDK and DDK, but running wiiscan with just the wiiuse
binaries is the easiest option.
It does not work on Windows 2000, and has not been tried out on a Vista
system.
TESTED SYSTEMS
The wiiscan has been tested on a Lenovo Thinkpad R500, XP professional
## TESTED SYSTEMS ##
The wiiscan has been tested on a Lenovo Thinkpad R500, XP professional
(without build-in bluetooth) with a Trendnet TBW-102UB bluetooth don‐
gle, and on a ASUS eeePC 1000H with XP home.
Only the MS bluetooth stack was tested.
Lenovo setup
Lenovo setup
Windows XP professional, version 2002, SP2 USB dongle: Trendnet
TBW-102UB bluetooth(Broadcom Ultimate Low Cost Bluetooth
2.0+EDR USB), date 24-02-2004, driver 5.1.2535.0 Microsoft BT
stack: date 03-08-2004, driver 5.1.2600.2180
eee setup
eee setup
Windows XP home, version 2002, SP3 USB dongle: buildin Azware
BT252, date 13-04-2008, driver 5.1.2600.5512 Microsoft BT
stack: date 13-04-2008, driver 5.1.2600.5512
BUGS
1: restart pop-up (FIXED)
## BUGS ##
1: restart pop-up (FIXED)
Installing new hardware causes windows to require restart. Hap‐
pens once in a while, balloon pop-ups reports hardware, that
where installed but not working properly. A restart pop-up
@@ -312,7 +313,7 @@ wiiscan(1) wiiscan(1)
dialog can anyway safly be ignored!
2: discoverable mode fast shutdown (FIXED)
2: discoverable mode fast shutdown (FIXED)
Sometimes the wiimote goes quickly out of discoverable mode, it
takes it only about 3 seconds from turn-on to turn-off. This
makes it hard to obtain a connection to it. Both my wiimotes
@@ -326,34 +327,34 @@ wiiscan(1) wiiscan(1)
wiimote connection has also been introduced.
3: buttons not working (OPEN)
3: buttons not working (OPEN)
Pressing the 1-2 button combination sometimes fails to turn-on
the wiimote, pressing sync or power makes it work again. The
the "1-2 button freeze" happens after a failed connection
attempt. See also bug-2.
4: radio null (OPEN)
4: radio null (OPEN)
Sometimes the BT radio fails to reinitialize after a USB
down/up flip, this means that "RadioInfo(time‐
out,true,dbg)"return NULL. Can be fixed by placing the blue‐
tooth radio device on another bus than the USB.
5: keep blinking (OPEN)
5: keep blinking (OPEN)
Sometimes the wiimote is found and connected OK, but the LEDs
keeps blinking (normal connect mode: LEDs are turned perma‐
nently on). This does however not affect connectability, and
the wiimote does not turn off again automatically.
6: failed to find wiimote (OPEN)
6: failed to find wiimote (OPEN)
Wiimote failed to find devices. This may be a non-fatal error
or an error caused by an undervolted wiimote. The
"wiiuse_find(0x0,4,2/4/6)" keeps returning 0.
7: remove failed (OPEN)
7: remove failed (OPEN)
Sometimes the remove steps fails, but this may be non-fatal
Removing device <Nintendo RVL-CNT-01>
@@ -361,7 +362,7 @@ wiiscan(1) wiiscan(1)
Done [FAILED]
8; balloon-tips (FIXED)
8; balloon-tips (FIXED)
Balloon-tips are annoying when connecting new hardware. Small
fix: do
@@ -372,13 +373,13 @@ wiiscan(1) wiiscan(1)
"EnableBalloonTips"=dword:00000000
9: double delete (FIXED)
9: double delete (FIXED)
Double delete of nintendo device may cause BluetoothFindFirst‐
Device() to return null Fixed by removing the throw, replacing
it with a "if (hbf()==NULL) then return false"
10: BSoD (OPEN)
10: BSoD (OPEN)
The "Blue Screen of Death" was encountered a number of times,
indicating a errorneous device driver. The cause may be in the
MS bluetooth stack or in the wiiuse lib. The BSoD mainly
@@ -389,7 +390,7 @@ wiiscan(1) wiiscan(1)
stack: date 03-08-2004, driver 5.1.2600.2180" (Lenovo version).
11: New Hardware found wizard (OPEN)
11: New Hardware found wizard (OPEN)
Sometimes the wizard appears out of the blue, when deleting the
HID entry and trying to reinstall it. It is the call Bluetooth‐
SetServiceState(...) that messes the Window system up. Dis‐
@@ -399,7 +400,7 @@ wiiscan(1) wiiscan(1)
cure this defect.
12: Devcon hangs (FIXED)
12: Devcon hangs (FIXED)
The devcon commands sometimes hangs at the diable USB command.
The state of the USB controllers, and BT devices are undefined
(some BT devices disabled, others not) and manually trying to
@@ -409,7 +410,7 @@ wiiscan(1) wiiscan(1)
FIX: reboot the machine.
13: Open Device fails to find a Nintendo (PARTLY FIXED)
13: Open Device fails to find a Nintendo (PARTLY FIXED)
When opening a named nintendo device, say 'Nintendo RVL-
CNT-01', the bluetooth fails to get the name from the device.
This results in an empty name, and hence matching on the name
@@ -420,7 +421,7 @@ wiiscan(1) wiiscan(1)
the ini file.
14: Wiiscan fails to run (FIXED)
14: Wiiscan fails to run (FIXED)
Running wiiscan in a dosbox makes it terminate immidiatly. Run‐
ning the tray version, or under MS VS Express causes it to dis‐
play an missing DLL dialog (msvcp90.dll and friends).
@@ -430,7 +431,7 @@ wiiscan(1) wiiscan(1)
of dynamic DLLs.
15: BluetoothFindFirstDevice() stalls (FIXED)
15: BluetoothFindFirstDevice() stalls (FIXED)
The BluetoothFindFirstDevice() sometimes newer returns. Happens
only for MS stack version "Microsoft BT stack: date 13-04-2008,
driver 5.1.2600.5512" (eee stack).
@@ -445,51 +446,41 @@ wiiscan(1) wiiscan(1)
out.
16: Wiimote drops connection after scanning (PARTLY FIXED)
16: Wiimote drops connection after scanning (PARTLY FIXED)
If a connection attempt goes well until the last part, it is
most likely due to low-power batteries. The final stage of con‐
necting draw extra power, that might cause the wiimote to shut‐
down.
## SEE ALSO ##
wiiuse
SEE ALSO
wiiuse Wiiuse is a library written in C that connects with several
Nintendo Wii remotes. Supports motion sensing, IR tracking,
nunchuk, classic controller, and the Guitar Hero 3 controller.
Single threaded and nonblocking makes a light weight and clean
API.
Wiiuse is a library written in C that connects with several Nintendo Wii remotes. Supports motion sensing, IR tracking, nunchuk, classic controller, and the Guitar Hero 3 controller. Single threaded and nonblocking makes a light weight and clean API. Licensed under GNU GPLv3 and GNU LGPLv3 (non-commercial) by Michael Laforest (<http:www.wiiuse.net/>)
Licensed under GNU GPLv3 and GNU LGPLv3 (non-commercial) by
Michael Laforest,
Wiimote Whiteboard
(http:www.wiiuse.net/)
Whiteboard software by Johnny Chung Lee.
(http:www.cs.cmu.edu/~johnny/projects/wii/,
http:www.wiimoteproject.com/)
devcon(1)
USB management software.
(http:support.microsoft.com/kb/311272)
Wiimote Whiteboard
Whiteboard software by Johnny Chung Lee.
(http:www.cs.cmu.edu/~johnny/projects/wii/,
http:www.wiimoteproject.com/)
devcon(1)
USB management software.
(http:support.microsoft.com/kb/311272)
VERSION
## VERSION ##
Version 0.9 NDEBUG
AUTHOR
## AUTHOR ##
Carsten Frigaard, Mergeit ApS, Kongsvang Allé 37, DK-8000 Århus C,
www.mergit.dk
COPYRIGHT
## COPYRIGHT ##
Copyright © 2009 MergeIt, Aps. License LGPL3 : GNU lesser GPL, version
3, <http:www.gnu.org/licenses/lgpl.txt>. This is free software: you are
free to change and redistribute it. There is NO WARRANTY, to the extent
@@ -497,4 +488,4 @@ wiiscan(1) wiiscan(1)
26 Mar 2009 wiiscan(1)
26 Mar 2009 wiiscan(1)

25
doc/README.rtf
View File

@@ -1,25 +0,0 @@
Copyright © 2008 MergeIt, Aps.
License GPLv3+: GNU GPL version 3 or later <http:\/\/gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Permission to use, copy, modify, and distribute this software
and its documentation for any purpose and without fee is hereby granted, provided that
the above copyright notice appear in all copies and that both that copyright notice
and this permission notice appear in supporting documentation.
WIISCAN:
a connection utility for wii console remotes
VERSION:
0.9
INSTALL:
just run Release/wiiscan or Release/wiiscantray
DOC:
read wiiscan.1 ("man ./wiiscan.1" or "more wiiscan.1.txt")
NOTE:
modify the Release/wiiscan.ini file according to the USB hub device remarks in the documentation before runnnig wiiscan!

25
doc/README.rtf~
View File

@@ -1,25 +0,0 @@
Copyright © 2008 MergeIt, Aps.
License GPLv3+: GNU GPL version 3 or later <http:\/\/gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Permission to use, copy, modify, and distribute this software
and its documentation for any purpose and without fee is hereby granted, provided that
the above copyright notice appear in all copies and that both that copyright notice
and this permission notice appear in supporting documentation.
WIISCAN:
a connection utility for wii console remotes
VERSION:
0.9
INSTALL:
just run Release/wiiscan or Release/wiiscantray
DOC:
read wiiscan.1 ("man ./wiiscan.1" or "more wiiscan.1.txt")
NOTE:
modify the Release/wiiscan.ini file according to the USB hub device remarks in the documentation before runnnig wiiscan!

358
doc/wiiscan.1
View File

@@ -1,358 +0,0 @@
.TH wiiscan 1 "26 Mar 2009"
.SH NAME
\fIwiiscan\fP - a connection utility for wii console remotes
.SH SYNOPSIS
wiiscan <-a <device> | -c <device> | -d <device> | -r | -s | -usbup | -usbdown> > [-cf <file>] [-lf <file>] [-b <sleep>] [-t <sleep>] [-u <sleep>] [-p <sleep>] [-w <sleep>] [-q <usbradio>] [-f <removemode>] [-m <powermode>] [-l <wiilibrary>] [-wb] [-v]
.SH OVERVIEW
\fIwiiscan\fP is a canvas function for a number of different scanning and connection utilities. It can detect build-in bluetooth radios, scan for nearby bluetooth devices, connect to a specific device and remove that device again from the hardware.
The main feature of \fIwiiscan\fP is to automatically connect to a wii remote (wiimote). This can be quiet cumbersome on a Windows system, and the nesseccary steps for doing a robust, working connection is done by
.TP 8
.B Delete wiimote hardware HID bluetooth entry:
delete old entries of the wiimote in the bluetooth hardware. On some windows system the wiimote is readily detected, after the first manually installation. Pressing the "1-2" makes the wiimote discoverable. On other systems (including mine), any attempt to connect to the wiimote, after one successful or un-successful connection attempt, will always fail! Removing the HID and wiimote registry entries before the next attempt cures this feature.
.TP 8
.B Cycle USB bus:
the wiimote can be switched automatically to discoverable mode, if the power is briefly cut from the device. This can be done on a wiimote powered by the USB +5 volt (with a proper voltage regulator to bring it under +3 volt). This step hence turns the USB hub off, killing the power, and turns it on again. The "1-2" buttons on the wiimote must be pressed at all times, done by say some tape or gaffa!.
.TP 8
.B Scan for wiimote:
now comes the main part of the connection; scanning for a wiimote. This includes bringing up the bluetooth radio device, initialize seek parameters, scanning and matching for a device name or address, connecting to a matched device, installing the HID interface (that was removed in the first step), and finally trying to open the wiimote and reading some data from it. All steps involve a time variable, meaning that say installing the HID causes some windows registry fiddling, that takes a rather variable amount of time, and the next step is critically dependent on the former step to be finished. Hence a number of tunable waiting variable is introduced, Important is to being able to reach the final connection step before the wiimote goes out of the discoverable mode and automatically turns off.
.TP 8
A note on USB voltage cycling:
This software solution is able to restart the wiimote in discoverable mode automatically. But this require that the wiimote is powered by a USB cable to the PC and that the "1-2" button combination is permanently pressed. Cycling the power for the wiimote with the "1-2" buttons pressed enables the discoverable mode, and the continuously pressing "1-2" does not interfere with wiimote operations hereafter.
So this is a non-intrusive fix to the so called "Ladder problem" (http:\/\/wyxs.net/web/wiimote/digital_whiteboard.html).
Power control over USB hubs is dependent on the particular hub devices, and disabling the power may not be possible for a single USB port only. \fIwiiscan\fP uses a trick of disabling all USB hubs and then only enable and disable a singe hub.
Disabling all hubs is a precondition to running \fIwiiscan\fP and it can be accomblised by either going into "Control Panel | System | Hardware | Device manager", and manually disable all USB hubs or by using "devcon", say (careful, these commands applies only to my system)
devcon disable "@PCI\VEN_8086&DEV_293*&SUBSYS_20F117AA&REV_03\3&B1BfB6*"
devcon disable "@PCI\VEN_8086&DEV_293*&SUBSYS_20F017AA&REV_03\3&B1BfB6*"
being careful that the pattern matches only our USB hubs!. You can test this by
devcon status "@PCI\VEN_8086&DEV_293*&SUBSYS_20F117AA&REV_03\3&B1BfB6*"
devcon status "@PCI\VEN_8086&DEV_293*&SUBSYS_20F017AA&REV_03\3&B1BfB6*"
A single USB now may be enabled or disabled by
devcon disable @PCI\VEN_8086*DEV_2934*SUBSYS_20F017AA*
again with the particular address for your system as a variable you need to lookup. The voltage on the USB bus can now be checked Using a voltmeter (see details in http:\/\/wyxs.net/web/wiimote/digital_whiteboard.html).
.TP 8
NOTE: The configuration file of wiiscan contains the particular system dependent USB hub pattern matches.
.TP 8
NOTE: be careful of connecting other devices to the USB bus, since the power cycle may cause severe interfere with the device.
.SH DESCRIPTION
.TP 8
.B -a <device>
auto-connect to a device.
.TP 8
.B -c <device>
connects to a device.
.TP 8
.B -d <device>
deletes a device, clears HID and bluetooth registry entries.
.TP 8
.B -r
looks for active internal bluetooth radio devices.
.TP 8
.B -s
scans for external bluetooth devices.
.TP 8
.B -usbup
turn the USB hub on.
.TP 8
.B -usbdown
turn the USB hub off.
.TP 8
Default mode: wiiscan -a " Nintendo RVL-CNT-01"
.TP 8
Note: "nintendo" is a shortcut for "Nintendo RVL-CNT-01"
.SH OPTIONS
.TP 8
.B -cf <file>
load a specific configuration file.
.TP 8
.B -lf <file>
specify a distinct logfile.
.TP 8
.B -b <sleep>
auto-mode bluetooth connection sleep in milliseconds.
.TP 8
.B -t <sleep>
bluetooth scanning interval in milliseconds.
.TP 8
.B -u <sleep>
auto-mode USB connection sleep in milliseconds.
.TP 8
.B -p <sleep>
automode usbm post-connection sleep in milliseconds.
.TP 8
.B -w <sleep>
timeout for wiimote in milliseconds.
.TP 8
.B -q <usbradio>
use bluetooth radio with this address. Note, this functionality is not working yet.
.TP 8
.B -f <removemode>
pre-remove mode of device, 0=remove if not connectable, 1=always remove, 2=never remove
.TP 8
.B -m <powermode>
choose USB powercycle mode, 0=no power cycle, 1=use USB hub, 2=use USBm IO hardware, 3=use USB Delcon IO hardware.
.TP 8
.B -l <wiilibrary>
use specific wiimote library, lib can be one-of (wiiuse,wiimotelib).
.TP 8
.B -y
scan retries in automode.
.TP 8
.B -wb
start whiteboard in auto-mode
.TP 8
.B -v
enable extra debugging printouts
.SH FILES
\fIwiiscan\fP looks for a file names wiiscan.ini when executing in the automode. See detail in the file.
.SH TIMING
Various timing parametes can be set on the command line or in the inifile. The process of connecting is
.TP 8
1: USB power down
.TP 8
2: Delete old HID entries
.TP 8
3: Sleep at least option_usbsleep (from 1) before commencing
.TP 8
4: USB power up
.TP 8
5: Sleep at least option_usbmsleep (from 3) before commencing. Sleep is only nesseccary for USBmicro devices, since step 4 is much faster using this device compared to the USB hub.
.TP 8
6: Find and wiimote and connect. Scan bluetooth the duration in option_timeout.
.TP 8
7: Sleep option_btsleep before commencing; waiting for HID entries and new-hardware-found to finish in windows.
.TP 8
8: Connect to the wiimote, Scan for wiimotes using the duration option_wiitimeout.
.SH EXAMPLE
Scanning for devices nearby:
wiiscan -s
Auto-connect to a nintendo device, scan bluetooth for four seconds, verbose on, and enable start of whiteboard software after a successful connection
wiiscan -a nintendo -t 4000 -v -wb
Cycle USB bus voltage
wiiscan -usbdown
wiiscan -usbup
.SH COMPILING
The source code can be compiled with MS Visual C++ Express 2008 (http:\/\/www.microsoft.com/express/vc/) or similar. It also needs wiiuse dlls (http:\/\/www.wiiuse.net/). If wiiuse is to be compiled by it self it needs Windows SDK and DDK, but running \fIwiiscan\fP with just the wiiuse binaries is the easiest option.
It does not work on Windows 2000, and has not been tried out on a Vista system.
.SH TESTED SYSTEMS
The \fIwiiscan\fP has been tested on a Lenovo Thinkpad R500, XP professional (without build-in bluetooth) with a Trendnet TBW-102UB bluetooth dongle, and on a ASUS eeePC 1000H with XP home.
Only the MS bluetooth stack was tested.
.TP 8
.B Lenovo setup
Windows XP professional, version 2002, SP2
USB dongle: Trendnet TBW-102UB bluetooth(Broadcom Ultimate Low Cost Bluetooth 2.0+EDR USB), date 24-02-2004, driver 5.1.2535.0
Microsoft BT stack: date 03-08-2004, driver 5.1.2600.2180
.TP 8
.B eee setup
Windows XP home, version 2002, SP3
USB dongle: buildin Azware BT252, date 13-04-2008, driver 5.1.2600.5512
Microsoft BT stack: date 13-04-2008, driver 5.1.2600.5512
.SH BUGS
.TP 8
.B 1: restart pop-up (FIXED)
Installing new hardware causes windows to require restart. Happens once in a while, balloon pop-ups reports hardware, that where installed but not working properly. A restart pop-up wants to reboot the PC. Small fix: just delete the device and re-run "wiiscan -c nintendo".
FIX: the 'Change of systemsettings ... Do you want to reboot now?' popup, happens only when the program runs for longer than 19 seconds. Keeping the connection time within 19 sec seems to cure the problem, Adding a sleep at the end of the program, say Sleep(20000) will eventually bring up the dialog again. The dialog can anyway safly be ignored!
.TP 8
.B 2: discoverable mode fast shutdown (FIXED)
Sometimes the wiimote goes quickly out of discoverable mode, it takes it only about 3 seconds from turn-on to turn-off. This makes it hard to obtain a connection to it. Both my wiimotes does this once in a while, after failed connection attempts.
Pressing one button only "1" or "2" makes the wiimote blink for a short time, but it is not really discoverable.
FIX: Initialization of wiilib has been rewritten, making it recall the HID inialization routine. Code for testing the wiimote connection has also been introduced.
.TP 8
.B 3: buttons not working (OPEN)
Pressing the 1-2 button combination sometimes fails to turn-on the wiimote, pressing sync or power makes it work again. The the "1-2 button freeze" happens after a failed connection attempt. See also bug-2.
.TP 8
.B 4: radio null (OPEN)
Sometimes the BT radio fails to reinitialize after a USB down/up flip, this means that "RadioInfo(timeout,true,dbg)"return NULL. Can be fixed by placing the bluetooth radio device on another bus than the USB.
.TP 8
.B 5: keep blinking (OPEN)
Sometimes the wiimote is found and connected OK, but the LEDs keeps blinking (normal connect mode:
LEDs are turned permanently on). This does however not affect connectability, and the wiimote does not turn off again automatically.
.TP 8
.B 6: failed to find wiimote (OPEN)
Wiimote failed to find devices. This may be a non-fatal error or an error caused by an undervolted wiimote. The "wiiuse_find(0x0,4,2/4/6)" keeps returning 0.
.TP 8
.B 7: remove failed (OPEN)
Sometimes the remove steps fails, but this may be non-fatal
Removing device <Nintendo RVL-CNT-01>
** error: failed to find device
Done [FAILED]
.TP 8
.B 8; balloon-tips (FIXED)
Balloon-tips are annoying when connecting new hardware. Small fix: do
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\Advanced]
"EnableBalloonTips"=dword:00000000
.TP 8
.B 9: double delete (FIXED)
Double delete of nintendo device may cause BluetoothFindFirstDevice() to return null Fixed by removing the throw, replacing it with a "if (hbf()==NULL) then return false"
.TP 8
.B 10: BSoD (OPEN)
The "Blue Screen of Death" was encountered a number of times, indicating a errorneous device driver. The cause may be in the MS bluetooth stack or in the wiiuse lib. The BSoD mainly occured in the first phase of this project and havent been seen for a while with the current version (v0.7).
Only happens for MS bluetooth stack version "Microsoft BT stack: date 03-08-2004, driver 5.1.2600.2180" (Lenovo version).
.TP 8
.B 11: New Hardware found wizard (OPEN)
Sometimes the wizard appears out of the blue, when deleting the HID entry and trying to reinstall it. It is the call BluetoothSetServiceState(...) that messes the Window system up. Disabling the wizard or disabling the Plug and play system do not seem to be an option, since the HID then newer get installed, and ends up in a failty state. A reboot of the system does not cure this defect.
.TP 8
.B 12: Devcon hangs (FIXED)
The devcon commands sometimes hangs at the diable USB command. The state of the USB controllers, and BT devices are undefined (some BT devices disabled, others not) and manually trying to disable or enable the USB constroller fails. A status on the USB device gives a strange result.
FIX: reboot the machine.
.TP 8
.B 13: Open Device fails to find a Nintendo (PARTLY FIXED)
When opening a named nintendo device, say 'Nintendo RVL-CNT-01', the bluetooth fails to get the name from the device. This results in an empty name, and hence matching on the name fails.
FIX: use a device adresss instead of a name. Put, say 'allowed_wiimote_adr=00:19:FD:CC:60:61 00:19:1D:D6:65:E5' in the ini file.
.TP 8
.B 14: Wiiscan fails to run (FIXED)
Running wiiscan in a dosbox makes it terminate immidiatly. Running the tray version, or under MS VS Express causes it to display an missing DLL dialog (msvcp90.dll and friends).
FIX: this is a MS bug, but can be fixed by setting the MT library in the project setting to use static libraries instead of dynamic DLLs.
.TP 8
.B 15: BluetoothFindFirstDevice() stalls (FIXED)
The BluetoothFindFirstDevice() sometimes newer returns. Happens only for MS stack version
"Microsoft BT stack: date 13-04-2008, driver 5.1.2600.5512" (eee stack).
Code stalls here:
DeviceAutoClose<HBLUETOOTH_DEVICE_FIND,BOOL> hbf(BluetoothFindFirstDevice(&bdsp,&bdi),&BluetoothFindDeviceClose);
FIX: start the BluetoothFindFirstDevice() function in a thread, terminate the thread if it has run for longer than, say 2+timeout.
.TP 8
.B 16: Wiimote drops connection after scanning (PARTLY FIXED)
If a connection attempt goes well until the last part, it is most likely due to low-power batteries. The final stage of connecting draw extra power, that might cause the wiimote to shutdown.
.SH SEE ALSO
.TP 8
.B wiiuse
Wiiuse is a library written in C that connects with several Nintendo Wii remotes. Supports motion sensing, IR tracking, nunchuk, classic controller, and the Guitar Hero 3 controller. Single threaded and nonblocking makes a light weight and clean API.
Licensed under GNU GPLv3 and GNU LGPLv3 (non-commercial) by Michael Laforest,
(http:\/\/www.wiiuse.net/)
.TP 8
.B Wiimote Whiteboard
Whiteboard software by Johnny Chung Lee.
(http:\/\/www.cs.cmu.edu/~johnny/projects/wii/, http:\/\/www.wiimoteproject.com/)
.TP 8
.B devcon(1)
USB management software.
(http:\/\/support.microsoft.com/kb/311272)
.SH VERSION
Version 0.9 NDEBUG
.SH AUTHOR
Carsten Frigaard, Mergeit ApS, Kongsvang Allé 37, DK-8000 Århus C, www.mergit.dk
.SH COPYRIGHT
Copyright © 2009 MergeIt, Aps. License LGPL3 : GNU lesser GPL, version 3, <http:www.gnu.org/licenses/lgpl.txt>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.