@fcwilt Ok, thanks!

Thanks JamesM and fcwilt!

Before I upgraded my board to the Duet2WiFi, (from a Melzi) I calculated my E Steps and set the E value to 95 steps/mm. I carried that value over, even when I had X128 microstepping enabled. I noticed in the instructions above that with X16 microstepping, the recommended E value is 420. Does that need to be modified for E Step calibration to ensure that the right amount of filament is extruded?

I'm running a Duet2WiFi board with firmware version 3.2. Do I need to change my movement speeds when I change the microstepping value? I have been running X128 microstepping because that's what the web configuration builder set for me, but it was recommended for me to reduce that to X16 with Interpolation, in order to save on CPU processing. After changing the values from X128 to X16, all of my stepper motors move extremely fast to the point where the bind on the end stops. When I change the values back to 128 for all axis, they move normally again.

The only thing that I can think of is that the speeds in my homing files are too fast when the printer is set to X16. Below are the relevant movement speeds from my config and my homing file. I currently have interpolation set to off, but the issue persists with it on or off. Thanks for your help!

config.g

M350 X16 Y16 Z16 E16 I0 ; configure X16 microstepping without interpolation
M92 X640.00 Y640.00 Z3200.00 E95.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z1200.00 E3000.00 ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X855 Y855 Z331 E855 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30

homeall.g

G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-205 Y-205 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000 ; go back a few mm
G1 H1 X-205 Y-205 F360 ; move slowly to X and Y axis endstops once more (second pass)
;G1 X2 Y59 F6000 ; go to first bed probe point and home Z
G90 ; absolute positioning
;G1 H1 Z-205 F360 ; move Z down stopping at the endstop
G1 X2 Y59 F6000 ; go to first bed probe point and home Z
;M558 P9 F300 ; speed up homing probe
M558 F300 ; speed up homing probe -- Was told to remove P9 from this command by forum moderator -- JSN
G30 ; home Z by probing the bed
;M558 P9 F120 ; slow down homing probe for second pass
M558 F120 ; slow down homing probe for second pass -- Was told to remove P9 from this command by forum moderator -- JSN
G30 ; home Z by probing the bed

@Phaedrux said in Z probe 0 not found after upgrading to Firmware v3.2 from v3.1.1:

M98 P"config.g"

That fixed it! Thanks a lot! Was that a change from v3.1.1 to 3.2?

Also, I am still receiving the following error. It doesn't seem to affect anything because OctoPrint just ignores it, but can you tell from my config.g what is wrong? Is there a way to output the line number that the error is referencing?

Recv: WiFi module is idle
Recv: HTTP is enabled on port 80
Recv: FTP is disabled
Recv: TELNET is disabled
Recv: Error: Invalid use of P parameter

@Phaedrux The errors are from trying to home all and home z.

I upgraded to firmware 3.2 from 3.1.1 today and now my printer will not home the Z axis. Before the upgrade, everything worked fine. I'm sure that it is a configuration issue; as I had to change a lot of my configuration syntax when updating from firmware version 2 to 3. I don't understand why the config formatting has to change between firmware versions to the point that it breaks things?

I am using a BL Touch as my z probe. The error that I am receiving is below. I will upload my config.g, homez.g, and homeall.g for your review. I ran the M98 P"config.g" command in terminal, as was suggested by another post with this error. The printer returned that there is in an invalid P parameter in my config, but it does not say which line that invalid parameter is on. Please let me know if you need any additional information. I appreciate your help!

Errors:
1/12/2021, 5:32:07 PM Error: in file macro line 9: G30: Z probe 0 not found
Error: Homing failed
1/12/2021, 5:32:07 PM Error: in file macro line 15: G30: Z probe 0 not found
Error: Missing Z probe pin name(s)
Error: in file macro line 17: G30: Z probe 0 not found
1/12/2021, 5:32:06 PM G28
Error: Missing Z probe pin name(s)

config.g
homez.g
homeall.g

Thanks for posting the screenshot... I see that you get some statistics with Kisslicer. I don't get anything with Cura. I'm wondering whether or not I have a Java issue, or an issue with the version of the Duet2 WiFi Web Interface that i'm running. Do those statistics start when the "Processing gcode file" progress bar goes away? The progress bar doesn't go away for me. It's there throughout the entire print. Could you post a screenshot of your "Software Information" section under Settings > General? Also, which web browser are you using to access the web interface? Thanks!

To further aid in the troubleshooting, I have printed files with both Chrome and FireFox using my MacBook Pro. Both provide the same result. Attached is a screenshot of a print that is currently on-going with no statistics... I noticed that the "Processing" progress bar above the statistics section is completely full, even though the 8 hour print just started. Isn't that bar supposed to increment throughout the printing process?

Sure, see attached. Thanks!

0_1566135541576_Calibration_Cube.gcode

@phaedrux

Duet2 WiFi
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.04RC1 (2019-07-14b1)
WiFi Server Version: 1.23
Web Interface Version: 1.22.6

I went ahead and opened another thread on the issue to get more visibility.
https://forum.duet3d.com/topic/11640/all-stats-display-n-a-when-printing-file