Annex 2
Annex 2
Página 1
     Do-it-yourself project to use a Wii remote controller, Wiiscan software and USB powering for a digital
                                      interactive whiteboard in classrooms
Contents
  6. Wiiscan
     6.1 WIISCAN_manual
     6.2 WIISCAN -H.rtf
     6.3 Wiiscan.ini
     6.4 INSTALL.rtf
     6.5 Wiiscantray
     6.6 Basic pen software
     6.7 Problems
  8. Whiteboards
     8.1. Melamine
     8.2. HPL (High Pressure Laminate)
       8.2.1 Cleaning HPL
       8.2.2 Glueing HPL
     8.3. Enamel
     8.4. Paint
     8.5. Plastic foil
  9. Speakers
     9.1. Speaker in the projector
     9.2. Separate speakers
  13. Software
    13.1. IR pen
    13.2. Pointers
    13.3. Whiteboard software
15. Testimonials
17. Disclaimer
  1. Introduction
  The Nintendo Wii remote controller is a popular device to construct digital interactive whiteboards. Most of them
  are based on Johnny Chung Lee's original idea, to be viewed on http://www.ted.com/talks/view/id/245.
  Johnny's splendid idea will almost certainly not function in a classroom, crowded with eager pupils and a teacher
  willing to educate them. Sooner or later one of them would touch the Wii remote controller (Wiimote from now on)
  , causing recalibration and thus the end of the lesson. Or, at the wrong moment of course, the batteries are empty
  and a pupil has to find fresh ones; unfortunately unavaiable. Or, starting up a program would fail because of some
  error, somehow during the operation. In classrooms Murpy's law is at its best! What is needed to use Johnnys idea
  in a classrooms is 'engineering'. The goal was set.
  A small group of enthousiasts took up Johnnys initial idea to construct a digital interactive whiteboard that is
  effectively usable in a classroom. The how to of that first prototype is still available on http://wyxs.net/web/
  wiimote/digital_whiteboard.html. During a year a teacher of grade 3 and her pupils gained practical experience in
  the classroom with the prototype and discovered that it needed several improvements and engineering. The
  engineering involved designing a stable, robust, reproducable, error- and maintenance free, open solution.
  In the classroom it means that, after a complete installation, the teacher only needs to power on the PC to start
  wroking with the pen.
complete_set-460x613.jpg
   For those who already have some of the expensive parts, a do-it-yourself kit without them is available. It contains:
   the USB power module enclosure, connectors, printed circuit boards, a microcontroller, transistor, crystal, voltage
http://wyxs.net/web/wiiscan/                                                                         06/06/2012 16:06:09
Do-it-yourself project to use a Wii remote controller, Wiiscan software and USB powering for a digital inte...   Página 5
  For those who already have some of the expensive parts, a do-it-yourself kit without them is available. It contains:
  the USB power module enclosure, connectors, printed circuit boards, a microcontroller, transistor, crystal, voltage
  regulator, resistors, capacitors, etcetera. Not included are the Nintendo Wiimote, the infra red pen, the ceiling
  mount and cables.
diy-kit.png
  By supplying the do-it-yourself kit, we assume you have a Wiimote laying around and you can make an infra red
  pen yourself. Simple manuals can be found on many places on the internet and here: http://wyxs.net/web/wiimote/
  digital_whiteboard.html.
  The cables we use are a standard USB A B cable between the Wiimote and the power module, and a self made
  cable with 2 RJ11 6P6C connectors and Cat 5 cable. For details, see section 3.5 Cables.
  A third option is to read this how to and do everything yourself. The how to describes the construction of a USB
  power module to power a Wiimote via the USB port of a PC and a microcontroller, a P-Channel MOS FET and a
  voltage regulator. The microcontroller costs $ 8,-- and is available via Delcom as part no. 902370. The other parts
  can be bought at most electronic parts stores.
  Also the connection of the Wiimote via Bluetooth to the PC is described in detail, as well as an installation guide
  on .NET USB 2.0, .NET Framework, Bluetooth and the software. The software used to operate the Wiimote is
  'Wiiscan',developed as open source software under a General Public License by Carsen Frigaard from Mergeit. The
  how to also gives suggestions on setting up the videoprojector, on whiteboard materials, speakers, mounts, cursors,
  etcetera.
  A project like this leans on many shoulders. Basic research was done by Carsten Frigaard from Mergeit. Carsten
  developed the Wiiscan software and the USB power module. We are very thankful for his OSS/GPL contribution to
  education.
  Niels Kooy engineerded Carstens work into robust, stable hardware. The public primary schools Corantijn and Joop
  Westerweel financed the initial experiments for this project. Peter Fokker, Arnold v.d. Burger and many others
  contributed with advice and practical help.
  Primary education itself thanks you all for your contributions!
  Of course, the author of this DIY project is the only one responsable for the text, its typos and errors. Tips and
  suggestions are welcome.
  1.3 Warning!
  Please, before doing anyting, read section 13. Disclaimer, the ususal disclaimer.
  1.4 Support
  When looking for support for the building, please find a electronics hobbyist. She is perfectly able to understand
  this text and build the devices for your school. As for installation support: please read this how to. It's all we know.
  Tips and suggestions are welcome.
  1.5 Skills
  When you have a ready made set, you only need to install software for which you need average computer skills.
  You should be able to open the DOS box and use basic DOS commands like 'cd', 'dir' and 'copy'. Furthermore you
  can download from the Internet, save, unzip, move and rename directories and files, install simple software, edit
  files with Notepad and create directories and links.
  For the DIY project of making the USB power module and the conversions to the Wiimote, basic electronic skills
  are necessary. With the help of the soldering mask on the pc boards and the schematics, you will find your way.
  Other DIY skills needed are cutting, sawing, filing and soldering.
The most needed skills for this project are precision and patience, patience.
  1.6 Conventions
  A lot of work is done in Windows. To easily naviagte in this OS we follow the way described in the following
  example, whereafter the explanation follows.
  "Go Start > Settings > Control Panel > System > W: System Properties > T:Hardware > B: Device Manager > W:
  Device Manager > Universal Serial Bus Controllers > + > USB Root Hub.
  This means: With your mouse, point to the 'Start' button in the lower left corner of your desktop. Left click with
  your mouse on the 'Start' button and navigate to 'Settings', whereafter you navigate to 'Control Panel'. Left click on
  'Control Panel'. A new window opens: Select 'System'. A window (System Properties) opens, select tab 'Hardware'.
  The tab opens, click button 'Device manager'. Window Device manager Opens, select USB Controllers, click + to
  open the list and find 'USB Root Hub.
  Using the '>', simple abbreviations and a bit of imagination, you will soon be familiar with this.
When we ask you to click a button, the button name is, for example, written as: [OK], [Next] or [Finish].
The text below is an adaption from one of our other projects: http://serveratschool.net
  Part of the workstation setup is working on the command line in a DOS environment. Here are the rules of
  engagement:
        DOS is not case sensitive. When DOS commands, filenames and program names are used in the text,
        UPPERCASE haracters are used. This does not mean you have to type uppercase. Commands etc. can be issued
        DOS is not case sensitive. When DOS commands, filenames and program names are used in the text,
        UPPERCASE haracters are used. This does not mean you have to type uppercase. Commands etc. can be issued
        in lower or upper case, even mixed.
        Windows is not case sensitive but is case preserving. When Windows-specific names are used in the text, we
        try to preserve the case, e.g. H:\My Documents rather than the otherwise equivalent H:\MY DOCUMENTS .
        In DOS, commands are invoked with an [Enter]. We will omit "... and press the [Enter] key on your
        keyboard" with every instruction in order to keep the documentation as readable as possible.
        The names of buttons are displayed between square brackets, e.g, [OK], [Next], [Finish].
        The keys on the keyboard are displayed as follows: [Enter] for the 'Enter' key and [Tab] for the tabulator
        key. Combinations of keys are displayed as follows: [Alt-U] means: 'press and hold the Alt key and hit the
        key labeled U' and [Ctrl-Alt-Del] means: 'press and hold the Ctrl key and the Alt key and hit the Del key'.
