JP1 Remotes

ok ive been at this for days slashing through fourms and i know that i have to have an extender to get this to work. I have the urc-6131n remote w/ 2k. I finally figured out that you had to add the upgrade device for the lkp function to be accessible under the special protocals function. But i keep getting an error after i enter what i want the lkp function to do: "This function will not work correctly until you load the associated Special Protocol (o1f9)." i hit ok and the code shows up but it doesn't work. the code looks something like this ... PVR 0 LKP(2) = [Short]:Shift-0 [Long]:XShift-0 $21 $9F $DF

Look in your protocols tab. Is protocol 01F9 listed there? If not, you need to add it. That protocol should have been automatically loaded if you used IR's "Merge using Extinstall" function to create your extended IR file from your unextended IR file. If you're just starting from a blank IR screen and selecting the 6131 2K Extender rdf, you need to add this protocol upgrade:

Upgrade Protocol 0 = 01 F9 (S3C8+) LDKP Protocol
00 00 01 E4 03 4A F0 4A 56 4A 0F F6 1F 80 56 03
07 38 3A 26 C3 03 76 2D 08 EB 0C F6 13 EE FB 1F
76 6B 20 6B F6 8B 1C C6 C0 25 00 F6 01 0D 56 6B
7F E6 F1 FF 6F 76 6B 80 EB 09 76 6B 20 6B F5 38
03 B0 03 A4 03 C3 2B 0D 87 43 2D A6 7F 80 3B 05
82 7F C4 3A EE AF
End

hey thanks capn trips. That got the error message to go away, but i still cant get it to work right. I've posted a copies of my rm and ir files if you or anyone else can give me some more help. This is for my xbox to use with xbox media center. What i want to do is have for example short0 to execute shift 0 and long0 to execute xshit 0. i have defined those in rm to be: shift 0 = actual mircrosoft xbox 0 code and xshift 0= custom code that will execute whatever i define the xbox to do when it get that specific code. in other words if i hold 0 long press it will automatically boot to my super nintendo emulator. thanks link: https://www.hifi-remote.com/forums/dload ... le_id=2814

OK dtw, although the actual LKP Special Function Keymoves are properly built, almost nothing else in your IR file is.

Your IR file has all sorts of problems, not the least of which is you don't have the MINIMUM REQUIRED Special Protocol and Device Upgrades for running this Extender (Device TV:1800 using Protocol 0180).

Further, your DSM and Device Multiplexor Devices will not work, since you don't have THEIR Special Protocols installed. And I have no idea what your VCR/DVD:1104 Device upgrade is, but it AIN'T LKP - these special protocols have no buttons preassigned in the device upgrade. What I suggested in my earlier post is exactly what you did. You are just trying to create an extender IR file from scratch - CANNOT BE DONE!

Here's what you need to do:

PREP PHASE:
(0) Ensure you have downloaded and unzipped the appropriate 6131 extender file from the extender section of the file area - and KNOW where you unzipped it to; READ ITS README!
(0.1) Ensure you have the latest rdf files downloaded from the tools section - these SUPERCEDE ANY RDF's packaged with the extender! So delete the two rdf's that came with the extender zip file;
(0.2) Ensure you have downloaded and installed the Extinstall program from the program file area - then in IR "File">"Set Directory">"Extinstall Path" TELL IR where the Extinstall program is.

EXECUTION PHASE:
(1) Open a blank IR file;
(2) Select the 6131 (unextended) 2K rdf in IR;
(3) Select "File">"Merge Using Extinstall" and a PROPER extender version of your IR file will be created, using the correct rdf, and preinstalling the REQUIRED protocol and device upgrades, PLUS a bunch of special protocols and devices. You can then delete the Special Device and Protocol upgrades you don't want, but KEEP the ones you need (by the way, LKP is usually TV:1106)

