Spurios "sensor not work" and not enough movement faults
-
@invertmast with the laser filament monitor I started getting "sensor not working " pauses even though the sensor was disabled. I think it was a poor connection - since recrimping at the board end it hasn't recurred.
-
another "sensor not working" fault yet the M591 says the sensor was working fine.
Duet3D magnetic filament monitor on input 3, enabled, sensitivity 25.50mm/rev, allow 70% to 120%, check every 20.0mm, version 3, mag 132 agc 111, measured sensitivity 26.26mm/rev, min 91% max 103% over 40330.0mm
-
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-956GU-DJ3SJ-6J9DD-3SD6S-9UPZH
Used output buffers: 1 of 24 (15 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 94152 of which 0 recycled
Exception stack ram used: 496
Never used ram: 10712
Tasks: NETWORK(ready,628) HEAT(blocked,1232) DUEX(suspended,160) MAIN(running,3800) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 41:41:36 ago, cause: software
Last software reset at 2020-04-10 13:16, reason: User, spinning module GCodes, available RAM 10744 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04417000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 18
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 395.3ms, max retries 0
MCU temperature: min 18.4, current 18.7, max 24.0
Supply voltage: min 23.6, current 24.3, max 25.1, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/184
Driver 1: standstill, SG min/max 0/1023
Driver 2: standstill, SG min/max 0/1023
Driver 3: standstill, SG min/max 0/316
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max 0/1023
Driver 6: standstill, SG min/max 0/1023
Driver 7: standstill, SG min/max 0/1023
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2020-04-12 06:57:39
Cache data hit count 4294967295
Slowest loop: 74.87ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 132, MaxWait: 40239061ms
Bed compensation in use: mesh, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== 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.8
=== GCodes ===
Segments left: 0
Stack records: 2 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: 395.42ms; fastest: 0.00ms
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 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 5c:cf:7f:76:63:7a
WiFi Vcc 3.40, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24136
WiFi IP address 192.168.254.19
WiFi signal strength -56dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0: pos 74.18, errs: frame 1 parity 0 ovrun 0 pol 1 ovdue 0
- WiFi -
-
I am seeing the exact same issues, I have a few other posts in this category abou tit as well... Its incredibly frustrating. I just had to disable the sensors entirely to keep them from screwing up prints. As someone noted, even setting the M591 Dx to S0 wont stop "Sensor Not Working" errors. I've gotten the "Sensor Not working" errors on the extruder that wasnt even being used in a print before! (I have an IDEX rig)
You have to set to M591 Dx S0 P0 to fully disable the sensor(s) to stop the errors.
I am happy someone else is seeing this problem cause its driving me insane.
I've also done new wires, new crimps, shorter wires, even had a sensor RMA'd to see if that helped. I also tried differnet endstops (CONN_LCD and E1/Z endstops) per @dc42 @droftarts and others recommendations.
A geek designing and building his own custom IDEX printer from scratch as seen here: https://joekelly.co/3d/
-
Its also interesting you are running a Duex as well. Curious if there is some commonality there and the reason others aren't reporting this.
-
@clegg78 said in Spurios "sensor not work" and not enough movement faults:
I am seeing the exact same issues, I have a few other posts in this category abou tit as well... Its incredibly frustrating. I just had to disable the sensors entirely to keep them from screwing up prints. As someone noted, even setting the M591 Dx to S0 wont stop "Sensor Not Working" errors. I've gotten the "Sensor Not working" errors on the extruder that wasnt even being used in a print before! (I have an IDEX rig)
You have to set to M591 Dx S0 P0 to fully disable the sensor(s) to stop the errors.
I am happy someone else is seeing this problem cause its driving me insane.
I've also done new wires, new crimps, shorter wires, even had a sensor RMA'd to see if that helped. I also tried differnet endstops (CONN_LCD and E1/Z endstops) per @dc42 @droftarts and others recommendations.
It is incredibly frustrating! I just sanded a good bit of the pcb side of the housing down and was able to get the AGC down to around 80. I then did right at a 2 hour print with absolutely NO errors or pauses, which is the longest print i've had go error free since i installed it !
The range of output was between 84% and 104%, which was a significant increase as well.
I'm about to do a 8 hour print, so fingers crossed it actually helps!
-
well so much for those good vibes. 20 minutes into the print and it error'd with "Extruder 0 reports not enough movement"....
-
I had several not enough movement errors when I first installed the mag sensor. I was able to flash the firmware up to version 3 which did not really help, but it did show that the agc was in a good place, stays around 70. I had to really go through my printer and make sure everything was spot on. Delta, 1 meter Bowden tube, E3d V6 hot end and Duet smart effector. The big break through was reducing the exstruder motor current from 2400 to 2150 and then setup PTFE tubing from the filament spool to the monitor so that there is about 6 inches of tubing that directs the filiment straight into the monitor, no binding at monitor entrance. I have had this setup for some months now and rarely have movement issues and when I do there is always a reason, usually a slightly clogged nozzle. My printer is truely a load and go machine thanks to this monitor and the turning I had to do to make it work properly.
-
How do you update the firmware in the sensor? I am getting 'not enough movement' errors but my sensor does not report the 'AGC' value cheers
-
@invertmast said in Spurios "sensor not work" and not enough movement faults:
well so much for those good vibes. 20 minutes into the print and it error'd with "Extruder 0 reports not enough movement"....
@invertmast, are your AGC readings still consistently below 100?
@CTRDevelopments, updating the firmware requires an AVR programmer (e.g. USBASP) and a 2.54mm pitch 2x3 pogo pin adapter such as this https://www.tindie.com/products/nicody/pogo-pins-2x6/ or https://www.sparkfun.com/products/11591.programming-/253682618407 or https://www.ebay.co.uk/itm/POGO-ICSP-AVR-Pogo-Pin-ICSP-ISP-Adapter-Kit/153891594446.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 said in Spurios "sensor not work" and not enough movement faults:
@CTRDevelopments, updating the firmware requires an AVR programmer (e.g. USBASP) and a 2.54mm pitch 2x3 pogo pin adapter such as this https://www.tindie.com/products/nicody/pogo-pins-2x6/ or https://www.sparkfun.com/products/11591.programming-/253682618407 or https://www.ebay.co.uk/itm/POGO-ICSP-AVR-Pogo-Pin-ICSP-ISP-Adapter-Kit/153891594446.
dc42 , thanks. Would this work as the programmer?
https://www.amazon.co.uk/ARCELI-Programmer-ATMEGA8-ATMEGA128-Support/dp/B077WRT87B/ref=sr_1_1?dchild=1&keywords=USBASP&qid=1588138376&s=electronics&sr=1-1 -
@CTRDevelopments probably, but i'd consider either a genuine usbasp or a clone of something that isn't usbasp as the clones can be notoriously troublesome.
also check the links in this post if that is something you can use https://forum.duet3d.com/post/147110
-
@bearer thanks for this, I dont want something that will cause more issue than its worth!
-
I get pauses like this which I am confused about as it looks to me like it is within the limits set?
-
Rather than me mess it up can i send the unit back to get reprogrammed? It is causing me more hassle at the moment as it keeps stopping the print for no reason
-
@CTRDevelopments said in Spurios "sensor not work" and not enough movement faults:
Rather than me mess it up can i send the unit back to get reprogrammed? It is causing me more hassle at the moment as it keeps stopping the print for no reason
I think we can arrange that. Which country are you in?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 UK, happy to post where ever needed. thanks
-
@dc42 If I purchase a new unit will it come with the newest firmware? Thinking it might be cheaper than sending this one back
-
I'm sorry, I missed your reply of 1 May. You are welcome to send it back to me for reprogramming at: Woodpeckers, Wearne, Langport TA10 0QQ. If you send just the PCB, in an antistatic bag and a padded bag, then it should be thin enough go as a large letter which will reduce the postage.
-
DC, OK, will do thanks. It just paused my print reporting -4% movement? IS this any sort of clue as to what the issue could be?
