JP1 Remotes

[Boet]

Hi,

I hope I posted this question in the right section...
On remotecentral.com I looked up the Pronto HEX codes for my Barco 701 CRT projector, and pasted them in IR tool to decode them. So far, so good.
DecodeIR DLL returns:
Protocol: pid-002A
Device: 0.-1
OBC: 14
EFC: 46

Now, when I enter the EFC in RM, the OBC automatically generated by RM doesn't match DecodeIR's decoded output.
The same thing the other way around, when I change OBC to 14, RM automatically changes the EFC, which doesn't match DecodeIR's output.
The same thing occurs in KM, however it generates other (non-matching) codes.
In other words, I can't enter the OBC and EFC decoded by DecodeIR DLL.

When I try to use the remote with a correct OBC and a wronly generated EFC, or a correct EFC and wronly generated OBC, the projector simply doesn't respond.

I found two tables on hifi-remote (EFC -> OBC and OBC -> EFC), http://hifi-remote.com/wasser/MakeEFCTable.shtml, but DecodeIR's codes don't match those tables either.

The HEX code used: 0000 006D 0000 000E 0000 0017 0000 0005 0000 0005 0000 0005 0000 0005 0000 0005 0000 0005 0000 000D 0000 000D 0000 000D 0000 0005 0000 0005 0000 0017 0000 129D
(There's many more, but I wanted to try to get the power button working first).

The remote I'm trying to re-program is an URC-3940 with JP1.3 by One For All.

Another question I haven't been able to find an answer to: When upgrading the remote, the upgrade is loaded in (for example) setup code 1808 under the TV button.
If I press the TV-button, does the remote automatically select the setup code (1808), or do I have to assign the setup code to the TV-key manually? Because the setup codes are only four digits, while the setup codes in the remote its manual are five digits.

If anyone could help me out, that would be highly appreciated.



Boet

[vickyg2003]

when working with a decode ALWAYS use the OBC. The EFC may or may not match depending on which executor is used..

Hopefully this link EFCs or OBCs will explain this fully.

[cauer29]

I could be wrong, but the pronto hex you posted seems to be malformed. Normally, word 4 is the on time of the first burst pair. It would seem to be a bit non-sensical for that to be 0000. Furthermore, none of the burst pairs have non-zero values for on times. Interpreted literally, you can transmit this IR by simply doing nothing.

I suspect that there is a typo there somewhere. Though the mostly deprecated IRTool manages to come up with something, none of the other JP1 tools (IR Scope, IR) can do anything with this pronto hex. In fact, IR gets some sort of floating point error on an attempted import, while IR Scope crashes entirely.

Could you point us to where you found this pronto hex on remotecentral?

A.A.

[Boet]

Thanks vickyg2003, I will read it thoroughly this evening.
Cauer29, I found the HEX codes on http://www.remotecentral.com/cgi-bin/codes/barco/701s_address_0 .

Elsewhere I found EFC/OBC codes for the Barco Data 708 once decoded by jon_armstrong, and the EFC/OBC's matched IRTool's decoded output. So I assume those two are correct at least...

[cauer29]

[3FG]

Barco is an unmodulated code, with a very short on burst--10microseconds. Most remotes don't learn it well. A completely valid Pronto Hex would start with 0100, indicating unmodulated rather than 0000. Of course, 10uS is a lot like zero, unless the Pronto Hex indicates a very high frequency.

Anyway, the decode is probably correct. If the Barco upgrade doesn't work, I suggest you edit protocols.ini, replacing pid:00 2A with the following:

[Barco]
PID=00 2A
DevParms=Device:5=0, dev flip:bool
DeviceTranslator=Translator(lsb,comp,0,5,0) Translator(1,1,7)
FixedData=08
CmdParms=OBC:6=0
CmdTranslator=Translator(lsb,comp,0,6,0)
Code.S3C80=00 00 11 8B 14 85 E5 80 00 05 06 00 05 00 19 00 05 00 4B F9 6A 00 05 00 7D 76 03 01 EB 03 46 2B 01 8D 01 49
Code.740=00 00 11 80 0F E0 D0 40 03 05 07 01 09 01 2B 01 18 03 01 50 A5 5D 85 5F 49 78 07 5D 02 85 5D 22 00 A5 73 22 37 3C 02 5B A2 47 A0 A7 22 44 22 06 90 ED 60
Code.6805-C9=00 00 11 20 0F E0 D0 40 07 05 07 01 07 01 2B 01 18 07 01 53 B6 5A B7 5C A8 78 00 5A 02 B7 5A CD 01 83 CD 01 B2 A6 02 B7 58 A6 AD AE 78 CD 01 9E CD 01 8C 24 EA 81
Code.6805-RC16/18=00 00 11 20 12 85 E5 80 00 05 06 00 02 17 00 02 30 7C BF 00 00 02 49 00 5A 02 10_7E CC 01 B2
Code.HCS08=20 17 00 00 11 85 E5 80 00 05 06 00 04 00 2D 00 04 00 5F F9 7E 00 04 00 91 00 60 02 10 A5 CC FF 5C

It may be necessary to turn on dev flip, which tells the executor to complement some of the device bits. Also, if Device= 0 doesn't work, try Device = 31, with dev flip both unchecked and checked.

Actually, I hope you will try this change to protocols.ini. If it works, we can include it in subsequent versions.

[Boet]

Yes, I've tried that one, but the projector didn't respond to any key I pressed.
I wondered whether I have to set up anything on the remote itself after disconnecting it from the computer, besides pressing the "TV" button. If so, that would explain a lot why it doesn't work.


I just opened a Barco 701s PCF file in ProntoEdit, but IRTool doesn't decode the HEX codes I extract from the PCF file ("The hex code is not a learned code").
The power-button code in the PCF file is 0100 000D 0000 000E 0003 005F 0003 001C 0003 0038 0003 001C 0003 001C 0003 003E 0003 001C 0003 003E 0003 003E 0003 0038 0003 001C 0003 001C 0003 005A 0003 8EC5.
The PCF file is also one I got from remotecentral, from the following link:
http://files.remotecentral.com/collection/2919-1/index.html

Thanks 3FG, I will try it in a few moments. How exactly do I turn dev flip on and off? I don't see an option in RM itself, neither a 'true' or 'false'.

Thanks for all the help so far!


Oh, I noticed the HEX-code I posted in my first post was the wrong one (address 1, while I need an address 0 code). Sorry about that, I got confused while trying every code I guess. The link I provided however points to the correct codes.
The "device" code is 18 in the address 0 code as opposed to 0 in the address 1 code. Do I need to try 18 and 31, 3FG?

[3FG]

The PCF is well formed and reports device = 18, so I would try that first. I'll keeping looking at the decode.
We'll get this; we just need to make sure that we handle the complements and bit reversals correctly.

[vickyg2003]

Dave, you're using vocuablulary that is over my head.

[cauer29]

[Boet]

I've tried your protocols.ini settings, both with device = 18 and device = 31, but without luck.
I've programmed OBC 14 under the "OK" key in the upgrade file, so I can test both the decoded HEX and the upgrade file without having to program twice every time.

[cauer29]

[Boet]

How do I paste learned signals into IR? All buttons in the "Learned Signals" tab are always grey.

[vickyg2003]

[Boet]

All right, the protocol.ini change wasn't working. I found out I had to change [Barco] into [pid: 00 2A], else it wouldn't show up in RM IR.
Let's give it another try...