Chicony keyboard?
Moderator: Moderators
-
rocketkarl
- Posts: 13
- Joined: Wed Oct 08, 2003 1:12 pm
- Location: Houston, TX
Chicony keyboard?
Anyone programmed the chicony wireless keyboard/mouse onto their remote? I don't see any references to it here or at yahoo jp1.
-
jon_armstrong
- Expert
- Posts: 1238
- Joined: Sun Aug 03, 2003 9:14 pm
- Location: R.I.P. 3/25/2005
- Contact:
First are you SURE it is IR and not RF? If so learn the numerals to your OFA remote and try them. Make sure you are using the latest version of IR and deocodeIR.dll in your windows sytem directory.
Use a quick but firm tap for each key and release.
Does IR decode the signals?
If those work, post them in the files|dianosis area at the JP1 Yahoo group and tell us and I am sure one of us will take a look.
Use a quick but firm tap for each key and release.
Does IR decode the signals?
If those work, post them in the files|dianosis area at the JP1 Yahoo group and tell us and I am sure one of us will take a look.
-Jon
-
rocketkarl
- Posts: 13
- Joined: Wed Oct 08, 2003 1:12 pm
- Location: Houston, TX
Yes, its IR. I've learned several of the buttons, but am out of memory, until I get my JP1 cable, and can start replacing all my learned and moved keys (on all devices, not just PC) with new created devices in ROM.
I was just curious if others had had luck with IR decoding the learned buttons for this keyboard, and also how others chose to lay out the keys.
I was just curious if others had had luck with IR decoding the learned buttons for this keyboard, and also how others chose to lay out the keys.
-
The Robman
- Site Owner
- Posts: 21930
- Joined: Fri Aug 01, 2003 9:37 am
- Location: Chicago, IL
- Contact:
You're putting the cart before the horse. Wait for your JP1 cable to arrive and then look at the learned commands. Normally speaking I'd say the chances of it being a known protocol are high, but IR keyboards can be tricky, but having said that we've already been put through the paces already by the Airboard, so the experts know what to look for.
If your keyboard uses an unknown protocol, chances are Jon will be back here looking for particulars to create a custom protocol just for you.
If your keyboard uses an unknown protocol, chances are Jon will be back here looking for particulars to create a custom protocol just for you.
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
-
rocketkarl
- Posts: 13
- Joined: Wed Oct 08, 2003 1:12 pm
- Location: Houston, TX
I forgot about this thread, and posted my results over in the General forum. Basically, my IR file, Chicony.txt is in the diagnostic file section at Yahoo JP1. In the learned tab, everything marked CD is from the keyboard. I will try fresh batteries in both remotes tonight, and see whether I get a better lock on the protocals.
OFA URC 8910
-
jon_armstrong
- Expert
- Posts: 1238
- Joined: Sun Aug 03, 2003 9:14 pm
- Location: R.I.P. 3/25/2005
- Contact:
I created a prototype device upgrade that has only the key down commands. Usually that works fine with keyboards. It is posted back in diagniostics under Chicony KB-KM.txt. You will need to open in KM Master and copy both the Protocol AND device upgrade into your remote and assign CBL_1999 in the General Tab.
The only commands not on here are whatever was on FWD and REW. Those commands look quite different. Could you please learn them again and post them. To learn KB commands you need to start the learn (rapidly flashing LED) and then a quick press AND release of the key. Just a quick hard tap.
The rest of the keys are in the same place. Please let me know how this works.
The only commands not on here are whatever was on FWD and REW. Those commands look quite different. Could you please learn them again and post them. To learn KB commands you need to start the learn (rapidly flashing LED) and then a quick press AND release of the key. Just a quick hard tap.
The rest of the keys are in the same place. Please let me know how this works.
-Jon
-
rocketkarl
- Posts: 13
- Joined: Wed Oct 08, 2003 1:12 pm
- Location: Houston, TX
-
rocketkarl
- Posts: 13
- Joined: Wed Oct 08, 2003 1:12 pm
- Location: Houston, TX
Most of what I've seen in JP1 stuff is great, and I can see and appreciate how much time and effort went into it all. But how you came up with those protocals from my IRdump - well, that appears to be magic! Thank you!
Almost all the buttons worked perfectly with your protocol. The only 2 that didn't (besides those 2 mouse buttons that were odd) were the ALT (menu) & window menu (guide) keys. I re-learned them (with fresh batteries) to the remote, along with HOME (frew), END (fwd), and a few more mouse movements: up (play), left (rec), right (pause), stop (down), left button (frew), right button (ffwd). I posted these in the diagnostic area as Chicony_IR2.txt. I also posted a modified version of your Chicony_KB_KM.txt file, with buttons relabeled appropriately.
I can't tell from the IR learned info, how to pick off the right OBC's to use for these other buttons. The OBC's that it comes up with don't work - at least not with that protocol. Does that mean this KB uses a combo-protocol of sorts?
Thanks again for your wizardry!
Almost all the buttons worked perfectly with your protocol. The only 2 that didn't (besides those 2 mouse buttons that were odd) were the ALT (menu) & window menu (guide) keys. I re-learned them (with fresh batteries) to the remote, along with HOME (frew), END (fwd), and a few more mouse movements: up (play), left (rec), right (pause), stop (down), left button (frew), right button (ffwd). I posted these in the diagnostic area as Chicony_IR2.txt. I also posted a modified version of your Chicony_KB_KM.txt file, with buttons relabeled appropriately.
I can't tell from the IR learned info, how to pick off the right OBC's to use for these other buttons. The OBC's that it comes up with don't work - at least not with that protocol. Does that mean this KB uses a combo-protocol of sorts?
Thanks again for your wizardry!
OFA URC 8910
-
jon_armstrong
- Expert
- Posts: 1238
- Joined: Sun Aug 03, 2003 9:14 pm
- Location: R.I.P. 3/25/2005
- Contact:
It may be useful to cover keyboard basics. Each key has two commands DOWN and UP. There is only one "a" key. "A" is shift-"a" to do a shift anything; the command sequence is shift-down, a-down, a-up, and shift-up for a total of 4 keystrokes. ctrl-alt-delete would be ctrl-down, alt-down, del-down, del up, alt-up and ctrl-up. Since the device being controlled generally executes when del-down is sent, the rest of the commands are moot.
To get the UP command, you will need to create a second device upgrade but you need only change the device 1 setting in KM Master| setup tab from 1 to 0 in Cell C9. Change it's name to CBL_1998 or something different. You will also need to copy this device upgrade to IR but the protocol is the same for both so you only need one copy.
Perhaps this explains why the Alt key appears not to work. For the Alt key make a macro for the compound key the sequence as described above.
I think the Windows Menu key needs an UP command issued after the Down command. You will need to create a Macro for the Windows menu key that is Windows Menu Key DOWN | Windows Menu Key UP, and that should make it work. I have updated the added some keys and updated the Protocol the KM Master file just posted in the diagnosis section Chicony_KB_KM.txt. This new protocol shortens the lead out time to allow for the proper interval between commands using a macro.
To get the UP command, you will need to create a second device upgrade but you need only change the device 1 setting in KM Master| setup tab from 1 to 0 in Cell C9. Change it's name to CBL_1998 or something different. You will also need to copy this device upgrade to IR but the protocol is the same for both so you only need one copy.
Perhaps this explains why the Alt key appears not to work. For the Alt key make a macro for the compound key the sequence as described above.
I think the Windows Menu key needs an UP command issued after the Down command. You will need to create a Macro for the Windows menu key that is Windows Menu Key DOWN | Windows Menu Key UP, and that should make it work. I have updated the added some keys and updated the Protocol the KM Master file just posted in the diagnosis section Chicony_KB_KM.txt. This new protocol shortens the lead out time to allow for the proper interval between commands using a macro.
-Jon
-
digitalcujo
- Posts: 6
- Joined: Thu Nov 04, 2004 1:12 am
chicony IR keyboard debug help
I learned how to get my radio-shack remote to learn from the Chicony IR keyboard. The remote can now send the learned keyboard signals successfully, but as many others have mentioned, I ran out of memory quickly. I’m currently stuck trying to get the JP1 software to load the chicony IR keyboard protocol in a format that the receiver with listen to.
Here are the steps I took:
1) I downloaded the IR software and KM spreadsheet and loaded the following file into the spreadsheet software…
https://www.hifi-remote.com/forums/dload ... ile_id=304
2) Within the spreadsheet I mapped the “cable” buttons to the learned keys, and loaded them up into the remote as cable “1999”.
3) When I try to send the signals from the remote, the IR port doesn’t respond at all to any keys.
4) To make sure I’m doing the whole process correctly, I learned the volume control from my sony TV remote, and then re-mapped the learned volume button to the cable button “zero” in IR software, and the TV does respond to my re-mapped key. This experiment tells me that I’m going through most of the process successfully.
I’m not sure how to proceed, so I posted the remotes memory dump to the diagnosis area, and I was hoping one of you could point me in the right direction.
1. Device: ir keyboard
2. Type of device: Chicony kb-0005
3. Remote model: learning remote: radioshack 15-2115
4. JP1 user? yes
5. Still have original remote? yup, I have the original ir keyboard.
6. Checked Yahoo file section? yes, used: Chicony_KB-KM3.txt
7. Checked Pronto file section (at R/C)? no
Diagnosis File: irchicony_chicony.txt
Everything in the "SAT" section is learned from the keyboard.
Here are the steps I took:
1) I downloaded the IR software and KM spreadsheet and loaded the following file into the spreadsheet software…
https://www.hifi-remote.com/forums/dload ... ile_id=304
2) Within the spreadsheet I mapped the “cable” buttons to the learned keys, and loaded them up into the remote as cable “1999”.
3) When I try to send the signals from the remote, the IR port doesn’t respond at all to any keys.
4) To make sure I’m doing the whole process correctly, I learned the volume control from my sony TV remote, and then re-mapped the learned volume button to the cable button “zero” in IR software, and the TV does respond to my re-mapped key. This experiment tells me that I’m going through most of the process successfully.
I’m not sure how to proceed, so I posted the remotes memory dump to the diagnosis area, and I was hoping one of you could point me in the right direction.
1. Device: ir keyboard
2. Type of device: Chicony kb-0005
3. Remote model: learning remote: radioshack 15-2115
4. JP1 user? yes
5. Still have original remote? yup, I have the original ir keyboard.
6. Checked Yahoo file section? yes, used: Chicony_KB-KM3.txt
7. Checked Pronto file section (at R/C)? no
Diagnosis File: irchicony_chicony.txt
Everything in the "SAT" section is learned from the keyboard.
Please also post a copy of the IR file you are using that has the device and protocol upgrades installed, so that we can see that you did that correctly.
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
-
Mark Pierson
- Expert
- Posts: 3017
- Joined: Sun Aug 03, 2003 12:13 am
- Location: Connecticut, USA
- Contact:
Re: chicony IR keyboard debug help
You lost me with this comment. Are you saying that you used the Cable device type with a setup code of 1999 (which is what the upgrade is already set for)? And what do you mean by mapped buttons to the learned keys?digitalcujo wrote:2) Within the spreadsheet I mapped the “cable” buttons to the learned keys, and loaded them up into the remote as cable “1999”.
When you opened the upgrade in KM, did you also select the proper remote to match your model on the Setup sheet (the upgrade is for a URC-9910)?
Mark
-
digitalcujo
- Posts: 6
- Joined: Thu Nov 04, 2004 1:12 am
thanks for the responses!
I uploaded the IR file to http://groups.yahoo.com/group/jp1/files ... hicony.txt
In my first post I was trying to say that the chicony device code I downloaded from the JP1 website changes the default device type in the spreadsheet to "cable" and setup code to "1999". I also made sure that I changed the remote type in cell C:2 to my remote type 15-2117/15-2116. After I copied the upgrade code and protocol code to the IR program and then uploaded it to the remote, my remote shows that shows the setup code for cable is set to 1999 in the LCD display.
As for my comment about "mapped buttons to the learned keys", I misspoke about the learned keys. I ment that I made sure that the remote buttons were correctly mapped to functions in the "buttons" worksheet.
here is the "setup" worksheet C2:C23 (the only part I changed is the remote type):
Remote: 15-2117 / 15-2116
Device Type: Cable
Setup Code: 1999
Button Codes: OBC
SURR = Select: NO
Protocol Name: Manual Settings
Device1: 1
Device2:
Device3:
Raw Fixed Data:
Protocol ID: 01 77
Fixed Data: 80
Manual Settings
PID:
2nd Cmd Byte: None
Signal Style: LSB
Bits/Dev: 8
Bits/Cmd: 8
I uploaded the IR file to http://groups.yahoo.com/group/jp1/files ... hicony.txt
In my first post I was trying to say that the chicony device code I downloaded from the JP1 website changes the default device type in the spreadsheet to "cable" and setup code to "1999". I also made sure that I changed the remote type in cell C:2 to my remote type 15-2117/15-2116. After I copied the upgrade code and protocol code to the IR program and then uploaded it to the remote, my remote shows that shows the setup code for cable is set to 1999 in the LCD display.
As for my comment about "mapped buttons to the learned keys", I misspoke about the learned keys. I ment that I made sure that the remote buttons were correctly mapped to functions in the "buttons" worksheet.
here is the "setup" worksheet C2:C23 (the only part I changed is the remote type):
Remote: 15-2117 / 15-2116
Device Type: Cable
Setup Code: 1999
Button Codes: OBC
SURR = Select: NO
Protocol Name: Manual Settings
Device1: 1
Device2:
Device3:
Raw Fixed Data:
Protocol ID: 01 77
Fixed Data: 80
Manual Settings
PID:
2nd Cmd Byte: None
Signal Style: LSB
Bits/Dev: 8
Bits/Cmd: 8
-
digitalcujo
- Posts: 6
- Joined: Thu Nov 04, 2004 1:12 am
opps, I forgot to mention the URL of the protocol upgrades:
https://www.hifi-remote.com/forums/dload ... ile_id=304
https://www.hifi-remote.com/forums/dload ... ile_id=304
-
digitalcujo
- Posts: 6
- Joined: Thu Nov 04, 2004 1:12 am
Update: This weekend I was able to download the upgrade code for my cable box (motorola DCT 2000) and program my remote with it (via JP1). Since this upgrade work flawlessly on my remote, I know that I’m on the right track as far as using the IR.exe/KM to program my remote with upgrade code. This leads me to think that something in the chicony protocol isn't working with my model of IR keyboard.
How do I go about decoding the learned codes to figure out how the difference between the learned code and upgrade code? Does anyone have a good example thread/website that I could learn from?
thanks in advanced.
How do I go about decoding the learned codes to figure out how the difference between the learned code and upgrade code? Does anyone have a good example thread/website that I could learn from?
thanks in advanced.