Sign in

Loosing connection - Code V3 on Mac

Follow
Avatar
Joao Urbano

Hi,

I have a brand new V3 code keyboard (full) and it looses connectivity every couple of minutes or so. Input is lost, the leds turn off for less than a second and then connection is resumed.

I am using it with a MacPro Mac OS 12.6.1 connected directly to one of the USB ports.

DIP switch 1 is set to ON all others are set to OFF.

Can you help?

Thanks

 

 

 

 

 

1

Comments

9 comments

Sort by Date Votes
  • Avatar
    Mike Krumpus

    I am also having intermittent problems with my V3 keyboard on my Mac as described above. At least twice per day, it stops working and then a few seconds later starts to work again. When it starts working again, the caps lock LED indicator no longer works. I have to physically disconnect the keyboard and reconnect it in order to get the keyboard back into a stable state. I am very disappointed in this situation. A keyboard should be a stable, reliable device without worry of it failing every day and needing constant attention. 

    Can we get some support for Mac users to help with this instability issue?

     

    0
    Comment actions Permalink
  • Avatar
    Donavon

    I'm having the same issue. I thought maybe it was my USB hub not providing enough power consistently for the keyboard to operate nominally, but I'm confident that is not the issue now.

    I'm on a M1 Pro Macbook Pro and Mac OS 13.4

    0
    Comment actions Permalink
  • Avatar
    Xun Zhang
    • Edited

    Same issue here. CODE V3 keyboard on a Mac mini (M2 Pro / macOS 13.5) keeps disconnecting and reconnecting every a few minutes (sometimes even worse - just a few seconds).

    I can't tell if this is a Mac issue or a keyboard issue (I do have another WASD V2 keyboard and will have a try).

     

    0
    Comment actions Permalink
  • Avatar
    Xun Zhang

    Update: The WASD V2 keyboard does not have this issue. Been using for the weekend and it worked perfectly.

    For the next step I'll downgrade the V3 keyboard to see if this bug is caused by a firmware upgrade.

    0
    Comment actions Permalink
  • Avatar
    Dana M

    I've been having this issue for the past year with my Code V3 (I bought it ~20 months ago).  I've used it exclusively with a Windows 10 laptop (Lenovo).  It started being a very occasional thing, and it seemed like doing a SW4 master reset and/or reflashing the firmware (v2.80) would take care of the issue, for a few months anyway, but it keeps happening especially of late.  The backlight goes out for a fraction of a second, the keyboard is unresponsive for about a second, and then it's back to normal.

    I've tried the following things to mitigate the issue:

    • Move the keyboard from one USB hub to another
    • Move the keyboard from a USB hub directly to one of my laptop USB ports
    • Reflash the keyboard firmware
    • Perform a SW4 hard reset
    • Turn the LED backlight off completely

    None of those things seem to have any effect on whether the problem repeats itself.  (It's happened at least once while I've been typing this.)  I put in a support request a year ago, and they suggested reflashing or downgrading the firmware, but that hasn't helped.  I put in another request about 7 days ago, and haven't heard anything back, so I just put in *another* request.  Hopefully someone from WASD sees this thread and realizes this isn't a one-off issue.

    To the OP... I strongly doubt this is a Mac-related issue.  This is an issue with the embedded microcontroller in the keyboard rebooting itself, and it does that with my Windows laptop, too.

    1
    Comment actions Permalink
  • Avatar
    Jens Kiel

    I'm experiencing similar behavior with a Code 3 keyboard on an Apple iMac. The backlight turns off for a split second in irregular intervals, and the keyboard becomes unresponsive. Two or three keystrokes later, the keyboard becomes responsive again. I've changed USB-A-to-USB-C cables without noticeable improvement, and USB-C-to-USB-C cables of different quality and data rates won't work at all.

    I operate a Code 2 keyboard with the new USB-C controller board at the home office and experience no issues whatsoever - the prime reason for buying a Code 3 keyboard for the office.

    0
    Comment actions Permalink
  • Avatar
    Dana M

    So, update... I got in touch with WASD Support... technician David said "Can you try setting SW3 and SW5 "on" and unplug/replug the keyboard? Let me know if this fixes your issue."  SW3 on disables Scroll Lock so that the LED shows the active layer, and SW5/6 = on,off is Fn key and layers enabled.  I've been running with those settings for the past few days and... it's not rebooting anymore?  So maybe y'all should try the same thing (run with SW3 and SW5 on, make sure to power-cycle the keyboard after changing switches) and see if that fixes things for you as well?

    Dana M.

    1
    Comment actions Permalink
  • Avatar
    Jens Kiel

    Nice find, indeed, Dana. I flipped the switches and haven't had a keyboard reboot since. Thank you for following up with WASD Support, and kudos to David for the workaround!

    ~Jens

    0
    Comment actions Permalink
  • Avatar
    Mike Krumpus

    I would also like to report that I have not had the issue since setting DIP switches SW3 and SW5 to "on" as described by Dana. It has been over 1 week. Thanks to everyone in helping to report this issue and for chasing down a resolution with WASD. As a hardware designer and embedded software developer, it seems inexplicable that a device as simple as a keyboard would have this kind of instability (!).

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post