Skip to main content ↑ ↓
Topic: Pioneer Remote Control cannot be recorded (Read 16136 times) previous topic - next topic

Re: Pioneer Remote Control cannot be recorded

Reply #15 –
@ Barf,

I have tested the latest version you told me 2 posts before. It should solve the problem of shifting entries in the table of tab "Scrutinize remote".

The new version has only a partial success. When I klick an entry (line) and klick rmb, I select move up (or move down) and the entry is moved up and done. However, when i click an entry and press ctlr-up or ctrl-down, only the blue rectangle moves up or down but the selected entry remains at its position.

regards

pope5

Re: Pioneer Remote Control cannot be recorded

Reply #16 –
Nice that it works now. Good example on when parametric captures fails, although my bottom line would be that a better and/or more flexible decoder would be the ultimate solution.

Quote
The new version has only a partial success. When I klick an entry (line) and klick rmb, I select move up (or move down) and the entry is moved up and done. However, when i click an entry and press ctlr-up or ctrl-down, only the blue rectangle moves up or down but the selected entry remains at its position.
Glad that the real problem is solved. The unexpected behavior with ctrl-up and ctrl-down is, I admit, unexpected and confusing, but it is strictly speaking not a bug. If you press ctrl-up or -down while the popup menu has focus, it will work correctly. But it does not "work" if the menu is not visible. That is because the Java table (class JTable) gets these key events, not the menu, and invokes some default actions, which are not really useful. The accelerators on the poput menus are not invoked.

It is not obvious how to proceed. If you have a good suggestion, please let me know. Anyhow, it is a pretty minor GUI-only issue. I might remove the accelerators, since they lead to confusion -- as you convincingly demonstrated!

Quote
it is not my Lirc, it is the program IrScrutinizer, which writes NEC in its log.
You are right. Let me explain: There are the protocols NEC1 and NEC2 (among others), but there is no protocol "NEC". Sometimes the decoder cannot decide between NEC1 and NEC2, and says just "NEC". A "NEC" signal can thus not be rendered, and produces the error message you quoted. If you receive a "NEC", you can either re-capture the signal, or, if you know what you are doing, manually change it to NEC1 or NEC2.

Thank you very much for your feedback!

Re: Pioneer Remote Control cannot be recorded

Reply #17 –
@ Barf

I have to thank you for your support.

pope5

Re: Pioneer Remote Control cannot be recorded

Reply #18 –
Barf,

sorry that I have to resume this tread. But unfortunately, now I get problems with the remote control for the Pioneer AV Receiver.

I wanted to record all my remote controls in RAW Mode, because it is easyer for my remote control app on my smartphone, to insert simply the raw code for a key.  Therefore, I startet to record all my remotes again and now I get the error for that Pioneer RC for the AV Receiver. (Other rcs work.)

Some keys like the play button do not add a new line in the "Scruinize remote tab" - Raw Mode.  That is also true in the "Scrutinize signal" tab. There I get an error reading: no signal received.

I have made a screen shot of Scrutinizer after I recorded multiple keys. Perhaps you can see more than I do.

And by the way: when there are more lines than fit in the screen, I do not see, if the next key has added another line (exept I look to the scroll bar - but that is very bad). Wouldn't it be better, to leave the table at the end than always going to the top? Then I would see, that all entries have been shifted up one line. Or wouldn't it be possible, also to drag the lower limit of that window down, to show more lines? My remote control has 55 keys.

Thank you for your reply

pope

Re: Pioneer Remote Control cannot be recorded

Reply #19 –
What first strikes me is the bad quality of the learns: frequency (should be around 40kHz) often way off, some have intro sequences, some have repeat sequences, some have ending sequences, protocol differs. If trying to caputure raw signals, you have to reject and recapture the bad ones. They should have both a (long) intro and a (long) repeat, but no ending. (BTW, Lirc cannot reproduce a long intro and a long repeat.)

