Connect Eurolite USB-DMX512-Pro to ola

733 views
Skip to first unread message

Felix N

unread,
Dec 26, 2018, 12:20:48 AM12/26/18
to open-lighting
Hello everyone,

I recently got the Eurolite USB-DMX512-Pro interface and was able to use it in FreeStyler (Windows) successfully.

Seeing the great potential, I am trying to connect the adapter to ola, but I am struggling to do so at the moment even though it is suggested the device is supported by the framework (https://www.openlighting.org/ola/getting-started/device-specific-configuration/#Eurolite_USB_DMX512_PRO)

I installed ola from git as described here: https://www.openlighting.org/ola/linuxinstall/#Git

I was also able to start it and access via the localhost web admin. However when trying to define my first universe, the list of available ports remains empty.
Setting the stated udev rule and also adding my user to plugdev and dialout group did not help. (was suggested here: http://opendmx.net/index.php/The_Newbie_Guide_for_OLA_on_Ubuntu)

I honestly also lack some basic understanding of the plugins, too:
Does the visibility of the device depend on the plugin activated?
What plugins do I need to access my adapter?
I already tried all the different USB-plugins without any success.

Trying to avoid the web app did not work either. When trying to set up a universe via terminal as described here: https://www.openlighting.org/ola/getting-started/using-ola/
the command "ola_dev_info" returns:
common/network/TCPSocket.cpp:158: connect(127.0.0.1:9010): Connection refused

I find it hard to find the right approach on the website, can anyone help me please?

Thanks in advance and best regards,

Felix

Peter Newman

unread,
Dec 26, 2018, 8:03:37 AM12/26/18
to open-lighting
Hi Felix,

There's another example udev rule here for this device (embarrassingly I didn't realise until recently that the other page existed; we need to work on improving our wiki/website links):

The device is available via the usbdmx plugin:

You don't say explicitly, but I'm guessing you're on Ubuntu or Debian, if you're on a fairly recent one (18.04 onwards) I'd generally recommend just installing via apt ("sudo apt-get install ola") as it's a lot simpler, although you probably want to remove your local install first.

Does the visibility of the device depend on the plugin activated?
Yes, the plugin that controls that device needs enabling, and then (in the case of most USB ones) the device will be detected on the machine and listed as an available port.

What plugins do I need to access my adapter?
The usbdmx plugin.

I already tried all the different USB-plugins without any success.
That suggests another issue then.

Trying to avoid the web app did not work either. When trying to set up a universe via terminal as described here: https://www.openlighting.org/ola/getting-started/using-ola/
the command "ola_dev_info" returns:
common/network/TCPSocket.cpp:158: connect(127.0.0.1:9010): Connection refused

That's odd, that error suggests olad isn't running, had you started the olad daemon?

So the next steps in terms of troubleshooting will be lsusb output please and also olad -l 4 output:

Felix N

unread,
Dec 26, 2018, 11:22:33 AM12/26/18
to open-lighting
Hi Peter,

Thanks for the quick response.
I work with Ubuntu 16.04.
 
 
I am already using this one.

The device is available via the usbdmx plugin:

I was just trying to disable all plugins except the usbdmx one, but it is still not working.


You don't say explicitly, but I'm guessing you're on Ubuntu or Debian

Yes, I work on Ubuntu 16.04

the command "ola_dev_info" returns:
common/network/TCPSocket.cpp:158: connect(127.0.0.1:9010): Connection refused

That's odd, that error suggests olad isn't running, had you started the olad daemon?

My bad, the error only occurs when olad isn't running. When olad is running the terminal where i ran the "ola_dev_info" command in does not return anything, instead the olad terminal returns:
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 31, events 2001, descriptor: 0x113f540
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 31

So the next steps in terms of troubleshooting will be lsusb output please and also olad -l 4 output:

Below is the lsusb output:

felix@felix-desktop:~/ola$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 004: ID 0bda:57cc Realtek Semiconductor Corp.
Bus 001 Device 003: ID 0489:e09f Foxconn / Hon Hai
Bus 001 Device 002: ID 0781:5583 SanDisk Corp.
Bus 001 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

This is the one which disappears when i unplug the usb-adapter:
Bus 001 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC


Below is the olad -l 4 output without all the loading stuff and the ss process time messages for better readability:

felix@felix-desktop:~/ola$ olad -l 4
olad/Olad.cpp:98: OLA Daemon version 0.10.7
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 5, events 2001, descriptor: 0x1ee5860
olad/OlaDaemon.cpp:121: Using configs in /home/felix/.ola
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 8, events 2001, descriptor: 0x1ede3f0
common/thread/Thread.cpp:200: Thread pref-saver, policy SCHED_OTHER, priority 0
common/rdm/PidStoreLoader.cpp:282: Loading BACKGROUND_QUEUED_STATUS_POLICY

[A TON OF OTHER LOADING STUFF JUST LIKE THE LINE ABOVE]

common/rdm/PidStoreLoader.cpp:221: Load Complete
common/network/PosixInterfacePicker.cpp:168: Skipping lo because it's a loopback
common/network/PosixInterfacePicker.cpp:256: Found: wlp3s0, 192.168.1.19, 30:f7:72:2f:15:bd
common/network/InterfacePicker.cpp:92: Using interface wlp3s0 (192.168.1.19)
olad/OlaServer.cpp:194: Server UID is 7a70:1301a8c0
olad/OlaServer.cpp:206: Server instance name is OLA Server
olad/plugin_api/Preferences.cpp:436: Missing /home/felix/.ola/ola-universe.conf: No such file or directory - this isn't an error, we'll just use the defaults
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 10, events 2001, descriptor: 0x1edcd60
olad/AvahiDiscoveryAgent.cpp:201: Client state changed to AVAHI_CLIENT_S_RUNNING
common/thread/Thread.cpp:200: Thread http, policy SCHED_OTHER, priority 0
common/http/HTTPServer.cpp:510: HTTP Server started on port 9090
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 14, events 2001, descriptor: 0x1efbcd0
olad/AvahiDiscoveryAgent.cpp:236: State for OLA Server._http._tcp,_ola, group 0x1efbf30 changed to AVAHI_ENTRY_GROUP_UNCOMMITED
olad/AvahiDiscoveryAgent.cpp:334: Adding _ola._sub._http._tcp
olad/AvahiDiscoveryAgent.cpp:342: Failed to add _ola._sub._http._tcp
olad/OlaServer.cpp:481: Updated PID definitions.
olad/AvahiDiscoveryAgent.cpp:236: State for OLA Server._http._tcp,_ola, group 0x1efbf30 changed to AVAHI_ENTRY_GROUP_REGISTERING
olad/OlaServer.cpp:489: PID store is at 0x20289b0
common/thread/Thread.cpp:200: Thread signal-thread, policy SCHED_OTHER, priority 0
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 22, events 2001, descriptor: 0x2019bd0
olad/PluginManager.cpp:73: Skipping ArtNet because it was disabled
olad/PluginManager.cpp:73: Skipping Dummy because it was disabled
olad/PluginManager.cpp:73: Skipping E1.31 (sACN) because it was disabled
olad/PluginManager.cpp:73: Skipping ESP Net because it was disabled
olad/PluginManager.cpp:73: Skipping GPIO because it was disabled
olad/PluginManager.cpp:73: Skipping KarateLight because it was disabled
olad/PluginManager.cpp:73: Skipping KiNET because it was disabled
olad/PluginManager.cpp:73: Skipping Milford Instruments because it was disabled
olad/PluginManager.cpp:73: Skipping Nanoleaf because it was disabled
olad/PluginManager.cpp:73: Skipping Enttec Open DMX because it was disabled
olad/PluginManager.cpp:73: Skipping Open Pixel Control because it was disabled
olad/PluginManager.cpp:73: Skipping OSC because it was disabled
olad/PluginManager.cpp:73: Skipping Renard because it was disabled
olad/PluginManager.cpp:73: Skipping SandNet because it was disabled
olad/PluginManager.cpp:73: Skipping ShowNet because it was disabled
olad/PluginManager.cpp:73: Skipping SPI because it was disabled
olad/PluginManager.cpp:73: Skipping SPI native DMX because it was disabled
olad/PluginManager.cpp:73: Skipping StageProfi because it was disabled
olad/PluginManager.cpp:73: Skipping Serial USB because it was disabled
olad/PluginManager.cpp:73: Skipping Pathport because it was disabled
olad/PluginManager.cpp:73: Skipping FTDI USB DMX because it was disabled
olad/PluginManager.cpp:73: Skipping UART native DMX because it was disabled
olad/PluginManager.cpp:195: Trying to start USB
libs/usb/HotplugAgent.cpp:89: libusb_set_debug(0)
libs/usb/HotplugAgent.cpp:94: HotplugSupported(): 1
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 2:1 @0x1f0ae40 [add]
plugins/usbdmx/AsyncPluginImpl.cpp:303: USB device added, checking for widget support, vendor 0x1d6b, product 0x0003
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:5 @0x1f0a990 [add]
plugins/usbdmx/AsyncPluginImpl.cpp:303: USB device added, checking for widget support, vendor 0x0bda, product 0x0129
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:4 @0x1f0a4e0 [add]
plugins/usbdmx/AsyncPluginImpl.cpp:303: USB device added, checking for widget support, vendor 0x0bda, product 0x57cc
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:3 @0x1f0a030 [add]
plugins/usbdmx/AsyncPluginImpl.cpp:303: USB device added, checking for widget support, vendor 0x0489, product 0xe09f
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:2 @0x1f09b80 [add]
plugins/usbdmx/AsyncPluginImpl.cpp:303: USB device added, checking for widget support, vendor 0x0781, product 0x5583
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:7 @0x1f812a0 [add]
plugins/usbdmx/AsyncPluginImpl.cpp:303: USB device added, checking for widget support, vendor 0x0403, product 0x6001
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:1 @0x1f81200 [add]
plugins/usbdmx/AsyncPluginImpl.cpp:303: USB device added, checking for widget support, vendor 0x1d6b, product 0x0002
libs/usb/LibUsbThread.cpp:50: -- Starting libusb thread
common/thread/Thread.cpp:200: Thread , policy SCHED_OTHER, priority 0
libs/usb/LibUsbThread.cpp:35: ----libusb event thread is running
olad/PluginManager.cpp:200: Started USB
olad/AvahiDiscoveryAgent.cpp:236: State for OLA Server._http._tcp,_ola, group 0x1efbf30 changed to AVAHI_ENTRY_GROUP_ESTABLISHED
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 31, events 2001, descriptor: 0x2017a90
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 31
^Ccommon/thread/SignalThread.cpp:115: Received signal: Interrupt
common/http/HTTPServer.cpp:537: Notifying HTTP server thread to stop
common/http/HTTPServer.cpp:539: Waiting for HTTP server thread to exit
common/http/HTTPServer.cpp:541: HTTP server thread exited
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 14
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 10
libs/usb/LibUsbThread.cpp:55: -- Stopping libusb thread
libs/usb/LibUsbThread.cpp:45: ----libusb thread exiting
felix@felix-desktop:~/ola$

Peter Newman

unread,
Dec 26, 2018, 11:50:46 AM12/26/18
to open-lighting
Hi Felix,

This might sound a bit odd but are you sure that's the device you have? The ones we have seen before are vendor 0x04d8 and product 0xfa63, but what you've got is
0x0403 and 0x6001 which is a standard FTDI device.

Can we see "lsusb -v" for that device please?

This sounds like it may be relevant, I'd give the steps in that a go and post your latest olad -l 4 (with the USB Serial plugin instead):

Felix N

unread,
Dec 26, 2018, 12:20:10 PM12/26/18
to open-lighting
Hi Peter,


This might sound a bit odd but are you sure that's the device you have? The ones we have seen before are vendor 0x04d8 and product 0xfa63, but what you've got is
0x0403 and 0x6001 which is a standard FTDI device.

I appreciate that you think of odd solutions! I am pretty sure thats the device I have. This link is not quite where i bought it but it looks exactly the same: https://www.conrad.de/de/eurolite-usb-dmx512-pro-mk2-dmx-interface-1519482.html

 
Can we see "lsusb -v" for that device please?

Here you go:

Bus 001 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            6.00
  iManufacturer           1 FTDI
  iProduct                2 FT232R USB UART
  iSerial                 3 AK069R3T
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower               90mA
    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 FT232R USB UART
      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:     0x0000
  (Bus Powered)


This sounds like it may be relevant, I'd give the steps in that a go and post your latest olad -l 4 (with the USB Serial plugin instead):

 See the new (cleaned) olad -l 4 output below:

felix@felix-desktop:~/ola$ olad -l 4
olad/Olad.cpp:98: OLA Daemon version 0.10.7
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 5, events 2001, descriptor: 0x1301860

olad/OlaDaemon.cpp:121: Using configs in /home/felix/.ola
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 8, events 2001, descriptor: 0x12fa3f0

common/thread/Thread.cpp:200: Thread pref-saver, policy SCHED_OTHER, priority 0
common/rdm/PidStoreLoader.cpp:282: Loading BACKGROUND_QUEUED_STATUS_POLICY
[LOADING STUFF]

common/rdm/PidStoreLoader.cpp:221: Load Complete
common/network/PosixInterfacePicker.cpp:168: Skipping lo because it's a loopback
common/network/PosixInterfacePicker.cpp:256: Found: wlp3s0, 192.168.1.19, 30:f7:72:2f:15:bd
common/network/InterfacePicker.cpp:92: Using interface wlp3s0 (192.168.1.19)
olad/OlaServer.cpp:194: Server UID is 7a70:1301a8c0
olad/OlaServer.cpp:206: Server instance name is OLA Server
olad/plugin_api/Preferences.cpp:436: Missing /home/felix/.ola/ola-universe.conf: No such file or directory - this isn't an error, we'll just use the defaults
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 10, events 2001, descriptor: 0x12f8d60

olad/AvahiDiscoveryAgent.cpp:201: Client state changed to AVAHI_CLIENT_S_RUNNING
common/thread/Thread.cpp:200: Thread http, policy SCHED_OTHER, priority 0
common/http/HTTPServer.cpp:510: HTTP Server started on port 9090
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 14, events 2001, descriptor: 0x1317d50
olad/AvahiDiscoveryAgent.cpp:236: State for OLA Server._http._tcp,_ola, group 0x1317fb0 changed to AVAHI_ENTRY_GROUP_UNCOMMITED

olad/AvahiDiscoveryAgent.cpp:334: Adding _ola._sub._http._tcp
olad/AvahiDiscoveryAgent.cpp:342: Failed to add _ola._sub._http._tcp
olad/OlaServer.cpp:481: Updated PID definitions.
olad/OlaServer.cpp:489: PID store is at 0x14449b0
olad/AvahiDiscoveryAgent.cpp:236: State for OLA Server._http._tcp,_ola, group 0x1317fb0 changed to AVAHI_ENTRY_GROUP_REGISTERING

common/thread/Thread.cpp:200: Thread signal-thread, policy SCHED_OTHER, priority 0
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 22, events 2001, descriptor: 0x1431920

olad/PluginManager.cpp:73: Skipping ArtNet because it was disabled
olad/PluginManager.cpp:73: Skipping Dummy because it was disabled
olad/PluginManager.cpp:73: Skipping E1.31 (sACN) because it was disabled
olad/PluginManager.cpp:73: Skipping ESP Net because it was disabled
olad/PluginManager.cpp:73: Skipping GPIO because it was disabled
olad/PluginManager.cpp:73: Skipping KarateLight because it was disabled
olad/PluginManager.cpp:73: Skipping KiNET because it was disabled
olad/PluginManager.cpp:73: Skipping Milford Instruments because it was disabled
olad/PluginManager.cpp:73: Skipping Nanoleaf because it was disabled
olad/PluginManager.cpp:73: Skipping Enttec Open DMX because it was disabled
olad/PluginManager.cpp:73: Skipping Open Pixel Control because it was disabled
common/io/EPoller.cpp:306: ss process time was 0.000001

olad/PluginManager.cpp:73: Skipping OSC because it was disabled
common/io/EPoller.cpp:306: ss process time was 0.000000

olad/PluginManager.cpp:73: Skipping Renard because it was disabled
olad/PluginManager.cpp:73: Skipping SandNet because it was disabled
olad/PluginManager.cpp:73: Skipping ShowNet because it was disabled
common/io/EPoller.cpp:306: ss process time was 0.000001

olad/PluginManager.cpp:73: Skipping SPI because it was disabled
olad/PluginManager.cpp:73: Skipping SPI native DMX because it was disabled
olad/PluginManager.cpp:73: Skipping StageProfi because it was disabled
olad/PluginManager.cpp:73: Skipping USB because it was disabled

olad/PluginManager.cpp:73: Skipping Pathport because it was disabled
olad/PluginManager.cpp:73: Skipping FTDI USB DMX because it was disabled
olad/PluginManager.cpp:73: Skipping UART native DMX because it was disabled
olad/PluginManager.cpp:195: Trying to start Serial USB

common/thread/Thread.cpp:200: Thread , policy SCHED_OTHER, priority 0
plugins/usbpro/WidgetDetectorThread.cpp:215: Found potential USB Serial device at /dev/ttyUSB0
common/io/Serial.cpp:158: Checking for /var/lock/LCK..ttyUSB0
common/io/Serial.cpp:199: Acquired /var/lock/LCK..ttyUSB0
plugins/usbpro/WidgetDetectorThread.cpp:221: New descriptor @ 0x7f03c8000c90 for /dev/ttyUSB0
plugins/usbpro/WidgetDetectorThread.cpp:384: trying stage 0 for 0x7f03c8000c90
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 24, events 2001, descriptor: 0x7f03c8008cd0
olad/PluginManager.cpp:200: Started Serial USB
plugins/usbpro/UsbProWidgetDetector.cpp:323: USB Widget didn't respond to messages, esta id 0, device id 0
plugins/usbpro/UsbProWidgetDetector.cpp:326: Is device in USB Controller mode if it's a Goddard?
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 24
plugins/usbpro/WidgetDetectorThread.cpp:384: trying stage 1 for 0x7f03c8000c90
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 24, events 2001, descriptor: 0x7f03c8000d40
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 24
plugins/usbpro/WidgetDetectorThread.cpp:381: no more detectors to try for  0x7f03c8000c90
common/io/Serial.cpp:247: Released /var/lock/LCK..ttyUSB0
olad/AvahiDiscoveryAgent.cpp:236: State for OLA Server._http._tcp,_ola, group 0x1317fb0 changed to AVAHI_ENTRY_GROUP_ESTABLISHED
plugins/usbpro/WidgetDetectorThread.cpp:215: Found potential USB Serial device at /dev/ttyUSB0
common/io/Serial.cpp:158: Checking for /var/lock/LCK..ttyUSB0
common/io/Serial.cpp:199: Acquired /var/lock/LCK..ttyUSB0
plugins/usbpro/WidgetDetectorThread.cpp:221: New descriptor @ 0x7f03c80014b0 for /dev/ttyUSB0
plugins/usbpro/WidgetDetectorThread.cpp:384: trying stage 0 for 0x7f03c80014b0
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 27, events 2001, descriptor: 0x7f03c8000d10
plugins/usbpro/UsbProWidgetDetector.cpp:323: USB Widget didn't respond to messages, esta id 0, device id 0
plugins/usbpro/UsbProWidgetDetector.cpp:326: Is device in USB Controller mode if it's a Goddard?
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 27
plugins/usbpro/WidgetDetectorThread.cpp:384: trying stage 1 for 0x7f03c80014b0
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 27, events 2001, descriptor: 0x7f03c80012f0
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 27
plugins/usbpro/WidgetDetectorThread.cpp:381: no more detectors to try for  0x7f03c80014b0
common/io/Serial.cpp:247: Released /var/lock/LCK..ttyUSB0

^Ccommon/thread/SignalThread.cpp:115: Received signal: Interrupt
common/http/HTTPServer.cpp:537: Notifying HTTP server thread to stop
common/http/HTTPServer.cpp:539: Waiting for HTTP server thread to exit
common/http/HTTPServer.cpp:541: HTTP server thread exited
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 14
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 10
felix@felix-desktop:~/ola$

Thanks alot for your help

Peter Newman

unread,
Dec 26, 2018, 12:32:32 PM12/26/18
to open-lighting
Thanks Felix, your link jogged my memory a bit more. See here:

How's your C++, fancy cloning that and fixing the remaining comments so we can merge it into mainline?

Felix N

unread,
Dec 26, 2018, 1:24:18 PM12/26/18
to open-lighting
Hi Peter,

My C++ is not great but not bad either.
The pull still did nothing for me though, so I do not really know where to start.
I pulled and ran the make commands again. Is there something else to do in order to apply the changes to the plugin?

Felix N

unread,
Dec 26, 2018, 1:30:17 PM12/26/18
to open-lighting
However now the device gets recognized by its correct type:

olad/PluginManager.cpp:195: Trying to start USB
libs/usb/HotplugAgent.cpp:89: libusb_set_debug(0)
libs/usb/HotplugAgent.cpp:94: HotplugSupported(): 1
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 2:1 @0x161fe40 [add]

plugins/usbdmx/AsyncPluginImpl.cpp:303: USB device added, checking for widget support, vendor 0x1d6b, product 0x0003
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:6 @0x161f990 [add]

plugins/usbdmx/AsyncPluginImpl.cpp:303: USB device added, checking for widget support, vendor 0x0bda, product 0x0129
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:5 @0x161f4e0 [add]

plugins/usbdmx/AsyncPluginImpl.cpp:303: USB device added, checking for widget support, vendor 0x0bda, product 0x57cc
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:4 @0x161f030 [add]

plugins/usbdmx/AsyncPluginImpl.cpp:303: USB device added, checking for widget support, vendor 0x0489, product 0xe09f
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:3 @0x161eb80 [add]

plugins/usbdmx/AsyncPluginImpl.cpp:303: USB device added, checking for widget support, vendor 0x0781, product 0x5583
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:15 @0x16962a0 [add]

plugins/usbdmx/AsyncPluginImpl.cpp:303: USB device added, checking for widget support, vendor 0x0403, product 0x6001
plugins/usbdmx/EuroliteProFactory.cpp:72: Found a new Eurolite USB-DMX512-PRO MK2 device  <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
libs/usb/LibUsbAdaptor.cpp:68: Failed to open libusb device: 0x16962a0: LIBUSB_ERROR_ACCESS
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:1 @0x1696200 [add]

plugins/usbdmx/AsyncPluginImpl.cpp:303: USB device added, checking for widget support, vendor 0x1d6b, product 0x0002
libs/usb/LibUsbThread.cpp:50: -- Starting libusb thread
common/thread/Thread.cpp:200: Thread , policy SCHED_OTHER, priority 0
libs/usb/LibUsbThread.cpp:35: ----libusb event thread is running
olad/PluginManager.cpp:200: Started USB
common/io/EPoller.cpp:306: ss process time was 0.000002
olad/AvahiDiscoveryAgent.cpp:236: State for OLA Server._http._tcp,_ola, group 0x1610f30 changed to AVAHI_ENTRY_GROUP_ESTABLISHED

Peter Newman

unread,
Dec 26, 2018, 1:44:02 PM12/26/18
to open-lighting
That's potentially promising, but doesn't really prove anything until you sort the permissions issue.

What does ls -al of /dev/ show for your device, or try replugging/rebooting after you added the udev rule? Are you running olad as the same user you added the udev rule to give permissions to?

Felix N

unread,
Dec 26, 2018, 6:44:08 PM12/26/18
to open-lighting
I solved the permission issue!!!
Setting the udev rule right did the trick (see below).
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"
In case I understood correctly, this basically allows each and everyone to access all usb_devices.
I might fix the security risk opened by this in the future though...
Some other rule (deleted now) was lying around in the same folder which seemed to have overwritten the rule above in some way.

Now the device gets listed as an output port and can be added to my very first ola universe :)
Fiddling with the sliders of the dmx console makes the status LED on the addapter turn green which indicates successfully incoming signals.

