URC-6440 on Linux and code programming

[davecs]

Let me suggest using a less generic title (presently "Using JP1 with Linux"). It should probably mention URC6440/OARxxx.

After all, it is all about helping other users.

I agree with that. After Rob set it up I couldn't work out how to change it, so I added a sentence at the beginning to say that it ought to work without difficulty on JP-type interfaces. I've got a URC7980 somewhere, I've had a hunt around for it, without success. I want to test permissions issues, but I suspect that all will be fine. I had permissions issues in the past when I was using the serial printer interface. I don't even have one now!

Can you confirm whether the method works with your Fedora setup?

At present, the distros that don't automount seem to have difficulty getting the UUID and Label off the remote. I'm looking for solutions where I can either get a Label assigned via UDEV, or I can automount via the /dev/disk/by-id label, steep learning curve for me at the moment.

[The Robman]

Let me suggest using a less generic title (presently "Using JP1 with Linux"). It should probably mention URC6440/OARxxx.

After all, it is all about helping other users.

I renamed it to "Using USB Remotes with Linux". I don't want to put specific models in the subject as I'm pretty sure it applies to any remote with a USB port.

[davecs]

Let me suggest using a less generic title (presently "Using JP1 with Linux"). It should probably mention URC6440/OARxxx.

After all, it is all about helping other users.

I renamed it to "Using USB Remotes with Linux". I don't want to put specific models in the subject as I'm pretty sure it applies to any remote with a USB port.

Are there others? It might be nice to test them also.

[davecs]

After a bit of online help, I've found an updated script where you don't need to specify a user. It might fail if more than one user is logged in at once (for example if you use "Switch User" to keep someone's work alive while someone else uses the computer). I think it makes the code a lot more usable though.

Meanwhile the search continues for a means of making these remotes behave as they used to in older versions of Linux. But this is a step up.

[The Robman]

Are there others? It might be nice to test them also.

According to the Remote Chart, this is the list of USB remotes:

ARRX12G Xsight Plus
ARRX15G Xsight Color
ARRX18G Xsight Touch
Nevo C2
Nevo C3
URC-6430
URC-6440
RCA OARUSB03G (URC-6530)
RCA OARUSB04G (URC-6540)
URC-7990/7991 Infinity
URC-8602 Xsight Color
URC-8603 Xsight Touch
URC-8610 Xsight Lite
URC-8620 Xsight Plus

[davecs]

Are there others? It might be nice to test them also.

According to the Remote Chart, this is the list of USB remotes:

ARRX12G Xsight Plus
ARRX15G Xsight Color
ARRX18G Xsight Touch
Nevo C2
Nevo C3
URC-6430
URC-6440
RCA OARUSB03G (URC-6530)
RCA OARUSB04G (URC-6540)
URC-7990/7991 Infinity
URC-8602 Xsight Color
URC-8603 Xsight Touch
URC-8610 Xsight Lite
URC-8620 Xsight Plus

It would be interesting to hear from anyone who has these remotes and runs them on Linux.

Obviously we've dealt with the URC-6440 and OARUSB04G.

I wonder whether the URC-6430 and OARUSB03G are the same remotes but with a button missing? Would be interesting if anyone can test.

I think that the 6440 and 04G have problems with Linux because their file system is, what we say in Britain, well dodgy. Some of the system messages when you plug them in, would indicate so.

Where we can do with some information, is if people have the other remotes, and they mount in modern Linux distros, great. If not, let us know, and I can tell them what information they can get me, and send them ideas to test. I would hope that if their file and partitioning systems are more, er.... , orthodox, they won't have any problems.

[rem]

For background info I have updated my previous post a little
https://www.hifi-remote.com/forums/viewt ... 952#p136952

I have tried installing RMIR to communicate with my Nevo C2
It works in Linux Mint 19.1 and 19.2 (both xfce and cinnamon)
MX Linux 18.3
PCLinux OS xfce

The remote behaves in a similar manner in all 3 distributions.
The remote is NOT mounted and nothing new shows up when using commands like lsblk or df
After extracting the files, I run Setup.sh and copy the xsight rules over, log out then back in and it works fine for downloading from remote Nevo C2.

The only odd one is the xfce PCLinuxOS - the setup script didn't update the menus, but just clicking on the RMIR icon via thuner explorer starts the process fine.

This is what dmsg shows in all 3 cases / distributions

Code: Select all

[  156.084203] usb 3-1: new full-speed USB device number 3 using xhci_hcd
[  161.262479] usb 3-1: New USB device found, idVendor=06e7, idProduct=8006
[  161.262489] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  161.262494] usb 3-1: Product: XSIGHT.
[  161.262498] usb 3-1: Manufacturer: UNIVERSAL ELECTRONICS INC.
[  161.262502] usb 3-1: SerialNumber: XSIGHT.
[  161.309245] hidraw: raw HID events driver (C) Jiri Kosina
[  161.329580] usbcore: registered new interface driver usbhid
[  161.329582] usbhid: USB HID core driver
[  161.341489] hid-generic 0003:06E7:8006.0001: hiddev0,hidraw0: USB HID v2.00 Device [UNIVERSAL ELECTRONICS INC. XSIGHT.] on usb-0000:25:00.0-1/input0

The Nevo C2 is the only remote I have that has usb interface, but I guess the result should hold true for the similar hardware - eg maybe these ones will behave the same
ARRX12G Xsight Plus
ARRX15G Xsight Color
ARRX18G Xsight Touch
Nevo C2
Nevo C3
URC-8602 Xsight Color
URC-8603 Xsight Touch
URC-8610 Xsight Lite
URC-8620 Xsight Plus

[davecs]

Yes, a nice, orderly dmseg output. No nonsense about data being beyond the end of the file. So it "just works". Thanks for the info.

EDIT: I've modified the second paragraph to clarify that many USB remotes will just work.