<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Wiibrew Forums - Hardware</title>
<description>Poking at the Wiis inner workings with a soldering iron. You break it, you get to keep all of the pieces.</description><link>http://forum.wiibrew.org/list.php?7</link><lastBuildDate>Tue, 10 Mar 2026 04:12:01 +0100</lastBuildDate>
<generator>Phorum 5.2.23</generator>
<item>
<guid>http://forum.wiibrew.org/read.php?7,74455,74455#msg-74455</guid>
<title>Wii component quality across console revisions</title><link>http://forum.wiibrew.org/read.php?7,74455,74455#msg-74455</link><description><![CDATA[ Hi, I wonder if any of the more knowledgable members can help me with this?<br /><br />It is well known that the Wii has poor component image quality. Gamecube component is much clearer:<br /><br />Example : [<a href="http://retrorgb.com/gamecubevswii.html" rel="nofollow">retrorgb.com</a>]<br /><br />Apparently, some of the later Wii hardware revisions had slightly better image quality than the earlier ones via component though.<br /><br />I&#039;ve been told that these are probably the later models - RVL-101 - the ones that had no Gamecube ports.<br /><br />Does anyone have any more in depth information as to exactly which hardware revisions have this &#039;upgrade&#039; in image quality?<br /><br />Cheers]]></description>
<dc:creator>andykara2003</dc:creator>
<category>Hardware</category><pubDate>Fri, 19 Sep 2014 08:49:07 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,74349,74349#msg-74349</guid>
<title>Does anyone have a dev unit?</title><link>http://forum.wiibrew.org/read.php?7,74349,74349#msg-74349</link><description><![CDATA[ I would really like a few files from the NAND, paticularly those in the shared2 folder. shared2/sys/SYSCONF is the most important, but a look at everything else might be helpful. I&#039;m using them for InspectMii.<br /><br />They are generated by the console (not copyrighted), so there shouldn&#039;t be any legal issues.]]></description>
<dc:creator>JoostinOnline</dc:creator>
<category>Hardware</category><pubDate>Sat, 17 May 2014 01:33:45 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73702,73702#msg-73702</guid>
<title>Making my very own Wiimote</title><link>http://forum.wiibrew.org/read.php?7,73702,73702#msg-73702</link><description><![CDATA[ Hi,<br /><br />I want to make my very own Wiimote with Motion Plus functionality as an experimental project. To do this I need some equipment:<br /><br />- Bluetooth<br />- Microcontroller<br />- Accelerometer<br />- Gyroscope<br />- IR camera<br />- etc.<br /><br />I want to use an AVR microcontroller since I have some exerience with AVRs. The AVR will communicate with the Bluetooth module using UART. I am thinking about using a <a href="http://www.rovingnetworks.com/products/RN42" rel="nofollow">RN42</a> class 2 Bluetooth module. I can read on the <a href="http://wiibrew.org/wiki/Wiimote" rel="nofollow">Wiimote site</a> that: "The Wii Remote uses (and, at times, abuses) the standard Bluetooth HID protocol to communicate with the host..." and "The Wii Remote actually uses a fairly complex set of operations, transmitted through HID Output reports, and returns a number of different data packets through its Input reports, which contain the data from its peripherals."<br /><br />Anyone know if I will be able to communicate with the Wii U using this RN42 module and a microcontroller?<br /><br />Thanks for any response!]]></description>
<dc:creator>Mikrogut</dc:creator>
<category>Hardware</category><pubDate>Mon, 16 Sep 2013 14:14:20 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73565,73565#msg-73565</guid>
<title>Tony Hawk Ride Board</title><link>http://forum.wiibrew.org/read.php?7,73565,73565#msg-73565</link><description><![CDATA[ Hey Guys,<br /><br />working on a system to use different controller types to navigate a 3D scene. Did some work on Kinect, Android smartphone and using Brian Peeks WiimoteLib for a Wiimote and Nunchuk. Now I just discovered a friend owing a board from Tony Hawk Ride. Is there a way to use its sensors on a PC? Using Win 7 x64 and like to code in C# but after all any working implementation is more than welcome. All I could find on the web was:<br /><br /><a href="http://cycling74.com/forums/topic/tonyhawkrideshredcontrollerhackjitter/" rel="nofollow">http://cycling74.com/forums/topic/tonyhawkrideshredcontrollerhackjitter/</a><br /><br />But I don&#039;t know this language nor did the original poster upload anything or responded to requests in the thread.<br /><br />Hope one might help,<br /><br />Cya]]></description>
<dc:creator>Hilarius</dc:creator>
<category>Hardware</category><pubDate>Fri, 16 Aug 2013 22:00:02 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73335,73378#msg-73378</guid>
<title>Re: Missing (some) wiimote connection attempts - is it improper page scan configuration?</title><link>http://forum.wiibrew.org/read.php?7,73335,73378#msg-73378</link><description><![CDATA[ 1) My problem was missing connect attempts initiated by the Wiimote. So if I understand correctly, in that scenario the Wiimote is paging, and my local controller is page scanning. Does the page scan type used by the Wiimote (specifying how the Wiimote behaves when it is page scanning, i.e. when it is made discoverable by pushing the sync button under the battery cover) have implications on how it pages, and how my local controller&#039;s page scan type should be configured?<br /><br />2) Likewise, is the correct approach to double the default page scan window (making it now as long as the interlaced (two back-to-back) scans in page scan type 1) or is the proper approach to use the default page scan window but specify page scan type 1?<br /><br />3) Also: I&#039;m far from an expert, but have been studying the BT spec quite a bit. I may have missed it, but don&#039;t see any way to directly query a remote controller, or any event resulting from a remote command that includes the remote controller page scan type. Is this something that requires specialized diagnostic equipment to sniff from the radio transmission itself?<br /><br />Thank you.]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Sun, 21 Jul 2013 17:19:47 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73335,73377#msg-73377</guid>
<title>Re: Missing (some) wiimote connection attempts - is it improper page scan configuration?</title><link>http://forum.wiibrew.org/read.php?7,73335,73377#msg-73377</link><description><![CDATA[ The wii uses page scan type 1 (interlaced scan) which performs two scans (each of the duration of the scan window) back to back.]]></description>
<dc:creator>tueidj</dc:creator>
<category>Hardware</category><pubDate>Sun, 21 Jul 2013 12:28:06 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73335,73373#msg-73373</guid>
<title>Re: Missing (some) wiimote connection attempts - is it improper page scan configuration?</title><link>http://forum.wiibrew.org/read.php?7,73335,73373#msg-73373</link><description><![CDATA[ My local BT controller was using default page scan settings. I modified the page scan window, doubling the default (from 11.25msec to 22.50msec) and no longer observe any "missed" wiimote connection attempts. Unfortunately, without being certain of the cause, this is an empirical solution only - until I see another missed connection.<br /><br />Still hoping someone else has seen this or can explain or point to other ways to confirm my suspicion and/or that my solution is robust.]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Sat, 20 Jul 2013 20:05:47 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73335,73372#msg-73372</guid>
<title>Re: Missing (some) wiimote connection attempts - is it improper page scan configuration?</title><link>http://forum.wiibrew.org/read.php?7,73335,73372#msg-73372</link><description><![CDATA[ I have confirmed that my host BT controller is never sending an event to my host when a wiimote connect attempt is missed. I put a scope on the HCI TX line to be sure there wasn&#039;t something wrong with my UART sampling that line. I don&#039;t have any way to monitor the actual radio, but this does indicate that my BT controller is never reporting any activity (which I extrapolate to mean it is never hearing the wiimote page)]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Sat, 20 Jul 2013 18:37:42 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73335,73335#msg-73335</guid>
<title>Missing (some) wiimote connection attempts - is it improper page scan configuration?</title><link>http://forum.wiibrew.org/read.php?7,73335,73335#msg-73335</link><description><![CDATA[ I have a basic Bluetooth stack that is able to interface pretty well with a wiimote. I&#039;ve noted that (after pairing, that is the wiimote is bonded to my host controller), a connection is not established every time a wiimote button is pushed. Monitoring my host controller, it looks like the page scan is not "seeing" the wiimote paging to establish a connection (there is nothing at all sent from the host controller to my local host). A connection is eventually established by pushing a wiimote button another time (or two). It seems to be about a 50% connect success rate, with no particular pattern - which wiimote button is pushed doesn&#039;t make a difference.<br /><br />I&#039;m wondering if this is due to improper setting of Page Scan Interval, Page Scan Window, or Page Scan Mode on my host controller? I&#039;m using PSM R1, which is what I saw the wiimote announcing in a request. I could try to set the host controller page scan to continuous, but wouldn&#039;t that leave no bandwidth for the data communication?<br /><br />Thanks.]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Tue, 16 Jul 2013 19:19:58 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73327,73327#msg-73327</guid>
<title>Is a delay/wait required to stop LEDS from blinking after connecting a Wiimote?</title><link>http://forum.wiibrew.org/read.php?7,73327,73327#msg-73327</link><description><![CDATA[ I have implemented a specialized Bluetooth stack to connect a small microcontroller to a wiimote. After much trial-and-error, it seems that when first sending an output report to set the state of the wiimote user LEDs, a pause is needed or they will continue to blink? Has anyone else seen that? Here&#039;s what I&#039;ve observed:<br /><br />1) Once an HID connection is established, I originally attempted to cause the LEDs to cycle from LED1, then LED2, 3, 4, and repeat. I sent output report 0x11 with the single data byte holding the proper value (bits 4-7 representing LEDs 1-4, respectively, and bits 0-3 cleared). I then verified that the setting was received by the wiimote by sending output report 0x15 and reading the current state of the LEDs from the 3rd data byte of the reply input report 0x20 . The LED values in the received input report matched what I had set, but the LEDs kept blinking as if I had not set a value.<br />2) After experimentation, I determined that by slowing down the cycling through each of the LED settings the flashing would stop and the desired pattern would be displayed (at a slower speed due to the inserted delay). The delay needed to be something greater than 1/2 second between sending the next LED setting.<br />3) Further experimentation showed that if I send an initial LED setting and then delay (at least 1/2 second) before sending any others, I could remove the delay between any subsequent changes to the LED settings, achieving the pattern in full-speed - limited only by the speed of my BT stack implementation.<br /><br />This seems to indicate there is some additional "initialization" time that must be observed after sending the first output report to stop the LED flashing.<br /><br />Questions:<br /><br />1) Has anyone else seen this?<br />2) Is it documented? (I did not find it anywhere. If not, should it be?)<br />3) Is there any known explanation for this?<br /><br />Thanks.<br /><br />* to clarify: I&#039;m sending<br />a2 11 10; a2 11 20; a2 11 40; a2 11 80; repeat;]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Tue, 16 Jul 2013 00:56:50 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73110,73304#msg-73304</guid>
<title>Unexpected LED initialization behavior</title><link>http://forum.wiibrew.org/read.php?7,73110,73304#msg-73304</link><description><![CDATA[ Moved to a separate post ("Is a delay/wait required to stop LEDS from blinking after connecting a Wiimote?")]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Sat, 13 Jul 2013 18:45:00 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73110,73121#msg-73121</guid>
<title>Re: How to pair a Wiimote? (LEDs continue to blink)</title><link>http://forum.wiibrew.org/read.php?7,73110,73121#msg-73121</link><description><![CDATA[ Blinking is done internally by the wiimote, if you want to do it yourself you have to send reports alternating the LEDs on and off.<br />You only need to store the link key if you plan on always enabling authentication, to avoid sending a link_key_request_negative_reply and then responding to the PIN request (which will cause a new link key to be generated every time). For a non-wii host device there are no advantages to using authentication after the initial pairing has been performed.]]></description>
<dc:creator>tueidj</dc:creator>
<category>Hardware</category><pubDate>Tue, 25 Jun 2013 00:08:12 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73110,73117#msg-73117</guid>
<title>Re: How to pair a Wiimote? (LEDs continue to blink)</title><link>http://forum.wiibrew.org/read.php?7,73110,73117#msg-73117</link><description><![CDATA[ I thought that might be true. I looked at the documentation and didn&#039;t see anyway to make the LEDs blink - only turn them on or off. I concluded that since I&#039;m not sending any output report to the wiimote to make the LEDs blink, it must be doing it on its own. Is there an output report to send to make them blink, or is it a mode that only the wiimote can put itself in (and can only be stopped, but not started, by a remote device)?<br /><br />Is there anything I need to do with the link key I receive in the Link Key Notification Event?<br /><br />Thanks.]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Mon, 24 Jun 2013 15:02:46 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73110,73115#msg-73115</guid>
<title>Re: How to pair a Wiimote? (LEDs continue to blink)</title><link>http://forum.wiibrew.org/read.php?7,73110,73115#msg-73115</link><description><![CDATA[ The LEDs blink until you send a report telling them to do something else.]]></description>
<dc:creator>tueidj</dc:creator>
<category>Hardware</category><pubDate>Mon, 24 Jun 2013 13:10:25 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73110,73110#msg-73110</guid>
<title>How to stop LEDS from blinking after pairing a Wiimote.</title><link>http://forum.wiibrew.org/read.php?7,73110,73110#msg-73110</link><description><![CDATA[ I&#039;m working on a project intending to use the wiimote as a user input device controlling a small embedded controller. I have a basic stack that is able to connect.<br /><br />I have two modes that I&#039;d like to support:<br /><br />First, a pairing mode: press the sync button under the wiimote battery cover, then command my local controller to inquire, connect, and finally pair with the wiimote. This seems to work. I think it is actually establishing a bond because after this process, and disconnecting the wiimote, a single button press on the wiimote causes a Connection Request event on my local controller. I presume that indicates that the Pin/BD_ADDR has been stored in the wiimote - indicating a successful pairing.<br /><br />However, after the (ostensible) pairing, the LEDs on the wiimote continue to blink. Is that because the pairing is not complete, or because I am required to send an output report to the wiimote after connecting to stop the LEDs from flashing?<br /><br />Second, a reconnect mode: after successfully pairing the wiimote once, I&#039;d like to be able to have it initiate a connection with my local controller using a single button press. This also seems to be working, but the LEDs on the wiimote continue to blink after the connection is established.<br /><br />Is there some additional configuration/handshake required to complete the pairing and single-button reconnect modes? Or, is it expected that the LEDs will continue to blink until some report is sent?<br /><br />Thanks.]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Mon, 24 Jun 2013 05:41:54 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73034,73109#msg-73109</guid>
<title>Re: Writing BT stack to connect with Wiimote - problems connecting</title><link>http://forum.wiibrew.org/read.php?7,73034,73109#msg-73109</link><description><![CDATA[ I have been successful in connecting to the wiimote with my "thin" BT stack. Thanks for all the help.<br /><br />I still don&#039;t understand why I cannot send an ACL packet with PB=02. But I&#039;m past that obstacle.]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Mon, 24 Jun 2013 05:26:22 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73034,73105#msg-73105</guid>
<title>Re: Writing BT stack to connect with Wiimote - problems connecting</title><link>http://forum.wiibrew.org/read.php?7,73034,73105#msg-73105</link><description><![CDATA[ Wow. Not what I expected.<br /><br />I tried setting the host buffer size to match the controller reported buffer sizes. This returned a success status.<br /><br />Then I tried issuing the same command to establish an L2CAP channel - and same symptoms: no response at all.<br /><br />In frustration (perhaps desperation) I decided to fiddle with the LLID bits. I&#039;m still confused by the description in the spec, which seems self-contradictory to me.<br /><br />As it turns out, if I issue the connection request (for an L2CAP channel) using PB of 00, I get a response! With PB=03 or 02, no response. This is really confusing. And, the response is sent with LLID = 20. I just don&#039;t understand this. (NOTE: to try to simplify, I&#039;m testing using a USB BT dongle on my desktop, not the wiimote).<br /><br />So once I send the (L2CAP) connection request (PSM==01), I receive an extended features request, then a configuration request (for MTU size). I do get a connection response with successful status. I wasn&#039;t prepared for all this traffic, so hadn&#039;t coded responses. Ultimately, the connection was terminated (reason==0x13, Remote User Terminated Connection).<br /><br />So I still can&#039;t figure out the proper use of LLID, but I have successfully created my first L2CAP channel.<br /><br />BTW, both the host and remote device report a version of 04, or BT 2.1 + EDR.<br /><br />Still don&#039;t understand the LLID flag.]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Thu, 13 Jun 2013 07:43:07 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73034,73101#msg-73101</guid>
<title>Re: Writing BT stack to connect with Wiimote - problems connecting</title><link>http://forum.wiibrew.org/read.php?7,73034,73101#msg-73101</link><description><![CDATA[ I will try. It occurred to me that the parameters may be a problem, but the behavior was to just not respond at all - as if the command was never sent. Surely a reasonable expectation would be for a Command Complete event with a non-success result code. With nothing to guide me, I couldn&#039;t even attempt to guess at what would be "reasonable" parameter values.<br /><br />With controller to host flow control disabled, wouldn&#039;t you expect the value of num_ACL_data_packets to be ignored and irrelevant? (I&#039;ll still try it, though). I did try values of 0 for both ACL data and synchronous data, thinking this would indicate unlimited buffers. It may be the buffer size that is the problem, even if 0 buffers is an acceptable parameter value.<br /><br />Is there any way to test behavior of a working wiimote interface - to see what happens if a connection (link) is established but no L2CAP channels are established for a minute? I still don&#039;t understand why the successful connection is disconnected (every time) just seconds after the connection is established.]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Wed, 12 Jun 2013 22:15:58 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73034,73100#msg-73100</guid>
<title>Re: Writing BT stack to connect with Wiimote - problems connecting</title><link>http://forum.wiibrew.org/read.php?7,73034,73100#msg-73100</link><description><![CDATA[ Try increasing the ACL packet length to at least 256 and num_acl_data_packets to 16. The synchronous data parameters shouldn&#039;t matter.]]></description>
<dc:creator>tueidj</dc:creator>
<category>Hardware</category><pubDate>Wed, 12 Jun 2013 20:41:34 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73034,73099#msg-73099</guid>
<title>Re: Writing BT stack to connect with Wiimote - problems connecting</title><link>http://forum.wiibrew.org/read.php?7,73034,73099#msg-73099</link><description><![CDATA[ You may be onto something with setting the host buffer size. As I read the spec, it says that if not set, the controller will assume that it can send an unlimited number of data packets of any size it wants. Also, if controller-to-host flow control is not enabled (which is the default, and I am not enabling it) the number of packets is not used anyway. However, I&#039;m more interested in making this work than interpreting the spec...<br /><br />When I tried to set the host buffer size with the Host Buffer Size command, there was no response. It was as though the command I was sending was incorrect. Eventually, after sending other commands, I finally got a Hardware Error Event. This is what I sent to the controller:<br /><br />01 330C 07 4000 20 0100 0100<br /><br />Which I believe indicates:<br /><br />UART HCI command; Host Buffer Size command opcode; parameter length; 64 bytes ACL data buffer size; 32 bytes synchronous data buffer size; 1 ACL data buffer; 1 synchronous data buffer<br /><br />Is there something wrong with this? Some improper setting (or understanding on my part) may be why the controller never sends ACL data to the host.]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Wed, 12 Jun 2013 16:54:03 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73096,73096#msg-73096</guid>
<title>Computer as a wii remote</title><link>http://forum.wiibrew.org/read.php?7,73096,73096#msg-73096</link><description><![CDATA[ So I have seen Rikmer&#039;s post about trying to do this on an Android over here: [<a href="http://forum.wiibrew.org/read.php?7,59126" rel="nofollow">forum.wiibrew.org</a>] I was wondering if anyone has successfully accomplished the feat using an actual computer, beit Windows or Linux. It sounds like Rikmer and his/her repliers had things nearly down with Android (only stopped by Android security problems), but it doesn&#039;t sound like they ever tested things on an actual computer. Please tell me if any of you have tried this (and how to do it if you succeeded ;) )]]></description>
<dc:creator>Matchlighter</dc:creator>
<category>Hardware</category><pubDate>Wed, 12 Jun 2013 06:26:12 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73034,73090#msg-73090</guid>
<title>Re: Writing BT stack to connect with Wiimote - problems connecting</title><link>http://forum.wiibrew.org/read.php?7,73034,73090#msg-73090</link><description><![CDATA[ A basic init sequence is:<br />- hci_reset<br />- hci_read_buffer_size<br />- hci_read_bd_addr<br />- hci_host_buffer_size<br />- hci_write_pin_type(0 = variable)<br />- hci_write_page_timeout<br />- hci_write_scan_enable(2 = page scanning enabled)<br />Additional optional commands (things the wiimote doesn&#039;t care about but are good practice):<br />- hci_write_cod<br />- hci_change_local_name<br /><br /><br />"The event code 0xFF is reserved for the event code used for vendor-specific debug events." Manufacturer specific stuff, for example the wii uses it to signal when the red sync button on the front panel has been pressed.]]></description>
<dc:creator>tueidj</dc:creator>
<category>Hardware</category><pubDate>Tue, 11 Jun 2013 23:06:56 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73034,73089#msg-73089</guid>
<title>Re: Writing BT stack to connect with Wiimote - problems connecting</title><link>http://forum.wiibrew.org/read.php?7,73034,73089#msg-73089</link><description><![CDATA[ I do not use any of these commands. As a matter of fact, I do nothing to initialize the local controller, other than issuing a Reset Command. If there are critical initialization steps please point me towards them. I note from the spec regarding the Read Buffer Size Command:<br /><br /><blockquote class="bbcode"><div><small>Quote<br /></small><strong></strong><br />The Read_Buffer_Size command must be issued by the Host before it sends any data to the Controller.</div></blockquote><br />I can see this is good practice, but will violating it cause a problem? Since the data packets from the wiimote are so small, I was simply going to use buffers sized for the MTU size (48 bytes). I presume there would only be an issue if I attempted to send a data packet larger than the controller&#039;s buffer size. I will test it later just to be sure.<br /><br />I also noted that upon power-up of the local controller (but not on reset) an event packet is sent by the controller. I presume this is some manufacturer-specific information (I will contact the manufacturer to verify) - have you heard of such a thing? I don&#039;t recognize the event code 0xFF. The byte sequence is:<br /><br />04FF1FC302000F000D000010000037000100004E0100000000000000000000000000]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Tue, 11 Jun 2013 22:02:55 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73034,73088#msg-73088</guid>
<title>Re: Writing BT stack to connect with Wiimote - problems connecting</title><link>http://forum.wiibrew.org/read.php?7,73034,73088#msg-73088</link><description><![CDATA[ Do you use the HCI_read_buffer_size and HCI_host_buffer_size commands as part of the controller initialization? Is flow control left off (by default) or explicitly enabled?]]></description>
<dc:creator>tueidj</dc:creator>
<category>Hardware</category><pubDate>Tue, 11 Jun 2013 21:04:17 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73034,73087#msg-73087</guid>
<title>Re: Writing BT stack to connect with Wiimote - problems connecting</title><link>http://forum.wiibrew.org/read.php?7,73034,73087#msg-73087</link><description><![CDATA[ That&#039;s what I was testing when I started using the BT dongle instead of the wiimote.<br /><br />I was able to send ACL data (based on the "Number of Completed Packets Event" received) with the BT dongle. However, I never received any ACL data (there was never an acknowledgement of the connection request). This is how I got into the LLID and BT version issue. I observed that if I use the LLID (PB flag) of 11 (which appears to be correct for v4.0 but not v1.2 as you point out) with the BT dongle (which is v4.0) then I receive the "Number of Completed Packets Event" (but still no acknowledgment of the connection request). If I use the LLID (PB flag) of 0b10 (which is valid for v1.2 but not v4.0) then I get neither the "Number of Completed Packets Event" nor an acknowledgment of the connection request from the BT dongle.<br /><br />My hypothesis is that with the BT dongle (v4.0) and an LLID/PB value of 0b11, that represents a complete L2CAP PDU and it is forwarded on by the remote controller (in this case as a signaling command on (fixed) channel 1). That is why I receive the "Number of Completed Packets Event". When I use the LLID/PB value of 0b10, that is a start packet, and the local controller is waiting for the continuation packet. While that may be plausible, that would imply that there is not backwards compatibility, which I find unusual. Also, while I&#039;m clearly not an expert, it seems that the controller could easily recognize an L2CAP B-frame (complete L2CAP PDU) and know that the packet is complete. (if I understand correctly).<br /><br />This is why I started wondering if there is some flow control setting (on my host controller - not the BT dongle or the wiimote) that is interfering with reception of the ACL data. Since I&#039;m using a UART HCI transport, I only have RX and TX lines, and the RX path through my UART is working because that&#039;s the path to receive events from the controller.<br /><br />Is it possible to validate that the wiimote will maintain a connection (link) with another BT device even if no L2CAP channel is established within some timeout period? I am only seeing the disconnect when using the wiimote, not the BT dongle. (but still, I can&#039;t establish an L2CAP channel on either)]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Tue, 11 Jun 2013 19:31:53 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73034,73086#msg-73086</guid>
<title>Re: Writing BT stack to connect with Wiimote - problems connecting</title><link>http://forum.wiibrew.org/read.php?7,73034,73086#msg-73086</link><description><![CDATA[ Have you tested sending/receiving ACL data when connected to something other than a wiimote? Nearly every device supports SDP, for example.]]></description>
<dc:creator>tueidj</dc:creator>
<category>Hardware</category><pubDate>Tue, 11 Jun 2013 18:32:53 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73034,73085#msg-73085</guid>
<title>Re: Writing BT stack to connect with Wiimote - problems connecting</title><link>http://forum.wiibrew.org/read.php?7,73034,73085#msg-73085</link><description><![CDATA[ I swapped out the troublesome wiimote for another one. I am now back to where I started: I am able to inquire and connect to the (different) wiimote - but it disconnects almost immediately. (Error code==0x16 "Connection Terminated by Local Host")<br /><br />I&#039;m using the exact sequence to establish the L2CAP channel as in the log you provided (with the exception that the connection handle is different). I&#039;m using:<br /><br /><br />02 2A20 0C00 0800 0100 02 01 0400 1100 4300<br /><br />HCI trasport - ACL data<br />Connection handle 0x002A, PB 0b10, BC 0b00<br />Packet length 0x000C<br />L2CAP header - length 0x0008<br />L2CAP header - channelID 0x0001 (signaling channel)<br />signal command 0x02 (connection request)<br />id 0x01<br />data length 0x0004<br />PSM 0x0011<br />source channel ID 0x0043<br /><br />Is is possible to conduct an experiment with a working wiimote connection? I&#039;m wondering if the wiimote behaves differently (than the BT dongle I was using) in that it will accept a connection but will drop that connection if the HID channels (PSM 11 and 13) are not established within a timeout period. I could understand this behavior since in normal operation the wiimote is always using those channels and does not need to support any others (although from the log I can see it also supports PSM 1 for SDP). (The BT dongle accepted a connection and it was not dropped even though I did not establish any L2CAP channels) I&#039;m trying to break this down into smaller pieces and look for a way to understand what is happening.<br /><br />I have never received any ACL data. When experimenting with the USB dongle on my desktop, I did receive a Number of Competed Packets event when I sent ACL data to that device (attempting to establish an L2CAP connection but never ACL data back with the connection response.<br /><br />Is there something that can be interfering with receipt of ACL data? I was wondering if flow control may be an issue.]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Tue, 11 Jun 2013 17:27:42 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73034,73078#msg-73078</guid>
<title>Re: Writing BT stack to connect with Wiimote - problems connecting</title><link>http://forum.wiibrew.org/read.php?7,73034,73078#msg-73078</link><description><![CDATA[ The versions don&#039;t matter.<br />The only thing I can think of that might help is to set the page scan type (HCI_Write_Page_Scan_Type) to 1.]]></description>
<dc:creator>tueidj</dc:creator>
<category>Hardware</category><pubDate>Tue, 11 Jun 2013 11:01:03 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73034,73077#msg-73077</guid>
<title>Re: Writing BT stack to connect with Wiimote - problems connecting</title><link>http://forum.wiibrew.org/read.php?7,73034,73077#msg-73077</link><description><![CDATA[ No joy today. I thought the log would help. I was unable to even connect to the wiimote. Using the same BT module and interface that I&#039;m using to attempt connecting to the wiimote (but failing), I was able to connect to a USB BT dongle on my desktop. The only differences I can see are that the USB BT dongle reports LMP v4 (EDR2.1+) but the wiimote is LMP v2 (v1.2). The error status returned with the failed connection attempt to the wiimote is 0x04 - "Page Timeout". I set the BT module page timeout to 0x8000 (~20 seconds) but that did not help. I am putting the wiimote into discoverable mode (the leds flashing) using the sync button underneath the battery cover.<br /><br />I am able to inquire and find the wiimote (reports back the BD_ADDR)<br />I am not able to read the wiimote (remote) name (returns error code 0x04 - "Page Timeout")<br /><br />Is there something I need to do to make a v4 radio talk to a v2 radio?]]></description>
<dc:creator>ags000</dc:creator>
<category>Hardware</category><pubDate>Tue, 11 Jun 2013 08:18:41 +0200</pubDate></item>
<item>
<guid>http://forum.wiibrew.org/read.php?7,73034,73076#msg-73076</guid>
<title>Re: Writing BT stack to connect with Wiimote - problems connecting</title><link>http://forum.wiibrew.org/read.php?7,73034,73076#msg-73076</link><description><![CDATA[ The CIDs aren&#039;t important, the wii&#039;s software just counts upwards and this was the second time a wiimote had been synched since the game started.<br />Both of "in MTU" values are translated wrong, there&#039;s another one further down (0xB900).]]></description>
<dc:creator>tueidj</dc:creator>
<category>Hardware</category><pubDate>Tue, 11 Jun 2013 04:57:44 +0200</pubDate></item>
</channel>
</rss>