JP1 Remotes

sorry for being a noob, but we all gotta start somewhere...

1. Device: JVC TH-A5 "Home Theater"
2. Type of device: DVD/Audio
3. Remote model: URC-7544
4. JP1 user? Yes
5. Still have original remote? Yes
6. Checked Yahoo file section? Yes
7. Checked Pronto file section (at R/C)? Yes (See below!)

I've made my own cable, and can download the current settings, so happy there. I've read the tutes, and have a basic understanding of the codes. I found a ccf that contains a number of different devices, including a TH-A9 which was around the same age, but no guarantees it will be identical.

I've converted the ccf to text with decodeCCF.exe, and can view it in excel, so I can see the Protocol, Device ID, OBC and EFC.

Following the online tute I've used KM to create a new device upgrade, and upload it to the remote, but It's not working. I set the code to 1111 and the type to VCR.

I'm getting very confused, as there's just so much info I'm overloading.

In the conversion of the ccf file I have 2 JVC protocols - JVC and JVC{2}, and the device ID is 239 AND 163, I can only assume it's due to the fact that the machine is both a DVD player and Audio device.

I'm further confused by the decodeCCF.exe in that all of the commands are listed 5 times with a different decode.

So I'm stumped.

Does anyone know if these 2001/2002 genus JVC machines should be JVC or JVC/48?

Do you think the codes will be the same for the TH-A5 and the TH-A9?

If I were to try plugging away at the advanced codes one by one, how do I set my URC-7544 to talk to the JVC? It doesn't have an LED indicator that it's receiving an IR signal, so I can't see anything happen unless I fluke a code.

Can the URC-7544 cope with 2 device ID's in one device definition? It only seems to care for JVC/48, but I can't tell if it's right or not.

fyi:
and: thanks both for the tutes and files and in anticipation of a pointer.

I assume this is the ccf file you found: JVC TH-A9R

I actually found three device codes in there: 163, 239 and 175. The correct protocol to use is JVC (not JVC-48). Ignore the way each button shows up 4 or 5 times, that's just because the signals were poorly learned, and ignore the JVC(2) stuff, that's just a quirk of DecodeIR, which I think is also related to the poor learning technic used.

You should be able to create 3 seperate upgrades to work all of these functions, using the JVC protocol and the correct device code (it doesn't matter what setup code you use for the upgrades).

Actually, I just created a device upgrade incorporating a JVC combination protocol and put that file here. Test is out and see if it works. You must copy both the device and protocol upgrade into IR. That way everything is in one device upgrade. I didn't assign many buttons. On the function names I put menu+name from that ccf file unless that didn't make sense. I also guessed at a discrete power On and Off at the bottom of the functions tab based on what ususally works for JVC gear.

Rob, that's the beast. I missed the 175 code, but it's only one function, so I wasn't worried.

So If I create the individual device codes I should be able to use a macro or key for it? Is that where you're going? I have no idea what that actually means - I'm just guessing.

Jon - did you do that for me? Sweet, but it doesn't work.

I've imported the protocol, the device, set the button to cable 2005, but nothing flies. I think the A9 is different from the A5 somehow.

Is it odd that I cannot find the right code via the search function? I've set the button to VCR, done the 992 search thing then bashed away - I know it's searching as it found the JVC VCR OK, but it still won't find the JCV HT. I tested this using the play button...

Can someone just take a quick look at the last question of mine about not being able to find it via search?

I would have thought it would work, but it really doesn't want to...

The search function only works when there's a valid code to be found. If the code that you need isn't in the remote, it won't find it, that's the main reason why we started JP1.

ahh, thanks.

So we're at the point where the only way I'm going to get anywhere is with a JP1 remote with learning.

I'm a (former) radio tradesman, so I'm reading up on Tommy's IR receiver to see if that helps...

If you're confident that you tried the codes properly that you found in that CCF file and they didn't work, then yes, a learning remote would be the way to go.

You don't list where you're located in your profile but I assume you're in Europe somewhere because you're using a URC-7544. The URC-7560/7562 is the cheapest learning remote in Europe (that I know of), but even that's not cheap.

I can sell you a URC-8811 for $29.50 total (that's $19 for the remote, $9 for shipping and $1.50 paypal CC surcharge), so if that's cheaper than you can get a learning remote locally, let me know.

I'm in Australia, and my URC-7544 cost me $50 Aussie.

Your learning remote, plus p&h will cost me $38.80 Aussie.

I've been ripped off!

Maybe I'll get the 8811 or the 8910 and send the 7544 to the back room for the kids.

argh!

I don't know why OFA remotes are so expensive over in Europe and Australia because they're very reasonably priced over here.

Just FYI, I can fit up to 3 remotes into the box that I use, so I could ship them all for the same $9 flat rate.

well, well, well..

the remotes arrived today thanks rob.

I've learned three codes from the JVC TH-A5 remote and lo, they are NEC2 protocol device 67 sub 83!

That's freaky - either JVC rebadged the home theater or they just used NEC chips or something. Very strange...

Are you sure that's NEC2, not NECx2?
Are you using a current version of DecodeIr.dll?
I think setup code Audio/1295 is NECx2:67.83

yeah - it's necx2, but detected as nec2 in IR6.

I'll check the decodeir.dll now - I thought I had the current, but I am getting some funky stuff with my foxtel (aka sky digital) remote at the moment.

I found 1295 in devices4.xls, but it's not in any other documentation, so had to build entirely from scratch.

my decodeir.dll is dated Tuesday, 14 December 2004, 6:00:00 AM

harley wrote:yeah - it's necx2, but detected as nec2 in IR6.

Now you really lost me.

If IR6 says its nec2, how do you know its necx2?

Did you check the option (in IR's advanced menu) to disable DecodeIr?

Without DecodeIr, IR won't distinguish NEC2 from NECx2. But with DecodeIr, I don't know any version any where near current that should get that wrong.

hehe...

I guessed it was NECX2 on the basis that NEC2 didn't work, and that the device4.xls said the 67:83 code was NECX2. So I flipped it over and it all worked.

I have not disabled decodeir.dll, and it is in the c:\windows\system32 folder.