Generic HID

[specter333]

It dawned on me why we are seeing different keys working on our remotes. It's a universal remote, duh , we don't have the same codes programmed. Sometimes the most obvious things just blow right by me.

Anyway, I spent the last few hours trying different codes to see which has the most active keys. I've got to get a life.

Code 3246 on the aux button is the best I've found so far. All of the keys above the mouse pad work as well as quite a few below. The only ones that don't generate an event in EG are;

The big annoying green button.
The four media keys over the number pad.
The * and # keys.
Last, Connect and DVD Menu.

Volume and mute keys generate events but always temporarily takes the remote to the TV page and always the same event no matter what you are controlling. Seems to be built into the remote this way, I can't change it.

Enter the code by pressing and holding the aux button and punch in the numbers. I haven't tried to see if the code will work on the TV or Cab pages yet. According to the instructions the keys that aren't being seen should be able to learn from other remotes. According to about a dozen other forums I been to that's just BS. When you send IR to it, it just locks up. The batteries have to come out to get it going again.

One Easter Egg type thing I discovered. When you push the Connect then the Setup Menu keys the four arrow keys become Keyboard arrow keys and the Ok key becomes Return although they still send their USB-UIRT code too. Push Aux again to get back to normal mode.

[level20peon]

Wow, let me try to handle this huge amount of quotes:

Note: the "not mappable" hasn't got to do anything with EventGhost primarily but with the OS support. So if there is a button marked as "Not mappable" it doesn't trigger an action inside the OS with its native drivers if you DON'T use EventGhost.

"Not mappable at all" INCLUDES EventGhost.

Sorry, I'm not certain I'm understanding this. I'm guessing there are three items were looking at here.

Not Mappable = Seen by EG as another device, such as the number keys.
Mappable = Seen only as event by EG that can be assigned to an action.
Not Seen = Not seen by EG or by OS.

Is that correct?

I used the term "Not Mappable" for buttons that don't work "out-of-the-box" in the respective Operating System if you use an application which is able to use a HID-device like MediaPortal for example.
EventGhost can map ANY button in ANY case (any OS) except the "Not Mappable at all in RF-Mode" marked button AND the number-keys.

By the way, those are all mappable with the USB-UIRT, not through the RF receiver.
[...]
What I mean is the remote transmits rf when using the PC mode and ir when using the TV, Aux and Sat modes (mostly). When in PC mode EG sees the number keys and transport keys as keystrokes, probably as a HID device.[...]

So you imply to switch modes in order to reprogramm the keypad ? This would be possible but not quite comfortable

I bet the DVD menu and Last keys are being intercepted by the OS and the connect key never makes it past the usb dongle.

"DVD menu" is mappable by EG.

It's a little confusing since EG sees different keys depending on which "Page" (I guess you would call it) of the remote your using. When I get some time I'll map out all for page keys and post the results.

Well there is just one "page" using RF and as I wrote above... using IR is most uncomfortable imo.

It dawned on me why we are seeing different keys working on our remotes. It's a universal remote, duh , we don't have the same codes programmed. Sometimes the most obvious things just blow right by me.

Anyway, I spent the last few hours trying different codes to see which has the most active keys. I've got to get a life.

Code 3246 on the aux button is the best I've found so far. All of the keys above the mouse pad work as well as quite a few below.

Same as above... IR ?? Not an option for me then

The only ones that don't generate an event in EG are;

The big annoying green button.
The four media keys over the number pad.
The * and # keys.
Last, Connect and DVD Menu.

in my case:
green button = "7.Button.13"
media key 1 = "7.Button.73"
media key 2 = "7.Button.70"
media key 3 = "7.Button.71"
media key 4 = "7.Button.74"

Last / Connect -> Not mappable
DVD Menu = "7.Button.36"

Seems like you haven't added all of the HID Devices (The Gyration remote registers more than one... refer to my instruction in the MediaPortal Forum for this).

Volume and mute keys generate events but always temporarily takes the remote to the TV page and always the same event no matter what you are controlling. Seems to be built into the remote this way, I can't change it.

You should check MediaPortal config to see whether you accidentally mapped the HID-input to this.

Enter the code by pressing and holding the aux button and punch in the numbers. I haven't tried to see if the code will work on the TV or Cab pages yet. According to the instructions the keys that aren't being seen should be able to learn from other remotes. According to about a dozen other forums I been to that's just BS. When you send IR to it, it just locks up. The batteries have to come out to get it going again.

I use two "pages" to Switch my TV and /or AMP on / off... thats all IR in my case... I don't really understand why you need IR despite the RF "page" to control your PC.

