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

    CONSTANT AJAX disconnect errors

    Scheduled Pinned Locked Moved
    General Discussion
    28
    307
    55.1k
    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.
    • KeeganBundefined
      KeeganB
      last edited by

      David,

      I think I have established a bit of a pattern in my situation. It seems that right at the beginning of every new print, it disconnects. Then sometime after that (I estimate between 15-30mins) it just reconnects itself and is fine from then until I start the next print.

      Artemis
      Rostock Max v2
      Orion

      1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators
        last edited by

        I did a little investigation this morning, and I found that for homing moves (i.e. G1 S1 moves), the maximum step rate possible is many times lower than for ordinary moves. So a high microstepping value can cause MaxReps to get very high during a homing move even if the combination of M350 microstepping and M203 maximum speeds is OK for normal moves. So if your print files have a G28 homing command at the start, that could be why you get a disconnection at the start of a print. The workaround for this particular issue is to use slower homing moves.

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        1 Reply Last reply Reply Quote 0
        • KeeganBundefined
          KeeganB
          last edited by

          I will try slower homing moves. I don't have a separate G28 at the start of my prints, but there is on inside of beg.g that runs (as G32) at the start of all prints.

          My micro stepping is 16x

          I should add though, that it doesn't necessarily disconnect during the homing move, sometimes it can be a few minutes into the print.

          Artemis
          Rostock Max v2
          Orion

          1 Reply Last reply Reply Quote 0
          • dc42undefined
            dc42 administrators
            last edited by

            I would not expect you to have this problem with only x16 microstepping.

            Duet WiFi hardware designer and firmware engineer
            Please do not ask me for Duet support via PM or email, use the forum
            http://www.escher3d.com, https://miscsolutions.wordpress.com

            1 Reply Last reply Reply Quote 0
            • Jareryundefined
              Jarery
              last edited by

              Similar to KeeganB, my board is set to 16x micro stepping (with interpolation).
              I also do not have a G28 homing in any of my Gcode but as KeeganB states in my Bed command is a G28 at the start. After that the Gcode has no homing until finished.

              My disconnects happen early in a print but unlike KeeganB, mine has never reconnected on its own that I'm aware of.
              I have never seen the reconnect count above 0.
              Edit: mine don't always happen only near start of a print, just that they are a high chance at start. Mine also disconnects just sitting idle sometime.

              I'm about a week away from commissioning a second delta with another duet wifi, based on dc42's large Kossel build. So in a week or so I'll be able to tell if both boards exhibit the same behaviour in my wifi network or if its specific to the one board.

              1 Reply Last reply Reply Quote 0
              • lolorcundefined
                lolorc
                last edited by

                Hi there.

                I also have the constant disconnections.
                the disconnections also happen when the printer is idle…

                I also have a tons of issue uploading g-code files through wifi. (when usb is plugged)

                1 Reply Last reply Reply Quote 0
                • BlackTomundefined
                  BlackTom
                  last edited by

                  I have had the same kind of issue with 1.19.2, 1.19 is correct.

                  I had issues when I was running my bed compensation routine and I had it too when I was printing,
                  I always finish by being disconnected of the web interface when I print and I cannot reconnect to it.

                  The print continue without issue until it's done so it doesn't affect it

                  The only way to get back access to the web interface is by powering off / on the board,

                  1 Reply Last reply Reply Quote 0
                  • lolorcundefined
                    lolorc
                    last edited by

                    @bloood3d:

                    The only way to get back access to the web interface is by powering off / on the board,

                    same here.

                    1 Reply Last reply Reply Quote 0
                    • botundefined
                      bot
                      last edited by

                      What about when you do a "hard refresh" of the web page through the web browser? On chrome this is done by holding the CTRL key while clicking refresh. In the past, this has helped me get back into a web interface session.

                      *not actually a robot

                      1 Reply Last reply Reply Quote 0
                      • KeeganBundefined
                        KeeganB
                        last edited by

                        bot,

                        That hasn't worked for me. I have also tried loading the page on difference devices.

                        Artemis
                        Rostock Max v2
                        Orion

                        1 Reply Last reply Reply Quote 0
                        • RGN01undefined
                          RGN01
                          last edited by

                          I'm commissioning my new Duet WiFi and have the same issue. I've tried it in two locations (both no more than 10 feet from the WiFi router) and with three clients (desktop PC, Android tablet and Android mobile phone all running Chrome). The desktop PC is best but it still drops the connection frequently - perhaps every 15 minutes - despite the printer not even being fully commissioned (the most it has done is home the towers and heatbed auto set up) and the PC is being used for browsing and email.

                          I hope that this is resolved as it is a bit concerning to someone new to the Duet (which I think is absolutely great!)

                          1 Reply Last reply Reply Quote 0
                          • dc42undefined
                            dc42 administrators
                            last edited by

                            Have you tried increasing the number of retries in the DWC settings?

                            Duet WiFi hardware designer and firmware engineer
                            Please do not ask me for Duet support via PM or email, use the forum
                            http://www.escher3d.com, https://miscsolutions.wordpress.com

                            1 Reply Last reply Reply Quote 0
                            • RGN01undefined
                              RGN01
                              last edited by

                              Thanks, David.

                              I increased it to 5 earlier this evening and it seems to be OK so far on the desktop PC (about 90 minutes) - but the printer and PC are effectively idle.

                              It was set to one initially, is there a recommended larger setting, or is it trial and error?

                              I'll monitor this as I start adding and testing functionality to the printer - and report back.

                              1 Reply Last reply Reply Quote 0
                              • dc42undefined
                                dc42 administrators
                                last edited by

                                1 is rather low, I think 3 would be a better default.

                                Duet WiFi hardware designer and firmware engineer
                                Please do not ask me for Duet support via PM or email, use the forum
                                http://www.escher3d.com, https://miscsolutions.wordpress.com

                                1 Reply Last reply Reply Quote 0
                                • KeeganBundefined
                                  KeeganB
                                  last edited by

                                  At this point I can confidently say mine fits the pattern I mentioned earlier. Every print it starts fine and after a few minutes it disconnects. After probably 30 mins or so, it reconnects without issue and stays connected until I start the next new print.

                                  David, I am considering downgrading to 1.19. Is there any reason not to?

                                  Artemis
                                  Rostock Max v2
                                  Orion

                                  1 Reply Last reply Reply Quote 0
                                  • Jareryundefined
                                    Jarery
                                    last edited by

                                    Interesting yours reconnects. Mine never has, retries I've changed to 5, 10, to no effect.

                                    1 Reply Last reply Reply Quote 0
                                    • KeeganBundefined
                                      KeeganB
                                      last edited by

                                      Jarery,

                                      It may just be that the webpage is auto reloaded by the browser when I come back to the computer and pull it up.

                                      Artemis
                                      Rostock Max v2
                                      Orion

                                      1 Reply Last reply Reply Quote 0
                                      • RGN01undefined
                                        RGN01
                                        last edited by

                                        Thanks, David. I've dropped it to 3 and am testing that. SO far, so good!

                                        1 Reply Last reply Reply Quote 0
                                        • snomonundefined
                                          snomon
                                          last edited by

                                          Hi guys, I'm having the same problem..Im trying to tell it to print something but it keeps giving me AJAX errors..ctrl+r a few times, i get in at some point. The print then keeps messing up and having me to reset it, not sure why

                                          2:55:56 AMM122
                                          === Diagnostics ===
                                          Used output buffers: 3 of 32 (15 max)
                                          === Platform ===
                                          RepRapFirmware for Duet WiFi version 1.19.2 running on Duet WiFi 1.0
                                          Board ID: 08DDM-9FAM2-LW4SD-6J9F6-3S46N-12X7W
                                          Static ram used: 21176
                                          Dynamic ram used: 96104
                                          Recycled dynamic ram: 1504
                                          Stack ram used: 1304 current, 5920 maximum
                                          Never used ram: 6368
                                          Last reset 00:12:18 ago, cause: power up
                                          Last software reset reason: User, spinning module GCodes, available RAM 3136 bytes (slot 4)
                                          Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
                                          Error status: 0
                                          Free file entries: 10
                                          SD card 0 detected, interface speed: 20.0MBytes/sec
                                          SD card longest block write time: 9.7ms
                                          MCU temperature: min 51.1, current 53.7, max 55.9
                                          Supply voltage: min 23.4, current 24.1, max 24.6, under voltage events: 0, over voltage events: 0
                                          Driver 0: stalled standstill
                                          Driver 1: stalled standstill
                                          Driver 2: stalled standstill
                                          Driver 3: standstill
                                          Driver 4: standstill
                                          Date/time: 2017-09-21 02:55:52
                                          Slowest main loop (seconds): 0.167053; fastest: 0.000034
                                          === Move ===
                                          MaxReps: 6, StepErrors: 0, FreeDm: 240, MinFreeDm 234, MaxWait: 10780ms, Underruns: 0, 0
                                          Scheduled moves: 5, completed moves: 5
                                          Bed compensation in use: none
                                          Bed probe heights: 0.000 0.000 0.000 0.000 0.000
                                          === Heat ===
                                          Bed heater = 0, chamber heater = -1
                                          Heater 0 is on, I-accum = 0.0
                                          Heater 1 is on, I-accum = 0.3
                                          === GCodes ===
                                          Segments left: 0
                                          Stack records: 2 allocated, 0 in use
                                          Movement lock held by null
                                          http is idle in state(s) 0
                                          telnet is idle in state(s) 0
                                          file is idle in state(s) 0
                                          serial is idle in state(s) 0
                                          aux is idle in state(s) 0
                                          daemon is idle in state(s) 0
                                          queue is idle in state(s) 0
                                          autopause is idle in state(s) 0
                                          Code queue is empty.
                                          Network state is running
                                          WiFi module is connected to access point
                                          WiFi firmware version 1.19.2
                                          WiFi MAC address 60:01:94:34:40:06
                                          WiFi Vcc 3.14, reset reason Turned on by main processor
                                          WiFi flash size 4194304, free heap 36896
                                          WiFi IP address 192.168.20.81
                                          WiFi signal strength -57dBm
                                          Reconnections 0
                                          HTTP sessions: 1 of 8
                                          Socket states: 2 0 0 0 0 0 0 0
                                          Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
                                          2:55:49 AMConnection established!
                                          2:55:24 AMDisconnected.
                                          2:55:16 AMConnection established!
                                          2:55:11 AMDisconnected.
                                          2:55:03 AMConnection established!
                                          2:55:01 AMDisconnected.
                                          2:54:53 AMConnection established!
                                          2:54:15 AMDisconnected.
                                          2:52:10 AMConnection established!
                                          2:46:32 AMDisconnected.
                                          2:43:49 AMConnection established!
                                          2:41:46 AMDisconnected.
                                          2:39:46 AMConnection established!
                                          2:38:11 AMDisconnected.
                                          2:33:01 AMConnection established!
                                          2:32:52 AMDisconnected.
                                          2:32:40 AMCalibrated 6 factors using 13 points, deviation before 0.028 after 0.014
                                          2:31:48 AMM32 Enclosure bracket v10(1).gcode
                                          File Enclosure bracket v10(1).gcode selected for printing
                                          2:30:54 AMM0 H1
                                          File Enclosure bracket v10(0).gcode print time was 0h 9m
                                          2:30:07 AMM25
                                          Printing paused
                                          2:25:29 AMConnection established!
                                          2:24:55 AMDisconnected.
                                          2:21:20 AMCalibrated 6 factors using 13 points, deviation before 0.091 after 0.024
                                          2:20:42 AMM32 Enclosure bracket v10(0).gcode
                                          File Enclosure bracket v10(0).gcode selected for printing
                                          2:20:14 AMM0 H1
                                          File Enclosure bracket v10(0).gcode print time was 0h 9m
                                          2:19:53 AMM25
                                          Printing paused
                                          2:11:17 AMCalibrated 6 factors using 13 points, deviation before 0.071 after 0.014
                                          2:10:35 AMM32 Enclosure bracket v10(0).gcode
                                          File Enclosure bracket v10(0).gcode selected for printing
                                          2:10:08 AMM122
                                          === Diagnostics ===
                                          Used output buffers: 1 of 32 (14 max)
                                          === Platform ===
                                          RepRapFirmware for Duet WiFi version 1.19.2 running on Duet WiFi 1.0
                                          Board ID: 08DDM-9FAM2-LW4SD-6J9F6-3S46N-12X7W
                                          Static ram used: 21176
                                          Dynamic ram used: 96200
                                          Recycled dynamic ram: 1408
                                          Stack ram used: 4048 current, 9104 maximum
                                          Never used ram: 3184
                                          Last reset 00:31:37 ago, cause: power up
                                          Last software reset reason: User, spinning module GCodes, available RAM 3136 bytes (slot 4)
                                          Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
                                          Error status: 0
                                          Free file entries: 10
                                          SD card 0 detected, interface speed: 20.0MBytes/sec
                                          SD card longest block write time: 0.0ms
                                          MCU temperature: min 54.7, current 55.3, max 55.6
                                          Supply voltage: min 23.4, current 24.0, max 24.4, under voltage events: 0, over voltage events: 0
                                          Driver 0: standstill
                                          Driver 1: stalled standstill
                                          Driver 2: stalled standstill
                                          Driver 3: standstill
                                          Driver 4: standstill
                                          Date/time: 2017-09-21 02:10:06
                                          Slowest main loop (seconds): 0.176147; fastest: 0.000000
                                          === Move ===
                                          MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
                                          Scheduled moves: 0, completed moves: 0
                                          Bed compensation in use: none
                                          Bed probe heights: 0.245 0.225 0.020 -0.266 -0.374
                                          === Heat ===
                                          Bed heater = 0, chamber heater = -1
                                          Heater 0 is on, I-accum = 0.0
                                          Heater 1 is on, I-accum = 0.5
                                          === GCodes ===
                                          Segments left: 0
                                          Stack records: 2 allocated, 0 in use
                                          Movement lock held by null
                                          http is ready with "M122" in state(s) 0
                                          telnet is idle in state(s) 0
                                          file is idle in state(s) 0
                                          serial is idle in state(s) 0
                                          aux is idle in state(s) 0
                                          daemon is idle in state(s) 0
                                          queue is idle in state(s) 0
                                          autopause is idle in state(s) 0
                                          Code queue is empty.
                                          Network state is running
                                          WiFi module is connected to access point
                                          WiFi firmware version 1.19.2
                                          WiFi MAC address 60:01:94:34:40:06
                                          WiFi Vcc 3.14, reset reason Turned on by main processor
                                          WiFi flash size 4194304, free heap 32424
                                          WiFi IP address 192.168.20.81
                                          WiFi signal strength -57dBm
                                          Reconnections 0
                                          HTTP sessions: 1 of 8
                                          Socket states: 0 0 0 0 0 0 0 0
                                          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
                                          2:10:00 AMM0 H1
                                          File Enclosure bracket v10.gcode print time was 0h 14m

                                          1 Reply Last reply Reply Quote 0
                                          • mhackneyundefined
                                            mhackney
                                            last edited by

                                            My update…

                                            I installed a wifi extender on my network to get a better signal to my Duet WiFi. I'm in the range of about -45dBm now, much better than the -79 I had before.

                                            I've been on a business trip for 3 days but have some additional observations.

                                            I've done 10ish prints before the trip and a few yesterday and did not have any disconnects during the print. The disconnects while idle still occur but they are farther between. The reason is
                                            "An AJAX error has been reported, so the current session has been terminated. Please check if your printer is still on and try to connect again."

                                            M122 shows:
                                            MaxReps: 117, StepErrors: 0, FreeDm: 240, MinFreeDm 120, MaxWait: 3180388ms, Underruns: 0, 1
                                            Scheduled moves: 1, completed moves: 1

                                            The good news is, when this happens, I am able to Connect without restarting the Duet. I did read the new wiki on disconnects and found my AJAX retries was set to 1 so I've changed that to 3 and I'll keep watching.

                                            My 3D Printing blog: http://www.sublimelayers.com
                                            Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

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