Can't connect to DWC.



  • Haven't had any issues with my printer until tonight.
    I can't seem to connect to DWC.

    The board seems to be working properly as all of the lights are lit, including a solid blue confirming it's connection to Wifi. The endstop indicators are lit and solid.
    I have logged into my router and the Duet is indeed connected with the same ip address I assigned it.
    I have connected to it via YAT, and WIFI is connected stating the same ip address the router shows as connected.
    I have tried 2 different browsers on my pc, and I even disabled my antivirus in case maybe it was interfering.
    I have even tried connecting from a different PC but no joy.
    All errors state "This site can't be reached. Connection Reset".

    I have rebooted my router, and cycled the power on the Duet.

    I am running Firmware version 2.02RC6. It's run flawlessly for the couple of months I have had it installed.

    Is it possible that parts of the firmware have become corrupted, and I need to reinstall?



  • That's odd.

    Can you send M122 from the terminal and post the results?



  • @phaedrux said in Can't connect to DWC.:

    That's odd.

    Can you send M122 from the terminal and post the results?

    === Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02RC6(RTOS) running on Duet WiFi 1.02 or later<LF>Board ID: 08DDM-9FAM2-LW4SD-6JKF0-3S46K-T2XZW<LF>Used output buffers: 1 of 20 (1 max)<LF>=== RTOS ===<LF>Static ram: 25524<LF>Dynamic ram: 98516 of which 0 recycled<LF>Exception stack ram used: 304<LF>Never used ram: 6728<LF>Tasks: NETWORK(ready,880) HEAT(blocked,1232) MAIN(running,3884) IDLE(ready,200)<LF>Owned mutexes: SD0(NETWORK)<LF>=== Platform ===<LF>Last reset 01:23:19 ago, cause: power up<LF>Last software reset at 2019-01-08 22:09, reason: User, spinning module GCodes, available RAM 6476 bytes (slot 2)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d<LF>Error status: 0<LF>Free file entries: 8<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 0.0ms, max retries 2<LF>MCU temperature: min 29.2, current 31.8, max 32.5<LF>Supply voltage: min 0.6, current 0.7, max 0.8, under voltage events: 0, over voltage <Warning: Maximal number of bytes per line exceeded! Check the end-of-line settings or increase the limit in the advanced terminal settings.>



  • Let's try this again.
    My first time using YAT...

    === Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02RC6(RTOS) running on Duet WiFi 1.02 or later<LF>Board ID: 08DDM-9FAM2-LW4SD-6JKF0-3S46K-T2XZW<LF>Used output buffers: 1 of 20 (1 max)<LF>=== RTOS ===<LF>Static ram: 25524<LF>Dynamic ram: 98516 of which 0 recycled<LF>Exception stack ram used: 304<LF>Never used ram: 6728<LF>Tasks: NETWORK(ready,880) HEAT(blocked,1232) MAIN(running,3884) IDLE(ready,200)<LF>Owned mutexes: SD0(NETWORK)<LF>=== Platform ===<LF>Last reset 01:23:19 ago, cause: power up<LF>Last software reset at 2019-01-08 22:09, reason: User, spinning module GCodes, available RAM 6476 bytes (slot 2)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d<LF>Error status: 0<LF>Free file entries: 8<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 0.0ms, max retries 2<LF>MCU temperature: min 29.2, current 31.8, max 32.5<LF>Supply voltage: min 0.6, current 0.7, max 0.8, under voltage events: 0, over voltage events: 0, power good: n
    o<LF>Driver 0: ok, SG min/max not available<LF>Driver 1: ok, SG min/max not available<LF>Driver 2: ok, SG min/max not available<LF>Driver 3: ok, SG min/max not available<LF>Driver 4: ok, SG min/max not available<LF>Date/time: 1970-01-01 00:00:00<LF>Cache data hit count 829270803<LF>Slowest loop: 239.64ms; fastest: 0.06ms<LF>I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0<LF>=== Move ===<LF>Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0<LF>Scheduled moves: 0, completed moves: 0<LF>Bed compensation in use: none<LF>Bed probe heights: 0.000 0.000 0.000 0.000 0.000<LF>=== Heat ===<LF>Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1<LF>=== GCodes ===<LF>Segments left: 0<LF>Stack records: 1 allocated, 0 in use<LF>Movement lock held by null<LF>http is idle in state(s) 0<LF>telnet is idle in state(s) 0<LF>file is idle in state(s) 0<LF>serial is ready with "M122" in state(s) 0<LF>aux is idle in state(s) 0<LF>daemon is idle in state(s) 0<LF>queue is idle in state(s) 0<LF>autopause is idle in state(s) 0<LF>Code queue is empty.<LF>=== Network ===<LF>Slowest loop: 239.73ms; fastest: 0.00ms<LF>Responder states: HTTP(2) HTTP(2) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)<LF>HTTP sessions: 0 of 8<LF>- WiFi -<LF>Network state is running<LF>WiFi module is connected to access point <LF>Failed messages: pending 0, notready 0, noresp 0<LF>WiFi firmware version 1.21<LF>WiFi MAC address 5c:cf:7f:ee:6a:3a<LF>WiFi Vcc 3.43, reset reason Turned on by main processor<LF>WiFi flash size 4194304, free heap 15472<LF>WiFi IP address 192.168.1.229<LF>WiFi signal strength -49dBm, reconnections 0, sleep mode modem<LF>Socket states: 2 2 0 0 0 0 0 0<LF>ok<LF>



  • I think there is an option in YAT for new line or something like that that should fix the <LF> stuff and create an actual line break. Makes it far easier to view.

    I can't see anything obvious to me in there.

    Here's what I suggest you try.

    Download the latest firmware here: https://github.com/dc42/RepRapFirmware/releases/download/2.02/Duet2Firmware-2.02a.zip

    Normally you'd be able to just upload that to the DWC and it would update everything, but since you don't have access to the DWC we'll have to do it manually. So you'll have to pull your SD card and use your PC to put the Duet2CombinedFirmware.bin and DuetWiFiServer.bin files into the SYS folder.

    Then download the updated DWC files here: https://github.com/dc42/RepRapFirmware/releases/download/2.02/DuetWebControl-1.22.6.zip
    Extract the contents to the WWW folder.

    Then put your card back into the duet and power up.
    Use the terminal to send command M997 S0 to install the firmware.
    The board should reboot.
    Then send command M997 S1 to install the wifi module firmware.
    The board should reboot again.

    Hopefully that will be enough to get back up and running.



  • You sir, are a scholar and a gentleman. That did the trick.
    I guess something was corrupted.

    I could've tried installing the latest before I asked, since I was suspecting that was the fix anyway, huh?
    But maybe someone who has the same issue will stumble across this.

    Thanks a million!



  • Glad it's working now.

    It's always a good idea to update to the full release if you're testing release candidates anyway.



  • @phaedrux said in Can't connect to DWC.:

    Glad it's working now.

    It's always a good idea to update to the full release if you're testing release candidates anyway.

    Noted.
    I hadn't intended on keeping a RC as a daily driver but it was working fine and I didn't think about it.


Log in to reply