#Wooting 80He will not turn on after doing firmware update to most recent beta version.

1 messages · Page 1 of 1 (latest)

cerulean canyon
#

I recently checked the wootility software for any updates that I could do, and downloaded it to the most recent version. Everything was fine until I changed the polling rate to 8KHz and then it randomly turned off. So I tried restoring it using the trouble shoot, and it said Error ID: Waiting for device reconnected. I’ve tried every possible solution and still no luck whatsoever and always gets stuck at that part. My main concern is if this would allow me to atleast get a return as I’m guessing there is warranty. Before this, I had a lot of problems with it randomly turning on and off aswell, So the USB could have just gave way and broke. Ofc if anyone has any suggestions on a possible solution that’s not listed here I would love to hear them!

fallow crestBOT
# cerulean canyon I recently checked the wootility software for any updates that I could do, and d...

Thanks for posting your support request!

Note: #community_support is only for answering general questions and for troubleshooting.
All order-specific and shipment-specific support must be handled via the Wooting Support Wizard*
(You need to create an account on the Wooting Hub, using the same email address as your purchase. The account is not created for you automatically!)

Troubleshooting your Wooting Keyboard? Try these steps first!
Basic Troubleshooting

Questions about shipping, or what to do if your shipment has a problem?
Possible Problems During Shipping (with Solutions)

Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, update your shipping address, and much more.

Is your order about to ship and you need to pause it for any reason?
Place it on hold via the Wooting Hub!

Do you need to...

All of these types of requests need to be made via the Wooting Support Wizard!

dusty glade
#

If you had issues with it turning off then it sounds like the JST cable between the main PCB and the daughterboard is loose and needs to be reconnected. It can be done by opening it up and making sure it's making good contact

celest umbra
#

From beginning to 3:30 is relevant for your case

crisp quiver
# cerulean canyon I recently checked the wootility software for any updates that I could do, and d...

i Don't think this is a loose JST cable

as the trigger was polling rate and the keyboard not emulating correctly once it restarted for the changes to take effect (requires a power cycle)

and the error "Device reconnect" tends to indicate the keyboard is connected to the system and completes a firmware upload but when it restarts to emulate the device it is not detected hence the error.

it looks like the system dosnt like "8000hz" polling some points iw ish to check

  • How is the keyboard detected in device manager and what drivers are visable

Go to device manager - Select "View" - Select "Device by container" - Find wooting 80HE and expand the device tree and take a picture

  • What is the state of the keyboard
    Can type Yes/no
    RGB off/on
    Wootility detects devices Yes/no
dusty glade
crisp quiver
#

ohhh missed that part

#

may relate to a signal issue and a barely attached JST cable but that is a theory

vast scarab
crisp quiver
#

Wooting Restore will only use USB Full-speed, so I think they have an issue with USB Hi-speed.

For reference:

  • 8000Hz polling uses USB Hi-speed and sends/receives information at 0.4 volts.
  • 1000Hz polling uses USB Full-speed and sends/receives information at 3.3 volts.

If the JST cable is barely attached, the signal could have issues and cause more problems.
Meanwhile, 1000Hz in Wooting Restore is detected fine.

It is really hard to say. i would need to see how the device is currently connected in normal mode as it may just be a driver issue .

  • Loose jst cable
cerulean canyon
crisp quiver
#

I would need to check the image of device manager with view - device by container selected

To check if there is a driver issue

cerulean canyon
grand girder
crisp quiver
#

Technically, it is a rare issue compared to the total units sold. for references this happens to less than 1% of total 80HE units sold.

That said, this still happens more than we would like. We have made various rolling changes to the product over time to help prevent or reduce the number of cases, which has helped. Sadly, it can still happen. For reference, some of the changes include:

  • Longer JST cables (less tension on the cable)
  • Adding foam to guide the cable to the correct location (PCB change)
  • removed cable channel (Case)
  • Shake tests to check if it comes loose before packing

We are still planning to make further changes, though this can take time.

grand girder
#

You produce 1500 keyboards/day, the thing is that the "JST problem" happen during the lifespan of the product, it can happen after 1 month (like me) or after 2 years, it is really hard to get precise percentage of defect on this case.

SwitchyHeart This said, i wish you the best to fix this