• I'm starting to get ERR_CONNECTION_TIMED_OUT from time to time. Wondering if it is time to get another one to replace it. I mean, it's living in a quite harsh environment and 2 years in a dirty workshop with high temp in the summer and damn cold in the winter may take its toll.

    I'm able to connect to with over usb. Included is the M122 result.

    Anything else I could check before I buy a replacement?


    === Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet Ethernet 1.02 or later<LF>Board ID: 08DGM-917NK-F2MS4-7JKD2-3SN6K-TGU4G<LF>Used output buffers: 1 of 24 (9 max)<LF>=== RTOS ===<LF>Static ram: 25712<LF>Dynamic ram: 92904 of which 0 recycled<LF>Exception stack ram used: 424<LF>Never used ram: 12032<LF>Tasks: NETWORK(ready,652) HEAT(blocked,1232) MAIN(running,3736) IDLE(ready,160)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 00:13:26 ago, cause: power up<LF>Last software reset at 2020-12-03 08:07, reason: User, spinning module GCodes, available RAM 12064 bytes (slot 0)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d<LF>Error status: 10<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 385.6ms, max retries 0<LF>MCU temperature: min 12.3, current 14.9, max 16.4<LF>Supply voltage: min 23.7, current 24.3, max 24.5, under voltage events: 0, over voltage events: 0,[Warning: Maximal number of bytes per line exceeded! Check the EOL (end-of-line) settings or increase the limit in the advanced terminal settings.]

  • Moderator

    Please change the end of line settings in YAT so that we can see the full M122 report with proper formatting.


Log in to reply