”The last HTTP request has timed out.”



  • Hi Forum
    I hope you can help me with the following.
    My printer was working, until this error started appearing
    ”The last HTTP request has timed out.”
    Apparently the disconnect happends when the extruder starts to heat.
    My heatbed is 220V and doesn´t trigger a disconnect.

    M122
    === Diagnostics ===
    Used output buffers: 3 of 32 (16 max)
    === Platform ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
    Board ID: 08DGM-956GU-DJ3S0-7J9FD-3SJ6K-KAGVF
    Static ram used: 16152
    Dynamic ram used: 100896
    Recycled dynamic ram: 1736
    Stack ram used: 1224 current, 4504 maximum
    Never used ram: 7784
    Last reset 00:05:09 ago, cause: power up
    Last software reset at 2020-01-12 19:59, reason: User, spinning module GCodes, available RAM 7888 bytes (slot 1)
    Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, 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 39.5, current 39.6, max 39.9
    Supply voltage: min 24.6, current 24.7, max 24.9, under voltage events: 0, over voltage events: 0
    Driver 0: standstill, SG min/max not available
    Driver 1: standstill, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2020-01-13 10:59:13
    Slowest main loop (seconds): 0.155631; fastest: 0.000116
    === Move ===
    MaxReps: 0, StepErrors: 0, LaErrors: 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 heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 1 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 ===
    Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8

    • WiFi -
      Network state is running
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.21RC4(08b3)
      WiFi MAC address 5c:cf:7f:76:64:25
      WiFi Vcc 3.37, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 16216
      WiFi IP address 192.168.38.100
      WiFi signal strength -54dBm, reconnections 0, sleep mode modem
      Socket states: 2 0 0 0 0 0 0 0
      === Filament sensors ===
      Extruder 0 sensor: position 0.08, ok, framing errors 0, parity errors 0, no calibration data
      === Expansion ===

    Thank you
    //Poul Erik



  • @Poul-Erik said in ”The last HTTP request has timed out.”:

    1

    the first thing i would try is to update the duetwifi you running v 1.x we are now on v 3.x try to update to 2.05 first and check again if this working then you can go to v3.x



  • Hi Slam
    Thank you, I´ll update and see what happends.
    //pe


  • Moderator

    When coming from such an old firmware definitely read the release notes. There will be some changes to your config required. I would suggest staying with 2.05 to start with. There will be enough major changes between 1.20 and 2.05 to keep you busy. The change to 3.x is even more substantial configuration wise.

    There has been a lot of work and fixes on wifi firmware and DWC between then and now, so your issue may have already been fixed.



  • Hi Phaedrux
    Thank you for your reply.
    I looked through the changes for version 3 firmware and it surely looks "substantial"!
    Where can I download the 2.05 build? I can´t see it on GitHub. Can you point me to it?
    Thanks
    // Poul Erik


  • Moderator

    It should be below the 3.x releases a bit.

    https://github.com/dc42/RepRapFirmware/releases/tag/2.05


  • administrators

    Your WiFi firmware in particular is old. I suggest you upgrade DuetWiFiServer to latest version.



  • Hi DC42
    Thank you for your comment.
    I will update the DuetWiFiServer first, and afterwards update the Firmware to 2,05.

    //Poul Erik



  • Thank you @Phaedrux
    I have updated the printer and I am working on the config.
    //pe



  • Hi @Phaedrux
    What is the preferred way to update the config file?
    I am intimidated by the sheer amount of changes, and worried to overlook something!
    Will I have to read through all changes from my previous firmware, as they are listed here?
    https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md
    Or is there a summary somewhere, with relevant changes for 3d printers or even for Delta printers?

    Kind Regards
    //Poul Erik


  • Moderator

    Yes it's a good idea to read through the what's new page. Or at least skim it for things that seem relevant. The biggest changes for each version are called out at the start usually.

    If after going through that you're not sure what to do, you can post your current config file set in a new thread and get some feedback on what should be changed.



  • @Phaedrux @dc42

    Hi Forum

    I thought that I found the reasen for the ustable internet, but unfortunately the instability has returned.
    After updating the firmware to version 2.05 /WiFi firmware version 1.23, and still had the issue, I found that My ”Philips Hue” was using the same IP address as the printer. When I changed the IP address, the Wifi connection became stable.
    Some days has passed and the trouble is back.
    I can connect to the printer, but when I send a print command, or some other command, the Wifi connection turns of and immediately afterwards it connects up again.
    I have tried to execute a print local on the printer, and the same thing happends, the screen goes black, then turns back on, and the printer is idle, no print is executed.
    Can you help me? It would be much appreciated.
    Kind Regards
    Poul Erik

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet WiFi 1.02 or later
    Board ID: 08DGM-956GU-DJ3S0-7J9FD-3SJ6K-KAGVF
    Used output buffers: 1 of 24 (6 max)
    === RTOS ===
    Static ram: 25712
    Dynamic ram: 93000 of which 0 recycled
    Exception stack ram used: 312
    Never used ram: 12048
    Tasks: NETWORK(ready,764) HEAT(blocked,1176) MAIN(running,3736) IDLE(ready,160)
    Owned mutexes:
    === Platform ===
    Last reset 00:00:41 ago, cause: power up
    Last software reset at 2020-01-22 20:19, reason: User, spinning module GCodes, available RAM 11868 bytes (slot 3)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 39.5, current 40.3, max 40.5
    Supply voltage: min 24.6, current 24.7, max 24.9, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max not available
    Driver 1: standstill, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2020-01-26 12:08:44
    Cache data hit count 104594956
    Slowest loop: 1.34ms; fastest: 0.07ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Move ===
    Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
    Bed compensation in use: none, comp offset 0.000
    === DDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 1 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 ===
    Slowest loop: 15.51ms; fastest: 0.00ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8

    • WiFi -
      Network state is running
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.23
      WiFi MAC address 5c:cf:7f:76:64:25
      WiFi Vcc 3.37, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 24424
      WiFi IP address 192.168.38.101
      WiFi signal strength -53dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0
      === Filament sensors ===
      Extruder 0: pos 0.04, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0

  • Moderator

    @Poul-Erik the fact that it fails like that when trying to start a local print as well would indicate It's not a wifi issue at all but perhaps a power supply?



  • @Phaedrux
    Thank you for the comment.
    I get what you are saying. Is there a guide to trouble shooting the powersupply. As you may have guessed, I´m not an electrical engeneer!
    This forum is just so helpfull!
    Kind Regards
    Poul Erik


  • Moderator

    Well in your m122 report it indicates the supply voltage was ok.

    I'm not sure what the last reset code indicates though. Was that report gathered after the last time it reset?

    When it resets do the fans and lights and everything stop?



  • @Phaedrux
    I checked again to see when the "blackout" happens.

    1. Job sent to printer.
    2. Bedheater starts 230v, and finish heating.
    3. Duet shuts down as extruder starts heating.
    4. Blackscreen for a second or so. There is a red light just above the Wifi module, that turns off for a second, all other lights on the board stay on.
    5. Duet restarts in Idle state.

    Any Ideas?
    //pe



  • @Poul-Erik said in ”The last HTTP request has timed out.”:

    Duet shuts down as extruder starts heating.

    does this happen if you just turn on the heater via the web interface to the printing temperature?



  • @Veti said in ”The last HTTP request has timed out.”:

    on the heater via the web interface to the printing temperature?
    Hi Veti
    Yes it does. I think we are closing in on something.
    Does it have to do with the extruder heater?



  • @Poul-Erik said in ”The last HTTP request has timed out.”:

    Does it have to do with the extruder heater?

    very likely. check for short circuits using a multimeter. check the resistance of the heater catrige.



  • @Veti
    Thank you Veti
    I´ll give that a try.
    //pe


Log in to reply