Changes

[[File:Wii Remote Dissection-60.jpg|200px|thumb|right|Wii nunchuk]] The Nunchuk is identified by the 16-bit constant 0x0000 (0xFEFE encrypted) at register address 0xa400fe. It provides three-axis acceleration data, two digital buttons, and an X-Y analog stick.

[[File:Wii Remote Dissection-60.jpg|200px|thumb|right|Wii Nunchuk]] The Nunchuk is identified by the 16-bit constant 0x0000 (0xFEFE encrypted) at register address 0xa400fe. It provides an analog stick, two digital buttons, and three-axis acceleration data.

== Data Format ==

== Data Format ==

The Nunchuk reports its information as 6 bytes of data, readable at 0xa40008 and streamable using Data Reporting Modes that include Extension bytes (unused bytes are filled with 0x00). The data is packed into the six bytes as follows ('''after decryption'''):

The Nunchuk reports its information as 6 bytes of data, readable at 0xa40008 and streamable using Data Reporting Modes that include Extension bytes (unused bytes are filled with 0x00). The data is packed into the six bytes as follows ('''after decryption'''):

| style="border: 1px solid #ccc; padding: 0.2em;" | '''B'''<span style="color: #c00;">Z</span>

| style="border: 1px solid #ccc; padding: 0.2em;" | '''B'''<span style="color: #c00;">Z</span>

|}

|}

