UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
I was asked to downgrade the firmware on my UM2 to 14.12.1 which I did. It seemed to fix the problem and I didn't see any problems on subsequent prints.
However, during a print, I acknowledged a sound that had been happening since I first started using the UM2 (I just hadn't got around to checking it out). It was a knocking/clicking sound, as if the print head was hitting something. On investigation it turned out to be the bed lead-screw (threaded rod) turning slightly, then releasing (this occurred mid layer, it wasn't moving to a new layer). Once I had found this was making the noise, I decided to place a light rotational force on the lead-screw with my fingers. As expected, the bed stayed still due to the holding torque of the motor, however, when the noise occurred, it released the holding torque and the bed lowered!!! I expect this was the problem all along, and that firmware version 14.12.1 has somehow improved the issue, but not resolved it. If anyone has seen anything like this, please let me know.
Link to post
Share on other sites
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
(Sorry, was out of office when this released)
This update is for...
All UltiMaker S series
New features
Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
A year after the merger of Ultimaker and MakerBotQQ, we have unlocked the ability for users of our Method series printers to slice files using UltiMaker Cura. As of this release, users can find profiles for our Method and Method XL printers, as well as material profiles for ABS-R, ABS-CF, and RapidRinse. Meaning it’s now possible to use either Cura or the existing cloud-slicing software CloudPrint when printing with these printers or materials
Recommended Posts
Orbis_PSL 0
Update:
I was asked to downgrade the firmware on my UM2 to 14.12.1 which I did. It seemed to fix the problem and I didn't see any problems on subsequent prints.
However, during a print, I acknowledged a sound that had been happening since I first started using the UM2 (I just hadn't got around to checking it out). It was a knocking/clicking sound, as if the print head was hitting something. On investigation it turned out to be the bed lead-screw (threaded rod) turning slightly, then releasing (this occurred mid layer, it wasn't moving to a new layer). Once I had found this was making the noise, I decided to place a light rotational force on the lead-screw with my fingers. As expected, the bed stayed still due to the holding torque of the motor, however, when the noise occurred, it released the holding torque and the bed lowered!!! I expect this was the problem all along, and that firmware version 14.12.1 has somehow improved the issue, but not resolved it. If anyone has seen anything like this, please let me know.
Link to post
Share on other sites