ploopyco / classic-trackball Goto Github PK

Is there no option to purchase /just/ the electronics? I have printers, I have general hardware, I'd really like to just buy the PCB and maybe the ball? No?

Thank you for all of your work making a durable, reparable, customizable, libre trackball. I'm absolutely loving my Ploopy Classic Left-handed trackball, but I almost flashed it according to the wiki using the rev1 configuration before remembering that the black PCBs you showcased on reddit had rev 1.005 printed on them. It would be helpful to put a new caveat in the wiki for that and mention that you can assign a reset key in via to try to recover in the event of a mistake. I'd do it myself as a PR but I figure you have better info re: which Lefties shipped with which revision and if there are tricks to tell them apart without opening up the Ploopy.

Super cool project!

But please include a LICENSE for this repository, such as The TAPR Open Hardware License ("OHL") or the CERN Open Hardware License.

Hi there. I noticed the docs talk about putting new firmware on the board using an Arduino nano as an ISP programmer.
While that certainly would work, it's maybe a bit involved when there's already lots of cheap ISP programmer options available, like the USBtinyISP, the USBasp, and more.

That said, it shouldn't even be necessary, as all ATmega32u4 chips that come configured to use an external crystal (non RC versions), also ship with Atmel-DFU pre-programmed, and as such can be programmed over USB.

The datasheet has a mistake in Table 33.2, but I've gotten clarification that the statement on the first page of the datasheet

Parts using external XTAL clock are pre-programed with a default USB bootloader

is indeed correct:

Figured I'd let you know for future batches :)

Scrolling makes content move up and down rapidly at certain points while scrolling. How would we implement a patch? Is there a patch yet?

The section of Appendix C: QMK Firmware Programming describing which buttons need to be pressed to enter the booloader appear to be backwards at the top.
https://github.com/ploopyco/classic-trackball/wiki/Appendix-C%3A-QMK-Firmware-Programming

If you've got a right-handed Ploopy Classic, hold the "forward" button and plug in the trackball. If moving the ball doesn't move the cursor, then you've got QMK. (Try unplugging and plugging it back in without holding the forward button just to make sure that moving the ball still works as normal.)

But then later when it discusses it:

If you're using a right-handed Ploopy Classic, hold the "back" button. This is the button just to the right of the ball; it normally sits under your ring (fourth) finger. If you're using a left-handed Ploopy Classic, hold the "forward" button.

This later one appears to be the correct one as it's what worked for me.

simliar to #6, if there should be variants, one like the Logitech Cordless Trackman Optical T-RB22 would be cool. since the trackball is only shifted a bit to the right, this shouldn't be as complicated

An outdated protocol is an odd thing to ask for, but I thought I'd try anyway. Is PS/2 output something that you've considered? Do you have any thoughts on level of effort? I'm imagining it would not be compatible with the current PCB.

I'm interested in connecting a Ploopy Mouse to a keyboard running QMK firmware, as described here and shown here.

Being able to connect it to QMK would allow me to bundle mouse and keyboard functionality into a single device, which paves the way to an integrated design, bluetooth, and more. :)

I'm really not an expert, but a little overview shows Ploopy firmware using C++, which is also what the ps2dev Arduino library uses.

If I put my computer in sleep mode, it will wake up a few seconds after, if my ploopy is plugged in.

Any way to mitigate this issue?

Don't know if I'm doing something wrong, but when I open ScrollWheel.stp in FreeCad I see it has 15 holes, not 13 like the STL.
I probably wouldn't even have noticed this if it wasn't for the fact that when I had printed the step file, the scroll direction would be reversed. Not sure what causes this, but I'm guessing it has something to do with the holes being slightly smaller?

Hi! I let someone print me the REVD version of the BTU mod,
but the ball doesn't fit. With or without the BTUs in place. The hole seems too small..
Here are some pictures comparing the original top part with the new BTU part. Am I doing something wrong? Should I sand down the new part?
I believe @gbrnt designed this, I couldn't make an issue on his fork however.

UPDATE:
I sanded the inner part down, and also bought a 44.5mm billiard ball. Though there are still issues and I think the model is of the wrong size! Here are some images and videos regarding the mouse, which shows the way it's too small. https://photos.app.goo.gl/rMXwHFF1sCEd3Zp79

The person who printed the model for me gave me some additional insight as well! First of all, it seems unlikely that the issue was in the print. The person in question has according to his own statements, 8 years experience with 3d printers and a professional 3d printer that allows for 1x1x1m prints, also

