; Quick motor testing M913 X35 Y35 ; drop motor current M564 S0 H0 ; allow movement without being homed and allow movement outside limits M291 R"Test X axis" P"Slowly test movement of X axis with small increment of movement" S3 X1 M291 R"Test Y axis" P"Slowly test movement of Y axis with small increment of movement" S3 Y1 M400 M913 X85 Y85 ; return motor currents to normal M564 S1 H1 ; restrict movement of unhomed axis and prevent movement outside limits

If motors still move correctly, test homing.

@dc42 ok thank you, will do

@alexjx said in Gcode viewer:

Does the CPU have the available processing power for this? Or we are talking about all in-browser viewer?

We're talking about an in-browser viewer.

Does the Duet show up in the Device Manager when connected?

Which lights are lit up when it's connected to USB?

You may be able to go through the fall back procedures to get back up and running. https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Fallback_procedure_Num_1

If you follow through on those, at what point does it fail?

@Phaedrux , thank you.
BTW, I did use the forum search function for this, but didn't get a hit that helped. This morning I used Google to search and found a number of helpful posts on this forum.
I'll use Google i n the future. Again, thank you.

The monitor function within Cura also works with OctoPrint as I had it with my Ender 3 Pro, before upgrading everything!
I have read that Duet have sent a board to Gina @ OctoPrint, I think to investigate integration between the Duet and OctoPrint.

ok Thank you i will try it

@totalos

Now is 100 and 60 - in my opinion it is not safe

I second that! It really should be 5 and 5 at default, better to extrude too little and too slow than too much and too fast.

Here's my end of print tune.

;Play a little beep beep beep to show print ended. M400 ; Clear queue again before jingle G4 S1 M300 P250 S750 G4 P251 M300 P200 S1250 G4 P201 M300 P250 S750 G4 P251 M300 P200 S1250 G4 P201 M300 P250 S2500 G4 P251 M300 P150 S2000 G4 P151 M300 P150 S2500 G4 P151 M300 P350 S3700 G4 P351

@stephen6309 sorry for the late thanks, but thank you for responding

@phaedrux said in Job Status don´t work:

@jgrouse said in Job Status don´t work:

Should I blow away the web server files on the SD and recreate the folder from the latest zip resources?

Replacing the DWC files in the /www folder with the latest version couldn't hurt. Perhaps a file has become corrupted or unreadable or something.

You could also upgrade DuetWiFiServer to the 1.23 release (instead of the beta that you are currently using) and main firmware to 2.03RC1.

Also check in DWC that the version of DuetWiFiServer you are running is 1.23.

@dc42 Duh! Thanks.

@zapta said in incorrect print time estimates (S3D), layer count etc:

@dc42, I wonder, board developers like you and slicer developers like Cura, S3D and Slic3r are on both ends of the same gcode protocol. Are there forums or communication channels between the two groups? For example, to discuss standard representation of estimation metadata that slicers can pass to the boards.

If there are any such channels, I am not aware of them. Every slicer seems to use different metadata keywords, and they often change.

There's also a difference between RC and beta releases. Beta releases often include large changes and experimental features, so they are more likely to include bugs. RCs are intended to be close to what we ship as a stable release.