Hi

Does anybody have these codes?

I have spent 2 frustrating days trying to find a way of gemerating a full set of discrete codes for my Samsung AV receiver (AV-R710). I really need the codes for ON and OFF for my Harmony One!

I have located and used Makehex and IrPanels. I have read that the Samsung20 protocol is not used now by Samsung and they use NECx2. I can generate a CCF and load onto a Pocket PC to test the codes.

What I need to know is
- what protocol should I use? is it Samsung 20, NECx2 etc (or which irp file in makehex?)
- What device number should I use?

If nobody knows - how can I find out? Or is there a much simpler way of generating and testing the codes??

thanks
Bill

Knowing the protocol wouldn't help much if you don't also know the device number(s).

Normally one looks for "discrete" codes when one already has some ordinary codes for the same device.

If you can get Pronto Hex for any ordinary code for that device, you can use IrTool to decode it. Then you have the protocol, device and if needed subdevice for use with MakeHex.

If you find the IR signals of a related model online in a pcf file or ccf file or jp1 or lirc or (more difficult) other formats, we can figure out the protocol, device, etc. and likely your model uses the same signals.

But I didn't see any Samsung AV-anything in any of the usual places I look for online data on devices.

Can your pocket PC learn IR signals? Or is it output only?

Hi

thanks for the reply.Yes the pocket PC can learn signals.

I installed the pronto edit software to get a hex code as you suggest but cant find the name listed for my samsung receiver, I may download all the ones that look possible onto my pocket pc and see if i can find one that works

Maybe then I will get there?

Bill

bill, you need to learn a code from the original samsung remote so that we can 'see' it and possibly move forward with this for you.

I need these as well for an AVR720.
I decoded a handful of codes and got Teac-K for the protocol device 0 subdevice 4
I need the Teac-K.irp to generate codes

John do you have the Teac-K.irp?

is it not listed here?
can this not be transferred into your makehex program??
[Link: hifi-remote.com]

if you compare the fujitsu irp in makehex to the info under 'fujitsu' in the above document you can see how they compare, however the Teac-K seems to have two parts so making up an irp file isn't that straightforward.

Post a few of those learned signals.

I don't recall where I've even seen samples of Teac-K and I'm sure I haven't seen many samples. I just checked my main library of IR signals in CCF files and there are no examples of Teac-K.

I found my IRP summary of the protocol inside the source code of DecodeIr.dll, which represents everything I deduced about Teac-K from whatever few samples I've seen. I just now translated that to the .irp file below and tested with MakeHex and pasted the results back into IrTool.exe and that works. But that only proves the C++ code in DecodeIr.dll matches the comments in the source code. It doesn't really prove I understood Teac-K from the samples I've seen.

If I missed by a lot, the signals from this .irp would decode the same as your signals but not work. If I missed by a little, they might decode the same and work, but not work as well (not extend correctly when you hold a button down, or not work as well as perfect signals when used from a bad angle or distance).

define M=67
define N=83
Device=0.4
Function=0..255
Frequency=37900
Time Base=432
Zero=1,-1
One=1,-3
Default S=0
Define X=M^N^(M:4:4)^(N:4:4)
Define T=D+(S:4)+(S:4:4)+(F:4)+(F:4:4)
Form=8,-4,M:8,N:8,X:4,D:4,S:8,F:8,T:8,1,-100;8,-8,1,-100


Yes it could and it would be just like what I posted above, except for the small difference in frequency. I don't think the difference in frequency would have a detectable effect on behavior in ordinary use. I'm not sure why I thought the frequency was 37000 when I wrote the documentation you quoted, but I thought it was 37900 when I wrote the decoder. Various original remotes sending various kinds of Kaseikyo protocol have frequencies all over the 37K to 38K range.


That got a bit ugly using the .irp file syntax supported by older versions of MakeHex (see aiwa.irp). But years ago I modified MakeHex.exe to support the more flexible syntax I used in the .irp file quoted above. (The newer MakeHex.exe still supports the older ugly syntax as well).


Is there a way to look at those learned signals in hex.


I don't understand enough of the interaction between the pocket PC and Pronto Edit to understand what you're saying.

For a real Pronto, you can transfer the configuration from the Pronto back to the PC after learning signals on the Pronto. Then you can use ProntoEdit to look at those learned signals in Hex.

If the device you're trying to control uses the same signals as the device Scott is trying to control, he's way ahead of you on learned signals, so you can just use his results.

