JP1 Remotes

re: http://www.remotecentral.com/cgi-bin/mb ... d.cgi?4949

The Robman, Your KM upgrade for the Insignia IS-HCO40917 works perfectly. Thank You.

Johnsfine, The volume and mute are working after following your instructions.

The only problems I have left are the functions mapped to the Menu, Info, and Exit buttons. They are Keymoves. I thought I saw somewhere that there was a diagnostic section but I can't find it so I'm going to copy my file here to see if you can help me with those three functions. Ha I found it:

https://www.hifi-remote.com/forums/dload ... le_id=3217

We need to see your IR file, not just your KM file. Presuming the function OBC/EFC values are correct, the keymoves appear to be proper in KM, but that doesn't mean you don't have a conflict of some other sort in IR.

Are you loading this using a WAV file? If so, when you created the WAY file did you just select "Upgrades"? If so, the keymoves would not be included in the WAV file.

When your JP1 cable arrives, loading keymoves like this will be seemless, but in the meantime you'll need to do a little bit of extra manual work.

Option 1:
You'll notice that there are still four unused buttons available in the upgrade (ie, 0, 9, F.FWD and F.REW) so you could program those three functions to those buttons. You could then copy those buttons to the MENU, INFO and EXIT buttons if you like.

Option 2:
You could program those three buttons using advanced codes (EFCs). Here are the advanced codes for the three buttons: Here's the instructions for programming advanced codes manually on the URC-8910...

1) Hold SET, till screen reads "CODE SET"
2) Scroll down to "KEYMOVER",
3) Press SELECT, screen reads "FROM MODE"
4) Press the device button the code is coming from, screen reads "FROM KEY"
5) Press SETUP, screen reads "SYNT"
6) Type the 3 digit advanced code
7) Press SELECT, screen reads "TO MODE"
8) Press the device button the code is going to, screen reads "TO KEY"
9) Press the button you are trying to program, screen reads "SUCCESS"

Option 3:
Use the entire IR image when creating the WAV file, but be aware that this will overlay all of your current programming (ie, macros, learned signals, keymoves, the setup codes assigned to the device buttons, everything) so it's NOT recommended.

The Robman wrote: Use the entire IR image when creating the WAV file, but be aware that this will overlay all of your current programming (ie, macros, learned signals, keymoves, the setup codes assigned to the device buttons, everything) so it's NOT recommended.

I think Rob is saying "not recommended" only because of the probability that a user is depending on some learned signal or other feature he programmed into the remote and may not realize he depends on and/or may not undestand that it would be overwritten by the full image WAV file.

In the other thread, you stated that you don't have learned signals or other previous programming in your remote, so reprogramming the entire image by WAV file is probably best. Be sure to check through the General Tab in IR.EXE to make sure all features there are the way you want them in the remote.

The Robman, I chose 'entire image' to export the WAV file. I will proceed with your option 2.

Capn Trips, This remote has never been programmed with anything except this upgrade.

Thanks, Jack

If you chose entire image then you shouldn't need to try Rob's option 2.

Hopefully when creating the .wav file in IR.exe you also did a save to create a .ir file, which you could reopen later in IR.exe to adjust any details you got wrong the first time. That .ir file is the one Capn Trips wanted to see to understand what went wrong with the keys that didn't work.

If you are loading an entire image via the WAV file, I would recommend that you re-create all of your settings in the IR file. By that I mean that if you have already assigned setup codes to some of the device buttons, you should replicate that programming in IR.exe. Ditto for any other programming that you might have done, otherwise you will need to re-do it every time you re-load the WAV file.

If you didn't save an IR file the first time through, please repeat the process of copying the upgrade over to IR, then save the file and post it for us to look at. While you're in IR.exe, you should check the keymoves tab to verify that the generated keymoves are there. If they're not there, we don't need to see the IR file as that's the problem. Go back to KM and verify that you don't have the "Disabled Embedded Keymoves" box checked.

Tried The Robman's option 2 and it erased all Insignia info. Tried twice.
Thanks everyone for all of the time you've given me. Here is the link to the ir file:

https://www.hifi-remote.com/forums/dload ... le_id=3219

OK, that was easy. You selected the extender RDF, which will put the keymoves in the wrong place. Re-do the process using the RDF for the regular remote and you'll be fine.

That's great news, The Robman. Looks like light at the end of the tunnel.

Thanks, Jack

Perfection The Robman! It's nice to have another Insignia product in the file section.

I want to thank everyone that has helped me and especially The Robman and Johnsfine.

You've taught me a lot the last couple of days. I feel like now I know 'Just enough to be dangerous'.

Can't wait to get the cable and really dig into this remote and my system.

Cheers, Jack

I hate sounding stupid, but was part of this discussion conducted via PMs? Because I see no other thread in which irs009 has posted. His total number of posts is covered in THIS thread (5 as of this writing). So the casual reader (e.g. ME) has a great deal of difficulty following what's gone on.

Capn Trips wrote:I see no other thread in which irs009 has posted.

At the top of this thread, he included a link to the thread at RC where this conversation started.

Capn Trips, This started on Remote Central. The Robman put the link in my first post on this forum. Thank you for the ir.exe information.

http://www.remotecentral.com/cgi-bin/mb ... d.cgi?4949


Jack

johnsfine wrote:

Capn Trips wrote:I see no other thread in which irs009 has posted.

At the top of this thread, he included a link to the thread at RC where this conversation started.

Actually, John, that link wasn't there until AFTER I posted my first question. and foolishly, I didn't go back and re-read what I had previously "read".

Well, done, Robman