Skip to content

Go60 Troubleshooting FAQs

Key Issues

A key is not triggering reliably or generating two characters

In our experience, the most likely cause is dust ingress into the key switch. Alternative causes can be mechanical switch failure, and layout/software issues.

Dust in the key switch can be easily solved by cleaning with compressed air. Please:

  • Remove the keycap
  • With a can of compressed air or an air compressor, blow into the gap around the switch stem
  • Please try to blow from multiple angles; sometimes it takes many attempts to clean dust out
  • If the problem is not resolved, replace the keyswitch

Further troubleshooting for software/layout issues:

  1. Did you recently change your Go60 layout? If you have, please check your layout to ensure that it is not using any timing-dependent behavior such as hold-tap, which can sometimes be mistaken for a switch issue.
  2. If your host computer is a Mac and you are using an app like Karabiner Elements which intercepts or processes keyboard input, try temporarily turning off that app to determine if it is the cause.

A key is occasionally held down, and generates a stream of repeat characters

Please check if you are connecting to the host device using a USB cable or a BLE connection. This problem is typically caused by a weak BLE connection.

Please see "Go60 is not sending keystrokes. How do I fix this?" for further information.

Trackpad Issues

The trackpad is not reliably recognizing all touches

The trackpad sensitivity depends on many environmental factors, such as humidity, temperature, RF noise in the environment and earthing.

If the trackpad is missing some touches, please adjust the trackpad sensitivity.

Connection Issue with Host Devices

Go60 is not sending keystrokes. How do I fix this?

The RGB indicators are very helpful to determine the cause of connection issues. Please see BT and USB indicators.

To activate the RGB indicators, tap the MoErgo key (also known as the Magic key) on the left side.

The RGB indicators can tell you:

  • Which device Go60 is currently sending the keystrokes to
  • Which of the Bluetooth Profiles are paired, and which of the Bluetooth Profiles are connected

To debug a connection issue, try the following steps:

  • Use the RGB indicator to determine which device (i.e. USB or Bluetooth Profile) Go60 is sending the keystrokes to. Look for the thumb key with a white LED.
  • If the device Go60 is sending keystrokes to is different from the device you want, try switching to that device as described in "Selecting BT Profile and USB-connected device".
  • Check the RGB indicator color of the device you want to send the keystrokes to. The color should give you a good idea why Go60 is not sending keystrokes to the device you want to send to.
  • If Go60 indicates that the desired device is not paired, then try pairing procedure as described in "Pairing with a BLE host".
  • If Go60 indicates that the desired device is paired but not connected, then it is possible that the other side has Bluetooth turned off or otherwise lost the Bluetooth pairing information. Try the "Troubleshooting" subsection.

Note

Bluetooth BLE uses 2.4 GHz microwave which is primarily line-of-sight. If the BLE path between the host and the left hand of Go60 is blocked by a conductor (such as a metal case) or something with high water content (such as a hand or a cat), the signal strength will decrease. Other common issues include missing BLE antennae on the PC. NOTE: If you are dual-booting with multiple OSes, very specific setup configurations are required to simultaneously pair the same device with multiple OSes on the same computer. Please see ZMK documentation for more details.

BLE connection issue with macOS

If you are experiencing BLE connectivity issues with macOS, please upgrade your Go60 to the latest production firmware.

If you have an older Intel Mac with the BCM_20703A2 (or similar) BLE chipset, you may also need to apply the workaround below.

Workaround for BCM_20703A2 BLE chipset

Please use the latest firmware, with the following Advanced Configuration settings overridden in your layout in the MoErgo Layout Editor:

  • BLE_CTLR_PHY_2M=n

Keystrokes no longer appear after connecting to USB charger or power brick

Is your left half of Go60 connected to a USB charger/power brick?

Some chargers & power bricks pretend to be a USB host device. If your Go60 has selected to use USB as the primary output device, then the Go60 could be tricked into sending the keystrokes to the charger/power brick instead. To check if this is indeed the situation, please disconnect the USB charger/power brick and type on Go60. If this is indeed the cause, to fix this problem, switch Go60 to output to the BT Profile of the host device you want to connect to.

If the above procedure does not fix the problem, please see Go60 is not sending keystrokes. How do I fix this?

I cannot pair with a Bluetooth host device

A successful pairing requires both the host device and Go60 to recognize the pairing.

If you have previously paired a host device with a Go60, and subsequently removed the pairing from one side, attempts to pair the same devices again will fail.

To successfully re-pair them, you need to remove the pairing information from both sides before trying again.

To do so, please refer to the "Unpairing from a BLE host".

After unpairing on both the host and the Go60, try pairing again.

If you still have problems please see the other FAQ entries in this section, in particular "Go60 is not sending keystrokes. How do I fix this?" and "BLE connection issue with macOS".

