ETS Inside on Linux - No dongles found
Hi,
I'm trying to run ETS Inside server on linux but without success.
I'm trying to run on ubuntu 14 on an udoo board. Instrallation was followed without issues.
If I run service ets-inside start I get:
Starting service … 5384
Knx.Ets.Osprey is now running, the PID is 5383
root@udoo:~# 2019-09-13 19:46:57,663 INFO : No dongles found
If I run lsusb -v I get (among the rest):
Bus 001 Device 003: ID 2a07:0102
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2a07
idProduct 0x0102
bcdDevice 2.01
iManufacturer 1 KNX
iProduct 2 License Stick KNX-96016512
iSerial 3 7A944C9C0E12
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 41
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 230
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 10
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 10
Device Status: 0x0000
(Bus Powered)
Can anyone from the ETS team lend a hand to help my run the software on linux?
-
Hi Ricardo. Did you manage to solve that problem? I've got the same running inside a Docker container.
0 -
Hi René,
In a way yes. I’m using a slightly modified ubuntu running on an udoo quad. I didn’t find a solution to the problem but I rapidly found out that running everything as root caused all the issues to vanish. I guess this means that my problem was somehow related to hardware access permissions. I’m more of a FreeBSD guy and didn’t have the skills to investigate this Linux-type issue. Since the machine is a dedicated one, I had no issues with running it as root.
0 -
Hi Ricardo,
thanks for the answer. I'll continue looking for a solution then :-)
Sooner or later we'll find a solution. I know others are looking as well.
0
Commenti
3 commenti
Accedi per aggiungere un commento.