Try this version of LOUDNESS

0000 0068 0000 0022 0168 00B4 0016 0043 0016 0016 0016 0043 0016 0016 0016 0016 0016 0043 0016 0016 0016 0043 0016 0016 0016 0043 0016 0016 0016 0043 0016 0043 0016 0016 0016 0043 0016 0016 0016 0016 0016 0016 0016 0043 0016 0016 0016 0016 0016 0016 0016 0043 0016 0016 0016 0043 0016 0043 0016 0016 0016 0043 0016 0043 0016 0043 0016 0016 0016 0043 0016 06D9

Try this version of Midnight

0000 0068 0000 0044 0168 00B4 0016 0043 0016 0016 0016 0043 0016 0016 0016 0016 0016 0043 0016 0016 0016 0043 0016 0016 0016 0043 0016 0016 0016 0043 0016 0043 0016 0016 0016 0043 0016 0016 0016 0043 0016 0043 0016 0043 0016 0043 0016 0043 0016 0016 0016 0016 0016 0043 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0043 0016 0043 0016 0016 0016 06D9 0168 00B4 0016 0043 0016 0016 0016 0043 0016 0016 0016 0016 0016 0043 0016 0016 0016 0043 0016 0016 0016 0043 0016 0016 0016 0043 0016 0043 0016 0016 0016 0043 0016 0016 0016 0043 0016 0043 0016 0016 0016 0043 0016 0016 0016 0016 0016 0043 0016 0043 0016 0016 0016 0016 0016 0043 0016 0016 0016 0043 0016 0043 0016 0016 0016 0016 0016 06D9



Looking at post 9 of this thread, the LOUDNESS signal there has the same structure as the LOUDNESS I posted and ones I've seen in many other places. But the one in post 9 is at a lower than normal frequency.

The Midnight signal in post 9 also matches the structure of the one I just posted (matching several other sources) but in that case the one in post 9 is at a higher than normal frequency. Hopefully the correct frequency will make it work.

Edit: I guess I should have reread the whole thread more carefully before answering. Some of the otherr versions of Loudness and Midnight in this thread are much closer to what I'm posting here, so that makes it harder to understand why they didn't work for you.

This message was edited by johnsfine on 09/10/04 13:47 ET.

I exchanged a couple emails with him. I don't think he has any IR signal info that either contradicts or noticably expands on what we have from previous reverse engineering efforts. Probably because that reverse engineering got everything right.

I'm wondering if we can narrow down whether the key to this issue is in CCF2MX or in the MX-500 or in your Pioneer device.

Is "Loudness/Midnight" one button? It seems to be two very different IR signals. Why do your mentions of it (and some others) talk about it as one thing? (Remember I know nothing about the Pioneer device in question).

When you got "everything else" to work, was some of that via CCF2MX, or all via learning from the original remote or what?

If you have Pioneer Pronto Hex samples that did convert correctly with CCF2MX, especially "double" format signals like Midnight rather than short one like Loudness, posting such samples may help us figure out the boundary between what can work through CCF2MX and what can't.

I just used their conversion utility CCF2MX v 0.91 to translate the command that John posted above and you get this when you convert all the values from decimal to hex (and it won't make any sense in decimal):

05 bottom nibble is number of words that follow (0 through 5)
00 96 =>Decimal 96 that is 6 x wavelength in uS =>25 uS

06 D9 Word 1 =>Number of wavelengths (Decimal 1753 x 25=43,533 uS)
01 68 Word 2 =>8,940 uS
00 B4 Word 3 =>4,470 uS
00 43 Word 4 =>1,664 uS
00 16 Word 5 => 546 uS

00 Beginning burst pair of repeat segment
43 Ending burst pair of repeat segment (67 decimal)

23 (burst pair 0 -lead in) (each nibble refers to the words above and alternate in on and off)
54 55 54 55 55 54 55 54 first data byte (54=One 55=Zero)
55 54 55 54 54 55 54 55
54 54 54 54 54 55 55 54
55 55 55 55 55 54 54 55
51 - Lead out
23 -Lead in second IR command
54 55 54 55 55 54 55 54
55 54 55 54 54 55 54 55
54 54 55 54 55 55 54 54
55 55 54 55 54 54 55 55
51 - Lead Out burst pair 67 decimal

So all that looks good, its the same commands but according to [Link: irclone.com] where i got the decoding information there is a maximum for each button of 75 bytes and the above is 83 bytes. If the document is correct then either the command gets truncated or it just doesn't work. It could be 75 bytes of burst pairs and if so it should work theoretically :-)

I didn't quite follow that, but I think it's suggesting a Pioneer double command is too long for the internal format used by irclone. I've seen a few other posts that suggest the same thing.

But:

1) That only explains why Midnight didn't work. Loudness is a single command and fits easily.

2) Many of the other commands for this device are double commands, yet it sounds like some of them worked. How can they work if Pioneer Double format is too long?

On reflection, Pioneer double commands have been around for quite a while and IIRC, the MX-500 is still in production. So it seems hard to believe that it couldn't learn those commands or we would have heard a lot more about it. I really was going to report that it looked like the conversion was very accurate, but then did a byte count.

I guess there is no clear answer other than testing the MX that neither of us have :-)

Hello.

Pioneer is getting ready to create a special web site that amoung other things, will have info on controling our products.

Anyone out there have anything that they want posted on the site?

Josh

thanks, hope you post a link when it is up and running

I am installing 15 Pioneer DVR-920H receivers and have all the discrete codes except for input select.

They are being used on a large yacht for backing up satellite programs when out of satellite signal footprint, and I urgently require the discrete code for INPUT 1. The other input codes would be useful.