If you have no problem pairing with other computers or smartphones, but have problems with one specific device, please see "Problem BLE pairing your Go60 with a specific computer but the Go60 can pair and work reliably with other computers and mobile phones over BLE"

Problem BLE pairing your Go60 with a specific computer but the Go60 can pair and work reliably with other computers and mobile phones over BLE

If the pairing issue seems to specifically affect a particular PC, but the Go60 is reliably pairing and working over BLE with other PCs/mobile phones, then please follow the following procedure:

  • Some desktop PCs (especially common for home-built PCs) have a missing or disconnected BLE/WIFI antenna. Please inspect your PC to ensure that the antenna is actually installed.

  • Some PCs, especially older ones, have certain BLE/WIFI chipsets that require a specific ZMK Advanced Configuration workaround below.

Workaround for certain BLE/WIFI chipsets

Please use the latest firmware, with the following Advanced Configuration settings overridden in your layout in the MoErgo Layout Editor:

  • BLE_CTLR_PHY_2M=n

Chipsets known to require this workaround:

  • Intel AX210
  • Intel AX211
  • Broadcom BCM_20703A2
  • Realtek chipsets (commonly used in BLE dongles)

While pairing with macOS, "press the button on the right side of the left hand shift button". Which button to press?

Which button to press? That depends on what locale you are using. MacOS is asking the question in order for it to guess which locale your keyboard is intended for. The button that macOS expects you to press is the button which is to the left or right of the shift button in the traditional-layout keyboard for your locale.

So, for example, if you are using the ANSI (U.S.) locale:

  • The button for "press the button on the right side of the left hand shift button" is Z
  • The button for "press the button on the left side of the right hand shift button" is /

What BLE dongles are known to work with Go60 firmware?

This is not an endorsement or recommendation.

These are some of the dongles that some customers had good experience with:

Dongles to avoid

Please avoid dongles with the ATS2851 chipset. Although some users managed to get their dongles working with ZMK, others couldn't.

USB connectivity issue with the host computer

If you are having issues with USB connectivity issue between the Go60 left hand and the host computer, please check the following:

  1. Using the BT and USB indicators activated by single tapping the Magic key, determine if you have selected USB as the output. If not please manually switch to USB output (on a factory default layout, press the magic-left alt combo).
  2. Are you using the white cable that comes with Go60 to connect the Go60 left hand to the host? We have found that damaged cables and out-of-spec cables are a common cause of USB connectivity issues. To test this hypothesis, please use the white cable that comes with Go60.
  3. Are you directly connecting the Go60 left hand to the USB port of the host computer? We have found another common cause of USB connectivity issue being a bad USB hub. To test this hypothesis, please directly connect the Go60 left hand to the USB port of the host computer.
  4. If the ZMK settings are corrupted, a common symptom is a weird USB connectivity issue. Please perform the Configuration factory reset and re-pairing left and right halves procedure.

Note

The Go60 right hand does not send keystrokes to the host computer, even if the right hand is connected to the host computer with a USB cable.

Connection Issue Between Two Sides

The right half is not typing but the left half is typing fine

Please try the following steps:

  1. If using the wired-split TRRS cable, is the TRRS cable connected to one half but not the other?
    Try firmly disconnecting and reconnecting it on both sides.

  2. Is the right half powered on?
    Check that the power button on the right half is pressed in.

  3. Is the right half out of battery?
    Try plugging in the right half to a charger, and try again.

  4. If you have recently updated the firmware, did you upload the same firmware to both halves?
    If you are not sure, please reload the firmware to both halves again.

Occasionally the two halves may fail to establish a connection when you power on the right side. This is rare, but it may happen.

  1. Power off the right half and power on again. See if that fixes the problem. If not try again a couple more times.

If not, there may be an extremely rare chance that one of the two halves has lost the Bluetooth pairing information with the other half.

  1. Attempt re-pairing the left and right half according to the Configuration factory reset and re-pairing left and right halves procedure. Please note that this will wipe off all the configuration information stored, including BT profiles.

RGB

The left half RGB LEDs are not working

Tap the MoErgo key (also known as "Magic Key"). If some RGB indicators turn on, it means that the battery is running low.

When the battery runs low, the Go60 automatically switches off RGB to conserve battery power.

If no RGB indicators turn on when you tap the MoErgo key, the battery may be completely depleted or the power may be switched off.

The right half RGB LEDs are not working

  1. Try typing on the right half, to check that it is not a connection problem between the left half and the right half.

  2. When the battery runs low, the Go60 automatically switches off RGB to conserve battery power. One way to test this is to plug the right half into a USB charger. If the RGB LED comes back, then the battery is running low.

  3. Try switching off and on the RGB light pattern a couple of times. ZMK does not sync the RGB pattern between left and right when you power on the right half.

  4. If you have recently updated the firmware, did you upload the same firmware to both halves?
    If you are not sure, please reload the firmware to both halves again. Right half RGBs not working is a common symptom of the left and right halves having incompatible firmware versions.

