[3.4.0beta7] Moves to back right of coreXY, after a few prints.
Random move to back right of coreXY, after a few prints. Will then hover around in this space of approx 1x1cm and spew out filament quickly. To stop, power off, then back on and coordinate system restored and usually get a couple print from file runs before issue returns. Unsure of cause.
2nd issue, with no changes to config.g or bed.g files from previous firmware version, sometimes works fine, however on last two runs, run outside bed and crashed. Cannot test for cause as printer 'disassembled itself on last repeat before I got to the power switch.
Been running with same config files (except for updates when firmware notes showed changes required) since 3.2.
I am running a duet 2 wifi v.14, with duex5
BLV MGN Cube coreXY with 3 way kinematics (custom).
Printer has been running in same configuration, except new heater, thermistor and fan for last 24months or more. Though not used often as been waiting for parts.
@dmandn Ok, new ballscrew in, re-checked and re-terminated some wires.
X,y and z operating normally for respected homes. Home all also fine.
No file changes made, still pointing towards firmware at this stage.
oliof last edited by
@dmandn you may need to enable (logging)[https://docs.duet3d.com/en/User_manual/Troubleshooting/Logging] to get some more info. Your config.g and an M122 either during the unexpected purge or right after emergency stop may have further pointers.
@dmandn Understood, though on this printer I really don't want to be replacing parts again due to another catastrophic failure (kind of procrastinating about it). Is is ok to downgrade firmware? Feel like a stable release might be safer for now. ....checking docs as not been through firmware doco for a while.
You can switch back to any version you'd like, just upload the zip file for the release you want to use.
o_lampe last edited by
during the unexpected purge
That reminds me of a situation I had last week with RRF3.3 stable: I sent a few commands to my printer through DWC console and while I was busy typing, suddenly a "filament change" message popped up.
I don't know where that came from, but it might be, that in case of the purge move something similar happend to trigger it?
WiFi error perhaps?
@phaedrux - Ah ok, I think I will do that, thanks.
@o_lampe Interesting thought. I didn't notice any comms issues though. This was also repeatable, seemed to happen after repeating the same print from file about 3-4 times. I found if I run only 1-2 times then power cycle it seemed to avoid the purge issue. ...right up to the go crazy and disassemble a ball screw, break through a couple plastic end blocks, etc issue it experienced.
I have now obtained a new ballscrew and got it functioning again, checked all config files and do not see any issues in the config files nor the print gcode.