JP1 Remotes

Barf wrote:Tired batteries or flaky cables/connectors?

Maybe the battery was a little low???? The cable is brand new, I couldn't find my cable so found the box buried in the basement with a brand new cable (I have two remotes). I hope the connector isn't failing

Literally, as I was typing the above reply, my remote suddenly connected. I noticed the screen flash to "USB Connected". I did a $ lsusb and there it was. I had just left it connected during the time I was typing (after a reboot), and it suddenly came alive?!?!?!?!????

The description of the usb ...

I don't know what happened. I was working with my ARRX18G last night without any problems on Ubuntu 16.04. This morning I am unable to to connect to the remote. It does not show up in lsusb.. I think I did do a ubuntu base update?

chad@m1330:~$ lsusb
Bus 002 Device 003: ID 05a9:2640 OmniVision ...

mathdon wrote:Did you follow this step in the installation instructions:

Yes, I swear I had tried installing again, earlier. But now it suddenly works? I think I'm losing my mind...

Sorry to have wasted your time

Thanks anyway for the help!

Deerewright, the post above yours that refers to jp12serial.dll v0.20 Beta is out of date. Please see this post announcing the official release of RMIR v2.03. That release includes jp12serial v0.20 (release version, not beta) compiled for each of Windows, Linux and Mac OS X, each in both 32-bit and ...

Reviving on old thread here in hopes that something new is happening. I am able to get things to work in Windows 10 with my URC-7962 by using the jp12serial v0.20 Beta driver. I would much prefer to use linux for most of my jp1 work. Is anyone working on a driver for linux (amd64)?

mdavej wrote: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.

As unusual as my URC-7960 and 7962?

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

my rdf file is "USB8005 (ARRX18G XSight 18).rdf", and it specifies 8603 on the "ImageMap=" line. Does that mean my rdf is old, as well?

I just checked the rdf file in "RemoteMaster.v2.03build14" and ...

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


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

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?

Perhaps a udev rule?

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



$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 ...

Here you go:

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

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?

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).

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...