One Easter Egg type thing I discovered. When you push the Connect then the Setup Menu keys the four arrow keys become Keyboard arrow keys and the Ok key becomes Return although they still send their USB-UIRT code too. Push Aux again to get back to normal mode.

[CollinR]

What do you guys think my chances are of success with this device?

http://resources.mini-box.com/online/pi ... 0x2%20(OEM)/Documentation/UsbLcd%20Hardware%20Installation%20Guide.pdf

I am not as concerned with the LCD functionality as I am the HID keypad and IR reciever.


This is a case piece, the rest of the case can be seen at:
http://www.mini-box.com/M300-LCD-Enclos ... ategory=87

[Bartman]

Is this even a HID device?
I cannot find any driver/software for the device which could give us a clue.
Although HID keyboards don't work with the HID plugin because they are exclusivly opened by windows.

[CollinR]

Pretty damn cool if it does though huh.

This could be a killer SageTV client, IR and front controls in a tiny package. Unfortunately the mainboard only has PCI (Intel "Little Valley"). So HD TV I dunno, I haven't booted it yet but a bunch of bang to your buck at ~$70US, add in a thumb drive and that case and would be killer.

More info:
The keypad
http://www.mini-box.com/picoLCD-20x2-OE ... tegory=490

The mainboard
http://www.intel.com/products/motherboa ... /index.htm

[Bitmonster]

This isn't a HID device. It uses an EXE to control the device and third-party application can connect to this server through network connections. The documentations looks fine, but someone has to write a new plugin for it.

[CollinR]

I have been playing with this some nd am having trouble with a UPS device. I also had a buddy mention this to me as well.

Code: Select all

1:59:33 PM   Error reading HID device: APC Back-UPS ES 500 FW:824.B1.D USB FW:B1
1:59:33 PM   Exception in thread \\?\hid#vid_051d&pid_0002#6&317cd3bb&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}:
1:59:33 PM   Traceback (most recent call last):
1:59:33 PM     File "threading.pyc", line 486, in __bootstrap_inner
1:59:33 PM     File "C:\Program Files\EventGhost\plugins\HID\__init__.py", line 540, in run
1:59:33 PM   UnboundLocalError: local variable 'buf' referenced before assignment
1:59:33 PM   
1:59:46 PM   System.PowerStatusChange


Any ideas?

[Bartman]

This could only happens when readfile does not raise an error.
Does the error always happens with this device?

Can you add a "print rc" statement after line 539?
this

Code: Select all

#parse data
if len(buf) == n and not self.abort:

should become

Code: Select all

#parse data
prit rc
if len(buf) == n and not self.abort:

[CollinR]

Code: Select all

2:30:30 PM   Error reading HID device: APC Back-UPS ES 500 FW:824.B1.D USB FW:B1
2:30:30 PM   Exception in thread \\?\hid#vid_051d&pid_0002#6&317cd3bb&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}:
2:30:30 PM   Traceback (most recent call last):
2:30:30 PM     File "threading.pyc", line 486, in __bootstrap_inner
2:30:30 PM     File "C:\Program Files\EventGhost\plugins\HID\__init__.py", line 540, in run
2:30:30 PM   UnboundLocalError: local variable 'rc' referenced before assignment
2:30:30 PM


Not a shocker if that is my fault. lol


EDIT:
Oh and this only happens on startup and when adding/configuring the plugin.

[Bartman]

hmm.
Maybe something wrong the event.

Can you take lines 526 to 532 put of the try block to see which lines raises an error?

[CollinR]

I am sorry but I do not understand what you want me to do.

I am very impressed looking through this though, very cool indeed.

[Bartman]

Try the attached file.

[CollinR]

That I can do!

Code: Select all

9:07:58 AM   Plugin: HID: APC Back-UPS ES 500 FW:824.B1.D USB FW:B1
9:07:58 AM   Bytes to read: 5
9:07:58 AM   Exception in thread \\?\hid#vid_051d&pid_0002#6&317cd3bb&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}:
9:07:58 AM   Traceback (most recent call last):
9:07:58 AM     File "threading.pyc", line 486, in __bootstrap_inner
9:07:58 AM     File "C:\Program Files\EventGhost\plugins\HID\__init__.py", line 527, in run
9:07:58 AM   error: (1, 'ReadFile', 'Incorrect function.')
9:07:58 AM 


[Bartman]

hmm.
Du you have any software from the UPS running which might prevent access?
Although the device is already opened.
Any other HID device on the computer? If yes do they work correctly?

[CollinR]

hmm.
Du you have any software from the UPS running which might prevent access?

No

Any other HID device on the computer? If yes do they work correctly?

I just tried a joystick I had lying around and it worked, worked really well too.


I don't have many HID devices yet but this plugin seems hugely interesting, as there as so many HID devices.