Keyboards and Keyboard/Mice Combo Sets

[markscottuk]

Im getting exactly the same with a home built workstation (i7 Extreme 3960X, Asus Rampage IV Extreme, 64GB RAM, Windows 7 x64).  

This is totally unacceptable, might be a breach of UK consumer laws (not fit for purpose).  I never had issues with my MIcrosoft desktop set and I am sorely tempted to sell this pile of crap and buy a decent Microsoft setup which will work.

[John41]

I have the same problem on 2 different systems each with an expensive set MX5500. I've tried everything, the latest setpoint, lots of time with the Logitech helpdesk but no solution.

The problem is very random. Sometimes after 1 hour, somtimes after 1 day.

Logitech doesn't have a solution and should give another, good working product instead of this expensive crap.

[John41]

YES maybe a temporary solution.

Remove all the Logitech Setpoint software. Now you can't use the special mouse and keyboard features but the connection problem seems te be solved.

It works for 2 days (no connection problems when comming out of hybernation mode) on a Intel MB with i7 and Win7 64b.

Logitech it seems you have a problem in your software so please do something.

i have tried this on 3 diff. systems each with their own MX5500 desktop and none of them has the connection error.

So guys try it yourself and let me know.

[Rodekill]

I have posted on another thread about this issue. The problem is with the SetPoint software and apparently Logitech does not wish to recognize this. Or the web suppport is not forwarding the information to the right people. Either way, the consumer is not provided support for the product. It is what it is.

It is correct that if you remove the provided Logitech SetPoint software, the issue does go away.

Best of luck to you all. At one time, I was a faithful Logitech customer.

[MichaelKenward Logi Guru]

---

Rodekill wrote:

Or the web suppport is not forwarding the information to the right people.

---

If you get nowhere here, you could try the official support channels.

Remember, despite the name and location, this is a user-to-user forum, with only occasional input from Logitech's hired hands.

New User Getting Started FAQ

Use the "Contact Us" option in "Support". Depending on where you are, there may be an "email" option.

[LeeBot]

Removing SetPoint didn't work for me, but I originally plugged my receiver into one of my USB 2.0 ports, and had this problem. When I moved it to one of the USB 3.0 ports, it worked perfectly. My theory is that the USB 2.0 ports on my system are actually chained off the USB 3.0 controller. Since the Logitech receiver acts like a USB hub (not a Bluetooth device; very strange), to the computer it looked like a USB hub connected to a USB hub connected to my system USB controller... which probably ended up confusing something along the line. Removing a level of indirection (I have plenty of spare USB 3.0 ports, so why not) seems to have fixed the issue for me.

[MichaelKenward Logi Guru]

Be warned that USB3 hubs can cause problems with wireless receivers.

Potential USB 3.0 interference - Logitech Forums

And see the message linked to the comment there.

I have no idea what you mean by "the Logitech receiver acts like a USB hub". I hub is a hub, a place to connect other stuff. The receiver doesn't act as a hub, it is just a receiver that works at a different frequency from Bluetooth.

[LeeBot]

Not having any problems with USB3 interference (maybe because I don't have any USB3 devices plugged in), but good to know about the potential interference issue for future reference. For now, the problem seems to be solved for me, and I'm happy with that. :-)

A bit of background: Up until now, I've used my MX5500 kit with a built-in Bluetooth receiver on my laptop. The sleep mode button didn't wake up my computer, but it wasn't a big deal because I always powered up my laptop manully anyway.

More recently, I built a PC for use as a Media Center, so I decided I would bring the MX5500 out of storage to use as my couch keyboard/mouse pair. Having the sleep button working on my keyboard would have been a definite plus, so I ordered a replacement Logitech Bluetooth USB receiver for my kit (having long ago lost the original one). Note that this Bluetooth receiver is apparently different than the wireless receiver used with most Logitech devices.

It worked, but I ran into this issue with disconnecting that I didn't have with a third-party Bluetooth receiver. I contemplated just disabling the sleep button, but I wanted the PC to automatically sleep as well as on command, so it absolutely had to wake from sleep with a working keyboard/mouse (and walking across the room to pair the devices again was an unpalatable option).

At this point, I grudgingly figured I would need to replace the kit (probably with a non-Logitech solution this time, such was my annoyance), when I hit upon this thread about trying to remove SetPoint to get things working. While that didn't work, I did run across another thread on another forum that suggested moving the receiver to a different USB port.

That seemed crazy to me (one USB port ought to be as good as the next one), but while monkeying around with removing SetPoint, I discovered in the Device Manager (when using the "View > Devices by connection" menu item) that the Logitech Bluetooth receiver was showing up as a USB hub plugged into a USB hub plugged into the USB controller, with the keyboard and mouse showing up as USB HID devices chained off the USB "hub" emulated by the Bluetooth receiver.

Once I discovered this, a lot of the "magical" behavior of the Logitech Bluetooth receiver compared to other Bluetooth receivers started to make sense. (With a normal Bluetooth receiver, the Bluetooth devices show up as Bluetooth devices, not USB devices, although the Bluetooth receiver itself may be connected by USB.) I'm guessing the newer Logitech Unifying receiver uses a different architecture (wouldn't know, don't have one), but with this model (maybe for compatibility?), the Bluetooth devices show up as USB devices. (Interestingly, the devices are there whether or not my devices were paired--as the pairing was lost after wake.)

Long story short: Moving to the USB 3.0 ports on my system removed that "extra" USB hub that was between my USB controller and the Logitech receiver when it was plugged into the USB 2.0 ports, and fixed the issue for me. I thought I'd post my success to help anyone else who came along later and ran into the same issue, but I felt maybe posting the whole story would just be too much information. :-)

[MichaelKenward Logi Guru]

USB stuff has a habit of remembering devices that you have plugged in in the past. I guess this is to prevent your PC from going through the reinstall hassle every time you plug in a new device.

In the past I have recovered from these disasters by removing USB things in device manager. If you do that, it is important to get windows to show disconnected devices that is not plugged in. There can be dozens of them.

Remove things and you will force Windows to find them again.

When you remove, you can also choose to delete the drivers.

All this is down to trial and error.

Maybe Windows 8 has mended some of this stuff.

[Rsavassi]

I'm having the same problem in here !!! I already did what was suggested before, to go to "Support > Contact Us" and open an specific request to this problem, with reference number for follow up: [removed personal information].

Lets see if they come up with a solution for the Set Point, because doesn't make any sense to spend money buying a set of keyboard and mouse full of features, to have to end up desabling them.

As soon as I hear back from them I'll post the reply in here.