the tolerance is 0.01 mm from the printer which is very accurate. so the model can only deviate from the drawing by 0.01 and that is not noticeable in the print. I think something about the drawing is wrong. but what struck me is that both drawings I received were exactly the same size.

He also sent me an image comparing the model to the original revd top stl model from github and there is indeed a difference in length of the model visible.

My conclusion at this point is thus, that the BTU model has to be increased in size. Though I would like some other professional have a look at it. Especially /u/FredCompany / @gbrnt
since he seems to have created the model.

USB C would make this much more interesting...

OS: Linux
Firmware: latest QMK

Issue: After using the trackball then stopping, after a few seconds trackball/mouse movement becomes completely unresponsive. If i click a button on the mouse then the trackball becomes usable again, and then the problem repeats after stopping the use of the trackball.

Already tried: disabling usb powersave via udev rule

I'm curious if it's possible to add a second sensor so it can do twist scrolling like the Kensington Slimblade. On a similar note, if it was possible to use for 1:1 rotation control for CAD/modeling programs. My understanding is that with two sensors you could track all three axis' of rotation.

I've been loving the trackball kit for almost a year. My hand fatigue has improved since ditching the normal mouse. There is just one thing about it that bugs me, the scroll wheel can get in a spot such that clicking moves it just so that it scrolls. This can be fixed with a detent to help the scroll wheel stay away from the transition points when at rest. I'm just not sure how to implement it. Something like a spring loaded nub that runs into the hole from the scroll wheel holder holder.
Thanks, Nick.

Hello!

I don't know if you've thought about handedness at all during this design, but how difficult of a process would it be to try and mirror the mouse over to create a left-handed version?

I imagine the PCB would also have to be mirrored, because the vertical section needs to be on the correct side, but would it just be a matter of flipping everything - stl's, and the pcb itself - along the y axis? Or is that going to spiral out of control into new and exciting problems?

I am having a hard time sourcing this sensor. would you mind sharing where you are getting them from? please and thankyou.

I apologize in advance, since I assume I am at fault here.

For the life of me I can not find the .stl file for the electronics assembly jig. Is this available? I have checked out various commits and I can not find it anywhere.

The jig is the following one:

Hi, I'm not sure how to put in the layer stackup/sequence to get the main PCB manufactured from JLCPCB.

Could you advise on this, and maybe put something in the wiki Appendix A about it?

Thanks

The link the source at Appendix A: Printed circuit boards is broken.

Do you have any Kicad files for the electronics and/or a Solidworks (or Autodesk Fusion 360) files for the casing?

Hi,

Fantastic project. Any plans to make a bluetooth version or add on?

Hi,
I've recently tried printing a rev C base and top (BTU modded).
I've just noticed after printing that the "rev C" version actually has "A" embossed on the base.
I've double checked what I printed:

The Rev. C STEP file has "A" on the base
The Rev C STL appears to have the correct "C"

It seems like only the STEP has the incorrect design - I'm not sure if it's only the lettering, or the whole model is old and not really rev C.
I also haven't checked any of the other versioning, I have only run into this one so far. Are the STL files more accurate? I don't want to need to reprint a lot of material.
Thanks

EDIT: Looks like the tops are the same.. The "C" BTU modded top I printed from the STEP file has no letter marking, the STL equivalent has a "C".. :(

First off, this looks like a pretty neat project. Very interested in building a mouse and upgrading from my Logitech M570. I however don't see the what dowel is required for the bearings (Step 17 in 3. Enclosure assembly).

Will look though all remaining files (if I find it, ill reply with the answer). Regardless, this information is still missing on both the Hardware and Assembly pages.

If I were motivated to customize both the enclosure and the PCB, how hard would it be to make a thumb trackball version of this? (Something like the MX Ergo.) I’m thinking that the electronics and firmware might be reusable, with some modifications to the PCB and plastic. Thoughts?

As a user of the Ploopy classic and nano trackballs, I would like the ability to hold down a key combination (both forward/back buttons together, for example) which would allow the trackball to act as a 2D scroll wheel, rather than a mouse input.

There are OS-specific solutions like Logitech Marblemouse software or AutoHotKey scripts that can accomplish this, but QMK also has the ability and would remove the OS restrictions and complicated setups.

I probably don't know enough or have enough experience with QMK to help, but I'd imagine this is a pretty common wish for trackball users.