• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 32 subscribers
  • Views 233 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TUSB2036: 3DConnexion Spacemouse intermittent respons when connected through hub

Danny Van den Bliek
Prodigy 50 points
Part Number: TUSB2036

When 3DConnexion Spacemouse connected directly to computer, respons is normal when rotating a 3D object on the screen, without any hicks. When the Spacemouse is connected through the TUSB2036, the object rotates slowly and intermitting.

Hub enumerates without any problems or errors. When the Spacemouse connects directly to the computer, it is connected as a low speed device and also when it connects through the hub. So bandwidth is not the problem.

I tested with no devices connected to the other ports of the TUSB2036.

Anyone else seen such behaviour of a Spacemouse or other HID connected to a hub?

Operating system on computer is Windows 10

Thanks.

  • 0
    TI__Guru** 105055 points

    did it show as low speed correctly on USBtree viewer?

    regards

    Brian

  • 0 in reply to Brian Zhou
    Prodigy 50 points

    Brian,

    Yes, see enclosed files: one when SpaceMouse directly connected to the computer, the other connected via hub.

    What I forgot to say: if I connect other devices ( keyboard controller, trackball ) to the hub, they all work as normal. 

    To me it looks like a Windows driver problem, but I don't know if it is possible that a hub has influence on the working of a driver

    direct connected.txt 
    Device Descriptor:
bcdUSB:             0x0200
bDeviceClass:         0x00
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x08 (8)
idVendor:           0x256F
idProduct:          0xC636
bcdDevice:          0x0437
iManufacturer:        0x01
0x0409: "3Dconnexion"
iProduct:             0x02
0x0409: "SpaceMouse Module"
iSerialNumber:        0x00
bNumConfigurations:   0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed:     Low
Device Address:       0x02
Open Pipes:              2

Endpoint Descriptor:
bEndpointAddress:     0x81  IN
Transfer Type:   Interrupt
wMaxPacketSize:     0x0008 (8)
bInterval:            0x0A

Endpoint Descriptor:
bEndpointAddress:     0x02  OUT
Transfer Type:   Interrupt
wMaxPacketSize:     0x0008 (8)
bInterval:            0x0A

Configuration Descriptor:
wTotalLength:       0x0029
bNumInterfaces:       0x01
bConfigurationValue:  0x01
iConfiguration:       0x00
bmAttributes:         0x80 (Bus Powered )
MaxPower:             0x32 (100 Ma)

Interface Descriptor:
bInterfaceNumber:     0x00
bAlternateSetting:    0x00
bNumEndpoints:        0x02
bInterfaceClass:      0x03 (HID)
bInterfaceSubClass:   0x00
bInterfaceProtocol:   0x00
iInterface:           0x00

HID Descriptor:
bcdHID:             0x0111
bCountryCode:         0x00
bNumDescriptors:      0x01
bDescriptorType:      0x22
wDescriptorLength:  0x00B7

Endpoint Descriptor:
bEndpointAddress:     0x81  IN
Transfer Type:   Interrupt
wMaxPacketSize:     0x0008 (8)
bInterval:            0x0A

Endpoint Descriptor:
bEndpointAddress:     0x02  OUT
Transfer Type:   Interrupt
wMaxPacketSize:     0x0008 (8)
bInterval:            0x0A
    via hub.txt 
    Device Descriptor:
bcdUSB:             0x0200
bDeviceClass:         0x00
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x08 (8)
idVendor:           0x256F
idProduct:          0xC636
bcdDevice:          0x0437
iManufacturer:        0x01
0x0409: "3Dconnexion"
iProduct:             0x02
0x0409: "SpaceMouse Module"
iSerialNumber:        0x00
bNumConfigurations:   0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed:     Low
Device Address:       0x06
Open Pipes:              2

Endpoint Descriptor:
bEndpointAddress:     0x81  IN
Transfer Type:   Interrupt
wMaxPacketSize:     0x0008 (8)
bInterval:            0x0A

Endpoint Descriptor:
bEndpointAddress:     0x02  OUT
Transfer Type:   Interrupt
wMaxPacketSize:     0x0008 (8)
bInterval:            0x0A

Configuration Descriptor:
wTotalLength:       0x0029
bNumInterfaces:       0x01
bConfigurationValue:  0x01
iConfiguration:       0x00
bmAttributes:         0x80 (Bus Powered )
MaxPower:             0x32 (100 Ma)

Interface Descriptor:
bInterfaceNumber:     0x00
bAlternateSetting:    0x00
bNumEndpoints:        0x02
bInterfaceClass:      0x03 (HID)
bInterfaceSubClass:   0x00
bInterfaceProtocol:   0x00
iInterface:           0x00

HID Descriptor:
bcdHID:             0x0111
bCountryCode:         0x00
bNumDescriptors:      0x01
bDescriptorType:      0x22
wDescriptorLength:  0x00B7

Endpoint Descriptor:
bEndpointAddress:     0x81  IN
Transfer Type:   Interrupt
wMaxPacketSize:     0x0008 (8)
bInterval:            0x0A

Endpoint Descriptor:
bEndpointAddress:     0x02  OUT
Transfer Type:   Interrupt
wMaxPacketSize:     0x0008 (8)
bInterval:            0x0A

    All feedback appriciated,

    Danny

  • 0 in reply to Danny Van den Bliek
    TI__Guru** 105055 points

    Danny:

       Did you use TI EVM or your own board? Did you implement  pwoer switching and current protection? wondering if 3D spacemouse draw a lot current.

    regards

    brian

  • 0 in reply to Brian Zhou
    Prodigy 50 points

    Brian,

    I'm using my own board. It is bus powered ( \BUSPWR low ); The 3 ports all have their own powerswitch ( TPS252DBV ) and \OCPROT  is tied low.

    The 3D Spacemouse draws only 35mA, so that should not be a problem. I also tested with external power supply connected to Spacemouse, and result is the same.

    I use a 48MHz oscillator. Can it be that the jitter on the clock is to much? Or would the enumeration the already fail?

    regards,

    Danny

  • 0 in reply to Danny Van den Bliek
    TI__Guru** 105055 points

    Danny:

         Can you send schematics?

  • 0 in reply to Danny Van den Bliek
    TI__Guru** 105055 points

    will send feedback later today.

  • 0 in reply to Brian Zhou
    TI__Guru** 105055 points

    schematic looks ok, did D mouse connected to Dn2 or Dn3?

    Regadrs

    brian

  • +1 in reply to Brian Zhou
    Prodigy 50 points

    Brian,

    Yes, the 3DSpaceMouse is connected to Dn2 or Dn3, it doesn't matter. On the other port normally a trackball is connected  and the keyboard controller is normally connected fixed to Dn1.

    Is it possible that the hub has influence on how the driver works? Strange that the TUSB4041 has no influence.

    Best regards,

    Danny

  • 0 in reply to Danny Van den Bliek
    TI__Guru** 105055 points

    Danny:'

         TUSB2036 was developed based on old USB phy, we do get report it didn't work with some of the new device . TUSB4041 was developed based on new USB phy, that's the difference between them.

    Regadrs

    brian