RRF 3.4 input shaping preview available

dc42

@skrotz said in RRF 3.4 input shaping preview available:

@dc42 I was able to do a print and captured some stepper errors with debug output. Included is my config.g, the gcode I was printing, and the output logs. Hopefully this helps diagnose the issues some of us are having with RRF 3.4. This was with PA disabled , and input shaping enabled via M593 P"ei2" F41 S0.10

config.g
printOutput.txt
CFFFP_xyzCalibration_cube_205.gcode

With your files I was able to identify and reproduce the problem. It is now fixed and I can run your test print using your configuration without errors.

We will release a new beta with input shaping within the next few days.

skrotz

@dc42 great! More than happy to test out a pre-release version of it if you put it on the dropbox

dc42

@skrotz said in RRF 3.4 input shaping preview available:

@dc42 great! More than happy to test out a pre-release version of it if you put it on the dropbox

I've just put the Duet 2 version at https://www.dropbox.com/sh/ja08b7qdzsl8kjc/AAAwUbkN2XJvurq5CuQTgx5Wa?dl=0. Please try it with care, this doesn't just contain a bug fix for that issue, the units used internally to measure speeds and accelerations have changed. It works OK so far on my delta, but I haven't tried it on a Cartesian or CoreXY machine yet.

skrotz

@dc42 I installed the new firmware, did some basic homing and movement tests, and all seemed fine, so I went for broke and printed out the calibration cube with both input shaping and pressure advance enabled.. no clunking issues or anything that seemed amiss during the print. However, I still have some extrusion zits (in the same places as before, seems caused by input shaping) and the print looked extremely similar to a non PA enabled print, with slightly bulging corners. M122 after showed no errors but 2 hiccups.

== Move ===
DMs created 83, segments created 33, maxWait 125385ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 11545, completed moves 11545, hiccups 2, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1

dc42

@skrotz thanks for your fast feedback! It has prompted me to check the balance between axis movement and extrusion again, and I have found an issue that may explain those symptoms. More soon.

dc42

@skrotz I have updated the binary at https://www.dropbox.com/sh/ja08b7qdzsl8kjc/AAAwUbkN2XJvurq5CuQTgx5Wa?dl=0 to fix the extrusion issue that I identified.

Adrian52

@dc42 just done calibration cubes, with no extruder problems and no hics or step errors, but appears that pa is not working for me with the latest 3.4

skrotz

@dc42 Unfortunately things look pretty much the same for me with the newest code. Some small extrusion zits or bubbles on the print, and PA doesn't seem like it is working. I did get a few step errors also it looks like, printing out a calibration cube:

=== Move ===
DMs created 83, segments created 35, maxWait 140417ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 11545, completed moves 11545, hiccups 2, stepErrors 3, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1

Things didn't seem or sound better or worse than previously. There are a couple of clunks I've heard during the prints I did on this firmware and the previous one.. I wasn't sure but now that I've done another print I'm fairly certain towards the end of the print in a couple of spots there was a distinct "clunk" noise, at the same place in both prints.

I will see if I can capture step error data again with this new firmware.

dc42

@skrotz and @Adrian52 please send M115 and report the firmware date/time that it reports.

skrotz

@dc42
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.0beta2-inputshaping ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2021-07-25 09:41:53

Will try and capture step error data now.

Adrian52

@dc42 2021-07-25 09:41:53

skrotz

@dc42 here's the log data with some stepper errors:

0725printerlog.txt
config.g
CFFFP_xyzCalibration_cube_205.gcode

on closer inspection the "zits" I'm seeing don't seem related to where the stepper errors occurred. They only seem to happen on the X side of the cube, at occasional points where it is changing direction for the X indented in the cube. It looks like overextrusion as it is a small blob. You have to magnify things to be able to see them, but it's happening a fair bit and is different/worse than RRF 3.3 which looks very clean. It seems to happen in exactly the same place each print, and has been pretty consistent throughout all the various 3.4s I've tried.

sebkritikel

Just ran a print off the lasted BIN

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.0beta2-inputshaping ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2021-07-25 09:41:53

Parts look great, but end of print M122 reports 65 hiccups and 1929 stepErrors

M593 P"zvdd" F38.4
M572 D0 S0.020

config(1).g
LOG JP_smallPart1^2021 rifle gps mount-Split1.txt
Print file

dc42

@skrotz what PA did you use when you had those step errors? Was everything apart from PA the same as in the config.g file you posted earlier?

dc42

@sebkritikel thanks, I will run that print on my bench setup.

skrotz

@dc42 I did have PA enabled, that’s probably the only difference between the config files I posted, I think. The tests with these new firmwares had PA enabled.

dc42

@skrotz said in RRF 3.4 input shaping preview available:

@dc42 I did have PA enabled, that’s probably the only difference between the config files I posted, I think. The tests with these new firmwares had PA enabled.

How much PA?

skrotz

@dc42 M572 D0 S0.12 is my standard PA setting, that's what the config.g had that I have been using for current 3.4 tests.

Adrian52

Should add that I used daa to compare 3.3 with 3.4, so that an identical config.g could be used for both. I use pa 0.8 with my 700mm bowden. No errors or hiccups with both, but pa not working with 3.4.
If I use ei3 with 3.4, I get 2 Step errors with the calibration cube (no hiccups or underruns), and I get 2 filament monitor 'insufficient movement' pauses on layers 97/98 out of 100.

dc42

@adrian52 @skrotz @sebkritikel I have put a new Duet 2 binary at https://www.dropbox.com/sh/ja08b7qdzsl8kjc/AAAwUbkN2XJvurq5CuQTgx5Wa?dl=0. This fixes the issue with pressure advance and other issues that I was able to reproduce.