CybrDisplay External Status Plugin

[cybrmage]

Originally Posted by Tide

Given your statement about PCI/PCI-E, will this work with Bus Hound?

Yes... It should... The devices will show up as USB controllers.... BusHound just doesn't log the traffic on the PCI bus... (Actually... Even the internal USB controllers on most motherboards are connected to the system via the PCI cbus...)

[Tide]

I did as you said but the log is empty.
Below this line
"Device Phase Data Description Cmd.Phase.Ofs(rep)"
There is no data.

I verified the device string at the bottom of Bus Hound before checking the box and proceeding.
"Hardware ID: USB\Vid_15c2&Pid_0038&Rev_0001&MI_01"

Did you expect me to hear a USB tone during any of this process?

Edit : I did manage to get some data by pressing the keyboard/mouse button on the remote. This log shows me pressing it 2 times. I tried a few other buttons but they gave no respone in the Bus Hound window although they did seem to be working.

[cybrmage]

Originally Posted by Tide

I did manage to get some data by pressing the keyboard/mouse button on the remote.

Ok.. so it is working....

I actually need the logging from the startup of iMon Manager... If running manager doesn't log any data, you will need to go back to the device screen, unselect the device and move up one device in the tree... and try the logging again...

Thanks.

[globaldonkey]

Originally Posted by cybrmage

Is that with both iMon Manager and the test app not running??? or is that with iMon running and the test app running???

The logs shows reports from the mousepad (PAD controller) via the "HID Remote" device... but it does NOT show that the device is sending and keyboard reports.....

That was actually a statement about either iMON running or iMON not running. Nothing to do with the test app.

If iMON is not running, three results are possible (under V6 and my hardware config):

1. If it is from a boot without iMON ever started, the pad moves the mouse (ie this appears to be the default)
2. If iMON has started, and keyboard mode is selected in iMON and iMON is then stopped (or frontview turned off), the pad moves the cursor (ie keyboard)
3. If iMON has been started, and mouse mode has been selected, and iMON is then stopped (or frontview turned off), the pad moves the mouse.

ergo my theory that in V6, if iMON (read frontview) starts then stops, it will leave the pad in the mode that was last set.

In V7, it doesn't matter what mode iMON is set for. If it stops, it leaves the pad in mouse mode. At least that's what it does on my system.

[globaldonkey]

OK, some interesting behaviour here.

If I start the test program, and start to press numbers, nothing is output. I didn't bother appending that log.

However, If I start the test program and move the mouse pad first (which has changed from mouse to keyboard with the start of the test program), then the numbers work. This is the output in 17.1.

I also noticed that the some weird mouse behaviour with the test program. UP and DOWN were reversed, LEFT did nothing, and RIGHT went left. This is the output in 17.2

[Tide]

It looks like Frontview has to be on to get any data.

Here are my results.

[cybrmage]

Originally Posted by globaldonkey

If I start the test program, and start to press numbers, nothing is output. I didn't bother appending that log.

Umm... Actually, the logs would have been helpful in figuring out what was going on... but... no problem... If it happens again, please post the logs.... 8-}

Originally Posted by globaldonkey

I also noticed that the some weird mouse behaviour with the test program. UP and DOWN were reversed, LEFT did nothing, and RIGHT went left. This is the output in 17.2

I think I have this one fixed.... new version attached...

Originally Posted by Tide

It looks like Frontview has to be on to get any data.

Here are my results.

Looking over it now... Thanks!!

[globaldonkey]

Originally Posted by Tide

It looks like Frontview has to be on to get any data.

Here are my results.

Yes that makes sense with my observation that it is actually the frontview component of iMON that sets the mode of remote.

Here are my results.

[cybrmage]

Tide:
Can you please repeat the USB logging...

1) run iMon Manager... set remote to mouse mode.
2) exit iMon Manager
3) run BusHound, start logging (click on "run")
4) run iMon Manager
5) stop the logging.

I need to figure out which of the commands sent set the remote mode, so I need to see the differences...

Thanks!

globaldonkey:

Your capture doesn't show any data.... did you select the correct device? did you select the root of the device?? (the log should show CTL and OUT reports.

[globaldonkey]

It happened again.... no numbers if they are the first thing that is pressed. Logs attached.

Also mouse is still moving in the wrong direction, and left is not working.