help request - translating yahama codes

friendlyfire · Post by **friendlyfire** » Sun Dec 04, 2005 4:02 pm

Hi, I'm having some trouble applying some codes I downloaded from yahaha's web site into IR. Here is what I know

the info from yamaha lists a "custom code" along with a "data code" in that order.

the protocol is NEC1

DVD input: yamha code is 7A C1 and I know this if OBC 193, EFC 177
CBL input: yamaha code is 7A 54 and I already know this is OBC 84, EFC 100
POWER OFF is 7E 7E and I know this is OBC 29, EFC 248

I have not found a reliable method to calculate the proper EFC for this yamaha code (night on): 7E 9B. I'd like to know the method so I can make a number of these conversions and build a device file for my RX550 (I will post it when done)

I checked the protocol help of IR but I didn't find it too informative.

thanks
Brian

Post by **The Robman** » Sun Dec 04, 2005 5:12 pm

You can use the Windows calculator to convert those codes to device codes and OBCs. The 7A is device code 122 and 7E is device code 126.

Forget about EFCs, just concentrate on the OBCs. C1, 54 and 7E and 9B translate to 193, 84, 29 and 155.

There isn't a protocol help screen in IR, there's just one in KM, and I would describe is as very helpful, but it wouldn't describe what you need to do with those codes that you downloaded because it's not meant to.

Mark Pierson · Post by **Mark Pierson** » Sun Dec 04, 2005 5:22 pm

The Robman wrote:C1, 54 and 7E and 9B translate to 193, 84, 29 and 155.

err.... Rob... maybe you're using a different Windows Calculator than me, but doesn't 7E = 126, not 29?

Post by **The Robman** » Sun Dec 04, 2005 6:03 pm

My bad, I actually copied that one from Brian's post.

friendlyfire · Post by **friendlyfire** » Sun Dec 04, 2005 10:23 pm

well this is the problem. The Yamaha discrete code page says power on is 7E 7E yet I know the code that works is OBC 29. This is what confused me! I worked out from the first two codes just to do a simple hex to decimal conversion and then the method failed on the third code! Since this code has a different prefix I fugred I need to include that in the calculation...

I guess I should try code 126 and see what it does...

thanks
Brian

Post by **The Robman** » Sun Dec 04, 2005 10:36 pm

Some other explanations...

1) It could be a typo.
2) It could be a code for a different mode.

friendlyfire · Post by **friendlyfire** » Sun Dec 04, 2005 10:50 pm

I tried hex command 7E but the device doesn't turn on, so I believe the prefix is important... Not sure what other mode it coud be...

this is the link to the PDF file containing these codes
http://www.yamaha.com/yec/customer/code ... 50,750.pdf

Post by **The Robman** » Mon Dec 05, 2005 7:27 am

friendlyfire wrote:I tried hex command 7E but the device doesn't turn on, so I believe the prefix is important... Not sure what other mode it coud be...

What you're calling the "prefix" is the device code, so abslutely it's important. If you tried this code with device code 122, rather than 126, I could have told you it wasn't going to work.

friendlyfire · Post by **friendlyfire** » Thu Dec 22, 2005 6:07 pm

aha, thanks, I understand now.
with the NEC1 protocol there is a way to enter a sub device but I don't understand how to enter functions directed to this device. The byte2 column is grayed out. (using KM). What's the secret?

Brian

Post by **The Robman** » Thu Dec 22, 2005 7:15 pm

You don't want to use a sub-device with these upgrades, that's not the same concept as using multiple device codes. If you just want to combine 2 device codes, you can use the NEC 2dev Combo protocol (leave the sub-devices blank), if you want to combine more than that, you'll need to use the device combiner as our tools (ie, KM and RM) don't support the 4dev version yet.

friendlyfire · Post by **friendlyfire** » Thu Dec 22, 2005 8:42 pm

ok, I think I am getting close but I still need a bit of help.
I switched to the NEC2Dev protocol and read the protocol help. I enter device 122 in device 1 and 126 as device 2. In byte2 I put "1 x1" ifor all the codes (because I am extending a device file build with NEC1 using only prefix 122). It doesn't work when I load it, what did I do wrong?

Thanks for your patience while I get there.

Brian