Support for different version of the dongle about xow HOT 26 CLOSED

Pairing 1708 controllers should work fine. I've noticed that it sometimes needs about a minute to complete the pairing. Debugging the actual pairing process is unfortunately next to impossible without access to the source code of the dongle's firmware.

from xow.

Unfortunately i can't seem to pair the controller. I tried it several times until the pairing search process on the controller times out (rapid blinking to slower blinking) and never saw a single message on the console.

Is this easier to debug with a 5Ghz dongle so i can capture packets and what not? If yes, any cheap recommendations?
EDIT: Also doesn't work on my Laptop with Ubuntu on it.

from xow.

The first thing you could try is a simple Wireshark USB capture between the dongle and your system (upload the resulting file). Maybe the pairing packets get received by the dongle but aren't recognized by xow. If the capture doesn't contain any pairing packets you'll have to do a wireless capture (2.4 GHz will work, xow uses channel 1 by default).

from xow.

What i know until now:

USB packets get sent to dongle for initialization of the pairing, LED in dongle flashes.
I tried to capture packets on 2.4GHz Channel 1 but either there were none from the dongle or i couldn't find them.
Therefore the controller probably never finds the dongle and therefore the dongle never sends USB packets back to the PC.

from xow.

You should at least see the beacon frames of the dongle when you capture on channel 1. You've put your network interface into monitor mode, right?

from xow.

I did and i also see other traffic on Channel 1.
I tried to identify the beacon packets with the help of https://gist.github.com/devkid/4b3bd50760504d1b93ea684cfd3ed895 and this is where i got the idea of the 5GHz dongle.
Is it correct that i am searching for a packet with that exact vendor specific tag?
EDIT: I also don't see the chip address in wireshark at all

from xow.

Yes, that's correct. The beacon data is hardcoded to the following (where pairing is either 0 or 1):

You could also try changing the wireless channel in the Makefile (take a look at the list of valid channels in mt76.h).
Another strange thing I've noticed is that the MAC address of your dongle starts with 6c:5d:3a whereas most of the addresses I've seen from other people start with either 62:45:b4 or 62:45:b5. Maybe you're using a different variant/type of dongle that's somehow incompatible with the way xow works?

from xow.

Tried changing channels and so on a little while ago.
Could be that there is a even newer version. Two of the brand new "Controller + Wireless Adapter for Windows 10" included dongles started with 6c, cant remember what exactly the other one was.
So i guess the dongle is the problem here and not the Controller....

When i press the pairing button on the dongle, is it expected to get two messages for "Pairing initiated"? So two messages for pressing it and two for releasing it

Maybe ill try to look more deeper at the USB communication later.

from xow.

When i press the pairing button on the dongle, is it expected to get two messages for "Pairing initiated"?

Yes, that happens with Microsoft's driver too (it's just not logged). It doesn't cause any harm to initiate the pairing multiple times, so I didn't bother differentiating between button presses and releases.

So i guess the dongle is the problem here and not the Controller....

Very likely. Have you checked whether the firmware in C:\Windows\System32\DriverStore\FileRepository\mt7612us_xxxxx is the same as the binary file included with xow? I've noticed that Microsoft distributes different packages of their driver with distinct firmware images.

from xow.

So i guess the dongle is the problem here and not the Controller....

Very likely. Have you checked whether the firmware in C:\Windows\System32\DriverStore\FileRepository\mt7612us_xxxxx is the same as the binary file included with xow? I've noticed that Microsoft distributes different packages of their driver with distinct firmware images.

Just checked and diff'ed it. They are the same

from xow.

Just checked and diff'ed it. They are the same

Then I'm unfortunately out of ideas of what we could try to make this work 😕. Unless I'll be able to get my hands on one of these dongles, I don't think there's much I can do to help you. I'd like to keep this issue open in case someone else has something important to share.

from xow.

Maybe the dongles should be referred to by model number, instead of slim and bulky, since there seems to be more than 2 now. On the edge of the dongle opposite the sync button, there is black writing. At the top right corner of that edge, mine says Microsoft and just below it says Model 1713. I'm pretty sure mine is the old bulky one. Anyone with the slim one can provide theirs? Bur0k, what does yours say?

from xow.

I think we're dealing with different revisions/versions of the two models here. Take a look at Microsoft's FCC applications. Their application ids always refer to the model number of a specific product. In case of the old dongle, it's C3K1713. I couldn't find a newer model of the dongle in their recent applications.

from xow.

Maybe the dongles should be referred to by model number, instead of slim and bulky, since there seems to be more than 2 now. On the edge of the dongle opposite the sync button, there is black writing. At the top right corner of that edge, mine says Microsoft and just below it says Model 1713. I'm pretty sure mine is the old bulky one. Anyone with the slim one can provide theirs? Bur0k, what does yours say?

Mine is 1790

Just checked and diff'ed it. They are the same

Then I'm unfortunately out of ideas of what we could try to make this work confused. Unless I'll be able to get my hands on one of these dongles, I don't think there's much I can do to help you. I'd like to keep this issue open in case someone else has something important to share.

If you want i can mail it to you and when you are done i'll provide the label to send it back

from xow.

Just to confirm, I also have the 1790 version of the dongle and my Elite 2 also won't pair.

from xow.

My dongle model is a 1790 and I'm able to pair just fine.

Are there some logs or anything that I can provide that could possibly help narrow down why I can pair my Elite v2 while using the 1790 dongle and others can't?

from xow.

2020-03-21 23:20:32 DEBUG - ASIC version: 7632
2020-03-21 23:20:32 DEBUG - Chip id: 7613
2020-03-21 23:20:32 INFO  - Wireless address: 6c:5d:3a:00:d1:ca

Maybe these three informations from the log could be usefull (v0.4 of xow)

from xow.

@Bur0k Can you provide me with a packet capture of the USB communication (both on Windows and on Linux with xow)? I might be able to spot some differences that explain why it's not working as intended. It might take a while for me to look through all the packets though. May I ask where and when you bought the dongle? That might help to narrow down the problems.

from xow.

@Bur0k Can you provide me with a packet capture of the USB communication (both on Windows and on Linux with xow)? I might be able to spot some differences that explain why it's not working as intended. It might take a while for me to look through all the packets though. May I ask where and when you bought the dongle? That might help to narrow down the problems.

The two capture files in the attached zip archive.
pcapng.zip

I bought the Controller+Dongle bundle from otto(dot)de

from xow.

@Bur0k While looking through the packet captures of people that had similar issues, I've noticed a very strange behavior of the Windows driver: The source address of the beacon frames is (in your case) not the actual MAC address read from the dongle. It's 62:45:bd:00:d1:ca despite the reading from the EEPROM being 6c:5d:3a:00:d1:ca. That might explain why the controllers didn't connect to your dongle. I'm working on a fix.

from xow.

@WernerAUT I've implemented a fix in the latest commit, you might want to check it out. I also added a check make sure only one instance of xow is running at the same time.

from xow.

tested it already right now and it works perfect, controller connected after seconds! Well done

from xow.

Elite 2 controller also paired right away.

from xow.

I was having the same issue, but that commit fixed it for me as well.

from xow.

Updated fixed it, thanks for all your investigations and work

from xow.

Raspbian tested fine, thanks a lot

from xow.