Then you can start adding all of your other device upgrades (It looks like you only have one right now, so that's easy to duplicate) creating all of your Keymoves and Special Protocol functions and macros, etc.

UNRELATED COMMENT:

The way you want your number buttons to work for this device using LKP is not at all an unusual way to use LKP, BUT you can save on all of the keymoves you created for the shifted-Number keys, if (as you say) all you want is for "shift-X" to execute what is on the "unshifted X" key when you call it in the LKP. Simply delete all of the keymoves for the "shift-X" keys - and when your LKP calls "shift-X" the remote will see that there is nothing assigned to "shift-X" and will then execute the "unshifted-X" function - this is a phenomenon which many take advantage of called "Shift-cloaking"

Wow Capn Trips. THANK YOU VERY VERY MUCH !!!!!!!!!!!!!!!!!!!

That worked great. I didn't know you had 2 download the extender ... i thought it was in the rdf files pack and you just had to select the extender in rm or ir and it would load everything it needed. I was about to give up with all the protocol stuff and can the remote ... but now ... it works like a charm. Your advice even helped fix another problem!!! There is a tutorial about rewiring the path of the audio cc buttons on the 6131n to give 2 different buttons. problem was the other button became dev8. But running the extender lets me use it as just another button! I can't thank you enough! I can't believe the functionality of this remote for the pennies it seems i've put into it. Never again will i go for a non jp1 remote! Except i haven't seen anything about using a jp1-like remote to send radio frequency signals. A combo jp1 infra red / radio frequency remote would be unstoppable. I digress ... Thank you again!

Well, I'm glad to have helped, but apparently you hadn't read quite enough

A handful of JP1 remotes have RF extenders (in addition to their inherent IR transmitter, they have an RF transmitter), with associated base stations to receive the RF and transmit the IR signal.

These include the Radio Shack RS 15-2117, URC 9910, HTPro (all out of production, but available here and there) and I believe some of the newer Kameleons (URC 9962) also have this capability.

Mind you, these are just RF extenders to the IR signals. If your OEM remote transmits RF only, you won't be able to learn/decode/reconstitute the RF signal (like the Video 2 mode on Dish receivers).

Capn, I have a slightly different view of this section:

Capn Trips wrote: EXECUTION PHASE:
(1) Open a blank IR file;
(2) Select the 6131 (unextended) 2K rdf in IR;
(3) Select "File">"Merge Using Extinstall" and a PROPER extender version of your IR file will be created, using the correct rdf, and preinstalling the REQUIRED protocol and device upgrades, PLUS a bunch of special protocols and devices. You can then delete the Special Device and Protocol upgrades you don't want, but KEEP the ones you need (by the way, LKP is usually TV:1106)

Then you can start adding all of your other device upgrades (It looks like you only have one right now, so that's easy to duplicate) creating all of your Keymoves and Special Protocol functions and macros, etc.

I think the purpose of Extinstall is to merge the extender into the open, existing, IR file with the intention of preserving your upgrades, keymoves and macros. Well, in 6131, keymove format is different, so you need to rebuild those to standard. Aditionally, Extinstall drops all notes, and is very finicky about its location, spitting error messages which you can hardly deal with. Given all this, I found it much simpler to just use the extender .txt file, add upgrades and redo the keymoves using previously preserved Summary or previous configuration in another window. Just tossing in an opinion

The problem with your approach Liz, is that you will start building an IR file using the extender rdf, BUT NOTHING ELSE! In fact, that is exactly what the original poster in this thread did and got himself into all kinds of trouble. You REALLY have to know what you're doing to figure out how to add the correct Device and Protocol upgrades for the EXTENDER ITSELF (TV/1800), and any of the extender-unique Special protocols like ToadTog (MISC/1800) and others. Individual installation of any of these is not explained ANYWHERE in the documentaion or fora, as far as I know. Using Extinstall gets all of that done, and you customize by DELETION rather than by ADDITION. Easier, imho.

Further, although you CAN use it on an existing unextended IR file (to preserve upgrades and Keymoves, etc.) you don't HAVE to. It works just fine on a bare IR file.

You have to redo Keymoves and notes regardless, so that's no benefit to your method (imho).

To each his/her own, I suppose

...but my way is better

Capn Trips wrote:...but my way is better

Oh, no MY IS

In the extender zip file for 2K remote is 6131_extender1_.txt. Open that in IR already setup to see the 2K RDF, and it all comes in. Every protocol. Every device.

I've gone down both routes. This was much simpler for me. Now, for 1K remote you get just the extender, and you pick and choose from Mike's zip file which protocols to add.

I didn't know you can run Extinstall on a bare IR file. That's precisely the effect of what I'm doing anyway (nothing to merge). So the methods merge

In case anyone is reading this serious debate, EXTINSTALL does a wonderful job. It just the trouble with paths annoyed me. IR didn't like different drive letters even when IR was told where RDF is and where Extinstall is.

Jeez, I just read the README file and the extender worked fine. Was I wrong?

If you're moving from unextended to extended remote use then - IMHO - it's time to do a bit of spring cleaning and start afresh with your upgrades and IR file since there will be several things that worked fine in the unextended remote but that would benefit from a change for the extended use. Anyway if your setup was perfect (The Robman's must be close 'cos he doesn't use an extender) then you wouldn't be installing the extender, would you?

ElizabethD wrote:

Capn Trips wrote:...but my way is better

Oh, no MY IS

In the extender zip file for 2K remote is 6131_extender1_.txt. Open that in IR already setup to see the 2K RDF, and it all comes in. Every protocol. Every device.

Oh really! (he said, continuing in a terrible Johnny Carson imitation..) "I did not know that."

I agree the methods are equivalent, so you win, Liz.

I will say in my defense, however, that many extender zip files do NOT come with such a "bare" extender IR .txt file, but only with rdf's, the .hex file and a readme, so your method may not be available for certain extenders.

Not to pile on Capn , but I did/do it Elizabeth's way with the 8811 (same extender she's using) and it worked just fine. I've also done it her way with the 8910 and it seemed to work okay as well. you get all your devices. You just need to setup your macros, dsm's, lkp, pause, etc..

Best,
jeff

UNCLE!

I submit!

You guys are funny!

underquark wrote:Jeez, I just read the README file and the extender worked fine. Was I wrong?

Did we learn in logic class in school that if it works, we're not wrong or am I making that up
Readme.txt file took me to install.txt instructions (a painful process on 8910 long ago). Here I took point zero alternative and returned to readme in minutes. Done. Worked great. I didn't fancy editing 50+ hex values for keymoves, which would require opening KM or RM anyway. And early spring cleanup fell into place. And don't forget that the whole point of this madness was to redesign to use extender features anyway. BTW if anyone reaches point 2 of 6131 install.txt, it takes you to 1994 remote, oops.

Capn Trips wrote:...many extender zip files do NOT come with such a "bare" extender IR .txt file, but only with rdf's, the .hex file and a readme, so your method may not be available for certain extenders.

Good point. Couldn't agree more. BTW 7800 is another one that allowed the easy way out via .txt file. Docs are a drag. I'd rather see the experts here do real inventions than edit couple hundred readmes. Perhaps a "documentation specialist" will come along and enjoy editing