@dc42
Thank you
Posts made by ArekRucki
-
Saving with M500
Hi All,
I've just made my very first delta autocalibration. Everything went well except saving with M500.
When I look at the directory with system files on DWC after sending M500 there is no config-override.g.
I thought it is created automatically by sending M500.Edit:
The file config-override.g was created after rebooting Duet.
Is this always like this?
Are the new values stored in config-override once I send M500?
Or stored in memory and appear in config-override after reboot?Greetings,
Arek Rucki -
RE: Delta printer calibration procedure
@dc42
I've just bought BL Touch.
There is in Duet3d manual: Adding trigger height corrections to the bed.g file
What is this actually for? I'd guess one need to do those corrections when there are
any points on bed surface that falls out of probe effective trigger height?
For BL Touch it is from 2,3 to 4,3 mm. So when all the bed is in this range I don't need to do it? -
RE: Delta printer calibration procedure
@dc42 OK. Thank you.
But now I've examined one of my build plates by touching it with the nozzle in different points and get values from 14,30 to 15,15. I guess the whole bed is a bit tilted. It gives 0,85 mm difference. I don't know it it is big... So when I go with G32 for the very first time with 6-factor calibration and save the results will it eliminate these differences? Or somwhere in higher parts the nozzle will hit the bed? -
RE: Delta printer calibration procedure
@nikscha Thanks for your time. I was not very clear. I'd have normal print bed e.g. plywood or plaster board. I think both of it have fairly even sufrace. The material I'd print with is clay.
But yes, I need to change the plates every print so they can differ in few milimeters each other.
So I will buy a z probe as @Phaedrux suggests. I still not sure which one. As I wrote few post above it could easily get dirty with clay. For now I'd bet on BL Touch. -
RE: Delta printer calibration procedure
@Phaedrux Thanks a lot. Now that is clear to me. Have a nice day!
-
RE: Delta printer calibration procedure
@Phaedrux Sorry for such simple questions. I read "Calibrating a delta printer" in user manual
1000 times and read lot of forum threads but I am totally new on this field.
So I command G28, then G32, then save? And everytime I run new G32 the "fresh" results will override the saved ones, right? Till I reboot my Duet, right?
And for saving should I use this procedure:?
If you are running firmware 1.17 or later, you can run M500 to save new M665 and M666 commands in the config-override.g file. Then, if you have an M501 command at the end of your config.g file, it will run config-override.g at that point, so that the new commands override the ones earlier in your config.g file.
Many, many thanks... -
RE: Delta printer calibration procedure
@Phaedrux Thanks.
Could you please look at this procedure? As I wrote before I would print clay
and change print bed very often.- turn on the printer
- run autocalibration
- do not home
- start print
- when the print is finished change the build plate
- home the printer
- run autocalibration and start new print?
Do I need to save the autocalibration results evertytime in this case?
Do I need to home in point 6? -
RE: Delta printer calibration procedure
@Phaedrux I read about DC42 IR sensor and BLToutch probes and don't know which to choose. What do you suggest in my case? IR sensor sounds good but I read that it needs 1,5 mm distance
from the nozzle. I think it is a bit to close and can be risky with clay. Can get dirty easily. -
RE: Delta printer calibration procedure
@Phaedrux If I had any Z probe is the @nikscha proposed pocedure still valid?
- turn on the printer
- run autocalibration
- do not home
- start print
- when the print is finished change the build plate
- home the printer
- run autocalibration and start new print?
Do I need to save the autocalibration results evertytime in this case?
Do I need to home in point 6? -
RE: Delta printer calibration procedure
@nikscha Many thanks. Now it looks more clear to me. But you think I could use delta autocalibration and bed leveling in this procedure? Yesterday I've examined one of my build plates by touching it with the nozzle in different points and get values from 14,30 to 15,15. It gives 0,85 mm difference. I don't know it it is big...
Other question is if in my case some z probe (bltouch or DC42 IR sensor for example) would help? -
RE: Delta printer calibration procedure
@Phaedrux Thanks for your time.
config.g
; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.16 on Sat Apr 15 2023 11:44:38 GMT+0200 (czas środkowoeuropejski letni); General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"My Printer" ; set printer name
M665 R115 L230 B85 H270 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them; Network
M552 S1 ; enable network
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 forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 E8 I0 ; configure microstepping without interpolation
M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z80.00 E24000.00 ; set steps per mm
M566 X300.00 Y300.00 Z300.00 E100.00 ; set maximum instantaneous speed changes (mm/min)
M203 X4800.00 Y4800.00 Z4800.00 E1200.00 ; set maximum speeds (mm/min)
M201 X100.00 Y100.00 Z100.00 E5.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E1000 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 Z0 S1 ; set minimum Z; 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 Z2 S1 P"zstop" ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin zstop; Z-Probe
M558 P0 H5 F120 T3000 ; disable Z probe but set dive height, probe speed and travel speed
M557 R85 S20 ; define mesh grid; Heaters
M140 H-1 ; disable heated bed (overrides default heater mapping); Fans
; Tools
M563 P0 D0 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
homedelta.g
; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool v3.3.16 on Sat Apr 15 2023 11:44:38 GMT+0200 (czas środkowoeuropejski letni)
G91 ; relative positioning
G1 H1 X275 Y275 Z275 F1800 ; move all towers to the high end stopping at the endstops (first pass)
G1 H2 X-5 Y-5 Z-5 F1800 ; go down a few mm
G1 H1 X10 Y10 Z10 F360 ; move all towers up once more (second pass)
G1 Z-5 F3000 ; move down a few mm so that the nozzle can be centred
G90 ; absolute positioning
G1 X0 Y0 F3000 ; move X+Y to the centrebed.g
; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool v3.3.16 on Sat Apr 15 2023 11:44:38 GMT+0200 (czas środkowoeuropejski letni)
M561 ; clear any bed transform
; Probe the bed at 3 peripheral and 3 halfway points, and perform 6-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
G30 P0 X0 Y84.9 H0 Z-99999
G30 P1 X73.53 Y-42.45 H0 Z-99999
G30 P2 X-73.53 Y-42.45 H0 Z-99999
G30 P3 X0 Y42.4 H0 Z-99999
G30 P4 X36.72 Y-21.2 H0 Z-99999
G30 P5 X-36.72 Y-21.2 H0 Z-99999
G30 P6 X0 Y0 H0 Z-99999 S6
; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S8-6JKDG-3S86S-1B72M
Used output buffers: 1 of 26 (12 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 73452 of which 344 recycled
Never used RAM 14448, free system stack 184 words
Tasks: NETWORK(ready,10.7%,257) HEAT(notifyWait,0.0%,388) Move(notifyWait,0.0%,363) MAIN(running,83.0%,442) IDLE(ready,6.4%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:14 ago, cause: power up
Last software reset at 2023-04-15 14:12, reason: User, GCodes spinning, available RAM 14376, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 28.0, current 29.5, max 29.9
Supply voltage: min 24.0, current 24.1, max 24.4, 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: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2023-04-16 13:39:07
Cache data hit count 557031466
Slowest loop: 5.97ms; 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: 20.0MBytes/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, 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 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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: 12.46ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.27
WiFi MAC address 48:3f:da:a6:f0:84
WiFi Vcc 3.38, reset reason Power up
WiFi flash size 2097152, free heap 22776
WiFi IP address 192.168.0.179
WiFi signal strength -75dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Tool 0: offsets X0.000 Y0.000 Z0.000 -
RE: Delta printer calibration procedure
@cosmowave ok. I know G92 Z0. It sets z0 position but then when I do homing
the new z0 disappears and I am getting wrong height where nozzle just touches the bed. -
RE: Delta printer calibration procedure
@Phaedrux Now I also don't know if I set this initial height correct because sometimes
when homing some axles don't reach the endstops. Should I increase it? -
RE: Delta printer calibration procedure
@Phaedrux After installing first "raw" firmware with homed height set to 270
I jog down the nozzle to the center of bed and get the value Z=14,9.
What should I do with this value? -
RE: Delta printer calibration procedure
@Phaedrux Thanks. In my case I don't know the basics of setting 3d printer.
Since couple of years I use Prusa printer but never dive into settings
When I don't have any Z probe do I still need to set trigger height?
I've just installed my first firmware from RRF confing tool and don't know what to do next...
I set up printer height in config.g to 270 mm (M665 R115 L230 B85 H270) but don't know if it is correct. -
Delta printer calibration procedure
Hi All,
I just finished building my delta printer for clay printing,
have checked all the motors, endstops, fans. Everything is running correctly.
Now I would like to calibrate the machine.
As I mentioned it is clay printer with no z probe. I'd like to print on plaster plates
and change them every print so I guess they will differ in width.
Now I am at setting z height of the printer and little confused of the process.
I've read all the calibration docs on Duet site (https://docs.duet3d.com/User_manual/Tuning/Delta_calibration) but still don't get it.
Till now I have generated firmware in RRF config tool where set up printer homed height to 290 mm. Homed all and want to measure trigger height. Will it work for me with no z probe?
I lowered the printhead to the center of the printbed. The height was 35,13 mm
so set the M665 command to H254,87 mm (290-35,13=254,87).
Am I doing in correctly? If so I don't know what the next step is.Arek
-
RE: Duet 2 Wifi - largest possible motor
@mrehorstdmd Thank you. I didn't know that. It is my first build. So I think I'll change the belts...
-
RE: Duet 2 Wifi - largest possible motor
@o_lampe
thanks for your suggestion. but what hardware could it be? what expansion connector could I use?
(I am now on 24 V).