JP1 Remotes

Posted: **Thu Nov 11, 2010 2:31 pm**

Hi all,

I'm a newbie here, with a question that is jp1 related, but it's not about programming a jp1 remote.

I recently picked up a Blu-Ray player on eBay - it was a good deal, but came without a remote. I can play a movie without a

remote, but there is a firmware upgrade available that requires me to press the Enter key in order to install the upgrade.

Of course, assuming I can emulate that, I should be able to get the navigation keys working too.

I have built a serial IR transmitter for my computer, which works with WinLIRC. I know is working properly, because I found

a LIRC configuration for an RCA TV, and I was able to use WinLIRC to power an RCA TV on & off, adjust the volume up &

down, and switch channels up & down. I didn't test all the buttons.

My Blu-Ray player is Insignia NS-BRDVD3-CA. I have an RMDU file for the NS-BRDVD3. They are the same player - mine is the

Canadian version. They both use the same remote (BD003).

What I hope to do is use this info to come up with a WinLIRC configuration that will control the Blu-Ray player. If that

works, I could teach a learning remote. In the longer term, I hope to purchase a jp1 or jp1.x remote, and then my problem

will be solved.

Here's the RMDU file:
http://www.hifi-remote.com/forums/dload ... le_id=7419

What I've learned to this point is that the Blu-Ray player uses the NEC1 protocol, the device number is 133 and the sub-device number is 237.

With this info, I was able to use makehex.exe with the NEC1 irp file to generate the raw hex codes for all the functions

from 0 to 255. Here is an example, function 17 (which is the Enter key).

Device Code: 133.237 Function: 17
0000 006D 0022 0002 0157 00AC 0015 0041 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0689 0157 0056 0015 0E94

I thought I would be able to use the raw hex codes in WinLIRC, but now I see that WinLIRC use decimal numbers when it uses raw data codes. I read somewhere that the LSB is transmitted first.

How do I convert each of the 4 digit hex codes into the appropriate raw data decimal format? And is this the proper approach?

The RCA file that I used with WinLIRC used hex values for each function. I am thinking that this method would be more desirable than the raw data method.

My objective is to generate a WinLIRC file for the NS-BRDVD3 remote - i.e. just 1 device, not many, as above.

Any advice would be appreciated.

Thanks in advance. And I apologize for such a lengthy question, but I wanted to give examples.

Posted: **Thu Nov 11, 2010 3:50 pm**

Just in case this turns out to be impossible, you may not realize that you can add these codes to a JP1 remote without using a cable. Check out THIS thread which lists compatible JP1 remotes and a way to manually program all the commands.

Posted: **Fri Nov 12, 2010 6:29 pm**

OK, I took a crack at it, let me know if it works ...

Code: Select all

#
# this config file was manually generated
# by The Robman on Fri Nov 12 18:115:00 2010
#
# contributed by The Robman
#
# NEC1 device 133, sub-device 237
#
# brand: Insignia 
# model no. of remote control: ???
# devices being controlled by this remote: BluRay DVD Insignia NS-BRDVD3
#

