Pioneer Remote Control cannot be recorded

Topic: Pioneer Remote Control cannot be recorded (Read 16137 times) previous topic - next topic

Pioneer Remote Control cannot be recorded

July 02, 2014, 04:48:22 pm

I want to record my Remote Control for a Pioneer BD Player BDP-333.

Recording with the program IRRECORD works, but I am told, that all keys are recorded with the same value. The reason is, that the remote control sends 2 frames for each key. The first frame is identical and only the 2nd frame is different per key.

a sample, how a recoding should look like, can be found here:

http://lirc.sourceforge.net/remotes/pioneer/VXX2910

Is there a way, to tell IRRECORD, to respect this fact?

pope5

Re: Pioneer Remote Control cannot be recorded

Reply #1 – July 02, 2014, 11:53:36 pm

[quote author="pope5"]I want to record my Remote Control for a Pioneer BD Player BDP-333.

Recording with the program IRRECORD works, but I am told, that all keys are recorded with the same value. The reason is, that the remote control sends 2 frames for each key. The first frame is identical and only the 2nd frame is different per key.

a sample, how a recoding should look like, can be found here:

http://lirc.sourceforge.net/remotes/pioneer/VXX2910

Is there a way, to tell IRRECORD, to respect this fact?

pope5[/quote]

Hmm...I swear that I replied to this once already. Anyway, do you just want to get the IR Toy and IRRECORD program to be able to record multi-partite protocols, or do you just want to be able to send IR that will control your Blu-ray player? If it's the latter, there are other better ways to capture/analyze data than IR Toy/IRRECORD combo. I have re-flashed my IR Toy with the "frowned upon" Widget FW and use it with a program called IR Scrutinizer to capture data and export in LIRC format.

To capture a multi-part Pioneer Blu-ray protocol, I first punched in the Pioneer code on my One-For-All programmable remote and used that as the source to be captured. Running IR Scrutinizer with the IR Toy running on Widget FW, I captured the "play" button and exported that in LIRC format. It looks like this:

Code: [Select]

# Automatically generated LIRC file
#
# Creating tool: IrScrutinizer version 1.1.0
# Creating user: Nobody
# CreateDate: Wed Jul 02 09:48:18 PDT 2014
#
#
# Export from IrScrutinizer
#
begin remote
	name	IrScrutinizerExport
	flags	RAW_CODES
	eps	30
	aeps	100
	frequency	40639
	gap	303159
		begin raw_codes

			name IrScrutinizer captured signal
				8342 4208 517 1575 517 517 517 517 
				517 517 517 517 517 1575 517 517 
				517 1575 517 517 517 1575 517 1575 
				517 1575 517 1575 517 517 517 1575 
				517 517 517 1575 517 517 517 517 
				517 517 517 517 517 517 517 517 
				517 1575 517 517 517 1575 517 1575 
				517 1575 517 1575 517 1575 517 1575 
				517 517 517 27388 8342 4208 517 1575 
				517 1575 517 1575 517 1575 517 517 
				517 1575 517 517 517 1575 517 517 
				517 517 517 517 517 517 517 1575 
				517 517 517 1575 517 517 517 1575 
				517 517 517 517 517 1575 517 1575 
				517 1575 517 517 517 517 517 517 
				517 1575 517 1575 517 517 517 517 
				517 517 517 1575 517 1575 517 
		end raw_codes
end remote

Try sending this from your IR Toy and see if it activates "play" on your Blu-ray player.

BTW, IR Scrutinizer is supposed to be compatible with the native IR Toy FW, though the author doesn't seem to think it works very well. It even has IR Toy send capability supposedly, but I'm too lazy to flash my IR Toy back to the native FW, just to see that.

Re: Pioneer Remote Control cannot be recorded

Reply #2 – July 03, 2014, 06:03:21 pm

Ok, now I verified that IR Scrutinizer software can capture multi-part IR protocols via IR Toy running native FW. No need to reflash with Widget FW. IR Scrutinizer seems to be using the IR Toy sampling mode. So, it doesn't know the actual frequency. In the exported LIRC file, it says 36 KHz even though Pioneer protocol uses 40 KHz. That won't make any difference, as I've never seen a device that is able to discriminate 36 vs 40. The Widget FW of course, is able to tell the frequency more exactly.

