JP1 Remotes

Can't find info on these anywhere.

In a probably larger "anywhere" than you checked, I also couldn't find that.

I did find something that said an RJTech 4000 is a DVD player. Most people reading this wouldn't know that and such information often helps.

You're also supposed to tell us which model OFA or RS remote you have. If it's a learning model then you can create the upgrade yourself.

Giving better information with the question will usually get you a better answer.

I have a URC-8810.
the RJ 4000 is a divx/dvd player.

when I capture the buttons from the OEM remote, the IR program either can't recognize the protocol or are differing protocals , everything from NEC to GAP.

its not an easy thing to decipher.

resago2001 wrote: when I capture the buttons from the OEM remote, the IR program either can't recognize the protocol or are differing protocals , everything from NEC to GAP.

NEC decodes are very rarely wrong (so if any of the decodes say NEC probably all the decodes are NEC). NEC is a very easy protocol for the 8810 to learn, so if NEC is correct but isn't decoded consistently then you probably are doing something wrong in the learning process and/or the batteries in the original remote are bad.

GAP decodes are always wrong. If they appear in the same signal as some other decode, they should be ignored. If they appear in a signal that has no other decode then they give diagnostic information which helps an expert figure out the correct decode.

Several DVD code sets are consistent across multiple brands. If you tell use the device and subdevice numbers from the NEC decodes we can probably identify the whole code set.

For hard decode problems (as this is if the above suggestions don't solve it) it is best to save an eeprom image file containing the learned signals and upload to the yahoo jp1 diagnosis folder and post the url back here.

Waka Waka

Upgrade Code 0 = 16 82 (DVD/1666) RJTech RJ4000 Divx/DVD (KM v8.26)
5A 11 5E FA F8 61 00 FF FF 0D 35 87 4F 77 A7 7D
67 B7 D7 27 DD FD 37 8F 5D F7 47 3D BD
End

for the urc-8810
I'll upload the full file in a minute.
Didn't think I'd be uploading my first remote code set in 24hrs from coming across this site and building my own cable. 8)

Not bad going!

Does anyone recognise this code set as a pre-defined code set?

If so, I'm sure a number of people without jp1 remotes would like to know what it is.

resago2001 wrote:Does anyone recognise this code set as a pre-defined code set?

I'm pretty sure there is no built-in setup code for this. I have no idea whether OFA customer support has an upgrade for it.

There are many different setup codes for NEC1 device 0. Most models have one built in, so if you want to use a lot of KeyMove memory, you could construct support for this device as a bunch of KeyMoves from some other NEC1:0 setup code.

There are many other upgrades in that folder where you loaded this one that are also NEC1 device 0. I did a rough scan of those. I might have missed something, but I don't think any of them have similar OBC numbering to the one you uploaded.

Many of the built-in setup codes for NEC1:0 in various model remotes are DVD setup codes. I checked those more carefully and none have similar OBC numbering to this.

There are also many NEC1:0 DVD entries in CCF files at RC. I checked all of those to see if any other brand duplicated this OBC numbering. None did.

WOW. should we send this in to OFA for thier customers' sake?

Just FYI, decide code 0 is an "un-regulated" code from NEC's point of view. I think their intent was for people just to use it as a test code or something like that, but obviously alot of OEMs have decided to go ahead and use it as a real production code, presumably because they don't have to fill out paperwork or pay a license fee or whatever it is that you normally do when you want to grab a new remote code.

From the consumer point of view, this is not a good thing as there are now alot of devices that all use the same code, so with only 256 EFCs to chose from, there's going to be alot of chances for code overlap.