begin remote

     name          NS-BRDVD3
     bits          16
     flags         SPACE_ENC|CONST_LENGTH
     eps           30
     aeps          100

     header        9000  4500
     one           570  1672
     zero          570   539
     ptrail        569
     repeat        9000  2250
     pre_data_bits 16
     pre_data      0xA1B7
     gap           108323
     toggle_bit    0

	begin codes
		0                   0x00000000000014EB
		1                   0x00000000000054AB
		2                   0x00000000000034CB
		3                   0x000000000000748B
		4                   0x0000000000000CF3
		5                   0x0000000000004CB3
		6                   0x0000000000002CD3
		7                   0x0000000000006C93
		8                   0x0000000000001CE3
		9                   0x0000000000005CA3
		open_close          0x000000000000649B
		power               0x000000000000609F
		search              0x000000000000A25D
		clear               0x00000000000002FD
		angle               0x000000000000E41B
		disc_menu           0x000000000000D02F
		popup_menu          0x00000000000030CF
		up_arrow            0x0000000000008877
		down_arrow          0x000000000000A857
		left_arrow          0x000000000000F00F
		right_arrow         0x000000000000C837
		enter               0x000000000000E817
		setup               0x000000000000B04F
		repeat              0x0000000000007C83
		repeat_a_b          0x000000000000FC3
		display             0x00000000000024DB
		pip                 0x0000000000000AF5
		resolution          0x00000000000042BD
		play_pause          0x00000000000058A7
		step                0x000000000000C43B
		fast_fwd            0x000000000000F87
		rewind              0x0000000000007887
		next                0x000000000000B847
		prev                0x00000000000038C7
		stop                0x0000000000009867
		zoom                0x0000000000003CC3
		audio               0x000000000000906F
		return              0x000000000000629D
		subtitle            0x00000000000050AF
		secondary_audio     0x0000000000008A75
		red_A               0x00000000000032CD
		green_B             0x000000000000B24D
		yellow_C            0x000000000000728D
		blue_D              0x000000000000F20D
		surround_mode       0x000000000000FD2
		audio_setup         0x000000000000708F
		fm_am               0x00000000000036C9
		mute                0x00000000000056A9
		audio_source        0x000000000000B649
		video_source        0x000000000000D629
		vol_down            0x00000000000006F9
		bass_on_off         0x0000000000006699
		vol_up              0x0000000000008679
		eq_mode             0x000000000000C639
	end codes

end remote

Posted: **Fri Nov 12, 2010 10:50 pm**

Hi Robman - YES - It does work!!!!

Thanks so much. I'll give you a more detailed report in the morning - I have to play now, and I'll probably be up quite late. Thanks again.

Posted: **Sat Nov 13, 2010 9:44 am**

I've been doing a lot of digging & reading since my first post in this thread, and along the way I stumbled across Vicky G's very excellent tutorial on infrared protocols, which is available here on this site. I would recommend this as a MUST READ for any newbies who are trying to do creative things with IR devices & remotes.

