Page 32 of 47
Posted: Wed Apr 20, 2016 2:03 pm
by Barf
Nice to hear that we were able to identify and fix the problem. Here is a udev rule that (I think) will work on both sides of the Atlantic:
Code: Select all
# European One for all 8603
SUBSYSTEMS=="usb", ATTRS{idProduct}=="8001", 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"
It may be feasible to generate it from Setup.sh.
BTW, I have an 8603, virtually virgin, lying around since several years, might finally be time to attack it...
BTW2, Ubuntu is "long time stable", Fedora for nerds who "love" updating...

Posted: Wed Apr 20, 2016 2:21 pm
by mdavej
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"
Posted: Wed Apr 20, 2016 2:29 pm
by deerewright
mdavej wrote: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 it shows the same thing.
Posted: Wed Apr 20, 2016 2:50 pm
by mdavej
No. That's ok since they're virtually identical. I was just thrown off by the 8603.map message. It's fine. False alarm.
Posted: Wed Apr 20, 2016 3:20 pm
by deerewright
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?

Posted: Thu Apr 21, 2016 12:46 am
by Barf
mdavej wrote:Barf,
How about this for covering all Xsight models?
...
Looks OK to me.
Remote download problem
Posted: Thu Jun 16, 2016 2:19 pm
by catmorry
hi newbie here,
Having problems downloading my Nevo C2 to rmir, links to error
and ir files
https://www.hifi-remote.com/forums/dload ... e_id=14099
https://www.hifi-remote.com/forums/dload ... e_id=14100
any help would be very appreciated
Thanks in anticipation
James
Posted: Thu Jun 16, 2016 2:50 pm
by The Robman
Did you connect it to the EZ-RC.com website first?
Posted: Sat Jun 18, 2016 3:40 am
by catmorry
Hi Rob,
Thanks for looking, yes i have already set up remote in EZ-RC
just cant download remote to rmir
James
Re: Remote download problem
Posted: Wed Jun 29, 2016 10:37 am
by mathdon
Sorry for the delay, but I've only just seen this post. I see from your error file that you are using the development version, RMIR v2.04 build 1. Unfortunately there is a bug in that build. I have revised the .jar file since then.
The latest .jar file for v2.04 is here. If you replace the one in build 1 with this, it will update it to build 5. I think that should resolve your problem.
Posted: Wed Jun 29, 2016 2:07 pm
by catmorry
Hi Graham,
Worked perfectly thank you very much
Appreciated
James
Posted: Sat Jul 30, 2016 2:18 pm
by Feuerbard
if anyone need i have full firmware dump from system flash with latest firmware from xsight 8005 and 8002 models (touch and color ) and have dump with old firmware from 8005 model
but cheap chinese programmers like tl866 or rt809f doesn't properly recognise atmel spi dataflash AT45DB321 from this remote
Posted: Mon Aug 08, 2016 5:44 am
by foggy69
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?
I am now running the latest 2.04 build 6 on both Windows XP and a Mac and have run into a new problem. When I open a rmir file, I can no longer view anything in the 'Favourites' tab. I click on the tab and nothing happens. All the other tabs work fine. Going back to 203 build 14, the tab works.
Posted: Mon Aug 08, 2016 7:50 am
by mdavej
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?
I am now running the latest 2.04 build 6 on both Windows XP and a Mac and have run into a new problem. When I open a rmir file, I can no longer view anything in the 'Favourites' tab. I click on the tab and nothing happens. All the other tabs work fine. Going back to 203 build 14, the tab works.
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.
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.
Posted: Mon Aug 08, 2016 4:45 pm
by mathdon
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.