Job Status don´t work

[dc42]

@kleudieu said in Job Status don´t work:

@deckingman I tried it now, is this right or should I get something else?

While the simulation is being run, you should see the Job Status screen updating, just as for a normal print but about 60x faster.

[KleudiEU]

@dc42 said in Job Status don´t work:

@kleudieu said in Job Status don´t work:

@deckingman I tried it now, is this right or should I get something else?

While the simulation is being run, you should see the Job Status screen updating, just as for a normal print but about 60x faster.

I switched back to the latest stable firmware release, but always the same issue. Job status don't work. I don't know what to do next.
I don't think it´s a problem with Cura, so many people use it and if something like that happens, it should be solved very fast.

Screenshot of my new firmware settings:

[KleudiEU]

@phaedrux said in Job Status don´t work:

Can you post the results of an M122 in the console?

This might help you with your wifi connection issues if that's what's actually going on.
https://duet3d.dozuki.com/Wiki/WiFi_disconnections_and_AJAX_timeout_errors

You may also want to try going back to the last stable release of the firmware and DWC, as I see you're running the new betas.

I get a message when the print starts and when it ends, but between nothing.
Here are my results:

[Phaedrux]

-75db is pretty border line for wifi signal strength. That could explain occasional drops.

From the wiki:

In Duet Web Control, on the Settings/General tab check that "Maximum number of AJAX retries" is at least 3.

I notice in your screen shot your ajax retries are 0.

[KleudiEU]

I finally got the problem solved. I updated the DWC to the newest beta release and it works now . I can't say why, but it works and I´m happy
Thanks for the help guys.

[jgrouse]

I've had this issue for ages now and I was hoping the last updates I just applied would get my job status to work but it's still not showing any info during 3D prints.

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.0 or 1.01
Firmware Version: 2.03beta3 (2019-03-25b6)
WiFi Server Version: 1.23
Web Interface Version: 1.22.6

Not sure what else to try? Is there any possibility that since updating to Simplify3D V4.X the code stopped supplying the required GCode for status info?

Attached are my relevant settings. Also attached is a sample gcode file from Simplify3D 4.1.2 0_1556848471785_config.g 0_1556848492115_StartPrint.g 0_1556848538450_Nitro 200 frame clip.gcode

[dc42]

I've run that GCode file in simulation mode on one of my printers, and the print progress is displayed correctly, using DWC 2.0.0-RC6 and also using DWC 1.22.6. The object height, layer height an filament usage are displayed in the GCode Files list, so S3D 4.x is including the same metadata that DWC needs as earlier versions did.

Is the WiFi connection to the Duet reliable, or do you get a lot of reconnections?

[jgrouse]

@dc42 - the wifi connection has been very reliable since I put Google Wifi points around the house and one in the garage. Before that it would drop regularly. But that was the beginning of the year and I had this issue before then. Attached are my config files. Hopefully you can spot something there? Should I blow away the web server files on the SD and recreate the folder from the latest zip resources?2_1557270693645_config.g 1_1557270693645_StartPrint.g 0_1557270693645_EndPrint.g

[Phaedrux]

@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.

[dc42]

@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.