Hi, I have a SONY DAV-S550 (DVD + Surround Sound AMP). I can learn control but would like to search for hidden codes.

Following is the HEX recorded for the PLAY button...
0000 0066 0000 003F 0061 0018 0018 0018 0030 0018 0018 0018 0018 0018 0030 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 0018 0030 0018 0030 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 020B 0061 0018 0018 0018 0030 0018 0018 0018 0018 0018 0030 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 0018 0030 0018 0030 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 020B 0061 0018 0018 0018 0030 0018 0018 0018 0018 0018 0030 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 0018 0030 0018 0030 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 0266

Now from this, is it possible to generate other OBC's?

I have tried MakeHex but i'm not entirely sure how to go on with that, I have though had success with ProntoUtil in generating RCA5 HEX codes or XBOX.

Would someone be able to provide me (and anyone else struggling with this) a step by step set of instructions on how to figure this out ~ cos once I understand, i'll stop asking & start helping :).

Any help will be most appreciated. Thanks - Steve.

Bump!

Perhaps my question was too much?

Can anyone tell me is it possible to generate other codes from a learned one using 'a utility'?

Not having tried Make Hex myself, I don't know if it'll help, but have you looked at it?

Here is a web site of commands for the Sony DVD.
[Link: hifi-remote.com]

The command you posted decodes as expected to Sony20 protocol, device 26.73, command 50. Which is what that site says Play should be.

MakeHex can be used to translate the commands from the format listed there into Pronto Hex.

On general principles, I'd expect a "Surround Sound AMP" to be operated by Sony's "Control-A1" protocol, which is documented here:
[Link: hifi-remote.com]
but I don't have any specific knowledge of whether your device actually understands Control-A1 IR protocol.

I don't think anyone has tried writing a .irp file to generate Sony Control-A1 IR signals with MakeHex. I think it could be done, but it would take a fair amount of MakeHex knowledge and ought to be done with an appropriate Sony device and Pronto available for testing. I have neither the Sony nor Pronto. I don't know who else other than jarmstrong has that level of MakeHex expertise and he doesn't have a Pronto either.

After you look at those two web pages, you should be able to form a better plan about which commands you's like to test. At that point, if you still need MakeHex help, ask again.

