Error: Cannot read file, error code 1. Cancelled printing...



  • Error: Cannot read file, error code 1.
    Cancelled printing file 0:/gcodes/CFFFP_foot.gcode, print time was 6h 21m
    The gcode file was pretty large, around 80MB.

    Something went wrong after over 6 hours. This is one of those random errors you do not want to get.
    The SD card was dismounted, a reboot got it back again. A quick check of the SD card on my PC said all was fine.

    What can I do to avoid this in the future?
    Junk that SD card? Deep format?

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
    Board ID: 08DGM-917NK-F23T0-6JKF6-3S46Q-1GA8D
    Used output buffers: 3 of 20 (18 max)
    === RTOS ===
    Static ram: 25524
    Dynamic ram: 98560 of which 0 recycled
    Exception stack ram used: 600
    Never used ram: 6388
    Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3844) IDLE(ready,200)
    Owned mutexes: WiFi(NETWORK)
    === Platform ===
    Last reset 52:18:21 ago, cause: software
    Last software reset at 2019-01-01 17:56, reason: User, spinning module GCodes, available RAM 6500 bytes (slot 1)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 16
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 39.7ms, max retries 0
    MCU temperature: min 29.7, current 30.4, max 32.7
    Supply voltage: min 23.9, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max 0/1023
    Driver 1: standstill, SG min/max 0/1023
    Driver 2: standstill, SG min/max 0/295
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max 0/1023
    Date/time: 2019-01-03 22:14:28
    Cache data hit count 4294967295
    Slowest loop: 233.60ms; fastest: 0.08ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 125, MaxWait: 885916ms, Underruns: 0, 2
    Scheduled moves: 1, completed moves: 26
    Bed compensation in use: mesh
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    Heater 0 is on, I-accum = 0.0
    Heater 1 is on, I-accum = 0.4
    === 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 idle 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: 181.60ms; fastest: 0.08ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8

    • WiFi -
      Network state is running
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.21
      WiFi MAC address bc:dd:c2:89:a1:c5
      WiFi Vcc 3.36, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 15344
      WiFi IP address 192.168.0.27
      WiFi signal strength -52dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0

  • administrators

    1. Was that the first M122 report you got after the error occurred? I'm surprised that the SD card max retry count is zero.

    2. Was there an "SD card removed" message on the GCode Console or the PanelDue console? If so then a bad solder joint on the SD card socket may be to blame.


 

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