@phaedrux That appears to have fixed it. I feel really dumb after changing just about everything but that setting. Thanks again for the help and hopefully I'm done bugging you smart guys with dumb guy questions!
Best posts made by dmnvk
-
RE: Delta calibration not touching bed at edges
Latest posts made by dmnvk
-
RE: Delta calibration not touching bed at edges
@phaedrux That appears to have fixed it. I feel really dumb after changing just about everything but that setting. Thanks again for the help and hopefully I'm done bugging you smart guys with dumb guy questions!
-
RE: Delta calibration not touching bed at edges
It should be able to reach since I have a 280ish mm build plate but am aiming for a much smaller area than that. I remember reading somewhere about that dive height so I’ll give that a shot next. Thank you!
-
Delta calibration not touching bed at edges
Hello All,
I finally got my delta to the point of calibration after various issues that were all self-induced. When I try to auto calibrate, it gets tot he point of touching the various spots on the bed by starting at the outside then working its way in but I have an issue with the initial 3 spots not going down far enough to touch. Once it passes those three and proceeds to the final 4 spots (including x0y0 it is able to touch and registers perfectly. Almost like I have a configuration problem with one of the settings so hoping someone has some insight on something I did wrong.
Here's my config.g file for the delta.
; Configuration file for Duet 3 (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sun May 22 2022 18:48:45 GMT-0500 (CDT); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Delta" ; set printer name
M665 R228.6 L400.1 B203.2 H546.45 ; 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
M551 P"******" ; set password
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.0 S0 ; physical drive 0.0 goes forwards
M569 P0.1 S0 ; physical drive 0.1 goes forwards
M569 P0.2 S0 ; physical drive 0.2 goes forwards
M569 P0.3 S0 ; physical drive 0.3 goes forwards
M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z80.00 E663.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 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"!io0.in" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin io0.in
M574 Y2 S1 P"!io1.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin io1.in
M574 Z2 S1 P"!io2.in" ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin io2.in; Z-Probe
M558 P8 R0.4 C"io8.in+io8.out" H5 F1800 T6000 ; set Z probe type to effector and the dive height + speeds
G31 P100 X0 Y0 Z-0.375 ; set Z probe trigger value, offset and trigger height
M557 R250 S20 ; define mesh grid; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out0 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 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C; Fans
M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
M106 P0 S1 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out4" Q500 ; create fan 1 on pin out4 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on; Tools
M563 P0 S"Extruder" 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
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power lossAnd here's my bed.g file:
; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sun May 22 2022 18:48:45 GMT-0500 (CDT)
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-9999
G30 P1 X73.53 Y-42.45 H0 Z-9999
G30 P2 X-73.53 Y-42.45 H0 Z-9999
G30 P3 X0 Y42.4 H0 Z-9999
G30 P4 X36.72 Y-21.2 H0 Z-9999
G30 P5 X-36.72 Y-21.2 H0 Z-9999
G30 P6 X0 Y0 H0 Z-9999 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) -
RE: Flashing firmware after update failure
Turns out my SD card must've died on me somewhere along the way as replacing it and dropping in the backup I took of it before the firmware update seems to have gotten me access to web control again. Unfortunately, I have another new issue! It's asking for a password that I'm not aware of in order to access web control. Currently looking through the docs hoping to find what the default is.
Thanks everyone for the help so far.
Edit: Using M551 I was able to get in and change config.g file with a password I know. All is well for now until I end up breaking this thing again!
-
RE: Flashing firmware after update failure
@droftarts I finally got some firmware to upload to the board after borrowing a coworkers windows machine. Had no luck with getting it to work via a linux machine I had lying around. I now have a new issue - upon connecting to the board with serial tools and sending M552 to start establishing a network connection I get this error:
M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.4.0 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2022-03-15 18:57:26
ok
M552
Error: M552: Network-related commands are not supported when using an attached Single Board Computer
okAs of this time I don't have any SBC connected or plans to use one. I can't seem to find anywhere in the docs for what to do next to get rid of this error.
Any insight?
-
RE: Flashing firmware after update failure
@droftarts Good info - I'm currently trying to get ubuntu on a flash drive but can't seem to get my M1 Mac to allow me to boot from it. One issue after another today apparently!
Currently my board has a solid light and per your prior response is telling me the firmware is gone. Not sure what could have happened to it during that update but it appears to have lost its firmware during that process through DWC. Bad board from the factory possibly? I was able to get on DWC during initial install of the board/wiring to the printer itself, but once uploading that new firmware for my delta it decided to not cooperate anymore. I specifically made sure to avoid the erase pins by putting some electrical tape around them so I know I didn't accidentally bridge them.
-
RE: Flashing firmware after update failure
@droftarts Thanks for the info - I must have been reading the docs wrong and thinking it would work for my board.
-
Flashing firmware after update failure
Hello all,
I'm having a really rough time trying to get firmware back on my MB6HC via my Mac.
I created new firmware for my delta using the reprap builder and when I went to upload it via the web control page it simply loaded and loaded but then never did anything after that. I let it sit for a few hours and came back to a bricked board.
I've tried following every tutorial to do this but can't get anywhere with it since Bossa won't launch and the command line version crashes upon start.
Does anyone have any insight or am I stuck just ordering a new board?