I've just searched and read though all the previous threads and have not found anything for this particular VCR model. There was a code someone had found for a PV-9662 which I thought might work but doesn't. The ones posted for Panasonic VCR's don't work either. Any help would be greatly appreciated. Just a discrete ON code would be enough.

Guy,

I know you as a big contributor to the Allied Digital message group. Are you trying these codes in a Pronto or using Jay Hogg's IR tools for your Ocelot?

The reason that I am asking is that Panasonic uses two protocols. The older is 58KHz and has 22 data bits. I am quite certain that there are no discrete commands in that command set. The newer ones use a 38KHz protocol with 48 data bits so it is a very long signal by comparison to to the common 32 data bit NEC protocol.

Some VCR's, CD's, DVD's will turn on from off when you hit the play button. So a macro for Play|stop is On and Play|power toggle is off.

I have some other ideas if you are using the Ocelot.

-Jon

Well you're right, I am using the Ocelot and Jay Hogg's IR tools (score 100% for your ESP! ;). As for the protocol carrier frequency, I'm able to learn the remote's commands reliably and I'm specifying 38kHz as the frequency when sampling with the Ocelot. I know that this isn't a definite identification method however. If you think you can see what type of encoding it represents, here is my learned code (converted to Pronto format using Jay's tools) for the power on/off toggle:

0000 006c 005d 0000 0084 0042 000f 0010 000f 0032 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0032 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0032 000f 0010 000f 0012 000f 0032 000f 0010 000f 0012 000f 0010 000d 0012 000f 0012 000d 0012 000f 0012 000d 0012 000f 0032 000f 0012 000f 0032 000f 0032 000f 0032 000f 0032 000f 0010 000f 0012 000f 0032 000f 0010 000f 0032 000f 0032 000f 0012 000f 0032 000f 0010 000f 0032 000f 0b1e 0085 0042 000f 0010 000f 0032 000f 0012 000d 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0032 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0032 000f 0010 000f 0012 000f 0032 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0032 000f 0010 000f 0032 000f 0032 000f 0032 000f 0032 000f 0012 000f 0010 000f 0032 000f 0012

I also tried the code that was supposed to work with PV-9662 found in another thread:

0000 0071 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 0030 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0030 0010 0030 0010 0010 0010 0030 0010 0030 0010 0010 0010 0a9c

and even "adapted" it to look like the learned on/off code (with the different header style and adding the equivalent repeated section which gives:

0000 006c 005d 0000 0084 0042 000f 0010 000f 0032 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0032 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0032 000f 0010 000f 0012 000f 0032 000f 0010 000f 0012 000f 0010 000d 0012 000f 0012 000d 0012 000f 0012 000d 0012 000f 0032 000f 0012 000f 0032 000f 0032 000f 0032 000f 0032 000f 0032 000f 0032 000f 0032 000f 0010 000f 0032 000f 0032 000f 0012 000f 0032 000f 0032 000f 0010 000f 0b1e 0084 0042 000f 0010 000f 0032 000f 0012 000d 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0032 000f 0010 000f 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0032 000f 0010 000f 0012 000f 0032 000f 0010 000f 0012 000f 0010 0010 0012 000f 0010 000f 0012 000f 0010 000f 0012 000f 0032 000f 0010 000f 0032 000f 0032 000f 0032 000f 0032 000f 0032 000f 0032 000f 0032 001f 0012

but it still doesn't work, although I'm still very new to IR encoding so this might just have been a shot in the dark. If you see an obvious fallacy in all this, tell me!

I know that as an Ocelot user, I can always make a current draw detection circuit (I made one using the core of an old tv flyback transformer) but I'm trying to avoid that if at all possible. Thanks for any suggestions.

Guy,

I can summarize what I found. I have repeated the first four, 2-hex byte words known as the "preamble" adjacent to what the command is. As you know 0000 is learned, the next is frequency/wave length, then # of burst pairs in non repeating and repeating segments respectively all in hex. Above those four words I put calculations for frequency, wavelength (the first two words and the decimal equavelent above the 3rd and 4th words.

Then below the preamble, I put the decimal equivalent of the 48 data bits 8-bits at a time (the bits are transmitted backwards. For all Panasonic newer protocol commands the first two numbers are always 2 and 32 respectively. VCR's are Device=144 and Sub-device=0 or 144 and 1 for VCR2. Then the command --61 is always the power toggle and in all the Panasonic discrete codes that I have seen 62=On and 63=Off. Finally the last 8-bits is a check byte and is the XOR of device, sub-device, and command.

In your toggle command (and your corrected command), what you actually have is the first 48 data bits followed by 42 data bits. There is a Lead-In burst and lead-Out burst so 1+48+1 (for segment 1)+1+42=93.

The correct number is really decimal 50, but that repeats. So in leaned commands we usually see fragments of successive commands. The Ocelot just learns the On and Off sequences until it runs out of memory allocation. I would probably ignore your "found command" except for the fact that its XOR is calculatd correctly.

It seems like to me if your toggle works, then your "corrected" command 253 should work. I have never seen this command before and I usually translate all found discrete commands into decimal device, sub-device and command.

So my suggestion that I generate a four command lir file from Barry Gordon's GenIRDB for Power toggle (to make sure that it works), VCR On and Off (commands 62 and 63) and command 253 to see if they work for you

Finally I added the discrete commands for VCR1 from Remote Central for comparison.


38.4 Hz, 26.1uS, 93 Burst Pairs, 0 Burst Pairs
toggle 0000 006C 005d 0000
2, 32, 144, 0, 61, 173

36.7, 27.3, 0, 50
"on" 0000 0071 0000 0032
2, 32, 144, 0, 253, 109

38.4, 26.1, 93, 0
Adj "On"0000 006c 005d 0000
2, 32, 144, 0, 253, 109

37.0, 27.0, 0, 50
off 0000 0070 0000 0032
2, 32, 144, 0, 63, 175

37.0, 27.0, 0, 50
on 0000 0070 0000 0032
2, 32, 144, 0, 62, 174

-Jon

This message was edited by jarmstrong on 01/05/03 10:34.

Well first of all, thanks for your clear explanation of how the codes work (field names, XOR, etc.). I tried the suggested codes you give at the bottom of your post and even tried creating a few of my own based on the idea that the existing discrete codes often appear to have the lower bits all set, so I tried:

2, 32, 144, 0, 254, 110

2, 32, 144, 0, 255, 111

2, 32, 144, 0, 127, 239

2, 32, 144, 0, 191, 47

But all without success. As a confirmation of the correct, format I also cleaned up the learned on/off toggle by removing the partial repeat and adjusting the number of burst pairs (third byte) to 32 hex, and the toggle still worked perfectly.

Smells like a TOAD to me... but I'm open to any other suggestions. Have other "48 bit" Panasonic devices also been determined to be TOADs too? Thanks for your time!