Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UHK 80 Left keyboard half issues. #1075

Closed
Salivala opened this issue Jan 7, 2025 · 14 comments
Closed

UHK 80 Left keyboard half issues. #1075

Salivala opened this issue Jan 7, 2025 · 14 comments

Comments

@Salivala
Copy link

Salivala commented Jan 7, 2025

Left half of keyboard appears to need the connecting cable even when connected.
When disconnecting connector cable and reconnecting, left half seems to turn off and on repeatedly, need to unplug and reconnect right usb cable.

@Salivala Salivala changed the title Left keyboard half issues. UHK 80 Left keyboard half issues. Jan 7, 2025
@mhantsch
Copy link
Contributor

mhantsch commented Jan 7, 2025

Does your UHK80 have batteries?

@pcooke9
Copy link

pcooke9 commented Jan 7, 2025

This sounds like the left half connection issues mentioned throughout @Zetaphor's thread, starting from this comment here:
#1059 (comment)

@Salivala
Copy link
Author

Salivala commented Jan 7, 2025

Does your UHK80 have batteries?

no

@Salivala
Copy link
Author

Salivala commented Jan 7, 2025

They keyboard reconnect issue doesn't seem to be happening now. Not sure why.

False alarm, it's still happening.

@Salivala
Copy link
Author

Salivala commented Jan 7, 2025

another thing of note, for the cable needing to be there, the pins seem to be connecting to eachother fine; agent knows when they're together and they're apart, when the cable is attached, so it's using that cross data with the pins. On the UHK 60 you didn't need the cable when both halves are connected, but it's almost like there is no power transfer happening if it's just relying on the keyboard pins.

@Salivala
Copy link
Author

Salivala commented Jan 7, 2025

I also have modules for both sides and they both work properly.

@pcooke9
Copy link

pcooke9 commented Jan 7, 2025

False alarm, it's still happening.

Try disconnecting the bridge cable, reset the left half with the reset button on the back of the left half, and then reconnect the bridge cable after it finishes the reset.

That works to temporarily stop it for me.

If that doesn't help, try re-flashing the firmware without the bridge cable (both halves joined in wireless mode).

EDIT: Sorry, I don't think power is transmitted with the halves joined physically, like the UHK60. So, obviously with the bridge cable disconnected, you'll probably need both halves connected to host via USB, since you don't have batteries.

@kareltucek
Copy link
Collaborator

uhk80 halves communicate over uart. Modules communicate over i2c.

I infer from this that they are not supposed to communicate over the bridge cable as I am not aware of any mechanism that would be switching the protocols on the pogo pins.

@Salivala
Copy link
Author

Salivala commented Jan 7, 2025

So this is expected behavior? I just assumed because the uhk60 could do this that the 80 would be able to. Doesn't really matter to me personally since i just keep the thing attached anyways but I'm just going through the board and seeing if everything is g2g before i get back to using it

@Salivala
Copy link
Author

Salivala commented Jan 7, 2025

image
image
I also get these phantom module connects

@Salivala
Copy link
Author

Salivala commented Jan 7, 2025

in both instances my halves were together.

@Salivala
Copy link
Author

Salivala commented Jan 7, 2025

20250107_141121
could it be due to the connectors being too far apart? with the keyboard together if i put a little pressure with my wrists to separate the halves it will also read as split.

@mondalaci
Copy link
Member

Unlike the UHK 60, the UHK 80 halves don't communicate and power each other via the pogo pins.

Please create a new Agent issue for phantom modules and delete the original issue template when creating new issues.

@mondalaci
Copy link
Member

Closing as a duplicate of #1079.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants