Filament sensor problem after upgrade to 3.2

Alijambo73 · 21 Apr 2022, 03:18

I have a Corexy with 4 extruders. After the upgrade to 3.2 I'm having a problem where if I run M591 D0 it shows filament is present but when I start a print it pauses and says no filament detected E0. It worked fine before the upgrade.

I have this in my config.g "M591 D0 P1 C"e0stop" S1". I can't figure it out. I have read some references to error,g but I'm not sure what that is or if it would be related? Do I need this or is my original pause .g sufficient?

Any thoughts on the filament sensor not detecting filament after the heaters reach temp and clarification on error.g would be welcomed.

Phaedrux · 21 Apr 2022, 04:24

What version were you running before updating to 3.2?

Why did you stop at 3.2 when 3.4 is out now?

Please post your config.g and the results of M122 and M98 P"config.g" as well.

Alijambo73 · 21 Apr 2022, 06:13

@phaedrux I was running 2.03. I was forced to upgrade when my original board died and the replacement I received had 3.2. I have just been making all the changes to my config and this is (as far as I can tell) the only problem.

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later + DueX5
Board ID: 0JD0M-9P6B2-NJ4S4-6JKDA-3S86K-KB16L
Used output buffers: 3 of 24 (21 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73964 of which 96 recycled
Never used RAM 14560, free system stack 182 words
Tasks: NETWORK(ready,155) HEAT(blocked,308) DUEX(blocked,31) MAIN(running,419) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:07:01 ago, cause: power up
Last software reset at 2022-04-20 20:03, reason: User, GCodes spinning, available RAM 14608, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 18.3, current 25.2, max 25.8
Supply voltage: min 23.8, current 24.0, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0, standstill, SG min/max not available
Driver 6: position 0, standstill, SG min/max not available
Driver 7: position 0, standstill, SG min/max not available
Driver 8: position 0, standstill, SG min/max not available
Driver 9: position 0, standstill, SG min/max not available
Driver 10: position 0
Driver 11: position 0
Date/time: 2022-04-21 00:11:22
Cache data hit count 510608225
Slowest loop: 4.43ms; fastest: 0.22ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 6.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
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
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
LCD 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: 23.78ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(1) 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.26
WiFi MAC address 48:3f:da:a6:83:44
WiFi Vcc 3.46, reset reason Power up
WiFi flash size 2097152, free heap 23296
WiFi IP address 192.168.1.221
WiFi signal strength -67dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 4 2 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
=== DueX ===
Read count 1, 0.14 reads/min

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: in file macro line 121 column 55: M911: control character in string
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 608C

config.g

Alijambo73 · 21 Apr 2022, 06:14

Sorry I didn't think this post went through.

dc42 · 21 Apr 2022, 15:21

@alijambo73 what type of filament sensor is it?

Phaedrux · 21 Apr 2022, 19:13

@alijambo73 said in Filament sensor problem after upgrade to 3.2:

Error: in file macro line 121 column 55: M911: control character in string

This error seems to be due to a missing closing quotation mark at the end of your M911 command.

 ;Power Fail Recovery
M911 S21.0 R23.0 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000

Do you still have the config.g file from your previous 2.03 board?

@alijambo73 said in Filament sensor problem after upgrade to 3.2:

3.2.2 running on Duet WiFi

I think it would be a good idea to update to the most recent firmware as well.

If you still have access to DWC. Upload these zip files, one at a time in the system tab. Don't extract them first. Reboot after each. Use M115 in the gcode console to verify the firmware has been applied.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.0/Duet2and3Firmware-3.4.0.zip

That will get your firmware and DWC up to date.

Alijambo73 · 22 Apr 2022, 00:48

@dc42 Traingle labs. I think I solved it thanks to this post I found today.

https://forum.duet3d.com/topic/21610/installing-trianglelab-filament-sensor-fb

The 1k resistor seems to have solved the problem.

Alijambo73 · 22 Apr 2022, 02:02

@phaedrux Will I need to make any config changes?

Phaedrux · 22 Apr 2022, 03:18

@alijambo73 said in Filament sensor problem after upgrade to 3.2:

@phaedrux Will I need to make any config changes?

Not likely.

	;Power Fail Recovery
	M911 S21.0 R23.0 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000