Crazy Z movement on first layer
-
@work-horse-xl there is a known issue in RRF 3.3 when the movement queue is empty, then you do a move using just a motor on a CAN-connected expansion board, followed by a move that uses motors connected to the main board. So in your case, a M400 or G4 command (or any of several other non-movement commands) followed by an extruder-only movement and then a Z motor movement could result in the Z motor movement happening at the wrong speed. The time taken by the extruder-only move would have to be within certain narrow limits for this to occur.
My investigation of this is ongoing, however it has been reported that this does not happen in firmware 3.4beta3.
See https://forum.duet3d.com/topic/24660/issues-after-prime/110, https://forum.duet3d.com/topic/24553/rrf-3-3-does-not-respect-max-accel-in-first-moves-after-tc and https://forum.duet3d.com/topic/24624/z-motor-stalled-on-long-retracts for reported instances of this issue.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42
Thanks dc42. I will upgrade and see if it fixes it. Just so I understand this is related to the 3HC canbus board? That would explain why it's doing this. I was just running the Duet 3 board and recently added the 3HC and a second tool to the machine. Not long after that it started going down hill.I will let you know how it works out.
Thank you -
@dc42
When trying to upgrade to 3.4beta3 My wc keeps showing version 3.3?
Never had seen this happen. Is the files incorrect? -
Are you using an SBC as well or standalone mode?
How did you try to update to the beta?
If in standalone mode You may be missing some files needed. I suggest updating to 3.3 again first before updating to the beta.
Upload this zip file to the system tab in DWC first.
Then upload the beta firmware bin for the mainboard and expansion.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zipCheck the versions again with M115 and M115 B# where # is the canbus address of the expansion board. Check if they are both on 3.3 and then again after the beta upload see if they have updated. If not, manually update with M997 S0 and M997 B# where # is the canbus address of the board.
-
@phaedrux
Thank you. I was able to get it updated and now I have other issues.The Duet 3 will run in stand alone mode but will not in SBC.
I have made a fresh copy of duet pi lite and down loaded it fresh.
I keep getting DCS not started. It will run in Stand alone mode or at least it was.
Is this relate to the beta version 3.4beta?
Thank you for the help.
D
-
@phaedrux
Thank you. I was able to get it updated and now I have other issues.The Duet 3 will run in stand alone mode but will not in SBC.
I have made a fresh copy of duet pi lite and down loaded it fresh.
I keep getting DCS not started. It will run in Stand alone mode or at least it was.
Is this relate to the beta version 3.4beta?
Thank you for the help.
D
-
Ok, if you're running in SBC mode you'll need to use the unstable branch for software updates.
https://github.com/Duet3D/DuetSoftwareFramework/wiki/SBC-Setup-Guide#unstable-package-feed
-
@phaedrux
phaedrux I upgraded the firmware to 3.4 beta 3 using stand alone. So the Duet 3 and the 3HC have 3.4 beta 3 on them now.
I have done a fresh install on the sd card and updated the wpa file.
like I have always done. Now I'm not getting the DWC and just the error DCS not started. I don't know how to use the unstable branch for software updates so I have always updated the board either with usb cable or stand alone method.Thank you
-
Well to use the beta you'll need to update DCS on the Pi as well using the unstable branch as described in that link. Or just use standalone mode to test.
-
@phaedrux
Good morning phaedrux.
So I print really large files and couldn't load them on the SD card using stand alone mode. So what I did was disable all firmware related to the 3HC board. I unhooked cables and just run the single board Duet 3 using firmware 3.3 and SBC.This thing is really crazy now. I'm running mesh bed leveling also,It does it with mesh bed level off also. This is something that has just started happening.
Now the printer worked when upgrades was made and this has just happened over the last few time of using it. It's getting worse each time I'm trying to use it. The printer runs 25 to 30 days straight most of the time.
It's so bad now when printing the purge line moving down and back it's already running into the tape on the bed. You can hear the mesh bed comp working while traveling.
Is it possible I have a bad stepper motor? Could the main driver on the Duet be bad and missing steps?
Thank you
D -
Were you able to test the 3.4 beta 3 yet?
Can you post a video of what you're describing?
-
Sorry for the late reply as I have been busy and not working on the printer. I was not able to test beta version. My files are extremely larger and would not fit on the sd card in stand a lone mode. I have stripped down the machine to just one hot end trying to get it working like that with only the Main duet board with latest stable version 3.3.
I will try the next stable version when it's released. I have noticed that I am no longer having false run out of filament from my simple switch sensors now.
So I'm guessing there is also a bug in that part using can-bus boards.
I was having a lot of false triggers before. I had replaced the switches thinking they was bad when the problem is the firmware glitch it looks like.Thank you
D -
https://duet3d.dozuki.com/Wiki/Duet_3_firmware_configuration_limitations
Check out this list of limitations for Duet 3 and canbus boards including some limits for filament sensors.
-
@work-horse-xl said in Crazy Z movement on first layer:
My files are extremely larger and would not fit on the sd card in stand a lone mode.
How large are those files?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 285 MB and 893 MB are the sizes.
Also the 3.3 version has a major bug in it. My printer has stopped printing twice on day 8 to 10. It's never done this with 3.2 version.It will be printing and just go to 100% done when it was just at 70% for no reason. It's random as it doesn't stop in the same place. I'm going to load 3.2 version back on it and make sure there is nothing wrong with the file just to make sure.
D
-
@phaedrux All sensors and wiring related to the 3HC board is connected to it. The 3HC board only runs the second extruder and Hotend. I used this board because we have future plans to add more devices to the printer.
The second Hotend,Extruder,fan,temp,and second parts fan are all on the 3HC board. It is currently unplugged and just using the Duet 3 single Hotend until a fix is released to fix the crazy Z movement we are having.
Thank you for your help.
D
