On Thursday 04 February 2016 14:20:34 Ralph Corderoy wrote: > This is assuming the Windows application wants access to a USB HID > device. It might be that the MCU presents something else, e.g. a serial > port?
Well the installer says that it is a HID device and it appears and disappears from the list of hidraw devices when I plug and unplug it. > > So as detailed in parts 1 and 2 of that link, I have added the rule: > > KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0664", GROUP="plugdev" > > to /etc/udev/rules.d > > You might want to undo that; I'm not sure it's relevant. Yes. I probably will. > The creator of the scope seems quite open about its workings, e.g. the > PDFs describing its circuit. On the forum he provides, I found this old > post about creating a symbolic link to have COM1 access the USB scope in > WINE; that's probably an older version of the scope that may have > presented a different, serial-port, interface. > http://dpscope.freeforums.org/dpscope-software-under-linux-using-wine-t62.ht > ml I'd try that. I'm not sure that it is a COM port in Windows, I'll check it out, but at the moment I want to use the scope to sort out my PWM issue. I can at least do that in VMWare. -- Terry Coles -- Next meeting: Bournemouth, Tuesday, 2016-03-01 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
