Mice and Pointing Devices

[varocketry]

My MX510 wired optical USB mouse has just started having connection problems, yesterday.

Symptoms:  mouse cursor will freeze and then come back,  sometimes it freezes long enough that I notice the RED Laser if off, it tends to become more frequent and then it stops altogether (meaning cursor is frozen, the red laser light is OFF).

A reboot starts things up working again but it decays and stops pretty quickly.

I've changed MX510 connection USB port from the front to the rear of the DEL OPTIPLEX. No change in behavior.

No errors reported in the native Microsot HID driver in Device Manager.

I downloaded and installed the latest MOUSEWARE drivers which made it seems more responsive but it died with 15 mins.

I'll test it on another hom PC later but I need to get work done so I've found a really old PS2 mouse.

Is this MX510 DYING?

THanks, Jim

[rlowens]

Yes, sounds like it is dieing. Does Windows make the "USB Device Disconnected" sound when the mouse goes out?

It is probably a fault in the cord (usually right where it leaves the mouse).

Try it on another PC to make sure it is the mouse that is the problem (not your PC). If the problem is the same on the other PC, get the mouse replaced.

Less than 30 days since purchase, you need to exchange it where you got it.
After 30 days, you would be covered under the 1, 3, or 5 year warranty from Logitech.
See here for RMA info.

If you wanted to repair it yourself, you could cut out the bad part of the cord, or replace the whole cord with one from another USB device or a cheap USB extension cord. Just solder the wires inside the mouse (the screws are under the mouse feet).

BTW, the red light is from an LED, not a Laser.

[varocketry]

Richard:

Yes, sometimes (but not consistently or even a majority of the time) it does make the USB disconnected sound twice in rapid succession - like a disconnect/reconnect.  Other times NO, the mouse simply stalls or freezes and I notice the RED LED is dark.

We think alike in that I've tried manipulating the cord in front of the mouse in an effort to assess whether something like that was happening.  It has more of the feel of Interrupt Conflicts like back in the day when you could put too many devices on the PCI buses with IRC conflicts.  I don;t know if USB is subject to that same issue.

I don't know if I've had this mouse 5 years yet.  I;d have to check that out SOMEHOW???  But it's worked like a charm right up until yesterday.

Thanks for your thoughts.

Jim

[rlowens]

You can also call Logitech and ask about a warranty replacement. They can tell from the SN/PID on the mouse (if it hasn't worn-off) when it was manufactured, and then get an upper-limit on how old it is.

[varocketry]

I plugged it into my wife's DELL MINI10 last night and used it for about 30 minutes before she claimed her laptop. It was readily recognized by WINXP and loaded as a new device at boot-up. No apparent problems while I used it or while she watched TV shows from HULU.

I also have a powered USB hub acting squirelly on the main PC, the MX510 LED mouse was not plugged into this usb hub, it was directly connected to PC's front or rear USB ports.  THis is an old DELL Optiplex that has only USB 1.0 and BIOS does not support USB 2.0.

I'll continue to test but this seems to suggest a USB bus/Hub problem perhaps .

[pmertz]

Actually i have exactly the same problem, and have had it for while. I think it is related to OS, my guess is that you have either Windows Vista or Windows 7 (RC or RTM) and its 64 bit (the problem might also exist on 32 bit - not sure about this). Perhaps it is also related to hardware or software. 

I have had the problem both on Vista and Windows 7. I have got many hits on google describing the same problem.

I am serious planning to buy a new mouse very soon.. 

[varocketry]

PMERTZ:
I am and have been running WIN XP SP3.

I recently had to rebuild a WD MY Book into a new enclosure which had USB 2.o interface.  The MYBOOK also had a FIREWIRE interface which I had been using.  I don;t know if the addition of a USB 2.0 device would cause these problems.

No other system changes occurred.

Jim