JP1 Remotes

Posted: **Tue Apr 19, 2016 11:52 am**

No, it is neither normal nor a very sane idea to run RM as root. Under Fedora it runs just fine for me.

Is your userid a member of group "lock"? At least on Fedora, this is necessary to access the serial USB ports.Try the groups command to find out.

Posted: **Tue Apr 19, 2016 1:14 pm**

I don't even show a group "lock" as an available group name???

Do I need to create the "lock" group and add my user to it?

I am on Ubuntu 14.04 for reference...

Posted: **Tue Apr 19, 2016 3:55 pm**

Have you read and followed this part of the announcement of RMIR v2.03, the first post in this thread:

If your OS is Linux then run Setup.sh from Terminal as a shell script. If the current directory in Terminal is the RemoteMaster installation directory then the command "sh Setup.sh" will run the script. It creates two .desktop shortcuts, one for RMIR and the other (named RemoteMaster) for RM. They will be created in your installation folder, but they are also copied to your $HOME/.local/share/applications folder to ensure that they appear on your Dash. Setup.sh will also add you to the dialout group of users, if you are not already in it. If you need to be added, then it will ask you for your sudo password as this step needs to be run with root privileges. This step is needed to enable RMIR to access USB serial ports without RMIR itself being run as root. Linux users will find further information in this thread in the JP1 forum.

The shell script Setup.sh was developed and tested in Ubuntu 14.04, so it should work for you.

Posted: **Tue Apr 19, 2016 4:59 pm**

Yes I have done the setup script. I also took a look at the script to see what all it did. I have also checked to make sure I am part of the dialout group, but still have the same problem. The only way I can get RMIR to recognize the remote is to run it as root (sudo).

Posted: **Wed Apr 20, 2016 9:38 am**

Could it be a permissions issue with the drivers? I seem to remember way back, manually replacing drivers, to make this work? Can anyone tell me how/where to check the drivers, or am I going down the completely wrong rabbit hole?

Posted: **Wed Apr 20, 2016 9:49 am**

Post the rmaster.err (two really) to the diagnosics area, when

1. running as root , and
2. not running as root

You are right, there is no "lock" group in Ubunto.

Posted: **Wed Apr 20, 2016 10:49 am**

Here you go:

https://www.hifi-remote.com/forums/dload ... e_id=14032

Posted: **Wed Apr 20, 2016 11:57 am**

In both cases, the communication library libhidapi.so loads fine, but as non-root, it fails getting any information from the USB device. My Fedora 23 system behaves "identically". So you know that it is not your problem alone...

Unfortunately, I do not know too much about USB for Linux. But it is a problem worth looking into.

Posted: **Wed Apr 20, 2016 12:20 pm**

Perhaps a udev rule?

When I plug the remote in, it is recognized by the system, but no name associated:

Code: Select all

$lsusb
Bus 002 Device 013: ID 05a9:2640 OmniVision Technologies, Inc. OV2640 Webcam
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 0483:2016 STMicroelectronics Fingerprint Reader
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 006: ID 06e7:8005

It is the "Device 006: ID 06e7:8005".....

Posted: **Wed Apr 20, 2016 12:41 pm**

YES!

I wrote the following file

Code: Select all

SUBSYSTEMS=="usb", ATTRS{idProduct}=="8001", ATTRS{idVendor}=="06e7", SYMLINK+="xsight" GROUP="dialout", MODE="660"

(that is one single long line) and put it as /etc/udev/rules.d/42-xsight.rules. And now it works!

Comments:

- File name is "arbitrary"
- GROUP is sort-of arbitrary, I just selected dialout since RMIR expects its users to be members of that group anyhow. Alternatively, put MODE="666" and forget GROUP.
- SYMLINK is optional, just feels cool...
- My Xsight (branded "One for all") has different vendorid and productid than yours. Change as requested.

Posted: **Wed Apr 20, 2016 1:09 pm**

Awesome! Got it working, but now when I download, I get an error that it cannot find the "URC 8603.map" file. Is there a way to specify a particular .map file?

I know how to change map folder location, but why does the remote look for a specific named file and/or how do I change it?

Posted: **Wed Apr 20, 2016 1:28 pm**

Should be in your installation. BTW, it is URC-8603.map (with a hyphen). Also available in svn, https://sourceforge.net/p/controlremote ... format=raw

why does the remote look for a specific named file and/or how do I change it?

In the rdf file, the line ImageMap defines the image and the map file.

For the record: your remote, with vendorid 06e7 and productid 8005, how is that branded?

Graham, this should definitely go into the instructions, possibly in Setup.sh.

Posted: **Wed Apr 20, 2016 1:35 pm**

ID 8005 should be Xsight brand, model 18G, not URC 8603. It would be very unusual for someone in the US to end up with an 8603.

Posted: **Wed Apr 20, 2016 1:43 pm**

Barf wrote:Should be in your installation. BTW, it is URC-8603.map (with a hyphen). Also available in svn, https://sourceforge.net/p/controlremote ... format=raw

why does the remote look for a specific named file and/or how do I change it?
In the rdf file, the line ImageMap defines the image and the map file.

For the record: your remote, with vendorid 06e7 and productid 8005, how is that branded?

Graham, this should definitely go into the instructions, possibly in Setup.sh.

I did some moving around of my files, so don't know where it went. I downloaded the (yes, there is a hyphen) URC-8603.map, and URC-8603.jpg to my "maps" folder.

My remote is an Acoustic Research (Universal Electronics) ARRX18G.

Thanks for all the help. Every year or so, I start to monkey with my remotes, and have to refresh my memory on how all this works. In the mean time I keep updating OS's, although, obviously I'm a year behind on Ubuntu

Posted: **Wed Apr 20, 2016 1:51 pm**

Sounds like your maps and images are quite old if you're getting the 8603 as your only choice.

JP1 Remotes

RMIR Xsight Support