I’m trying to open a support ticket, but I can’t! I need to upload log files but the form ticket misses how tu upload from A1.
I’m a little frustrated.
Just updated the firmware and launched a new printing and I see the error: The resonance frequency of the X axis is low. The timing belt may be loose.
It is a new printer! I cannot believe it needs the belt to be straightened. Either A1 is a premature product or my one has defects.
What can I do? I’m just thinking to perform a return. I’m a little disappointed about the support. I cannot find a direct support for new customer and I cannot open a new support ticket without printer logs!
That’s pretty poor to be honest. Being a Cartesian style printer, it will have 2 separate belts, one for the x-axis and one for the y-axis. Both will have their own tensioners.
The wiki is not completed.
The video may give you an idea on how to adjust the belt but honestly, you shouldn’t have to try and figure it out yourself.
Bambu Lab is now well known for having poorer than expected customer service.
Agree, without proper documentation or instructions on repairs, this smacks of something released too early.
Sorry I can’t be of more help than that. Perhaps someone with the similar issue of uploading logs will chime in with a solution for your ticket submission.
Nope. I also have a new A1 with a few hours printing and also just got this error. Latest FW as well. Currently ignoring it and prints are coming out fine. That said, the process for troubleshooting is not clear. Going to let it slide for a bit and see if it clears itself.
I also had this problem.
Here’s the link to the belt tensioning procedure for the A1: (a bit hard to find)
// I somehow can’t post links, just search for belt tension in the bambu lab wiki
Pretty straight forward. After I did that the error was gone.
Same here. Printer is 3 days old with 3 prints. Error appeared after initial calibration. Prints come out fine, but cannot clear error. Checked belts and they seem tight and straight. Latest firmware, latest Studio, even tried new gcode_start from A1 mini. No joy.
Opened a support ticket today. We’ll see what comes back.