Best posts made by Charlie

Thank you both for your replies! I tried a normal diff checker, but there was far too much different for me to compare. Using "gcodeanalyser.com" (amazing tool, way better than the "gcode.ws" that I used originally which didn't depict accelerations) I think I found my issue.

First image is using Cura 4.5 (no issues).

Second image is using Cura 4.6 (stuttering issues).

Same exact settings, same layer, but notice how Cura 4.6 speeds up and slows down many more times during the layer. I would assume that it would accelerate once for the layer start, and again for the small radius corner (as in 4.5) but 4.6 changes a lot more.

It's worth noting that the version of Cura that @Phaedrux kindly provided does not appear to have the issues that "stock" Cura 4.6 seems to have.

Please let me know if I'm mistaken with any of my assumptions.

@Sindarius

Your solution appears to have worked! I deleted M551 and no more error messages in Safari.

@fcwilt
Z Probe readout value is 0, and remains 0 for the entire homing attempt.

@NitroFreak First of all, thank you for printing items to fight COVID!

Looks like you have many "Hiccups." In my experience, this has to do with very high microstepping. In your config.g file, what does it show under "M350"? For instance, mine is "M350 X16 Y16 Z16 E16 I1".

@alankilian

Neither do I.

No worries! You've been super helpful, and way more knowledgeable than myself! I greatly appreciate your time.

Since changing the browser or removing the password GCode fixed this issue, Im super happy.

Upon some preliminary testing, it appears as though the wiring may be to blame. In a few days Ill have the time to do some more digging. Ill keep you posted as to the results. Thank you all for your help so far!

As an update, I was able to eliminate the stuttering (the banding is likely an issue for another day, lol) by re slicing in Cura 4.5 (Cura 4.6 was where I was having the issues).

Settings are:
No wall overlap compensation
Max resolution: 2.333 mm
Max travel resolution: 0.8 mm
Max deviation: 0.05 mm

x16 Microstepping with interpolation

Still had Look Ahead Errors (forgot to copy the M122) but MaxWait was 0 ms.

@AndyE3D This may sound simple, but how do I get the "v, a, cf" display in SBC mode? I enabled debugging using the M111 P4 S1 in dwc, plugged my computer into the USB port on the Duet, and I tried Serial Tools on a Mac, but I dont get any response. Im assuming that this may be correct for standalone mode, but not for SBC. Is this correct?

After a long hiatus, Ive come back to the project and it definitely was a wiring issue. The silicone ribbon cable jacket was completely intact, but the wire inside was frayed. Hopefully with a Toolboard installed, I should have less wiring issues. Thank you again to everyone for your help in troubleshooting!

@CCS86 Yes, Cura 4.6.1 does appear to fix the issue (at least it looks fixed in "GCode Analyzer"). Much appreciated!

@AndyE3D I also tried using YAT on a PC, and was unable to get a response from any commands that I made (like M122 or M115). Im assuming that this may have something to do with SBC mode, or Im making some other error in the setup.

Just want to second this. I would love if it were a GCode value (like an M203, but for a ceiling on the flow rate). That way it could be input into the start GCode or filament files, and could be changed/checked via the console on the DWC.

@jay_s_uk Thank you so much for your help! I must've missed this.

@Notepad I completely agree. "Acceleration/Velocity constant." Does not help much when trying to tune settings. I was hoping to be able to report back how the calculations are made after doing some testing (and reverse calculating the current factor), but without being able to get a debugging output Im unable to help.

@Richard-F It would absolutely work. Ive seen a few systems using this, and Ive used it myself in the past. I know the Duet supports it, though Id recommend looking around to see how others have implemented it. (eg: using printed levers to contact the filament instead of the switch lever contacting the filament directly)

@AndyE3D Thank you so much for posting this code. Im pretty new to code in general, but it looks like makes sense (unless im completely mistaken which is also possible). Looks like this is in GitHub: ReprapFirmware/src/Movement/PhaseStep.cpp, line 132 for others that may be looking.

After trying to put some of this in a spreadsheet (which Im sure is not the best way to go about this, but its what I kinda know), and putting in some velocity and acceleration values, Im struggling to get the PIDControlSignal value to be anything other than the 256 max value, which will in turn set the currentFraction to the max of 1.

Im not sure what Im missing here. Could be that the mParams arent actually as simple as the speed and accel in mm/sec(^2), I may have calculated holdCurrentFraction wrong (in PhaseStep.h as 0.71), or the default values are really conservative. Or something else that I cant think of.

@penguinya Do you have a link to this? I havent seen anything about it.