Hi,
I have learnt an RC5 code from a Philips Remote. After that I have also created a Philips code using CSF Creator, as I need to create a big number of Philips RC5 codes which I need to use with an austrian home automation system.

I managed to create the hex code in CSF Creator to match the learnt one, it also works when testing...but once transferred to the remote it doesnt work realiably.

you can find a test pcf here: [Link: lowenstein.netlantic.net]

the Button number 2 in default style works the one above in brown doesn't, although both contain the same visible parameters. the additional "2 " at the bottom is just a copy of the top default style which works as well.

I would appreciate any help...
stephen

Since they all looked the same, I was puzzled. In PPENG they all came up as:

5000 0000 0000 0001 000C 0002

I went to the undelying code in xml. Your three two's were:

21 0 f 6e 2 65 a8 20 40 3f 4f af 24 1 d8 cf d3 2b 4c 0 f6 d

15 0 f 6c 2 61 a7 20 40 3f 4f 5e 49 2 b0 6f

21 0 f 6e 2 65 a8 20 40 3f 4f af 24 1 d8 cf d3 2b 4c 0 f6 d

I created a pcf file by entering:

5000 0000 0000 0001 000C 0002

and got this:

21 0 f 6e 2 65 a8 20 40 3f 4f af 24 1 d8 cf d3 2b 4c 0 f6 d

So I think you imported or copied an RC5 commands in the learned format starting with a 0000 and that is usually a bad idea in a Pronto since you usually lose functionality. I am assuming that one didn't work.

It so easy to generate the 5000 format codes in Excel, whay not do that:

always start with 5000 0000 0000 0001

and add:

000C system address in hex (12 decimal)

0002 command in hex

I've just started to look at the underlying xml code and I understand it for a number of protocols but I can't explain the difference yet for RC5. I have created learned RC5 commands too and they always are shorter than the ones entered in the database format. My guess is that the toggle bit doesn't work in the ones impoted from CSF Creator.

JArmstrong,

I have the same issue with legacy Pronto 7000 (not the remote model, but the IR code format specifier) format codes that are a derivation of the RC6 protocol used for my Streamzap remote.

If you come up with meaning, I'd love to know what it is. What I found was that some of the codes, following an import into PPENG, cause double presses. I'm gonna ship the original CCF and my PCF to the ProntoTeam in the future for comments but I'm not yet ready to do so. I'd love any info you can provide. Email me if you'd like.

I'll take a closer look. The Streamzap protocol is just like RC5 with an extra system address bit. So even if we don't understand everything we can probably come up with a solution. If you can export just the ccf and pcf files for the Streamzap, I'll take a look. Email is in my profile.

Thanks for the answer!

The funny thing in this case is that the learned RC5 command is the one which works. The two longer ones are the RC5 created in CSF creator. As I've only started to play with the TSU7000: how did you get to look at the underlying XML and how would you go about importing the Excel created value?

rgds
Stephen

Perhaps, that is because you application doesn't use the toggle bit typically in RC5? I get the "short" version when I use MakeHex and create an RC5 command in the learned forrmat, create a ccf file in IRPanels and import. The Long version comes from using entering the 5000 format directly into PPENG. I just got this from coping the learned fromat from MakeHex into PPENG of RC5:12:2:

15 0 f 6c 2 65 a8 20 40 3f 4f 5e 49 2 b0 6f

That's a slightly different command from above and I haven't yet come up with the decoding scheme for RC5, but you could paste this into PPENG and see if it works:

Device Code: 12 Function: 2
0000 0073 0000 000B 0020 0020 0040 0020 0020 0040 0020 0020 0040 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0040 0040 0CC4


Change the suffix from pcf to zip and open with one of the unzip programs. Then open ConfigEdit.xml. I assume you can just copy and paste the "correct" sring, but I have nerver tried it since I don't have the hardware.