Author Topic: Leopold FC660C connecting problem. (Read 14403 times)

Saclet · « **on:** Thu, 23 May 2013, 04:49:38 »

Hello, I got a Leopold FC660C from EK few days ago. It's working great but there is small problem but it's very annoying. Every time I turn off or restart my PC, the keyboard always stop working after the PC turns back on. I always have to unplug the keyboard USB cable and plug it in again in order to make it work again. It's very weird, and right now I only have it and my mouse so there is no another keyboard. Do you have any ideas to fix it ?

And I checked the Hardware and Devices in Windows 7 control panel, but I didn't see any model, or manufacturer information about this keyboard, my CM QFR still has all information when I plug it in but Leopold FC660C doesn't, both of them don't require any driver as far as I know.

Jocelyn · « **Reply #1 on:** Thu, 23 May 2013, 04:51:34 »

I don't really have a solution for you, but a lot of keyboards are like this upon reboot.

Saclet · « **Reply #2 on:** Thu, 23 May 2013, 04:56:24 »

Quote from: Jocelyn on Thu, 23 May 2013, 04:51:34

I don't really have a solution for you, but a lot of keyboards are like this upon reboot.

Are there any chance this is a fault one ?

Jocelyn · « **Reply #3 on:** Thu, 23 May 2013, 04:58:44 »

I guess there's a chance, but I doubt it. That's probably just how it works, but I'm sure someone who has one will post and let you know. If not, I'll have WFD's FC660C on Friday or Saturday and I'll test it out and post back here

Saclet · « **Reply #4 on:** Thu, 23 May 2013, 05:05:05 »

Quote from: Jocelyn on Thu, 23 May 2013, 04:58:44

I guess there's a chance, but I doubt it. That's probably just how it works, but I'm sure someone who has one will post and let you know. If not, I'll have WFD's FC660C on Friday or Saturday and I'll test it out and post back here

