Hi, my preamp (Thule PR350B) uses RC5 coded signals (38,5Khz) same as the
corresponding Tuner and CD-Player (Thule TU100 and CD150). When entering the
codes in PPENG and downloading to the device only those for the tuner and CD
work, but not those for the preamp. Why is that?
I verified by learning from the orig. remote, that the sent signal is indeed
RC5 and that the systemaddr. and the commandcode transmitted by the original
remote match the numbers I entered for RC5. PPENG When learning the code
does not itself recognise it as rc5 and therefore learns it as 0000 code
(even for the orig. remote of the Tuner/CD-Player). Also I found no way to
set the freq. for the rc5 signal. When I try to change the second word (the
one after the 5000) it will not be stored and is changed back to 0000 when I
reopen it.
Using learned codes is no real solution, as commands get only accepted once
(because of the toggle bit in the rc5 format). Can you tell me why it is not
working for the preamp as it does for the Tuner/CD-Player?

Thanks

P.S: I also tried contacting Philips Support, but the number herer in Germany only has a tape on that tells me I'm calling outside of their business hours even though I called at times that were definetely within those! My e-mail support requests did not garner a reply either. Is there any other way to get in contact?

You apparently understand that is higher than the frequency RC5 normally uses.

That leads one to wonder whether your device really uses RC5 at a higher frequency or whether the learning firmware got the frequency wrong.


How did you verify that? You took the 0000 code and decoded it with some program to get the systemaddr and commandcode? Which program? Maybe you should post one of those 0000 codes into this thread so we can see for ourselves whether that decode is accurate.


I'm pretty sure you are correct. If you really need RC5 with a higher frequency and with a correct toggle bit, I don't think there is any good solution.

I decoded the learned code manually. I know they are RC5 since i contacted the manufacturer (acually Mr.Thule himself). I have the RC5 codelist from them too, which work for the tuner and CD-player.

I can post the learned code when I get home.

I strongly suggest getting the JP1 version of IrTool.exe plus DecodeIr.dll. Together those decode most Pronto Hex more accurately and with much less work than doing it manually.

[Link: remotecentral.com]
[Link: john.fine.home.comcast.net]

true, but I did the same with the learned codes for the CD / Tuner and came up with exactly the adress/command code that was listed in the RC5 list from Thule. Entering those as RC5 works. Even though those devices expect the same freq. as the Preamp. What I don't understand is, why doing the same for the preamp will not work and also why PPENG will not keep my manual changes to the freq. field in RC5 code format.

No according to the info from Thule they use 38,5 and therefore higher than the 36 which I think is normal, but within 10% of the standard freq.


Here are some of the learned codes, which contain some with two versions for 1st and 2nd press on orig. remote:

STBY:
0000 006C 0000 000C 0020 0020 0020 0020 0020 0020 0040 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0040 0020 0020 0040 0020 0020 0CCD


Vol+
0000 006C 0000 000C 0020 0020 0020 0020 0020 0020 0040 0020 0020 0020 0020 0020 0020 0020 0020 0040 0040 0020 0020 0020 0020 0020 0020 0CCD

Vol-
0000 006C 0000 000C 0020 0020 0020 0020 0020 0020 0040 0020 0020 0020 0020 0020 0020 0020 0020 0040 0040 0020 0020 0020 0020 0040 0020 0CCD

up (1st press)
0000 006C 0000 000C 0020 0020 0020 0020 0020 0020 0040 0020 0020 0020 0020 0020 0020 0020 0020 0040 0020 0020 0020 0020 0020 0020 0040 0CCD

up (2nd press)
0000 006C 0000 000B 0021 0021 0040 0040 0040 0021 0021 0021 0021 0021 0021 0021 0021 0040 0021 0021 0021 0021 0021 0021 0040 0CCD

down (first press)
0000 006C 0000 000C 0020 0020 0040 0040 0040 0020 0020 0020 0020 0020 0020 0020 0020 0040 0020 0020 0020 0020 0020 0020 0020 0020 0020 0CCD

down (2nd press)
0000 006C 0000 000D 0020 0020 0020 0020 0020 0020 0041 0020 0020 0020 0020 0020 0020 0020 0020 0041 0020 0020 0020 0020 0020 0020 0020 0020 0020 0CCD

right (1st press)
0000 006C 0000 000B 0020 0020 0040 0040 0040 0020 0020 0020 0020 0020 0020 0040 0040 0020 0020 0020 0020 0020 0020 0020 0020 0CCD

right (2nd press)
0000 006C 0000 000C 0020 0020 0020 0020 0020 0020 0040 0020 0020 0020 0020 0020 0020 0040 0040 0020 0020 0020 0020 0020 0020 0020 0020 0CCD


left (1st press)
0000 006C 0000 000C 0020 0020 0020 0020 0020 0020 0040 0020 0020 0020 0020 0020 0020 0040 0040 0020 0020 0020 0020 0020 0020 0040 0020 0CCD

left (2nd press)
0000 006C 0000 000B 0020 0020 0041 0041 0041 0020 0020 0020 0020 0020 0020 0041 0041 0020 0020 0020 0020 0020 0020 0041 0020 0CCD

With the latest software and firmware, have you tried adjusting the IR Duration setting? Also, as you suspected, the learned codes (0000) will have problems because of toggle bits. However, I couldn't ascertain from the above discussion whether you've used the RC5 dialog from PPENG to enter the codes where you would then see a '5000' versus '0000' format.

You didn't mention what you got by hand decoding. Probably you got the correct systemaddr, which is 16 decimal (10 hex).

So the STBY signal would be
5000 0000 0000 0001 0010 000C

Do I understand you correctly, that the 0000 form works (except for toggle issues) but this 5000 form doesn't?

exactly. When I enter the decoded values (system/command) via the RC5 dialog it does not work (the shown code then starts with 5000). The learned code works (except for toggle problems). To get around this I made up a "dummy" command with the opposite toggle, which was easy since I knew all command codes that existed from the Thule info sheet and I simply chose a command number that was not assigned. But this is not the way it should be and I would like to find out what the reason is, and why I can't adjust the freq. field in the 5000 version of the code.

With the latest software and firmware, please try the IR Duration Feature. Change it from Default to something like 0.2s.