I would like to ask a question about the file "beekeeb_piantor_rpi_pico_vial.uf2." Should this file be loaded into both the left and right microcontrollers (raspberry pi pico)? After loading, my right-hand device actually has the layout of the left hand?

I saw a module that can extend Pico to use Pico.
https://detail.tmall.com/item_o.htm?spm=a230r.1.14.3.5b876a678HzI6f&abbucket=15&ns=1&releaseId=368216&bucketId=518000&id=696942327882&fbclid=IwAR2oCqNSngqnUsdNqu0lODWyCuugVSu8yv243aTVnz5hjKwXuEBntk5nL54

Not sure if this would work with the offical firmware?

Any debug ideas?
The left side works just fine, and if I plug in the right side to the pc the key presses show up, but the opposite side never works. I've used two different cables to connect the two together and desoldered the TRRS Jacks and put different ones on as well.

Hi, I stumbled upon this post on Reddit showcasing the v2 of the piantor using USB-C connectors instead of the TTRS. Is this version going to be open sourced or more details provided on the beekeeb website? I'd be interested in buying or building one myself.

For anyone interested, see the following Vial configuration file for the workman layout on the Piantor. I didn't do any optimization on special characters. There are some Umlauts on the first layer, because that's what I need in German. Otherwise, it's full English.

vial configuration

Is there anyway we can get the step files for the two case .stl files? Importing the mesh into FreeCAD or Fusion 360 to make modifications to the case is a bit unwieldy.

About a month ago I bought a Piantor Kit and have been really happy with it. But now the right side has stopped working for some reason. When connected directly to the computer it always presents itself as the RPI-RP2 mass storage device suggesting that it is in bootloader mode. Normally after dragging the .uf2 firmware file into it it would restart and reconnect as the keybord. But mine now always reconnects as the RPI-RP2 device again after flashing.
Interestingly the first time I connected it to a different pc it showed up in the little windows notification as piantor only to immediatly disconnect and reconnect as the mass storage device again. I have no idea what is going on here and I hope someone can help me with this

i've been trying to read the source and readmes, but i can't tell if there are any default pins configured for the RP2040 that deal RGB. I really could like just a few addressable RGBs to tell what layer i'm on as I often get stuck toggled on weird layers that I wasn't expecting.

Is it simply not possible to add rgbs to this board?

Anyone have an idea what is wrong?

I have happily used a Piantor keyboard for a couple of months now, and regularly take it with me to other places in a protective bag from Beekeeb. Now I plugged it in again and is seems to have stopped working correctly.

First of all, I'm aware unplugging the TPRS cable whilst powered can cause components on the microcontrollers to be damaged, so I have been very careful each time when packing away the keyboard. As far as I am aware I have never unplugged the TPRS cable before unplugging the USB C cable. However, as there seems to be no other change from the last time the Piantor still worked, maybe this happened without me realizing. Although, I don't believe I did.

Anyway, when connecting power to the (normal left-side of the) keyboard now the power LEDs glow much weaker than before, and fluctuate slightly. Connected this way, my computer receives no signals form the keyboard when keys are pressed. However, very infrequently a couple of key presses go through (the LED seems to also glow brighter when this happens).
The weird thing, to me at least, it that when I connect the USB C to the right side of the Piantor, both LEDs glow as normal and all key presses register fine. However, when plugged in on this side the key mapping is all wrong as the QMK config of the Piantor is configured relative to the left side.
Moreover, when just using the left half of the Piantor (meaning I connect the USB C to the left side without using the TPRS cable to connect to the right side) the LED glows at normal brightness and all key presses register correctly. But in this setup I am not able to use the right side, so I cannot use the keyboard in this way.
By the way, I can still upload new firmware without any problems.

It seems I could use the keyboard by connect to the right side and reconfiguring the keymapping. However, clearly something is wrong, and I do not want to damage the micro controller further.

Does anyone have an idea what is wrong with my Piantor? What could have caused it? Might it be a firmware problem that can easily be resolved? Or can I replace a component?
Thanks for any help.

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:

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:

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 🎉

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

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.

Would it be possible to create a version of the Piantor whose TRRS ports are replaced by USB-C ports?

Hello! I am loving my new piantor but I'd love to try my hand at printing snap-on tilts or a tilted case, by any chance is there a way to derive the 36 key case from the artifacts in this repo? I only see the 42, but maybe there is something I am missing.

Hello,
I had some major struggles with getting a YD-RP2040 to work on the PCB and have a PR ready to go that add notes to the README.md explaining how to make the YD-RP2040 work on the Piantor.

If you don't want to give me access to open a PR, I can paste the notes I have here for you (in the BOM table)

Thanks!

It would be nice to provide some information on the maximum size the keycaps can have without interfering with each other. I just got myself these transparent keycaps which are 17.5mm x 18mm, while normal MKB Keycaps are 17.5mm x 16.5mm. I either have to buy new ones or shave off a few mm of the height to make them fit (since I like the transparent esthetic).

https://beekeeb.shop should probably be https://shop.beekeeb.com.

Hi is it possible for you to share/add the stl file of keycaps ?

(Keycap Set for Kailh Choc Switch PG1350 Low Profile (3D Printed with Nylon)I

Unfortunately I found this out the hard way when I was building my own keyboard using the DIY kit from beekeeb.

Now I know there are already warnings in the beekeeb docs warning against this, but it is inevitable that at some point this will happen by mistake. I acknowledge that it is mostly my fault this has happened and have no intention to blame the designers.

I would rather ask, is there a way to make this safer so this doesn't happen again to other people?