[MagicQ] PC wing starting very slowly

[Keeper of the Keys]

I'm having issues with my PC wing only being detected from time to time and starting really slow, it can be connected to my laptop running magicQ 1.4.5 (or any other version) for quite some time before it finally becomes active.

 

I usually manage to make it become active somehow, but I am also never really sure how I managed to do it, are others also having this issue, is there a solution?

 

I'm running Ubuntu 10.04, but I recall also having these issues when I was still on 9.10 and maybe even on 9.04...

[DonkiDonki]

I'm having issues with my PC wing only being detected from time to time and starting really slow, it can be connected to my laptop running magicQ 1.4.5 (or any other version) for quite some time before it finally becomes active.

 

I usually manage to make it become active somehow, but I am also never really sure how I managed to do it, are others also having this issue, is there a solution?

 

I'm running Ubuntu 10.04, but I recall also having these issues when I was still on 9.10 and maybe even on 9.04...

 

I only use Windows, but have used XP & Vista and have never encountered any issues like this, in fact it's always been rock-solid for me.

When I connect my wing you just have to wait for the self-test sequence which takes a few seconds then it is good to go.

 

Sorry I can't be more helpful with the linux version.

[Wol]

Hi,

 

What do you mean by "starting really slow"? Do you mean that it takes a while before MagicQ detects it, or that the blue sequence of LEDs on startup goes really slowly, or something else?

 

Try running "lsusb" to make sure that the OS is detecting the device straight away to try and narrow down to see if your problem is regarding the USB connection or the MagicQ connection.

 

What version of the FTDI drivers and libusb are you using currently? Run "dpkg -l | grep ftdi" and "dpkg -l | grep libusb" to show these.

[Keeper of the Keys]

Hi,

 

What do you mean by "starting really slow"? Do you mean that it takes a while before MagicQ detects it, or that the blue sequence of LEDs on startup goes really slowly, or something else?

 

Try running "lsusb" to make sure that the OS is detecting the device straight away to try and narrow down to see if your problem is regarding the USB connection or the MagicQ connection.

 

What version of the FTDI drivers and libusb are you using currently? Run "dpkg -l | grep ftdi" and "dpkg -l | grep libusb" to show these.

 

I mean that it takes a long time for MagicQ to detect the wing and make it active.

 

If I'm no mistaken it's the versions that ship with MagicQ, but I'll check later. (Though my Ubuntu install is 64bit)

 

Off by hart what I remember is that lsusb seems to show a more generic device.

 

As far as a description of what happens goes:

 

[Computer is booted and MagicQ running when wing is powered up and connected]

Wing goes on, only first blue led comes on.

 

[Wing not connected or MagicQ/computer not yet running when powered up]

Wing goes through regular startup, with the blue leds coming on one after the other and flashing when done.

MagicQ fails to respond to when the wing gets connected.

 

I will be setting it up later tonight or tomorrow morning so I'll be able to give more details.

[Keeper of the Keys]

For a while it worked a bit better, but then I git trouble again, I think I also pinpointed the problem:

 

It seems the pc-wing appears and disappears from the system, the following device keeps popping up and disappearing from lsusb:

 

Bus 003 Device 099: ID 0403:6001 Future Technology Devices International, Ltd FT

232 USB-Serial (UART) IC

 

This is some output from dmesg:

[ 637.061387] usb 3-1: new full speed USB device using ohci_hcd and address 44

[ 637.269714] ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected

[ 637.269714] usb 3-1: Detected FT232BM

[ 637.269714] usb 3-1: Number of endpoints 2

[ 637.269714] usb 3-1: Endpoint 1 MaxPacketSize 64

[ 637.269714] usb 3-1: Endpoint 2 MaxPacketSize 64

[ 637.269714] usb 3-1: Setting MaxPacketSize 64

[ 637.273418] usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0

[ 638.153465] usb 3-1: USB disconnect, address 44

[ 638.154279] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0

[ 638.154367] ftdi_sio 3-1:1.0: device disconnected

[Keeper of the Keys]

I noticed in an older linux install guide that if the system tries using the ftdi_sio driver it should be disabled which I did through blacklisting.

Now the wing shows steadily in lsusb and dmesg doesn't show any disconnect/reconnect.

 

However MagicQ is not detecting the wing either.

[Wol]

Hi,

 

Can you try running "lsusb -v" to get a verbose listing of the usb devices. Somewhere under the giant list which it produces, it should show which driver has captured the device. Also double check that you have libftdi1 installed happily. ("dpkg -L libftdi1" should show if/where the files have ended up)

[Keeper of the Keys]

Bus 003 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC

Device Descriptor:

bLength 18

bDescriptorType 1

bcdUSB 2.00

bDeviceClass 0 (Defined at Interface level)

bDeviceSubClass 0

bDeviceProtocol 0

bMaxPacketSize0 8

