USB Hub for external pointer setup

[Nick Demaree]

Hi, folks!

I have been trying to solve this issue on and off for a few weeks, but have been unable to find a solution, even with the assistance of the QS discord group.

Basically, I am trying to replicate this setup depicted in the “external pointers” section of the QS manual - specifically, I want to connect my quadstick and an Ultrastik 360 through a USB hub and not the USB port on the back of the QS (As that is already being used as a “Device mode” connection to another console). In this scenario, I am trying to connect the US360 and QS to a Nintendo Switch, though I would like to replicate this with other consoles eventually as well.

So far, I am able to use the US360 with no problems when everything is connected to a PC, regardless of the US360 is connected to the PC directly, the USB hub, or the QS. I am also able to use my Nintendo Switch when the US360 is connected to the QS via the USB-A port on the back. However, as soon as the US360 is plugged into another USB port, I am not able to use it. 

I’m curious what I might be missing – for example, if the host device for the USB hub needs to be the PC or the console (I did briefly try both, without much luck). Perhaps this is a programming issue with my profiles? I have attached an example below which works well for me when the US360 is plugged directly into the QS. 

https://docs.google.com/spreadsheets/d/1QLFSe35Ff4ViV7sP9NLMo55QhZbgcjaRWf6orxVErvw/edit?usp=drivesdk

Another potential cause that was suggested to me is that the USB hub might not be providing enough power - it is possible, though the hub I am using has a dedicated 5V power supply attached, and seems to be providing sufficient power to my accessories, so I would be surprised if that’s the case. Maybe there are specific hardware requirements for a USB hub to work in this configuration?

In any case, I’ve been scratching my head about this for a while, and could use some guidance on how to set this up. Thanks all!

[Fred Davison]

The different ways of using an UltraStik or two with the Quadstick vary in fundamental ways, at a low level.

The scenario shown in the diagram has a laptop running QMP.  The laptop is the Host or master of the devices that are connected to it.  QMP running on the laptop is communicating with the UltraStik(s) over USB and is communicating with the Quadstick over USB via a second independent USB connection.  The Quadstick and the UltraStik are not communicating with each other over USB.  They are both devices to the laptop.

QMP reads data from the UltraStiks and relays it to the Quadstick where it shows up as the usb_1/2_up/down/etc in the configuration.   There is no path where the ultrastiks are sending data directly to the quadstick like when the ultrastik is plugged into the back of the quadstick.

Continuing with this example, the controller data from the Quadstick is then relayed to the CronusMax Plus (or Console Tuner Titan One) which handles the console.  (CronusMax Plus/T1 support is only in QMP 3.09.2, not in QMP 4+)  

______________________________________

New topic:  The Quadstick's CPU has one USB Device mode coprocessor that can be connected to either port B (default) or port A, but not to both at the same time.  It has one USB Host mode coprocessor that can only be connected to port A.

A scenario with the Quadstick connecting to a console over one device mode connection on port B and simultaneously to another device mode connection on port A, or with the ports reversed, is not possible.  There are not two USB device coprocessors in the Quadstick.  When the Quadstick is communicating as a device over USB-A, the USB-B port is completely idle and host mode coprocessor normally used for USB-A is disabled.

If the Quadstick's USB-B device connection is not to a PC, but is to a console directly, or through some other USB adapter, then QMP cannot relay UltraStik data over USB.  

All is not lost however, there are two other ways to transmit UltraStik data from QMP to the Quadstick:  Over a serial port connection or Bluetooth SSP.  The Quadstick can be connected to a console, the UltraStik is connected to the PC and QMP is relaying the data via a serial connection.  This will work with either QMP 3 or 4. 

________________________________________

usb_1... vs usb_2...    usb_2 data will only show up via QMP if there are two ultrastiks, or an ultrastik as usb_1 and a mouse pointer is captured by QMP as usb_2.

[Nick Demaree]

Thanks for the explanation, Fred – this explains a lot about the issues I’ve been having. 

I did purchase one of the FTDI serial cables from the manual and have now successfully used it to connect to the QMP- I will be sure to experiment with using it with the US360! This does give me 2 quick follow-up questions before I go back to testing:

1. Is the FTDI USB serial cable capable of acting as a totally separate data connection, like the USB A and B the ports on the back? For example, if I provide only power to the quadstick through the USB – B port and connect the QS via the serial cable to a PC, would I still be able to utilize the serial connection to play on the PC or is it only designed to relay voice commands and file management?

2. When I initially purchased my QS, I remembered coming across this post discussing shortages of the Bluetooth module and encouraging those who do not need one not to order it. 

https://groups.google.com/g/quadstick/c/l0-hdCYE55Y/m/I52AuxFDCAAJ

Granted, this was posted many years ago at this point, but when I ordered, I decided to err on the side of caution and did not include one in my order, as I did not think I would need one. However, as I have continued to practice with the quadstick and added more connections and functionality to my setup, I have begun to notice many use cases where having Bluetooth would be very convenient, and now I find myself wishing I had included one in my order. 

Is it possible to have a quadstick retrofitted with a Bluetooth module if it was not initially assembled with one? If so, what is the base cost of parts and labor?

Thanks again for all your help!

Nick