Posts made by rooracleaf

undefined

@droftarts
Actually, after doing this and making the bed size smaller in cura its working better, there's still a 3mm difference in the edges of the bed but oh well. Thanks for all your help it is greatly appreciated.

IMG20230123132925 (2).jpg

undefined

@droftarts
Hello again, sorry I've been away a while.

I just tried this and it seems to have allowed the bed to move forward a slight bit more but the nozzel still moves over the front of the bed sadly.
Is this normal, it moves over the edge when im controlling it through the web control but will it behave normally when printing?

undefined

@droftarts

Hi again,

This method works for the X-Axis but not matter what I change on the Y-axis nothing happens.
The distance between the nozzel and the edge of the bed does not change, do you have any more ideas?

undefined

@droftarts
My Home point after a G28 is X54 Y26 which is towards the back center of the bed. My X0 Y0 is towards the back right corner of the bed. Should I change the X axis endstop to the low end?

Homeall.g:

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.15 on Tue Jan 03 2023 18:37:28 GMT+1000 (Australian Eastern Standard Time)
G91                   ; relative positioning
G1 H2 Z5 F6000        ; lift Z relative to current position
G1 H1 X240 Y240 F3000 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X-5 Y-5 F6000   ; go back a few mm
G1 H1 X240 Y240 F240  ; move slowly to X and Y axis endstops once more (second pass)
G90                   ; absolute positioning
G1 X54 Y26 F6000      ; go to first bed probe point and home Z
G30                   ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91                  ; relative positioning
;G1 Z5 F100           ; lift Z relative to current position
;G90                  ; absolute positioning

undefined

@droftarts
I'm pretty sure the build volume I have there now is incorrect but it was the only way I could get the X axis to stay on the bed.

Here's the Config.g

