RDF Map and pic for Insignia NS-RMT5D21 with A B C in Place of APP 1 APP2 APP3
http://www.hifi-remote.com/forums/dload ... 821e0a4577
370601 Insignia NS-RMT5D21
-
The Robman
- Site Owner
- Posts: 21886
- Joined: Fri Aug 01, 2003 9:37 am
- Location: Chicago, IL
- Contact:
Re: Insignia NS-RMT5D21
Yeah, I didn't miss the A/B/C buttons, but as you'd called them App1/2/3 in the RDF, and the user manual calls them application buttons, I just ran with it. My goal here was to create a working map, not to re-work the RDF as you seemed happy with it.HamburgerHelper1 wrote:Rob
Your map definitely better than mine especially for the polygons on the direction keys
and the closeness on the Rewind/ FFwd(Held) keys
But you missed that Insignia changed App 1 2 3 to A B C
also I am still getting error on keycode 72 and 71 which is weird
because I was expectiing your map to clear up that problem
Randy
EDIT
I just noticed that App 1 2 3 was in the RDF as well so that is one of the older RDF''S
And when I tried creating an RMDU file using RM, I didn't get any of the map errors that you listed earlier.
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
As I explained in my earlier posts, the errors do not arise from any file of the Insignia. They come from the RDF of the URC-3660 v2 which has buttons missing by mistake and which has the same signature and is processed by RMIR on a download (only) of the Insignia as it tries to identify which remote of this signature is being downloaded.The Robman wrote:when I tried creating an RMDU file using RM, I didn't get any of the map errors that you listed earlier.
You saw App1 etc in the RDF as you were not using the latest draft RDF for the remote.
Graham