JP1 Remotes

Dear all

I have an OFA URC-8550 with JP1-interface and latest version of IR-software. I'd like to know if its posible to programm my RC to controll a "NEC MT1060" LCD video projector. Or is it generally imposible becouse its not compatible?

thanks in advance.

Check this thread for beginners first.

To get the most out of the remote, you'll need an interface. Not the connector in the remote, but rather a cable to connect your computer to the remote. This is how IR communicates with the remote. I'm not familiar with your remote. Check this thread as well to determine the type of interface you'll need.

Post back after you've gone through this stuff.

The short answer is if your remote is already jp1/jp1x compatible, you should be able to control the device.
jeff

Other people have already posted upgrades for these Nec projectors. Chances are one of these upgrades might work your projector.

NEC 1260 LT260 8910
NEC DP5200 Projector
NEC LT-100
NEC MT820 Projector
NEC-XG Projector

Firstly thank you very much for answers.

I have already the cable, and had already connaction between PC and remote, so it works. At the time I just go through the document "JP1_For_Beginners_Rev1.0.doc" and try to learn how to work with the IR.EXE...

@vickyq2003: can you just give me the link for this NEC MT820. can't find it...

If you click on the file section at the top of the page you can find all of the projector upgrades

File Section

You'll see a list of Device Upgrades
Device Upgrades
Upgrade files for use with either KM or RM.
Sub Category: AC & fans, Audio, Cable, Cameras, CD, Digital STBs, DVD, DVD / VCR combo units, Home Automation, HT Systems, Keyboards, Laser Disc, Misc, MP3 Players, Projectors, PVR, Satellite, Satellite Radio, Tape, TV, TV Combos, VCR, Video Selectors, UEI Official, WAV Files,

Scroll down until you find the item you want. If it ahs a KM icon, it will work with the Keymaster program or the RemoteMaster Program. The RM icons will require Remotemaster.

NEC MT820 Projector

vickyg2003 wrote:If it has a KM icon, it will work with the Keymaster program or the RemoteMaster Program. The RM icons will require Remotemaster.

I'm pretty sure that's only true if the person who uploaded the upgrade file was diligent about setting the icon correctly - it isn't automatically set based on the file extension.

I've come across a number of upgrade files that have either no icon, or have the plain-text icon

@vickyg2003:

Thank you very much for help! I loaded the data of the NEC MT820 and now can even controll my MT1060 with it. So I learned how to upgrade the RC.

But I would like to know how can I get these OBC/EFC codes, and where can I get the protocol of the device I want to control? Is it posible to get them from HEX-codes I learned with WinLIRC?

Assuming it is in prontohex format then yes it is possible to decode that to get the information we typically use. I believe decodeIR handles that but not too familiar with the details.

Question to all who knows WinLIRC and IR !!!

If I have an unknown device nobody deals with before and want to upgrade my URC to controll it, so I need protocoll-ID and the EFCs (or OBCs) for each button-code. Right?
Is it posible to learn the original remote with winLIRC and get the necessary information from its config-file to build an upgrade-sheet in KM?
Or are there other possibilitys to get the protocol-ID etc. ?

In most cases experts here can look at the learned signals in an LIRC conf file at tell you the protocol, device and subdevice and also tell you how to translate each function's lirc hex value into either JP1 hex or OBC

We don't have any software that does that translation.

If you post an LIRC file (or better, the URL for an LIRC file) I'll take a look.

@johnsfine:
Here is my configfile:
#
# this config file was automatically generated
# using WinLIRC 0.6.5 (LIRC 0.6.1pre3) on Mon Feb 11 21:31:16 2008
#
# contributed by
#
# brand: RemoteT6
# model:
# supported devices:
#

begin remote

name RemoteT6
bits 16
flags SPACE_ENC
eps 25
aeps 100

header 9106 4363
one 670 447
zero 670 1575
ptrail 670
repeat 9068 2146
pre_data_bits 16
pre_data 0xFE9B
gap 44361
toggle_bit 0


