Need .bin file from LIRC for Customized NBC Remote

jojo · Post by **jojo** » Thu Oct 06, 2016 10:18 am

[quote="vickyg2003"]Hmm something looks wrong with your file.

Hi Vicky,

NBC is a terrestrial NEC2 set top box.

Where am I going wrong?

Regards,
Jojo

Barf · Post by **Barf** » Thu Oct 06, 2016 10:19 am

vickyg2003 wrote:Hmm something looks wrong with your file.

Protocol 99 99
Protocol Import only.

Vicky, you appear not to have read the context. The file is generated from a Lirc file by IrScrutinizer. At that point, information about the RM protocols is not present, but have to be manually entered, either im RM or otherwise. "Importonly" means exactly what the name suggests, also see the comments in the file. Background.

@jojo: So it is a problem with RM. As I said, I cannot reproduce ("see"?) the problem. Post the rmaster.err so that a we can analyze the problem.

jojo · Post by **jojo** » Thu Oct 06, 2016 10:41 am

Hi Barf,

Please find the rmmaster.err file here:
http://www.hifi-remote.com/forums/dload ... e_id=14225

Regards,
Jojo

jojo · Post by **jojo** » Thu Oct 06, 2016 11:22 am

Hi Barf,

I don't have any such problems with RemoteMasterv2.03build14.

Now I am able to generate a rv.bin. Though when I plug the .bin file to slingbox, it doesn't let me continue and tells me invalid custom bin file.
What am I missing?

Infact I have downloaded various rv.bin available on the slingbox website and am not able to plug it successfully. I must be missing something?

Regards,
Jojo

alanrichey · Post by **alanrichey** » Fri Oct 07, 2016 12:53 am

Unless you have a very old European manufactured Slingbox you should be using the PL BIN file.

Barf · Post by **Barf** » Fri Oct 07, 2016 1:17 am

jojo wrote:
I don't have any such problems with RemoteMasterv2.03build14.

That is good news! It means that

* it is a problem that was introduced since that version. (Also explains why I could not reproduce it.) Graham, can you have a look at it? The previously uploaded rmaster.err appears useful.

* You can use the old one in between.

you should be using the PL BIN file.

This is probably the solution to the second problem.

mdavej · Post by **mdavej** » Fri Oct 07, 2016 5:57 am

Most people should not be using any version past 2.03 14. Later ones support a few new remotes but also introduced several new bugs.

jojo · Post by **jojo** » Fri Oct 07, 2016 7:28 am

Hi Alan,

Thanks for the pointer.

Hi Barf,

Thanks a lot for the support.

I have been able to set up the custom remote.

Though some keys are picked up thrice. On pressing the arrow keys or volume keys. It is picked up thrice.

Am I missing something?

Regards,
Jojo

jojo · Post by **jojo** » Fri Oct 07, 2016 9:13 am

Hi Barf,

Using NEC1 protocol instead of NEC2 helped solve the issue.

Thanks a lot for all information provided to me.

Appreciate your support.

Regards,
Jojo

alanrichey · Post by **alanrichey** » Fri Oct 07, 2016 10:25 am

Just for future reference, the Slingbox system sends 3 copies of the iR Burst to ensure it's received. But some sensitive receivers will react to more than one burst. The latest PROTOCOLS.INI has a number of extra protocols (Including NEC), tweaked to set the repeat rate to zero. By default they are not shown but you can access them under the Options Menu in RM.

Barf · Post by **Barf** » Fri Oct 07, 2016 12:05 pm

For the record: the first Lirc file appears to be NEC1-like signals, just that the lead-in (the first gap and the following gap) was missing. The second one was a Lirc raw file. Such a file just one sequence, so there is no way to specify a repeat method. (Yes, Lirc is primitive

). So IrScrutinizer came up with the only reasonable conclusion: assumed that the (single) given sequence repeated. I.e., NEC2.