idVendor 0x0403 Future Technology Devices International, Ltd

idProduct 0x6001 FT232 USB-Serial (UART) IC

bcdDevice 4.00

iManufacturer 1 ChamSys

iProduct 2 MagicQ PC Wing

iSerial 3 31900072

bNumConfigurations 1

Configuration Descriptor:

bLength 9

bDescriptorType 2

wTotalLength 32

bNumInterfaces 1

bConfigurationValue 1

iConfiguration 0

bmAttributes 0xc0

Self Powered

MaxPower 0mA

Interface Descriptor:

bLength 9

bDescriptorType 4

bInterfaceNumber 0

bAlternateSetting 0

bNumEndpoints 2

bInterfaceClass 255 Vendor Specific Class

bInterfaceSubClass 255 Vendor Specific Subclass

bInterfaceProtocol 255 Vendor Specific Protocol

iInterface 2 MagicQ PC Wing

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x81 EP 1 IN

bmAttributes 2

Transfer Type Bulk

Synch Type None

Usage Type Data

wMaxPacketSize 0x0040 1x 64 bytes

bInterval 0

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x02 EP 2 OUT

bmAttributes 2

Transfer Type Bulk

Synch Type None

Usage Type Data

wMaxPacketSize 0x0040 1x 64 bytes

bInterval 0

Device Status: 0x0001

Self Powered

[Wol]

Try cat /proc/bus/usb/devices | grep ftdi?

 

Which version of MagicQ are you trying to run at the moment?

[Keeper of the Keys]

Hmmm, I don't have usb folder in /proc/bus/

 

I just now switched to 1.4.6 also since my first post I started trying Ubuntu 10.10 so I guess there may be a problem with 10.10, I'll probably be switching back to 10.04 soon (10.10 is running fairly smoothly but I hve to rule out the possibility that testing software is what is preventing me from using my wing in Linux).

 

I have managed to rule out hardware failure completely by installing magicq on a partition that had windows on it (for the purpose of getting the latest firmware into my touchscreen, sadly the company has only released genuinely good firmware for win7_64).

 

When I set 10.04 up again I will update this.

 

BTW. I am very happy that 1.4.6 now uses the whole available screen width, it makes all the buttons larger which is so much easier when using a touchscreen.

[Keeper of the Keys]

I just made a clean install of 10.04 on a different computer and hooked up my PC-wing, it seems 10.04 has the same issues that 10.10 has (and what was probably already rearing it's ugly head in 9.10).

 

The wing defaulted to ftdi_sio, which I had to blacklist, but magicQ is not detecting the wing.

If I manually modprobe ftdi_sio then magicQ eventually notices the wing on 10.04.... On 10.10 (64bit with 32bit libraries installed) it doesn't seem to ever discover it.

 

The behaviour is random, if it was some pattern that I could safely say if I do this sequence of actions I'll have a working wing in X time it wouldn't bother me so much, but it's random and unpredictable.

 

We are talking about a 32bit install of 10.04 with MagicQ 1.4.6.

ii libftdi1 0.17-1 Library to control and program the FTDI USB

 

On both systems /proc/bus/usb does not exist.

 

Edit: Maybe we shoudl move this to the bugtracker since I am seemingly the only one running into this problem/trying to run new versions of ubuntu

[Wol]

Slightly confused as to why your /proc/bus/usb doesn't exist. I'm sure it's shown up on previous installs of ubuntu that I've done!

 

You should't be using ftdi_sio at all on your system. This is the kernel level driver, which MagicQ will not reliably use. As per the install instructions, this should be blacklisted on the system for use with MagicQ.

 

Can you turn on extended logging in MagicQ, try to recreate the problem, and once youve been able to reproduce it, email across a set of the logfiles to support@chamsys.co.uk?

[Keeper of the Keys]

How do I enable extended logging?

I have straced magicq in the past but extended logging....

 

Edit: as pointed out above without ftdi_sio magicq fails to detect the wing completely, ftdi_sio on the other hand interferes with the proper boot of the wing.

[Wol]

Setup > Hardware > Extended Logging = Yes

 

the ftdi_sio driver will incorrectly capture the device upon connection, causing problems in the communications between MagicQ and the wing itself. This is why you must have it blacklisted, so that it doesn't interfere when connected. If once you fully blacklist the ftdi_sio driver, MagicQ still isn't detecting the wing, it would appear that there is a problem with your install of the libftdi drivers still present.

[Keeper of the Keys]

I think what happens is the following:

 

- Without ftdi_sio no device path is ever created for the wing, which in turn causes magicQ not to detect the wing.

- With ftdi_sio the devicepath (/dev/ttyUSB0) gets created, but it gets reset constantly, if the module is removed/added under the right circumstances (which I have not figured out yet) the resetting stops and MagicQ detects the wing (but a restart of MagicQ may be required before it gets detected).