Firmware 2.02 Release Candidate 1 now available

dc42

I have just released this at https://github.com/dc42/RepRapFirmware/releases/tag/2.02RC1. This addresses some issue with stealthChop motor driver mode on the Duet Maestro, laser cutters/engravers, and a few other issues. See https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md for upgrade notes and the full change list.

incogizmo

Hi dc42,
Im using a Maestro and upgraded to RC1 today. I am not setting microstepping and motor driver mode so defaults apply and the stepper motors are quite noisy during moves after the upgrade. If I set the drivers to spreadcycle they are constantly noisy.

Confirmed with M350 all steppers are set to 16(on) and M596 P0-5 and confirmed driver mode is in stealthChop.

I downgrade to 2.02beta 1 with same config and the steppers are silent again. Let me know if there is anything I can help with to diagnosing / troubleshooting.

Thanks Nigel

zzing

I have also upgraded just now, and kept the stealthchop on my maestro. The movements are now definitely audible.

dc42

You can use the V parameter of the M569 command to set the speed at which the motors change over from stealthChop to spreadCycle. When they change over, there is a jerk (this is a feature of the driver chip, described in the datasheet). The higher the changeover speed, the worse the jerk is.

So you have two options:

Use a low changeover speed (the default in this release). The motors will be in stealthChop mode when the printer is idle, but the X and Y drivers will be in spreadCycle mode most of the time when printing.
Use a high changeover speed, perhaps a little higher than your maximum printing speed but lower than your maximum travel speed. In this case the motors will be quiet during printing moves but you may hear the jerk at the start and end of fast travel moves. If you do a travel move at a speed slightly higher than the changeover speed, then it may sound horrible due to switching back and forth between modes.

HTH David

incogizmo

Thanks David, turns out it was mainly my Z axis that was the noisy culprit. Changing the V value as you said has made the printer beautifully quiet agian.

On another note however I have noticed I keep finding the network services appear to be stopping during prints now with RC1. I can ping the host however cannot connect via FTP or HTTP. If I power cycle the device all is ok again, should I run a M122 from USB while in this state?

Edit - Ran M122 over serial
https://pastebin.com/Djm2bdUP

Edit2 - Suspicious of Simplify3D generated gcode, it was regularly stuttering during the last print, and even with 2.02b1 causing noticable blobs throughout the print. Sliced the same set of STL files with Slic3r PE and so far things are running significantly better.

Edit3 - I am using a RepRap Full grapical LCD and configured the menu to display XY&Z coordinates. It seems the display is updated with every destination coordinate from the gcode. I noticed the in high detailed areas such as Slic3rs Gyroid infil or really small holes the stuttering would occur. I have since removed the lines from the menu config and the stuttering appears to have stopped. I will keep testing with Simplify3d and gyriod infil parts and report back.

GizmotronX5000

Has anything changed in terms of build instructions with this release candidate? To absolutely nobody's surprise I have a new set of Eclipse errors, this time seemingly related to the compiler. About 300 errors like these:

Nearly all of the errors are coming from stl_algobase.h

I see that you have started moving some libraries out of this project, but it looks like that didn't start until after this RC.

Just to sanity check, I tried and succeeded at compiling the last 2.0 firmware just fine, so at least there's that.

dc42

@GizmotronX5000, I suspect you updated the RRF project without also updating the CoreNG project.

dc42

@incogizmo said in Firmware 2.02 Release Candidate 1 now available:

Edit3 - I am using a RepRap Full grapical LCD and configured the menu to display XY&Z coordinates. It seems the display is updated with every destination coordinate from the gcode. I noticed the in high detailed areas such as Slic3rs Gyroid infil or really small holes the stuttering would occur. I have since removed the lines from the menu config and the stuttering appears to have stopped.

Thanks for that, looks like we need to limit the refresh rate of the display or move it to a background task. I'll add this to the work list.

GizmotronX5000

@dc42 Should I be using CoreNG Master or dev-v2 at this point? It looks like master is more recently updated.

Edit: definitely master. Got it!

dc42

I've just released firmware 2.02RC2 so I am closing this thread and starting a new one. Those of you running 2.02RC1, please upgrade to 2.02RC2. If you were getting spurious "motor phase A/B disconnected" messages with RC1, then please report in the new thread whether you still get them with RC2.