begin codes
Power 0x000000000000EF10
Mute 0x000000000000B748
1 0x00000000000027D8
2 0x00000000000057A8
3 0x0000000000007788
4 0x0000000000009768
5 0x0000000000006798
6 0x00000000000017E8
7 0x00000000000007F8
8 0x0000000000008778
9 0x00000000000047B8
0 0x0000000000000FF0
up 0x0000000000007F80
down 0x000000000000BF40
- 0x0000000000001FE0
+ 0x000000000000CF30
Set 0x0000000000004FB0
Mem 0x0000000000002FD0
Audio 0x000000000000D728
end codes

end remote

Could you also tell me how to find the protocoll, and EFC/OBC etc. out of these codes? That would be great.

32 total bits (bits plus pre_data_bits), a header roughly 9000,4500 and a repeat roughly 9000,2250 are the major characteristics by which I identify the NEC1 protocol in LIRC files. NEC1 is the protocol I see most in LIRC files.
LIRC usually gets the one and zero backwards as it did this time. But it doesn't always, so you need to check, because in interpreting the rest of the data, you need to know whether one and zero are backwards. For most protocols, including NEC1, the correct "one" has the larger values and the correct "zero" has the smaller values.

Sometimes LIRC gets the split of pre_data_bits vs. bits wrong (correct 32 total but incorrect split). In that case you would need to move bits between the pre_data and the individual codes before interpreting.

In this case the split is right, so we get the device and subdevice from the pre_data and we get the JP1 hex directly from the individual function hex.

That is all easiest in RemoteMaster.

The NEC1 executor in JP1 also has the one and zero reversed. The fact that both LIRC and JP1 are the same for a protocol (both reversed or both non reversed) means we can directly use the LIRC hex numbers as described below:

1) I opened RemoteMaster and filled in most of the setup sheet: Chose a (JP1) remote and a device type and an (arbitrary) setup code number and the Protocol NEC1.

2) I switched temporarily to the Functions sheet to let RM help translate device and subdevice. I typed the device hex FE (from the predata) into the hex column on one row, and the subdevice hex 9B into that column on another row. Then I read the device number 128 and the subdevice number 38 for, the OBC column. That is a surprising device,subdevice combination. I hope I'm doing this right. You'll find out when you test it.

3) Switch back to the setup sheet and put those device and subdevice numbers in the indicated place (leave parm blank).

4) Switch back to the functions sheet. For each function from the LIRC data, find or type the function name in the "Name" column. Then take the two hex digits that are two from the end of the lirc line and type them into the hex column (first two replacing the two we used as a translation tool earlier). For Power the hex code is EF. For Mute it is B7.

RM will compute the EFC and OBC when you type the hex.

If anyone uses this post for general reference later: If LIRC had been opposite JP1 in whether "one" and "zero" were reversed, then you would use the end two digits from the LIRC hex rather than two from the end, and you would need to subtract the device and subdevice number tanslated in step 2 from 255 before using them in step 3. (255 minus 128 is 127. 255 minus 38 is 217).

Thank you very much for the answer, johnsfine! You helped me very well.

So as I see its better to work with RemoteMaster if you have WinLIRC...Using Keymap-master and Devices.xls etc. its more difficult to get the required data for building an upgrade-sheet.

If you don't have RemoteMaster, you can use the EFC calculator from the tools menu of IR.exe

Type a Hex value into the Hex field of the EFC calculator and you can read the OBC number from one of the other fields. For this case (NEC1 with LIRC reversed identically to JP1) that other field is LSBcomp.

But you would go back and forth between KM and IR.exe and end up typing twice as much as if you used RM.

Oh boy! I didn't even notice that there is a calculator in IR! Thanks again!

But how does the calculator convert the codes? Do you know the relation between HEX and EFC/OBC?

And about the protocoll: how did you know that its NEC1? only experience? or are there some sources/files where you can verify it?