-
Notifications
You must be signed in to change notification settings - Fork 1
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
Magnet for RPM sensing #100
Comments
The only issue I see is that it might be possible to place the magnet in the wrong direction, since it is a cube, which would render the hall effect sensor useless -- A disc magnet might be better? |
@GeorgesOatesLarsen I think you're right about the disc shape. I can fit two of the below magnets in the brush holder. |
I'm not sure whether that would work very well; The magnetic pole needs to face perpendicularly to the axis of the rotor shaft. The height of those magnets makes me think you might be planning to have them parallel to the shaft? If you can get the magnetic axis perpendicular to the shaft, then those would work just fine Actually, those magnets seem pretty tiny to me, what about: I am imagining a disc-shaped depression in the surface of the brush holder that said disc magnets could be glued into, and held as close to the EVPR board edge as possible Also, I am thinking since it would be ideal to have two magnets with flipped poles, we end up having to be careful about the magnet orientation anyways. Although with disc magnets, its just important that we get the magnets facing the opposite direction as each other, whereas with cube magnets, there are a large number of other orientations that are incorrect |
Need a magnet in the brush holder for RPM sensing.
@GeorgesOatesLarsen Below is the link for the magnet I'm considering for RPM sensing. It's the same width and depth as the brushes. (1/4"x1/4") so I should have minimal issue incorporating it. If there's any potential issues you see, let me know.
https://www.mcmaster.com/5848K91/
The text was updated successfully, but these errors were encountered: