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

Ajax communication error: connection terminated

Scheduled Pinned Locked Moved Solved
General Discussion
5
25
651
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.
  • undefined
    Mklein23
    last edited by 1 Mar 2024, 12:11

    Duet 2 WIFI

    Hi all, I've had a bit of a hiatus for 2 years and I'm finally back into this passion project of my 3d printer. I got a new ISP and now when my printer is in my basement, I get this AJAX error after 30-45 seconds, and can not reconnect unless I power cycle the machine. It does not matter if the machine is moving or not, and it will never reconnect. The connection is completely stable However when the printer is in my office (first floor) I can connect and use it no problem. I have done 3 test prints with no issues. 2 years ago, the printer was in the basement and never had an issue, which is why I'm inclined to believe it has something to do with the ISP change.

    I am completely befuddled. Some useful information(?) is: like I mentioned, I got a new ISP (Century link/quantum fiber) which came with a 2 pod mesh network wifi.

    I am running an old board, version 1.0, and old firmware version 1.19.2.

    Anyways, here's an M122 that I was able to send before the disconnect:

    M122
    === Diagnostics ===
    Used output buffers: 3 of 32 (7 max)
    === Platform ===
    RepRapFirmware for Duet WiFi version 1.19.2 running on Duet WiFi 1.0
    Board ID: 08DDM-9FAM2-LW4S4-6J1DD-3S46T-93T7X
    Static ram used: 21176
    Dynamic ram used: 96416
    Recycled dynamic ram: 1192
    Stack ram used: 1304 current, 4888 maximum
    Never used ram: 7400
    Last reset 00:01:35 ago, cause: power up
    Last software reset reason: User, spinning module GCodes, available RAM 7400 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 29.9, current 34.0, max 34.2
    Supply voltage: min 11.8, current 11.9, max 12.0, under voltage events: 0, over voltage events: 0
    Driver 0: standstill
    Driver 1: standstill
    Driver 2: standstill
    Driver 3: standstill
    Driver 4: standstill
    Date/time: 2024-02-29 22:02:07
    Slowest main loop (seconds): 0.004402; fastest: 0.000034
    === 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.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heater = 0, chamber heater = -1
    === 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 5c:cf:7f:76:6f:17
    WiFi Vcc 3.11, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 32248
    WiFi IP address 192.168.0.15
    WiFi signal strength -42dBm
    Reconnections 0
    HTTP sessions: 1 of 8
    Socket states: 2 0 0 0 0 0 0 0

    undefined 1 Reply Last reply 1 Mar 2024, 12:24 Reply Quote 0
    • undefined
      chrishamm administrators @Mklein23
      last edited by 1 Mar 2024, 12:24

      @Mklein23 said in Ajax communication error: connection terminated:

      RepRapFirmware for Duet WiFi version 1.19.2 running on Duet WiFi 1.0

      RepRapFirmware v1 hasn't been supported for ages. I suggest you upgrade at least to RepRapFirmware v2 or even better to v3. See https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_firmware

      Duet software engineer

      undefined 1 Reply Last reply 1 Mar 2024, 12:32 Reply Quote 0
      • undefined
        Mklein23 @chrishamm
        last edited by 1 Mar 2024, 12:32

        @chrishamm I figured that may be my best way forward. I've been watching firmware installation tutorials all morning.

        Seems like the best bet to jump up from ver 1 to ver 3.1 is to install it using Bossa.

        Will new firmware require new system files? Config.g, homeall,g, etc?

        undefined 1 Reply Last reply 1 Mar 2024, 12:39 Reply Quote 0
        • undefined
          droftarts administrators @Mklein23
          last edited by 1 Mar 2024, 12:39

          @Mklein23 3.4.6 is the current release, not 3.1, so update to that version. You can do that directly with Bossa. Yes, you'll need new configuration files, but don't forget to backup your current SD card to be able to refer to your old config. You can upgrade via DWC rather than Bossa:

          To update to 3.x, if you still have access to DWC, upload these zip files one at a time in the system tab. Don't extract them first. Reboot after each. Use M115 in the gcode console to verify the firmware has been applied.
          https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
          https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
          https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
          https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.5/Duet2and3Firmware-3.4.6.zip
          You'll need to generate a fresh config set for RRF3. https://configtool.reprapfirmware.org/
          There are notes on migrating between 2.x and 3.x here: https://docs.duet3d.com/User_manual/RepRapFirmware/Migration_RRF2_to_RRF3

          Though sometimes it's worth starting with a new SD card to this specification: https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#specification

          Ian

          Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

          undefined 3 Replies Last reply 1 Mar 2024, 22:09 Reply Quote 0
          • undefined
            Mklein23 @droftarts
            last edited by 1 Mar 2024, 22:09

            @droftarts so I downloaded files you linked, and started with 2.05, duet recognizes it as firmware and prompts me to install it. I click yes, some installing happens, and the wifiserver setup gets almost all the way to the end, then the progress bar disappears, and nothing happens. M112 shows firmware 1.19, and wifi 1.0.

            Is there anything I need to check on the board itself?

            I'm using the SD card that came with the board. I can dig around for a different one and try that?

            This is all Greek to me.

            1 Reply Last reply Reply Quote 0
            • undefined
              Phaedrux Moderator
              last edited by 1 Mar 2024, 22:40

              If you still want to do the DWC metho, try updating to 2.0 first.

              Or try sending M997 to trigger a firmware flash.

              If that fails, BOSSA would be the way to go. You'll need to manually update the DWC files in the WWW folder. If that all works you could upload the 3.4.6 zip file again just to ensure you have all the IAP files, etc ready for the next time you update.

              Z-Bot CoreXY Build | Thingiverse Profile

              undefined 1 Reply Last reply 2 Mar 2024, 00:15 Reply Quote 0
              • undefined
                Mklein23 @Phaedrux
                last edited by 2 Mar 2024, 00:15

                @Phaedrux ill give earlier versions a try.

                If I go with bossa, do I still need to install firmwares sequentially, or can I go straight to 3.4?

                1 Reply Last reply Reply Quote 0
                • undefined
                  Mklein23 @droftarts
                  last edited by 2 Mar 2024, 03:29

                  @droftarts I'm finally making progess on this, I had to go back and start at 1.2, then step forward one release at a time looking at the change notes to see when the big changes were.

                  I've had to go
                  1.19(start) > 1.2 > 1.21 > 2.0 > 2.1 > 2.05 > 3.0

                  I tried going to 2.05 first but it wouldn't take. I think in 1.2 and 1.21 had wifi server updates that conflicted with the files in 2.05.

                  Keep on chugging I guess.

                  undefined 1 Reply Last reply 2 Mar 2024, 12:37 Reply Quote 0
                  • undefined
                    Mklein23 @droftarts
                    last edited by 2 Mar 2024, 03:55

                    @droftarts
                    I got up to firmware version 3.3, WIFI server version 1.26, and web interface version 1.22.3

                    Now I'm getting an Error:

                    M997: File 0:/firmware/DuetWiFiServer.bin not found

                    Tried a few older versions of that file name but all give that error.

                    Not sure where to go from here.

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      oliof
                      last edited by 2 Mar 2024, 06:49

                      somewhere at the release train you are at now, Duet3D moved the firmware files from /sys to a dedicated /firmware folder.

                      Best way forward is to create that /firmware folder and moving firmware files (and the iap4e binary IIRC) there.

                      <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        Phaedrux Moderator
                        last edited by 2 Mar 2024, 07:03

                        Don't forget to update the DWC files. The version should match the firmware release version. Things will behave strangely or not work at all if they are out of sync. With such an old version who knows what will happen.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          droftarts administrators @Mklein23
                          last edited by 2 Mar 2024, 12:37

                          @Mklein23 said in Ajax communication error: connection terminated:

                          I've had to go
                          1.19(start) > 1.2 > 1.21 > 2.0 > 2.1 > 2.05 > 3.0

                          I tried going to 2.05 first but it wouldn't take. I think in 1.2 and 1.21 had wifi server updates that conflicted with the files in 2.05.

                          I tested updating from very old versions a while ago. You should be able to update straight to 3.0 from any version later than 1.19, so long as you have the in-app-programmer (iap4e.bin) in the sys folder. You appear not to be uploading the zip file of the firmware release, which should update DWC and WiFi server as well.

                          After updating to 3.0, you can update to the latest, just upload it twice, so firmware folder is created the second time and files are put in the correct place.

                          Occasionally the WiFi update hangs on update from 3.0 to later, and may need a manual update via USB.

                          Ian

                          Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                          undefined 1 Reply Last reply 2 Mar 2024, 13:58 Reply Quote 0
                          • undefined
                            Mklein23 @droftarts
                            last edited by Mklein23 3 Feb 2024, 14:21 2 Mar 2024, 13:58

                            @droftarts This morning I could not connect to the DWC. This morning I followed this video. Things were behaving a bit wonky and the file structure didn't match what was in the documentation so I figured I should start fresh. I followed the documentation for a new SD card and reformatted the card, and followed the above guide for flashing firmware. I tried substituting version 3.5.4 but I got a BOSSA error (I of course didn't write it down) so I figured I would just follow the guide explicitly.

                            And success! (?)

                            Looks like I'm successfully on version 3.1.1. I've copied my M122 below.

                            Can you confirm that the software versions are in order? I have:
                            Duet web control 3.5.0-rc.3
                            duet wifi server as 1.26
                            RR firmware for duet 2 wifi as 3.1.1

                            If that is correct, my next step is to install firmware version 3.5.4 through the DWC.

                            Edit:
                            Upon correcting my config file ( had some end stops set wrong) I get an error message about incompatible software:

                            Incompatible software versions

                            The installed software versions do not match. Please operate your setup only at equal versions to avoid potential incompatibilities and unexpected errors.

                            Please check out the docs on how to upgrade your Duet software components.

                            M122
                            === Diagnostics ===
                            RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
                            Board ID: 08DDM-9FAM2-LW4S4-6J1DD-3S46T-93T7X
                            Used output buffers: 3 of 24 (21 max)
                            === RTOS ===
                            Static ram: 27980
                            Dynamic ram: 94132 of which 44 recycled
                            Exception stack ram used: 276
                            Never used ram: 8640
                            Tasks: NETWORK(ready,384) HEAT(blocked,1224) MAIN(running,1892) IDLE(ready,80)
                            Owned mutexes: WiFi(NETWORK)
                            === Platform ===
                            Last reset 00:09:54 ago, cause: reset button or watchdog
                            Last software reset at 2024-03-01 21:07, reason: User, spinning module GCodes, available RAM 7744 bytes (slot 0)
                            Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task ����
                            Error status: 0
                            MCU temperature: min 32.2, current 33.6, max 34.1
                            Supply voltage: min 0.4, current 0.5, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
                            Driver 0: ok, SG min/max not available
                            Driver 1: ok, SG min/max not available
                            Driver 2: ok, SG min/max not available
                            Driver 3: ok, SG min/max not available
                            Driver 4: ok, SG min/max not available
                            Date/time: 2024-03-02 07:52:23
                            Cache data hit count 1042385207
                            Slowest loop: 28.30ms; fastest: 0.09ms
                            I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                            === Storage ===
                            Free file entries: 10
                            SD card 0 detected, interface speed: 20.0MBytes/sec
                            SD card longest read time 1.8ms, write time 10.8ms, max retries 0
                            === Move ===
                            Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
                            Bed compensation in use: none, comp offset 0.000
                            === MainDDARing ===
                            Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
                            === AuxDDARing ===
                            Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
                            === Heat ===
                            Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
                            === GCodes ===
                            Segments left: 0
                            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
                            USB is idle in state(s) 0
                            Aux is idle in state(s) 0
                            Trigger is idle in state(s) 0
                            Queue is idle in state(s) 0
                            Daemon is idle in state(s) 0
                            Autopause is idle in state(s) 0
                            Code queue is empty.
                            === Network ===
                            Slowest loop: 201.56ms; fastest: 0.07ms
                            Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                            HTTP sessions: 1 of 8

                            • WiFi -
                              Network state is active
                              WiFi module is connected to access point
                              Failed messages: pending 0, notready 0, noresp 2
                              WiFi firmware version 1.26
                              WiFi MAC address 5c:cf:7f:76:6f:17
                              WiFi Vcc 3.39, reset reason Unknown
                              WiFi flash size 4194304, free heap 24000
                              WiFi IP address 192.168.0.15
                              WiFi signal strength -49dBm, reconnections 0, sleep mode unknown
                              Socket states: 0 0 0 0 0 0 0 0
                            1 Reply Last reply Reply Quote 0
                            • undefined
                              Phaedrux Moderator
                              last edited by 2 Mar 2024, 17:58

                              @droftarts said in Ajax communication error: connection terminated:

                              https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
                              https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.5/Duet2and3Firmware-3.4.6.zip

                              Now that you're on 3.1 you should upload these two zip files one at a time. don't extract them first.

                              Z-Bot CoreXY Build | Thingiverse Profile

                              undefined 2 Replies Last reply 2 Mar 2024, 20:21 Reply Quote 0
                              • undefined
                                Mklein23 @Phaedrux
                                last edited by 2 Mar 2024, 20:21

                                @Phaedrux

                                will any config changes/pid tuning that I do on 3.1 need to be re-done after those updates?

                                undefined 1 Reply Last reply 2 Mar 2024, 22:04 Reply Quote 0
                                • undefined
                                  droftarts administrators @Mklein23
                                  last edited by 2 Mar 2024, 22:04

                                  @Mklein23 yes, because the heater tuning parameters have changed. Just redo the heater tuning. You can do the tuning by tool now, which allows compensation for part cooling fans.

                                  Ian

                                  Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                                  undefined 1 Reply Last reply 6 Mar 2024, 14:05 Reply Quote 0
                                  • undefined
                                    Mklein23 @droftarts
                                    last edited by 6 Mar 2024, 14:05

                                    @droftarts said in Ajax communication error: connection terminated:

                                    Just redo the heater tuning

                                    That's the only thing? Config.g and Homex/y/z and tool change files are unchanged?

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      Mklein23 @Phaedrux
                                      last edited by 7 Mar 2024, 04:01

                                      @Phaedrux

                                      Followed your instructions, and started with 3.3, downloaded the *-3.3.zip file, and did not extract it. I followed the "Usual procedure" on the updating firmware documentation, DWC prompted me if I wanted to install the new firmware, I clicked "yes."

                                      I got this error:
                                      M997 S0:1
                                      Error: M997: In-application programming binary "Duet2CombinedIAP.bin" not found

                                      I don't know if this is worth noting, but now my system directory is full of firmware files.

                                      I thought the documentation said that the firmware files are supposed to go into a new file 0/firmware.

                                      ba640a7f-2034-4eff-bd06-cd9892ed445f-image.png

                                      1 Reply Last reply Reply Quote 0
                                      • undefined
                                        Phaedrux Moderator
                                        last edited by 7 Mar 2024, 05:57

                                        What version does your DWC report? It will need to match 3.3, if it doesn't you can download the DWC SD zip file from the 3.3 release and extract it's contents to the www folder on the SD card to get back in sync.

                                        What do you have in the firmware folder? Is that IAP.bin file present there?

                                        Z-Bot CoreXY Build | Thingiverse Profile

                                        undefined 1 Reply Last reply 7 Mar 2024, 12:16 Reply Quote 0
                                        • undefined
                                          Mklein23 @Phaedrux
                                          last edited by Mklein23 3 Jul 2024, 12:19 7 Mar 2024, 12:16

                                          @Phaedrux How do I check the DWC version?

                                          I quick google search only brings up checking the firmware version, not the DWC version.

                                          These are the only files in the 0/firmware folder:
                                          720cf9f2-bf1e-4ddc-b1d8-d8e815324d31-image.png

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