Web interface can load, but can't connect to Duet firmware?



  • I was able to "successfully" configure the wifi on my new Duet2 WiFi board. I can load the web interface at its IP address without any trouble, but when I try to press the "connect" button, the web interface errors out saying "Could not establish a connection to the Duet firmware!". It'll usually say that it's connected for a second or two though first.

    Any suggestions for getting this to work?

    Here's the results from running the M122 (diagnostic) command:
    ok
    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS) running on Duet WiFi 1.02 or later
    Board ID: 08DGM-9T6BU-FG3SN-6JKD0-3S46J-9UYHD
    Used output buffers: 1 of 20 (10 max)
    === RTOS ===
    Static ram: 28380
    Dynamic ram: 96148 of which 16 recycled
    Exception stack ram used: 304
    Never used ram: 6224
    Task NETWORK ready, free stack 628
    Task HEAT blocked, free stack 928
    Task MAIN running, free stack 3656
    === Platform ===
    Last reset 00:08:12 ago, cause: watchdog
    Last software reset details not available
    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 28.7, current 28.9, max 28.9
    Supply voltage: min 1.6, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0
    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: 1970-01-01 00:00:00
    Slowest loop: 5.12ms; fastest: 0.07ms
    === Move ===
    Hiccups: 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
    Heater 1 is on, I-accum = 0.0
    === 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 ready with "M122" 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: 1.18ms; fastest: 0.01ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 0 of 8

    • WiFi -
      Network state is running
      WiFi module is connected to access point
      Failed messages: pending 660, notready 0, noresp 0
      WiFi firmware version 1.21
      WiFi MAC address 84:f3:eb:42:af:42
      WiFi Vcc 3.40, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 12872
      WiFi IP address 192.168.0.15
      WiFi signal strength -39dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0
      === Expansion ===
      ok

  • administrators

    @froggyman said in Web interface can load, but can't connect to Duet firmware?:

    Failed messages: pending 660, notready 0, noresp 0
    WiFi firmware version 1.21

    Please try updating the wifi firmware to 1.22 or 1.23beta. As you don't have a good wifi connection yet, you will need to:

    • Download the new DuetWiFiserver.bin file
    • Put the SD card in a PC and copy the new DuetWiFiServer.bin file into the /sys folder, overwriting the one already there
    • Eject/Safely Remove the SD card from the PC and put it back in the Duet
    • Start the Duet and send M997 S1 to install the new WiFi firmware


  • For the people of the future, I was able to update the firmware was suggested, but I still had the same failure of not being able to connect with the web interface.

    Changing my WiFi network channel to channel 6 was able to solve the issue though, which was suggested in another troubleshooting guide I found.


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.