@deckingman Yes, it is RepRap. I disconnected the Paneldue and was able to do a 2.5 hour print with no issues and no Bad commands appearing in the logs.
I will be changing the PanelDue cable to a shielded one later today (after work) and trying again.
@T3P3Tony I don't believe it is an SD card issue, or file corruption issue as I tried with a new card and new file. I also verified the files are proper when compared to eachother.
@deckingman this has all my config files and a copy of the G-code.
https://www.dropbox.com/sh/yvealx81yym4kqh/AACMONG_FHO9DB7TqGrw7dyia?dl=0
Also, Note. I tried using different slicers, and got the error in all of them.
Feel free to take a look and let me know if you can see what's happening.
It was a fresh g-code. I also tried a different print and it ended up giving the same Attempting to extrude error.
I changed out the SD card with a new out of the box class 10 one. This was my output of the eventlog. The print did complete.
2020-09-27 00:25:13 Event logging started
2020-09-27 00:25:35 Error: Bad command: J184 M409 F"d99f"*71
2020-09-27 00:26:15 Error: M409: control character in string
2020-09-27 00:26:56 Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset.
2020-09-27 00:31:03 Error: M409: control character in string
2020-09-27 00:36:36 Error: Bad command: s73 M409 F"d99f"
2020-09-27 00:36:37 Error: Bad command: `M409 F"d99f"
2020-09-27 00:36:38 Error: Bad command: >0M409 F"d99f"+72
2020-09-27 00:36:56 Warning: M609: Command is not supported
2020-09-27 00:37:00 Error: Bad command: M<09 F"d99f"
2020-09-27 00:37:06 Error: Bad command: ^403 M409 F"d99f"*77
2020-09-27 00:37:11 Error: M409: control character in string
2020-09-27 00:37:55 Error: M409: expected string expression
2020-09-27 00:38:19 Warning: M40: Command is not supported
2020-09-27 00:38:26 Warning: M429: Command is not supported
2020-09-27 00:41:23 Error: M409: control character in string
2020-09-27 00:41:47 Error: M409: control character in string
2020-09-27 00:41:55 Warning: M429: Command is not supported
2020-09-27 00:45:03 Error: Bad command: $M409 F"d99f"
2020-09-27 00:48:07 Error: Bad command: O409 F"d99f"
2020-09-27 00:48:23 Error: Bad command: O628 M409 F"d99f"*70
2020-09-27 00:49:36 Error: Bad command: `m409 F"d99f#*78
2020-09-27 00:51:28 Error: Bad command: < M409 F"d99f"
2020-09-27 00:53:12 Error: M409: control character in string
2020-09-27 00:53:52 Warning: M40: Command is not supported
2020-09-27 00:54:20 Error: Bad command: ?17 M409 F"d99f"
2020-09-27 00:54:48 Error: M4: Command is not supported in machine mode FFF
2020-09-27 00:55:40 Error: Bad command: `M409 F"d99f"
2020-09-27 00:57:00 Error: Bad command: `M409 F"d99f"
2020-09-27 00:58:32 Warning: M40: Command is not supported
2020-09-27 01:00:28 Error: M4: Command is not supported in machine mode FFF
2020-09-27 01:02:05 Error: M409: expected string expression
2020-09-27 01:02:53 Warning: M40: Command is not supported
2020-09-27 01:05:57 Error: Bad command: :91 M409 F"d99f"
2020-09-27 01:11:05 Error: M409: expected string expression
2020-09-27 01:12:05 Error: Bad command: 3 M409 K"job" F"v"
2020-09-27 01:14:26 Error: Bad command: 018 M409 F"d99f"
2020-09-27 01:15:22 Error: M409: expected string expression
2020-09-27 01:15:34 Error: M409: expected string expression
2020-09-27 01:17:58 Error: M4: Command is not supported in machine mode FFF
2020-09-27 01:18:34 Error: Bad command: (M409 K"job" F"v"
2020-09-27 01:20:38 Error: M409: expected string expression
2020-09-27 01:24:42 Error: Bad command: J1172 M409 F"d99f"*127
2020-09-27 01:26:48 Warning: M509: Command is not supported
2020-09-27 01:28:26 Error: Bad command: y M409 F"d99f"
2020-09-27 01:30:55 Error: M4: Command is not supported in machine mode FFF
2020-09-27 01:31:11 Error: Bad command: :0 M409 K"job" F"v"
2020-09-27 01:34:27 Warning: M40: Command is not supported
2020-09-27 01:36:11 Error: Bad command: 55 M409 F"d99f"
2020-09-27 01:37:53 Finished printing file 0:/gcodes/Printer Parts/Flying_Bondtech.gcode, print time was 1h 14m
ok, Nevermind... happened again. Here is the Diagnostic logs.
@dc42 I tested the resistance, and it is below 0.1. Also the wires are not near any stepper motors.
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L2MS8-6JTDD-3S06N-98HLP
Used output buffers: 3 of 24 (24 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93556 of which 92 recycled
Exception stack ram used: 528
Never used ram: 8916
Tasks: NETWORK(ready,308) HEAT(blocked,1224) MAIN(running,1788) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:43:59 ago, cause: software
Last software reset at 2020-09-26 21:20, reason: User, spinning module GCodes, available RAM 9316 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 4
MCU temperature: min 33.0, current 35.7, max 36.1
Supply voltage: min 24.4, current 24.6, max 24.8, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, SG min/max 0/205
Driver 1: ok, SG min/max 0/211
Driver 2: ok, SG min/max 0/201
Driver 3: standstill, SG min/max 0/193
Driver 4: standstill, SG min/max not available
Date/time: 2020-09-26 22:04:29
Cache data hit count 4029131711
Slowest loop: 59.57ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 5.1ms, write time 28.9ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 166, MinFreeDm: 101, MaxWait: 703770ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 29343, completed moves: 29335, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: 3
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.3
=== GCodes ===
Segments left: 2
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) 2
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 63.59ms; fastest: 0.00ms
Responder states: HTTP(4) HTTP(2) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address dc:4f:22:6e:60:44
WiFi Vcc 3.34, reset reason Unknown
WiFi flash size 4194304, free heap 24568
WiFi IP address 192.168.1.253
WiFi signal strength -51dBm, reconnections 0, sleep mode modem
Socket states: 2 2 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
I am still not sure what's happening here. Can someone please assist!?!?!?
Here is a download of all the Duet Config files.
https://www.dropbox.com/s/9okmtuly2bz2gmk/Duet Configs.zip?dl=0
ok, so I have now done 2 prints without this error happening.
Here was my fix.
I have no idea why, but this worked so far. I'm going to keep this open until i get a good 10 prints with no more of this error.
Update: ran a test print, same issue.
I am now downgrading versions of the duet firmware to 3.0 to see if that resolves it.
Sorry to bring up an old thread, I am having the exact same issue. Has there been any updates to this?
I have removed that line. I'll run another test print to verify.