RMIR Xsight Support

foggy69 · Post by **foggy69** » Tue Aug 09, 2016 6:02 am

mathdon wrote:Apologies, but I don't have time for fixing RMIR at present. I hope that normal service will resume in due course, but no promises as to when that will be.

No need to apologise, you have done fantastic work to make working on this remote possible. Thank you for all you have done

mdavej wrote:
foggy69 wrote:I am using a Nevo C2 USB8006

Up until a few months ago, I could use RemoteMaster on a Windows 10 x64 machine. But now I keep getting the 'No remotes found!' box. I have tried old and new versions of RM, the reg hack and ensured the rdf and image files are in the correct folders. Is there anything else I can try?

No remotes is still most likely the registry. Make sure you change ALL Xsight keys while the remote is plugged in. Then unplug and plug back in. Then confirm the appropriate interface is chosen in RM. I do all of my Xsight programming in Win 10 and find that I occasionally have to perform the reg change again to restore connectivity.

After a lot more fiddling around, I have now managed to get the remote to connect. I moved the 'RemoteMaster' folder from 'c:\Program Files (x86)' to the root c:\. I kept getting Admin permissions prompts when it was in the Program Files folder. I think this is something MS must have changed, because the result was the same on my desktop and laptop.

I also noticed that the registry had 2 separate mentions of the remote so I ensured that the 'EnhancedPowerManagementEnabled' was changed to 0 on both
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_06E7&PID_8006\XSIGHT.\Device Parameters
and
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB\VID_06E7&PID_8006\XSIGHT.\Device Parameters

Post by **mathdon** » Tue Aug 09, 2016 6:29 am

foggy69 wrote:I moved the 'RemoteMaster' folder from 'c:\Program Files (x86)' to the root c:\.

Yes, this is essential. The installation instructions in the first post of this announcement thread does warn:

Please note the requirement that the installation folder should not be read-only. In particular, for Windows installations it should not be a sub-folder of Program Files.

Post by **mathdon** » Mon Oct 10, 2016 6:15 am

mdavej wrote:Barf,

How about this for covering all Xsight models?

Code: Select all

# European One for all 8603 
SUBSYSTEMS=="usb", ATTRS{idProduct}=="8001", ATTRS{idVendor}=="06e7", SYMLINK+="xsight" GROUP="dialout", MODE="660" 

# European One for all 8602 
SUBSYSTEMS=="usb", ATTRS{idProduct}=="8002", ATTRS{idVendor}=="06e7", SYMLINK+="xsight" GROUP="dialout", MODE="660" 

# American Acoustic Research (Universal Electronics) ARRX15G 
SUBSYSTEMS=="usb", ATTRS{idProduct}=="8004", ATTRS{idVendor}=="06e7", SYMLINK+="xsight" GROUP="dialout", MODE="660" 

# American Acoustic Research (Universal Electronics) ARRX18G 
SUBSYSTEMS=="usb", ATTRS{idProduct}=="8005", ATTRS{idVendor}=="06e7", SYMLINK+="xsight" GROUP="dialout", MODE="660" 

# American Nevo (Universal Electronics) C2 
SUBSYSTEMS=="usb", ATTRS{idProduct}=="8006", ATTRS{idVendor}=="06e7", SYMLINK+="xsight" GROUP="dialout", MODE="660" 

# American Nevo (Universal Electronics) C3 
SUBSYSTEMS=="usb", ATTRS{idProduct}=="8007", ATTRS{idVendor}=="06e7", SYMLINK+="xsight" GROUP="dialout", MODE="660" 

# European One for all 8610 
SUBSYSTEMS=="usb", ATTRS{idProduct}=="8008", ATTRS{idVendor}=="06e7", SYMLINK+="xsight" GROUP="dialout", MODE="660" 

# European One for all 8620 
SUBSYSTEMS=="usb", ATTRS{idProduct}=="8009", ATTRS{idVendor}=="06e7", SYMLINK+="xsight" GROUP="dialout", MODE="660" 

# American Acoustic Research (Universal Electronics) ARRX12G 
SUBSYSTEMS=="usb", ATTRS{idProduct}=="8011", ATTRS{idVendor}=="06e7", SYMLINK+="xsight" GROUP="dialout", MODE="660"

I understand that this is something I should include in the next RMIR release, which will be a development one, RMIR v2.04 build 8. But it is meaningless to me and I have no idea what I am supposed to do with it. Can one of you knowledgeable about Linux please spell out in simple terms how I should include this in the release? If it needs a revision to Setup.sh, can you supply a suitably revised version? Many thanks.

radmanbobbin · Post by **radmanbobbin** » Mon Oct 10, 2016 7:48 am

Hi,

I've just bought an Xsight Lite and am having a few problems.

I've seen that I need to patch the registry to the it working on Windows 10, which I have done. The device seems to connect fine to the ez-rc website and when I've been through the web based wizard it claims it's downloaded the settings to the remote control.

However, although all the device names are then shown on the remote control, none of the buttons do anything!

I've tried this on both a Windows 7 and Windows 10 device and the same things happens on both.

