-
Notifications
You must be signed in to change notification settings - Fork 245
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
[BFW-6351] [BUG] No phase stepping calibration in the Settings menu(CoreOne) #4461
Comments
Hello, phase stepping is always enabled on the Core ONE and it is not possible to disable it (because it wouldn't server any purpose). I don't know what the screenshot is from, but it's the document that's out of spec, not the firmware. |
Correction: phase stepping calibration for CORE One is planned, but we are still tweaking the procedure for 400 step motors and attachable accelerometer (XL has 200 steps motors and fixed accelerometer), therefore we have hidden the calibration from the menu. Toggle will not be present in the menu at all. CORE One is always using phase stepping, without calibration it is just not applying corrections to motor currents. Reopening the issue for you to keep track, but rest assured, we are working on this even without the github issue being open :) |
Correct me if I'm wrong, but is Phase Stepping the feature that was released for the XL that dramatically reduced how loud it was? I received my assembled CORE One on Tuesday, and I already had the Accelerometer that I bought for my MK4S, so I ran the Input Shaper calibration on the CORE One, and it's had a positive effect on the loudness. Being able to use the Accelerometer for Phase Stepping on the CORE One in the future is very exciting! |
So I got my core one yesterday, and I believe you are mistaken that phase stepping is turned on by default with no option to disable it. My core one printing the included lighthouse file is VERY loud, so loud that I heard it from the lower story of my house. I had to stop the print because there was no way I was going to listen to it for 22 hours. It is a lot louder than my MK4s and even my vorons. I am on firmware 6.3.0+10073. I am wonder if different firmware was sent to people with review units because a few of those users claim that the printer is “so quiet” but I have completely opposite experiences. |
I agree. It is way louder than my MK4S. Input Shaper calibration helped a little bit, but I'm hoping there are some future updates to address the sound. |
Looks like the X/Y motors are 0.9 degree motors, and according to the person above they do not have phase stepping setup for them yet. So then the core one doesn’t have phase stepping? Cause the XL uses 1.8 degree motors |
I can't confirm that. Yes, the frequency during fast movements is slightly louder/higher, but this is due to the rail on X. It's the same with the XL. At normal speeds, my Core One is actually pretty quiet. |
It is turned on on the Core one. But when uncallibrated, it does not have any effect nothing in terms of loudness – but it's computationally easier to drive the motors this way. When you will be able to calibrate it, it should silence the printer quite nicely. |
I'm just asking because my Core One vibrates very strange when I apply certain print speeds. It sounds just like the XL at the beginning when the Stepping Calibration phase did not yet exist. You can listen to/watch it here under this link: https://drive.google.com/file/d/1-NYn1wOrUK8HDYgAOzgrPsmcLKOG4P69 |
Well that’s kind of useless and misleading. I know the product description of the Core One mentions to have phase stepping but clearly it doesn’t. What is the timeline for this to be fully implemented into firmware? |
Printer model
Core One
Firmware version
6.3.0
Upgrades and modifications
No response
Printing from...
N.A.
Describe the bug
In the Settings Menu, there is no Phase Stepping but it should be.
How to reproduce
Navigate in the Settings Menü. Scroll through the Menu.
Expected behavior
No response
Files
No response
The text was updated successfully, but these errors were encountered: