Eurolite USB-DMX512-PRO MK2

[Marco Schikatis]

Hi, 
I am trying to get the Eurolite USB-DMX512-Pro MK2 to work with OLA. 
I scoured this group, but none of the answers worked for me so far. 

The system is a headless Raspi 4 2GB running Raspian.
I installed OLA version 1.07 via APT.

I added enable_eurolite_mk2 = true  to ola-usbdmx.conf, blacklist cdc_acm to eurolite-dmx.conf,  

SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", GROUP="plugdev" MODE="660"
to  etc/udev/rules.d/02-eurolite-dmx.rules. 

When enabling the FTDI USB DMX plugin, device shows up as  FT232R USB UART with serial number : AQ01FIF8 as an output device but does not recognize any device connected to it.

Am I missing somthing?

Thanks Marco

[Marco Schikatis]

Alright, 
I started from scratch with .11 following https://groups.google.com/u/0/g/open-lighting/c/rDIbzhqnWxQ/m/QTFLq7N-BAAJ
It's working now.

[Peter Newman]

Sorry I missed this before Marco but glad to see you've sorted it.

As you've spotted you'll need version 0.11.0 upwards or our git master branch for  Eurolite USB-DMX512-Pro MK2 support.

[Marco Schikatis]

Thanks for coming back to me!
While I am joyfully playing with the command-line tool,  I can't seem to get the Python API to work with python3.x ("ModuleNotFoundError: No module named 'ola'. 
For the moment I am using subprocesses and threads to run command-line tool commands but there is a noticeable delay from call to execution (0.5 - 1 s). 
I tried configuring with 'PYTHON=python3 --enable ./configure python-libs' as mentioned here. 
Do you have any hint how to get it working?

Thanks

Marco

[Peter Newman]

Hi Marco,

You want something more like this (that's two hyphens before enable):

PYTHON=python3 ./configure --enable-python-libs

If you have a look at the end of the configure run it should give you a little summary of what will be built (for example if you don't have the Protobuf Python libs, it won't actually set up Python, although it should throw an error).

In theory these packages should be sufficient:

python3-protobuf

python3-numpy (this may just be for the RDM tests)

[Peter Newman]

Hi Marco,

Please reply to all in future not just me so other people can benefit in future:

------------------------------------------------------------------------------------------------

Hm. 
I don't get any errors when configuring or compiling. 
I have one little hick up with   libcppunit-1.15-0. Apt doesn't find a package for 1.15.0. I guess the reason is that I cannot upgrade Raspian/Debian due to a driver that is kernel-specific and necessary. Could that be the culprit?
If not do I have to specifically include the path of the API?

------------------------------------------------------------------------------------------------

Sorry, forgot to actually answer your questions: 
I actually configured with the correct command - just botched it in the earlier mail.
The configure summary shows "Python API yes". 
------------------------------------------------------------------------------------------------

Try searching for libcppunit on it's own, there's probably a later version, although this won't stop the Python stuff working.

Okay, so if it enabled the API it presumably built it fine too? Did you do a make install? I suspect either the OLA Python library hasn't been installed, or your Python is looking for it elsewhere to where it is.

You could try a sudo updatedb && locate OlaClient.py

[Marco Schikatis]

Hi Peter, 
Sorry, for bugging you so much!
updatedb && locate shows /usr/local/lib/python3.7/site-packages/ola/OlaClient.py - ... Still, when I try to run a script containing OlaClientwrapper I get "no module named 'ola'"
.

[Marco Schikatis]

Alright, I included /site-packages/ and stuff works.
Sorry for the fuzz and thank you very much!

[Peter Newman]

Glad you sorted it. For the next person, what do you mean by "I included /site-packages/"? I think Python should do this automatically for you.

[Marco Schikatis]

Sorry, I will try to explain what I did and why.

I do not know if it is specific to Python 3.7 or the specific toolset I am using.
My python install doesn't seem to include  /usr/local/lib/python3.7/site-packages/ in the list of module paths. 

Specifically adding 

from sys import path

sys.path.append ('/usr/local/lib/python3.7/site-packages/' )

at the top of the script solves that issue. 
I believe ideally you'd either add the path directly to the importer config or add a .path  file to the project folder, but this works for the moment.

[Peter Newman]

Ah. This is probably a mismatch between where it's been installed to and where your version of Python is looking. If you're using the system Python, the files should probably go in /usr/share or something, which you can set via configure options (and would be set when it was built if installed via apt).

I guess if it's working that will do the trick for now!