(top)
  NOTICE:
  The amount of memory (512 Mb RAM) is seems rather low. More is better; wich also applies to the processor
  speed. It seems a full fledged interactive whiteboard with running applications needs a rather fast computer. More
  info needed.
  2.2.1 Computer
  You need a PC with at least two free USB 2.0 slots. One for a USB Bluetooth radio (dongle) that establishes the
  data connection between the Wiimote and the PC. The other USB slot is used to power the USB power module that
  powers the Wiimote.
  To check if the PC indeed has USB 2.0, proceed as follows:
  Go: Start > Settings > Control Panel > System > W: System Properties > T: Hardware > B: Device Manager > W:
  Device Manager.
  In the hardware list, search for 'Universal Serial Bus Controllers'. Click the + to expand the list. Look for the line
  containing 'XXX USB Enhanced Host controller'. 'XXX' refers to the chip brand.
  conjunction with our DHCP server. Later on we took Mr. Harsh advice serious and bought a Belkin USB 2.0 Hi-
  Speed PCI card
  Check your work. Go: Start > Settings > Control Panel > System > W: System Properties > T: Hardware > B:
  Device Manager > W: Device Manager > Universal Serial Bus Controllers > +. Look for the line containing 'XXX
  USB Enhanced Host Controller'. 'XXX' refers to the chipset manufacturer.
  In the list of USB controllers our 'VIA USB Enhanced Host Controller' was found. So, you now have USB 2.0.
