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

Wyvern

I'm not sure, but it looks like the shield grounds, but nothing I haven't seen before.

If it makes you feel better put down some flux and kiss those connections with an iron.

Sounds like an SD issue though.

Try to get the identical SD card, just so there are no compatibility issues.

nz_andy

I possibly have the same issue, was there any resolution to this?

Same Error: "Error: Cannot read file, error code 1. Cancelling printing"

I am printing 10 x 24 hour prints I have not changed the file, 7 times it has worked no problem, on 3 prints this error has happened but not in the same place, i.e. it could be anywhere in the print process.

I do need to resolve this, so some help would be great.

Below is the diagnostics:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4SD-6J9F6-3S46K-12XMW
Used output buffers: 1 of 20 (15 max)
=== RTOS ===
Static ram: 28380
Dynamic ram: 95872 of which 0 recycled
Exception stack ram used: 420
Never used ram: 6400
Task NETWORK ready, free stack 324
Task HEAT blocked, free stack 1200
Task MAIN running, free stack 3592
=== Platform ===
Last reset 10:45:36 ago, cause: software
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 6344 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0041f000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 40.9, current 41.1, max 41.8
Supply voltage: min 23.8, current 24.1, max 25.4, under voltage events: 0, over voltage events: 0
Driver 0: standstill, SG min/max 0/0
Driver 1: standstill, SG min/max 0/0
Driver 2: standstill, SG min/max 0/0
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2019-03-27 08:23:58
Slowest loop: 160.89ms; fastest: 0.08ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 236, MaxWait: 317525ms, Underruns: 0, 0
Scheduled moves: 15, completed moves: 29
Bed compensation in use: none
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
=== 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: 7.73ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 2 of 8

WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 152, notready 0, noresp 0
WiFi firmware version 1.21RC3(28b1)
WiFi MAC address 60:01:94:30:06:48
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 14584
WiFi IP address 192.168.20.30
WiFi signal strength -56dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: position 0.00, ok, measured sensitivity 2.769mm/pulse +221% --123%
=== Expansion ===

dc42

@nz_andy, upgrade your firmware to 2.02. It includes retry code for when SD card errors occur.

Both of you, I suggest you replace the SD card.

bondus

I replaced the SD card. It has worked perfectly since.

I tested the "bad" SD card on my PC using some SD card testing software. It ran flawlessly for a week (I forgot I had started it).

But I still threw it away.

domingo

I have the same problem, I have already burned a lot of plastic for this problem and I don't know what else to do, change SD, install and reinstall to 2.04, the welds are fine ... what can I do?
I also read this post
https://forum.duet3d.com/topic/6788/cannot-read-file-error-code-1

dc42

@domingo said in Error: Cannot read file, error code 1. Cancelled printing...:

I have the same problem, I have already burned a lot of plastic for this problem and I don't know what else to do, change SD, install and reinstall to 2.04, the welds are fine ... what can I do?
I also read this post
https://forum.duet3d.com/topic/6788/cannot-read-file-error-code-1

Are you saying that you get this error even when using firmware 2.04 and a new SD card?

domingo

@dc42 unfortunately, the prints always stop at the same point, replace the SD card with a newly purchased one and reinstall all the software, check the connector welds, reconnect and check all the wiring, I don't know what else to try

dc42

@domingo said in Error: Cannot read file, error code 1. Cancelled printing...:

@dc42 unfortunately, the prints always stop at the same point, replace the SD card with a newly purchased one and reinstall all the software, check the connector welds, reconnect and check all the wiring, I don't know what else to try

Does it give the same error if you run the print in simulation mode?

domingo

@dc42 if I just tried several models and in simulation they end well,I've tried again in normal mode and I have another half piece Now I have a horde of turtles

dc42

@domingo, which firmware version are you using?

dc42

@domingo, is this still a problem? if so, please report which firmware version you are using.

domingo

@dc42 RepRapFirmware for Duet 2 WiFi/Ethernet version 2.04 running on Duet WiFi 1.02 or later

dc42

Thanks. There a chance (although not a large one I admit!) that changes to DMA handling in firmware 2.05RC1 may have fixed this, so please try that version.

I have this issue on my list to resolve in the 2.05 firmware release.

domingo

@dc42 ok, I update now to 2.05rc1 and I am telling you the progress, thank you very much for the great work and support

dc42

@domingo said in Error: Cannot read file, error code 1. Cancelled printing...:

@dc42 ok, I update now to 2.05rc1 and I am telling you the progress, thank you very much for the great work and support

Thanks for that information. Please let me know immediately if the problem returns. For now I will treat it as fixed.

domingo

@dc42 of course I would let you know, for now, after the last update, the two pieces went well

domingo

Hello @dc42 , upgrade from Release 2.05RC1 to Release 2.05RC2 and I have the same problems again.

This is possible?
any solution?

domingo

@dc42 ohh the bug has returned in Release 2.05 final

dc42

@domingo, is this still a problem? Are you running firmware 2.05.1 now?