@OwenD Thank you Owen. I figured it out. I cut open the RJ11 cable, crimped the 2 middle wires (of 4) into a molex connector, and made sure I was matching L to L and H to H.
Best posts made by tylersuard
-
RE: How do I install the 1HCL on the Duet3 Mini 5+?
-
RE: Web UI not accessible if I leave printer on Pause for too long
I was able to solve the problem by connecting to my board via USB and turning the board's wifi off with M552 S-1 and then on again with M552 S1
-
RE: Retraction settings changed mid-print?
The answer: I had created a retraction tower earlier. The "alter Gcode" plugin was still active even though it was not visible, and was increasing my retraction distance every 20 layers.
-
RE: Monitoring of extruder head using laser distance sensors
@OwenD I'm not sure what you mean by this, my layer shifts are horizontal, not vertical.
Latest posts made by tylersuard
-
RE: SOLUTION: Can't connect to Duet Web Control
@gloomyandy === Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.4 (2023-06-08 23:40:14) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 54FNS-WR6KL-K65J0-409N0-5Q02Z-RQFPY
Used output buffers: 1 of 40 (18 max)
=== RTOS ===
Static ram: 102996
Dynamic ram: 125200 of which 20 recycled
Never used RAM 13840, free system stack 150 words
Tasks: NETWORK(1,ready,11.0%,219) HEAT(3,nWait,0.0%,331) Move(4,nWait,0.0%,358) CanReceiv(6,nWait,0.0%,798) CanSender(5,nWait,0.0%,337) CanClock(7,delaying,0.0%,351) TMC(4,nWait,1.2%,108) MAIN(1,running,86.7%,704) IDLE(0,ready,0.2%,29) AIN(4,delaying,0.8%,266), total 100.0%
Owned mutexes: WiFi(NETWORK) USB(MAIN)
=== Platform ===
Last reset 00:04:50 ago, cause: power up
Last software reset at 2024-02-16 10:34, reason: User, Gcodes spinning, available RAM 12640, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00433000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 290481, completed 290480, timed out 0, errs 0
MCU temperature: min 18.8, current 29.0, max 29.2
Supply voltage: min 24.0, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 5 queued, 5 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 26352, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 26352, 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 26352, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 26354, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 26355, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 26352, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 26352, writes 13, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2024-02-16 14:26:01
Cache data hit count 531164937
Slowest loop: 8.30ms; fastest: 0.17ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.7ms, 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, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
=== 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
Heater 1 is on, I-accum = 0.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 ready with "M122" 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 0x0000803
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages queued 2840, received 5014, lost 0, boc 0
Longest wait 55ms for reply type 6041, peak Tx sync delay 21902, free buffers 18 (min 17), ts 1452/1451/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 15.37ms; 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, notready 0, noresp 0
Firmware version 1.26
MAC address e8:68:e7:e1:4d:67
Module reset reason: Power up, Vcc 3.36, flash size 2097152, free heap 21256
WiFi IP address 10.0.0.115
Signal strength -52dBm, channel 0, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok -
RE: SOLUTION: Can't connect to Duet Web Control
@Phaedrux === Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.4 (2023-06-08 23:40:14) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 54FNS-WR6KL-K65J0-409N0-5Q02Z-RQFPY
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 102996
Dynamic ram: 125200 of which 20 recycled
Never used RAM 13840, free system stack 143 words
Tasks: NETWORK(1,ready,8.4%,329) HEAT(3,suspended,0.0%,327) TMC(4,nWait,1.2%,114) MAIN(1,running,89.3%,704) IDLE(0,ready,0.3%,29) AIN(4,delaying,0.8%,266), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:03:33 ago, cause: power up
Last software reset at 2024-02-02 20:03, reason: User, Gcodes spinning, available RAM 13840, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00489000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 213501, completed 213500, timed out 0, errs 0
MCU temperature: min 19.4, current 27.5, max 27.5
Supply voltage: min 24.1, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 7 queued, 7 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 19342, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 19341, writes 13, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x41
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 19342, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 19345, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 19345, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 19342, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 19342, writes 13, timeouts 0, DMA errors 0, CC errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 395592143
Slowest loop: 99.91ms; fastest: 0.17ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.3ms, 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, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
=== 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 ready with "M122" 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
=== Filament sensors ===
Extruder 0 sensor: no filament
=== CAN ===
Disabled
Longest wait 56ms for reply type 6041, peak Tx sync delay 21228, free buffers 18 (min 17), ts 1005/1004/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 14.99ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Interface state: disabled
Module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok -
RE: SOLUTION: Can't connect to Duet Web Control
@Phaedrux Thank you for your reply. How would I find that out?
-
Can't connect to Duet board: Network scan failed
Can't connect to DWC. When I first bought my Duet, everything worked fine. After a few months, I noticed that I had to connect to the board with a USB cable and turn the network connection off and on again (M552 S-1 and then M552 S1) a few times before it would connect to my internet, but I figured that was just an annoyance I can put up with. Now, today, my trick of turning the network connection off and on again is not working, and I am getting this:
WiFi module is idle
Error: WiFi module reported: network scan failed
WiFi module is idle
Error: WiFi module reported: network scan failed
WiFi module is idleRepeated thousands of times, and then:
WiFi module is connected to access point , IP address 255.255.255.255Which of course does not work.
-
SOLUTION: Can't connect to Duet Web Control
I will sometimes leave my printer on pause for up to 24 hours, and when I get back, I can't connect to the Duet Web Control anymore. Here is my solution:
- Connect your computer to the Duet board via USB cable. I have a long USB cable right next to my computer always plugged into the Duet because this happens so often.
- Open YAT and connect. If you can't connect, try rebooting your computer.
- Send command M552 S-1. This will turn off the wifi chip.
- Wait around 10 to 30 seconds
- Send command M552 S1. This will turn the wifi chip back on and hopefully connect. You might get a ton of errors, but just wait, and it might give you the IP address at the end. If the IP address is 255.255.255.255, repeat steps 3-5.
- You should be able to connect to the Duet Web Control!
-
RE: Filament sensor problems after firmware upgrade to 3.5.0-beta.4
@Phaedrux thank you for replying. I am using io6, on the mini 5+. full config:
; General preferences
G4 S1 ;wait for expansion boards to start
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"V-Core 3" ; set printer name
M669 K1 ; CoreXY
G21 ; Set Units to Millimeters; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet;Closed-loop steppers setup
M584 X50.0
M569.1 P50.0 T3 S200 ; Configure the Duet 3 Expansion 1HCL board at CAN address 50 with a Duet 3 magnetic encoder, warn if 1 fullstep threshold exceeded, error if 2 full steps threshold exceeded.
M906 X2500; set motor current
M569 P50.0 D2; set open loop mode
M17 X
M203 X10800.0
G4 P300
M569 P50.0 D4
G4 P300
M569.6 P50.0 V2M584 Y51.0
M569.1 P51.0 T3 S200
M906 Y2500
M569 P51.0 D2
M17 Y
M203 Y10800.00
M201 Y3000.00
G4 P300
M569 P51.0 D4
G4 P300
M569.6 P51.0 V2M917 X0 Y0 ; Set the closed loop axes to have a holding current of zero
M350 X32 Y32 ; set steps/mm to 32 to make full use of the encoder resolution
M92 X160 Y160 ; steps/mm for a 20 tooth gt2 pulley; Drives
M569 P0.0 S1 D3 ; physical drive 0.0 goes forwards
M569 P0.1 S1 D3 ; physical drive 0.1 goes forwards
M569 P0.2 S1 D3 ; physical drive 0.2 goes forwards
;M569 P0.3 S1 D3 ; physical drive 0.3 goes forwards
;M569 P0.4 S1 D3 ; physical drive 0.4 goes forwards
M569 P0.5 S1 D3 ; physical drive 0.5 goes forwards
M569 P0.6 S1 D3
M584 X50.0 Y51.0 Z0.0:0.1:0.2 E0.5:0.6 ; set drive mapping
M350 Z16 E16:16 I1 ; configure microstepping with interpolation;M92 X80.00 Y80.00 Z800.00 ; set steps per mm
M92 Z800.0
M906 Z800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeoutM566 X400.00 Y400.00 Z6.00 E300.00:300.00 P1 ; set maximum instantaneous speed changes (mm/min)
M203 X10800.00 Y10800.00 Z1000.00 E7200.00:7200.00 ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z100.00 E10000.00:10000.00 ; set accelerations (mm/s^2); Axis Limits
M208 X0 Y0 Z-10 S1 ; set axis minima
M208 X500 Y500 Z500 S0 ; set axis maxima; Endstops
M574 X1 S1 P"io0.in" ; configure active high endstops
M574 Y2 S1 P"io1.in" ; configure active high endstops; Filament Runout Sensor
M591 D0 P1 C"io6.in" S1 ; simple sensor (high signal when filament present) connected to IO_6 for drive 0, enabled
;M591 D0 ; display filament sensor parameters for extruder drive 0M671 X-4.5:250:505 Y-4.52:505:-4.52 S10 ; define positions of Z leadscrews or bed levelling screws
M557 X50:450 Y50:450 P5 ; define 5x5 mesh grid; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Bed" ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out5 and map it to sensor 0
M307 H0 B0 S.50 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S85 ; set temperature limit for heater 0 to 110C;; Run Bed PID Tune!! Below is an example for a 300x300 bed
;M307 H0 A303.1 C356.7 D1.4 S1.00 V24.0 B0
M307 H0 R0.467 K0.281:0.000 D7.29 E1.35 S1.00 B0; Fans
M950 F0 C"out4" Q450 ; create fan 0 on pin out4 and set its frequency
M106 P0 C"Flexion Fan" S255 H-1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"out3" Q500 ; create fan 1 on pin out3 and set its frequency
M106 P1 C"Revo Micro Fan" S255 H-1 ; set fan 1 name and value. Thermostatic control turned on for Hotend; Tools
M563 P0 S"Flexion Extruder" D0 H1 ; define tool 0
G10 P0 X10 Y-26 Z0 ; set tool 0 axis offsets
G10 P0 R215 S0 ; set initial tool 0 active and standby temperatures to 0CM563 P1 S"Revo Micro Extruder" D1 H2 ;define tool 1
G10 P1 X-18.5 Y-56.5 Z0
;last: G10 P1 X-17 Y-56.5 Z0
G10 P1 R220 S0M950 H1 C"out1" T1 ; create nozzle heater output on out2 and map it to sensor 1
M307 H1 B0 S.60 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S230 ; set the maximum temperature in C for heaterM950 H2 C"out2" T2
M307 H2 B0 S.80
M143 H2 S290; EVA 2 / BMG / E3D V6
;M92 E690 ; set extruder steps per mm, 0.9 angle/step (LDO Pancake)
;M92 E304
M92 E244.17671:680
M906 E1361:800 ; set extruder motor current (mA) and idle factor in per cent
;Max: E1512
;Original: E800M308 S1 P"temp1" Y"thermistor" T100000 B3950 A"Flexion Heater"
;For mosquito:
M308 S2 P"temp2" Y"thermistor" T100000 B4725 C7.060000e-8 A"Revo Micro Heater"
;; Run Heater PID Tune!!
;; M307 H1 A751.5 C196.6 D4.7 S1.00 V23.9 B0
;Mosquito
;M307 H1 R3.108 K0.765:0.123 D6.44 E1.35 S1.00 B0
;M307 H1 R4.707 K1.275:0.000 D8.01 E1.35 S0.50 B0 V23.9
;Normal, extruder fan duct but no bed fan:
;M307 H1 R4.521 K0.457:0.000 D8.91 E1.35 S0.50 B0
;With bed fan:
;M307 H1 R3.793 K0.978:0.000 D9.61 E1.35 S0.60 B0
;Flexion PID params
;M307 H1 R3.308 K0.457:0.000 D11.78 E1.35 S0.50 B0
;Flexion PID params, FAN ON
M307 H1 R3.625 K0.519:0.000 D11.25 E1.35 S0.60 B0
;Revo Micro PID params
;M307 H2 R4.988 K1.051:0.000 D1.53 E1.35 S0.80 B0 V24.1
;M307 H2 R5.029 K0.514:0.000 D1.84 E1.35 S0.80 B0
;Revo Micro PID Params, FAN ON
M307 H2 R5.056 K0.775:0.000 D1.73 E1.35 S0.80 B0;Z-Probe
;; Inductive Probe
; M558 P5 C"!io3.in" H5 F400 T5000 ; set Z probe type to unmodulated and the dive height + speeds
; G31 P500 X-30 Y-15 Z0.20 ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed
; BLTouch
M950 S0 C"io2.out" ; Create a servo pin on io2
M558 P9 C"io2.in" H5 F240 T10800 A5 ; set Z probe type to unmodulated and the dive height + speeds
;M558 C"zprobe.in" P8 R0.4 F1200 H10 T6000
G31 P25 X10.00 Y-30.00 Z1.2 ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed; Select default tool
T0; Pressure Advance
; M572 D0 S0.10 -
After tuning, closed-loop motors do a sharp jerk and error
Every time I turn my printer on, my Duet3d closed-loop system (2x 1HCL and 2x Duet magnetic encoders) goes through a calibration process. At the end, it does this quick jerk and then tells me that the encoder had an error(Driver 50.0 and 51.0 error: failed to maintain position). What is happening here, and how should I fix it? Video attached, below is my config. kathunk smallest.mp4
; General preferences
G4 S1 ;wait for expansion boards to start
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"V-Core 3" ; set printer name
M669 K1 ; CoreXY
G21 ; Set Units to Millimeters; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet;Closed-loop steppers setup
M584 X50.0
M569.1 P50.0 T3 S200 ; Configure the Duet 3 Expansion 1HCL board at CAN address 50 with a Duet 3 magnetic encoder, warn if 1 fullstep threshold exceeded, error if 2 full steps threshold exceeded.
M906 X2500; set motor current
M569 P50.0 D2; set open loop mode
M17 X
M203 X10800.0
G4 P300
M569 P50.0 D4
G4 P300
M569.6 P50.0 V2M584 Y51.0
M569.1 P51.0 T3 S200
M906 Y2500
M569 P51.0 D2
M17 Y
M203 Y10800.00
M201 Y3000.00
G4 P300
M569 P51.0 D4
G4 P300
M569.6 P51.0 V2M917 X0 Y0 ; Set the closed loop axes to have a holding current of zero
M350 X32 Y32 ; set steps/mm to 32 to make full use of the encoder resolution
M92 X160 Y160 ; steps/mm for a 20 tooth gt2 pulley; Drives
M569 P0.0 S1 D3 ; physical drive 0.0 goes forwards
M569 P0.1 S1 D3 ; physical drive 0.1 goes forwards
M569 P0.2 S1 D3 ; physical drive 0.2 goes forwards
;M569 P0.3 S1 D3 ; physical drive 0.3 goes forwards
;M569 P0.4 S1 D3 ; physical drive 0.4 goes forwards
M569 P0.5 S1 D3 ; physical drive 0.5 goes forwards
M569 P0.6 S1 D3
M584 X50.0 Y51.0 Z0.0:0.1:0.2 E0.5:0.6 ; set drive mapping
M350 Z16 E16:16 I1 ; configure microstepping with interpolation;M92 X80.00 Y80.00 Z800.00 ; set steps per mm
M92 Z800.0
M906 Z800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeoutM566 X400.00 Y400.00 Z6.00 E300.00:300.00 P1 ; set maximum instantaneous speed changes (mm/min)
M203 X10800.00 Y10800.00 Z1000.00 E7200.00:7200.00 ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z100.00 E10000.00:10000.00 ; set accelerations (mm/s^2); Axis Limits
M208 X0 Y0 Z-10 S1 ; set axis minima
M208 X500 Y500 Z500 S0 ; set axis maxima; Endstops
M574 X1 S1 P"io0.in" ; configure active high endstops
M574 Y2 S1 P"io1.in" ; configure active high endstops; Filament Runout Sensor
M591 D0 P1 C"io6.in" S1 ; simple sensor (high signal when filament present) connected to IO_6 for drive 0, enabled
;M591 D0 ; display filament sensor parameters for extruder drive 0M671 X-4.5:250:505 Y-4.52:505:-4.52 S10 ; define positions of Z leadscrews or bed levelling screws
M557 X50:450 Y50:450 P5 ; define 5x5 mesh grid; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Bed" ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out5 and map it to sensor 0
M307 H0 B0 S.50 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S85 ; set temperature limit for heater 0 to 110C;; Run Bed PID Tune!! Below is an example for a 300x300 bed
;M307 H0 A303.1 C356.7 D1.4 S1.00 V24.0 B0
M307 H0 R0.467 K0.281:0.000 D7.29 E1.35 S1.00 B0; Fans
M950 F0 C"out4" Q450 ; create fan 0 on pin out4 and set its frequency
M106 P0 C"Flexion Fan" S255 H-1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"out3" Q500 ; create fan 1 on pin out3 and set its frequency
M106 P1 C"Revo Micro Fan" S255 H-1 ; set fan 1 name and value. Thermostatic control turned on for Hotend; Tools
M563 P0 S"Flexion Extruder" D0 H1 ; define tool 0
G10 P0 X10 Y-26 Z0 ; set tool 0 axis offsets
G10 P0 R215 S0 ; set initial tool 0 active and standby temperatures to 0CM563 P1 S"Revo Micro Extruder" D1 H2 ;define tool 1
G10 P1 X-18.5 Y-56.5 Z0
;last: G10 P1 X-17 Y-56.5 Z0
G10 P1 R220 S0M950 H1 C"out1" T1 ; create nozzle heater output on out2 and map it to sensor 1
M307 H1 B0 S.60 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S230 ; set the maximum temperature in C for heaterM950 H2 C"out2" T2
M307 H2 B0 S.80
M143 H2 S290; EVA 2 / BMG / E3D V6
;M92 E690 ; set extruder steps per mm, 0.9 angle/step (LDO Pancake)
;M92 E304
M92 E244.17671:680
M906 E1361:800 ; set extruder motor current (mA) and idle factor in per cent
;Max: E1512
;Original: E800M308 S1 P"temp1" Y"thermistor" T100000 B3950 A"Flexion Heater"
;For mosquito:
M308 S2 P"temp2" Y"thermistor" T100000 B4725 C7.060000e-8 A"Revo Micro Heater"
;; Run Heater PID Tune!!
;; M307 H1 A751.5 C196.6 D4.7 S1.00 V23.9 B0
;Mosquito
;M307 H1 R3.108 K0.765:0.123 D6.44 E1.35 S1.00 B0
;M307 H1 R4.707 K1.275:0.000 D8.01 E1.35 S0.50 B0 V23.9
;Normal, extruder fan duct but no bed fan:
;M307 H1 R4.521 K0.457:0.000 D8.91 E1.35 S0.50 B0
;With bed fan:
;M307 H1 R3.793 K0.978:0.000 D9.61 E1.35 S0.60 B0
;Flexion PID params
;M307 H1 R3.308 K0.457:0.000 D11.78 E1.35 S0.50 B0
;Flexion PID params, FAN ON
M307 H1 R3.625 K0.519:0.000 D11.25 E1.35 S0.60 B0
;Revo Micro PID params
;M307 H2 R4.988 K1.051:0.000 D1.53 E1.35 S0.80 B0 V24.1
;M307 H2 R5.029 K0.514:0.000 D1.84 E1.35 S0.80 B0
;Revo Micro PID Params, FAN ON
M307 H2 R5.056 K0.775:0.000 D1.73 E1.35 S0.80 B0;Z-Probe
;; Inductive Probe
; M558 P5 C"!io3.in" H5 F400 T5000 ; set Z probe type to unmodulated and the dive height + speeds
; G31 P500 X-30 Y-15 Z0.20 ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed
; BLTouch
M950 S0 C"io2.out" ; Create a servo pin on io2
M558 P9 C"io2.in" H5 F240 T10800 A5 ; set Z probe type to unmodulated and the dive height + speeds
;M558 C"zprobe.in" P8 R0.4 F1200 H10 T6000
G31 P25 X10.00 Y-30.00 Z1.2 ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed; Select default tool
T0; Pressure Advance
; M572 D0 S0.10 -
RE: Filament sensor problems after firmware upgrade to 3.5.0-beta.4
@dc42 I created a filament-error.g file and added
M25
M79 P200 Filament runout!The board still does nothing when I insert or remove filament in the sensor.
-
RE: Filament sensor problems after firmware upgrade to 3.5.0-beta.4
@dc42 I created a new filament-error.g file, and this is its contents:
M25
M79 P200 Filament runout!Is that ok?
-
RE: Filament sensor problems after firmware upgrade to 3.5.0-beta.4
@dc42 I do not have a filament-error.g file. When that file does not exist, it should just default to pause, is that correct?