brish

Since upgrading to the latest firmware, I have been unable to get my Key Croc to connect to C2. Was there any follow up with this issue or other known aspects about it? I have completely reset it. I have tried with multiple internet and wifi connections where I have complete control. The Croc can see (at least ping) the server where C2 is located. All other devices can still connect to C2. I have tested removing the firewall settings on the C2 server. I have removed and created a new device in C2 downloading the updated config. Based on this post, I have removed all aspects of the device.config file and sent it to the Croc with scp from Windows. In all previous cases (including when it worked in the past), I was using arming mode and just copied the device.config file to the root of the Croc in Windows Explorer. On a side note that may not be related, I have had much more difficulty connecting to wifi since upgrading. Changing the config.txt has not worked immediately. I did find that I could update the wpa_supplicant.conf file which would work. After resetting, I noticed that the connections were easier. However, after I changed the root password, it was not wanting to connect when making changes to the config file. Once I changed it back to the default password, the config.txt file changes seem to work just fine. I have not tested this thoroughly, so it may just be a coincidence. This also did not resolve the issue with C2.

Initially, this was passing through a basic USB-A hub connecting to a Microsoft Surface Dock connected with the dock connector to the Microsoft Surface. Realizing this, I tested again with the Key Croc connected directly to the USB-A port on the Surface with the same Lenovo keyboard. When I put the Surface to sleep, I had the same result. There was still activity with the LEDs (NumLock, CAPS Lock) on the keyboard and key strokes were picked up by the Key Croc passing to C2, but nothing passing to the PC. One additional oddity that may or may not be relevant was that the NumLock LED remained lit on the keyboard after the Surface went to sleep while connected to the Key Croc. Without the Key Croc, the NumLock turns off within about 10 seconds of being put to sleep.

I have had this same issue testing today. This is not a solutions, but I am including some more details and troubleshooting. Using a Microsoft Surface 7 running Windows 10 with standard Lenovo US keyboard. Once the computer locked and went to sleep, the keyboard was no longer responsive. It would not wake the computer as usual. I woke it with the mouse. I then tested typing with no response. I also checked the NumLock and Caps Lock LEDs. They functioned. I checked my streaming to C2. The keystrokes were still being picked up by the KeyCroc and being sent to C2. They just were not passing to the computer. When I unplugged the keyboard from the KeyCroc (leaving the KeyCroc plugged into the computer), it still would not work. My issue also required me to remove the KeyCroc from the computer to allow it to reboot before it would work again. To further test, I tried to duplicate the issue. Once connected and functioning correctly, I tried removing the keyboard from the KeyCroc and reconnecting. It continued to function once reconnected. I also checked the Device Manager to see if there was a power saving option that was causing it to disconect or sleep in some way like a network adapter. This was not the case. I did find if the computer was locked, but did not yet have time to go to sleep, the keyboard would continue to function after unlocking. Manually causing the sleep would duplicate the issue. I did notice that the HID Keyboard Device (on USB input device) continued to remain in the Device Manager when the keyboard was not passing input to the computer. I am not sure if it is relevent, intended, or a separate issue, but ever time the KeyCroc boots, the USB keyboard (showing as a HID Keyboard Device) resinstalls. It is quite noticeable because it connects, disconnects, and reconnects a time or two with an audible alert each time. This could be an issue in deployment.