Duet wifi problems



  • I'm posting this in general because I don't know what exactly is the problem, is it hardware, software or firmware.

    My duet wifi has been disconnecting and the wifi board most of the time didn't even start to connect.
    Resting the board would sometimes solve it but it would still disconnect after some time.

    Today I decided to update everything on the board to the newest versions (I was on firmware 1.21). After updating I was able to open DWC where I did the final edit of config.g to change the g-codes to 3.xx compatible codes as it is advised on the wiki.
    After turning the board on again it stopped connecting to my wifi and if I connect it over USB it says that it's connected but I cannot connect to it my browser.


  • Moderator

    @MrIvorVra Can you post your config.g, and full response to M122?

    Are you getting a blue light on the WiFi module? Send M552 to see network connection status, which should report the current IP address. See if you can connect to that.

    Compare the files on your SD card with https://duet3d.dozuki.com/Wiki/SD_Card#Section_Creating_the_file_structure
    You may have updated the DWC, so file names may be different.

    Ian



  • Before seeing your response I went and redid the the whole firmware installation.
    It decided to work all of a sudden.
    First time connecting it had some problems so I went and changed the WiFi channel form 13 to 7 on my router.
    So far the connection is stable

    On the old firmware the led on the Wifi module would just blink and then stop blinking. That would happen a lot while literally nothing was changed hardware vise.

    Now, M122 reports WiFi signal strength -70 which is weird because when I initially when I set up the printer two years ago it was -50 and the printer was not moved from it's original spot. And there were no modifications that would've interfered with the WiFi.

    The M122 Report

    • SENT: M122
    • READ: === Diagnostics ===
    • READ: RepRapFirmware for Duet 2 WiFi/Ethernet version 3.01-RC10 running on Duet WiFi 1.02 or later
    • READ: Board ID: 08DGM-956GU-DJMSN-6J9F4-3SD6S-1VRHHUsed output buffers: 1 of 24 (10 max)
    • READ: === RTOS ===
    • READ: Static ram: 28044
    • READ: Dynamic ram: 92912 of which 172 recycled
    • READ: Exception stack ram used: 304
    • READ: Never used ram: 9640
    • READ: Tasks: NETWORK(ready,200) HEAT(blocked,1228) MAIN(running,1904) IDLE(ready,80)
    • READ: Owned mutexes: WiFi(NETWORK)
    • READ: === Platform ===
    • READ: Last reset 00:01:08 ago, cause: software
    • READ: Last software reset at 2020-04-30 12:57, reason: User, spinning module GCodes, available RAM 9688 bytes (slot 0)
    • READ: Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    • READ: Error status: 0
    • READ: Free file entries: 10
    • READ: SD card 0 detected, interface speed: 20.0MBytes/sec
    • READ: SD card longest block write time: 0.0ms, max retries 0
    • READ: MCU temperature: min 37.4, current 38.9, max 39.3
    • READ: Supply voltage: min 12.2, current 12.3, max 12.4, under voltage events: 0, over voltage events: 0, power good: yes
    • READ: Driver 0: standstill, SG min/max not available
    • READ: Driver 1: standstill, SG min/max not available
    • READ: Driver 2: standstill, SG min/max not available
    • READ: Driver 3: standstill, SG min/max not available
    • READ: Driver 4: standstill, SG min/max not available
    • READ: Date/time: 2020-04-30 12:58:15
    • READ: Cache data hit count 120397639
    • READ: Slowest loop: 5.71ms; fastest: 0.13ms
    • READ: I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    • READ: === Move ===
    • READ: Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
    • READ: Bed compensation in use: none, comp offset 0.000
    • READ: === MainDDARing ===
    • READ: Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
    • READ: === AuxDDARing ===
    • READ: Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
    • READ: === Heat ===
    • READ: Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
    • READ: Heater 1 is on, I-accum = 0.0
    • READ: === GCodes ===
    • READ: Segments left: 0
    • READ: Movement lock held by null
    • READ: HTTP is idle in state(s) 0
    • READ: Telnet is idle in state(s) 0
    • READ: File is idle in state(s) 0
    • READ: USB is ready with "M122" in state(s) 0
    • READ: Aux is idle in state(s) 0
    • READ: Trigger is idle in state(s) 0
    • READ: Queue is idle in state(s) 0
    • READ: Daemon is idle in state(s) 0
    • READ: Autopause is idle in state(s) 0
    • READ: Code queue is empty.
    • READ: === Network ===
    • READ: Slowest loop: 16.23ms; fastest: 0.00ms
    • READ: Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
    • READ: HTTP sessions: 1 of 8
    • READ: - WiFi -
    • READ: Network state is active
    • READ: WiFi module is connected to access point
    • READ: Failed messages: pending 0, notready 0, noresp 0
    • READ: WiFi firmware version 1.23
    • READ: WiFi MAC address 60:01:94:73:5f:05
    • READ: WiFi Vcc 3.31, reset reason Unknown
    • READ: WiFi flash size 4194304, free heap 25944
    • READ: WiFi IP address 192.168.5.75
    • READ: WiFi signal strength -68dBm, reconnections 0, sleep mode modem
    • READ: Socket states: 0 0 0 0 0 0 0 0
    • READ: ok

    I watch the old firmware connect and start to send data to firefox and then not actually sending anything.


  • Moderator

    @MrIvorVra said in Duet wifi problems:

    And there were no modifications that would've interfered with the WiFi.

    Neighbours? Try a different wifi channel on your router?


Log in to reply