SX,SY are the Analog Stick X and Y positions, while AX, AY, and AZ are the 10-bit accelerometer data (in the same format as described in [[Wiimote#Accelerometer]]).

SX, SY are the analog stick X and Y positions, while AX, AY, and AZ are the 10-bit accelerometer data (in the same format as described in [[Wiimote#Accelerometer]]).

The values returned by the analog stick in the nunchuk enclosure do not encompass the full possible range, but rather have upper and lower bounds.  These bounds seem to be in the same range across Nunchuks, but there is some variation. Analog stick X returns data from around 35 (fully left) to 228(fully right), while analog stick Y returns from around 27 to 220.  Center for both is around 128.

The values returned by the analog stick in the Nunchuk enclosure do not encompass the full possible range, but rather have upper and lower bounds.  These bounds seem to be in the same range across Nunchuks, but there is some variation. Analog stick X returns data from around 35 (fully left) to 228 (fully right), while analog stick Y returns from around 27 to 220.  Center for both is around 128.

The accelerometer data uses the full range of 0-1024.  However, the full range is only seen when moving or rotating the Nunchuk sharply.  To measure still Nunchuk rotation in space, the following approximate bounds apply: X goes from around 300 (fully tilted left) to 740 (tilted right), turning further starts bringing the value closer to 512 (neutral position).  Similarly, Y goes from around 280 (tilted backwards) to 720 (forwards).  Z goes from 320 (upside-down) to 760 (right-side up).

The accelerometer data uses the full range of 0-1024.  However, the full range is only seen when moving or rotating the Nunchuk sharply.  To measure still Nunchuk rotation in space, the following approximate bounds apply: X goes from around 300 (fully tilted left) to 740 (tilted right), turning further starts bringing the value closer to 512 (neutral position).  Similarly, Y goes from around 280 (tilted backwards) to 720 (forwards).  Z goes from 320 (upside-down) to 760 (right-side up).

BC and BZ are the state of the C and Z buttons (0=pressed).

BC and BZ are the state of the C and Z buttons (0=pressed).

Nintendo games calibrate the center position of the Analog Stick upon power-up or insertion of the Nunchuk. The mechanism for that is unknown.

Nintendo games calibrate the center position of the analog stick upon power-up or insertion of the Nunchuk. The mechanism for that is unknown.

== Hardware ==

== Hardware ==

[[File:Wii-Nunchuk-top.jpg|200px|thumb|right|Wii nunchuk circuit board, top surface]][[File:Wii-Nunchuk-bottom.jpg|200px|thumb|right|Wii nunchuk circuit board, bottom surface]][[File:Wii chuck Board.jpg|200px|thumb|right|Wii Nunchuck Board Pinout for use without the cable]]The official Nintendo wired nunchuk appears to be electrically much simpler than the other controller extensions. It has a single joystick comprised of a 30KΩ potentiometer per axis, two switches, an accelerometer chip, and a microcontroller.

[[File:Wii-Nunchuk-top.jpg|200px|thumb|right|Wii nunchuk circuit board, top surface]][[File:Wii-Nunchuk-bottom.jpg|200px|thumb|right|Wii nunchuk circuit board, bottom surface]][[File:Wii chuck Board.jpg|200px|thumb|right|Wii Nunchuck Board Pinout for use without the cable]]The official Nintendo wired Nunchuk appears to be electrically much simpler than the other controller extensions. It has a single joystick comprised of one 30KΩ potentiometer per axis, two switches, an accelerometer chip, and a microcontroller.

{| class="wikitable" border="1"

{| class="wikitable" border="1"

|}

|}

Like the classic controller, the joystick potentiometers appear to be wired in parallel. The accelerometer chip is in the LIS3L02 series from [http://www.st.com STMicroelectronics]. The AE variant is not on their web site; their closest public product is their [http://www.st.com/stonline/stappl/productcatalog/app?path=/comp/stcom/PcStComOPNTableView.onTheClickOfOPNLink&code=88227&producttype=product LIS3L02AT], in the same LGA-8 package, but possibly with a different pinout.

Like the Classic Controller, the joystick potentiometers appear to be wired in parallel. The accelerometer chip is in the LIS3L02 series from [http://www.st.com STMicroelectronics]. The AE variant is not on their web site; their closest public product is their [http://www.st.com/stonline/stappl/productcatalog/app?path=/comp/stcom/PcStComOPNTableView.onTheClickOfOPNLink&code=88227&producttype=product LIS3L02AT], in the same LGA-8 package, but possibly with a different pinout.

The microcontroller chip appears to be a relabeled NEC (now [http://www2.renesas.com/micro/en/product/index.html Renesas]) uDP78F05 microcontroller, or a pin-compatible equivalent.

The microcontroller chip appears to be a relabeled NEC (now [http://www2.renesas.com/micro/en/product/index.html Renesas]) uDP78F05 microcontroller, or a pin-compatible equivalent.

=== Datel Blade-FX ===

=== Datel Blade-FX ===

This wireless Nunchuk can emulate either a Nunchuk or a Classic Controller. At startup it behaves like a Nunchuk, but pressing the "Classic" button puts it into Classic Controller mode. While in Classic Controller mode, the FUNCTION LED will be solidly lit (red). Classic controller emulation allows it to be used in the Wii system menu, with the joystick controlling the cursor, and the Z button selecting, and the C button having no visible effect. It also allows it to work (according to the instructions) with some Virtual Console games.

The Datel Blade-FX looks like a wireless Nunchuk but can emulate either a Nunchuk or a Classic Controller. At startup it behaves like a Nunchuk, but pressing the "Classic" button puts it into Classic Controller mode. While in Classic Controller mode, the FUNCTION LED will be solidly lit (red). Classic Controller emulation allows it to be used in the Wii system menu, with the joystick controlling the cursor and the Z button selecting. The C button has no visible effect. It also allows it to work (according to the instructions) with some Virtual Console games.

This wireless Nunchuk also has a cheat feature that remembers a motion that you do and repeats it continuously without you having to keep doing the motion. That is done with the "FX" button.

This Blade-FX also has a cheat feature that remembers a motion that you do and repeats it continuously without you having to keep doing the motion. That is done with the "FX" button.

There is also a "SYNC" button where the cord would be. Pressing it once connects the wireless nunchuk. While connected, the STATUS LED will slowly flash.  

There is also a "SYNC" button where the cord would be. Pressing it once connects the Blade-FX. While connected, the STATUS LED will slowly flash.  

When the wireless adapter is plugged in, but the wireless nunchuk has not been synced or turned on, then it behaves as though nothing was plugged in. No status report is generated when the wireless adapter is plugged in or unplugged, unless the nunchuk is synced. Querying the status report returns 0 for the extension flag (instead of 2).

When the wireless adapter is plugged in, but the Blade-FX has not been synced or turned on, then it behaves as though nothing was plugged in. No status report is generated when the wireless adapter is plugged in or unplugged, unless the Blade-FX is synced. Querying the status report returns 0 for the extension flag (instead of 2).

But when the wireless nunchuk is synced, then it sends a status report indicating that an extension is connected. Trying to read the 16 bytes from 0xF0 of the expansion (to identify the expansion) successfully returns "FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF", which isn't particularly helpful. Trying to read any 16 byte block has the same effect, it returns success, but it is all FFs.

But when the Blade-FX is synced, it sends a status report indicating that an extension is connected. Trying to read the 16 bytes from 0xF0 of the expansion (to identify the expansion) successfully returns "FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF", which isn't particularly helpful. Trying to read any 16 byte block has the same effect - it returns success, but it is all FFs.

   

   

BUT... trying to read the calibration data from 0x20 or 0x30 (although it still returns success as above) causes the Nunchuk to disconnect, sending a status report to indicate no extension is plugged in. It will automatically reconnect 0.5 seconds later. While disconnected, attempting to read from the Nunchuk returns error 7.

BUT... trying to read the calibration data from 0x20 or 0x30 (although it still returns success as above) causes the Blade-FX to disconnect, sending a status report to indicate no extension is plugged in. It will automatically reconnect 0.5 seconds later. While disconnected, attempting to read from the Blade-FX returns error 7.

Expansion data (in the input reports that include expansion data) is all 0xFF, just like trying to read the Nunchuk memory.

Expansion data (in the input reports that include expansion data) is all 0xFF, just like trying to read the Blade-FX memory.

As soon as the "Classic" button is pressed, a status message is sent saying that the extension has been unplugged. It will stay "unplugged" until the status button is released again, however long they hold down the button for. Once the "Classic" button has been released, it will wait about half a second and then send a status message saying the extension has been plugged in again. If the Classic button is pressed twice before it sent the released message, then it may send another disconnect and connect message after the connect message. It is not currently possible to tell whether it is in Classic Controller or Nunchuk mode. But we can use this method to read when the "Classic" button is held down (although it will always look like it was held down longer than it really was).

As soon as the "Classic" button is pressed, a status message is sent saying that the extension has been unplugged. It will stay "unplugged" until the status button is released again, however long the button is held down for. Once the "Classic" button has been released, it will wait about half a second and then send a status message saying the extension has been plugged in again. If the Classic button is pressed twice before it sent the released message, then it may send another disconnect and connect message after the connect message. It is not currently possible to tell whether it is in Classic Controller or Nunchuk mode. But we can use this method to read when the "Classic" button is held down (although it will always look like it was held down longer than it really was).

Actually unplugging the adapter will give the same disconnect message, so after a few seconds one should assume that they did a real disconnect instead of holding down the "Classic" button. In one case, after unplugging and replugging the adapter, the BladeFX started returning all 00 instead of FF when reading the expansion type from 0xF0. The data returned from report 0x34 also had 00 00 00 as the last 3 extension bytes, even though the first 16 (starting from 0x08 in extension memory) were all FF. Trying to read the calibration from 0x20 still returned all 0xFF and then disconnected as usual. Pressing buttons on the BladeFX had no effect on the data returned in report 0x34. I have not done any additional experiments with this state yet.

Actually unplugging the adapter will give the same disconnect message, so after a few seconds one should assume that they did a real disconnect instead of holding down the "Classic" button. In one case, after unplugging and replugging the adapter, the Blade-FX started returning all 00 instead of FF when reading the expansion type from 0xF0. The data returned from report 0x34 also had 00 00 00 as the last 3 extension bytes, even though the first 16 (starting from 0x08 in extension memory) were all FF. Trying to read the calibration from 0x20 still returned all 0xFF and then disconnected as usual. Pressing buttons on the Blade-FX had no effect on the data returned in report 0x34. I have not done any additional experiments with this state yet.

Clearly the current method of turning on an expansion doesn't work for the Datel Blade-FX, and we need some way to turn it on. Perhaps then the calibration can be read without an error, and we can get real data.

Clearly the current method of turning on an expansion doesn't work for the Datel Blade-FX, and we need some way to turn it on. Perhaps then the calibration can be read without an error, and we can get real data.

=== Datel Wireless Duo-FX ===

=== Datel Wireless Duo-FX ===

Using the standard initalization sequence, this nunchuck does not work. However, it works perfectly well with the sequence posted above for the Nyko Kama. The data is streamed unencrypted and the Datel can be fully read. However, the Nunchuk must be synced before initalizing the Extension Controller, otherwise, strange errors occur. For now, simply repeat the initialization sequence. After some tries, the Nunchuk works correctly (can be up to 10).

Using the standard initalization sequence, this nunchuck does not work. However, it works perfectly well with the sequence posted above for the Nyko Kama. The data is streamed unencrypted and the Datel can be fully read. However, the Nunchuk must be synced before initalizing the Extension Controller, otherwise, strange errors occur. For now, simply repeat the initialization sequence. After some tries (can be up to 10), the Nunchuk works correctly.

[[Category:Peripherals]]

[[Category:Peripherals]]