Device ttyUSB disconnects all the time: Massimo image

[stef35]

Hello All

I would need some help with an ENTTEC Open DMX USB connected to a RPi
As soon as i try to load this device in the configuration tab in Web interface, i have got the following message in /var/log/messages and nothing works properley. I use the Massimo RPi image, a RPI 1 and 2 and a powered USB Hub.

Sep 16 00:10:13 raspberry-pi kernel: [ 664.696753] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Sep 16 00:10:13 raspberry-pi kernel: [ 664.709472] ftdi_sio 1-1.3.1:1.0: device disconnected

Thank you for any idea

[stef35]

By the way, could someone who has an ENTTEC open dmx device tell me if he has the same diconnect message when he just plugs the enttec device to RPi, whitout plugging the led par? Linking the DMX USB device to the Universe with web interface just disconnects the ttyUSB in my case.

I am wondering if i do the right tests to try to spot where the pb comes from? Maybe the enttec device is no auto-terminated

thanks

[pfcl.sound]

Hi,

I'm use RPI2 with enttec open dmx,usb mouse, usb keyboard, hdmi out to monitor, web access, it's all working fine.

Kai

[stef35]

thanks kai for your answer
could you please make a test for me?
disconnect the DMX wire from the enttec box and in the web interface, change the output device from anyone, go to another page, and come back to the dmx output.
Doing so, i get some disconnected message in my log (open a ssh connexion and run dmesg)

Is that the case as well for you?

thanks in advance

Hi,

I'm use RPI2 with enttec open dmx,usb mouse, usb keyboard, hdmi out to monitor, web access, it's all working fine.

Kai

[pfcl.sound]

Ok, I'm try to check all your requirement today and maybe I'm try to record video it's for you.

KAI

thanks kai for your answer
could you please make a test for me?
disconnect the DMX wire from the enttec box and in the web interface, change the output device from anyone, go to another page, and come back to the dmx output.
Doing so, i get some disconnected message in my log (open a ssh connexion and run dmesg)

Is that the case as well for you?

thanks in advance

Hi,

I'm use RPI2 with enttec open dmx,usb mouse, usb keyboard, hdmi out to monitor, web access, it's all working fine.

Kai

[stef35]

well, it does not come from my led par, as i just test my config with a new one
i have swapped as well the XLR wire (i use standard one, no dmx specific one, i hope it does not come from this: the thing is that it was working fine for a while ;-(
idem for usb wire

i am thinking about changing my usb/dmx device, it is my last chance to get it work
By the way, do you use XLR terminator in your config?

[stef35]

It has been resolved by changing the USB DMX box.
But the strange thing is i still have some messages about disconnecting ttyUSB and i don't have the /dev/ttyUSB0 ?!!!

[mcallegari]

The disconnection message is normal and it happens also on a Linux PC.

Here's my Enttec MK2 dmesg output:

Code: Select all

[85713.427351] usb 2-1.1: new full-speed USB device number 11 using ehci-pci
[85713.527212] usb 2-1.1: New USB device found, idVendor=0403, idProduct=6001
[85713.527220] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[85713.527223] usb 2-1.1: Product: DMX USB PRO Mk2
[85713.527226] usb 2-1.1: Manufacturer: ENTTEC
[85713.527229] usb 2-1.1: SerialNumber: ...
[85713.530121] ftdi_sio 2-1.1:1.0: FTDI USB Serial Device converter detected
[85713.530171] usb 2-1.1: Detected FT232RL
[85713.530175] usb 2-1.1: Number of endpoints 2
[85713.530177] usb 2-1.1: Endpoint 1 MaxPacketSize 64
[85713.530180] usb 2-1.1: Endpoint 2 MaxPacketSize 64
[85713.530183] usb 2-1.1: Setting MaxPacketSize 64
[85713.530686] usb 2-1.1: FTDI USB Serial Device converter now attached to ttyUSB0
[85750.839445] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[85750.839865] ftdi_sio 2-1.1:1.0: device disconnected

@85750 is when QLC+ opens the DMX USB plugin.
That doesn't mean the device is not working properly.
Since QLC+ uses libftdi the message is probably when the library (or libusb) takes control of the device.
Again, this is normal.