Replies to This Discussion

Permalink Reply by James masterman on March 20, 2012 at 6:03pm

This is caused by windows misinterpreting the driver for XBee. It's happened to me on Windows XP, not sure about windows 7 as my field notebook is only XP. There is no proper fix for it. The only work around I have found is as follows:

• Open device manager in windows so you can see the list of hardware installed. Keep the cursor near the "pointing devices" node in the tree
• Plug in the XBee USB cable to the computer
• In a few seconds it will load a new mouse called something like "Trackpoint device".
• As quick as you can, right click on this new device and select uninstall.

 

That will fix the problem for now. It appears to happen randomly so there is no guarantee that it won't happen again.

 

Hope that helps.

 

Cheers

James

• ▶ Reply

Permalink Reply by Brandon Jones on April 21, 2012 at 3:28pm

I had a similar problem in windows 7, but my mouse would jump around.  XBee TM module showed up as Microsoft Serial BallPoint in device manager.  Luckily my mouse still kinda worked, so I could just disable it and was good to go.

• ▶ Reply

Permalink Reply by Alex.CCCP on April 26, 2012 at 7:29pm

Just keep your virtual comport busy before you power the APM, keep it opened by an application (MP/GCS/etc). Otherwise, when APM is sending telemetry data windows thinks there is a "Microsoft Serial BallPoint" connected to the comport.

• ▶ Reply

Permalink Reply by Steve on April 28, 2012 at 5:10pm

So start Mission Planner before powering up the APM?

• ▶ Reply