You can go the way John suggested OR... you can download my Sony DVD CCF from the Files Section (I believe it's in the Pronto Section). It has ALL codes for Sony DVD players with common functions labeled for Command Mode 1 to Command Mode 3.

If you don't have a command mode switch or setting on your player, use Command Mode 1.

BTW. The code posted above is very dirty. My CCF includes ultra-clean codes.

Thanks for everyting so far, but as always, theres more!.

Using various snippets of information & several tools, I've managed to get somewhere.

What I've learned...
Sony12=Sony 5bit Device Code
Sony15=Sony 8bit Device Code
Sony20=Sony 13bit Device Code

And to generate HEX file from IRTOOL...
Paste Learned Pronto HEX into IRTOOL.EXE
DecodeIR.DLL reports some items (Protocol, Device etc), & then IRTOOL returns other items (Frequency)
Use this info from these 2 results & create a .irp file for MakeHex

Then from the tables at [Link: hifi-remote.com] see what commands are availible.

Hows that so far???

1st a Statement, then questions...
Statments...

• The original remote does not have discrete cmds for speakers volume + & -, Test Tone, etc
  
• I want individual codes for individual speakers volume + & -, Test Tone, etc


• I've been thru the learned commands & i've found the following device protocols/codes are in use...
  Sony15 Device208
  Sony15 Device80
  Sony20 Device16.16
  Sony20 Device26.73
  (Also seen this one Protocol Async5:444-449:10.11..15.11 Device 17.81 [followed a Sony15 Device208 code])

Questions...

• Now none of the pages on hifi-remote list these codes under the devices mensioned above. Does that mean I cant get the codes I want ?


• The codes i want ARE listed in Devices 26.233, Control-A1 (and some others). What would I do to generate these in MakeHex? Which proocol? Which Frequencey, Which format etc?

The code posted above is very dirty. My CCF includes ultra-clean codes
How do you know this? How do i clean these?
You can go the way John suggested OR... you can download my Sony DVD CCF from the Files Section (I believe it's in the Pronto Section). It has ALL codes for Sony DVD players with common functions labeled for Command Mode 1 to Command Mode 3
Is that the SonyDVDAll.ccf CCF? I've tried several screen but can't find what i need (i'm not too patient & theres lots of buttons!) If these are Control-A1 codes I will try them all.

Again, thanks everyone for your help & patience.

PS, The programs i am using are disconnected & basic (don't confuse basic with being simple, this is proper hackers land!), what i'm trying to say without offending anyone is I'd like to get hold of the source code for these apps & create a GUI with all the Copy & Paste / Drag and drop frills posible ~ Currently, its very labourious with several text files floating about, 3 or so apps running.....

This message was edited by sd00 on 09/24/04 22:32 ET.

There isn't a lot missing from that collection of Sony codes I mentioned earlier. If you're seeing so much that isn't there, something is wrong with your signals. I'd need to see several samples (Pronto Hex) of the unexpected signals to form an opinion about what is wrong.


But that one is my fault. DecodeIr has a bunch of seperate routines for recognizing different protocols. Some of the protocols are hard to validate and some of the routines are not very good and the coordination between those routines is pretty bad. The end result of all that is occasional total garbage decodes showing up that do not mean any such signal is present. That Async5 decode is that sort of garbage and should be ignored.


The frequency is the same as the other Sony protocols. The structure (which is the form part of an .irp file) is a combination of structures from other Sony .irp files with minor tweaks.

One detail not obvious to me is how to make a useful series of commands. Typical IR protocols include a single command byte, that varies while other parts are mostly constant. These Control-A1 signals have more variation. MakeHex allows many more variable within an IRP than the typical device, subdevice and command. But it doesn't give a clean way to organise a set of generated signals across multiple variables.

The checksum in Control-A1 would also require some effort when constructing a .irp file, but I think MakeHex supports all the required operations.


I don't keep the posted source code up to date because few people have expressed interest, but I have posted source code for MakeHex and DecodeIR and many other related utilities. I'll provide current source code to anyone who want to move any of these tools forward.

I have IrTool source code as well, but not direct from the author and I'm not sure his permission was provided for others to take it over, so I'm part way through writing a new one from scratch (there isn't much too it, I just haven't had much time for it) so I could give you some of that as well.

My source code is all C++ with some dependancies on Visual Studio (so a little extra effort required to port to a different build environment).

I know MakeHex should have a GUI rather than editing the input file and the option to produce IrPanels type output directly rather than the present way. But I don't like writing GUI so I haven't taken the time.

DecodeIR is a much bigger project that has grown along with my evolving understanding of both IR protocols and typical IR learning distortion. It has some of the flaws typical of programs that were "grown" rather than designed. But it does its job far better than any of the other decoders I've seen. I have posted DecodeIR source code, but I doubt anyone but me could successfully make any major changes to it. Instead of making the source code friendly, I focused on making a simple DLL interface so many different programs can use DecodeIR for their decoding without caring what goes on inside it.

I'm not qualified to even guess whether the 26.233 command are valid for your device. But they're easy to generate and test.

Edit sony20.irp to change the device number to 26.233
Drag/drop it onto MakeHex.exe
Open the resulting sony20.hex file and either copy/paste individual commands to ProntoEdit or copy/paste the whole thing to IrPanels.
Load the resulting CCF to your Pronto and test it.

|

John,

Check out my SonyCDSuperCharger program in the Pronto Files Section. There's a description of the Control A1 format in a readme.txt file that discusses the Control A1 bytestream format. I used Control A1 to generate a namelist CCF for downloading the names and artists of discs to my CD Jukeboxes (when they were in use).

sd00,

Your code is unclean because it it doubled up. Here's what it should look like to be considered clean.

0000 0066 0000 0015 0061 0018 0018 0018 0030 0018 0018 0018 0018 0018 0030 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 0018 0030 0018 0030 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 020B remaining section deleted

For more information, download a document describing Pronto IR Formats from the User Documentation section of the Pronto Files forum.

You can either go through this effort to change codes yourself or simply download my CCF, import it, merge it with your PCF, and then Shift-Drag to copy actions from my buttons to yours.

Lyndel