Hi All,

With reference to my dispair at not being able to import codes from a ccf, does anyone have an rcc with the discrete on and off codes for a TAG McLaren AV32R? Remote pretty useless without the codes.

Thanks

Saw your other post. What form hex do you have? It has to start with "0" to show up as a "learned" command in the UB. RC5 codes cannot be dragged over. That being said, other forms of hex can be converted. Take a look at this thread.

Also, have you checked any of the CCFs in the "Files" section here. There are quite a few AV32R files.

Mike
www.SurfRemoteControl.com

Hi Mike,

Yes I have, and in fact still have my old ccf from the RC5000 days for my AV32R. The codes are of course not learned they were simply "entered" from the RC5 list TMA published. I am looking into the link you pointed to and hopefully something good will come of it.

Many Thanks

I will naturally post back with my findings here.

You can use MakeHex to generate the RC5 signals in the form of Pronto Hex that begins 0000 (the form the Universal Browser understands). You can use IrPanels or hex2ccf to convert the result to a ccf file.

I assume you still have the list TMA published to tell you the device number you need before running MakeHex and the function numbers you need for selecting which buttons to drag in Universal Browser.

Ok Success. I tried using programs like MakeHex, Hex2ccf and Makelearnedb2. All these failed for me. Most likely finger trouble as others seem to be doing fine with it. Anyways, I downloaded all of the Av32 files from here and found this one....

([Link: remotecentral.com])

to have the discretes as learned code, instead of the usual entered RC5. I tried making clean hex using RC5 19 120 (on for the TAG but it doesn't work) The generated hex from makelearnedb2 looked nothing like that of Henrick's.

Anyway his codes labelled as learned data work beautifully so I am happy again!!

Intersted parties may like to know

On is (0000 006b 0014 0000 0020 0021 0040 0042 0040 0021 0020 0042 0020 0021 0040 0021 0020 0042 0020 0021 0040 0021 0020 0ce5 0020 0021 0040 0042 0040 0021 0020 0042 0020 0021 0040 0021 0020 0042 0020 0021 0040 0021 0020 0021)

Off is (0000 006b 0016 0000 0020 0021 0020 0021 0020 0021 0040 0021 0020 0042 0020 0021 0040 0021 0020 0042 0020 0021 0040 0021 0020 0ce5 0020 0021 0020 0021 0020 0021 0040 0021 0020 0042 0020 0021 0040 0021 0020 0042 0020 0021 0040 0021 0020 0021)

Thanks Mike for answering before.

You better test a bit more carefully. Both of the signals you just posted are the power toggle signal. They are NOT discrete power signals.

RC5 has a feature that can make a power toggle signal seem to be a power discrete signal when you try a simple test. But if you test more carefully you will discover it is not.

Here are commands 120 and 121 generated by MakeHex:

Device Code: 19 Function: 120

0000 0073 0000 000B 0040 0020 0020 0040 0040 0020 0020 0040 0020 0020 0020 0020 0020 0020 0020 0020 0040 0020 0020 0020 0020 0CC5

Device Code: 19 Function: 121

0000 0073 0000 000B 0040 0020 0020 0040 0040 0020 0020 0040 0020 0020 0020 0020 0020 0020 0020 0020 0040 0020 0020 0040 0020 0CA4

Hi John,

Interesting. I have just checked to see if the code I posted was the same as those in the ccf, and they are. Both the codes listed are working perfectly, without hesitation. I have repeated pressed the buttons for on and off and nothing goes wrong.

I will out of interest try replacing the codes I listed with those you listed and report back.

Thanks for your help.

Matt

Using just the supposed discrete On and Off you might get results that make them seem correct. To really test them you need to use other functions as well (as you would in real use).

I don't know enough firmware details of the device to be sure which sequence will prove the supported discrete codes wrong, but I have a good guess:

1) Turn it on with the "discrete On" signal.
2) Use some other function.
3) Try the "discrete On" again. I think it will toggle the device off, because it isn't really a discrete On.

I bow to your experience my good man. That is exactly what happened. I pressed On then menu, plus a load of other buttons then on again and it went off. Thank you for this insight.

I'm off to try MakeHex again.

Many Thanks

Matt

Why is it that when I use MakeHex I get

Device Code: 19 Function: 120
0000 0073 0000 000B 0040 0020 0020 0040 0040 0020 0020 0040 0020 0020 0020 0020 0020 0020 0020 0020 0040 0020 0020 0020 0020 0CC4

Note then last four digits are different to your output.

Have I done something wrong?

This question has I'm sure been asked before. How do I know what to change this text to.

Device=19
Function=0..127
Define T=0

Protocol=RC5
Frequency=36000
Time Base=889 '888.89 = 32 cycles at 36Khz
Message Time=128 '128 times TimeBase
Zero=1,-1
One=-1,1
Prefix=1 'Officially -1,1 but starting with off is silly
First Bit=MSB
Form=;*,~F:1:6,T:1,D:5,F:6

Thanks Matt

I have just now tried the new discrete codesthey MakeHex has just output and all is well. How did you know from looking at the code that I posted that it was not right??

Learning all the time....thanks

Matt

Most of the values in Pronto Hex are approximate durations, so slight changes in the numbers don't change the meaning at all. That is especially true of the last number. Even a much bigger change in the last number wouldn't change the meaning.

I guess we're using different versions of MakeHex. Occasionally I change the rounding rules or similar details in MakeHex because I find some obscure protocol where it matters. That tends to cause lots of tiny changes to the numbers in all the common protocols where such changes don't matter. Sorry for the confusion.


It is rarely correct to change anything other than the device number.

There might be a need to change T to be 1 instead of 0. RC5 has two versions of each signal. Changing T gets you the other version. The device won't accept the same version of the same signal twice in a row. If you need to use the same signal twice in a row in a macro, you may need to construct the two different versions of the signal to make that work. Of course you don't need that for discrete codes because you wouldn't want to use one twice in a row.

Other than Device and T, it is really rare to have reason to change something else in an IRP file.


I decode Pronto Hex with the JP1 version of IrTool.exe plus DecodeIr.dll
[Link: remotecentral.com]
[Link: john.fine.home.comcast.net]

With those I could see your two discretes were the same device and function but different values of T. So I knew they weren't really discretes, just sometimes acted like discretes (because sometimes the device will accept only the value of T that it didn't see last).

With those tools I also saw that the function number was 12. Almost all devices that use RC5 protocol use function 12 as their power toggle command.

Hi John,

Superb, thanks for the links too. Very grateful for your aid here in increasing the usefullness of my 3000

Seasons greetings to all.