3.2-RC1 Plugin Failures
-
So I did a clean upgrade, complete build from blank SD card ....
The heightmap is now available under 'controls' on the left hand menu, it no longer appears as a plugin, my plugin list is empty.
I do however have 'other' interface issues still.
The main dashboard shows 'Starting' at all times
The status window never shows any status during prints - it goes straight to print completed although it is not. This is a problem as the pause option cannot be selected in this state.
The previous file read failures do not occur via the RPi and the machine completed the print overnight (16 hours total). The status window wasn't available for that either and the 'starting' was present for the entire print - was there when I turned in and there when I got up.
This is an image for a print I just started ...
-
Can you confirm that both DSF and RRF are on RC1?
-
Confirmed
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2-RC1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
Board ID: 08DJM-956L2-G43S8-6JKD8-3SS6L-9B12H
Used output buffers: 1 of 40 (10 max)
=== RTOS ====== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 1ms ago
RX/TX seq numbers: 63835/63835
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c8a8
Buffer RX/TX: 0/1480-0
=== Duet Control Server ===
Duet Control Server v3.2.0-rc1
-
@Garfield Can you please share your config.g? It doesn't look right that RRF remains in the "Starting" state.
-
@chrishamm it hasn't changed in a while now but it is attached here. config.g
Powered up this morning and still shows 'Starting' ...
-
Journal contains nothing useful that I can see.
Dec 23 11:33:01 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1] Dec 23 11:33:01 duet3 DuetWebServer[589]: Request starting HTTP/1.1 GET http://10.100.254.252/ Dec 23 11:33:01 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1] Dec 23 11:33:01 duet3 DuetWebServer[589]: Request starting HTTP/1.1 GET http://10.100.254.252/ Dec 23 11:33:01 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0] Dec 23 11:33:01 duet3 DuetWebServer[589]: No endpoint found for GET request via / Dec 23 11:33:01 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0] Dec 23 11:33:01 duet3 DuetWebServer[589]: No endpoint found for GET request via / Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[6] Dec 23 11:33:02 duet3 DuetWebServer[589]: The file /index.html was not modified Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Server.Kestrel[34] Dec 23 11:33:02 duet3 DuetWebServer[589]: Connection id "0HM576Q0Q0EUL", Request id "0HM576Q0Q0EUL:00000001": the application aborted the connection. Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[2] Dec 23 11:33:02 duet3 DuetWebServer[589]: Sending file. Request path: '/index.html'. Physical path: '/opt/dsf/sd/www/index.html' Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request finished in 234.1646ms 304 text/html Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request finished in 234.1644ms 0 text/html Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request starting HTTP/1.1 GET http://10.100.254.252/css/app.37435a82.css Dec 23 11:33:02 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0] Dec 23 11:33:02 duet3 DuetWebServer[589]: No endpoint found for GET request via /css/app.37435a82.css Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[6] Dec 23 11:33:02 duet3 DuetWebServer[589]: The file /css/app.37435a82.css was not modified Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request finished in 3.3812ms 304 text/css Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request starting HTTP/1.1 GET http://10.100.254.252/js/app.166d29b4.js Dec 23 11:33:02 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0] Dec 23 11:33:02 duet3 DuetWebServer[589]: No endpoint found for GET request via /js/app.166d29b4.js Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[6] Dec 23 11:33:02 duet3 DuetWebServer[589]: The file /js/app.166d29b4.js was not modified Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request finished in 0.94ms 304 application/javascript Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request starting HTTP/1.1 GET http://10.100.254.252/fonts/materialdesignicons-webfont.4187121a.woff2 Dec 23 11:33:02 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0] Dec 23 11:33:02 duet3 DuetWebServer[589]: No endpoint found for GET request via /fonts/materialdesignicons-webfont.4187121a.woff2 Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request starting HTTP/1.1 GET http://10.100.254.252/rr_connect?password=reprap&time=2020-12-23T11%3A33%3A1 application/json Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[6] Dec 23 11:33:02 duet3 DuetWebServer[589]: The file /fonts/materialdesignicons-webfont.4187121a.woff2 was not modified Dec 23 11:33:02 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0] Dec 23 11:33:02 duet3 DuetWebServer[589]: No endpoint found for GET request via /rr_connect Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request finished in 32.3736ms 304 font/woff2 Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request finished in 12.2236ms 404 Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request starting HTTP/1.1 GET http://10.100.254.252/img/icons/favicon-32x32.png Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request starting HTTP/1.1 GET http://10.100.254.252/img/icons/apple-touch-icon-152x152.png Dec 23 11:33:02 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0] Dec 23 11:33:02 duet3 DuetWebServer[589]: No endpoint found for GET request via /img/icons/apple-touch-icon-152x152.png Dec 23 11:33:02 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0] Dec 23 11:33:02 duet3 DuetWebServer[589]: No endpoint found for GET request via /img/icons/favicon-32x32.png Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[2] Dec 23 11:33:02 duet3 DuetWebServer[589]: Sending file. Request path: '/img/icons/favicon-32x32.png'. Physical path: '/opt/dsf/sd/www/img/icons/favicon-32x32.png' Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[2] Dec 23 11:33:02 duet3 DuetWebServer[589]: Sending file. Request path: '/img/icons/apple-touch-icon-152x152.png'. Physical path: '/opt/dsf/sd/www/img/icons/apple-touch-icon-152x152.png' Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request finished in 31.6052ms 200 image/png Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request finished in 31.6044ms 200 image/png Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request starting HTTP/1.1 GET http://10.100.254.252/machine Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Cors.Infrastructure.CorsService[5] Dec 23 11:33:02 duet3 DuetWebServer[589]: CORS policy execution failed. Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Cors.Infrastructure.CorsService[6] Dec 23 11:33:02 duet3 DuetWebServer[589]: Request origin http://10.100.254.252 does not have permission to access the resource. Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0] Dec 23 11:33:02 duet3 DuetWebServer[589]: Executing endpoint 'DuetWebServer.Controllers.WebSocketController.Get (DuetWebServer)' Dec 23 11:33:03 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3] Dec 23 11:33:03 duet3 DuetWebServer[589]: Route matched with {action = "Get", controller = "WebSocket"}. Executing controller action with signature System.Threading.Tasks.Task Get() on controller DuetWebServer.Controllers.WebSocketController (DuetWeb Dec 23 11:33:03 duet3 DuetWebServer[589]: info: DuetWebServer.Controllers.WebSocketController[0] Dec 23 11:33:03 duet3 DuetWebServer[589]: WebSocket connected from ::ffff:10.100.0.4:52628 Dec 23 11:33:03 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1] Dec 23 11:33:03 duet3 DuetWebServer[589]: Request starting HTTP/1.1 GET http://10.100.254.252/machine/directory/0:%2Fmacros%2F application/json Dec 23 11:33:03 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0] Dec 23 11:33:03 duet3 DuetWebServer[589]: Executing endpoint 'DuetWebServer.Controllers.MachineController.GetFileList (DuetWebServer)' Dec 23 11:33:03 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1] Dec 23 11:33:03 duet3 DuetWebServer[589]: Request starting HTTP/1.1 GET http://10.100.254.252/machine/file/0:%2Fsys%2Fdwc-settings.json application/json Dec 23 11:33:03 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0] lines 1-95/230 36% pi@duet3:~ $ sudo journalctl -u duetcontrolserver -- Logs begin at Wed 2020-12-23 01:17:01 GMT, end at Wed 2020-12-23 11:47:41 GMT. -- Dec 23 01:18:32 duet3 systemd[1]: Starting Duet Control Server... Dec 23 01:18:34 duet3 DuetControlServer[398]: Duet Control Server v3.2.0-rc1 Dec 23 01:18:34 duet3 DuetControlServer[398]: Written by Christian Hammacher for Duet3D Dec 23 01:18:34 duet3 DuetControlServer[398]: Licensed under the terms of the GNU Public License Version 3 Dec 23 01:18:35 duet3 DuetControlServer[398]: [info] Settings loaded Dec 23 01:18:35 duet3 DuetControlServer[398]: [info] Environment initialized Dec 23 01:18:35 duet3 DuetControlServer[398]: [info] Connection to Duet established Dec 23 01:18:35 duet3 DuetControlServer[398]: [info] IPC socket created at /var/run/dsf/dcs.sock Dec 23 01:18:35 duet3 systemd[1]: Started Duet Control Server. Dec 23 01:18:35 duet3 DuetControlServer[398]: [info] Starting macro file config.g on channel Trigger Dec 23 01:18:36 duet3 DuetControlServer[398]: [warn] M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 573C Dec 23 01:18:36 duet3 DuetControlServer[398]: [warn] M307: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 341C Dec 23 01:18:36 duet3 DuetControlServer[398]: [info] Finished macro file config-override.g Dec 23 11:32:02 duet3 DuetControlServer[398]: [info] System time has been changed -
@Garfield Thanks, can you post your config-override.g as well? I just tried the config.g on another board and it completed as expected. When I get your override file, I'll try it again on a MB6HC.
-
@chrishamm I don't have an override file.
-
@Garfield Interesting, please try to remove M501 from your config.g then and check if it makes a difference.
Edit: I can reproduce this problem if I delete config-override.g. I'm looking into it.
-
@chrishamm Confirmed - if I remove M501 the 'starting' becomes idle. if I add a config override but leave the M501 the starting becomes idle, it seems to be that the system expects to find a config override if M501 is used and gets stuck if it can't find it.
This is what impacts the status screen updating and the print going straight to 'complete' - I just verified it. The print however will continue and completes as it should.
-
@Garfield Thanks, I've just fixed this. It will be resolved in RC2.
-
No worries, appreciated - you can always rely on users to do the unexpected. I never realy thought about the override file, never used it, suppose I should have realised what M501 actually did. It's one of those things you do early on then forget about - until it bites you .....