Hint for other newbs like me getting desperate in the wiki:
olad cannot be run as root, so the permissions of every new usb device, which is automatically only allowed to be accessed by root at first, need to be adapted.

Thanks so much for your time, patience and new ideas!!!
Would'nt have worked without you.
I will try to connect my actual light soon. Wish me luck :)

Peter Newman

unread,
Dec 26, 2018, 8:12:32 PM12/26/18
to open-lighting
Glad you worked around it Felix. As you say, there's probably a more subtle option somewhere in between, or it ought to be possible to make our one listed on the wiki work (indeed it's probably as simple as changing the vendor and product ID's to match, although thinking about it, there's probably another parallel rule for AMA type interfaces or something that you can probably leverage, rather than needing to rewrite):

That sounds rather promising, as you say, a light will be the proof, and the smoothness of fades is generally the acid test.

Assuming that all works, I'd really appreciate it if you wouldn't mind adding the default disable option to the Mk2, then we can merge the pull request and support for it will "just work" in future versions of OLA. If you look at the DMXCProjectsNodleU1 within the same plugin that shows some code for accessing our preferences from within a Factory, which is where the change needs to be made, I'm happy to help where I can. For why I haven't just done it myself see here:

And for the bitter proof, this Pull Request, which is still awaiting someone with a different device assisting troubleshooting:

