Topics created by janusofdoors

@T3P3Tony I don't run anything more beefy than a big 3D printer but I know Duet is certainly designed for tasks like running a CNC Mill. How would I have fared if I had a similar error during a milling operation? I understand the default is already set but I do think picking a policy for the event should be enforced somehow for new builds.

@vishiano we only found that bug a day or two ago, so it hasn't made it to a bug list yet. We do sometimes add a "known issues" section to release notes. Eventually they will be moved to github issues.

@dc42

Upgraded from 3.2 to 3.3b. Only issue I ran into was the upgrade created a firmware directory but didn't move the firmware files from the sys directory. Pretty easy fix for me to move the files but wanted to make sure you were aware of it.

Update seems to have fixed the issue. I did the same M122, M122 B21 during the print and it shows no lost CAN messages. Doing M122 B21 did hiccup the print but no error message and it was much less noticeable than before. toolboard_good.txt

The print also came out similarly to when the extruder is wired to the mainboard. I was getting worried that the problem was my mainboard, thanks for the help!

@Phaedrux
I tried using the new connector that came with the new toolboard. no luck. I'll try some more stuff tomorrow.

Would it be possible to setup both toolboards and have them both extrude a print simultaneously? Even if no filament is loaded I should be able to tell if the extruder is showing the issue.

Thanks dc42 & Phaedrux!

@oozeBot Thanks I'll give this a shot after my print is done 😁

@Phaedrux Alright thanks for the help, I guess I can substitute M226 in the gcode for now.

@Phaedrux That did it, thanks for the help.