I am the owner of a Velleman PCRU01 datalogger (see https://www.velleman.eu/products/view/?id=436316). I have been using Linux for years (Kubuntu 18.04LTS in this time), Windows 7 Prof. on a dual boot PC is only my backup system. Datalogger user software does not see the USB connected hardware in Linux Wine subsystem, I describe it below.
I ask at the beginning: is there any way to solve the user software access to the datalogger? I am only an advanced user, not a programmer, so unfortunately I can't help myself...
Of course, I could provide all the necessary cooperation (various system listing and dumps, your proposals/modifications/changes etc.) upon request.
I'm adding some basic information:
1) The PC software at https://www.velleman.eu/support/downloads/?code=PCRU01, specifically https://www.velleman.eu/downloads/files ... _v1.02.zip was installed in Wine 7.0.1 on Kubuntu 18.04 LTS without any problems. Everything in it works normally (in demo mode), it just doesn't connect to the PCRU01 datalogger. I have the necessary USB port permissions set (I have created the appropriate *.rules file according to VID and PID in /etc/udev/rules.d). After connecting the datalogger to the USB port, the hidraw6 device is created in the /dev directory (with root privileges).
2) when installing the program in Windows 7 Professional the PCRU01 works normally, so the reason for the problem in Linux is the usual problem with the access of applications running in Wine to the USB port.
3) lsusb -v listing (after removing unnecessary parts):
Code: Select all
Bus 003 Device 008: ID 10cf:0d01 Velleman Components, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x10cf Velleman Components, Inc.
idProduct 0x0d01
bcdDevice 0.02
iManufacturer 1 Velleman Instruments
iProduct 2 PCRU01 Recorder
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 41
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 200mA
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 28
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
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 1
Device Status: 0x0001
Self Powered
5) The PIC18F24K50 processor is used in the datalogger - it communicates directly with the USB port and provides all other functions.
Thank you very much for the answer.
--
JirkaZ