In any case, here's the IR Toy FW capture via IR Scrutinizer exported to LIRC:

Code: [Select]

# Automatically generated LIRC file
#
# Creating tool: IrScrutinizer version 1.1.0
# Creating user: nobody
# CreateDate: Thu Jul 03 08:47:26 PDT 2014
#
#
# Export from IrScrutinizer
#
begin remote
	name	IrScrutinizerExport
	flags	RAW_CODES
	eps	30
	aeps	100
	frequency	36683
	gap	1397443
		begin raw_codes

			name IrScrutinizer captured signal
				8069 4662 627 1472 627 409 627 409 
				627 409 627 409 627 1472 627 409 
				627 1472 627 409 627 1472 627 1472 
				627 1472 627 1472 627 409 627 1472 
				627 409 627 1472 627 409 627 409 
				627 436 627 409 627 409 627 409 
				627 1472 627 409 627 1472 627 1472 
				627 1472 627 1472 627 1472 627 1472 
				627 409 600 27561 7551 5152 627 1472 
				627 1472 627 1472 627 1472 627 436 
				572 1527 627 409 627 1472 627 409 
				627 409 627 409 572 436 627 1472 
				627 409 627 1472 627 409 627 1472 
				627 409 627 409 627 1472 627 1472 
				627 1472 627 409 627 409 627 409 
				572 1527 627 1472 627 409 627 409 
				627 409 627 1472 627 1472 627 
		end raw_codes
end remote

The IR Scrutinizer software is a bit more than most IR Toy users will want, but it does solve the immediate issue of capturing multi-part signals using the IR Toy. You can fetch it here:

http://http://www.hifi-remote.com/forums/dload.php?action=file&file_id=12313

Discussion/help here:

http://http://www.hifi-remote.com/forums/viewtopic.php?t=14986

Re: Pioneer Remote Control cannot be recorded

Reply #3 – July 06, 2014, 02:11:08 pm

@Qwlciguk

sorry for my deleayed reply. I was a little bit too bussy with other things. So I couldn't reply immediately.

I want to use IRToy to get the codes the original remote control sends, that I can use this code in my tablet pc and also in my smartphone which both have an infra red beam to control my LCD, Sat receiver, AV Receiver and so on.
Even databases with 60.000 remote controls do not show those, I use (Vantage, Pioneer).

Today, I have installed IR Scrutinizer, however there are so many tabs, that I have to look closer, how I can record all buttons of especially my Pioneer rc for blueray disk player, that I get the codes for my app for the tablet (Lenovo) and smartphone (Galaxy S4).

I will report here, when I succeeded.

pope5

Re: Pioneer Remote Control cannot be recorded

Reply #4 – July 08, 2014, 03:13:32 pm

I have tried to run the program IrScrutinizer Vers. 1.1.0. But generally speaking, I do not understand how to use it. Especially, how to create a file similar to a file, created by winlirc.

Besides, I get messages like "Internal error" followed by "no signal received". And sometimes, I get a string in the upper window.

What I do after I started the program is first, that I klick the tab "Capturing hw", select then IrToy, enter the Serial Port Com12 (I take this from the manager "Com and LPT" entry, as this comport appears, whenI connect the IrToy) an klick then "open". IrScrutinizer shows Version: V222 (which seems the fw version from the IrToy). This tells me also, that the IrToy is connected and recognized.

Then I klick the tab Scrutinize signal and the button Capture. The button gets darker and I then I press the play button on my Pioneer Remote Control. I get the message Internal error and no signal received.

However, I also got sometimes a string in the upper part of the window. What shall I do then?

Thank you for any help.

pope5

Re: Pioneer Remote Control cannot be recorded

Reply #5 – July 08, 2014, 05:04:41 pm

[quote author="pope5"]I have tried to run the program IrScrutinizer Vers. 1.1.0. But generally speaking, I do not understand how to use it. Especially, how to create a file similar to a file, created by winlirc.

Besides, I get messages like "Internal error" followed by "no signal received". And sometimes, I get a string in the upper window.

