The simple Pioneer signals are just NEC2 at 40000 Hz. If you don't have an .irp file for that, you can just edit the frequency in the NEC2.irp file.
On December 13, 2007 at 15:22, tgrugett said...
Does anyone know if this beast responds to discrete power
commands?
I thought the Pioneer web site was pretty good at giving such info. Doesn't it have the device type you want?
The non-working codes decode as a NEC2 protocol
Power NEC2 D170, F28
0000 0009 0001 0022 0F57 07A9 0F57 07A9 00F1 00F1 00F1
That's a mess. My decode software can give a correct decode for some really bad learns like that. But I wouldn't expect that learned signal to work.
Another power code from the RTI library decoding as a
Pioneer protocol does work.
It appears to have four repeats which are not set via
the RTI software.
The only difference between the simple Pioneer protocol and NEC2 is the modulation frequency. Your bad learn had totally garbage frequency. The RTI library signal had correct Pioneer frequency.
You are correct that library signal encodes exactly four frames, where the learn (or normal MakeHex output or most other sources of Pioneer signals) encodes "repeat one frame as long as the button is held". I don't think that is the important difference.
The non-working (NEC2) file lists discrete power codes
at functions 26 an 27 so I would like to generate Pioneer
protocol versions of these to try but unfortunately there
does not seem to be a Pioneer protocol .irp file in my
make hex collection.
Answered above.
Last edited by johnsfine
on December 13, 2007 17:11.