So then I just tried using RMIR, and it works fine, uploading and downloading settings perfectly. It's great!

I'd quite like to get ez-rc working too though. Does anyone have any ideas?

I've got IE11 setup so that the ez-rc website is in the "intranet zone" with security settings turned to low, the website is added to compatibility view too. The activeX control is fully enabled too and as I've said previously, the registry is patched.

I'm stumped...

mdavej · Post by **mdavej** » Mon Oct 10, 2016 9:47 am

Sounds like you've set everything up correctly. Since RMIR works, that means the registry patch is working. It applies to both EZ-RC and RMIR. Of course Win 7 works without the patch.

I will dig out an Xsight Lite tonight and see if I can connect mine to EZ-RC.

If you post your RMIR file, I will try to load it into mine and see how it works with EZ-RC.

Post your file here: http://www.hifi-remote.com/forums/dload ... &cat_id=35

What country are you in?

Barf · Post by **Barf** » Mon Oct 10, 2016 11:04 am

mathdon wrote:
I understand that this is something I should include in the next RMIR release, which will be a development one, RMIR v2.04 build 8. But it is meaningless to me and I have no idea what I am supposed to do with it. Can one of you knowledgeable about Linux please spell out in simple terms how I should include this in the release? If it needs a revision to Setup.sh, can you supply a suitably revised version? Many thanks.

This is intended to be dropped as a file as e.g. /etc/udev/42-xsight.rules. If you do that (in a system with udev, and I think that is most modern Linuxes), when a device is plugged in, a symbolic link is created to the "real device" offering one (or more) alternative names for the device. This has two advantages:

1. A more user friendly name, like, here, /dev/xsight instead of /dev/usb/hiddev1,
2. A certain persistence/uniqueness, i.e., the name tends to be unique between sessions, and different from other, similar devices.

IMHO, making these sort of modifications to the system is not the task of the installation routine of a program like RM. Suggestion: just add the file to the distribution, possibly with some comments at the start, and let the user decide if he wants to use it himself.

Post by **mathdon** » Tue Oct 11, 2016 11:54 am

mdavej wrote:Graham is aware that none of the tabs for Xsight display correctly in 2.04 build 6. Please use 2.03 build 14 until it's fixed.

I believe this is fixed in RMIR 2.04 build 8. I would be grateful for any testing of this.

mdavej · Post by **mdavej** » Tue Oct 11, 2016 8:35 pm

Works great. Thanks Graham.

Post by **mathdon** » Wed Oct 12, 2016 5:22 am

Barf wrote:IMHO, making these sort of modifications to the system is not the task of the installation routine of a program like RM. Suggestion: just add the file to the distribution, possibly with some comments at the start, and let the user decide if he wants to use it himself.

Thanks, Barf. I'll include it as linux_xsight.rules in the next build. I understand that the filename is arbitrary, provided it ends .rules, and this should make it clear that it is only relevant to Linux users with XSights.

foggy69 · Post by **foggy69** » Sat Oct 15, 2016 4:04 am

mathdon wrote: I believe this is fixed in RMIR 2.04 build 8. I would be grateful for any testing of this.

Works great on Windows 10 64bit, thanks

deerewright · Post by **deerewright** » Mon Oct 17, 2016 9:53 am

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?

Code: Select all

chad@m1330:~$ lsusb
Bus 002 Device 003: 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 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 413c:8103 Dell Computer Corp. Wireless 350 Bluetooth
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
chad@m1330:~$ uname
Linux
chad@m1330:~$ uname -a
Linux m1330 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux


Here is my rules file from /etc/udev/rules.d/:

[quote]SUBSYSTEMS=="usb", ATTRS{idProduct}=="8005", ATTRS{idVendor}=="06e7",
SYMLINK+="xsight" GROUP="dialout", MODE="660" [/quote]

deerewright · Post by **deerewright** » Mon Oct 17, 2016 10:10 am

Literally, as I was typing the above reply, my remote suddenly connected. I noticed the screen flash to "USB Connected". I did a

Code: Select all

$ 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 device is, however, blank:

$ lsusb
Bus 002 Device 003: 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 002: ID 06e7:8005
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 413c:8103 Dell Computer Corp. Wireless 350 Bluetooth
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[/quote]

Barf · Post by **Barf** » Mon Oct 17, 2016 10:15 am

Tired batteries or flaky cables/connectors?

deerewright · Post by **deerewright** » Mon Oct 17, 2016 10:19 am

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

henfri · Post by **henfri** » Mon Oct 17, 2016 1:04 pm

Hello,

I've been using RMIR succesfully in the past on this machine and this Remote (Xsight Light), but I cannot connect anymore.
EZ-RC.com does work.

You can find my logs here: https://dl.dropboxusercontent.com/u/233 ... Master.zip

I spend some hours on this now, but could not get it to work. I read in this thread that a registry-patch might help.
Where do I find this?

By the way: should I run RMIR with, or without admin rights?

Regards,
Hendrik

JP1 Remotes

RMIR Xsight Support

Lost connection under Linux