| Post 1 made on Thursday December 25, 2008 at 18:33 | ...it's new! |
davelasker Junior Member |
| |
I am an experienced programmer who understands hex notation, but I have little knowledge of IR or signal processing. I am trying to use irtool and makehex for the 1st time ever.
This is in reference to my post: http://www.remotecentral.com/cgi-bi...screte/thread.cgi?5227 I am looking for a missing discrete code for my Panasonic TV. I expect from makitamark's reply, my chances are slim to none, but I thought this would be a good excuse to figure out how to learn to use makehex to try all the codes for my TV.
I am referring to the Panasonic codes documented here: ftp://ftp.panasonic.com/pub/Panason...desProntoCCFformat.pdf
As an example, I tried the discrete code for Component 1 (3rd code in the above pdf):
0000 006D 0000 0032 0083 0042 0010 0010 0010 0031 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010
0010 0010 0010 0010 0010 0010 0010 0010 0010 0031 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010
0010 0010 0010 0010 0010 0031 0010 0010 0010 0010 0010 0031 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010
0010 0010 0010 0031 0010 0031 0010 0031 0010 0031 0010 0031 0010 0010 0010 0010 0010 0010 0010 0010 0010 0031 0010 0031
0010 0031 0010 0031 0010 0031 0010 0AED
I enter this code into IRTool, and it says:
Protocol: Panasonic
Device: 128.4
OBC: 124
So I modified panasonic.irp changing the Device from 128.0 to 128.4, and run makehex.
However, the code for function 124 generated with makehex starts with "0000 0070", so it is different from the original input which started with "0000 006D".
Is there something else in the .irp file that I need to change to generate the correct codes?
Thanks for the help! |
| [ Reply | Quote & Reply |
| Post 2 made on Thursday December 25, 2008 at 19:11 | ...it's new! |
Jasonvp Regular Member |
| |
The codes for irp file should work because they are clean codes.The way you changed the irp file is correct.
Did you try the makehex hex code to see if it works?
Device Code: 128.4 Function: 124
0000 0070 0000 0032 0080 0040 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0ACE
I don`t know why they are different in the way they look but I would say it`s the same code just decoded differently.
If Johnsfine (the person that wrote makehex) reads this thread he will tell you why they are different hex codes,he is the master of IR codes.
If you are going to try all 256 codes from makehex I would try both Device 128 and Device 128.4. |
| [ Reply | Quote & Reply |
| Post 3 made on Thursday December 25, 2008 at 23:37 | ...it's new! |
Kupakai Long Time Member |
| |
The second number in the Pronto hex code sequence is the carrier frequency. "0t070" equals about 37khz and "006D" is equal to 38khz. As you can see in the document you linked to, the signal will still work within some variation of the frequencies. The listed frequencies varies between "006C" to "0071", probably because they are learned codes and not "clean" generated codes.
In the makehex generated codes, the "0070" is derived from the parameter "Frequency=37000" in the irp file. If you really want to generate a set of codes with "006D" as the carrier frequency, you can change the value to "Frequency=38000", but I doubt it will make too much of a difference (it should work either way), and I wouldn't change it.
This message was edited by Kupakai on Friday December 26, 2008 at 10:25. |
| [ Reply | Quote & Reply |
| Post 4 made on Friday December 26, 2008 at 10:04 | ...it's new! |
johnsfine IR Expert |
| |
Most of the values in a Pronto Hex string are approximate, so two Pronto Hex strings might look entirely different but still encode the same signal.
As Kupakai explained, the second hex number encodes the carrier frequency. Many IR learning devices, including Prontos, are not very accurate about frequency. Fortunately most IR receivers in the devices to be controlled aren't very picky about frequency.
You might expect a manufacturer publishing discrete codes in Pronto Hex to use some tool like MakeHex to generate "perfect" signals. And you certainly should expect they know details, such as the exactly best frequency better than what is represented in the .irp files I wrote. But if you look at the Pronto Hex strings in that PDF file, you can easily see they are learned signals not generated signals. I expect they are all close enough to work, but I wouldn't guess they are closer to perfect signals than what you get from MakeHex. |
| [ Reply | Quote & Reply |
| Post 5 made on Monday December 29, 2008 at 08:24 | ...it's new! |
makitamark Long Time Member |
| |
hi dave, any luck with the code testing, you would be very popular if you managed to discover some hidden discretes.
regards mark. |
| [ Reply | Quote & Reply |
| Post 6 made on Monday December 29, 2008 at 21:01 | ...it's new! |
davelasker Junior Member |
| |
| I won't have access to the TV for 2 weeks. But some more googling found this post: http://www.appdigusers.com/forums/u...owthreaded/Number/4293 that says the discrete Panasonic TV Tuner Input I am looking for is Device 128 Command 0. I'll give all the codes a try and report back later. |
| [ Reply | Quote & Reply |
| Post 7 made on Tuesday December 30, 2008 at 08:45 | ...it's new! |
makitamark Long Time Member |
| |
checked out the link, pasted the codes, off to a customers now to test them.
see you later.
regards mark. |
| [ Reply | Quote & Reply |
| Post 8 made on Tuesday December 30, 2008 at 12:16 | ...it's new! |
makitamark Long Time Member |
| |
ok, tested on a two year old 42" UK spec pana plasma, the only codes that worked were the power discretes, nothing else worked, even the input codes from panasonics own htp site. some of these codes however do work on other panasonic panels, including their LCD's so you may be more lucky. as i probably said earlier i steer my customers away from panasonic and certainly don't supply them myself due to their total disregard for this industry. We spec. pioneers so who knows what the future of that will hold when panasonic supply them? pioneers with no discretes? the world will be a sadder place.
regards mark. |
| [ Reply | Quote & Reply |
| Post 9 made on Tuesday January 6, 2009 at 20:48 | ...it's new! |
davelasker Junior Member |
| |
I finally had a chance to test the result of makehex on my 2008 Panasonic Viera plasma TV. I didn't have a chance to test all of the codes but I did some spot checking. Here is what I found:
1) I ran all the codes from the pdf on Panasonic's site through IRTool and found they were from devices 128, 128.4, and 128.9. I spot checked a few of these (as generated by makehex) and they all worked as they should.
2) The post in the Applied Digital forum that I referenced above has 3 discrete codes that are not in Panny's documentation:
-TV Tuner
-Zoom Aspect
-Full Aspect
Unfortunately these 3 are all non-functional on my TV. That's a real shame, since I was really hoping to find the discrete code for TV Tuner input.
3) I didn't have time to try all 768 codes generated by makehex for the 3 devices, but the few that I did try that were not on Panny's list were all non-functional.
Sorry to not have better news...
Dave |
| [ Reply | Quote & Reply |
| Post 10 made on Thursday January 8, 2009 at 07:13 | ...it's new! |
simoncope Junior Member |
| |
| Just to add to this, I am currently working on a project that has a TH-50PZ81B in it. All the usual known discrete input commands work, with the exception of the Component input... Neither the Component 1 or the Component 2 discrete commands that Panasonic published work, and no input command that I can find will work. So, so frustrating from Panasonic (yet again). We will always try to avoid specifying Panasonic TV sets for this very reason, but every now and then we come up against an existing installation, or a customer-supplied unit. |
| [ Reply | Quote & Reply |