I was about to post this lirc file (which doesn't work) to get some pointers, but then I saw Robman's configuration, and I had to try it.

Code: Select all

# brand: Insignia
## model no. of remote control: BD003
## devices being controlled by this remote: Insignia NS-BRDVD3 Blu-Ray Player

begin remote
  name          BluRay
  bits          16
  flags         SPACE_ENC|CONST_LENGTH
  eps           30
  aeps          100
  header        9024  4512
  one           564  1622
  zero          564   564
  ptrail        564
  gap           43992
  pre_data      0x20 0x5E 0x48
  min_repeat    1
  toggle_bit    0

      begin codes
          open/close              0x85ED9B64
          power                   0x85ED9F60
          up                      0x85ED7788
          down                    0x85ED57A8
          left                    0x85ED0FF0
          right                   0x85ED37C8
          enter                   0x85ED17E8
          setup                   0x85ED4FB0
          stop                    0x85ED6798
          play/pause              0x85EDA757
      end codes
end remote

What I had done was put the device & subdevice plus the command & it's complement as the data string for each command. I used the timing info straight from Vicky G's tutorial. I also tried reversing one of the command strings.

The rmdu file has some fixed data, which I had put in as pre_data, but I see now that I had neglected to mention pre_data_bits.

So a couple of questions I still have - first, I don't see where your pre-data came from. I see your data strings contain the hex code plus its complement, but what about all the preceding zeroes? And how did you get the timing? I also don't see the device code or subdevice in your configuration.

Of course, I will still be doing more reading, and hopefully soon I will have a better understanding of all this.

The original remote is BD003.

I had to change some of the button names because WinLIRC gave me errors. Please don't consider this as a complaint - it is helping me to learn. And of course I am truly grateful for your efforts.

So, once again - Thanks. You are like a modern day Merlin, working your magic here.

Posted: **Sat Nov 13, 2010 11:30 am**

I'm glad my explanation of the signals helped you.

I had been studying signals here for a long, long time without a clue as to what people were telling me.

I can explain the predata

The NEC1 signal looks like this.
IRP notation: {38.4k,564}<1,-1|1,-3>(16,-8,D:8,S:8,F:8,~F:8,1,-78,(16,-4,1,-173)*)

All Signals are assumed to be LSB unless stated otherwise.

You reported that the device was 133.

133=85hex=10000101binary
LSB(10000101)=1010 0001 = A1hex

Subdevice = 237
237 = EDhex=1110 1101binary
LSB(11101101)=1011 0111 = B7 Hex

I don't know how the rest of the LIRC is figured out.

Posted: **Sat Nov 13, 2010 9:40 pm**

Thanks for the feedback, Vicky. (Great tutorial, BTW!) So the device code & subdevice code are there in the pre_data, I just didn't recognize it. One mystery solved.

As it turns out, not all of the functions are working - in particular the navigation keys and the enter key are not working. I went through all 256 possibilities tonight trying to test them.

Power works, open/close works, and this is what I tested last night, but actually, as it turns out, there isn't very much else working.

Just when I think I am starting to get a handle on this, then reality sets in.

Hey Vicky, I read about the red button comcast remotes in some of your posts, but what about the gray button ones - they are still jp1.x? There are lots of them on eBay, just want to make sure before I buy something.

And if anyone can shed some illumination on my current WinLIRC dilemna - i.e a few keys working, many not working, it's much appreciated.

Thanks.

Posted: **Sat Nov 13, 2010 10:28 pm**

We have two upgrades for this device and they are both the same arrow key codes and they match the hex that Rob prepared.

gadget89 wrote:Hey Vicky, I read about the red button comcast remotes in some of your posts, but what about the gray button ones - they are still jp1.x? There are lots of them on eBay, just want to make sure before I buy something.

The Gray button/On Demand remotes are JP1.2 remotes. I'm a JP1.2 fan, but with the Comcast you are much better off with the JP1.3 version, simply because it has so much more user memory.

Posted: **Sun Nov 14, 2010 7:00 am**

The Robman wrote: bits 16
...
pre_data_bits 16

gadget89 wrote:bits 16

Notice that bits is how many bits are allowed to vary between commands and pre_data_bits is how many bits before the varying bits are the same for every command.

gadget89 wrote:What I had done was put the device & subdevice plus the command & it's complement as the data string for each command.

That is OK. You can include non varying bits in with the varying bits. But only if you count them in with the varying bits. If you wanted all 32 bits together, you should have bits set to 32.

gadget89 wrote:pre_data 0x20 0x5E 0x48

I have no idea what that line was supposed to mean, given the strange format and no definition of pre_data_bits and all 32 bits together in each command's data.

gadget89 wrote:what about all the preceding zeroes?

The bits line tells lirc how many bits (at the least significant end) are valid. Lots of leading zeroes are typical in lirc files. They don't affect the number of bits in the signal.

gadget89 wrote:my current WinLIRC dilemna - i.e a few keys working, many not working

I don't even have a guess. Just to make sure we understand the question correctly, those are the symptoms when you use the file Rob posted?

Posted: **Sun Nov 14, 2010 8:32 am**

Thanks for your help. This is a great forum - everyone is so helpful.

Well that file was my first attempt, and it didn't work, but I wasn't really expecting it to.

With all the info I've gotten back, I'm getting a much clearer picture.

But yes, I was using the Robman's file. I had to edit it a little, because WinLIRC was giving an error loading the file.

Things like "right arrow" it doesn't like, but "right_arrow" is OK.

So I'm using his file, just edited enough so that WinLIRC is not complaining. When I first tested it, I only tested a couple of codes, power and open/close. But I was having problems with the mouse on that computer I'm testing with, so that's as far as I went. I was pretty optimistic at that point anyways - it seemed like it was working.

Posted: **Sun Nov 14, 2010 8:41 am**

Given that information, I'd get rid of all the special characters (spaces, /, _, ...) from the button names. But I'd also start from 0 and work my way down to see if the file stops working at a specific line.

Posted: **Sun Nov 14, 2010 12:21 pm**

I just updated my earlier post to only use "_" as a special character, I removed the spaces and the "/"s

Posted: **Sun Nov 14, 2010 12:59 pm**

OK, here is a copy of my working LIRC config:

Code: Select all

#

# this config file was manually generated

# by The Robman on Fri Nov 12 18:115:00 2010

#

# contributed by The Robman

#

# NEC1 device 133, sub-device 237

#

# brand: Insignia

# model no. of remote control: ???

# devices being controlled by this remote: BluRay DVD Insignia NS-BRDVD3

#




begin remote


     name          NS-BRDVD3

     bits          16

     flags         SPACE_ENC|CONST_LENGTH

     eps           30

     aeps          100

     header        9000  4500

     one           570  1672

     zero          570   539

     ptrail        569

     repeat        9000  2250

     pre_data_bits 16

     pre_data      0xA1B7

     gap           108323

     toggle_bit    0


   begin codes


      test1		   0x000000000000F00F

      test2                0x000000000000F10E

      test3                0x000000000000F20D

      test4                0x000000000000F30C

      test5                0x000000000000F40B

      test6                0x000000000000F50A

      test7                0x000000000000F609

      test8                0x000000000000F708

      test9                0x000000000000F807

      test10               0x000000000000F906

      test11               0x000000000000FA05

      test12               0x000000000000FB04

      test13               0x000000000000FC03

      test14               0x000000000000FD02

      test15               0x000000000000FE01

      test16               0x000000000000FF00



#      0                   0x00000000000014EB

#      1                   0x00000000000054AB

#      2                   0x00000000000034CB

#      3                   0x000000000000748B

#      4                   0x0000000000000CF3

#      5                   0x0000000000004CB3

#      6                   0x0000000000002CD3

#      7                   0x0000000000006C93

#      8                   0x0000000000001CE3

#      9                   0x0000000000005CA3


      open_close          0x000000000000649B

      power               0x000000000000609F

      search              0x000000000000A25D

#      clear               0x00000000000002FD

#      angle               0x000000000000E41B

#      disc menu           0x000000000000D02F

#      popup menu          0x00000000000030CF

      up_arrow            0x0000000000008877

      down_arrow          0x000000000000A857

      left_arrow          0x000000000000F00F

      right_arrow         0x000000000000C837

      enter               0x000000000000E817

      setup               0x000000000000B04F

#      repeat              0x0000000000007C83

#      repeat a-b          0x000000000000FC3

#      display             0x00000000000024DB

#      pip                 0x0000000000000AF5

#      resolution          0x00000000000042BD

      play_pause          0x00000000000058A7

#      step                0x000000000000C43B

#      fast fwd            0x000000000000F87

#      rewind              0x0000000000007887

      next                0x000000000000B847

      prev                0x00000000000038C7

      stop                0x0000000000009867

#      zoom                0x0000000000003CC3

#      audio               0x000000000000906F

      return              0x000000000000629D

#      subtitle            0x00000000000050AF

#      secondary audio     0x0000000000008A75

#      red A               0x00000000000032CD

#      green B             0x000000000000B24D

#      yellow C            0x000000000000728D

#      blue D              0x000000000000F20D

#      surround mode       0x000000000000FD2

#      audio setup         0x000000000000708F

#      fm/am               0x00000000000036C9

#      mute                0x00000000000056A9

#      audio source        0x000000000000B649

#      video source        0x000000000000D629

      vol_dn                0x00000000000006F9

#      bass on/off         0x0000000000006699

      vol_up                0x0000000000008679

#      eq mode             0x000000000000C639

   end codes


end remote

As you can see, I've commented out a lot of the functions, and I'm working with a very basic set. WinLIRC loads this one without any problem. With the test buttons test1 to test16, I started at:

test1 0x00000000000000FF
to test16 0x0000000000000FF0

testing 16 functions at a time. Next,

test1 0x00000000000010EF
to test16 0x0000000000001FE0

then testing these 16 functions, until I got to where they are now.

On the Blu-Ray, I had my usb drive plugged in with the firmware upgrade, so on the screen, there is a message that says select OK or cancel, then press Enter. The cancel button is already selected. If I found the enter key, the upgrade would have been cancelled, and if I found the left key, then OK would have been selected. But I went all the way through all the functions, and didn't get results. I did find the power button on the way through the list, as well as open/close. At least one other button showed a "prohibited" message on screen, with red circle & slash. I did all that while the hockey game was on last night, (switching back & forth) and haven't done anything further.

Posted: **Sun Nov 21, 2010 10:45 am**

OK, here's an update.

I purchased a pair of Comcast 1067ABC3 remotes on eBay yesterday, so they should arrive later this week. I scoured the shops in my town for the RCA remote (RCRP05B) but couldn't locate one, so this seemed to be my best option.

I'm hoping they'll have the JP1 connector, or at least the holes, but even if they don't, that remote should work with the advanced codes that mdavej directed me to in his post.

I'm still experimenting with winlirc - I'm trying to send some raw codes, although at the moment I'm getting errors with the config file. I'll play around a little, and then post my results.

Once again, I'd like to thank all the wonderful folks on this forum who've been a great help in my experiments.

I expect I will probably have more questions in the future. I plan to build the JP1 interface cable so that I can have my way with these remotes.

Hopefully, as I learn more, I can repay the favor and help some future newbies out.

Posted: **Sun Nov 21, 2010 12:49 pm**

gadget89 wrote:OK, here's an update.

I purchased a pair of Comcast 1067ABC3 remotes on eBay yesterday, so they should arrive later this week. I scoured the shops in my town for the RCA remote (RCRP05B) but couldn't locate one, so this seemed to be my best option.

I'm hoping they'll have the JP1 connector, or at least the holes, but even if they don't, that remote should work with the advanced codes that mdavej directed me to in his post.

With this particular signal, Nec1 133.237, you won't be able to do manual programming. AFAIK, there isn't any Nec1 or Nec1 Combo code in any Comcast remote, capable of sending that signal. So you'll need a custom code, and the only way to get that is with a cable.

I'm still experimenting with winlirc - I'm trying to send some raw codes, although at the moment I'm getting errors with the config file. I'll play around a little, and then post my results.

If I understand your previous results correctly, then the codes that are uncommented are the codes that you did find. And the codes that you did find, matched the codes in Rob's WinLirc Attempt. That is promising.

Many of the things that you found not to work, like A,B,C,D,angle, disc menu, and subtitles may not work if the playback media doesn't support these features. Other features may not work if you don't have the right equipment attached. Things like step will only work when your already paused. The number buttons, only work after the SEARCH button has been pressed.

The 2 things that I'm surprised you didn't find were FFW and REW. I can't imagine those keys not being present on a DVD player.

I think the next order of business would be to see what the user manual has to say about the functions that don't work.

Have you seen a picture of the OEM remote in the documentation? Does it have all the keys on it like PIP and Zoom? Those features are usually only available in high-end equipment.

JP1 Remotes

Insignia NS-BRDVD3-CA Blu-Ray

Insignia NS-BRDVD3-CA Blu-Ray

Insignia NS-BRDVD3 working!!!

Insignia NS-BRDVD3 working!!!

NS-BRDVD3 - only a few keys work ....

Re: NS-BRDVD3 - only a few keys work ....

Insignia NS-BRDVD .....