SK-7551 Keyboard and comcast urc-1067

As keyboards are such a pain to get replicate using a remote, they get their own forum. Hopefully having all the posts in one place will make it easier to find the solution.

Moderator: Moderators

Post Reply
crosstalk
Posts: 45
Joined: Sun Apr 30, 2006 6:43 pm
Location: PA

SK-7551 Keyboard and comcast urc-1067

Post by crosstalk »

Hello. I am trying to use the device upgrade SK7551_KM with the RM program. I am getting an error that the manual protocol is incompatible with the comcast urc-1067.

Should I try the KM spreadsheet or is this just not going to work due to the particular processor in the 1067 remote?

Thanks,
Rich
The Robman
Site Owner
Posts: 21884
Joined: Fri Aug 01, 2003 9:37 am
Location: Chicago, IL
Contact:

Post by The Robman »

Do you have a link for the file that you're talking about?
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
crosstalk
Posts: 45
Joined: Sun Apr 30, 2006 6:43 pm
Location: PA

Post by crosstalk »

The file is found at:
JP1 Remotes Forum Index -> Download Database -> JP1 File Section -> Device Upgrades -> Keyboards -> Silitek SK-7551
http://www.hifi-remote.com/forums/dload ... le_id=2381

I am using this device upgrade because it can send a make and break command, which better emulates the real keyboard. I was using a make-only device upgrade successfully for a long time until I upgraded my linux kernel and x server. Now I get repeating characters with the make-only device upgrade.

Thanks,
Rich
crosstalk
Posts: 45
Joined: Sun Apr 30, 2006 6:43 pm
Location: PA

Post by crosstalk »

Although I wanted to use the comcast remote, I decided to program my urc-8811 with the device upgrade linked above. No problem getting this remote to use the manual protocol. Although it initially seemed like this device upgrade solved my repeating key problem, it is not completely solved. I still get occasional repeats.

I noticed in a post from a few years ago that the author of the protocol modified it to send a burst length of 3. Does any one know how to change this? Would changing this likely solve my problem?

Thanks,
Rich
Post Reply