; Configuration file for Duet Maestro (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.15 on Tue Jan 03 2023 18:37:27 GMT+1000 (Australian Eastern Standard Time)

; General preferences
G90                                                    ; send absolute coordinates...
M83                                                    ; ...but relative extruder moves
M550 P"MDAero Ender 3"                                 ; set printer name

; Network
M552 P0.0.0.0 S1                                       ; enable network and acquire dynamic address via DHCP
M586 P0 S1                                             ; enable HTTP
M586 P1 S0                                             ; disable FTP
M586 P2 S0                                             ; disable Telnet

; Drives
M569 P0 S0                                             ; physical drive 0 goes backwards
M569 P1 S0                                             ; physical drive 1 goes backwards
M569 P2 S0                                             ; physical drive 2 goes backwards
M569 P3 S1                                             ; physical drive 3 goes backwards

M584 X0 Y1 Z2 E3                                       ; set drive mapping
M350 E128 I0                                           ; configure microstepping without interpolation
M350 X16 Y16 Z16 I1                                    ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E741.00                      ; set steps per mm
M566 X600.00 Y600.00 Z60.00 E300.00                    ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z600.00 E6000.00                ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z120.00 E5000.00                  ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E900 I30                           ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                                ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                                       ; set axis minima
M208 X230 Y230 Z250 S0                                 ; set axis maxima

; Endstops
M574 X2 S1 P"xstop"                                    ; configure switch-type (e.g. microswitch) endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop"                                    ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop
M574 Z1 S2                                             ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"zprobe.mod"                                  ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F900 T6000                    ; set Z probe type to bltouch and the dive height + speeds
M558 H30                                               ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X40.5 Y10 Z2.24                               ; set Z probe trigger value, offset and trigger height  X37.5 Y10 Z2.24 
M557 X10:235 Y10:235 S20                               ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T98801 B4185          ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                                  ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.00                                       ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0                                                ; map heated bed to heater 0
M143 H0 S80                                            ; set temperature limit for heater 0 to 80C
M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                                   ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00                                       ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S285                                           ; set temperature limit for heater 1 to 285C

; Fans
M950 F0 C"fan0" Q500                                   ; create fan 0 on pin fan0 and set its frequency
M106 P0 C"PCF" S0 H-1                                  ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"fan1" Q500                                   ; create fan 1 on pin fan1 and set its frequency
M106 P1 C"HEF" S1 H1 T45                               ; set fan 1 name and value. Thermostatic control is turned on
M950 F2 C"fan2" Q500                                   ; create fan 2 on pin fan2 and set its frequency
M106 P2 C"ECF" S1 H1:0 T45                             ; set fan 2 name and value. Thermostatic control is turned on


; Tools
M563 P0 S"Hotend" D0 H1 F0                     ; define tool 0
G10 P0 X0 Y0 Z0                                    ; set tool 0 axis offsets
G10 P0 R0 S0                                       ; set initial tool 0 active and standby temperatures to 0C


; Custom settings are not defined

; Miscellaneous
M501                                                   ; load saved parameters from non-volatile memory
M911 S21 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"     ; set voltage thresholds and actions to run on power loss

T0

Here's the M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 3.4.5 (2022-11-30 19:42:44) running on Duet Maestro 1.0
Board ID: 08DJM-9X66L-LG3SJ-6J9F0-3SJ6L-TAXAR
Used output buffers: 1 of 26 (24 max)
=== RTOS ===
Static ram: 23620
Dynamic ram: 67136 of which 204 recycled
Never used RAM 20240, free system stack 158 words
Tasks: NETWORK(ready,32.9%,254) HEAT(notifyWait,0.1%,350) Move(notifyWait,0.0%,318) TMC(notifyWait,1.3%,117) MAIN(running,65.7%,428) IDLE(ready,0.0%,31), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:45:58 ago, cause: power up
Last software reset at 2023-01-10 16:49, reason: User, GCodes spinning, available RAM 23732, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 872
MCU temperature: min 45.7, current 45.9, max 46.1
Supply voltage: min 24.3, current 24.4, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/46/46, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, read errors 0, write errors 0, ifcnt 14, reads 374, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, read errors 0, write errors 0, ifcnt 14, reads 374, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, read errors 0, write errors 0, ifcnt 11, reads 374, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, read errors 0, write errors 0, ifcnt 9, reads 374, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, read errors 0, write errors 0, ifcnt 6, reads 373, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2023-01-10 20:06:28
Slowest loop: 0.75ms; fastest: 0.17ms
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: 15.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 18, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 4408, completed 4408, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1, chamber heaters -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.4
=== 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: 5.69ms; fastest: 0.06ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex

undefined

I've got an issue where 0 one the Y axis is around 2cm to far forward on the bed making the nozzel fly off the end of the bed when the Y axis hits its upper limit. I've tried changing the bed size and Z-probe offset but it stays at that constant distance. The X axis also has a similar issue but can be solved if I make the bed size smaller.

undefined

@dc42

Yes my extruder is running backwards but I don't know how to fix that without using a specific filament config.

When I z home the bltouch probes at the X centre of the bed at the back of the bed. During mesh probing the bltouch starts at the same X centre and continues off the edge of the bed. I'm pretty sure I have the correct volume in, the issue may be the offset because I just copied the previous owner's offset but It would be helpful if you could confirm whether that is the issue or not.

Thanks.

undefined

@Phaedrux

Hey I've got new questions now if you could answer that would be great.

Do I have to make fillament configurations?

Why does my filment move out when I press load and in when I press unload?

Why does my bl touch start at the centre of the bed and not as close to 0,0 as possible?

undefined

@OwenD

Thank you

undefined

@Phaedrux
Thank you so much, now the hotend shows up all good, I have no idea how I would've figured that out alone.

I now have an error when I press the "Load Filament" button I get the error "Failed to load filaments Directory 0:/filaments/ not found" I didn't realise that this would also be an issue, do you know how to fix this aswell?

I just noticed the other part of your message, here's the M122 result:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 3.4.5 (2022-11-30 19:42:44) running on Duet Maestro 1.0
Board ID: 08DJM-9X66L-LG3SJ-6J9F0-3SJ6L-TAXAR
Used output buffers: 1 of 26 (17 max)
=== RTOS ===
Static ram: 23620
Dynamic ram: 67136 of which 0 recycled
Never used RAM 23732, free system stack 205 words
Tasks: NETWORK(ready,28.4%,270) HEAT(notifyWait,0.1%,350) Move(notifyWait,0.0%,404) TMC(notifyWait,0.0%,123) MAIN(running,71.3%,492) IDLE(ready,0.2%,31), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:01:16 ago, cause: software
Last software reset at 2023-01-05 15:53, reason: User, GCodes spinning, available RAM 23864, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 939
MCU temperature: min 40.1, current 40.4, max 40.8
Supply voltage: min 0.2, current 0.2, max 0.2, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: ok, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: ok, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: ok, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 6: ok, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2023-01-05 15:54:16
Slowest loop: 6.12ms; fastest: 0.17ms
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: 15.0MBytes/sec
SD card longest read time 0.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1, chamber heaters -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== 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: 111.29ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex

undefined

@dc42

I've probably done something dumb but here it is.

undefined

@chrishamm
Here's my details

RepRapFirmware for Duet 2 Maestro 3.4.5

I may have gone from v2 to V3 but I started this setup months ago and have forgotten what I did back then and I'm not 100% sure how to check.

Here's what I got after running M98:

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Heater 0 predicted maximum temperature at full power is 177°C
Error: Heater 2 not found

undefined

I bought a second hand ender 3 with a duet maestro, E3D v6 hotend and a Bl-touch. The bed heater is showing up just fine but thats the only tool in the online controller. My bed is set to Heater 0 and nozzel is set to heater 1. I'm pretty new to this and I understand that these kind of things aren't very friendly for new comers so it would just be really nice to get some help.

Or maybe someone can just send me a complete configuration file if they've got the same setup.