-
-
Notifications
You must be signed in to change notification settings - Fork 288
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
SplitFlap Display has three strange behaviors #117
Comments
It looks as though the display is binding at 'A'. Look closely around 38 seconds - it holds the 'A' position for ~2 seconds before it relaxes, which indicates that it's trying to move the spool but can't. I've noticed a similar phenomenon on my own test modules when the spool gets out of position. Scott may have better advice, but I'd start by checking that the flaps aren't hitting the enclosure anywhere except at the very top edge. |
thanks for the advice, I try to cut the displays again using the v.6 but if the problem was the beat of the cards it would solve only one of the three problems I am having. Let's say that the main problem I'm having concerns point 1. I still can't get the letter I want to display, it works randomly and resets itself continuously. |
My guess is that the motor is stalling/skipping due to not having enough torque at the higher speed. The behavior you're seeing is that the module will always rotate slowly (which has more torque) when it is searching for the home position at startup (or if it detects an error while moving it will also search for the home position before continuing), and then once it's found it will return to normal mode and accelerate up to full speed to go to the desired flap. It seems like everything works fine until it starts accelerating, so the first thing I would try is to reduce the speed - the default values are fairly aggressive and may not work if there is more friction, or you have a slightly different motor, etc. You can reduce the top speed by closing the Arduino IDE, then edit generate_acceleration.py (should be in the same folder as the arduino code) to change the MIN_PERIOD_MICROS value - maybe try setting it to 2400 to start, which should be half the default speed. Then run that script (should be directly executable on Mac or Linux, or you may need to invoke it via python from the command prompt on Windows), which will generate a new acceleration curve in acceleration.h. After that you can re-open the Arduino IDE and upload the code again and test it. If that works you can try some lowering the value again to find the fastest speed your module will allow reliably. |
Hi Scott, thanks for your reply and time.
here a video of this second problem: https://www.youtube.com/watch?v=e1L3PMftkNk&feature=youtu.be&ab_channel=DanieleMartini |
For the second problem, in your video you're typing spaces between |
Hello Scott, I finally finished my display but I need help for the last time. Here the display -> https://youtu.be/7kNUpaLQhlQ Daniele |
Ok I think I foud the solution By myself. The cards I cut are not very accurate so this creates small malfunctions in the system, but all in all it seems to me to be working. This weekend I try to make new cards and improve the functioning of my display. In the meantime, I made this little video to thank Scott for This beautiful project. https://www.youtube.com/watch?v=u_ax8iPwcRU&feature=youtu.be&ab_channel=DanieleMartini Thanks for everithing |
Daniele, I just noticed when watching your latest video - I think the front faces on your modules are installed upside down/inside out. The taller portion should be on the top, and the shorter portion on the bottom. If you flip the front face vertically (so the side that was facing in now faces out) I think that may help with reliability, as it will hold the flaps back more consistently at the top. See https://youtu.be/UAQJJAQSg_g?t=36 for a demonstration of why that position is key to reliable behavior. (it's unfortunate that the design is subtly asymmetric like this, but @dmadison has smartly added engraved orientation markers in an upcoming revision of the hardware design so it's hopefully easier to notice in the future) |
............. :-) ok thank you Scott. I'll fix it and see if my display start to work better making this change. |
Hello Scott, It's been a long time and I would like to finish this project started more than a year ago. I have completed the construction of a module and mechanically it should be ok, I have also done some tests with the sensor and it is correctly detected but I still cannot see the letter I want on my display. In this short video I show the three problems I'm having:
https://youtu.be/BHOUhOT_epA
I would be really grateful if you could help me complete this project.
The text was updated successfully, but these errors were encountered: