Openvizsla sniffing nothing (but transfer amount continues to go up) #57
Comments
|
Do you observe the same with latest software from https://github.com/OpenVizslaTNG/ov_ftdi ? How do you connect the Pro Controller with Switch via OpenVizlsa? What type of cables/usb-c adapters do you use? |
|
To force fpga gateware reset, just add |
|
Hi! Thanks for responding! I didn't know anything about this OpenvizslaTNG repository! I'll have to give it a try! I found (only in the past 60 minutes or so) that making sure I always call ovctl with the I'm using no-name USB cables, nothing real special. The Switch -> openvizsla cable is a monoprice cable that I bought maybe 8 years ago, it's about 10 feet long and I've never used it until now. The openvizsla -> pro controller cable is this weird USB A to C cable that has magnets embedded periodically throughout its length.... it's branded "Supercalla". The openvizsla -> analysis computer cable is another monoprice cable I've had since forever. The printing on both of the Monoprice cables says "USB2.0 SHIELDED HIGH SPEED CABLE" |
|
Yes, exactly! Using |
|
(closing issue as "completed") |
I'm trying to reliably capture data sent between a Nintendo Switch Pro Controller and a Nintendo Switch.
Sometimes this works fine, but more often than not, this sort of situation occurs:
The LED next to the FPGA is dimly lit in the same way that it is when sniffing is working, and the kB value is increasing, but no packets are being displayed.
This behavior appears to be "sticky", that is, when sniffing works, chances are ok (if I had to put a number on it, I'd say maybe 75%?) that sniffing will work again if you stop and start the process... but when sniffing doesn't work, chances are very good (I'd say around 90%) that it'll continue to not work.
When it's not working, resetting the USB devices (ie, via the 'usbreset' command) doesn't seem to help any more than just trying again and hoping for the best.
This is only a full speed connection I'm dealing with, so I'd assume this board would have no problems whatsoever dealing with communications between a controller and a games console. Is there anything I can do to get it to be more reliable? Or to more fully reset the thing back into a state where I know it'll start sniffing properly when I ask it to do so?
I am using some rather long USB cables to connect between the console and the controller, but as the Switch is having no problems whatsoever picking up what the controller is putting down, I assume this isn't an issue.
Or, occasionally, something like this happens:
And very occasionally, it'll do this:
The text was updated successfully, but these errors were encountered: