JP1 Remotes

The program for PIC12F629 has been completed, and tested.
This program receives a NEC Protocol with Device ID 192, and send it in real time, but updated to Device ID 0.
So, you must program your JP1 remote with the original codes but in Device ID 192 instead of 0.
The PIC chip will be connected ...

Decided. I am going to build a program for PIC12F629, to receive a NEC Protocol with Device ID 192, and send it in real time, but updated to Device ID 0.
So, I will program my JP1 remote with the original codes but in Device ID 192 instead of 0.
The PIC chip will be connected inside the device, in ...

¡¡¡Oh my God!!!
This weekend, my wife gave me a present: It is a HD DVB, USB Media player and recorder with Timeshift and DVD combo set.
Do you guess?
YES. It is a IR protocol NEC Device ID 0.
This is my third device in the same room with this protocol.
THIS IS A NIGHTMARE.
My 14 inches TV, the HDMI ...

Since he has a laptop he'll probably need to build a JP1 usb cable.

A quick search at newegg showed only one pcmcia parallel port card http://www.newegg.com/Product/Product.aspx?Item=N82E16839158008 and it was 50 bucks. Couldn't even say for sure if that would work either.
I have bought a $17 ...

Does anyone know if the JP1 works ok with PCMICA cards?
I have bought a $17 PCMCIA Parallel card and it works with my URC-8910 JP1 remote.
Because there are a lot of cards with different chips, look for a card with the MCS9805 chip inside.
This is the link for the card that I have bought:
http ...

I will try this improvements.
But, why to use W6? can I save memory? What is W6 and where must be defined?
Thank you for the idea of making the hdmi button repeatable. Just one comment: I think the last instruction must be AND R29,#FE instead of OR.

Thank you very much to everybody.
I fixed this problem without modify anything in the devices.
The only things I used to solve this problem was JP1 protocols, my brain, and your unvaluable help.
What I did was to build two NEC1 new protocols, one of them for the TV and another one for the HDMI ...

It worked.
I had to modify the protocol a bit, but finally it worked.
This is the assembler that I used:
REMOTE S3C8+
DB 41H,8DH ;38.1 kHz 31%
DB 31H
JR start
DB E5H ;pf0: 11001111=devs,cmds,dev-cmd,OffAsTotal
DB 46H ;pf1: 01000111= Not-RptHeld,LI-same,1on-LO
DB 08H ;pd00: DevBits1=8
DB ...

Thank you everybody.
I think that I get it.
What I want with this, is sending commands to a HDMI-MATRIX which is NEC1 device 0, but without changing anything in the TV, which unfortunately is NEC1 device 0 as well.
To do that, I am going to use NEC1 device 0 command 85H before and after the real ...

I want a NEC1 protocol that send a fixed command before the command of the button pressed, and another one fixed command after that.
Total 3 commands: Fixed prev-command, normal button command, and fixed post-command. Is like a macro, but since all button commands require this fixed command before ...

I want a NEC1 protocol that send a fixed command before the command of the button pressed, and another one fixed command after that.
Total 3 commands: Fixed prev-command, normal button command, and fixed post-command. Is like a macro, but since all button commands require this fixed command before ...

Changing the first two bytes is the correct approach, but the NEC executor is huge, so if it were me, I would produce a scaled down version that just produced the NEC1 signal, at 56kHz, with no other options.
I agree with you.
I will use the complete version of the NEC executor just to test, and ...

Changing the first two bytes is the correct approach, but the NEC executor is huge, so if it were me, I would produce a scaled down version that just produced the NEC1 signal, at 56kHz, with no other options.
I agree with you.
I will use the complete version of the NEC executor just to test, and ...

What is an executor?
It is a new protocol?
in assembler may be?
You will be creating a new protocol when you modify your TV. Currently it responds to NEC1, which has a frequency of 38kHz, so when you change the frequency to (let's say) 56 kHz, you will no longer be using the NEC1 protocol (and ...

I understand.
Where is there any documentation about executors, and/or assembly language for the s3c80+?
Since I am a programmer with experience on assembly programming, I would like to learn about this.
Thanks.