Magnetic Filament Monitor Firmware Requirement?
I just implemented a v1.7 (not the A version) magnetic filament monitor into one of my builds, and am going through the calibration section of the instructions.
In the technical section it states "If your sensor does not report mag and agc, you'll need to update the firmware."
My question is what benefits does this offer? The monitor has been happily working for several hours now, and has had around 80 meters of filament running though it so far without any hitches. A couple of 'snip' tests show that pause functionality works fine too.
The M591 output of the current print running is:
Duet3D rotating magnet filament monitor v2 on input 3, enabled, sensitivity 25.37mm/rev, allow 70% to 130%, check every 10.0mm, current pos 341.7, measured sensitivity 25.25mm/rev, min 91% max 109% over 5058.7mm
Which again looks fine to my inexperienced eye. I have the sample length set to 10mm because the monitor is several centimetres above the extruder connected by a length of bowden tube.
I don't have an issue with upgrading to v3 if its a requirement for some reason, but I don't really want to build a custom pogo jig just for this if its not - hence the question.
Just in case the answer is Duet firmware dependant, I'm running:
Board: Duet WiFi 1.02 or later (duetwifi102)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.03 (2019-06-13b2)
Duet WiFi Server Version: 1.23
Duet Web Control 3.1.1
@slimshader upgrading to 2.05.1 would be sufficient if you don't want to move to RRF3.
@dc42 oh! I assumed the firmware was for the filament sensor itself rather than the Duet?
@dc42 thanks! I upgraded the Duet firmware yesterday, will give it a test today.
@dc42 I am still not seeing the AGC or mag features reported by M591even after upgrading the Duet firmware to 2.05.1. is this expected?
What does your M591 D0 report now?
Can you also share the results of M122?
from my latest print:
Board: Duet WiFi 1.02 or later
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.05.1 (2020-02-09b1)
Duet WiFi Server Version: 1.23
Duet3D magnetic filament monitor on input 3, enabled, sensitivity 25.59mm/rev, allow 10% to 150%, check every 10.0mm, version 2, measured sensitivity 25.42mm/rev, min 81% max 118% over 8951.8mm
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L4MSN-6J1FG-3SN6M-9S3GR
Used output buffers: 3 of 24 (9 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93052 of which 36 recycled
Exception stack ram used: 488
Never used ram: 11784
Tasks: NETWORK(ready,676) HEAT(blocked,1232) MAIN(running,348) IDLE(ready,160)
=== Platform ===
Last reset 01:01:55 ago, cause: power up
Last software reset at 2021-05-25 20:17, reason: User, spinning module GCodes, available RAM 11816 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 6.9, current 26.2, max 29.5
Supply voltage: min 23.8, current 24.1, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/224
Driver 1: standstill, SG min/max 0/216
Driver 2: standstill, SG min/max 0/212
Driver 3: standstill, SG min/max 0/1023
Driver 4: standstill, SG min/max not available
Date/time: 2021-05-26 10:50:54
Cache data hit count 4294967295
Slowest loop: 121.46ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 21, FreeDm: 160, MinFreeDm: 80, MaxWait: 134839ms
Bed compensation in use: none, 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.1
Heater 1 is on, I-accum = 0.3
=== 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: 42.14ms; fastest: 0.00ms
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.23
WiFi MAC address 84:0d:8e:b3:b8:6f
WiFi Vcc 3.37, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25536
WiFi IP address 192.168.1.177
WiFi signal strength -62dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0: pos 24.26, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
- WiFi -
@phaedrux I'm not keen currently, but I will have too at some point I guess. My problem is this is a new build and I wanted to get it all stable before doing that - but I suppose I could just as easily do that with RRF3. Problem is I have 5 other RRF2 machines which I'd also need to do to bring them all in line so easier supportability across the farm.
I'll look into it if there's a benefit, but my understanding was that other than greater hardware support and use of Pi's and the like, for general printing there isn't currently many compelling reasons? I might be wrong there as I haven't been following RRF3 for a while. Feel free to persuade me
@slimshader I confirm that RRF 2.05.1 does support the AGC feature. However, the firmware on your filament monitor is reporting it is version 2, and only firmware version 3 reports the AGC.
@dc42 thanks! So that brings me back to the original question of updating the monitors firmware, and I guess the answer would be reporting of those values. Given I've now run around 5kg through it and it seems very stable, detected two run outs and a jam, pausing properly on all occasions, I think I'll call it good for the time being.
Now @Phaedrux has put the idea of RRF3 in my head I'll start planning upgrade of all my machines and get the monitor upgraded to V3 at that point.
Thank you both for the advice!
@slimshader it's possible to upgrade the filament monitor firmware using suitable equipment. See https://duet3d.dozuki.com/Wiki/Duet3dFilamentMonitor_RotatingMagnetVersion#Section_Flashing_the_firmware. If you are in the UK then I can do that for you, otherwise shipping costs and Brexit make it uneconomical. However, it sounds to me that your filament monitor is working well.
@dc42 Thanks David, I can build up a pogo jig and do it myself, but I appreciate the offer all the same.
Now I've proven it working for my use cases I'll be looking to source at least another two monitors - I take it the case availability it still problematic? What about component kits availability?
@slimshader yes case availability is still problematic, but I know we have PCBs and i believe we have the other parts available. Send an email to info at duet3d dot com to enquire.