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.
vickyg2003 wrote:Rob, is there a 2 byte limitation on function hex?
A limitation on who's part?.
Keymaster, RemoteMaster, RMIR?
I've been fiddling with those mouse commands looking for a pattern. I do see some columns of 4 bits that are all the same, and the final bit being a parity bit, but I can't find any pattern. Its such a few commands.
I tried to use the commands on my NUC but it doesn't show any infrared devices, at the same time, I went into the bios and its enabled and I have a choice of generic, xbox or RC6 commands in the bios.....
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
The first 8 bits are fixed, the next 5 bits are variable, the next 8 bits are fixed (at zero), the next 8 are variable, the final 8 bits are mostly fixed at zero, but for 3 buttons (colon, comma and right square bracket) there are 2 bits that might be set.
So, what you could do is, treat the first 8 bits as the 1st device code, the 8-bits of zeroes could be the 2nd device code and the last 8 bits could be the 3rd device code. You could use 2 variable bytes where the 2nd byte populates that 8-bit variable portion. 5 bits of the first variable byte can populate the 5-bit variable portion. That leaves 3 bits spare, which you can use to populate the 2 bits on the last byte that sometimes get set.
The benefit of doing all that executor logic is that you would have 2 variable bytes rather than 4, saving you 2 bytes per button. But the question is, will the executor use up more bytes than you save?
Rob www.hifi-remote.com Please don't PM me with remote questions, post them in the forums so all the experts can help!
I do see where there are 4 1111 or 0000 in a row that corresponds to a direction.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
vickyg2003 wrote:I do see where there are 4 1111 or 0000 in a row that corresponds to a direction.
Yeah, I just noticed those too. So, once you handle the 8-bit device code, you have 26 variable bits, which would require 4 variable bytes. If you can reduce it to 24 bits or less, you can use 3 variable bytes. So, if you could handle those 4 bits using 1 or 2 bits, you would be down to 23 or 24 bits.
Rob www.hifi-remote.com Please don't PM me with remote questions, post them in the forums so all the experts can help!
The sad thing is, I'm a huge pack rat, and last year forced myself to clear off a shelf in my bookcase. I threw out all the books on DOS based programming, including how to program for a mouse..... It seems to me that some of those bytes are speed in the various X Y direction. If I knew the specs we could probably simplify it by making them the same speed in all directions.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
00001000 01111 1111010 0000000 00 ~10000 ; UP
00001000 11110 0000110 0000000 00 00001 ; Down
Lefts have 1111
00001000 01000 1111010 1111010 00 10111 ; Left UP
00001000 00001 0000000 1111011 00 11110 ; Left
00001000 10000 0000111 1111000 00 01111 ; Left Down
Rights have 0000
00001000 01110 1111011 0000101 00 10001 ; Right Up
00001000 01111 0000000 0000101 00 10000 ; Right
00001000 10000 0000101 0000101 00 01111 ; RightDown;
Ups have 1111s
00001000 01111 1111010 0000000 00 10000 ; UP
00001000 01000 1111010 1111010 00 10111 ; Left UP
00001000 01110 1111011 0000101 00 10001 ; Right Up
Downs have 0000s
00001000 11110 0000110 0000000 00 00001 ; Down
00001000 10000 0000111 1111000 00 01111 ; Left Down
00001000 10000 0000101 0000101 00 01111 ; RightDown;
Clicks With Mouse buttons
00001000 00011 0000000 0000000 01 11100 ; Left Click
00001000 00101 0000000 0000000 10 11010 ; Right Cick
There are 2 bits that appear to indicate which button are pressed.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
I think the first 5 bits (counting the bits from left to right) are a checksum of the rest of the data, but I haven't spotted the formula yet. Bits 1 and 10 are the same.
Rob www.hifi-remote.com Please don't PM me with remote questions, post them in the forums so all the experts can help!
I have added the Mouse Commands to my MCE zip file, so now the Keyboard and Mouse buttons as well as the regular MCE upgrades are sitting there waiting for someone to test them.
I haven't seen jriker1, the OP, around lately. I PM'd him when I finished the KeyBoard commands, but he hasn't picked that up. It could be the weather,
Those hurricane's have been impacting lots of people . I hope I didn't do this for nothing.
I can't figure out why my NUC's infrared device isn't showing up, or I'd test it myself.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
vickyg2003 wrote:I haven't seen jriker1, the OP, around lately. I PM'd him when I finished the KeyBoard commands, but he hasn't picked that up. It could be the weather, those hurricane's have been impacting lots of people.
Looks like he's in the Chicago area, so I don't think it's hurricane related. I just emailed him (and copied 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!
Amazing work Vicky, Barf and Rob. I have no MCE IR dongle anymore to test these, but I can fill in a few gaps. Here are some additional codes I found in the keycodes table below that could be added to your keyboard upgrade (OBC values in hex. I don't know what to use for byte 2 (complement?)). Nobody will probably ever use these, so it's just as well if they are not added. Just wanted to post them for completeness if it ever comes up.
Just like the mice commands there is some sort of checksummy thingy in those codes that i don't know what they mean. But maybe some day.....
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Hey Vicky, while answering Graham's questions in your other thread, I discovered an old spreadsheet that I put together that does the conversion to binary for you, check it out...
The Robman wrote:Hey Vicky, while answering Graham's questions in your other thread, I discovered an old spreadsheet that I put together that does the conversion to binary for you, check it out...
I'll take a look at this, but typically I leave this part up to someone else, as my dyslexia really makes this part unpleasantly hard.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.