Gunther Seiser

unread,
Jul 10, 2020, 2:28:48 AM7/10/20
to open-lighting
Hi,

I tried for several hours to get the eurolite usb dmx512 pro mk2 working with no success. I tried the method described in the manual as a FTDI device, with udev rules etc, The device was ready to get plugged in into a universe in OLA, but desg showed me that the device was disconnected.

Second try was to install it as usbdmx plugin, as described in the openlighting docs (http://docs.openlighting.org/ola/conf/ola-usbdmx.conf.html). It didn't show up as a device in OLA.

Could somebody please summarize the correct method to get the eurolite usb dmx mk2 to work with OLA? Obviously I missed something essential...
(one thing that adds the confusion is when I search, I get results dated from 2011 to 2018, I'm not sure which one is still valid and which not)
Thanks, gunther (user of OLA since 5 years with enttec, dmxking and artnet)

Peter Newman

unread,
Jul 12, 2020, 7:32:53 AM7/12/20
to open-lighting
Hi Gunther,

You'll need to add (or edit if already present) this line in your ola-usbdmx.conf:
enable_eurolite_mk2 = true

To get this to work you need OLA 0.11.0 which hasn't yet been released, so you'll need to build OLA from our master branch. You don't specify your OS, but you can install most of the dependencies using the package managers, so you just need to compile OLA itself.

If it's still not working, please can we have -l 4 logs:

Gunther Seiser

unread,
Jul 12, 2020, 1:19:23 PM7/12/20
to open-lighting
Hi Peter,

thanks for your reply. I'm on the way to build OLA 0.11.0 on my fresh installed Raspberry Pi-4.

At the moment I hang at the configure error: cannot find the protoc header files
checking protoc version... 3.6.1
checking google/protobuf/compiler/command_line_interface.h usability... no
checking google/protobuf/compiler/command_line_interface.h presence... no checking for google/protobuf/compiler/command_line_interface.h... no configure: error: Cannot find the protoc header files
I found an issue (#1463) on Github/openlightingproject/ola, which seems to cover the same error, but I don't understand what I could possibly do???

Peter Newman

unread,
Jul 12, 2020, 6:02:41 PM7/12/20
to open-lighting
If you're building master, then the issue you linked to is long gone.

Can you share your config.log?

Are you sure you've got libprotoc-dev installed?

Gunther Seiser

unread,
Jul 13, 2020, 3:39:16 AM7/13/20
to open-lighting
Hello Peter,

libprotoc-dev was missing.

I used git clone https://github.com/OpenLightingProject/ola to get the project from Git. I suppose this should be the master branch.

I got compiled and installed OLA now. In the web page (127.0.0.1:9090) I get version number 0.10.7 ??? 
Other questions arise: I don't have ./ola/ola-osc.conf, ola-usbdmx.conf

Anyway, here is my log file...
ola_l4_log.txt

Peter Newman

unread,
Jul 13, 2020, 9:44:32 AM7/13/20
to open-lighting
See inline

On Monday, 13 July 2020 at 08:39:16 UTC+1 gunther....@gmail.com wrote:
Hello Peter,

libprotoc-dev was missing.

I used git clone https://github.com/OpenLightingProject/ola to get the project from Git. I suppose this should be the master branch.
That would indeed be!

I got compiled and installed OLA now. In the web page (127.0.0.1:9090) I get version number 0.10.7 ??? 
Yeah we don't number the master branch so you just get the latest released version number.
 
Other questions arise: I don't have ./ola/ola-osc.conf, ola-usbdmx.conf
Can we see your config.log, it sounds like you didn't have dependencies for those plugins installed when building it. Try installing these packages too and recompiling "libftdi-dev libftdi1 libusb-1.0-0-dev liblo-dev libavahi-client-dev".

Anyway, here is my log file...
Can you just check you don't have another olad on your machine, what does "which olad" show? And "sudo updatedb && locate olad"? Did you do a make install?

Gunther Seiser

unread,
Jul 14, 2020, 9:39:37 AM7/14/20
to open-lighting
Hi Peter,

thank you for taking me by the hand and guiding me through the make process! I finally got it working. Maybe it's helpful to others, if I sum up the steps I took?

So here are my notes during installation of OLA 0.11:

sudo apt-get install git

git clone https://github.com/OpenLightingProject/ola.git ola

cd ola


(Error: could not resolve host..., therfore:)

git config --global --unset http.proxy

git config --global --unset http.proxy


sudo apt-get install autoconf libtool bison flex uuid-dev libcppunit-dev

sudo apt-get install libmicrohttpd-dev protobuf-compiler libprotobuf-dev python-protobuf

sudo apt-get install libftdi-dev liblo-dev libavahi-client-dev libprotoc-dev

sudo apt-get install libusb-1.0.0-dev libcurses5-dev pkg-config liblo

autoreconf -i 

./configure (optionally: --enable-rdm-tests --enable-python-libs)

make
make check
sudo make install

sudo ldconfig

At this point OLA is ready to use. Next steps:

sudo nano /etc/rc.local:
insert before " exit 0 "-line:
su pi -c "olad -f"

sudo nano /etc/modprobe.d/eurolite-dmx.conf:

blacklist cdc_acm


check Vendor -ID and Product-ID, when Eurolite usb-dmx mk2 is plugged:
lsusb

sudo nano /etc/udev/rules.d/02-eurolite-dmx.rules:

(this is one line:)

SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="0403",

 ATTRS{idProduct}=="6001", GROUP="plugdev" MODE="660"


deactivate:

open with editor and change enabled = true to enabled = false

/home/pi/.ola/ola-opendmx.conf

/home/pi/.ola/ola-usbserial.conf

/home/pi/.ola/ola-stageprofi.conf


add this line in ola-usbdmx.conf:

enable_eurolite_mk2 = true


After restarting, EurolitePro USB Device shows up on OLA Admin page (127.0.0.1:9090) and can be patched.

I hope, I didn't forget something in the summary.

Thank you once again for your help, I couldn't succeed without your guidance!



Jiří Atanasovský

unread,
Nov 6, 2020, 5:03:11 PM11/6/20
to open-lighting
Thank you Gunter for posting these steps. It worked for me and it was nice to have it all in one place!

Dne úterý 14. července 2020 v 15:39:37 UTC+2 uživatel gunther....@gmail.com napsal:

Gunther Seiser

unread,
Nov 7, 2020, 9:00:08 AM11/7/20
to open-lighting
great to hear that it worked for you.
Gunther

James Trueeb

unread,
Nov 29, 2021, 5:36:17 PM11/29/21
to open-lighting
Hi everybody,

I discovered this post for setting up an Eurolite USB DMX512 Mk2 with OLA.

Since this recipe seemed to work for everybody, I tried to follow it on my RPi with Rasbian 10. I successfully installed OLA but I am having trouble when trying to access the web app on 192.168.1.11:9090 I am getting a 404 (NOT FOUND). Maybe somebody know what is wrong when looking at my logs:

sudo services olad status:

● olad.service - LSB: OLA daemon
   Loaded: loaded (/etc/init.d/olad; generated)
   Active: active (exited) since Mon 2021-11-29 22:07:58 CET; 10min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 2730 ExecStart=/etc/init.d/olad start (code=exited, status=0/SUCCESS)

Nov 29 22:07:58 raspberrypi systemd[1]: Starting LSB: OLA daemon...
Nov 29 22:07:58 raspberrypi systemd[1]: Started LSB: OLA daemon.

olad -l 4:

olad/Olad.cpp:98: OLA Daemon version 0.10.7
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 4, events 2001, descriptor: 0x14fa788
olad/OlaDaemon.cpp:121: Using configs in /home/pi/.ola
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 7, events 2001, descriptor: 0x14f4548
common/thread/Thread.cpp:200: Thread pref-saver, policy SCHED_OTHER, priority 0
common/file/Util.cpp:135: Could not open /usr/share/ola/pids:No such file or directory
common/rdm/PidStoreLoader.cpp:190: Load Complete
common/network/PosixInterfacePicker.cpp:161: Skipping lo because it's a loopback
common/network/PosixInterfacePicker.cpp:244: Found: wlan0, 192.168.1.11, dc:a6:32:10:18:6f
common/network/InterfacePicker.cpp:92: Using interface wlan0 (192.168.1.11)
olad/OlaServer.cpp:194: Server UID is 7a70:0b01a8c0
olad/OlaServer.cpp:206: Server instance name is OLA Server
olad/plugin_api/Preferences.cpp:436: Missing /home/pi/.ola/ola-universe.conf: No such file or directory - this isn't an error, we'll just use the defaults
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 9, events 2001, descriptor: 0x14f9790
olad/AvahiDiscoveryAgent.cpp:201: Client state changed to AVAHI_CLIENT_S_RUNNING
common/thread/Thread.cpp:200: Thread http, policy SCHED_OTHER, priority 0
common/http/HTTPServer.cpp:496: HTTP Server started on port 9090
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 13, events 2001, descriptor: 0x1504400
olad/AvahiDiscoveryAgent.cpp:236: State for OLA Server._http._tcp,_ola, group 0x1502908 changed to AVAHI_ENTRY_GROUP_UNCOMMITED
olad/AvahiDiscoveryAgent.cpp:334: Adding _ola._sub._http._tcp
olad/AvahiDiscoveryAgent.cpp:342: Failed to add _ola._sub._http._tcp
olad/OlaServer.cpp:481: Updated PID definitions.
olad/AvahiDiscoveryAgent.cpp:236: State for OLA Server._http._tcp,_ola, group 0x1502908 changed to AVAHI_ENTRY_GROUP_REGISTERING
olad/OlaServer.cpp:489: PID store is at 0x14f7440
common/thread/Thread.cpp:200: Thread signal-thread, policy SCHED_OTHER, priority 0
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 21, events 2001, descriptor: 0x1505050
olad/PluginManager.cpp:73: Skipping Enttec Open DMX because it was disabled
common/io/EPoller.cpp:306: ss process time was 0.000016
common/io/EPoller.cpp:306: ss process time was 0.000020
common/io/EPoller.cpp:306: ss process time was 0.000011
olad/PluginManager.cpp:73: Skipping StageProfi because it was disabled
olad/PluginManager.cpp:73: Skipping Serial USB because it was disabled
olad/PluginManager.cpp:73: Skipping FTDI USB DMX because it was disabled
olad/PluginManager.cpp:73: Skipping UART native DMX because it was disabled
olad/PluginManager.cpp:195: Trying to start Dummy
olad/plugin_api/DeviceManager.cpp:105: Installed device: Dummy Device:1-1
olad/PluginManager.cpp:200: Started Dummy
olad/PluginManager.cpp:195: Trying to start ArtNet
common/network/PosixInterfacePicker.cpp:161: Skipping lo because it's a loopback
common/network/PosixInterfacePicker.cpp:244: Found: wlan0, 192.168.1.11, dc:a6:32:10:18:6f
common/network/InterfacePicker.cpp:92: Using interface wlan0 (192.168.1.11)
common/network/Socket.cpp:144: Binding to 0.0.0.0:6454
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 23, events 2001, descriptor: 0x150a978
olad/plugin_api/DeviceManager.cpp:105: Installed device: ArtNet [192.168.1.11]:2-1
olad/PluginManager.cpp:200: Started ArtNet
olad/PluginManager.cpp:195: Trying to start ShowNet
common/network/PosixInterfacePicker.cpp:161: Skipping lo because it's a loopback
common/network/PosixInterfacePicker.cpp:244: Found: wlan0, 192.168.1.11, dc:a6:32:10:18:6f
common/network/InterfacePicker.cpp:92: Using interface wlan0 (192.168.1.11)
common/network/Socket.cpp:144: Binding to 0.0.0.0:2501
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 24, events 2001, descriptor: 0x150aa48
olad/plugin_api/DeviceManager.cpp:105: Installed device: ShowNet [192.168.1.11]:3-1
olad/PluginManager.cpp:200: Started ShowNet
olad/PluginManager.cpp:195: Trying to start ESP Net
common/network/PosixInterfacePicker.cpp:161: Skipping lo because it's a loopback
common/network/PosixInterfacePicker.cpp:244: Found: wlan0, 192.168.1.11, dc:a6:32:10:18:6f
common/network/InterfacePicker.cpp:92: Using interface wlan0 (192.168.1.11)
common/network/Socket.cpp:144: Binding to 0.0.0.0:3333
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 25, events 2001, descriptor: 0x150ba78
olad/plugin_api/DeviceManager.cpp:105: Installed device: ESP Net [192.168.1.11]:4-1
olad/PluginManager.cpp:200: Started ESP Net
olad/PluginManager.cpp:195: Trying to start SandNet
common/network/PosixInterfacePicker.cpp:161: Skipping lo because it's a loopback
common/network/PosixInterfacePicker.cpp:244: Found: wlan0, 192.168.1.11, dc:a6:32:10:18:6f
common/network/InterfacePicker.cpp:92: Using interface wlan0 (192.168.1.11)
common/network/Socket.cpp:144: Binding to 0.0.0.0:37895
common/network/Socket.cpp:144: Binding to 0.0.0.0:37900
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 27, events 2001, descriptor: 0x150c2d0
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 26, events 2001, descriptor: 0x150c2e8
olad/plugin_api/DeviceManager.cpp:105: Installed device: SandNet [192.168.1.11]:7-1
olad/PluginManager.cpp:200: Started SandNet
olad/PluginManager.cpp:195: Trying to start Pathport
common/network/PosixInterfacePicker.cpp:161: Skipping lo because it's a loopback
common/network/PosixInterfacePicker.cpp:244: Found: wlan0, 192.168.1.11, dc:a6:32:10:18:6f
common/network/InterfacePicker.cpp:92: Using interface wlan0 (192.168.1.11)
common/network/Socket.cpp:144: Binding to 0.0.0.0:3792
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 28, events 2001, descriptor: 0x150cc48
olad/plugin_api/DeviceManager.cpp:105: Installed device: Pathport [192.168.1.11]:9-1
olad/PluginManager.cpp:200: Started Pathport
olad/PluginManager.cpp:195: Trying to start E1.31 (sACN)
common/network/PosixInterfacePicker.cpp:161: Skipping lo because it's a loopback
common/network/PosixInterfacePicker.cpp:244: Found: wlan0, 192.168.1.11, dc:a6:32:10:18:6f
common/network/InterfacePicker.cpp:92: Using interface wlan0 (192.168.1.11)
common/network/Socket.cpp:144: Binding to 0.0.0.0:5568
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 29, events 2001, descriptor: 0x150d5f8
olad/plugin_api/DeviceManager.cpp:105: Installed device: E1.31 (DMX over ACN) [192.168.1.11]:11-1
olad/PluginManager.cpp:200: Started E1.31 (sACN)
olad/PluginManager.cpp:195: Trying to start USB
libs/usb/HotplugAgent.cpp:85: libusb_set_option(LIBUSB_OPTION_LOG_LEVEL, 0)
libs/usb/HotplugAgent.cpp:94: HotplugSupported(): 1
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 2:1 @0x150f050 [add]
plugins/usbdmx/AsyncPluginImpl.cpp:272: USB device added, checking for widget support, vendor 0x1d6b, product 0x0003
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:6 @0x150eb88 [add]
plugins/usbdmx/AsyncPluginImpl.cpp:272: USB device added, checking for widget support, vendor 0x046d, product 0xc52b
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:4 @0x1525208 [add]
plugins/usbdmx/AsyncPluginImpl.cpp:272: USB device added, checking for widget support, vendor 0x046d, product 0xc52b
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:7 @0x15252b0 [add]
plugins/usbdmx/AsyncPluginImpl.cpp:272: USB device added, checking for widget support, vendor 0x0403, product 0x6001
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:2 @0x15250e0 [add]
plugins/usbdmx/AsyncPluginImpl.cpp:272: USB device added, checking for widget support, vendor 0x2109, product 0x3431
libs/usb/HotplugAgent.cpp:172: USB hotplug event: 1:1 @0x1524b08 [add]
plugins/usbdmx/AsyncPluginImpl.cpp:272: USB device added, checking for widget support, vendor 0x1d6b, product 0x0002
libs/usb/LibUsbThread.cpp:50: -- Starting libusb thread
common/thread/Thread.cpp:200: Thread , policy SCHED_OTHER, priority 0
libs/usb/LibUsbThread.cpp:35: ----libusb event thread is running
olad/PluginManager.cpp:200: Started USB
olad/PluginManager.cpp:195: Trying to start OSC
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 36, events 2001, descriptor: 0x1521788
plugins/osc/OSCDevice.cpp:88: No targets specified for OSC Output port 0
plugins/osc/OSCDevice.cpp:88: No targets specified for OSC Output port 1
plugins/osc/OSCDevice.cpp:88: No targets specified for OSC Output port 2
plugins/osc/OSCDevice.cpp:88: No targets specified for OSC Output port 3
plugins/osc/OSCDevice.cpp:88: No targets specified for OSC Output port 4
olad/plugin_api/DeviceManager.cpp:105: Installed device: OSC Device:14-1
olad/PluginManager.cpp:200: Started OSC
olad/PluginManager.cpp:195: Trying to start SPI
common/io/EPoller.cpp:306: ss process time was 0.000013
plugins/spi/SPIWriter.cpp:59: Created SPI Writer /dev/spidev0.1 with speed 1000000, CE is 0
plugins/spi/SPIDevice.cpp:97: spidev0.1, Software backend, 1 ports
common/thread/Thread.cpp:200: Thread , policy SCHED_OTHER, priority 0
olad/plugin_api/DeviceManager.cpp:105: Installed device: SPI Device:15-spidev0.1
plugins/spi/SPIWriter.cpp:59: Created SPI Writer /dev/spidev0.0 with speed 1000000, CE is 0
plugins/spi/SPIDevice.cpp:97: spidev0.0, Software backend, 1 ports
common/io/EPoller.cpp:306: ss process time was 0.000015
common/thread/Thread.cpp:200: Thread , policy SCHED_OTHER, priority 0
olad/plugin_api/DeviceManager.cpp:105: Installed device: SPI Device:15-spidev0.0
olad/PluginManager.cpp:200: Started SPI
olad/PluginManager.cpp:195: Trying to start KiNET
common/network/Socket.cpp:144: Binding to 0.0.0.0:6038
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 38, events 2001, descriptor: 0x1524448
olad/plugin_api/DeviceManager.cpp:105: Installed device: KiNet Device:16-1
olad/PluginManager.cpp:200: Started KiNET
olad/PluginManager.cpp:195: Trying to start KarateLight
common/io/IOUtils.cpp:39: open(/dev/kldmx0): No such file or directory
plugins/karate/KaratePlugin.cpp:79: Could not open /dev/kldmx0 No such file or directory
olad/PluginManager.cpp:200: Started KarateLight
olad/PluginManager.cpp:195: Trying to start Milford Instruments
plugins/milinst/MilInstPlugin.cpp:57: No path configured for device, please set one in ola-milinst.conf
olad/PluginManager.cpp:200: Started Milford Instruments
olad/PluginManager.cpp:195: Trying to start Renard
plugins/renard/RenardPlugin.cpp:57: No path configured for device, please set one in ola-renard.conf
olad/PluginManager.cpp:200: Started Renard
olad/PluginManager.cpp:195: Trying to start Open Pixel Control
olad/PluginManager.cpp:200: Started Open Pixel Control
olad/PluginManager.cpp:195: Trying to start GPIO
olad/PluginManager.cpp:200: Started GPIO
common/io/EPoller.cpp:306: ss process time was 0.000017
olad/AvahiDiscoveryAgent.cpp:236: State for OLA Server._http._tcp,_ola, group 0x1502908 changed to AVAHI_ENTRY_GROUP_ESTABLISHED

Help would be so much appreciated, I am nor able to find the problem. Thank you.

Kind regards,
James

Peter Newman

unread,
Dec 3, 2021, 10:11:28 PM12/3/21
to open-lighting
Hi James,

Did you follow Gunther's steps:

Your early line still says 0.10.7, it needs to say 0.10.8 or later to have that device support (but built from our master branch).

Try running this:
sudo apt-get purge ola libola

Then:
dpkg -l | grep -i ola

And share the output of the second command.

Then follow Gunther's steps again.

Peter Newman

unread,
Dec 10, 2021, 5:08:01 PM12/10/21
to open-lighting
Hi James,

Please reply all rather than replying privately so others can benefit too.

From the output you can see that libola1 versions 0.10.7 is still installed.

Sorry it looks like you need to run:
sudo apt-get purge ola libola1

Please do that and then recompile OLA and you should be all good!

----- Original Message -----
From: James Trueeb
To: Peter Newman
Sent: Friday, December 10, 2021 9:58 PM
Subject: Private Nachricht betreffend: Connect Eurolite USB-DMX512-Pro to ola


Hi Peter,

Yes, I followed Gunther's steps but it did not work. My only assumption would be that the Eurolite USB DMX512 Pro does not get enough power from the RPi4 Usb output to communicate properly. Here is the output of the second command you named:


ii  fonts-inconsolata                     001.010-5                           all          monospace font for pretty code listings and for the terminal
ii  libccolamd2:armhf                     1:5.4.0+dfsg-1                      armhf        constrained column approximate library for sparse matrices
ii  libcolamd2:armhf                      1:5.4.0+dfsg-1                      armhf        column approximate minimum degree ordering library for sparse matrices
ii  libola1:armhf                         0.10.7.nojsmin-1+b1                 armhf        Open Lighting Architecture - shared libraries
ii  libtwolame0:armhf                     0.3.13-4                            armhf        MPEG Audio Layer 2 encoding library
rc  ola                                   0.10.7.nojsmin-1+b1                 armhf        Open Lighting Architecture


Regards
James

James Trueeb

unread,
Dec 11, 2021, 5:02:13 AM12/11/21
to open-lighting
Hi Peter,

Thank you for the help. Unfortunately when I uninstall ola and libola and then reinstall from source, one test is not passed when running "make check":

FAIL: ola/OlaClientTester

I installed all dependencies, except for liblo and libcurses5-dev. For these, no distributions were found (Raspbian 10). I gues this should then be the problem, or what do you think? Kind regards
James

Camill Trüeb

unread,
Dec 11, 2021, 6:12:24 AM12/11/21
to open-l...@googlegroups.com
Hi,

Nevermind, it seems to work :) Thank you so much! Although, when I type in „olad status“, it says:

common/network/TCPSocket.cpp:235: bind to 127.0.0.1:9010 failed, Address is already in use
common/rpc/RpcServer.cpp:102: Could not listen to the RPC port 9010, you probably have another instance running.
olad/OlaServer.cpp:252: Failed to init RPC server

But if this is expected, everything works fine now. Have a good weekend.

Regards
James

Am 12/11/21 um 11:02 schrieb James Trueeb <camill...@hotmail.com>:

-- 
The Open Lighting Project: open-l...@googlegroups.com, #openlighting (irc.freenode.org)
To unsubscribe from this group, send email to open-lightin...@googlegroups.com
For more options, visit https://groups.google.com/groups/opt_out?hl=en
--- 
You received this message because you are subscribed to the Google Groups "open-lighting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-lightin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-lighting/c32ba915-31f3-4a5c-8ab1-316251547f9bn%40googlegroups.com.

Gunther Seiser

unread,
Dec 12, 2021, 1:47:36 PM12/12/21
to open-lighting
Hi James,

i get the same message when I type 'olad status'. Since it works on my PI without any problems for months, I think you can safely ignore this message.

Regards,
Gunther

Cyrill Appert

unread,
Feb 12, 2022, 9:17:19 AM2/12/22
to open-lighting
I thought it worked for me but now the USBDMX plugin isn't even existing. What happened?

Peter Newman

unread,
Feb 12, 2022, 9:53:00 AM2/12/22
to open-lighting
So the ola/OlaClientTester test will have been failing because OLA was still running.

You'd probably want liblo-dev (for OSC) and libncurses6-dev now (for some of the CLI example tools).

Glad you fixed it anyway.

Peter Newman

unread,
Feb 12, 2022, 9:54:32 AM2/12/22
to open-lighting
For both of you, olad is the OLA server, so typing olad foo means run olad with the argument foo, you need to use the control system that's running olad to find out if it's running.

E.g. "sudo service olad status" or "sudo /etc/init.d/olad status" will probably do what you actually want.

Peter Newman

unread,
Feb 12, 2022, 10:07:18 AM2/12/22
to open-lighting
Hi Cyrill,

Did it work for you before, but doesn't now? Perhaps you've got two copies of OLA and running different ones at different times? I assume this is another Eurolite Pro again?

Can we have -l 4 logs:
Reply all
Reply to author
Forward
0 new messages