Hello all,
I'm new here, so apologies if this is in the wrong subforum (I thought about putting it in Delfino Plaza but that seems to be more general discussion than developer focused). This question has nothing to do with Dolphin, but I have a feeling some Dolphin devs may know the answer.
I am currently trying to write a (real) Wiimote bluetooth communication system similar to the one in Dolphin. I have communication working between the PC and the Wiimote, but when I get a response from the wiimote, it responds with an error code. For example, if I send the wiimote a simple LED change command:
... the wiimote responds with:
According to the Wiibrew Documentation this means that the wiimote has received the command 0x11 (LED Change), but has run into some sort of error. I don't know what this error actually means however. So, I guess my question is: What triggers the wiimote to respond with error code 0x03 when acknowledging an output report?
---
Here's some info that could help you help me fix this problem (if you graciously lend me your awesomeness for a moment
):
1. I am using Signal11's HIDAPI to communicate with the Wiimote.
2. The command goes through correctly on Mac, but NOT on my Windows PC. My macbook is using the default Mac bluetooth driver. My PC is using the Broadcomm driver.
3. My theory is that, in the example given above, only two bytes are written to the remote, whereas on Windows 22 bytes are written (as reported by hidapi). So somehow this is throwing off the remote. This occurs because of a WinAPI WriteFile() limitation. However, Dolphin never does anything to circumvent this, so I may be wrong.
Sorry for the long post. If anyone can do anything to help, I would be really grateful!
- Flafla2
I'm new here, so apologies if this is in the wrong subforum (I thought about putting it in Delfino Plaza but that seems to be more general discussion than developer focused). This question has nothing to do with Dolphin, but I have a feeling some Dolphin devs may know the answer.
I am currently trying to write a (real) Wiimote bluetooth communication system similar to the one in Dolphin. I have communication working between the PC and the Wiimote, but when I get a response from the wiimote, it responds with an error code. For example, if I send the wiimote a simple LED change command:
Code:
0x11 0x10... the wiimote responds with:
Code:
0x22 0x00 0x00 0x11 0x03According to the Wiibrew Documentation this means that the wiimote has received the command 0x11 (LED Change), but has run into some sort of error. I don't know what this error actually means however. So, I guess my question is: What triggers the wiimote to respond with error code 0x03 when acknowledging an output report?
---
Here's some info that could help you help me fix this problem (if you graciously lend me your awesomeness for a moment
): 1. I am using Signal11's HIDAPI to communicate with the Wiimote.
2. The command goes through correctly on Mac, but NOT on my Windows PC. My macbook is using the default Mac bluetooth driver. My PC is using the Broadcomm driver.
3. My theory is that, in the example given above, only two bytes are written to the remote, whereas on Windows 22 bytes are written (as reported by hidapi). So somehow this is throwing off the remote. This occurs because of a WinAPI WriteFile() limitation. However, Dolphin never does anything to circumvent this, so I may be wrong.
Sorry for the long post. If anyone can do anything to help, I would be really grateful!
- Flafla2
