This is quite fiddle. Lots of problems in the comments. Some hints that worked for me: 1) strum it once, not several times, let it read the resonance, not the actual pick. 2) put your finger, lightly, on the belt you are not tuning. I had a hell of a time, until I figured out it was resonating both belts and reading 2 sources. (Also, duh, make sure it's quiet and you aren't reading traffic noise or something.) 3) you probably need several plucks, make sure you get a few readings the same (not necessarily in a row- you'll get exactly what I'm saying when you do it) , and use that as your number. Without any adjustment, I could read 60 to 123, all while it sounded perfectly the same. Don't trust it until you get 3 or 4 the same, that look about right. If you have it tensioned to "that's probably close", don't believe any readings on the upper or lower limits of the app. You're probably within 10-20Hz just by guessing.
If your Y-Axis test fails: just loosen both belt tensioners and disable motors in the menu. Push the gantry manually to the very front and keep pushing the left side while you tension the left side. Make sure it stays at the front when you let go. Repeat for the right side. Both sides should touch the front simultaneously. This fixed Y-Axis-Selftest for me.
The belt tuner app is beyond useless. Is there anything else available that just runs on my iPhone to analyze the frequency? This is positively the worst part of building my CoreOne (beyond the days of work to actually do the upgrade -- in retrospect I should have just BOUGHT a new CoreOne and kept my working MK4S/MMU.)
what a faff! I really hope a MUCH better solution comes along when i upgrade to the next version. (yes i probably will despite the disappointing instructions and some aspects of the design. ad long as you stay open and dont outsource to china)
1) strum it once, not several times, let it read the resonance, not the actual pick.
2) put your finger, lightly, on the belt you are not tuning. I had a hell of a time, until I figured out it was resonating both belts and reading 2 sources. (Also, duh, make sure it's quiet and you aren't reading traffic noise or something.)
3) you probably need several plucks, make sure you get a few readings the same (not necessarily in a row- you'll get exactly what I'm saying when you do it) , and use that as your number. Without any adjustment, I could read 60 to 123, all while it sounded perfectly the same. Don't trust it until you get 3 or 4 the same, that look about right. If you have it tensioned to "that's probably close", don't believe any readings on the upper or lower limits of the app. You're probably within 10-20Hz just by guessing.
This fixed Y-Axis-Selftest for me.
This is positively the worst part of building my CoreOne (beyond the days of work to actually do the upgrade -- in retrospect I should have just BOUGHT a new CoreOne and kept my working MK4S/MMU.)