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 --------------------- http://randomseed.org 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 > > --------------------- > http://randomseed.org > > _______________________________________________ > Pd-list@iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
