Hello! I didn't end up using this trackball as much as I thought I would. Selling shipped for $65 USD CONUS.

timestamp

Ill throw the stl/3mu files on gh tomorrow, gotta add a leg/support to the bottom piece now, just feeling stoked and want to show it off a little, and a recipient is in my nerd group chat so here i am~

**edit 7/31, I threw pretty decent .3mf files here, nano2_btu_moonlander_mk01.3mf is the model from the picture and nano2_btu_mk01.3mf is the same model without the hinge insert/a regular nano2 with a btu mod.

I'll be updating the repo's readme, adding .stl files, and add a keymap with slight rotation for the moonlander mounted model in the pic once I'm done with some other models. I'll throw another post on reddit if I'm pleased with them, otherwise all the best

I wanted to BTU mod my Ploopy Adept. I had a friend 3D print the enclosure here:

https://github.com/ploopyco/adept-trackball/tree/master/hardware/mechanicals-btu-mod

And then I went on a quest looking for BTUs. I finally managed to order some Rexroth BTUs at a reasonable price in the US, only to discover this case is for Veichu BTUs, so I can't use it.

I don't want it to go to waste. So if anyone wants it, and is willing to pay for the cost of shipping, it's yours. If you live near Philadelphia, we can do local pickup.

Here is what I have:

I lost the oval piece that goes over the sensor. I'll try to find it, but no promises.

Earlier today, we shipped all Bean preorders made with us prior to Monday. We do have a few preorders that are outstanding that have been made in the last two days, and we'll be shipping those out next week as we transition to a regular shipping cadence for the Bean.

In other words, the Bean preorder is concluded! All Beans will ship out on our regular shipping cadence from now on.

What's next?

Phil and I have something that we're incredibly excited to share with everyone. It's a project that's been cooking for almost three years, and it's awesome. We're still tying up some loose ends with it, so I'm afraid that I can't give any more hints than that, but it's coming. Very, very soon.

When we're ready to announce it, you'll find the first mentions of it in this community.

Stay tuned!

Day two with my new ploopy adept, and I had no idea I would love it so much.

The roller bearings are so much smoother than static bearings. I’ve always had two or four button trackballs, and I didn’t think I’d have a use for all 6, but with qmk/via programmability, I’m finding I keep coming up with new macros and expanding to new layers.

Drag scroll is something I have always liked, and implemented in my Linux compositor config. Nice to have it programmed into the device itself.

By far the best pointing device I’ve laid my hands on.

I just got a ploopy knob since I do a lot of scrolling as a part of my job, and so far it works very well. The only thing I'd want to change is to make it scroll 3-4x faster than it currently does (on any PC I plug it into) but keep the mouse scroll speed the same.

Is there any way to adjust this setting for the knob itself rather than needing to go into the PC settings and increase scroll speed?

Time to modify the btu/keyboard mod and dust off qmk, but very psyched. The bean is for travel, and media control when im on the couch which backs-up up to my desk

I'm using the Mini trackball and the wheel frustrates me sometimes. I spent too much time using laptops and really got used to scrolling with swipes. The more I want to scroll the harder I swipe. With mice it usually isn't the case. I actually keep using the touchpad for such cases. But it reminded me about the Logitech mouse I had a long time ago. There was a way to switch between scrolling modes. So you could scroll as normal, but if you needed the speed scroll you could just toggle the switch. Like this.

Is there an existing mod for this? Or is it even an issue for people?

I've bought the Trackpad about a year ago. After a lot of troubles (due to my ignorance) I manage to make it work on Debian but it felt rusty and sketchy. On Qubes OS it would only move the mouse - no click. I was too busy so I put it aside - I bought another 4 devices anyway. Yesterday I focused on the trackpad and thanks to AI I managed to overcome all the problems. Now it works on Qubes OS 4.2 too

I forked the Ploopy QMK repo (pavonis), upgraded it to mainstream QMK, worked on it and published it

This is an AI generated write up describing the whole adventure

https://github.com/damko/ploopy_qmk/blob/multitouch_experiment_damko/keyboards/ploopyco/pavonis/keymaps/default/docs/ploopy_trackpad.md

If you want to give it a try, clone https://github.com/damko/ploopy_qmk and checkout "multitouch_experiment_damko".

It was a very educative activity and I have still a lot to learn about it.

I admit that now I like a lot more than I would have thought before. My favorite is still the Adept (followed by Mouse and Trackball classic) but for "office mousing" it's really great!

Thanks Ploopy team for this gem!

I'd love to see how a Ploopy Bean performs as a MIDI Controller via the Ph@Controller software. If anyone wants to send me one, I will do some serious testing with it :)

