JP1 Remotes

Judging from those pics, I think it's a fairly safe bet that this is a JP1.3 remote. I was hoping that the button codes would be on the PCB too, but they're not, so we will need to get those the old fashioned way using either macros or keymoves.

Oh yeah, PCB means "printed circuit board":
http://en.wikipedia.org/wiki/Printed_circuit_board

PCB=Printed Circuit Board.

It most definitely says "JP1" next to the connector, but since there is no EEPROM, and the remote is clearly designed to support upgrades out-of-the-box, if it WERE a JP1 remote, it would REQUIRE an EEPROM. Therefore it msut be a JP1.x remote.

I'm not smart enough to tell whether it's a JP1.1, 1.2, or 1.3, but I've not seen a mislabelled JP1.3.

I don't recall the HCS08 (JP1.2) remotes having "glob" style MCU chips, which is why I guessed JP1.3. But regardless, it's definitely not old JP1 without an EEPROM, so getting a JP1.x cable is your next move.

While there's always a chance that it could be a JP1.1 remote, UEI used that chip for such a short period of time, that I really doubt that it is, so you should be safe with a JP1.2/3 cable.

I just ordered a JP1.2/3 interface cable. Unfortunately there where only
US sources and I am in Vienna (Austria). Therefor it will take some time,
until I can continue.

BTW: I am really happy with this remote! It's a lot faster than the logitech
I had before (who needs a display on the remote ?), the macros work good,
and it can control the IR switchable light in the bedroom. So I bought a
second one today

alext wrote:It is possible to generate a .wav from a jp1 file ? I haven't found this yet. (any link, and what are the magic numbers to activate this upgrade procedure ?)

Yes, it is possible using IRtoWAV in conjunction with RM and IR.exe. But since you've purchased a JP1.2/3 cable, it makes no sense to try to install an upgrade via a WAV file. The cable is far more secure and convenient, especially since there is some question about the correct RDF file.

... plus, we need to know a lot more about the remote before we can set things up so that you can use the tools to create WAV files. It's not usually an option for the first person who brings a remote to the JP1 group.

But, hopefully once you've got your cable we can help you use it to get the info that we need from the remote and then the next person can indeed use the JP1 tools to create a WAV file.

All flash remotes use a chip that is square, with 11 pins on each side. Often pin 1 is identified by a number "1", a white dot, or both, and the pin numbers increment in counterclockwise fashion (or anticlockwise, for our friends across the pond). For JP1.3 remotes the ceramic resonator Y1 is connected to pins 7 and 8, but for JP1.2 remotes it is connected to pins 28 and 29. As you can see from img_3858.jpg (an excellent quality picture, by the way) this is a JP1.2.

URC-9040 is definitly a JP1.2 remote with HCS08.
The Hardware is the same as URC-8350, which I have too.
I'm working on a RDF for both.

Hi Uwe, welcome back!

I received the jp1.2 interface today, configured a win computer and downloaded the remote eeprom. As expected he didn't find a rdf file.

The information I found till now is:
ModelID: 11131113
EEpromSize: $1800 (6k?)

Is there a howto how I should proceed now ?

Thanks...

Post your IR file.
List the device buttons and what setup codes are assigned to them.

Status: You find the IR file on http://mail.at/9040/
9040-1.ir has mapped enter to the red button and
9040-2.ir has mapped "1" to the red button in PC mode
(difference 0x14<->0x15 on position 0x0030)

The device keys are labeled: TV, PC, AUDIO, STB

The device codes are:
TV: 11312
AUDIO: 31320
STB: 01561
PC: not set (RF sender mode)

I was curious and read through the hex codes a little bit and
found those device codes, when I split them as 1 - 1312:
TV: nibble 0x1, 3 nibbles 0x520 on position 0x0c
AUDIO: nibble 0x3, 3 nibbles 0x528 on position 0x10
STB: nibble 0x0, 3 nibbles 0x619 on position 0x0a

At position 0x0e there seems to be the code for "PC" 0x2 341

I'm sure those results are obvious for you, but I like this kind of riddles
and wanted to give it a try.

Here's a starter RDF:
http://www.hifi-remote.com/forums/dload ... le_id=6907

Thanks for the starter file.

On http://mail.at/9040/ you can find an updated version with correct
button codes. Now all the macros show up correctly. I also tried to
change macros and upload the config successfully.

This Dev5 is very strange. It seems to be related to the PC Feature
or this remote, because the only keymove which is in PC mode shows
up as Dev5.

What's next ?

As you know, the color buttons don't send anything in PC mode but it's
possible to "keymove" a button "1" to "red" in PC mode. I tried to change
this keymove using the IR8 software so that "red" is sending an other
keyboard scan code. I thought "efc" or "hex cmd" instead of "key" should
work. But it doesn't.

In PC mode the remote uses a strange setup code "3749", which is
actually the original code 1701 + 2048 (3rd bit in highbyte). 3749 is
rejected in IR8 (to high). But I could solve this by changing this byte
in raw data mode.

But still I can only copy keycodes from one button to the other. If I
change from "keymove" to "EFC" (03 -> 04 in rawmode), the remote still
sends only the scan code of the related button an not a new scan
code.
i.g. with keymove "dev5" "red" -> "dev5" "Hexcmd" 0x1515 it sends the
scan code of button 0x15 ("1").
If I type in other numbers instead of 0x15 with no related buttons the
remote sends nothing.

Now the question comes in mind: who is translating button codes to
keyboard scan codes in RF mode.
Is it the URC Software like in IR mode, and how can I change it ?
Is it the RF transmitter "hard wired" ?
Or is it the RF receiver ?

If the scan code mapping is not done in the URC Software I am probably
stuck. But how can I find out..

Thanks for your time...