What I do after I started the program is first, that I klick the tab "Capturing hw", select then IrToy, enter the Serial Port Com12 (I take this from the manager "Com and LPT" entry, as this comport appears, whenI connect the IrToy) an klick then "open". IrScrutinizer shows Version: V222 (which seems the fw version from the IrToy). This tells me also, that the IrToy is connected and recognized.

Then I klick the tab Scrutinize signal and the button Capture. The button gets darker and I then I press the play button on my Pioneer Remote Control. I get the message Internal error and no signal received.

However, I also got sometimes a string in the upper part of the window. What shall I do then?

Thank you for any help.

pope5[/quote]

As far as I can tell, you did everything correctly. I do the same sequence and it's working. Maybe you could try the patch:

http://www.hifi-remote.com/forums/dload ... e_id=12633

Re: Pioneer Remote Control cannot be recorded

Reply #6 – July 08, 2014, 06:10:28 pm

ok, I installed the patch and tried it again (now under Win 7). IrScrutinizer seems to work better.

But... this is the result I get when I press the play button on my Pioneer rc. Look a little bit different

0000 151553 0000 0044 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

protocol = NEC2, device = 161, obc = 129
protocol = NEC2, device = 175, obc = 57

What shall I do next?

(when I press the button "scutinize" I get a window reading: ParseException: Could not interpret string 000 151553 0000 0044 ....
and I can only klick the ok button)

Thanks for your help

pope5

Re: Pioneer Remote Control cannot be recorded

Reply #7 – July 08, 2014, 06:49:39 pm

First of all, the patch is absolutely crucial for IrToy users; it fixes several problems.

The caputure "0000 151553 ...." is completely nonsensical, consisting mostly of zeros. It is not compatible with the decodes as NEC2. This is a bad capture, do no worry about a parse error...

However, the lirc file previously posted looks completely plausible.

The procedure for recording and exporting a remote goes like this: Since you want to investigate a remote (collection of signals), not just a single singal, you select the "Scrutinize remote" pane. Select "Parametric remote", unless you are sure you want to capture raw. Press "Capture". Now you fire your remote to the sensor, key after key. (The 1.4 second delay is to blame on the IrToy firmware...) Fill in the name column as you see fit. Then go to the export pane, select the desired export format, e.g. LIRC, press "Export param. remote".

You can also, without selecting the "Export" pane, from the top menu, select File -> Export -> Parametrized Signals -> LIRC.

Of course, there are also some more options...

Re: Pioneer Remote Control cannot be recorded

Reply #8 – July 09, 2014, 03:57:25 pm

@Barf

Thank you for your information, how to create a lirc file. That was something, I missed in the help documentation. Knowing this, I could record all the keys of my remote and was able to create a lirc file.

So far the good news.

1.) The bad news is, that all keys seem to have the same value. That was already the fact, when I used the program winlirc.
As previously Qwlciguk (Thu Jul 03, 2014 6:03 pm) said, the remote has multi-part IR protocols. And for me it seems, that all
keys have only the first part.

Here is the beginning of the generated LIRC file:

# Automatically generated LIRC file
#
# Creating tool: IrScrutinizer version 1.1.0a
# Creating user: ppi5750
# CreateDate: Wed Jul 09 14:09:20 CEST 2014
#
# Manufacturer: Pioneer
# Model: BD333
#
# Export from IrScrutinizer
#
begin remote
   name   unknown_thing
   flags   RAW_CODES
   eps   30
   aeps   100
   frequency   38400
   gap   39756
      begin raw_codes

         name on/off
            9024 4512 564 1692 564 564 564 564
            564 564 564 564 564 1692 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 564 564 1692
            564 564 564 1692 564 564 564 564
            564 564 564 564 564 564 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 1692 564 1692
            564 564 564
         name open/close
            9024 4512 564 1692 564 564 564 564
            564 564 564 564 564 1692 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 564 564 1692
            564 564 564 1692 564 564 564 564
            564 564 564 564 564 564 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 1692 564 1692
            564 564 564
         name Video_Output_Reset
            9024 4512 564 1692 564 564 564 564
            564 564 564 564 564 1692 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 564 564 1692
            564 564 564 1692 564 564 564 564
            564 564 564 564 564 564 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 1692 564 1692
            564 564 564
         name Audio
            9024 4512 564 1692 564 564 564 564
            564 564 564 564 564 1692 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 564 564 1692
            564 564 564 1692 564 564 564 564
            564 564 564 564 564 564 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 1692 564 1692
            564 564 564

