Duet2/Ethernet Update from 2.05 to 3.2 went perfectly.

alankilian

I see the Z265s in the homing code. I'll regenerate that in the configurator and see if that solves my homing stopping short problem.

Phaedrux

What is your probe? How is it wired up?

What is the first probe macro? Where does it say it doesn't know the pin?

alankilian

@Phaedrux My probe is an SE300

The First Probe macro is in the DWC Dashboard on the right-side.
Is that a leftover from 2.05?
Maybe I should have refreshed my SD card?

alankilian

@alankilian said in Duet2/Ethernet Update from 2.05 to 3.2 went perfectly.:

I see the Z265s in the homing code.

Changing these to 420 solved the homing problem.

I'll go back to the configurator and see if I can change them there so I have a new, proper configuration.

Phaedrux

@alankilian said in Duet2/Ethernet Update from 2.05 to 3.2 went perfectly.:

@Phaedrux My probe is an SE300

The First Probe macro is in the DWC Dashboard on the right-side.
Is that a leftover from 2.05?
Maybe I should have refreshed my SD card?

I don't know. Can you post the contents of that macro?

alankilian

First Probe file from the macros folder:

M117 Begin RostockMAX Autolevel Calibration
M117 Heating Bed Please Wait
M190 S60
M104 S0
M140 S0
M117 Heat Off - Starting Autolevel Keep Clear
M558 P5 I0 A1 S0.05 R0.4 H20 F2500
G32
M500
M117 Re-Heating for Bed Mapping Please Wait Keep Clear
M558 P5 I0 A1 S0.05 R0.4 H20 F2500 
M190 S60
M140 S0
M106 P0 S0
G29
M500
G28
M84
M375
M117 End RostockMAX Autolevel Calibration

alankilian

I've NEVER really gotten a satisfactory workflow for:

calibrating after moving the machine
calibrating once-per-power-on
calibrating once-per-print.

Phaedrux

@alankilian The problem with that macro is that it has M558 commands formatted for RRF2. So if you intend to use that macro you need to update those M558 lines or remove them entirely.

Running that macro could be part of the problem actually if it's altering your expected M558 from config.g

Phaedrux

@alankilian said in Duet2/Ethernet Update from 2.05 to 3.2 went perfectly.:

I've NEVER really gotten a satisfactory workflow for:

calibrating after moving the machine

calibrating once-per-power-on

calibrating once-per-print.

I'm not a delta user so I'm next to useless there. though from what I gather people tend to home to the top, do a single G30 at the center of the bed, and then do G32 for a 6 factor calibration and maybe a G29 for a heightmap if the bed isn't perfectly flat.

Other than that I can only point you here:

https://duet3d.dozuki.com/Wiki/Calibrating_a_delta_printer
https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareDeltaPrinter

alankilian

@Phaedrux said in Duet2/Ethernet Update from 2.05 to 3.2 went perfectly.:

or remove them entirely

When I have time I should go through the SeeMeCNC SD card contents and update them for RRF3 and send them back.

alankilian

@Phaedrux said in Duet2/Ethernet Update from 2.05 to 3.2 went perfectly.:

https://duet3d.dozuki.com/Wiki/Calibrating_a_delta_printer
https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareDeltaPrinter

Are those RRF 3 applicable?

Phaedrux

They are delta applicable.

dc42

@alankilian said in Duet2/Ethernet Update from 2.05 to 3.2 went perfectly.:

I've NEVER really gotten a satisfactory workflow for:

calibrating after moving the machine

calibrating once-per-power-on

calibrating once-per-print.

The workflow that I use on my delta is:

Press the button on PanelDue that runs the preheat macro. This heats the bed to 60C and the nozzle to 190C.
When it is hot, press the auto calibration button. My bed.g file will home the printer first if necessary.
Print

Between prints I usually run the sequence again, but if I have several small prints to do then I skip it.

Some users put the G32 command in the start.g file or the slicer start Gcode.

HTH David

thekarlmiller

@alankilian - did you come up with a working set of duet2 files for use with the SE300 ?
SeeMeCNC is REFUSING to tell me what the specs are for the SE300 so I can setup the e0temp and e0heat.
I can't figure out what type of temperature sensor it has or its Beta value or the heater parameters either. Very frustrating considering I supported them when they started up, and just paid for the SE300 but the most they would tell me is "change the parameters in config.g".

alankilian

@thekarlmiller I got a few answers from them:

From Steve:
M307 H0 B0                                ; Heated Bed (H2)
M305 P0 T100000 B4388 R4700 C7.06e-8 H30 L0        ; Bed thermistor

M305 P1 T100000 B4388 R4700 H30 L0        ; Hot end Thermistor
M563 P0 D0 H1                              ; Hot end (T0), drive (E0), heater (H1)
G10 P0 S0 R0                              ; Hot end operating and standby temperatures