The standard tips on capturing are: Fresh batteries, avoid ambient light in particular sun light and other light sources with IR content. Experiment with the relative locatons of sensor and remote. You can press the keys fairly long: IrScrutinizer identifies the repeats; if the outcome is bad, the capture was bad.

But there is a way to use "cooked" (opposite of raw) signals, just that DecodeIR does not cooperate: Add the following lines to the end of your IrpProtocols.ini:
Code: [Select]

[protocol]
name=Pioneer-Mix
irp={40k,564}<1,-1|1,-3>(16,-8,D:8,~D:8,F:8,~F:8,1,^108m,(16,-8,D2:8,~D2:8,F2:8,~F2:8,1,^108m)+) [D:0..255,F:0..255,D2:0..255=D,F2:0..255=F]
EFC_translation=LSB comp
[documentation]
Two-signal version of the Pioneer protocol; first sends the "normal" signal,
then, as repeat, the one determined by D2 and F2.

Restart the program, which will now know a new protocol "Pioneer-Mix", taking the four parameters D, F, D2, F2.
When you (successfully) capture such a signal in the scrutinizer, (make sure that the option "Print decodes to console" is on), the decoder  will print two lines to the console, like

Code: [Select]
p
rotocol = Pioneer, device = 171, obc = 0
protocol = Pioneer, device = 175, obc = 255
These correspond to the parameters D, F, D2, F2. You then generate, with a mix of captures and manual typing, the desired remote configuration in the "Parametric Remote" table. It should use "Pioneer-mix" as protocol, F, D, D2, F2 per the captures. Since there are no columns for F2 and D2, you have to enter them in the "Misc. Parameters" column, format like "D2=175 F2=255"

Quote
And by the way: when there are more lines than fit in the screen, I do not see, if the next key has added another line (exept I look to the scroll bar - but that is very bad). Wouldn't it be better, to leave the table at the end than always going to the top? Then I would see, that all entries have been shifted up one line.
It should work like that. I will see if there is something flaky, and if so, I will fix it to next version.

Quote
Or wouldn't it be possible, also to drag the lower limit of that window down, to show more lines?
The window is resizeable, and the divider between the middle part and the console can adjusted. So I actually do not understand your wish.

Re: Pioneer Remote Control cannot be recorded

Reply #20 –
@ Barf,

sorry for the delay in my answer. I had no time, to continue testing.

Today, I have added the lines you told me to the file IrpProtocols.ini . I started IrScrutinizer, set the options "Print decodes to console" on and started to recode. Apperently, there is no change. But I didn't understand, what you mean with the "four parameters D, F, D2, F2".

Can you please tell me, what I should do?

After I have captured 23 keys from the remote, I took a screen shot. Now there are so many lines, that not all lines can be shown. 

I can drag the bottom line (marked with a blue arrow) up and down. I can also drag the line, marked with the yellow arrow. This increases however only the grey area. But the line, marked with the red arrow always remains at its position. And I can not drag this line!

When I add more keys, I only see, that the scrolling bar (marked with a green arrow) gets smaller. But the keys shown do not scroll that the very last is seen. I have to drag the scroll bar to see it. But wenn I add another one, line 1 is shown again.

If you need more information, let me know. I expect, that I can report this time more quickly.

pope

Re: Pioneer Remote Control cannot be recorded

Reply #21 –
[quote author="pope5"]
Today, I have added the lines you told me to the file IrpProtocols.ini . I started IrScrutinizer, set the options "Print decodes to console" on and started to recode. Apperently, there is no change.[/quote]