2.) Besides, I get problems with some keys of the remote control.
When creating the LIRC File, there are some errors in the log:
Warning: Signal named secondary_video (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named Disc_Navigator (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named play1 (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named pause (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named yellow (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named replay (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named 3_again (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named enter_again (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named ??? (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named yellow_again (null) could not be rendered (Protocol NEC not known.); ignored.
File D:lirc_2014-07-09_14-09-20.lirc was successfully written.

3.) I wanted to record some of the keys again. How can I move the line to the appropriate position. I klick the newly recorded line at the end of the Parametric Remote Table, then i press the right mouse button an select "move up". The field above the marked line is framed with a blue rectangle. I press some more ctrl-up, the rectangle move up more lines. But how do I get the desired line to the rectangle?

Thank you for your help

pope5

Re: Pioneer Remote Control cannot be recorded

Reply #9 – July 09, 2014, 06:24:44 pm

[quote author="pope5"]@Barf

Thank you for your information, how to create a lirc file. That was something, I missed in the help documentation. Knowing this, I could record all the keys of my remote and was able to create a lirc file.

So far the good news.

1.) The bad news is, that all keys seem to have the same value. That was already the fact, when I used the program winlirc.
As previously Qwlciguk (Thu Jul 03, 2014 6:03 pm) said, the remote has multi-part IR protocols. And for me it seems, that all
keys have only the first part.

Here is the beginning of the generated LIRC file:

# Automatically generated LIRC file
#
# Creating tool: IrScrutinizer version 1.1.0a
# Creating user: ppi5750
# CreateDate: Wed Jul 09 14:09:20 CEST 2014
#
# Manufacturer: Pioneer
# Model: BD333
#
# Export from IrScrutinizer
#
begin remote
   name   unknown_thing
   flags   RAW_CODES
   eps   30
   aeps   100
   frequency   38400
   gap   39756
      begin raw_codes

         name on/off
            9024 4512 564 1692 564 564 564 564
            564 564 564 564 564 1692 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 564 564 1692
            564 564 564 1692 564 564 564 564
            564 564 564 564 564 564 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 1692 564 1692
            564 564 564
         name open/close
            9024 4512 564 1692 564 564 564 564
            564 564 564 564 564 1692 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 564 564 1692
            564 564 564 1692 564 564 564 564
            564 564 564 564 564 564 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 1692 564 1692
            564 564 564
         name Video_Output_Reset
            9024 4512 564 1692 564 564 564 564
            564 564 564 564 564 1692 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 564 564 1692
            564 564 564 1692 564 564 564 564
            564 564 564 564 564 564 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 1692 564 1692
            564 564 564
         name Audio
            9024 4512 564 1692 564 564 564 564
            564 564 564 564 564 1692 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 564 564 1692
            564 564 564 1692 564 564 564 564
            564 564 564 564 564 564 564 564
            564 1692 564 564 564 1692 564 1692
            564 1692 564 1692 564 1692 564 1692
            564 564 564

2.) Besides, I get problems with some keys of the remote control.
When creating the LIRC File, there are some errors in the log:
Warning: Signal named secondary_video (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named Disc_Navigator (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named play1 (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named pause (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named yellow (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named replay (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named 3_again (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named enter_again (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named ??? (null) could not be rendered (Protocol NEC not known.); ignored.
Warning: Signal named yellow_again (null) could not be rendered (Protocol NEC not known.); ignored.
File D:lirc_2014-07-09_14-09-20.lirc was successfully written.

3.) I wanted to record some of the keys again. How can I move the line to the appropriate position. I klick the newly recorded line at the end of the Parametric Remote Table, then i press the right mouse button an select "move up". The field above the marked line is framed with a blue rectangle. I press some more ctrl-up, the rectangle move up more lines. But how do I get the desired line to the rectangle?

Thank you for your help

pope5[/quote]

It will capture both parts of the signal if you capture via the "scrutinize signal" tab instead of the "scrutinize remote" tab. I mentioned it to the author in the IR Scrutinizer thread. There doesn't seem to be an obvious solution there.

Re: Pioneer Remote Control cannot be recorded

Reply #10 – July 09, 2014, 06:52:42 pm

Barf,

unfortunately, when I capture the signal via the Scrutinize signal Tab, I get only such a string, you told me, that it is without value, as it contains mostly 0000.

I just tried the play button again and got:
0000 A8AAA 0000 0044 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

The log reads:
protocol = NEC, device = 161, obc = 129
protocol = NEC, device = 175, obc = 57
protocol = NEC, device = 161, obc = 129
protocol = NEC, device = 175, obc = 57
WARNING: When computing the Pronto representation, a (non-empty) ending sequence was ignored

When I press the key longer, I get an error message reading:
HarcHardwareException: Hardware based exception:IrToy:Erroneous data received.

Do you have more ideas, what can I do?

Thank's

pope5

Re: Pioneer Remote Control cannot be recorded

Reply #11 – July 09, 2014, 08:33:50 pm

[quote author="pope5"]
1.) The bad news is, that all keys seem to have the same value. That was already the fact, when I used the program winlirc.
As previously Qwlciguk (Thu Jul 03, 2014 6:03 pm) said, the remote has multi-part IR protocols. And for me it seems, that all
keys have only the first part.
[/quote]
I explained what is going on in the other thread. The easy ("obvious") solution is to instead capture as raw (select Scrutinize Remote -> Raw Remote instead. Capture and export as before. In particular since you seem to be interested in generating LIRC files, and LIRC definitely does not know what "dual Pioneer" is.

Quote

2.) Besides, I get problems with some keys of the remote control.
When creating the LIRC File, there are some errors in the log:
Warning: Signal named secondary_video (null) could not be rendered (Protocol NEC not known.); ignored.

Here is something that you do not tell me/us. How is your Lirc coming up with the idea that it is NEC?

Quote

3.) I wanted to record some of the keys again. How can I move the line to the appropriate position. I klick the newly recorded line at the end of the Parametric Remote Table, then i press the right mouse button an select "move up". The field above the marked line is framed with a blue rectangle. I press some more ctrl-up, the rectangle move up more lines. But how do I get the desired line to the rectangle?

Oops, I will have a closer look

Quote

I just tried the play button again and got:
0000 A8AAA 0000 0044 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

The log reads:
protocol = NEC, device = 161, obc = 129
protocol = NEC, device = 175, obc = 57
protocol = NEC, device = 161, obc = 129
protocol = NEC, device = 175, obc = 57

I have a problem in that the Hex form and the decodes are not consistent. There is no way the listed hex can decode to a NEC signal.
Turn on the "verbose" option, turn off "invoke repeat finder" and "used cleansed captures".

Re: Pioneer Remote Control cannot be recorded

Reply #12 – July 09, 2014, 09:36:14 pm

Quote

3.) I wanted to record some of the keys again. How can I move the line to the appropriate position. I klick the newly recorded line at the end of the Parametric Remote Table, then i press the right mouse button an select "move up". The field above the marked line is framed with a blue rectangle. I press some more ctrl-up, the rectangle move up more lines. But how do I get the desired line to the rectangle?

OMG. Sorry for that. Try http://www.harctoolbox.org/storage/IrScrutinizer.jar

Thanx for finding the bug.

Re: Pioneer Remote Control cannot be recorded

Reply #13 – July 09, 2014, 10:12:42 pm

Quote

pope5 wrote:1.) The bad news is, that all keys seem to have the same value. That was already the fact, when I used the program winlirc.
As previously Qwlciguk (Thu Jul 03, 2014 6:03 pm) said, the remote has multi-part IR protocols. And for me it seems, that all
keys have only the first part.

I explained what is going on in the other thread. The easy ("obvious") solution is to instead capture as raw (select Scrutinize Remote -> Raw Remote instead. Capture and export as before. In particular since you seem to be interested in generating LIRC files, and LIRC definitely does not know what "dual Pioneer" is.

the created lirc file looks better and it seems, the keys are different. I will try these values to use it with my Samsung Galaxy S4 with built in ir beamer and the app IRCOID where I set these values to use my smartphone as a remote control. I will report, if this works.

The beginning of the file looks like this:
# Automatically generated LIRC file
#
# Creating tool: IrScrutinizer version 1.1.0a
# Creating user: ppi5750
# CreateDate: Wed Jul 09 21:37:34 CEST 2014
#
# Manufacturer: Pioneer
# Model: BDB333
#
# Export from IrScrutinizer
#
begin remote
name unknown_thing
flags RAW_CODES
eps 30
aeps 100
frequency 6
gap 1398078
begin raw_codes

name on/off
8530 4217 554 1537 553 493 553 493
553 493 553 493 554 1537 553 493
554 1537 553 493 554 1537 554 1537
554 1537 554 1537 553 493 554 1537
553 493 554 1537 553 493 553 493
553 493 553 493 553 493 553 493
554 1537 553 493 554 1537 554 1537
554 1537 554 1537 554 1537 554 1537
553 493 555 25344 8530 4217 554 1537
554 1537 554 1537 554 1537 553 493
554 1537 553 493 554 1537 553 493
553 493 553 493 553 493 554 1537
553 493 554 1537 553 493 553 493
553 493 554 1537 554 1537 554 1537
554 1537 553 493 554 1537 554 1537
554 1537 553 493 553 493 553 493
553 493 554 1537 553 493 555
name open/close
8526 4203 555 1537 554 492 554 492
554 492 554 492 555 1537 554 492
555 1537 554 492 555 1537 555 1537
555 1537 555 1537 554 492 555 1537
554 492 555 1537 554 492 554 492
554 492 554 492 554 492 554 492
555 1537 554 492 555 1537 555 1537
555 1537 555 1537 555 1537 555 1537
554 492 551 25348 8526 4203 555 1537
555 1537 555 1537 555 1537 554 492
555 1537 554 492 555 1537 554 492
554 492 554 492 554 492 555 1537
554 492 555 1537 554 492 554 492
555 1537 555 1537 554 492 555 1537
555 1537 554 492 555 1537 555 1537
554 492 554 492 555 1537 554 492
554 492 555 1537 554 492 551
name Video_Output_reset
8530 4207 555 1538 554 492 554 492
554 492 554 492 555 1538 554 492
555 1538 554 492 555 1538 555 1538
555 1538 555 1538 554 492 555 1538
554 492 555 1538 554 492 554 492
554 492 554 492 554 492 554 492
555 1538 554 492 555 1538 555 1538
555 1538 555 1538 555 1538 555 1538
554 492 555 25344 8530 4207 555 1538
555 1538 555 1538 555 1538 554 492
555 1538 554 492 555 1538 554 492
554 492 554 492 554 492 555 1538
554 492 555 1538 554 492 555 1538
554 492 554 492 554 492 554 492
555 1538 554 492 554 492 554 492
555 1538 555 1538 555 1538 555 1538
554 492 555 1538 555 1538 555

Quote

2.) Besides, I get problems with some keys of the remote control.
When creating the LIRC File, there are some errors in the log:
Warning: Signal named secondary_video (null) could not be rendered (Protocol NEC not known.); ignored.

Here is something that you do not tell me/us. How is your Lirc coming up with the idea that it is NEC?

it is not my Lirc, it is the program IrScrutinizer, which writes NEC in its log. Or don't I understand you?

Quote

3.) I wanted to record some of the keys again. How can I move the line to the appropriate position. I klick the newly recorded line at the end of the Parametric Remote Table, then i press the right mouse button an select "move up". The field above the marked line is framed with a blue rectangle. I press some more ctrl-up, the rectangle move up more lines. But how do I get the desired line to the rectangle?

Oops, I will have a closer look

great, I already see, that you have a solution for this. I will try it tomorrow.

Quote

I just tried the play button again and got:
0000 A8AAA 0000 0044 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

The log reads:
protocol = NEC, device = 161, obc = 129
protocol = NEC, device = 175, obc = 57
protocol = NEC, device = 161, obc = 129
protocol = NEC, device = 175, obc = 57

I have a problem in that the Hex form and the decodes are not consistent. There is no way the listed hex can decode to a NEC signal.
Turn on the "verbose" option, turn off "invoke repeat finder" and "used cleansed captures".

I tried this, but when I select the tab "Scrutinize signal", a key press is not easily recognized (though all 50 keys were recognized, when I did the "scrutinize remote" immediately before). Finally I got the warning:
Outputting an uninterpreted IrSequence in the selected output format not possible, using Raw format.
I klick the ok button, then I can copy and past the upper window:

+8512 -4224 +555 -1557 +533 -491 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -512 +533 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -1557 +533 -491 +555 -491 +555 -491 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -1557 +555 -1536 +555 -491 +555 -25344 +8512 -4224 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -1557 +555 -491 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -491 +555 -1557 +533 -491 +555 -1536 +555 -491 +555 -491 +555 -1536 +555 -1557 +555 -1536 +555 -491 +555 -491 +555 -512 +533 -1536 +555 -1536 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -1536 +555 -25344 +8512 -4245 +533 -1557 +533 -491 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -1536 +555 -512 +533 -1536 +555 -491 +555 -491 +555 -512 +533 -512 +533 -491 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -25344 +8512 -4224 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -1557 +555 -491 +555 -491 +555 -512 +533 -491 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -491 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -1536 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -1536 +555 -25344 +8512 -4224 +555 -1536 +555 -491 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -491 +555 -491 +555 -512 +533 -491 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -25344 +8512 -4224 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -491 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -1536 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -1536 +555 -25344 +8512 -4224 +555 -1536 +555 -491 +555 -491 +555 -512 +533 -491 +555 -1536 +555 -491 +555 -1536 +555 -512 +533 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -491 +555 -491 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -25344 +8512 -4224 +555 -1536 +555 -1536 +555 -1536 +555 -1557 +533 -491 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -491 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -1536 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -1536 +555 -25344 +8512 -4224 +555 -1557 +555 -491 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -512 +533 -1557 +555 -491 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -491 +555 -491 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -512 +533 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -25344 +8512 -4224 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -512 +533 -491 +555 -491 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -512 +533 -1536 +555 -491 +555 -512 +533 -1536 +555 -1536 +555 -1536 +555 -512 +533 -491 +555 -512 +533 -1536 +555 -1536 +555 -491 +555 -491 +555 -512 +533 -1536 +555 -1536 +555 -25344 +8512 -4224 +555 -1536 +555 -491 +555 -491 +555 -491 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -1536 +555 -1536 +555 -1557 +555 -491 +555 -1536 +555 -491 +555 -1536 +555 -491 +555 -491 +555 -491 +555 -491 +555 -512 +533 -491 +555 -1536 +555 -512 +533 -1536 +555 -1536 +555 -1536 +555 -1557 +533 -1536 +555 -1536 +555 -491 +555 -25344 +8512 -4224 +555 -1536 +555 -1536 +555 -1536 +555 -1536 +555 -491 +555 -1536

and the log:
no signal received
no signal received
protocol = NEC, device = 161, obc = 129
protocol = NEC, device = 175, obc = 57
protocol = NEC, device = 161, obc = 129
protocol = NEC, device = 175, obc = 57
protocol = NEC, device = 161, obc = 129
protocol = NEC, device = 175, obc = 57
protocol = NEC, device = 161, obc = 129
protocol = NEC, device = 175, obc = 57
protocol = NEC, device = 161, obc = 129
protocol = NEC, device = 175, obc = 57
protocol = NEC, device = 161, obc = 129

I hope, this will help you, to get the desired information. If you need anything more, let me know.

I will report, if the values from the lirc raw file work.

pope5

Re: Pioneer Remote Control cannot be recorded

Reply #14 – July 10, 2014, 12:59:59 pm

Good news!

I have captured all the buttons of the Pioneer Remote in RAW Format and have inserted some of the values in some buttons of my smartphone app RCoid. And it works. I can e.g. switch on and off the Pioneer BD Player.

Thank you for all your help.

pope5