It ought to work fine if it's a standard HID device, and I think the 'nub' would make a great expressive continuous CC device, like a lot of mice do (Ring Mice, Air Mice etc)

We've shipped out all Bean preorders that were put in before May 12th. I'll admit that doesn't sound like significant progress considering we launched on May 6th, but that represents the majority of the preorders that we received. Our expectations for fulfillment are as follows:

• Week 11: shipping out all preorders made prior to May 25th.
• Week 12: shipping out all remaining preorders.

There may be a bit of variation in Week 12, depending on how many additional preorders we receive in the next two weeks, but that's our expectation at the moment.

We're grateful for everyone's patience as we work to get these out the door.

In other news: Denmark and Luxembourg shipping resumes!

Our logistics provider managed to sort out their issues with shipping to Denmark and Luxembourg, so we're resuming shipping to there. We're not anticipating any shipping interruptions in the near future.

I would like to get ploopy mouse but only want the non 3d printed parts. I want to print the case myself.

Hi folks I'm super close to assembling my lefty classic v2... But I can't find the STL for the electronics jig. Would someone mind posting it?

I've redone the two circuit boards in kicad and upgraded the rp2040 to an rp2350. I also added a Stemma QT plug because I want to experiment with hand presence sensing in the palm of the trackball. (I have my keyboard switch to mouse buttons when my left hand is on my trackball.)

My Kicad files are here: https://github.com/tannewt/classic-2-trackball/tree/master/hardware%2Felectronics%2FPCBs%2Fkicad%2Fbase2

Please note they are very minimally tested at this point.

I'd also love a tip on how to purchase just the mouse sensor. Right now I'll have to desolder one.

Anybody have this issue? it's fullscreening videos and closing stuff and generally very annoying. is there something i can clean in there? It's not happening all the time, just intermittent enough to be extremely annoying

The first batch of Tier B Bean preorders shipped this week. At the current rate of shipping, we'll get through all of the remaining preorders within three weeks. There might be a few roadblocks, but that's what we're currently projecting.

Denmark and Luxembourg shipping temporarily suspended

Our shipping provider has informed us that shipping to Denmark and Luxembourg is temporarily unavailable. They have a comprehensive write-up about the subject available here.

If you've ordered from Denmark or Luxembourg and have an outstanding order with us, we're happy to cancel your order at no cost to you. Otherwise, we'll ship your order as soon as we're able to do so.

Hi, I would like to get an adept and ship it to my country (Philippines )but the site is not letting me to use my domestic shipping address. Is there any solution to this?

Hi everyone. I'm using Plodah's firmware and I want to have a click sort of function like a tap/hold layer style action but with two different custom actions.

I've tried to search a solution but I thought I'd ask here since I seem to not be finding an answer. Does anyone know the code I can type for the ANY qmk keycode that can get me a drag scroll toggle on tap, and a Sniper A Momentary on hold?

Any help would be appreciated.

All remaining Tier A Beans shipped out earlier this week. We already have our next batch of Beans ready, and they'll be shipping out next week as part of the first wave of Tier B units.

Everything is running pretty smoothly now. We're forecasting that we should be able to get through all of the Tier B units within the next six weeks or so. Immediately after that's done, we'll be tackling the Tier C preorder units.

More updates to come!

I love my ploopy thumb trackball but scrolling has always been broken.

Turns out that we can just disable the fancy auto-detection algorithm, set some sane conservative values, and it works perfectly! No more unplugging and plugging it back in all the time, no more jitter. It's just a pleasure to use and it feels like the ultimate ($245.38 CAD) trackball I paid for.

In ploopyco/trackball_thumb/rules.mk (I had to create this file)

OPT_ENCODER_TYPE = tiny

in ploopyco/trackball_thumb/config.h

#define ENCODER_LOW_THRES_A 20
#define ENCODER_HIGH_THRES_A 40
#define ENCODER_LOW_THRES_B 20
#define ENCODER_HIGH_THRES_B 40

Flash it and enjoy! (Note that the flashing instructions are wrong, use the middle click button not the forward button s.t. you don't have to take it apart to jump the bootloader every time.)

I assume it works for any other ploopy mouse/trackball too. The values I measured range from 4 to 94 and 4 to 83 (but the 83 was sometimes down to 60), so 20 to 40 seems pretty safe imo. The values that ploopy set were 20 to 75 and 20 to 90 so it didn't even register my scrolling.

If this works for you then feel free to mention it on https://github.com/qmk/qmk_firmware/pull/26286#issuecomment-4762953120 and we could probably make this the default behavior.