Firmware

How to put Go60 into bootloader mode?

There are two ways. One way requires a correctly functioning ZMK firmware.

The preferred method "Entering bootloader mass storage device mode on power-up" works even if the ZMK firmware is not functioning.

I am having problem loading firmware from macOS Ventura

Before Ventura v13.1, due to an issue with Ventura v13.0 and beta versions, it is not possible to simply copy the Go60 UF2 firmware file to the finder to update the Go60 firmware.

This problem has been resolved by Apple on macOS Ventura v13.1. We recommend that you upgrade to Ventura v13.1+.

How do I find what version of firmware I am running?

ZMK currently does not provide this capability.

If you are unsure what version you are running, the best solution is to generate the latest version with the MoErgo Layout Editor and flash two Go60 halves.

When transferring firmware, the Go60 seems to prematurely exit bootloader mode. Windows throws an "operation interrupted" error

This is a timing issue between the bootloader and the OS. Effectively the Go60 bootloader processes the new firmware and reboots too quickly for the OS to receive the completion acknowledgment.

This is okay and nothing needs to be done. The firmware has been flashed successfully, and Go60 should work as normal after it has finished rebooting.

Note

This issue also affects macOS

When transferring firmware from macOS, the transfer fails with "The operation can't be completed because one or more items cannot be found. (Error code -43)"

The filename of the firmware file is too long. Please rename the firmware file, while keeping the same extension (.uf2)

The workplace I.T. policy blocks access to the USB port on the PC. Is there any workaround?

To load firmware onto Go60 from a PC, necessary privileges to access the USB port are required. Some workplace I.T. policies limit such access privileges.

One workaround is to use an OTG USB cable with your phone. Many (but not all) phones support USB mass storage devices via an OTG USB cable. Please note that this method is not officially supported by MoErgo due to the vast variety of phones, however, it may be worth a try.

Where can I learn more about ZMK?

ZMK is a powerful firmware, but as a result, it can be somewhat complicated.

On the MoErgo Discord server there are the #go60-zmk-mod channel for ZMK-related discussions and #go60-keymaps channel for keymap/layout-related discussions.

The best place to start learning ZMK is with their excellent documentation.

ZMK has an active community on the ZMK Discord server. This is a great place for technical discussion around ZMK.

Where can I find Go60's ZMK repository?

If you are looking to compile ZMK firmware without using the MoErgo Layout Editor, check out Go60's ZMK configuration GitHub repository.

If you are planning to modify the ZMK firmware source code, check out the official Go60 ZMK distribution.

Other

The right half battery life is very short. How can I fix it?

This is a known issue for Go60 units with firmware that has persisted "bad" configuration data. It can be easily fixed.

Step 1: Charge the right half with a USB charger. Keep it connected while performing the subsequent steps.

Step 2: Power off and power on both halves.

Step 3: Switch on RGB LEDs (for the default layout in the US locale using the key combo magic-t). Make sure RGB LEDs are operating on both halves(unless you have a Kickstarter Batch Standard Edition without RGB on the right hand). If this step fails, please contact us.

Step 4: Switch off the RGB LEDs (for the default layout in the US locale using the key combo magic-t). Then wait for at least one minute without powering off the two halves; this is necessary for persisting the new configuration.

Step 5: Keep the right half charging for 4 hours.

This procedure should fix the problem.

The red LED next to the power switch is not working

We have not yet defined the behavior of the red LED while the Go60 is running ZMK firmware. The red LED is not a charging indicator. We are still trying to find the best use of this LED while running ZMK.

The behavior of this LED however is defined when Go60 is in bootloader mode:

  • Slow pulsing indicates that the bootloader is operating in mass storage device mode and is ready for firmware loading

  • Fast pulsing indicates that no ZMK firmware is found and the USB is disconnected

Will Go60 work with my KVM?

We recommend that you use a powered KVM such that it can provide enough current to the Go60, especially if you intend to turn on the RGB LEDs on your Go60.

Furthermore, not all KVMs implement an adequately complete implementation of HID protocol. As such some models of KVMs are not compatible with certain keyboards which may include Go60. There are no hard and fast rules; we recommend that you enquire with the KVM vendor and run actual tests.

How to clean Go60?

The cleaning procedure:

  1. Use air to blow dust out
  2. Or gently remove keycaps, if you want a deep clean between key switches
  3. Use a very slightly damp cloth (but not too damp) to wipe down the Go60 keyboard body. Water and electronics don't mix.
  4. Do not use organic solvents under any circumstances

Please also see How to look after the wooden palm rests.

How to look after the wooden palm rests?

The caps lock, num lock & scroll lock indicators are not working

ZMK has known limitations with these indicators over a Bluetooth connection on certain operating systems.

However these indicators should work if the Go60 is connected to the host device via a USB cable.