I have been trying to generate discreet codes for my Yamaha RX-V1200 receiver but have been having problems. I first use Charles Parks excellent spreadsheet to convert the Yamaha Extended Codes for my 1200 to device and command codes for use with the IRTool. I'm then using a known good hex code to decode and get the IRTool set up. Then I input the the device and command code and encode to get the hex and paste it into a command in ProntoEdit. None of the codes will work.

I finally found out what is happening but can't figure out why or how to correct the problem. I can take a working hex code either directly from the Pronto such as surround mode Rock Concert and decode it as follows to Device 126, Command 237.

The working hex I paste into IRTool is as follows:
0000 006d 0022 0002 0155 00aa 0016 0016 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 0016 0016 003f 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 003f 0016 003f 0016 0016 0016 003f 0016 003f 0016 0016 0016 003f 0016 003f 0016 003f 0016 0016 0016 003f 0016 0016 0016 0016 0016 003f 0016 0016 0016 0016 0016 0016 0016 05e6 0155 0055 0016 0e3d

If I were to then take the same device and command codes 126, 237 and encode those with the tool, the hex is changed to:
0000 006d 0022 0002 0155 00aa 0016 0016 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 003f 0016 0016 0016 003f 0016 003f 0016 0016 0016 003f 0016 003f 0016 003f 0016 0016 0016 003f 0016 0016 0016 0016 0016 003f 0016 0016 0016 0016 0016 0016 0016 05e6 0155 0055 0016 0e3d

The first sequence which gets incorrectly modified is 24 which gets changed from 003f to 0016. I first thought it was because I was using a dirty code to set up IRTool but after trying many codes I know this isn't the problem. I've searched the boards for more in-depth info on the tool to try and solve this on my own, but couldn't find anything. Not a single extended code I've encoded with the tool will work. I've even tried the tool on another PC.

I'm stuck. Any ideas?

The spreadsheet has already been converted to Pronto hex codes. I'm not sure where to find it, but you could searching on "Yamaha".

Found it in one go at

[Link: remotecentral.com]

Thanks for the info but unfortunately many of the codes for my RX-V1200 are different from the RX-V1. Mine is a newer model and has it's own code list, so I need to figure out how to make the tool work. I searched for files on the Rx-V1200 and 2200 but it seems that few own these units. I believe they were released in September

I sent you an RX-V1200 file.

@Barry Shaw: could you send me the file for the RX-V1200? Or anybody other? I search also a power toggle code. Thanks a lot.

Cimba-

What remote are you using?

A Philips Pronto (1MB)

Hey Barry, do you have the info so I can update the spreadsheet and add the 1200 and the other new receivers?

Cimba-

Sent you a file for v2.0 & 1.05... take your pick.


Andrea-

I've been busier/lazier than usual and don't have the Yamaha .pdf for the 1200 or 2200 from their website handy.

The file I've been sending out is fully tested except for Zone 2 stuff. I still haven't had time to do the 2200 yet.

As the 1st post above notes, I've had to manually "adjust" IR Tools's output to get them to work. This is part of the reason I've been slower this generation - I need the gear in front of me to confirm the codes work. The generated codes are so close that editing them isn't a big deal once you see the pattern, but I would like to understand what I'm missing. Here was my question for Glenn:


Glenn-
I obviously don't understand IR structure and can prove it with the examples below. I used your IR Tool last year (thanks!) to generate the Yamaha Extended Codes for the RX-V800/1000/3000 receivers. I don't remember doing anything "special" at the time. Life was good... they all worked.

Yamaha just brought out the new RX-V1200/2200 receivers and I needed to add some new commands. I used a known working code pasted & decoded to set up IR Tool, then generated/encoded the new ones. No luck! I see what's happening and "edited" the new 103 command to make it work, but I'm confused why it's happening.


Device 126, Command 253... as generated last year on IR Tool... It worked!
0000 006d 0022 0002 0155 00aa 0016 0016 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 0016 0016 003f 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 003f 0016 003f 0016 0016 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 0016 0016 003f 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 05e6 0155 0055 0016 0e3d

Device 126, Command 253... as "re-generated" today on IR Tool v1.2... No longer works... What did I do differently in setup?
0000 006d 0022 0002 0155 00aa 0016 0016 0016 003f 0016 0016 0016 003f 0016 003f 0016 003f 0016 003f 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 003f 0016 0016 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 0016 0016 003f 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 05e6 0155 0055 0016 0e3d



Device 126, Command 103... as generated last week on IR Tool v1.2... Will not work.
0000 006d 0022 0002 0155 00aa 0016 0016 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 003f 0016 003f 0016 003f 0016 0016 0016 0016 0016 003f 0016 003f 0016 0016 0016 0016 0016 0016 0016 0016 0016 003f 0016 003f 0016 0016 0016 0016 0016 003f 0016 05e6 0155 0055 0016 0e3d

Device 126, Command 103... after "editing", shown in bold, this works!
0000 006d 0022 0002 0155 00aa 0016 0016 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 0016 0016 003f 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 003f 0016 003f 0016 003f 0016 003f 0016 0016 0016 0016 0016 003f 0016 003f 0016 0016 0016 0016 0016 0016 0016 0016 0016 003f 0016 003f 0016 0016 0016 0016 0016 003f 0016 05e6 0155 0055 0016 0e3d

Can you (anybody!) tell me whats going on?

Barry, that's so strange. I get the following hex code generated by IR Tool for Device 126, Command 253:

0000 006d 0022 0002 0155 00aa 0016 0016 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 003f 0016 0016 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 003f 0016 0016 0016 003f 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 05e6 0155 0055 0016 0e3d

This is different the your working code from last year and slightly different than the code you generated now.

What's going on here? Weren't we using IRTool 1.2 last year when we did this?

Andrea-

I did the RX-V1200 late on a dark & stormy night at a friend's house with frosty beverages just to complicate things... It was faster that night to just manually fix the codes, & I haven't had time to take much of a second look at it since.

I thought I'd set it up the same way but obviously I'm missing something I did from the last time... Anybody?

Bump

I'm a newbie of a few weeks, so I didn't use IRTool last year, but I downloaded it today and the unzipped files are all dated '99 or '00.
I don't think it's setup...the tool definitely seems to be screwing up - it's not setting the bits which are the complement of the device code correctly, i.e. that portion of the code is stuck at all zeros (all 0016 0016), no matter what device code you plug in.

Strange, if it worked a year ago....maybe the tool isn't Y2k2 compliant.

-Paul

At least I now know I am not going completely mad. I have been trying to take advantage of the great work by Andrea, Barry & others on the RX-V extended codes to add in the changes for the RX-V2200. I have been spectacularly unsuccessful. This thread tells me why. IR Tools seems to consistently change the encoded hex of the 24th word and the 38th word from "003f" to "0016". I will do some work over the next few days to get some of the codes working manually. If anyone else is working along these lines I would like to pool efforts.

Thanks

Peter