2.1.1 Problems
  Everything worked well with the PCI card, but we could not enter the BIOS anymore and we could not enter
  SABRINE (http://serveratschool.net). The problem was solved with the Belkin USB 2.0 fHigh-Speed PCI card. We
  also found found usefule info on http://www.usbman.com/Guides/usb_2%20pci%20cards.htm from which we
  quote: "VIA has entered the USB 2.0 PCI card business. VIA based cards can be troublesome and the driver
  installation is confusing. I recommend that you choose an NEC based card from the list of tested and approved
  cards below.". As said, we changed to Belkin. See the site.
  Again, see [1]
2.2.3 Bluetooth
  The Wiiscan software steers the USB power moudle that powers the Wiimote. Wiiscan also takes care of setting up
  the connection between the Wiimote and the PC. The data transfer between the Wiimote and the PC is done via a
  Bluetooth connection. The connection is established with a USB Bluetooth device, also known as a 'dongle'. Basic
  info on Bluetooth can be found on: http://en.wikipedia.org/wiki/Bluetooth.
  Info on the Bluetoot stack (driver software) can be found at: http://en.wikipedia.org/wiki/Bluetooth_stack
  For this project, the USB Bluetooth device must be a Microsoft comatipble USB Bluetooth dongle. In other words,
  it must be able to operate with the MS Bluetooth stack (driver software).
  NOTICE:
  Do NOT install the driver that is packed with a USB bluetooth dongle! Wiiscan only operates with the Microsoft
  BT stack. Do not worry if you already installed BT drivers; this issue is discussed below.
  Maybe it's best to buy [1] a USB Bluetooth dongle, of which the spcifications says it needs no driver on Windows
  XP Pro/Home, Vista or W7. That one will almost surely use the built in MS Bluetooth stack.
The USB BT dongle installation procedure is not, but can be complicated. Three conditions can occur:
     1. Your PC does not have Bluetooth. You have to buy [1] a Bluetooth USB dongle. Buy a MS compatible one
        and continue with 'Installing a MS compatible USB Bluetooth dongle'.
     2. Your PC has an MS compatible Bluetooth USB dongle, but you already installed a driver. Continue with 'I
        already insted a driver for my MS BT USB dongle'.
     3. You have a BT dongle built in the PC or separate, but it's not MS compatible and a driver is installed. See
        below under 'BT USB dongle problems'
  Also check if the dongle is actually working. You cannot use the USB power module because you are not sure it's
  built without errors. So you test Bluetooth functionality by using the Wiimote and power it with 2 1,5 Volt AA
  batteries in stead of the USB power module.
  Carefully open the battery lid and remove it from the Wiimote. Insert two fresh 1,5 volt AA batteries in the battery
  compatiment.
  Press the buttons 1 and 2 continuously; or even beetter, use a tie-wrap and a piece fo plastic to press the buttons 1
  and 2 continuously. The four leds on the Wiimote will flash.
perspex_wii_permanent_on.png
  On your PC, go Start > Settings > Configuration Panel > Bluetooth > W: Bluetoot-devices > B: Add > W: Add
  Bluetooth Device Wizard > Check 'My device is set up and ready to be found' > B: Next > Swinging Torch icon ...
  wait... device is added: NINTENDO RVL-CNT 01.
  Select the NINTENDO RVL-CNT 01; it becomes selected > Next > Check 'Don't use a passkey' > Next > W: Add
  Bluetooth Device Wizard > B: Finish.
  Popup messages appear: Found New Hardware. The Wiimote has been found, proving the BT dongle is working.
  The 4 LEDss keep on flashing. In some cases only one LED flashes. Both are fine.
  The window 'Bluetooth Devices' is still open. While you are here, you can do a necessary job of which the result is
  needed later on: obtaining the MAC (Media Access Control) address. It's a unique identification number that is
  given to a device in a network.
  In the 'Bluetoot Devices' window, select the NINTENDO RVL-CNT 01 > B: Properties > W: NINTENDO RVL-
  CNT 01 Properties.
  There you find the MAC address. It will be something like this example: Address: 00:21:bd:a4;07:ad. Your
  Wiimote's MAC addrwss will differ from this example.
  NOTICE: the letters are in lowercase here. Later on, you will use the MAC address with letters in UPPERCASE,
  thus the example above will read: 00:21:BD:A4;07:AD.
  The MAC address cannot be cut and pasted, so write the MAC address on a piece of paper and double check if it's
  correct. Wiiscan will not work if the address does not macth with the device.
To check your work, perform the above test and click here
  Help is given by Carsten Frigaard in his CHANGEINGBTSTACK.RTF document, found in C:\wiiscan\doc\. Below
  is a copy of the text. It's layout is slightly edited for browser viewuing:
[From http://forum.eeeuser.com/viewtopic.php?id=38533]
[Manufacturer]
  [Azwave.NT.5.1]
  BT253= USB\Vid_0b05&Pid_b700
  Here are some more links, without guarantees. More tips on USB Bluetooth welcome.
  NOTICE: We experienced no problems with 2 'off the shelf' BT dongles.
         [quote] This got me to thinking if it would be possible to make my Ambicom dongle work with the Microsoft
         Bluetooth stack. After uninstalling the Widcomm drivers I was using and rebooting I found Windows would
         detect the Bluetooth adapter but complained that it did not have a suitable driver to support it. Fortunately
         with a bit of Googling, I was able to find a way to make it work simply by altering the contents of the
         Windows bth.inf file. The info here at Jon’s Guides was pretty helpful to putting me on the right track. To
         make it work you simply need to add the applicable hardware IDs to the list of supported devices. Once this
         is done Windows will detect the adapter correctly and load the Microsoft Bluetooth stack. After the drivers
         are installed Bluetooth support is ready to use – in my case after bonding my Nokia 3650 phone to my PC
         (using the included wizard) I was able to fire up Nokia’s PC Suite and everything worked automagically.
In case anyone is curious here is how I edited the bth.inf file to support my Ambicom adapter:
            1. determine the hardware ID of your adapter. This can be done by clicking on the device in the Windows
               Device Manager and selecting “Hardware IDs” from the Details tab. My Ambicom device had a
               hardware ID of: vid_0bdb&PID_1002
            2. [empty, DS]
            3. once you have determined the hardware ID locate the bth.inf file and make a copy of it
            4. open up the copy in an editor and scroll down to
            5. the Device section
            6. select one of the headings (I placed mine under [Belkin.NT.5.1]) and paste in the following:
                  ; AmbiCom Support
                  Erickson Bluetooth Adapter= BthUsb, USBVID_0BDB&PID_1002
               I named it as an Erickson Bluetooth Adapter since the chipset in my dongle appears to be made by
               Erickson.
            7. Save the file
            8. Update the dongle drivers to use your newly edited inf file. If all goes well it will detect and install the
               adapter.
            9. Enjoy a working Bluetooth stack :)
         [/quote]
         Our Belgian colleagues Kurt Dossche and David Braet (http://digitaleschool.be) mailed us:
         When you have a laptop that has a built in BT dongle and
         an already installed driver (or a dongle with Xp-driver),
         this could be a workaround for problems:
  [1] The cocluding remark is from Harsh J: "P.S. Next time, don’t buy a cheap hardware [...]. Its better and easier to
  use a known and popular device even if they cost a few bucks extra. Or you can consider going in for Ubuntu OS
  rather".
  We followed his advice and did not use a cheap USB 2.0 adapter card but bought a Belkin USB 2.0 Hi-Speed PCI
  card.
  2.3 Software
  For the USB power module and Wiiscan to work, you need Windows XP Pro/Home, Vista or W7 with at least
  Service Pack 2 and .NET Framework version 3.5 SP1. To check if the OS has these components, proceed as
  follows:
  Go Start > Settings > Control Panel > System > W: System Properties > T: General.
  You should see under 'System' a line: 'Service Pack 2'. Of course Service Pack 3 is also fine. Upgrade to at least
  SP2 and get all bugfixes and patches from MS. This can take a lot of time.
  The directory might be empty, or you might see directories like: v1.1.4322, v1.0.3705, indicating the .NET
  Framework versions already installed on your OS.
  Go to the MS site and download a version of .NET Framework 3.5 SP1 or abopve. Obey to MS rules. After
  downloading and installing, check if the version is properly installed by typing in the address bar in Explorer:%
  systemroot%\Microsoft.NET\Framework
  Update your OS if necessary before proceeding any further with this project.
  NOTICE: We upgraded to .NET Framework Version 3.5 SP1.
  You also need the Wiiscan program and the pen software. These are discussed in the next section below and section
  6.6 Basic pen software. Do not install that software now since a basic pen version is already in Wiiscan. The
  installation of the right version of the pen softwar is discussed in section 13.1 IRpen
  2.3.3 Wiiscan
         Download and install the Wiiscan software and documentation from Mergeit. Go to http://mergeit.dk/open-it/
         projekter/egne/wii/ and download wiiscan-0.9-release-2.0.zip. This is the latest known version (July 2009).
         You can also downoad from http://wyxs.net/downloads/whitebaord/. Save the file, for example in C:\
         Unzip the wiiscan-0.9-release-2.0.zip file, for example in C:\. Rename the directory, omitting the quotes, in
         'wiiscan' to reduce typing later on.
The unzipped and renamed directory contains the following directories and sub-directories:
  C:\WIISCAN>tree /f
  Map PATH-lijst
  The volume number is 4A69-73E7
  C:.
  +---redist
  ¦       usbiods.inf
  ¦       usbiods.sys
  ¦
  +---src
  ¦   ¦   wiiscan-0.9.zip
  ¦   ¦   wiimotelibpoll-0.9.zip
  ¦   ¦   wiiscantray-0.9.zip
  ¦   ¦
  ¦   +---wiimotelibpoll-0.9
  ¦   ¦   +---wiimotelibpoll-0.9
  ¦   ¦       ¦   WiimoteWhiteboard.sln
  ¦   ¦       ¦   wiimotelibpoll.csproj
  ¦   ¦       ¦   Form1.cs
  ¦   ¦       ¦   Form1.Designer.cs
  ¦   ¦       ¦   wiimotelibpoll.cs
  ¦   ¦       ¦
  ¦   ¦       +---Properties
  ¦   ¦               Settings.settings
  ¦   ¦               Resources.Designer.cs
  ¦   ¦               Settings.Designer.cs
  ¦   ¦               AssemblyInfo.cs
  ¦   ¦               Resources.resx
  ¦   ¦
C:\WIISCAN>
  NOTICE: The tree is boringly long, but in several directories you can find documentation! So it's a good idea to
  unzip all directories.
(top)
         Wiiscan_sch.pdf is the schematic of the USB power module that powers the Wiimote via the PCs USB port.
         The schematic is based on basic research by Carsen Frigaard from Mergeit. His work is adapted and
         engineered by Niels Kooy.
USB_power_module_schematic.png
         Discussion of schematic:
         Via the USB data connection, the Delcom microcontroller (U2) gets data, and translates the comamndos
         from Wiiscan to an on/off signal. This signal is fed to the gate of the P-channel MOS FET transistor (T1)
         which is the real switch that turns the power to the Wiimote on/off.
         In the schematic the gate of the P-channel MOS FETtransistor (T1) is permanently pulled-up to 5 Volt by the
         resistor (R3), so the Wiimote gets no power and the LED (D1) is off.
         When 0 Volt is set to G(ate) by U2, the P-channnel MOS FET (T1) switches on and 5 Volt goes to the
         LM317 voltage regulator. When 5 volts is set to G(ate), the P-channel MOS FET switches off and 0 volt goes
         to the voltage regulator (U1).
         U1 is an adjustable voltage regulator. With two resistors R1 and R2 the output voltage is set. The formula to
         determine the resistor values for the output voltage is:
         Vout = 1.25 * (1+R3/R4). In this case: 1.25*(1+680/560) = 2,77 Volt.
         NOTICE: In later models pin 1, 2 and 3 are connected as well as pin 4, 5 and 6, due to power loss. See also
         the 3.5 Cables section.
Wiiscan_pcb.pdf is the printed circuit board and solder mask for the wiiscan_sch.pdf schematic.
USB_power_module_solder_mask.png
USB_power_module_pcb_side_a.png
USB_power_module_pcb_side_b.png
         Wiimote_pwr_sch.pdf is the schematic for the power connection of the Wiimote inside the battery
         compartiment. The Wiimote is powered via a plain Cat 5 nework cable with two RJ11 (6P6C) connectors.
         See also section Cables
wiimote_power_schematic.png
         Wiimote_pwr_pcb.pdf is the printed circuit board and solder mask for the powering inside the Wiimote
         battery compartiment. This small printed circuit board serves to hold the clips that power the Wiimote.
         NOTICE: In later models pin 1, 2 and 3 are connected as well as pin 4, 5 and 6, due to power loss. See also
         the 3.5 Cables section.
wiimote_power_solder_mask.png
wiimote_power_pcb_side_a.png
wiimote_power_pcb_side_b.png
  NOTICE: In later models pin 1, 2 and 3 are connected as well as pin 4, 5 and 6, due to power loss. See also the 3.5
  Cables section.
  In the next section you find the electronic parts list for the USB power module and the Wiimote.
  Wiimote
  The powering inside the Wiimote has no electronic parts, it just contains:
  You also need some glue to fix the RJ11 (6P6C) connector to the battery cover. The place of J1 is rather critical.
  See picture and measures below.
  C1                 1     4,7 uF
  C1, C2, C5         3     100 nF
  C3, C4                 2   22 pF
  C6                       1   1uF, 16 Volt
3.3 Components
USB_conectors.png
PDIP-18.jpg CY7C63723.png
BS250.png
LM317.jpg
symbol_led.jpg
diy-kit.png
  A picture of the battery lid of the Wiimote. The place of the holes is rather critical, specially the hole for the cable
  because its distance is determined by the clips that replace the batteries. The RJ11 hole measures 12x13 millimeter.
  The hole for the ball head ceiling mount is 7 millimeter.
  The RJ11 connector is glued to the battery lid.
wiimote_power.png
battery_lid_outside.png
battery_lid_inside.png
What you have constructed, when built from sratch, could look like:
pcb_ready.png
         Do not solder the chip directy on the PC board but use an 18 pins PDIP (Plastic Dual Inline Package)
         connector.
         Transistors are heat sensitive. Use a pair of tweezers to conduct the heat to during soldering.
         Be careful with the BS250. Reversing the source and drain will probably result in a blown up transistor.
         Be patient.
  3.5 Cables
  Two cables are used for this project:
  - To feed and send data to the power module, a plain USB2 A B cable is used.
  - Powering the Wii is done with two RJ11 (6P6C) connectorsors and plain Cat 5 networking cable. 2 wires of the
  cable are not used. Wiring:
  The wire colors are not important, nor is the wiring between 1 and 4 etc. In the Wii and the power module 1, 2 and
  3 are connected as well as 4, 5 and 6.
  NOTICE:
  Since 2009 we use plain networking cable with 8 pn RJ 45 connectors.
         Is everything corecctly conneced? Are you sure? Please check and double check. It's not a bad idea to have
         someone else inspect your work. She might have a fresh view on the matter.
         Meticuously inspect the printed circuit board for solder spikes and accidentally connected copper lanes.
         Test the input voltage on the USB side. It shoudl be around 5 Volt.
         Do a simple test. Remember, the BS250 switches the power on/off. When 0 Volt is set to G, the BS250
         switches ON and 5 Volt goes to the LM317.
         Bear in mind that D (drain, pin 2) is permanently connected to 5 volt via a 10 K resistor, so the LED should
         be off.
                 Connect the printed circuit board to the PC. Power on the PC. The LED should stay OFF.
                 Connect D (drain, pin 2) to GROUND. The LED should light.
                 When the LED is on, 5 volt goes to the LM317 voltage regulator.
                 With a voltmeter, check the output voltage of the LM317. It should be around 2,77 to 2,85 Volt,
                 depending on the precision of the resistors used.
         If necessary, remove the battery lid from the Wiimote.
         Connect the RJ11 cable between the USB power module and the Wiimote.
         Check if the polarity is correct on the battery clips.
         Unpower the board.
         Before you insert the microcontroller in its socket, ground yourself and your desktop in order to prevent static
         electricity ruiining the microcontroller.
         Observe the notch on the chip and the notch on the socket and carefully insert the chip in the socket. The
         pens are fragile.
         Ready!
  Close the USB power module enclosure and take a break. After the datasheet section below we will test the USB
  power module with the Wiiscan software.
  3.7 Datasheets
  wiihardware.pdf. This is Carsen Frigaards description of his USB power module schematic. One might wonder why
  we did not simply copy his schematic. The reasons is that we wanted all parts to be as simple as possible and
  enlarge the availability of parts. One part was difficult to get in the Neterhlands, so we expected similar problems
  elewhere.
  - CY7C637xx.pdf. Datasheet for the CY7C637xx microcontroller
  -BS250.pdf. Datasheet for the BS250 P-Channel MOS FET
  -LMx17.pdf Datasheet for the LM317 voltage regulator.
(top)
  Before we can use the USB power module and Wiiscan, we have to determine which Delcom microcontroller
  version is used in the USB power module. Is unlikely that it's a Delcom 'Generation 1' with part number 802370. If
  it is the case, then it will need a dirver.
  When a Delcom 'Generation 2' with part number 902370, it is a 'Generation 2' micro controller which does not need
  a driver.
         Generation 2:When inserting the USB cable from the USB power module in the PC, you just hear the 'Dong
         ding' sound. The new hardware is automatically detected. This is the normal condition. In the power module
         is a Delcom 'Generation 2' microcontroller with Delcom part number 902370. Skip step 2 below and proceed
         with the next one: 'Testing the USB power module'.
         Generation 1: When inserting the USB cable from the USB power module in the PC, you get a text balloon
         'Found New Hardware' and the window 'Found New Hardware Wizard' opens, asking you to install the
         driver.
         So it's the 'Generation 1' micro controler, Delcom part no. 802370 is in the USB power module. This chip
         works us just as perfect but needs a driver. This is no problem. Please a proceed to the next section.
     1. We assume you are still on the window: New hardware found. Check the 'No, not this time' option and click
        [Next].
     2. In the next window, you check 'Install from a list or specific location (Advanced)'. Click [Next].
     3. In the next window, the option 'Search for the best driver in these locations' is already checked. Also check
        'Include this location in the search'.
     4. The [Browse] button becomse selectable. Click [Browse].
     5. The 'Browse for Foler' window opens. Navigate to C:\wiiscan\redist\.
     6. Click 'redist'. The [OK] button becomes visible and is clickable.
     7. Click the [OK] button. The window closes.
     8. Window: Found New Hardware Wizard: the location is specified: C:\wiiscan\redist. Click [Next].
     9. Window: Wizard new hardware found: Hardware Installation: the 'Delcom USB IO Dirver' is found.
    10. Also the Window 'Hardware Installation' opens. You get a warning that the driver does not meet the
        Windows Logo specification. Ignore the warings to end the installation and click [Continue Anyway]. The
        window closes.
    11. Window: Found New Hardware: The installation of the soteware for the following device is finished.
        Delcom USB IO driver. Click [Finish].
    12. You get a text balloon 'Found New Hardware'. The new hardware is installed and can be used.
    13. As usual, reboot.
  Check your installation by going: Start > Settings > Control Panel > System > W: System Prperties > T: Hardware
  > B: Device Manager > Universal Serial Bus Controllers > +. You should find a line with 'Delcom USB IO Driver'.
  The driver for your USB power module is successfully installed.
  NOTICE: When you have the normal distribution of the USB power module, you have a Delcom chip with part
  No. 902370. This 'Generation 2' chip needs no driver and installation is not necessary.
  Before you can test the USB power module, you have to initialize wiiscan to use the Delcom microcontroller. This
  is done by editing the wiiscan initialization file. The file is located in C:\wiiscan\bin\Release and it needs
  'option 3'. Use Notepad to edit the initialization file. Browse trough te file to get familiar with it. The % sign
  indicates that the line is either a comment, or an option that is commented out, i.e. not working.
  Proceed as follows to edit wiiscan.ini:
         % 0=no power cycle, 1=USB hub control, 2=USBm IO, 3=USB Devcon
         option_usbpowermode=0
         In the line option_usbpowermode=0, change the 0 (zero) into 3 (three). Save your work.
         Check your work by opening the file again and look for:
         % 0=no power cycle, 1=USB hub control, 2=USBm IO, 3=USB Devcon
         option_usbpowermode=3
  4.4 Testing
  In the previous steps the version of the Delcom microcontroller was established and eventually a driver was
  installed. Also wiiscan.ini was edited to use the Delcom microcontroller.
  Now we can test the USB power module. Proceed as follows:
Great! The USB power module functions correct. If its not working, go to the next section.
4.5 Problems
  What to do when the LED does not light. There is little help we can offer here. Just a few
  hinst and questions in the hope it helps:
(top)
  In a previous section the USB power module was tested. In this section the Wiimote is
  attached and tested. To perform the test we have to tell Wiiscan which Wiimote to use by
  editing the MAC (Media Access Code) address in wiiscan.ini. You alredy noted the MAC address
  on a piece of paper when you were in section USB Bluetooth dongle test
1. Open the wiiscan.ini file again with Notepad and look for the lines:
You are now ready to connect the Wiimote to the USB power module.
  5.2 Connecting
  If necessary, remove the batteries, replace the lid and connect the Wiimote to the USB power
  device with the cable with the two RJ11 6P6C connectors. At this point you have everything
  connected. The Wii has its buttons 1 and 2 continuously presed with a piece of plastic and a
  tie-wrap. See section 12.. Wiimote for details.
perspex_wii_permanent_on.png
  5.3 Testing
  The basic test is the same as with the USB power module. We assme you have done the pevious
  test and the USB power module functions.
  Great! Both the USB power module and the Wiimote get power. We now can make use of all the
  fine features of Wiiscan.
  5.4 Problems
  Reported problemss:
          LED on USB power module lights up but the LED's on the Wii stay off
          . Is the cable really working? Carefully open the battery lid on the Wii. Prevent
          bending the battery clips.. With a volt meter, check if power is on the battery clips
          when the USB power LED is on. You should measuere something between 2,8 and 3 volt. If
          this is tindeed the case, the clips do not make contact to wii. Inspect and if
          necessary, carefully bend the clips.
          Close the cover by laying the cover on the Wii in such a way that the front side and the
          back side lay almost flat on the Wii, but without the two tips on the front side of the
          lid in their holes. Shift the lid backward, let the clips slide in their holes and
          carefully press the backsiide of the lid, thus closing the cover.
          Broken cable/connections?. Are the connectors well crimped? Check able.
          Typo in MAC addressThanks to Kurt! The typo results in: you can switch on the LED in the
          power module (with wiiscan -usbup), but the 4 LED's on the Wii do not blink. Remember
          that the letters in the MAC address must be in UPPERCASE.
(top)
  6. Wiiscan
  In the previous two sections the USB power module and the Wiimote were tested for powering
  capabilities. We now take up the final steps: connecting and fine tuning. First we discuss
  some files, and finally a small section about problems.
  6.1 WIISCAN_manual
  This is the best starting point, in other words RTFM (Read the Fine Manual)
wiiscan(1) wiiscan(1)
   NAME
            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
         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.
                     being careful that the pattern matches only our USB hubs!.                You
                     can test this by
           NOTE: be careful of connecting other devices to the USB bus, since                  the
           power cycle may cause severe interfere with the device.
             -c <device>
                    connects to a device.
             -d <device>
                    deletes a device, clears HID and bluetooth registry entries.
             -usbdown
                    turn the USB hub off.
   OPTIONS
             -cf <file>
                    load a specific configuration file.
             -lf <file>
                    specify a distinct logfile.
             -b <sleep>
                    auto-mode bluetooth connection sleep in milliseconds.
             -t <sleep>
                    bluetooth scanning interval in milliseconds.
             -u <sleep>
                    auto-mode USB connection sleep in milliseconds.
             -p <sleep>
                    automode usbm post-connection sleep in milliseconds.
             -w <sleep>
                    timeout for wiimote in milliseconds.
             -q <usbradio>
                    use bluetooth radio with this address. Note, this functionality
                    is not working yet.
             -f <removemode>
                    pre-remove   mode of device, 0=remove                if   not   connectable,
                    1=always remove, 2=never remove
            -l <wiilibrary>
                   use    specific    wiimote            library,     lib     can     be     one-of
                   (wiiuse,wiimotelib).
   FILES
           wiiscan looks for a file names wiiscan.ini when executing in the auto-
           mode. See detail in the file.
   TIMING
         Various timing parametes can be set                    on the command line or in the
         inifile. The process of connecting is
4: USB power up
   EXAMPLE
         Scanning for devices nearby:
wiiscan -s
   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
         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
         (without build-in bluetooth) with a Trendnet TBW-102UB bluetooth don-
         gle, and on a ASUS eeePC 1000H with XP home.
            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
                   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)
                   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
                   wants to reboot the PC. Small fix: just delete the device and
                   re-run "wiiscan -c nintendo".
                     Pressing one button only "1" or "2" makes the wiimote blink for
                     a short time, but it is not really discoverable.
            8; balloon-tips (FIXED)
                   Balloon-tips are annoying when connecting new               hardware.     Small
                   fix: do
                      [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVer-
                     sion\Explorer1]
                      "EnableBalloonTips"=dword:00000000
                     DeviceAutoClose<HBLUETOOTH_DEVICE_FIND,BOOL> hbf(BluetoothFind-
                     FirstDevice(&bdsp,&bdi),&BluetoothFindDeviceClose);
   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.
(http:www.wiiuse.net/)
Wiimote Whiteboard
(http:support.microsoft.com/kb/311272)
   VERSION
         Version 0.9 NDEBUG
   AUTHOR
         Carsten Frigaard,          Mergeit    ApS,    Kongsvang    Allé 37, DK-8000 Århus C,
         www.mergit.dk
   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.
  6.2 WIISCAN -H
  Below is the output of
wiiscan -h
  C:\WIISCAN\BIN\RELEASE>wiiscan -h
  Usage: WIISCAN <-a | -c | -d | -r | -s | -usbup
  | -usbdown> [-cf ] [-lf ] [-b ] [-t ] [-u ] [-p ] [-w ] [-q ] [-f ]
  [-m ] [-l ] [-y] [-wb] [-v]
    VERSION: 0.9 NDEBUG 32BIT LITENDIAN
    modes:
      -a : autoconnect to device
      -c : connect the device, that matches this name
      -d : deletes the device, that matches this name
      -r: lookup and list bluetooth radio devices
      -s: scan external bluetooth devices
      -usbdown: disable usb hubs
      -usbup: enable usb hubs
    options:
      -cf : specify a distinct configurationfile, default=wiiscan.ini
      -lf : specify a distinct logfile, default=cout
      -b : automode bluetooth connection sleep in milliseconds,
                              default=2000
      -t : timeout for bluetooth stack in milliseconds, default=2000
      -u : automode usb connection sleep in milliseconds, default=500
      -p : automode usbm post-connection sleep in milliseconds,
           default=3000
      -w : timeout for wiimote in milliseconds, default=2000
      -q : use bluetooth radio with this address (not working),
           default=any device
      -f : pre-remove mode of device, 0=remove if not connectable,
           1=always remove, 2=never remove, default=0
      -m : choose USB powercycle mode, 0=no power cycle, 1=use USB
           hub, 2=use USBm IO hardware, 3=use USB Delcon IO hardware
C:\WIISCAN\BIN\RELEASE>
  6.3 Wiiscan.ini
  For lay out in a web page we show the content of wiiscan.ini slightly modiefied. The % sign
  indicates a comment line; it's not code.
  % Configfile_begin
          % config file for wiiscan
           % launching exe file have a problem with spaces, hence renamed exe,
       % replaced space with underscores
           % The original Johnny Chung Lee wb software version 0.3, downloaded
       % from [http://johnnylee.net/projects/wii/]
                   % whiteboard_software="d:/WiimoteWhiteboard/WiimoteWhiteboard_v0.3.exe"
           % same stuff, but binary build from sources and redistributed in this
       % package
                   %whiteboard_software="WiimoteWhiteboard.exe"
            % wiiscan parameters
                    %option_device="Nintendo RVL-CNT-01"
option_startwhiteboard=1
             % 0=no power cycle, 1=USB hub control, 2=USBm IO, 3=USB Devcon
                     option_usbpowermode=0
             % wiiscantray options
                     % number of connection attempts before autoscan i restarted
                     option_tray_pool_retries=2
             % final connection step reqires some sleep before windows PnP is ready
                     option_sleep_before_final_connect=1500
When editing this file it is recommended to write slashes the Unix way i.e. '/' (omit quotes).
  6.4 INSTALL.rtf
  We simply follow Carstens INSTALL.rtf in C:\wiiscan\bin\Release. We added notes in the text
  between square brackets.
INSTALLATION
Version: 0.9
Prerequisites
Running
     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.[6]
  ENJOY
   Mar 26 2009
   Carsten Frigaard,
   MergeIt ApS, Kongsvang Allé           37,   DK-8000
   Århus C, www.mergit.dk
  Mr. Ferri also suggests other ways of disableing error reporting and here is another good
  link: http://www.windowsnetworking.com/articles_tutorials/Disable-Error-Reporting-Windows-XP-
  Server-2003.html. Experiment with the settings until you have only disabled whiteboard stuff.
REGEDIT4
  [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PCHealth\ErrorReporting]
  "AllOrNone"=dword:00000001
  "IncludeMicrosoftApps"=dword:00000001
  "IncludeWindowsApps"=dword:00000001
  "IncludeKernelFaults"=dword:00000001
  "DoReport"=dword:00000000
  "ShowUI"=dword:00000000
  6.5 Wiiscantray
  Wiiscantray is the ideal program for a busy teacher in a classroom. It permits her to just
  'press the button' and, about 60 to 90 seconds later, to have her digital interactive
  whiteboard fully operational.
  This is done by having a shortcut to wiiscantray.exe in the Start Menu or on the desktop.
  After powering up the PC, wiiscantray is automatically executed. It powers up the Wiimote and
  establishes teh Bluetooth connection between the PC and the Wiimote.
  When you have made the shortcut to Wiiscantray.exe, either on the desktop or in the Start
  Menu, and the USB power module and the Wiimote are started with wiiscantray.exe, you find the
  icon in the taskbar notification area and you find the pen software on on the desktop.
  % and finally, a custom build v0.3 version, with fixed calibration.dat write
  whiteboard_software=WiimoteWhiteboard_v0.3.exe
  When you look around in wiiscan.ini, you see other whiteboard IR pen software versions,
  located in D:\. This gives you an indication how you can put your version of the IR pen
  software on the PC. This subject is further elaborated in section 13.1 IR pen software.
  Many thanks for you feedback, let me see if I can help you. The
  logfile points me in the direction of either an undetected
  Bluetooth radio (adapter) or missing bluetooth link to the wiimote.
> wiiscan -r
> wiiscan -s
The error
  means that the software does not detect any bluetooth devices, the
  scan function ("wiiscan -s") should reveal any nearby devices and
  list them. You could try to put the wiimote into "discover" mode by
  pressing the "hard-sync" button (the internal red button) and then
  running "wiiscan -s".
  You should then be able to see an wiimote adr. and perhaps the
  "Nintendo" name of the mote.
allowed_wiimote_adr = 00:00:00:00:00:00
  This would allow wiiscan to find devices based on adr. and not on
   names only, and this mode is far more robust, when scanning for
  motes (the name part in the BT protocol takes a long time to
  transfer, and is in some cases missing when scanning....)
         A version of Boon Jin Goh's pen software always give a .NET Framework error when started
         via Wiiscantray and the path in wiiscan.ini. When pressing 'continue' in the error, BJ
         starts, but does not work properly. When starting BJ manually, no error.
         SOLUTION 1:
         There is a simple solution to most problems: create a batch file, for example c:
         \wiiscan.bat with the following content:
NOTICE: We prefer the batch file below which gives even better resutls.
         SOLUTION 2:
         Below is another, better way to start the whiteboard.
         The first line kills the pen softeare. This is necessary in case of a second start of
         the batch file and prevents the existence of two or more instances of the Somoothboard
         prgromgram. For command line options type taskkill or see http://www.microsoft.com/
         resources/documentation/windows/xp/all/proddocs/en-us/taskkill.mspx?mfr=true.
         The second line starts wiiscan from the command line; that is without using wiiscantray.
         For command line options type start /? or see http://www.microsoft.com/resources/
         documentation/windows/xp/all/proddocs/en-us/start.mspx?mfr=true .
         The third line executes the wait program with a pause of 30 seconds. This pause depends
         on the PC used. For command line options type wait -h .
         And the fourth line starts the pen software..
         Below is a batch file for a school that has many whiteboards, each with its own
         wiiscan.ini file. All programs are stored in the P: share on the server and in
         SABRINE.BAT the specific workstation name is stored.
         NOTICE:
         Sometimes even 90 seconds is too short. When Windows, or any other program starts
         looking for updates, or performs any other action, it is possible that Wiiscan is unable
         to start and the process is interruped, resulting in an .
         For this reason it is best to disable automatic updates by Windows and other programs.
         On a href="http://support.microsoft.com/kb/306525 is described how:
         Turn off Automatic Updates
         If you want to turn off the automatic updates, follow these steps:
           1. Click Start, click Run, type sysdm.cpl, and then press ENTER.
           2. Click the Automatic Updates tab, and then click to select Turn off Automatic
              Updates.
           3. Click OK.
         When you put wiiscan.bat in the Start Menu, everything works by just switching the PC on
         and logging in. Of course you can also start some application with this batch file.
         All programs, 'Wiiscan', 'wait' and 'WiimoteSmoothBoard' can be found on http://
         wyxs.net/downloads/whiteboard/. See also section 13.1. IR pen
(top)
  An abundance of infra red pens can be found on the Internet. Ready made, as well as do-it-
  yourself projects. A comprehensive how to on making an infra red pen for about € 4,-- can be
  found on http://wyxs.net/web/wiimote/digital_whiteboard.html.
  In a year of experimenting, we have gained some experience with infra red pens. Here is our
  humble opinion:
     1. The best infra red pen looks like a normal pen, feels like a normal pen and performs
        like a normal pen.
     2. When lightly pressing the tip of the pen to the whiteboard surface, an internal
        momentary switch should put the LED on.
     3. Manually operated switches make cheap pens, but are not easy to use.
     4. A 1,5 Volt battery, type AA or AAA, is the best power source. It's available everywhere
        and cheap.
     5. Use a VISHAY TSAL6400 high-power infra red LED. It has the right wavelength, lightning
        angle and power.
  At this moment our school uses 'The Groove' from http://www.irpensonline.com/. A reasonable
  good pen. Not so good on the first point in the list.
(top)
  8. Whiteboards
  There are a lot of possibilities to get a whiteboard which is both a good projection surface
  and a good writing surface for an IR pen and being able to write with felt markers (both for
  whiteboards and 'normal' makrers which are sometimes accidentally used). We looked at
  reflective properties, ease of cleaning, cost effectiveness and last but not least the 'hot
  spot, which is exmplained at http://en.wikipedia.org/wiki/Projection_screen.
                                                      blackboard.jpg
  The blackboard at about 13.00 PM.
whiteboard_ready.jpg
  It took about an afternoon to make this whiteboard. The teachers like this one because they
  can still use the chalkboards left and right, fold them to use the backsides and have a
  perfect projection surface, that is easy to clean, even when someone uses the wrong felt
  makrker.
  8.1Melamine
  We started our experiments with a chipwood board, covered with a Melamine layer, costing about
  € 11,-- (eleven) for a size of 244 x 122 centimeter. We just put it in front of the classical
  green blackboard. For testing purposes it's a perfect and cheap solution. Advantages: very
  cheap, reasonable reflective qualities and hot spot, can be sawn to any size.
  Disadvantages: a bit difficult to cean. Do not use an abrasive (Jiff). A mild detergent will
  do. One can expect the Melamine layer to become thin over time, requiring replacement of the
  board. We do not use this solution any more.
  RESOPAL
  A HPL from 'Resopal' (white-dull No. 0179-20), costing about € 15 to 20 per m2 including VAT.
  Available in 365 x 132, 305 x 132 and 218 x 102 centimeter, thickness 0,7 millimeter. No hot
  spot, very good projection quality. Cleans well, see 8.2.1 Cleaning HPL below. This is a very
  good surface.
  DUROPAL
  Duropal (No. W400 SM). Very good projection quality and no hot spot, cleans like a blackboard,
  see 8.2.1 Cleaning HPL below.. Maximum size 410 x 130 centimeter, thickness 1 millimeter.
  Price per m2 including VAT around € 16. This is up till now (december 2011) the best non-
  magnetic surface.
  HOMAPAL
  We found Homapal (No. 8217). A magnetic HPL. The magnetic layer is an advantage of this
  brand, but it has a bit of a hot spot. Maximaum size 305 x 130 centimeter, thickness 1,1
  millimeter. Price inc. VAT per m2 around € 40. Cleaning, see 8.2.1 Cleaning HPL below.
  HPL can be cleaned with hot water and common non abrasive household cleaners. The only
  precaution: avoid using strong acids and bases (adapted from: http://www.arpausa.com/hpl_arpa/
  _pulizia.asp).
  When you accidently have used a permanent felt marker, you can remove your writing with a
  whiteboard marker and hot water.
  On http://www.skovby.dk/showpage.php?lang=NL&pageid=7031526 is a Danish, English and German
  extensive PDF document on maintenance. Also available here
  Duropal gives cleaning instructions on http://duropal.b-onweb.de/care-cleaning
  8.3Enamel
  These boards are made of a layer of enamel on a sheet of metal. This is the 'whiteboard' as
  most of us know it.
Advantages: easy to clean, small magnets can be used to attach paper etc. to the board
  We tested an example from Smit Visual Supplies who claims excellent reflective and hot spot
  properties. Reflective properties are good, but the dull enamel coating produces a rather big
  hot spot; bigger than those of HPL and the EGAN foil below.
  8.4Paint
  Whiteboards based on a hardened paint on steel exists. We have no experience with this type of
  whiteboard. Please send us an example.
  Advantages: excellent reflection and low hot-spot, easy to clean, can be cut to any size
  (maximum length 32 meters(!)x 137 centimeters). Disadvantages: VERY expensive, 2 x 1 meter is
  about € 400 (four hundred euro), not that classroom resistant. Our first board produced a few
  tiny and almost invisible air-pockets. This was due to the material we attached the foil to.
  When using a chipwood or MDF board you get a flat surface.
  OUR CONCLUSION:
  Duropal and Resopal are our favourites.
(top)
  9. Speakers
  Simple speakers are good enough. Hi-Fi quality is not needed even not desirable. The low
  frequencies in the audio spectrum lessen the intelligibility of the sound.
  We have now about a year experience now with the built in speaker in our short throw beamer
  and we absolutely prefer this way of working over separate speakers. The sound volume is
  controlled with the beamers remote control.
(top)
wiimote_ceiling_mount_SEC-BRACK50.jpg
wiimote_ceiling_mount_SAC-BRACK50_pieces.png
  ... and easily extended when the classroom has a high ceiling. Go to an ironmonger and buy an
  'extended nut', diamter M8 (8 millimeter).
extended_nut1.png
Also buy a meter of M8 thread bar (is that the correct name?). Total costs about € 3.
If you want, you can cover the thread with a chrome pipe.
video_projector_ceiling_mount.gif
They sell between € 30,-- and € 50,-- inc. VAT, depending on quantity.
         Short throw beamers are better for teachers and pupils. Manufacturers of projectors, in
         their user guides, warn not to look into the prjection lamp. That's clear language. In
         several countries it's forbiden for teachers and pupils to look into the vidoe projects
         lamp.
         When you want an old fashioned projection setup, no whiteboard interaction, no pupils
         presenting in front of the whiteboard, then take an old fashioned projector with a long
         throw lens.
         The resolution should be at least 1024 x 768 pixels.
         Do not be impressed by the number of ANSI lumen, but test projection qualities in the
         classroom, with the whiteboard, in the expected lightning conditions, to see if the
         projector produces eneough lumen for your purposes. Remember that how bigger the screen,
         the more light is needed.
         In a bright well lit classroom, is there some kind of darkening or dimming the light?
         Opt for a maintenance free projecor. Some have filters that need regular cleaning. And,
         once every few months cleaning a projector, standing on a ladder, is a risky task for a
         teacher.
         How long is the expected life time of the lamp? And how much costs a new one? And can it
         easlily be replaced by a teacher?
         Projectors can be noisy. Test for silence, or the lack of it.
         We like projectors with a VGA in- and output. In a classroom you also need a normal
         monitor and the return signal from the projector is used for the monitor on the PC. If
         your projector does not have a VGA output, buy a good quality VGA splitter. Cheap ones
         may produce low image quality.
         Built in speaker or separate speakers? Both have their dis- and advantages. If you use a
         long throw beamer, the sound of a built in speaker does not seem come from the screen.
         Aspect ratio. Do you want to continue using the old 4:3 aspect ratio or the new 16:9?
         Can the projector and the monitor handle the new aspect ratio? Testing might be
         necessary before drilling, cutting and sawing.
         Our blackboards measure about 2 x 1 meter which has some resenmblance with the 16:9
         aspect ratio.
         ...More tips? Please write.
  We have good experiences with the OPTOMA EX525ST: short throw, maintenance free, built in
  speaker, VGA out.
(top)
  12.1 Whiteboard
  No matter what kind of surface you choose, the place of the whiteboard in the classroom is
  important. The classical blackboard is installed on a place where it can get good daylight.
  In theory that's not the best place for a digital interactive whiteboard.
  Furthermore, the sun radiates a lot of infra red light; direct sunlight on the whiteboard
  might spoil correct pen tracking. Make a calulted guess about what the sun does during a year.
  Curtains or Luxaflex can help to dim the light a bit, but a classroom in the dark harms
  pupil/teacher interaction.
  12.3 Wiimote
  The buttons 1 and 2 need to be pressed permanently. One can use a piece of plastic and a tie-
  wrap or glue. Tape is easy but the risk is that, over time, the button pressure releases the
  tape. So, to your surprise, after hours of looking why your whiteboard is not working, you
  discover that the buttons are no longer pressed enough. Maybe it's a better idea to take a
  piece of white plastic and glue it over the buttons or tighten it with a tie-wrap. Do not
  glue the buttons themselves because glue may leak into the Wiimote.
perspex_wii_permanent_on.png
  The wiimote can be attached to the ceiling via a mount, preferably with a ball head for easy
  positioning the Wiimote to the whiteboard. The middle of the desktop area, the lens of the
  projector and the Wiimote should be in one line if poosible.
  You have to test what is the best location for the Wiimote. Too near the whiteboard increases
  tracking resolution but you risk incomplete coverage of the desktop area and, if you use the
  12 IR sensitive spots, the area around the desktop. Too far away results in low resolution.
  This is demonstrated in http://wyxs.net/web/wiimote/digital_whiteboard.html#h6.1
  Fine tuning the position of the Wii takes some patience and can best be done with 2 persons;
  one behind the PC to start the calibration procedure and calibrating, the other person on a
  ladder to fine tune the position of the Wiimote.
  For calibration you can best use the pen software that has a feature that shows the area
  covered by the IR camera in the Wii and the PC desktop area. The Smooth Board 0.2 BETA
  software has this feature.
  What is the exact distance between the Wiimote and the whiteboard in your classroom?You can
  find it out by trial and error, or do some calculations to get an idea of the right spot.
  Anyhow, before drilling holes, test the found position on the ceiling with the Wiimote.
Thanks are due to work done by Eyucel and Stefan van Aalst.
  The IR camera in the Wii has an aspect ration of 4:3. The camera has a horizontal viewing
  angle of 40 degrees and a vertical viewing angle of 30 degrees.
  NOTICE:
  The caculations below assume the Wii is positoned under an angle of 90 degrees of the
  whiteboard, on the crossing of the diagonal lines of the rectangle formed by the desktop and
  eventual sensitive areas around the desktop, i.e. a test position.
wiimote_distance.png
  The distance of the Wiimote to the screen can be calculated with the following formulas
  where:
  d = distance
  h = total horizontal screen size
  v = total vertical sreen size
      h : 2
  d = ------
      40 : h
       v : 2
  d = ------
      30 : v
  A classroom example: The projected horizontal width of the desktop image on the wihteboard is
  130 cm. We also want a 10 cm area around the desktop as clickable areas. So, the total
  horizontal width becomes 130 + 10 + 10 = 150 cm.
      h : 2          150 : 2             75
  d = ------     d = --------      d = ------     d = 281,32cm.
      40 : h         40 : 150          0,2666
UNDER CONSTRUCTION!!
  An example:
  The screen size horizontal is 130 cm. The result of tan(radians(20))=0.36397
x= (130/2)/0.36397=178.50 cm.
tan(radians(15))=0.267949
x= (130/2)/0.267949=242.50 cm.
  We now can calculate the distance of the Wiimote to a whiteboard when we know the total width
  of the projected desktop and clickable areas. However, bear in mind, the Wiimote is mounted
  to the ceiling, thus projecting downward. So, the IR camera sees a trapezoid like image of
  the desktop, where the bottom of the trapezioid is the widest.
  The cable from the Wiimote to the USB power module can be led over the ceiling if possible.
  The cable is long enough to place the compter where you (or your pupils) need it. The cable
  can also be led to the video prjector mount and led through it's pipe.
  12.4 Speakers
         Where do we want the speakers? In the video projecctor, next to the whiteboard or ...?
         How do we do the volume control? A knob on the speaker, a separate amplifier with a
         volume control, with software on the PC?
         In a claasroom one does not need high-fidelity sound quality; that even undermines
         intelligibility. Generlly cutting off low frequencies improves intelligibility.
  12.5 Cables
  You need quite a few rather long cables. Because they are long, the risks of signal loss and
  noise exist. Buy good quality audio and vidoe cables.
         Where will tha cables lay? In the classroom, via the ceiling, on top of the ceiling
         tiles, ...? It makes sense to find a way to get rid of the cables.
         How long will the cables be?
         It's not a bad idea to have a multi socket extension lead with a on/off switch to power
         everything with one switch. It s saves energy.
         Double sided velcron tape is your friend when tidying up cables and giving your setup a
         final touch.
  NOTICE:
  Observe local electricity regulations concerning earthing the projector, leading cables in a
  cable trough, and separation of mains and other cables.
  12.6 Testing
  No need to say that extensive testing and a try out period are necesary before giving the
  infra red pen to the puils and their teacher.
  12.7 Ready!
  Here is our first setup with an old fashioned video projector with ONSBORD Wii setup http://
  onsobrd.nl and a formica whiteboard.
ONSBORD_1_ready_front.jpg
                                                 ONSBORD_1_ready_rear.jpg
  The projector and Wii on the ceiling
                                                     short_throw.png
  Our other classroom with an Optoma EX525ST short throw projector with ONSBORD (OURBOARD)
  http://onsobrd.nl.
                                               short_throw_high_ceiling.png
  A short throw projecor on a high ceiling.
(top)
  13. Software
  13.1 IR pen software
  We use Boon Jin Goh's Wiimote Smooth Board version 0.2 BETA, dated 13th July 2008. This
  version has enough features, right-click, double-click and 12 clickbable areas outside the
  desktop area are available. Our primary schools need no more.
  You can download the 0.2 BETA version at http://wyxs.net/downloads/whiteboard/, where you
  find Wiimote_Smooth_Board_0.2.zip 02-Jul-2009 06:36 267K .
  NOTICE:
  Use this version when you have tested everything with Boon Jin Goh's Smoothboard version which
  is included in Carsten Frigaard's Wiiscan software.
  When you have everything working with the pen software included in Carsen's Wiiscan you can
  take the final steps: make a 'one click' solution by again modifying wiiscan.ini and creating
  a batch file. Proceed as follows:
  Open Notepad and create a batch file, for example c:\startwb.bat. In it the following
  content:
  Explanation:
  The first line starts wiiscantray.
  The second line gives wiiscan time to start and create the BT connection. Ninety seconds is
  good for our setup; experiment with the time until you have no errors and a reasonable short
  start time. Be aware that Carsten chose the safest connection method, not the fastest.
  The third line starts Wiimote Smooth Board version 0.2 BETA.
  NOTICE:
  Because BJG's software is started with the batch file, the software should not be started
  with wiiscan via wiiscan.ini. To eliminate the starting of board software with wiiscan.ini,
  open wiiscan.ini and search for the line:
  To put this file in the Start Menu, right click on 'Start' > Open > Programs > Startup, and
  move the batch file there. The only thing a teacher has to do is to switch the PC on and log
  in. Of course you can also start some application with this batch file.
  Both programs, 'wait' and 'WiimoteSmoothBoard' can be found on
  Boon Jin Goh's Wiimote Smooth Board is now also available in a paid version as trialware with
  a nag screens. His latest version has lots of features, see http://www.smoothboard.net/home/.
  For these resaons you could use a pointer that is bigger, to improve visibility. When it's
  also poining from a different angle (pointing towards the bottom right corner of the screen),
  we have a better view on the pointer.
  Use 'Icon Edit' freeware and part of 'Icon Suite', created by Mike Bouffler. Google or see:
  http://freewareapp.com/mb-icon-edit_download/. We use version 2.1.9 which enables us to
  create every pointer we want.
         Jarnal: by David K. Levine and Gunnar Teege. From the blurb: "Jarnal is an open-source
         application for notetaking, sketching, keeping a journal, making a presentation,
         annotating a document - including pdf - or collaborating using a stylus, mouse or
         keyboard. It is similar to Microsoft Windows Journal and to the earlier Mimeo
         whiteboarding and Palm notepad applications." Site: http://www.dklevine.com/general/
         software/tc1000/jarnal.htm
         We love this fine cross-platform application. Dutch, German and Italian versions are
         available.
         Below is a batch file that eases starting up Jarnal with options. and makes the command a
         more readablend. For markup reasons Below is a way to make the command more readable.
         Whiteboard V1.0: by Gary Jones. A kind of simple version of Jarnal. Good manual, Platform
         independent. Little features, which is a big feature. The ability to write outside the
         desktop area is a blockbuster in school.
         You can find Garys "Whiteboard Getting Started Guide", the "Windows Whiteboard Executable
         Launcher" and the "Whiteboard Application" on http://www.wiimoteproject.com/index.php?
         action=downloads;cat=3. Another download site is: https://www.intellectfactory.com/.
         It's a secure connection, accept Garys certificates.
         Coccinella: by Mats Bengtsson and now maintained by Sander . From the blurb: "The
         Coccinella project is [...] a free and open-source cross-platform communication tool with
         a built-in whiteboard for improved collaboration with other people." Site: http://
         thecoccinella.org/
         GeoEnZo: Excellent Dutch whiteboard software by Ton Groeneveld. From the blurb: " GeoEnZo
         is een programma waarmee het digitale schoolbord in de wiskundeklas als dagelijks
         instrument kan worden gebruikt. Met GeoEnZo heeft u het 'gewone' (white)bord eigenlijk
         niet meer nodig. Ook uw oude bordpasser, liniaal of geodriehoek kunt u voorgoed opbergen.
         GeoEnZo voorziet in alles wat u op het bord nodig hebt en biedt u daarbij heel veel
         elektronische voordelen." Software is worth translating.
         http://geoenzo.nl/geoenzo/index.htm
         LinktivityPresenter: From the blurb: "LinktivityPresenter is a personal graphic
         communications tool for everyone. You can draw, highlight and type directly on your
         computer screen, on PowerPoint slides, on Word documents, Excel sheets or on any
         application that you have open on your computer."
         Also from the page below: "Note: LinktivityPresenter was initially sold for $9.99.
         Effective April 2006, it is now free."
         Site: http://www.linktivity.com/presenter.html.
         Kindlelab: says their whiteboard software is free and open source. I don't know if it is
         that free when it's not GPL licensed but has a 'Ning' license. You must enter a 'social
         network' to download it. Site: http://kindlelab.com/
         Edusim: thier blurb: "Edusim is a free opensource 3D multi-user virtual world
         specifically for your classroom interactive whiteboard. Edusim is extendable allowing
         multiple classrooms to connect their interactive whiteboards for collaborative learning
         session". The software is in alpha stage. Site: http://edusim3d.com/alpha/">http://
         edusim3d.com/alpha/">http://edusim3d.com/alpha/
         See also their download site at: http://www.classroom20.com/profiles/blog/show?
         id=649749%3ABlogPost%3A116931
         Moodle: OSS/GPL E-learning system is world famous. Better than Blackboard. Go Site:
         http://moodle.org/. Log in as guest and go to: http://moodle.org/mod/forum/discuss.php?
         d=37248 to follow a discussion on whiteboard software. You can dowload whiteboard.swf, a
         Flash drawing program.
         Eduribbon: from the blurb: "EduRibbon is a universal tool for creating interactive
         presentations and explanation support". They have a free version: http://www.dosli.eu/
         eng/products/eduribbon. Seems usable feeeware.
         : ....... RANDOM STUFF, MUST BE EDITED!
  Loose ends:
  Magic Whiteboard http://www.magicwhiteboard.co.uk/
  Static whiteboard foil
  SubEthaEdit http://www.codingmonkeys.de/subethaedit/
  Kin of collaboration tool. Closed, Costly.
  Notatelt: http://www.notateit.com/
  Commercial licenses from € 25 to € 65 per license.
  PhotoNote: http://www.softpedia.com/get/Multimedia/Graphic/Graphic-Editors/PhotoNote.shtml
  Process images of your whiteboard? Freeware $ 50
  Firedoodle: https://addons.mozilla.org/nl/firefox/addon/4651
  Firefox add on turns any website into a whiteboard. To save you need to register to a server.
  ClearBoard: http://www.softtouchit.com/xpe/portal/674eef30-1119-1000-8121-46648aa451c5
  commercial, € 77, needs a photo camera, sort of note taking software?
  Bluechillies :http://www.bluechillies.com/list/whiteboard.html
  A collection of whiteboard stuff. Freeware, shareware.
  FaceTop: http://www.wired.com/science/discoveries/news/2004/07/64129
  "...a new system that cleverly blends a video-conference feed with a transparent image of a
  computer desktop into one full-screen window".
  CapTrue: http://www.batchconverter.com/CapTrue-download-73132.shtml
  Screenshot capture, also video.
  Ritepen3.0: http://www.ritescript.com/Products/ritePen.aspx
  "Write anywhere on your screen in continuous words and phrases, in smooth electronic ink.
  Watch your handwriting converted into text and entered into any application". Kind of Jarnal,
  commercial.
  v2Whitebaord: http://www.version2software.com/v2whiteboard.html
  "...sketch out how your computer network looks ... instead of trying to describe it. Or, what
  if you wanted to collaborate with a co-worker on the UI design of your next great piece of
  software".
  http://lightools.fredisland.net/index2.htm
  Looks great!
kleuters http://www.nldata.nl/laurentius/piramide/cgi-oic/pagedb.exe/show?no=627&fromno=506
(top)
  Bluetooth operates with high- and low band RF signals, thus emitting RF energy. We have some
  ideas on omitting RF signals. These might be interesting for those who want to use our
  digital interactive whiteboard in environments like radio astronomy, or where regulations are
  against wireless communication. When interested, contact us.
(top)
  15. Testimonials
  We received an e-mail from Aaron Johnson from the Jordan catholic school USA, from which we
  quote:
  Anyways, it's awesome to hear that you're excited to see what we've done with your ONSBORD
  system in our school! We have your system set up in a 7th/8th grade classroom at our Middle
  school and it is the epitome of interactive whiteboards in our opinion! We plan to put the 3
  additional systems in three more of our Middle school classrooms and will eventually bring the
  system to our 4th, 5th, and 6th grades.
  [snip]
  We really appreciate everything you have done to help improve free and open source
  technologies in education!
                                                Jordan_school_classroom.png
  Aaron also sent us this picture of his classroom. His whiteboard has a bit of a hot spot.
  "ONSBORD – The ultimate WiiBoard implementation! ONSBORD is what Jordan Catholic School is
  using in their classrooms to create a high-tech learning environment also known as the
  Interactive Whiteboard – we like to call it the WiiBoard! :~) ONSBORD has taken the original
  Wiimote Interactive Whiteboard idea (founded by Johnny Chung Lee) and has perfected it by
  making it work seamlessly in the modern day classroom. Once installed properly ONSBORD can
  and will function better than the commercial products provided by SMART and even Promethean!
  Please note that their main website is in Dutch so be sure to copy and paste the URL into
  Google Translate in order to be able to read it! Be sure to check out their DIY guide located
  here."
(top)
(top)
  17. Disclaimer
  Although we have tested every part of this project and many eyeballs have seen the texts,
  neither the author(s), nor the Public Primary School Rosa Boekdrukker or other schools or
  companies mentioned in this DIY project can be held responsable for any damamage, neither
  direct, nor inirect, neither consequential, nor accidental or whatsoever, when using the
  hardware, software, materials, advices or suggestions we write about or refer to.
  This project 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.
(top)
(top)