Here are some codes. I have a few more if you need them.

Vol-
0000 006B 0032 0002 0060 0049 0010 002D 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 002D 0010 0010 0010 002D 0010 002D 0010 0010 0010 0010 0010 002D 0010 0010 0010 002D 0010 0010 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 002D 0010 002D 0010 0010 0010 0010 0010 002D 0010 002D 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0699 0060 0081 0010 0699

Vol+
0000 006B 0032 0002 0060 0049 0010 002D 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 002D 0010 0010 0010 002D 0010 002D 0010 0010 0010 0010 0010 002D 0010 0010 0010 002D 0010 0010 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 002D 0010 0010 0010 0010 0010 0010 0010 002D 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 069A 0060 0081 0010 069A

Mute
0000 006B 0032 0002 0060 0049 0010 002D 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 002D 0010 0010 0010 002D 0010 002D 0010 0010 0010 0010 0010 002D 0010 0010 0010 002D 0010 0010 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 002D 0010 0010 0010 0010 0010 0010 0010 002D 0010 0010 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 069B 0060 0081 0010 069B

Power (toggle)
0000 006B 0032 0002 0060 0049 0010 002D 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 002D 0010 0010 0010 002D 0010 002D 0010 0010 0010 0010 0010 002D 0010 0010 0010 002D 0010 0010 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 069C 0060 0081 0010 069C

Input DVD
0000 006B 0032 0002 0060 0049 0010 002D 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 002D 0010 0010 0010 002D 0010 002D 0010 0010 0010 0010 0010 002D 0010 0010 0010 002D 0010 0010 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 002D 0010 002D 0010 0010 0010 0010 0010 002D 0010 002D 0010 002D 0010 0010 0010 0010 0010 002D 0010 002D 0010 002D 0010 0010 0010 0010 0010 0010 0010 0010 0010 0698 0060 0081 0010 0698

galileo01, have you tried the new irp and tested the makehex version of say function 115 (DVD)?

Those learned signals look like what I would expect from my previous reverse engineering commented inside DecodeIr.dll source code, and they look close enough to what makehex generates from the .irp file above that the device shouldn't be able to detect any difference.

Bill, do those same signals work on the AV-R710?

this thread!!
ok i am confused, i posted the whole makehex output for you over at the UK AV Forums site, you didn't have the IRP for Makehex so you couldn't have generated the same codeset i did. have you tested any of the hex i posted for you?
[Link: avforums.com]

Since I haven't ever signed up there, I'll comment here on the question there

[Link: avforums.com]

They are in Pronto Hex. Are you sure you understand how to use IRpanels?

The created ccf file is called IRCodesCreate.CCF, for these codes that is a 74KB file.

Your symptoms sound like you used IRCodesMaster.ccf, which contains only the graphics and not the IR signals. Maybe you didn't notice IRCodesCreate.CCF or maybe you used IRpanels incorrectly and didn't create it.

If you used a correct IRCodesCreate.CCF then maybe your Pocket PC has some capacity limit for IR signals. You could try pasting just a fraction of the IR signals (you must start at the beginning) from the .hex file into IRpanels. That would create a smaller CCF file and you can test whether that avoids some capacity proble in the Pocket PC.

Hi

Good news! I tested all 5 codes posted by galileo01 and all of them work perfectly!
All I need now is the .irp file that generated those codes and I can generate and test the whole set.

I will make an irp out of the lines posted by John and run it through makehex to try that this evening.

For background info, I used IRTool with DecodeIR.DLL to decode signals from my remote and it returns...
Protocol : Teac-K
Device : 0.4
OBC: 0
EFC: 181

To test the signals I have given up on the old pocket pc. I am using IR receiver and blaster thats comes with the Windows Media Centre remote plus the freeware 'IR Server Suite' software.

Thank you all for your help so far
Bill

those five codes were learnt codes not generated codes, try this generated code for power using John's new IRP file with makehex.
0000 006D 0032 0002 0083 0042 0010 0032 0010 0032 0010 0011 0010 0011 0010 0011 0010 0011 0010 0032 0010 0011 0010 0032 0010 0032 0010 0011 0010 0011 0010 0032 0010 0011 0010 0032 0010 0011 0010 0032 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0032 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 0032 0010 0011 0010 0011 0010 0011 0010 0011 0010 0011 0010 066B 0083 0084 0010 066B
if this works then generate them all and test....
bear in mind though this is Samsung and there probably won't be any new codes to be found.