[newRPL] interested in RPN mode?

[jpcuzzourt]

(11-23-2019 06:09 PM)Claudio L. Wrote:  Did you follow the wiki on USB permissions for Linux? newRPL Desktop will not see the USB device unless the user it runs under has permission to read/write the USB device. If you did, make sure you spelled the group name consistently, on one of my machines I had created the group usbdevices, then added my user to usbdevice (no s). Took me a while to figure it out.
EDIT: Maybe it helps to note I'm using KUbuntu 19.04 on my main dev systems, 2 different setups and both work well, so if there's one build that's well tested is Linux 64-bit.

Code:

jpcuzzourt@mx:~
$ groups jpcuzzourt
jpcuzzourt : jpcuzzourt tty lp uucp dialout cdrom floppy sudo audio dip video plugdev users netdev lpadmin scanner vboxsf vboxusers usbdevices
jpcuzzourt@mx:~
$ cat /etc/udev/rules.d/50-HIDDevices.rules
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0664", GROUP="usbdevices"
SUBSYSTEM=="usb", ATTR{bInterfaceClass}=="03", MODE="0664", GROUP="usbdevices"
jpcuzzourt@mx:~
$ lsusb
Bus 004 Device 004: ID 03f0:231d HP, Inc Broadcom 2070 Bluetooth Combo
Bus 004 Device 003: ID 04f2:b230 Chicony Electronics Co., Ltd Integrated HP HD Webcam
Bus 004 Device 005: ID 03f0:0121 HP, Inc HP 39g+ [F2224A], 39gs [F2223A], 40gs [F2225A], 48gII [F2226A], 49g+ [F2228A], 50g [F2229A, NW240AA]
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 138a:003c Validity Sensors, Inc. VFS471 Fingerprint Reader
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$ uname -a
Linux mx 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64 GNU/Linux

I don't see anything wrong with my configuration, but I include it for you to verify in case I am missing something.
I believe this was working under v1299, that is, I could see and select select the device although I still got errors whenever I tried to do I/O. I should try reverting back and verifying this.*
Thanks.
JP

FINAL EDIT: You can skip all the edits below. It's just me figuring out how to go back to 1299 and confirm that it also did not see the USB devices.
I'll continue trying to figure out why.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
EDIT: *Can you tell me which commit corresponds to V1299? Sorry to be a bother, but I'm a git AND QT noob. I don't know where the VERSION number comes from. Is it autogenerated somehow in QT creator, or is it in one of the source files? I'm assuming I can use git to checkout the source corresponding to a particular commit and rebuild v1299 to see if there's a difference in USB behavior on my system. (The reason I'm uncertain where I saw this behavior previously, is that before compiling for linux, I had also used it under Windows 10 both natively and in Virtualbox, as well as under wine. And now my recollections are all jumbled, lol. Now that I can compile a 64-bit linux version, that is how I'd much prefer to use it.)
EDIT: OK, I see that it comes from "git rev-list --count HEAD", so piping it to |head -17 shows me that 17408 is the commit I want. I'll give it a go and see what happens.

EDIT: Results. It made no difference. I must've been mistaken about ever seeing my linux version recognize the USB device. I did verify that the v1315 firmware I compiled for the 39GS will talk to the Windows version of newRPL-UI (Win7 running on Virtualbox linux host). I should note that under that scenario, newRPL-ui reports a USB communications error right after it completes a USB archive restore to my 39GS. But the restore seems to work correctly. This could be a quirk of using VirtualBox. My virtual Win7 OS repeatably crashes when I use the same newRPL-UI to do a firmware update. The firmware update completes, and then crashes Windows 7. I am able to use conn3X on that same Win7 instance to download firmware without issue. The entire reason for that win7 virtual machine was to run conn3x because I couldn't get it to work on Win10 to initially install the firmware to my 39GS. The SDcard method, of course, is not available to me yet - I still need to find the right sdcard holder to install.)

So, while I have a usable enough system right now, ideally I need to figure out why my linux version of newRPL-ui does not see the USB hardware. I'll see what else I can figure out, unless you spot something wrong in my group/permissions setup in the code window above.