Wow wow, one more thing, I set FN + Q to turn ESC to ` then the insert light is on, after I restart the PC the insert light still on but the keyboard doesn't work. That's very weird now.

WhiteFireDragon · « **Reply #5 on:** Thu, 23 May 2013, 05:05:42 »

It's just yours. My computer has been through sleep, reboot, and shutdown with it still plugged, and still works fine after computer is on again.

What you're describing is actually a pretty big problem, and if this was in all the FC660C, there would be a lot of complaints by now. Try a different computer to see if it has the same problem. It might be how your mobo handles USB devices, or some weird driver/software installed on your computer.

RyanM · « **Reply #6 on:** Thu, 23 May 2013, 05:07:52 »

Yeah, I don't think that's really normal. I've never had that problem except maybe one freak occurance years ago. I wouldn't think it's an actual hardware problem, though.

Grim Fandango · « **Reply #7 on:** Thu, 23 May 2013, 05:12:20 »

Also consider that this may be a motherboard problem rather than a problem with the keyboard. I have heard similar stories before. It may sound stupid, but have you tried using a different USB port? Does it work prior to windows starting? Can you F8 to get into BIOS for example? You could update (chipset, usb controller drivers, bios) to make sure all those things are not the reason before you send the keyboard back. I think it is more likely to be a system issue than a keyboard fault. Though of course i can not know for sure.

Saclet · « **Reply #8 on:** Thu, 23 May 2013, 05:25:06 »

The weird thing is after I restart my PC, I still can do Fn + Q command so I can see the insert light but that's it, the keyboard doesn't do anything but that until I have to unplug it and plug it in ........ again!

Glissant · « **Reply #9 on:** Thu, 23 May 2013, 05:36:12 »

I had a random thought; did you check if the dip switches are all aligned? Just see of moving them can help.
No idea if it will work.

Saclet · « **Reply #10 on:** Thu, 23 May 2013, 05:59:00 »

I never had it before, I have both HHKB Pro 2 and Realforce 87u, all of them are doing well and flawless so far.

jabar · « **Reply #11 on:** Thu, 23 May 2013, 08:19:00 »

Check your BIOS version and see if there is an upgrade available. I had an issue where a keyboard would flat-out not be recognized at all in Windows and it turned out that either the chipset drivers were corrupt (which could have been the case - I had some other keyboards give me BSODs) or there was a bug addressed in the newest version.

phoenix1234 · « **Reply #12 on:** Thu, 23 May 2013, 09:13:46 »

Quote from: Saclet on Thu, 23 May 2013, 04:49:38

Hello, I got a Leopold FC660C from EK few days ago. It's working great but there is small problem but it's very annoying. Every time I turn off or restart my PC, the keyboard always stop working after the PC turns back on. I always have to unplug the keyboard USB cable and plug it in again in order to make it work again. It's very weird, and right now I only have it and my mouse so there is no another keyboard. Do you have any ideas to fix it ?

And I checked the Hardware and Devices in Windows 7 control panel, but I didn't see any model, or manufacturer information about this keyboard, my CM QFR still has all information when I plug it in but Leopold FC660C doesn't, both of them don't require any driver as far as I know.

I think you can work around with the following steps:
- Try to replace the usb cable with another one
- Try to change the usb port
- Try to clean the usb port with contact cleaning liquid

I did not have this issue but I faced the issue with usb thumb-drive many times, it is normally because of the port.

aggiejy · « **Reply #13 on:** Thu, 23 May 2013, 09:35:44 »

I'm on a Mac, but mine comes back one after a restart. However, the Fn-Q option, which I use, resets to off after I unplug or power down. The light doesn't stay on like you describe though. I assume this is the way it's supposed to work though.

daerid · « **Reply #14 on:** Thu, 23 May 2013, 11:19:45 »

If a replacement USB cable doesn't fix the problem, then you should get your unit replaced. That's definitely NOT how it's supposed to work.

Saclet · « **Reply #15 on:** Thu, 23 May 2013, 14:17:09 »

All drivers and BIOS is up to date, and I tried to change USB cables but it's still happen. If the keyboard doesn't response at all after restart the PC, it will be a common problem. However FN + Q still working but the rest of it doesn't which made me feel very weird about this.

WhiteFireDragon · « **Reply #16 on:** Thu, 23 May 2013, 14:47:55 »

Isolate the problem whether it's your keyboard or computer. Just try it on a completely different computer instead of trying to diagnose every possibility with your computer.

Quote from: WhiteFireDragon on Thu, 23 May 2013, 05:05:42

Try a different computer to see if it has the same problem.

Masterchief79 · « **Reply #17 on:** Thu, 23 May 2013, 19:49:59 »

Well, I randomely have the same problem with my Mouse (Razer Lachesis at USB3.0 port). Did you plug it at an USB3.0 (blue) or 2.0 (black) port? Maybe it's not even necessary to connect it to 2.0. As you may know, there are some USB3.0 ports which are natively supported (Z77 chipset for example) and some which are added by external controllers on the mainboard (such as Renesas or Atheros). The native ones happen to have much less issues like this one.
Actually, my HID's are all connected to internal USB2.0 ports because the 3.0 are *****ing so much. There are these little bracket adapters, they are perfect for this usage.

PS: Another reason why I prefer native PS2 keyboards

Saclet · « **Reply #18 on:** Thu, 23 May 2013, 20:48:17 »

Quote from: Masterchief79 on Thu, 23 May 2013, 19:49:59

Well, I randomely have the same problem with my Mouse (Razer Lachesis at USB3.0 port). Did you plug it at an USB3.0 (blue) or 2.0 (black) port? Maybe it's not even necessary to connect it to 2.0. As you may know, there are some USB3.0 ports which are natively supported (Z77 chipset for example) and some which are added by external controllers on the mainboard (such as Renesas or Atheros). The native ones happen to have much less issues like this one.
Actually, my HID's are all connected to internal USB2.0 ports because the 3.0 are *****ing so much. There are these little bracket adapters, they are perfect for this usage.

PS: Another reason why I prefer native PS2 keyboards

I think 2.0 or 3.0 is doesn't matter, btw the last time I used PS2 keyboard was IBM Model M, I did have to buy special adapter for it because the USB (both 3.0 and 2.0) can't pull enough power.

jabar · « **Reply #19 on:** Thu, 23 May 2013, 21:10:14 »

Also, I have a few mech keyboards (not sure which ones, but they seem to be USB) which don't work immediately upon Win7 login unless I press a few keys and wait 10-15 seconds. Then the keyboard "wakes up".

I did mention BIOS issues before, and you responded, but does the FC660C work in BIOS but not Windows?

Saclet · « **Reply #20 on:** Fri, 24 May 2013, 12:20:34 »

Quote from: jabar on Thu, 23 May 2013, 21:10:14

Also, I have a few mech keyboards (not sure which ones, but they seem to be USB) which don't work immediately upon Win7 login unless I press a few keys and wait 10-15 seconds. Then the keyboard "wakes up".

I did mention BIOS issues before, and you responded, but does the FC660C work in BIOS but not Windows?

It doesn't work in BIOS.

ValerieV · « **Reply #21 on:** Fri, 24 May 2013, 14:49:34 »

I had this same exact problem with my Realforce keyboard. I asked around on this site if anyone had this problem and they said no. I don't know if it is a keyboard issue or a computer issue. Either way, i would ask for a replacement keyboard. That is a big deal. I would always have to unplug and then plug it back in and that gets annoying and it can't be good for the connection cable either.

Saclet · « **Reply #22 on:** Sat, 25 May 2013, 04:35:02 »

Quote from: ValerieV on Fri, 24 May 2013, 14:49:34

I had this same exact problem with my Realforce keyboard. I asked around on this site if anyone had this problem and they said no. I don't know if it is a keyboard issue or a computer issue. Either way, i would ask for a replacement keyboard. That is a big deal. I would always have to unplug and then plug it back in and that gets annoying and it can't be good for the connection cable either.

I got Realforce 87u 45g and HHKB Pro 2. All of them had no problems, even the keyboards which use different switches. This is the first keyboard in my inventory has this problem.

ValerieV · « **Reply #23 on:** Sat, 25 May 2013, 14:13:43 »

Yeah, i would ask for an exchange. Like i said, it's a big deal and for the money we spend around here on keyboards we deserve to get the ones that work.

daerid · « **Reply #24 on:** Sat, 25 May 2013, 14:33:10 »

Not only that, but Brian over at EK takes the reputation of the products he sells very seriously. I'm sure he'd be more than happy to give you an exchange with no problems.

WRXChris · « **Reply #25 on:** Sat, 25 May 2013, 14:35:26 »

As others have said, I highly recommend testing the keyboard on another computer before RMAing it. This will isolate the problem to either the keyboard or your computer. If it doesn't hang on restart on another computer, then the problem is obviously not the keyboard, and an RMA would just be a waste of EK's money and both of your time.

Saclet · « **Reply #26 on:** Sun, 26 May 2013, 02:13:58 »

Quote from: WRXChris on Sat, 25 May 2013, 14:35:26

As others have said, I highly recommend testing the keyboard on another computer before RMAing it. This will isolate the problem to either the keyboard or your computer. If it doesn't hang on restart on another computer, then the problem is obviously not the keyboard, and an RMA would just be a waste of EK's money and both of your time.

I'm using win 7 and I tried it on 2 computers which are using win xp and win 7 pro. But I still have that problem.

WRXChris · « **Reply #27 on:** Sun, 26 May 2013, 02:22:17 »

Quote from: Saclet on Sun, 26 May 2013, 02:13:58

Quote from: WRXChris on Sat, 25 May 2013, 14:35:26
As others have said, I highly recommend testing the keyboard on another computer before RMAing it. This will isolate the problem to either the keyboard or your computer. If it doesn't hang on restart on another computer, then the problem is obviously not the keyboard, and an RMA would just be a waste of EK's money and both of your time.
I'm using win 7 and I tried it on 2 computers which are using win xp and win 7 pro. But I still have that problem.

Definitely a problem with the keyboard itself if it's having the problem on 2 different machines. like others have said, If I were you I would contact EK about a replacement, they have a good reputation when it comes to problems like this one!

ValerieV · « **Reply #28 on:** Sun, 26 May 2013, 07:43:17 »

Also, you don't want to waste too much time when calling EK. Yes you probably have a warranty but it still is a good idea to get that done as soon as possible. Good luck.

zoolzoo · « **Reply #29 on:** Mon, 27 May 2013, 20:41:49 »

Try unplugging the board and uninstalling the HID device controller pertaining to the board in device manager and restarting. Once fully booted up, plug it back in. Give it a sec to "wake up".

Also, try messing with the dip switches if that doesnt work.

The FC600C doesnt seem to be called out by name in device manager, so what you are seeing there is normal.

zoolzoo · « **Reply #30 on:** Wed, 29 May 2013, 22:19:48 »

any luck?

Saclet · « **Reply #31 on:** Thu, 30 May 2013, 01:03:41 »

Quote from: zoolzoo on Wed, 29 May 2013, 22:19:48

any luck?

There are 2 things, first one is it couldn't be unconnected since the insert light is still working but that's all, I doubt it. Second one is EK agreed to send me a replacement, it will come on this Friday. Let's hope it will be ok. I will check and post news on Friday.

ValerieV · « **Reply #32 on:** Thu, 30 May 2013, 06:03:44 »

The guys at EK are pretty good. At least you are getting a replacement. LIke i said, i had this same problem so hopefully it was just the keyboard itself. Good luck and let us know how everything goes.

Travellerr · « **Reply #33 on:** Fri, 27 December 2013, 13:21:44 »

Hey I know this is a bit of different situation, but mine also does this at times as well, but does your Leopold fc660c work with a ps2 adapter? Because I runs lovely with no errors or problems via usb, but as soon as I try starting up my rig with the Leopold fc660c plugged into the ps2 port I get no reaction or response from the keyboard. It kind of has been bumming me out, and granted I have a good many usb 3.0 slots that are backwards compatible(something like a total of 9 or something maybe 10) but I prefer having my keyboards, mechanical or not, plugged into the ps2 port. Does or has anyone else have this problem with the Leopold 660c? Or does any keyboards owners with more knowledge than I know if their is a fix(I have used two different ps2 adapters both from Cooler Master for my XT and my Rapid) or should i contact Brian from EK?

Mr. C · « **Reply #34 on:** Wed, 01 January 2014, 22:51:57 »

I have FC660C which works fine plugged into Dell Win 7 64bit desktop, ASUS Ultrabook laptop, & a USB KVM to Dell CentOS 5.9 Linux server. No problem with any of the above. Good luck with the replacement. It should solve your problem.

quickcrx702 · « **Reply #35 on:** Fri, 03 January 2014, 05:14:04 »

Quote from: WRXChris on Sun, 26 May 2013, 02:22:17

Quote from: Saclet on Sun, 26 May 2013, 02:13:58
Quote from: WRXChris on Sat, 25 May 2013, 14:35:26
As others have said, I highly recommend testing the keyboard on another computer before RMAing it. This will isolate the problem to either the keyboard or your computer. If it doesn't hang on restart on another computer, then the problem is obviously not the keyboard, and an RMA would just be a waste of EK's money and both of your time.
I'm using win 7 and I tried it on 2 computers which are using win xp and win 7 pro. But I still have that problem.

Definitely a problem with the keyboard itself if it's having the problem on 2 different machines. like others have said, If I were you I would contact EK about a replacement, they have a good reputation when it comes to problems like this one!

This. As a side note, if you have too much crap plugged into the usb ports, along with usb hubs full of devices, the devices will start acting weird because you are drawing too much power. If that is the case then you need a powered USB hub, or unplug some stuff when you aren't using it like scanners, webcams, etc.

aggiejy · « **Reply #36 on:** Thu, 16 January 2014, 10:46:43 »

I have this same problem when going through some hubs. It always works going direct. (Mac)

News:

Author Topic: Leopold FC660C connecting problem. (Read 14403 times)