all that it worked out, do not know what's the problem,
olad still complains:
common/io/Serial.cpp:151: Device /dev/ttyUSB0 doesn't exist, so there's no point trying to acquire a lock
Jannis Achstetter
unread,
Dec 20, 2020, 4:55:35 PM12/20/20
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to open-l...@googlegroups.com
Good evening joni,
as you said in your message title, you are using the Anyma uDMX device.
Those are not USB-serial-based and as such you won't find a
/dev/ttyUSBX-device node on your machine for them. This is expected.
Can you please show us the output of your ./configure run?
Can you try the configure step with "--enable-libusb"?
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to open-lighting
--enable-libusb shouldn't be explicitly needed Jannis as --enable-libusb should bring it in. FWIW --disable-nanoleaf is redundant if you've got --disable-all.
Although as Jannis alludes to, something has gone wrong, if you really did ./configure --disable-nanoleaf --disable-all --enable-usbdmx and you're running that code, nothing should be trying to talk to any ttyUSB0. You did make etc afterwards didn't you?
Sharing config.log would also help.
Unfortunately we missed the 20.04 deadline so this is more complicated than it normally would be (not just apt-get install), our Debian packaging expert is getting us into the next release of that so we should be back in Ubuntu soon.