SFS V2.0 to Duet 3 Mini
-
Is it possible to connect a BTT SFS V2.0 filament monitor (https://biqu.equipment/collections/all-accessories/products/btt-sfs-v2-0-smart-filament-sensor) as a simple switch. According to the manual, it has four wires. Two are for the switch and the other two are for the monitor. I used what I believe are the two switch wires. I wired it to the IO_6 on my Duet 3 Mini 5 (red wire to io6.in and blue wire to GND) and configured it as follows.
M591 D0 P1 C"io6.in" S2Filament runout directions state that a monitor must be connected to the same toolboard that the extruder is on. I am running a Duet 3 Toolboard. I figured since I'm using it as a simple switch that I could still connect it to the MB. Is that not the case?
With my current configuration I get the following error "Error in start-up file macro line 73: Unknown pin name 'io6.in'."
Is what I'm trying to do possible and I'm just doing it wrong or is it just not possible the way I'm trying to do it?
-
@SonnyD1 no, even though it says in the release notes, it doesn't actually work yet
-
@jay_s_uk So I switched over to a simple switch that I use on my other printer so I know it works.
Wired it exactly the same with the only difference is that my other machines are running Duet 2 instead of the Duet 3 Mini 5 that I'm running on this machine. With the following code I get the following error.....what gives?M591 D0 P1 C"io6.in" S2Error in start-up file macro line 73: Unknown pin name 'io6.in'
According to the hardware page for that board, that is the exact pin name.
-
Can you share your full config and the results of M122 and M98 P"config.g" please?
-
@Phaedrux @droftarts @jay_s_uk Thoughts?
; Configuration file for RepRapFirmware on Duet 3 Mini 5+ Ethernet ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.5.0-rc.4+1 on Sun Apr 21 2024 09:30:28 GMT-0400 (Eastern Daylight Time) ; General G90 ; absolute coordinates M83 ; relative extruder moves M550 P"Lulzbot Workhorse" ; set hostname ; Accessories M575 P1 S0 B57600 ; configure PanelDue support ; Network M552 S1 ; enable network M586 P0 S1 ; configure HTTP M586 P1 S1 ; configure FTP M586 P2 S0 ; disable Telnet ; Expansion Board G4 S2 ; Wait a moment for the CAN expansion boards to become available ; Accelerometers M955 P121.0 I24 ; configure accelerometer on board #121 ; Smart Drivers M569 P0.1 S0 D2 ; driver 0.1 goes forwards (Y axis) M569 P0.2 S0 D2 ; driver 0.2 goes forwards (X axis) M569 P0.3 S0 D2 ; driver 0.3 goes forwards (LEFT Z axis) M569 P0.4 S1 D2 ; driver 0.4 goes backwards (RIGHT z axis) M569 P121.0 S0 D2 ; driver 121.0 goes forwards (extruder 0) ; Motor Idle Current Reduction M906 I30 ; set motor current idle factor M84 S30 ; set motor current idle timeout ; Axes M584 X0.2 Y0.1 Z0.3:0.4 ; set axis mapping M671 X-130:380 Y0:0 ; position of leadscrew/bed pivot point at left and right of X axis M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation M906 X1200 Y1200 Z800 ; set axis driver currents M92 X100 Y100 Z400 ; configure steps per mm M208 X-42:309 Y-10:320 Z0:290 ; set minimum and maximum axis limits M566 X600 Y600 Z12 ; set maximum instantaneous speed changes (mm/min) M203 X9000 Y9000 Z180 ; set maximum speeds (mm/min) M201 X500 Y500 Z20 ; set accelerations (mm/s^2) ; Extruders M584 E121.0 ; set extruder mapping M350 E16 I1 ; configure microstepping with interpolation M906 E900 ; set extruder driver currents M92 E393 ; configure steps per mm M566 E120 ; set maximum instantaneous speed changes (mm/min) M203 E3600 ; set maximum speeds (mm/min) M201 E250 ; set accelerations (mm/s^2) ; Kinematics M669 K0 ; configure Cartesian kinematics ; Probes M558 K0 P9 C"121.io0.in" H5 F300 T6000 ; configure BLTouch probe via slot #0 G31 P500 X49.7 Y-19.3 Z3.9 ; set Z probe location, trigger value, offset and trigger height. If you have to move the nozzle closer to the bed, increase the G31 Z value by the amount of baby stepping used. If you have to move the nozzle farther away from the bed, decrease the G31 Z value by the amount of baby stepping used. M950 S0 C"121.io0.out" ; create servo #0 for BLtouch M376 H10 ; taper off bed compensation over 10mm ; Endstops M574 X1 P"io1.in" S1 ; configure X axis endstop M574 Y1 P"io2.in" S1 ; configure Y axis endstop M574 Z1 S2 ; configure Z axis endstop M574 'z2 P"io3.in" S1 ; configure z axis endstop ; Filament Runout M591 D0 P1 C"io6.in" S2 ; configure filament monitor (simple switch) for E0 ; Mesh Bed Compensation M557 X25:275 Y25:275 P5:5 ; define grid for mesh bed compensation ; Temperature Sensors M308 S0 P"temp0" Y"thermistor" A"Heated Bed" T100000 B4725 C7.06e-8 ; configure sensor #0 M308 S1 P"121.temp0" Y"thermistor" A"Nozzle" T100000 B4725 C7.06e-8 ; configure sensor #1 ; Heaters M950 H0 C"out1" T0 ; create bed heater #0 M140 P0 H0 ; configure heated bed #0 M143 H0 P0 T0 C0 S120 A0 ; configure heater monitor #0 for bed heater #0 M307 H0 R0.321 K0.450:0.000 D1.20 E1.35 S1.00 B0 ; configure model of heater #0 M950 H1 C"121.out0" T1 ; create hotend heater #1 M143 H1 P0 T1 C0 S300 A0 ; configure heater monitor #0 for hotend heater #1 M307 H1 R3.832 K0.446:0.329 D2.21 E1.35 S1.00 B0 V24.1 ; configure model of hotend heater #1 ; Fans M950 F0 C"121.out2" ; create fan #0 M106 P0 C"Heatsink Fan" S0 B0.1 H1 T45 ; configure fan #0 M950 F1 C"121.out1" Q250 ; create fan #1 M106 P1 C"Part Cooling Fan" S0 B0.1 L35 X250 ; configure fan #1 ; Tools M563 P0 S"Tool 0" D0 H1 F1 ; create tool #0 M568 P0 R0 S0 ; set initial tool #0 active and standby temperatures to 0C ; MiscellaneousM122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.1 (2024-04-19 14:41:25) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: K4V3J-AP6KL-K65J0-409NG-2012Z-7P0WG Used output buffers: 3 of 40 (24 max) Error in macro line 73 while starting up: Unknown pin name 'io6.in' === RTOS === Static ram: 103232 Dynamic ram: 121108 of which 12 recycled Never used RAM 14208, free system stack 194 words Tasks: NETWORK(2,nWait 7,13.4%,216) HEAT(3,nWait 6,0.0%,351) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.0%,797) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,0.8%,102) MAIN(1,running,84.5%,665) IDLE(0,ready,0.4%,30) AIN(4,delaying,0.9%,264), total 100.0% Owned mutexes: === Platform === Last reset 00:01:24 ago, cause: power up Last software reset at 2024-06-10 13:57, reason: User, Gcodes spinning, available RAM 14208, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00487000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 84521, completed 84521, timed out 0, errs 0 MCU temperature: min 23.2, current 28.9, max 29.1 Supply voltage: min 23.7, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/36/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 4413, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 4409, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 4409, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 4409, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 4410, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-06-10 15:55:08 Cache data hit count 161391614 Slowest loop: 12.02ms; fastest: 0.15ms === Storage === Free file entries: 20 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 4.2ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Movement locks held by null, 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 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000000 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 770, received 1679, lost 0, errs 0, boc 0 Longest wait 1ms for reply type 6034, peak Tx sync delay 6, free buffers 26 (min 25), ts 422/421/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 14.32ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.1.0 MAC address e8:68:e7:e1:50:dd Module reset reason: Power up, Vcc 3.39, flash size 2097152, free heap 39692 WiFi IP address 192.168.1.133 Signal strength -50dBm, channel 8, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0M98 Results
Endstop configuration: X: low end switch connected to pin io1.in Y: low end switch connected to pin io2.in Z: low end Z probeError: Unknown pin name 'io6.in' Warning: Heater 1 predicted maximum temperature at full power is 516°C -
@SonnyD1 said in SFS V2.0 to Duet 3 Mini:
M574 'z2 P"io3.in" S1I wonder if the apostraphe in this line is causing an issue. The runout command is on the following line.
-
@SonnyD1 I believe it's been fixed in the source and will be working in 3.5.2
Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@Phaedrux I removed the apostrophe and I still get the same error. This is really weird. I have the same line (M591 D0 P1 C"" S1) on my another printer with the same filament runout switch and I don't have this issue. Only difference is the other one is a Duet 2 running 3.4.
Creativity 3D Printer Filament Detection Sensor Module Filament Run-Out Pause Detecting Monitor for 3D Printer Lerdge Board 1.75mm Filament (Black) https://a.co/d/dzyfMmf -
@jay_s_uk I've since switched to another Filament Runout sensor. Now I'm using :
Creativity 3D Printer Filament Detection Sensor Module Filament Run-Out Pause Detecting Monitor for 3D Printer Lerdge Board 1.75mm Filament (Black) https://a.co/d/dzyfMmf -
Guys I really need to get this resolved. I know it's kind of a weird issue. Right now,I have a printer that's unusable. I've done everything that I know how to do.
-
Have you tried 3.5.2 that was just released?
-
@Phaedrux Ok I just updated to 3.5.2. It eliminated the error but the switch still isn't working. I need to verify the wiring and I'll get back with you. Thank you for your help thus far. Almost there...
-
@Phaedrux I verified the wiring. It matches another machine that works perfectly. I'm at a loss yet again. Clearly I'm not as smart as I think I am. I verified that its not a bad switch by swapping it out with another. I verified the wiring matches a known functional setup and I swapped the signal and the volt wire to be sure. I'm out of ideas. If its a config issue, I can't imagine what it is. Thoughts? Do I have to run a simple switch off the same toolboard that the extruder is on?
-
@SonnyD1 With version 3.5.2, it works perfectly. I mean my filament sensors on the Duet3 Mini and use two tool boards. Before version 3.5.2, I also got an error message unknown pin name.
Love my Duet 3 Mini.
https://www.instagram.com/proschi3d
https://youtube.com/@proschi3d
https://www.proschi3d.de -
@Proschi78 3.5.2 fixed that error on mine as well. Now the sensor still wont work and I can't seem to get any help. I'll keep trying to fix it though. TY for the reply.
-
Can you show us exactly what switch it is, and how it's wired?
@SonnyD1 said in SFS V2.0 to Duet 3 Mini:
It matches another machine that works perfectly.
And you've said you've swapped in another board and it's not working either? That would seem to indicate wiring or a crimp maybe.
-
@Phaedrux Yea you nailed it. I went and ran another jumper wire and it worked. So I ran all new wiring. Musta been a bad crimp like you said. The LED on the switch lights up and I get a filament error when I remove filament just like it should. I know I'm a pain and this was a headache but I really appreciate you hangin in there with me. Sometimes the most obvious solution eludes me. TYVM!!!
-
@Phaedrux The filament runout error doesn't pop up on my paneldue like it does on my other printers. Only pops up on the DWC....any idea why?
-
