hello,
i ll try to get the enttec dmx usb pro to work under linux ubuntu 7.10 and pd.
i followed the instructions of iohannes in dmx512 . everything compiled fine. but i am not able to open the enttec.
plugin in and dmesg:
[ 1332.756000] usb 3-1: new full speed USB device using uhci_hcd and address 3 [ 1332.952000] usb 3-1: configuration #1 chosen from 1 choice [ 1333.372000] usbcore: registered new interface driver usbserial [ 1333.372000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/usb-serial.c: USB Serial support registered for generic [ 1333.372000] usbcore: registered new interface driver usbserial_generic [ 1333.372000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/usb-serial.c: USB Serial Driver core [ 1333.404000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device [ 1333.404000] ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected [ 1333.404000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/ftdi_sio.c: Detected FT232RL [ 1333.404000] usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0 [ 1333.404000] usbcore: registered new interface driver ftdi_sio [ 1333.404000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver [ 1333.532000] dmxdev 2.6 compiled for Linux 2.6.22-15-generic Copyright (c) 1998-2005 by Michael Stickel [ 1333.532000] dmxdev: 20 universes for input / 20 universes for output [ 1333.532000] dmxdev: registration of dmx succeded [ 1333.532000] dmxdev: registration of dmxin succeded [ 1333.532000] dmxdev: proc entries created [ 1333.548000] ftdi2dmx: no version for "dmx_find_driver" found: kernel tainted. [ 1333.548000] family USB created [ 1333.548000] dmx-driver ftdi2dmx created [ 1333.548000] usbcore: registered new interface driver FTDI2DMX [ 1333.548000] /home/erich/software/dmx4linux-2.6.1/drivers/devices/usb/ftdi2dmx.c: FTDI2DMX registered.
plugin in and out again and dmesg:
[ 1639.956000] usb 3-1: USB disconnect, address 3 [ 1639.956000] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [ 1639.956000] ftdi_sio 3-1:1.0: device disconnected [ 1642.212000] usb 3-1: new full speed USB device using uhci_hcd and address 4 [ 1642.404000] usb 3-1: configuration #1 chosen from 1 choice [ 1642.408000] ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected [ 1642.408000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/ftdi_sio.c: Detected FT232RL [ 1642.408000] usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0
when u ise dmxconsole or pd and dmesg it gives an additional:
[ 1714.280000] dmxdev: opening as DMXFI_DMXOUT
but i never get the green lamp on the device blinking, so it is not initialized.
i also tried to use the dmx_usb driver from Erwin Rol also without success (it creates an additional /dev/dmx0, which i could not access).
anybody a hint how i could proceed ?
thx
erich
to give some more info:
i had success with wtf2osc which includes a python script osc2dmx.enttec.py, which is able to open my device and via osc i am able to send.
i belief the problem is that dmx512 tries to open /dev/dmx but my dmx controller is on /dev/ttyUSB0.
erich
On Thu, 20 Nov 2008, Erich Berger wrote:
hello,
i ll try to get the enttec dmx usb pro to work under linux ubuntu 7.10 and pd.
i followed the instructions of iohannes in dmx512 . everything compiled fine. but i am not able to open the enttec.
plugin in and dmesg:
[ 1332.756000] usb 3-1: new full speed USB device using uhci_hcd and address 3 [ 1332.952000] usb 3-1: configuration #1 chosen from 1 choice [ 1333.372000] usbcore: registered new interface driver usbserial [ 1333.372000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/usb-serial.c: USB Serial support registered for generic [ 1333.372000] usbcore: registered new interface driver usbserial_generic [ 1333.372000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/usb-serial.c: USB Serial Driver core [ 1333.404000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device [ 1333.404000] ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected [ 1333.404000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/ftdi_sio.c: Detected FT232RL [ 1333.404000] usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0 [ 1333.404000] usbcore: registered new interface driver ftdi_sio [ 1333.404000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver [ 1333.532000] dmxdev 2.6 compiled for Linux 2.6.22-15-generic Copyright (c) 1998-2005 by Michael Stickel [ 1333.532000] dmxdev: 20 universes for input / 20 universes for output [ 1333.532000] dmxdev: registration of dmx succeded [ 1333.532000] dmxdev: registration of dmxin succeded [ 1333.532000] dmxdev: proc entries created [ 1333.548000] ftdi2dmx: no version for "dmx_find_driver" found: kernel tainted. [ 1333.548000] family USB created [ 1333.548000] dmx-driver ftdi2dmx created [ 1333.548000] usbcore: registered new interface driver FTDI2DMX [ 1333.548000] /home/erich/software/dmx4linux-2.6.1/drivers/devices/usb/ftdi2dmx.c: FTDI2DMX registered.
plugin in and out again and dmesg:
[ 1639.956000] usb 3-1: USB disconnect, address 3 [ 1639.956000] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [ 1639.956000] ftdi_sio 3-1:1.0: device disconnected [ 1642.212000] usb 3-1: new full speed USB device using uhci_hcd and address 4 [ 1642.404000] usb 3-1: configuration #1 chosen from 1 choice [ 1642.408000] ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected [ 1642.408000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/ftdi_sio.c: Detected FT232RL [ 1642.408000] usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0
when u ise dmxconsole or pd and dmesg it gives an additional:
[ 1714.280000] dmxdev: opening as DMXFI_DMXOUT
but i never get the green lamp on the device blinking, so it is not initialized.
i also tried to use the dmx_usb driver from Erwin Rol also without success (it creates an additional /dev/dmx0, which i could not access).
anybody a hint how i could proceed ?
thx
erich
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
hi
Erich Berger wrote:
to give some more info:
i had success with wtf2osc which includes a python script osc2dmx.enttec.py, which is able to open my device and via osc i am able to send.
i belief the problem is that dmx512 tries to open /dev/dmx but my dmx controller is on /dev/ttyUSB0.
this is helpful.
my external will not work directly with a serial port. it uses the dmx4linux api, which is accessed via /dev/dmx[0-9]* by default [dmxout] will just try to connect to /dev/dmx, but you can change that by setting the environmental variable "DMX" to a more appropriate value.
% export DMX=/dev/dmx0 % pd
so also
% export DMX=/dev/ttyUSB0
would work ?
erich
On Fri, 21 Nov 2008, IOhannes m zmoelnig wrote:
hi
Erich Berger wrote:
to give some more info:
i had success with wtf2osc which includes a python script osc2dmx.enttec.py, which is able to open my device and via osc i am able to send.
i belief the problem is that dmx512 tries to open /dev/dmx but my dmx controller is on /dev/ttyUSB0.
this is helpful.
my external will not work directly with a serial port. it uses the dmx4linux api, which is accessed via /dev/dmx[0-9]* by default [dmxout] will just try to connect to /dev/dmx, but you can change that by setting the environmental variable "DMX" to a more appropriate value.
% export DMX=/dev/dmx0 % pd
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
thx iohannes for your help and suggestions !
if /dev/ttyUSB0 is a dmx device (which i doubt; according to its name it should be a serial device), then it will work.
its a serial device and it did not work as you doubted.
maybe it works with the erwin rol drivers.
no, i tried them, i got the device attached to /dev/dmx0 but even i exported DMX to /dev/dmx0 and took care of the rights i get nothing through (also blacklisted all the other modules which might interfere)
still - it works with wtf2dmx and osc - so at least i can work with it.
thx
erich
fgmadr IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Erich Berger wrote:
no, i tried them, i got the device attached to /dev/dmx0 but even i exported DMX to /dev/dmx0 and took care of the rights i get nothing through (also blacklisted all the other modules which might interfere)
when i worked with DMX (only once and not with an enttec) it was crucial to plug in the device after the system had booted. else it would just freeze (no matter how i tried to blacklist and/or remove offending modules)
while it was ugly, it was acceptable as in this special case it was guaranteed that the machine never had to reboot without human watchmen....
still - it works with wtf2dmx and osc - so at least i can work with it.
good.
fgamsdr IOhannes
when i worked with DMX (only once and not with an enttec) it was crucial to plug in the device after the system had booted. else it would just freeze (no matter how i tried to blacklist and/or remove offending modules)
while it was ugly, it was acceptable as in this special case it was guaranteed that the machine never had to reboot without human watchmen....
i actually have to plug it in twice :-) otherwise it would not attach to /dev/ttyUSB0
erich
-
Erich Berger -
IOhannes m zmoelnig