Using MI_00 etc

[mbround]

I'm working on a problem with the PHX01RN remote, where the device seems to have two subclasses (not the right word I know) to handle keyboard and mouse mode.

Currently it's registered using this string

Code: Select all

        self.winUsb.Device(self.Callback, 8).AddHardwareId(
            "PHX01RN USB Receiver", "USB\\VID_0755&PID_2626"
        )

Some of the buttons then only register a string of zeroes, which are just the "button-up" action coming through, suggesting that some of the information isn't being captured.

Using this USB snooper -http://sourceforge.net/projects/usbsnoop/ - I can see 2 sub-devices, listed as USB\\VID_0755&PID_2626&MI_00 and USB\\VID_0755&PID_2626&MI_01. I found an additional plugin on these forums for the PHX01RN which attempted to address this, but any attempt to use the &MI_00 part to register results in a "device not found" error within eventghost.

Anyone got any tips as to how to look at both of these input channels ?

[mbround]

I have an "interesting" follow-up to report on this one - though unfortunately I've not solved the problem !

EG 0.4.1.r1600 installs a single driver for the P-01RN device, which means that the plugin file mentioned in this post (viewtopic.php?f=2&t=2304&hilit=phx01rn) fails to initialise.

I then installed EG 0.4.1.r1568, which installs 2 separate drivers for the P-01RN device, listed as MI_00 and MI_01 (keyboard & mouse respectively). This means the plugin file initialises correctly, but then oddly doesn't actually produce any data in the log when buttons are pressed.

It has been reported that this remote has worked in the past, but it seems that something has changed with more "recent" EG releases to install a different driver that then doesn't provide all the information that's required for the plugin to process.

Anyone with any further ideas on things to try ?

[WharfRat]

I have started a new PHX01RN forum topic here (viewtopic.php?f=2&t=5927).

What might interest you the most is Part V - The Autopsy.