Wireless Issues

  • Yesterday I had started printing a benchy and it printed fine. However, when it was nearing the end the web interface disconnected and I was unable to reconnect.

    It finished printing as I mentioned, and now when I try going to the printer it either cannot find it or it loads up a partial page: http://imgur.com/a/u9fbS

    I can connect to the machine serially, and I can reset the wireless and it gives me:

    Printer is now online.
    >>> M552 s0
    SENDING:M552 S0
    WiFi server stopped
    >>> M552 s1
    SENDING:M552 S1
    WiFi server starting up
    DuetWiFiServer version 1.03 (ch fork)
    Flash size 4194304, free RAM 32816 bytes, WiFi Vcc 3.14V, host name: duetwifi, reset reason: Turned on by main processor
    WiFi server connected to access point Campbell's Soup, IP=, signal strength=-56dBm
    >>> m999
    [ERROR] Can't read from printer (disconnected?) (SerialException): call to ClearCommError failed
    [ERROR] Can't write to printer (disconnected?) (SerialException): WriteFile failed ([Error 22] The device does not recognize the command.)
    Printer is now online.
    >>> m552
    Network is enabled, configured IP address:, actual IP address:, HTTP port: 80

    Not sure why it says a configured IP is different from actual IP.

    I am running versions DuetWebControl-1.14a.bin, DuetWiFiFirmware-1.17e.bin, DuetWiFiServer-1.03-ch.bin

    I am using it with an Apple router, it says the connection is excellent and on, 72Mb/s, -46dBm, 802.11b/g/n mode.

    Any thoughts would be welcome.

  • administrators

    The configured IP address is currently ignored on the Duet WiFi and it always uses dhcp to get can IP address from your router.

    It's normal for the USB to disconnect when you send M999 to reset the printer. But it's odd that after the wireless disconnects, you can't reconnect again without resetting the printer.

    There is a major rewrite of the WiFi module code scheduled, which I hope will improve the situation for those who are having WiFi connection issues. This will happen after the 1.18 firmware release.

  • I just came back much later and turned it on again without issue. But I did discover some suspicious issue with the router - it was on but nothing was connecting to it. It might have gone bad on the duet first, and only later got bad enough to hit the other devices.

Log in to reply