Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Solved 3.2-RC1 Plugin Failures

    Beta Firmware
    2
    16
    642
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Garfieldundefined
      Garfield
      last edited by

      Pretty much get an error for all plugins following introduction of RC1, the following is one such example. There is no such file in any folder on my SD card

      Heightmap is no longer available.
ChunkLoadError: Loading chunk HeightMap failed.
(error: http://10.100.254.252/js/HeightMap.c18cb13f.js)

      Folders

      pi@duet3:/opt/dsf/dwc/js $ ls
app.166d29b4.js              HeightMap.ef4ed2d6.js               OnScreenKeyboard.a4596cd5.js
app.166d29b4.js.map          HeightMap.ef4ed2d6.js.map           OnScreenKeyboard.a4596cd5.js.map
GCodeViewer.03fd3878.js      ObjectModelBrowser.89b13181.js
GCodeViewer.03fd3878.js.map  ObjectModelBrowser.89b13181.js.map

pi@duet3:/boot/www/js $ ls
app.2a4070cd.js.gz      HeightMap.2baad695.js.gz               OnScreenKeyboard.84b33c6d.js.gz
app.2a4070cd.js.map.gz  HeightMap.2baad695.js.map.gz           OnScreenKeyboard.84b33c6d.js.map.gz
app.b867548c.js.gz      HeightMap.4ee5c020.js.gz               OnScreenKeyboard.9a79c70b.js.gz
app.b867548c.js.map.gz  HeightMap.4ee5c020.js.map.gz           OnScreenKeyboard.9a79c70b.js.map.gz
app.d0e602e2.js.gz      ObjectModelBrowser.9383802b.js.gz      Visualizer.29c9871a.js.gz
app.d0e602e2.js.map.gz  ObjectModelBrowser.9383802b.js.map.gz  Visualizer.29c9871a.js.map.gz

      Others are the same story i.e.

      Error: Loading CSS chunk Visualizer failed.
(/css/Visualizer.7d33149d.css)

      pi@duet3:/boot/www/css $ ls
app.2eca9440.css.gz  HeightMap.7a255baa.css.gz           OnScreenKeyboard.58652065.css.gz
app.c0302286.css.gz  HeightMap.ed3f384d.css.gz           Visualizer.79c49760.css.gz
app.eb4376bc.css.gz  ObjectModelBrowser.c5e13b42.css.gz
      1 Reply Last reply Reply Quote 0
      • chrishammundefined
        chrishamm administrators
        last edited by chrishamm

        It looks like you didn't update the duetwebcontrol package but installed the SD bundle via Upload on the System Files page. The SBC package doesn't have .gz files in it.

        The recommended way to perform an update is via

        sudo apt-get update
sudo apt-get upgrade

        At the moment you still have to be on the unstable package feed to try out RC1.

        Duet software engineer

        Garfieldundefined 1 Reply Last reply Reply Quote 0
        • Garfieldundefined
          Garfield
          last edited by Garfield

          That is exactly how I did the upgrade ....

          Could this be a legacy from running without the RPi when it had a bug causing stutter?

          Edit : I just ditched the RPi and did things directly on the Duet3, copied the files across and that update works fine.

          1 Reply Last reply Reply Quote 0
          • Garfieldundefined
            Garfield @chrishamm
            last edited by

            @chrishamm

            Running direct on the Duet3 I now encounter 'other' issues not encountered via the Pi

            Error: Cannot read file, error code 1
Cancelled printing file 0:/gcodes/Jacuzzi Cushions.gcode, print time was 2h 12m
12/21/2020, 5:11:07 PM 	M32 "0:/gcodes/Jacuzzi Cushions.gcode"

File 0:/gcodes/Jacuzzi Cushions.gcode selected for printing

12/21/2020, 5:04:48 PM 	Error: Cannot read file, error code 1
Cancelled printing file 0:/gcodes/Jacuzzi Cushions.gcode, print time was 0h 35m
Error: Cannot read file, error code 1
Warning: Failed to read header of G-Code file "0:/gcodes/Jacuzzi Cushions.gcode"

            This is not on a cheapo SD card either, it checks out fine, the file can be read without issue. No I can't upload the file, the site won't allow compressed files and as a gcode file it is too large (7,097KB).

            This file fails in different places - the fail point is not consistent. When this happens the printer does not behave in a friendly manner - it just stops where it is, it doesn't park the hot end although it does turn off the heaters.

            Time to have multiple SD cards to hand, time to create a new RPi image .... I'll let you know if the plugin problem goes away.

            1 Reply Last reply Reply Quote 1
            • Garfieldundefined
              Garfield
              last edited by

              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

              starting.png

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

              no status.png

              1 Reply Last reply Reply Quote 0
              • chrishammundefined
                chrishamm administrators
                last edited by

                Can you confirm that both DSF and RRF are on RC1?

                Duet software engineer

                1 Reply Last reply Reply Quote 0
                • Garfieldundefined
                  Garfield
                  last edited by

                  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

                  version.png

                  1 Reply Last reply Reply Quote 0
                  • chrishammundefined
                    chrishamm administrators
                    last edited by

                    @Garfield Can you please share your config.g? It doesn't look right that RRF remains in the "Starting" state.

                    Duet software engineer

                    Garfieldundefined 1 Reply Last reply Reply Quote 0
                    • Garfieldundefined
                      Garfield @chrishamm
                      last edited by

                      @chrishamm it hasn't changed in a while now but it is attached here. config.g

                      Powered up this morning and still shows 'Starting' ...

                      starting 2.png

                      1 Reply Last reply Reply Quote 1
                      • Garfieldundefined
                        Garfield
                        last edited by

                        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
                        1 Reply Last reply Reply Quote 0
                        • chrishammundefined
                          chrishamm administrators
                          last edited by

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

                          Duet software engineer

                          Garfieldundefined 1 Reply Last reply Reply Quote 0
                          • Garfieldundefined
                            Garfield @chrishamm
                            last edited by

                            @chrishamm I don't have an override file.

                            chrishammundefined 1 Reply Last reply Reply Quote 0
                            • chrishammundefined
                              chrishamm administrators @Garfield
                              last edited by chrishamm

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

                              Duet software engineer

                              Garfieldundefined 1 Reply Last reply Reply Quote 0
                              • Garfieldundefined
                                Garfield @chrishamm
                                last edited by Garfield

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

                                chrishammundefined 1 Reply Last reply Reply Quote 1
                                • chrishammundefined
                                  chrishamm administrators @Garfield
                                  last edited by

                                  @Garfield Thanks, I've just fixed this. It will be resolved in RC2.

                                  Duet software engineer

                                  1 Reply Last reply Reply Quote 0
                                  • Garfieldundefined
                                    Garfield
                                    last edited by

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

                                    1 Reply Last reply Reply Quote 1
                                    • First post
                                      Last post
                                    Unless otherwise noted, all forum content is licensed under CC-BY-SA