The decoding in IrScrutinizer is done in the library DecodeIR, which was written in C++ a number of years ago, and subsequently improved by others. Even though the sources are available, I consider it as completely unmaintainable code with severe internal problems (see http://www.hifi-remote.com/forums/viewtopic.php?t=14219). There is no possibility to extend it; in particular, adding a protocol to IrpProtocols.ini does not make it aware of the new protocol. There may come a day when I write my own decoder, but that day is not in 2014.

Quote
But I didn't understand, what you mean with the "four parameters D, F, D2, F2".
For example, in the last code snippet, it is 171, 0, 175, and 255.

Quote
I can drag the bottom line (marked with a blue arrow) up and down. I can also drag the line, marked with the yellow arrow. This increases however only the grey area. But the line, marked with the red arrow always remains at its position. And I can not drag this line!
Sorry. That is a bug that will be fixed for the next release.

Actually, everything is in the last message, although possibly a bit brief :-).

But I also converted this file: http://hifi-remote.com/forums/dload.php ... le_id=8635. You can download the result: http://www.harctoolbox.org/storage/pioneer-bluray.girr and import it in IrScrutinizer (Import -> Girr, just paste the URL in the File/URL field, press "Load File/URL", then "Import all"). This should do as a starting poing. But you have to change the Pioneer-mix protocol to
Code: [Select]
[protocol]
name=Pioneer-Mix
irp={40k,564}<1,-1|1,-3>(16,-8,D0:8,~D0:8,F0:8,~F0:8,1,^108m,(16,-8,D:8,~D:8,F:8,~F:8,1,^108m)+) [D0:0..255,F0:0..255,D:0..255=D0,F:0..255=F0]
EFC_translation=LSB comp
[documentation]
Two-signal version of the Pioneer protocol; first sends the "normal" signal (parameters D0 and F0, then, as repeat, the one determined by D and F.

(It is just the parametrization that is changed.)

Re: Pioneer Remote Control cannot be recorded

Reply #22 –
Barf,

thank you for your quick reply!

I still do not understand, what shall I do. Especially, when I want to record the keys of my Pioneer Remot controls.

you wrote:

Quote
    But I didn't understand, what you mean with the "four parameters D, F, D2, F2".

For example, in the last code snippet, it is 171, 0, 175, and 255.

do I have to set anything in th IrSrutinizer before recording the keys?

Today, I have downloaded the file for the Pioneer  BD Player 320. Then I changed the file IrpProtocols.ini to the lines, you gave me in your replay from today and then I started IrScrutinizer. As told, I selected Import -> load File/url and got after pressing import all the message "Import was successfull with 49 signal(s). Jump to panel.

There I made a screenshot. I finally exported this file to a .lirc file.

Was this ok?

regards

pope5

Re: Pioneer Remote Control cannot be recorded

Reply #23 –
The "Pioneer-mix" protocol has four parameters: In the first version, I called them D, F, D2, and F2, in the second version D0, F0, D, and F. Due to imperfection is DecodeIR, these signals cannot be directly captured in "Parametric Remote". Instead, when you capture such a signal, for example on the "scrutinize signal" pane (make sure that the option "print decodes to the console" is on), two lines like
Code: [Select]
protocol = Pioneer, device = 161, obc = 129
protocol = Pioneer, device = 175, obc = 188
are printed to the console. (If it says "NEC" instead of "Pioneer", that is OK.) These numbers correspond (using the newer parametrization) to D0 = 161, F0 = 129, D = 175, and F = 188. You have to enter these signals manually in the parametric remote table (or you fix an existing row). D and F are entered in the respective colums; for D0 and F0 there are no columns, so they have to be entered as "Misc. Parameters" Your screendump shows how it is supposed to look like.

The WARNINGs in your sceendump means that the changes to IrpProtocols.ini either were  not correct, or did not take effect. They are fatal. Not that the program reads the file IrpProtocols.ini  only on startup.

Hope this helps.

Re: Pioneer Remote Control cannot be recorded

Reply #24 –
Barf,

thank you for your patience and your quick reply. Unfortunately, I do not completely understand, what you tell me because I am only a dump user (I have never to to, wir ir protocols). So mostly I guess, what to do. and that I will describe here.

I re-edited the file IrpProtocols.ini and re-added the these lines:

[protocol]
name=Pioneer-Mix
irp={40k,564}<1,-1|1,-3>(16,-8,D0:8,~D0:8,F0:8,~F0:8,1,^108m,(16,-8,D:8,~D:8,F:8,~F:8,1,^108m)+) [D0:0..255,F0:0..255,D:0..255=D0,F:0..255=F0]
EFC_translation=LSB comp
[documentation]
Two-signal version of the Pioneer protocol; first sends the "normal" signal (parameters D0 and F0, then, as repeat, the one determined by D and F.

The only difference I believed to see was, that there was a line-break in the line, following the line {documentation]. But this is shurely not the reason, why I got the errors. More interesting is, that I imported again the .girr file you told me, an today, there were no error messages. The scrutinize remote -> Parametric Remote showed a lot of keys and I could export this data to a .lirc file. If have not used these .lirc file in the app of my smartphone , so I cannot say, if the values are valid.

Then I terminated scrutinize, restartet it again, selected the capturing hardware IrToy, selected the comport and opened the connection. I get Version V222. Now I want to record the Pioneer AV Receiver remote control.

Then I selected "scrutinize remote" -> Parametric Remote and captured 41 keys. (Btw I recognized, that when the pan gets full, all lines are shifted up - have you changed this and is there an automatic update?).  All keys have the protocol NEC2 or NEC but not Pioneer-Mix. 

I also recognized, that some of the keys of the remote never sent a signal - or was not recognized. Eg. the key "1", "3", "4" are recorded, but not the key "2". I do not understand this.

Finally, I klicked the EXPORT Button and got "UnknownProtocolException: Protocol NEC not known.".  See Screenshot 1 (irs 1.jpg)

Then I selected the pane "scrutinize signal", klicked the record button, and pressed the on/off button for 3 seconds on the remote control. After 2 seconds I got an error reading "HarcHardwareException: Hardware based exception: Unsupported IrToy protocol version"  (see screenshot 2 (irs 2.jpg).

Finally I pressed the on/off button for 1 second. and got screenshot 3 (irs 3.jpg).


Barf, you have already spent a lot of time your precious time with my problems. Can you please tell me in detail (for dummies), what shall I do, to record this remote control?  How can I capture e.g. the key "2" on it. And as I understand you, I should copy  some keys, I capture in the 'pane "scrutinize signal" into the table in the pane "Scrutinize remote". If this is true, can you please tell me, how to to this?

Thank you for your help

pope

Re: Pioneer Remote Control cannot be recorded

Reply #25 –
Quote
... showed a lot of keys and I could export this data to a .lirc file. If have not used these .lirc file in the app of my smartphone , so I cannot say, if the values are valid.
Why don't you test it directly from IrScrutinizer? Open the IrToy as sender on "Sending hardware", set "count on that pane to 2 (or more) (problem that is fixed in the development version), and you can send, e.g. from the "Parametric Remote" by the right mouse menu, Transmit selected. (The tooltip text says "Not implemented", which is wrong, sorry).

Quote
All keys have the protocol NEC2 or NEC but not Pioneer-Mix.
I have explained this above.

Quote
got "UnknownProtocolException: Protocol NEC not known.".
Also this was explained above. This is what I wrote:
Quote
There are the protocols NEC1 and NEC2 (among others), but there is no protocol "NEC". Sometimes the decoder cannot decide between NEC1 and NEC2, and says just "NEC". A "NEC" signal can thus not be rendered, and produces the error message you quoted. If you receive a "NEC", you can either re-capture the signal, or, if you know what you are doing, manually change it to NEC1 or NEC2.
I cannot explain it simpler than that. But let me add that NEC1 or NEC2 are the same as Pioneer, except for the repeat and the frequency.

To the first screen shot: The decodes means D0 = 165  F0 =90  D = 165 F = 203. What is disturbing is the "silly" numbers in the upper window. Likely the irtoy delivered a completely wrong frequency. Note that the documentation says (it I remember it correctly) that for accurate frequency measurement, you have to hold the remote very close to the irtoy.