Also from Steve:
B57560G104F EPCOS / TDK | Mouser 
https://www.mouser.com/ProductDetail/EPCOS-TDK/B57560G104F/?qs=%2Fha2pyFaduhYMyMmNPiRCZBlFExy0IoMv%2FYmPx9ox2iWGLyJQlg7Pg%3D%3D

Here's my config.g but I haven't really worried about the temps. I always end up adjusting up or down for a particular print, so I don't really care that it's super accurate.

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 09 2021 13:21:24 GMT-0500 (Eastern Standard Time)

; General preferences
G90                                                     ; send absolute coordinates...
M83                                                     ; ...but relative extruder moves
M550 P"alan"                                            ; set printer name
M665 R132.5 L291.06 B132.5 H400                         ; 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 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 S1                                              ; physical drive 0 goes forwards
M569 P1 S1                                              ; physical drive 1 goes forwards
M569 P2 S1                                              ; physical drive 2 goes forwards
M569 P3 S1                                              ; physical drive 3 goes forwards

; Testing external driver
;M569 P5 S1 T4:4:4:4                                     ; physical drive 5 goes forwards
;M584 X0 Y1 Z2 E3 U5                                     ; set drive mapping
;M350 X16 Y16 Z16 E16 U16 I1                             ; configure microstepping with interpolation
;M92 X100.00 Y100.00 Z100.00 U100.00 E91.00              ; set steps per mm
;M566 X1200.00 Y1200.00 Z1200.00 U1200 E1200.00          ; set maximum instantaneous speed changes (mm/min)
;M203 X18000.00 Y18000.00 Z18000.00 U18000E1200.00       ; set maximum speeds (mm/min)
;M201 X1000.00 Y1000.00 Z1000.00 U1000E1000.00           ; set accelerations (mm/s^2)
;M906 X1000 Y1000 Z1000 E800 U1000I30                    ; set motor currents (mA) and motor idle factor in per cent

M584 X0 Y1 Z2 E3                                        ; set drive mapping
M350 X16 Y16 Z16 E16 I1                                 ; configure microstepping with interpolation
M92 X100.00 Y100.00 Z100.00 E91.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"xstop"                                     ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop"                                     ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"zstop"                                     ; configure active-high endstop for high end on Z via pin zstop

; Z-Probe
M558 P1 C"zprobe.in" H5 F60000 T6000                    ; set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z0.1                                     ; set Z probe trigger value, offset and trigger height
M557 R132 S20                                           ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4388 C7.06e-8 ; 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 S120                                            ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4385           ; 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 S280                                            ; set temperature limit for heater 1 to 280C

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

; Tools
M563 P0 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
M501                                                    ; Load config-overrides.g
T0                                                      ; Select tool zero

; Miscellaneous
M575 P1 S1 B57600                                       ; enable support for PanelDue

And, after tuning, my config-override.g:

; config-override.g file generated in response to M500 at 2021-02-19 14:01
; This is a system-generated file - do not edit
; Delta parameters
M665 L291.060:291.060:291.060 R143.801 H400.348 B132.5 X0.025 Y-0.081 Z0.000
M666 X-0.047 Y-0.016 Z0.062 A0.00 B0.00
; Heater model parameters
M307 H0 R0.105 C920.580:920.580 D9.08 S1.00 V13.0 B0
M307 H1 R3.939 C97.142:97.142 D5.78 S1.00 V13.0 B0
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00
M486 S-1

I don't think my mech bed heigh compensation works well at all, I just move the part around on the bed until it's OK, and use baby-stepping until I get up to about 0.55mm every time I start.

I had it working much better with RRF 2.05, but I jumped in to RRF 3 and haven't spent the time to figure out how to get things working again.

I just have too many "real" things to print to worry about it.

thekarlmiller

@alankilian said in Duet2/Ethernet Update from 2.05 to 3.2 went perfectly.:

B57560G104F

Thank you very much @alankilian . This is a huge help.
Your answer actually highlights one of my difficulties...
The NTC thermistor you provided has Beta values indicated on its product page of (4066 K, 4036 K, 4085 K), and the datasheet has them as (4072, 4036, 4092) and the product page values aren't even represented in the datasheet.
M308 commands in your config.g set the thermistor Beta value as 4385. I am not saying that it isn't correct, but I don't yet know how to determine how to setup these thermistors for the Duet firmware. BTW - I am currently using v3.2.2.
The other value I don't get is the T100000 - shouldn't that be T104000?
How did you determine the C value for the bed thermistor?
Thank you again, Karl

alankilian

@thekarlmiller I got the bed from Steve at SeeMeCNC:

From Steve:
M307 H0 B0                                    ; Heated Bed (H2)
M305 P0 T100000 B4388 R4700 C7.06e-8 H30 L0   ; Bed thermistor

T100000 is right because these thermisters have a reistance of 100,000 Ohms at 25 degrees C.

But like I said I haven't checked at ALL to see if these are right.

I just fire it up and print.
And then adjust the temps until the parts come out right.