-
Notifications
You must be signed in to change notification settings - Fork 19
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
Adjust carriage offsets to theoretically optimal values #214
Adjust carriage offsets to theoretically optimal values #214
Conversation
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
c7085a9
to
300ad5d
Compare
@jonathanperret as this is still in Draft state - is this meant to get into 1.0 as well? |
Apologies for the lack of information on this PR. My hope is that this would fix the mispatterning that's occurring with the lace carriage currently, which I think we should fix for 1.0. It is still provisional though until I can get reports that it doesn't break anything. |
300ad5d
to
d418b95
Compare
Closing this in favor of an upcoming PR which will touch only the lace carriage offsets. Looking into #40 more deeply I discovered that my idea of which offsets were optimal was slightly wrong. |
This is a potential fix for #40 by adjusting the needle selection offsets to values that are based on the physical properties of the machines.
It is still a draft for now pending more testing on hardware. I opened the PR so that a firmware is built and can be tested by going to https://code.jonathanperret.net/ayab-webtool/#pr=214