CybrDisplay External Status Plugin

[cybrmage]

Here is a new Test App....

I have added code to make sure that iMon Manager is not running...

I also added code to try to force the HID devices into a known state....

Please test and report... Thanks

[Tide]

I guess it is back to working. I think this is what did it. I am not sure what i did but I switched the inital startup type to mouse instead of keyboard. Started Frontview. Stopped iMon manager. Changed back to keyboard as the initial type. Started Frontview. Shut down iMon Manager.

Now the mouse stick will again work if iMon Manager is not running.

Something is odd with Frontview and what it does to the mouse stick behavior.

________________________________

Here is my log from test 15.
- I just pressed all the buttons. Do you want me to do the removal steps too?

[me1]

cybrmage:
This are the logs with test app 15 - done with the mce remote
Test15WithMCE.ZIP

[globaldonkey]

Originally Posted by Tide

Something is odd with Frontview and what it does to the mouse stick behavior.

Definitely Tide. That's the sort of thing I found too. I could not get the pad to work at all if frontview was set to never with the V7 software. That's why Cybrmage has always recommended V6 of iMON Manager.

@Cybrmage

I'll help with Option 1 if you can point me in the right direction of where to get a USB logger from. I've never used one.

I think option 3 could be a bit dicey given the above discussion with Tide (ie people running different versions of Imon Manager and it doing different things)

[armandp]

Here i am to participate.. you already found my configuration details.
If there's details missing let me know and i'll supply them.

Also not wanting to create confusion i'm using the unrecommended iMON_7_01_0204_BETA_ENG drivers and i have IMON OEM that comes with the Antec Fusion 430 V2 case. The CybrDisplay 12-4 version works great on the LCD part but the MCE remote response is delayed.

Your test application (15) keeps crashing after the initial configuration dialog:

Detect_HID(): checking device "\\?\HID#VID_04FC&PID_05D8&MI_01&Col04#7&377a8 e87&
0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}"
Detect_HID(): checking device "\\?\HID#VID_04FC&PID_05D8&MI_01&Col03#7&377a8 e87&
0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}"
Detect_HID(): checking device "\\?\Root#RDP_KBD#0000#{884b96c3-56ef-11d1-bc8c-00
a0c91405dd}"
Detect_HID(): checking device "\\?\HID#VID_04FC&PID_05D8&MI_00#7&1fb70242&0& 0000
#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}"
Detect_HID(): checking device "\\?\Root#RDP_MOU#0000#{378de44c-56ef-11d1-bc8c-00
a0c91405dd}"
Detect_HID(): checking device "\\?\HID#VID_04FC&PID_05D8&MI_01&Col01#7&377a8 e87&
0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}"
Found an iMon DOS Device

KillImonManager()
KillImonManager(): iMon Manager not running
KillImonManager(): completed
System.Runtime.InteropServices.COMException (0x80070006): The handle is invalid.
(Exception of HRESULT: 0x80070006 (E_HANDLE))
At System.Runtime.InteropServices.Marshal.ThrowExcept ionForHRInternal(Int32
errorCode, IntPtr errorInfo)
At System.Runtime.InteropServices.Marshal.ThrowExcept ionForHR(Int32 errorCod
e)
At System.Runtime.InteropServices.Marshal.FreeHGlobal (IntPtr hglobal)
At InputService.Plugin.iMonHIDReceiver.SetHardwareMod e(RcMode mode)
At InputService.Plugin.iMonHIDReceiver.Start_DOS()
At InputService.Plugin.iMonHIDReceiver.Start()
At InputService.Plugin.iMonHIDReceiver.Main()

The exception is not logged so that's why i'm quoting it from the cmd prompt.
I attached the generated log to the post. I also tried some previous versions of the test app but they all fail in a similar way.

[globaldonkey]

Strange behaviour cybrmage.....

Test 15.1 is a simple start the test program, press the up, down, left and right buttons on the pad. The right button seems to be interpreted as a left click.

Test 15.2 is a start followed by mouse/ keyboard toggle, then up, down, left and right.

[Tide]

Just for note I too am using the iMON_7_01_0204_BETA_ENG drivers.

Cybrmage if I need to get USB logger and run it let me know.

[cybrmage]

Originally Posted by Tide

Now the mouse stick will again work if iMon Manager is not running.

Which, unfortunately, is NOT what we want... We want the device to be in a mode where it does NOT send data as a mouse or a keyboard. The reason we want this, is that we then have full control of what the remote does... otherwise, we will get unwanted mouse movement and keystrokes...

Originally Posted by Tide

Something is odd with Frontview and what it does to the mouse stick behavior.

Yes... there is.... Soundgraph is CONSTANTLY changing the way that the software operates....

Originally Posted by Tide

Do you want me to do the removal steps too?

Yes... Please... If it's not too much of a hastle...

Originally Posted by me1

cybrmage:
This are the logs with test app 15 - done with the mce remote

Thanks!

Originally Posted by globaldonkey

I'll help with Option 1 if you can point me in the right direction of where to get a USB logger from. I've never used one.

Thanks... I'll get information to you shortly....

Originally Posted by globaldonkey

I think option 3 could be a bit dicey given the above discussion with Tide (ie people running different versions of Imon Manager and it doing different things)

I agree... but the other options will cause a lot of code bloat... and WILL be time consuming....

I think that, for now, option 3 (which I've already implimented in test 15) along with the recommendation of installing iMon Manager v6.crap with be the short term solution.... (that way, the driver will be usable, and can actually be released for use)...

The version of iMon Manager installed will be immaterial... it will just be used as a helper application... Then I can take the time to find a more suitable solution that does not depend on having the iMon Manager installed...

Originally Posted by armandp

Here i am to participate..

Welcome.

Originally Posted by armandp

i have IMON OEM that comes with the Antec Fusion 430 V2 case.

You have my sympathies...

Originally Posted by armandp

The CybrDisplay 12-4 version works great on the LCD part but the MCE remote response is delayed.

Yes... that is correct.... If you read the release notes, that feature is marked as experimental... had has evolved into the HID test app (which will get a name change shortly, as it not supports the legacy devices as well)... Once the testing with the IR Server Suite plugin is done, iMon remote support will be removed from the CybrDisplay plugin...

(Before people with a VLSYS_Mplay device start to complain... remote support for that device will remain... due to the design of that device, remote support MUST be combined with the display driver)

Originally Posted by armandp

Your test application (15) keeps crashing after the initial configuration dialog:

Normally, you will not need to post logs (although it IS appreciated) for this device (as I have the same device), except when you encounter problems (as you have).

I can not duplicate this problem... And do not see where this error could be generated, so I have added extra logging to the next version of the test app to try to determine what is happening...

Could you also do the following:
1) open Control panel
2) select system
3) select hardware
4) open Device Manager
5) expand the "Universal Serial Bus Controllers"
6) double click on the "SG Remote Control device"
7) click on driver
8) report the driver date and driver version (this is different from the iMon Manager version)

Originally Posted by globaldonkey

The right button seems to be interpreted as a left click.

It looks like the driver was able to force the device into "mode 1"... and the mousepad data is being sent via the HID remote control device... good... but I had an index into the data structure wrong.... it is fixed in the next version of the test app.

Originally Posted by Tide

Cybrmage if I need to get USB logger and run it let me know.

As I mentioned to globaldonkey, I will get information to you shortly.... Thanks!!



And attached is the updated test application

[Tide]

Originally Posted by cybrmage

Which, unfortunately, is NOT what we want... We want the device to be in a mode where it does NOT send data as a mouse or a keyboard. The reason we want this, is that we then have full control of what the remote does... otherwise, we will get unwanted mouse movement and keystrokes...

Knowing this is what you want, I think I can achieve this. I thought you wanted the mouse stick to move when iMon Manager is closed. During my attempt to get it back to this state I had it in the state you describe as wanting. I think I can get it back into your desired state. I will give it a try after I run 16 then run 16 again.

[globaldonkey]

That looks better. All the input is coming from the HID device. I did the following,

1. Moved the PAD in all directions
2. Pressed some keys (play, stop etc)
3. Pressed the mouse/keyboard toggle
4. Moved the PAD in all directions

Just an FYI, if IMON starts with Frontview set to "never" the remote stays in mouse mode (I think what you referred to as mode 1 - all input from the HID device). The end result is that the pad only controls the mouse, and the mouse/keyboard toggle does not work to switch it into keyboard mode. I think it is frontview that actually changes the mode.