@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

I'm using Cura 4.2.1 to slice my files. After uploading the gcode file to the printer via the Web Interface and starting the print, all of the layer statistics and time estimations within the "Job Status" section display n/a throughout the entire print. How can i enable those stats? Below are the versions that i'm running and i've attached a screenshot of the "Job Status" page. Thanks.

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

Yes i do. I turned it off and no longer get the error. I still do not receive any statistics during the print. Everything shows n/a. How do I enable those? The attached screenshot is what i'm talking about.

After changing the temp in Cura, I no longer get the M141 error. I do get a M900 is not supported message though; although it is in blue and not red like the Error. Is that another Cura setting? I set my gcode flavor to RepRap in Cura. Is that correct? I saw an option in the web configurator to make the firmware look like Marlin. What's the purpose of that?