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

One side of the keyboard not working #22

Open
Hentuloo opened this issue Mar 6, 2024 · 3 comments
Open

One side of the keyboard not working #22

Hentuloo opened this issue Mar 6, 2024 · 3 comments

Comments

@Hentuloo
Copy link

Hentuloo commented Mar 6, 2024

Hi, I encountered a problem where only one part of the keyboard was working after assembly, depending on the connected power source, as shown in the picture where the LED only lights up on one side:

20240306_142000

I'm using Tzt raspberry pi pico board rp2040 16MB (dual-core 264kb arm low-power mikro computer hoch leistungs Cortex-M0 + prozessor) which was purchased on AliExpress.

While searching for a solution, I came across a diagram:

Przechwytywanie

It appears that the Vin and Vout pins are connected/shorted, whereas on my boards they were not connected. After soldering these pins on both parts, the keyboard started functioning 🎉

Przechwytywani2

The problem lies in the fact that the second board had insufficient voltage, which prevented it from starting up.

20240306_192853

I have created this issue requesting to add some information about it on the BeeKeeb homepage. It may help people like me who have bought similar microcontrollers.

@magicalpuffin
Copy link

This is a really great find. I bought a Aitexm Raspberry Pi Pico Board RP2040 TYPE-C 16 MB on Aliexpress and I was having similar issues where I could only get one half connected.

I tried soldering the Vin and Vout pins and was able to get both LEDs to light up, however, I couldn't get the Vial firmware to work.

I already permanently damaged one microcontroller when I tried to remove it so I'll have to abandon my build but this does have potential to help others.

image

@Hentuloo
Copy link
Author

Hentuloo commented Mar 7, 2024

@magicalpuffin

I also had other issues with the boards that I didn't mention:

  1. one of the board refuses to connect to the computer at all; it shows a message that the device is unknown. I tried various things, but it's likely that it needs to be replaced (I recommend ordering a spare from AliExpress right away).

  2. I also encountered problems with the remaining boards. Initially, I used the beekeeb_piantor_rpi_pico_vial.uf2 software available on the beekeeb website (https://docs.beekeeb.com/piantor-keyboard#firmware-for-clearing-the-flash)

image

but the keyboard didn't appear in the Vial software. In the web version (https://vial.rocks/) I noticed the console error "device read timed out!" (screen)

image

After several attempts, I decided to install the beekeeb_piantor_vial.uf2 software, which is the third option from the top, and both Vial web and desktop versions started working.

image

Before flashing any software, I cleared the memory using flash_clear.uf2 "Firmware for clearing the flash," which is also available on beekeeb (https://docs.beekeeb.com/piantor-keyboard#firmware-for-clearing-the-flash).

@mumblingdrunkard
Copy link

Just adding this for anyone searching for "YD-RP2040 Piantor".
My friend bought YD-RP2040 controllers and this same "hack" works on this.
Shorting Vin and Vout on the master side lets the other side receive power.

This happens because the original Pico has Vbus and Vsys instead of Vout and Vin, respectively. Vsys can source current and the Piantor PCB has a trace running from Vsys to the TRRS port and uses that to power the non-master side.
On the YD-RP2040 (and whatever the controllers here are) this pin is replaced with Vin, which cannot source current, and delivers no power to the TRRS port, although it can receive power from it.

This is/should be safe as you're only bypassing the diode that goes from Vin to Vout, but experiment with your cheap knockoff microcontrollers at your own risk.
I believe it's safe to short both sides provided you only power one side at a time, but you only need the short on the master side.

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

3 participants