Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Duet2/Ethernet Update from 2.05 to 3.2 went perfectly.

    Firmware installation
    3
    16
    44
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • alankilian
      alankilian last edited by alankilian

      I followed the three-part upload process to update the Duet2/Ethernet described by @Phaedrux here

      I also used the configurator to get a working set of config files I uploaded to the system.

      My Paneldue eas showing the expected incorrect values for temperatures, so I also updated that. It took me three tries because my order says "Paneldue 5 inch" and I had no idea which one I had, so I tried old firmware, then different firmware, then just the right firmware and got it working. I used Bossa, but now that I know I have a Paneldue-3 5" I think I can update using the Duet2.

      My hot-end fan was always on, so I looked and it was plugged into FAN2 so I moved it to FAN1 and it works properly.

      I found the thermister Beta for the bed and set that. I'm waiting for SeeMeCNC to tell me what thermister is in the SE300 so I can set the beta for that, but it at least heats up and is stable.

      When the head is very low, G28 raises the carriage and stops and I have to run it again. I think I had a problem with the configuration where it would not let me set a move longer than 250mm. There are two settings for "height" and I think you need to set one of them first and then the other, but I didn't do that.

      Using the DWC "Bed Mapping" butting results in an error message about macros/bed mapping not having any Z-probe pins defined. Maybe I'm not supposed to use that anyway.

      G29 works fine for bed mapping however, so I'm good.

      So, it all went pretty smoothly.

      I'll need to load some filament and try printing and see how that goes now. 🙂

      1 Reply Last reply Reply Quote 0
      • Phaedrux
        Phaedrux Moderator last edited by

        If you want you can post your files and we can take a look and see if there are any errors to correct.

        Post your config.g, homing files, and the results of M122 and M98 P"config.g" please.

        1 Reply Last reply Reply Quote 0
        • alankilian
          alankilian last edited by alankilian

          I have a few issues:

          • G28 does not home the first time if the extruder is vary low. I need to do it twice.
          • After G28/G29, my Z=0 is about 2.5mm LOWER than the bed. I need to baby-step a million times at the beginning of a print. So I need to calibrate that somehow.
          • I'm overextruding so I need to calibrate that next.
          • I can't run the first probe macro. It says it doesn't know the pin for the ZProbe.
          M98 P"config.g"
          HTTP is enabled on port 80
          FTP is disabled
          TELNET is disabled
          
          m122
          === Diagnostics ===
          RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet Ethernet 1.02 or later
          Board ID: 08DGM-95BLL-N6PSS-6JKD2-3S46Q-1JSRL
          Used output buffers: 3 of 24 (15 max)
          === RTOS ===
          Static ram: 23460
          Dynamic ram: 68116 of which 60 recycled
          Never used RAM 20444, free system stack 141 words
          Tasks: NETWORK(ready,186) HEAT(blocked,309) MAIN(running,466) IDLE(ready,19)
          Owned mutexes:
          === Platform ===
          Last reset 00:01:00 ago, cause: power up
          Last software reset at 2021-02-01 14:05, reason: User, GCodes spinning, available RAM 20444, slot 1
          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
          MCU temperature: min 20.4, current 23.7, max 24.6
          Supply voltage: min 13.0, current 13.1, max 13.1, under voltage events: 0, over voltage events: 0, power good: yes
          Driver 0: position 65025, standstill, SG min/max 0/503
          Driver 1: position 65025, standstill, SG min/max 0/499
          Driver 2: position 65025, standstill, SG min/max 0/520
          Driver 3: position 0, standstill, SG min/max not available
          Driver 4: position 0, standstill, SG min/max not available
          Driver 5: position 0
          Driver 6: position 0
          Driver 7: position 0
          Driver 8: position 0
          Driver 9: position 0
          Driver 10: position 0
          Driver 11: position 0
          Date/time: 2021-02-01 14:51:40
          Cache data hit count 90232356
          Slowest loop: 7.74ms; fastest: 0.18ms
          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 1.3ms, write time 0.0ms, max retries 0
          === Move ===
          DMs created 83, maxWait 23456ms, bed compensation in use: none, comp offset 0.000
          === MainDDARing ===
          Scheduled moves 5, completed moves 5, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === AuxDDARing ===
          Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === Heat ===
          Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
          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: 18.73ms; fastest: 0.02ms
          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
          HTTP sessions: 1 of 8
          Interface state active, link 100Mbps full duplex
          
          ; homedelta.g
          ; called to home all towers on a delta printer
          ;
          ; generated by RepRapFirmware Configuration Tool v3.2.2 on Sun Jan 31 2021 17:48:35 GMT-0500 (Eastern Standard Time)
          G91                        ; relative positioning
          G1 H1 X265 Y265 Z265 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 F6000               ; move down a few mm so that the nozzle can be centred
          G90                        ; absolute positioning
          G1 X0 Y0 F6000             ; move X+Y to the centre
          
          ; bed.g
          ; called to perform automatic delta calibration via G32
          ;
          ; generated by RepRapFirmware Configuration Tool v3.2.2 on Sun Jan 31 2021 17:48:35 GMT-0500 (Eastern Standard Time)
          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)
          
          ; Configuration file for Duet WiFi (firmware version 3)
          ; executed by the firmware on start-up
          ;
          ; generated by RepRapFirmware Configuration Tool v3.2.2 on Sun Jan 31 2021 17:48:35 GMT-0500 (Eastern Standard Time)
          
          ; General preferences
          G90                                            ; send absolute coordinates...
          M83                                            ; ...but relative extruder moves
          M550 P"MyDuet"                                 ; set printer name
          M665 R144 L291.06 B135 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 S1                                        ; enable network
          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
          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.20             ; 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 X1200 Y1200 Z1200 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 P5 C"^zprobe.in" A5 H3 R0.4 F2000 T6000   ; set Z probe type to switch and the dive height + speeds
          G31 P500 X0 Y0 Z-0.15                          ; set Z probe trigger value, offset and trigger height
          M557 R85 S20                                   ; define mesh grid
          
          ; Heaters
          M308 S0 P"bedtemp" Y"thermistor" T100000 B4388 ; 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 B0 S1.00                               ; disable 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 B4388  ; 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 S250                                   ; set temperature limit for heater 1 to 250C
          
          ; 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
          T0
          
          ; Custom settings are not defined
          
          ; Miscellaneous
          M501                                           ; load saved parameters from non-volatile memory
          M575 P1 S1 B57600
          
          ; config-override.g file generated in response to M500 at 2021-02-01 13:42
          ; This is a system-generated file - do not edit
          ; Delta parameters
          M665 L291.060:291.060:291.060 R144.279 H402.471 B150.0 X-0.319 Y-0.403 Z0.000
          M666 X0.477 Y-0.293 Z-0.184 A0.00 B0.00
          ; Heater model parameters
          M307 H0 R0.101 C338.000:338.000 D7.20 S1.00 V13.0 B0
          M307 H1 R3.856 C85.700:85.700 D5.60 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
          
          1 Reply Last reply Reply Quote 0
          • alankilian
            alankilian last edited by

            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.

            alankilian 1 Reply Last reply Reply Quote 1
            • Phaedrux
              Phaedrux Moderator last edited by

              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 1 Reply Last reply Reply Quote 0
              • alankilian
                alankilian @Phaedrux last edited by

                @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?

                Phaedrux 1 Reply Last reply Reply Quote 0
                • alankilian
                  alankilian @alankilian last edited by

                  @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.

                  1 Reply Last reply Reply Quote 0
                  • Phaedrux
                    Phaedrux Moderator @alankilian last edited by

                    @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?

                    1 Reply Last reply Reply Quote 0
                    • alankilian
                      alankilian last edited by

                      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
                      
                      Phaedrux 1 Reply Last reply Reply Quote 0
                      • alankilian
                        alankilian last edited by

                        I've NEVER really gotten a satisfactory workflow for:

                        • calibrating after moving the machine
                        • calibrating once-per-power-on
                        • calibrating once-per-print.
                        Phaedrux dc42 2 Replies Last reply Reply Quote 0
                        • Phaedrux
                          Phaedrux Moderator @alankilian last edited by

                          @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

                          alankilian 1 Reply Last reply Reply Quote 0
                          • Phaedrux
                            Phaedrux Moderator @alankilian last edited by

                            @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 1 Reply Last reply Reply Quote 1
                            • alankilian
                              alankilian @Phaedrux last edited by

                              @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.

                              1 Reply Last reply Reply Quote 0
                              • alankilian
                                alankilian @Phaedrux last edited by

                                @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 1 Reply Last reply Reply Quote 0
                                • Phaedrux
                                  Phaedrux Moderator @alankilian last edited by

                                  They are delta applicable. 🤷

                                  1 Reply Last reply Reply Quote 0
                                  • dc42
                                    dc42 administrators @alankilian last edited by

                                    @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

                                    1 Reply Last reply Reply Quote 1
                                    • First post
                                      Last post
                                    Unless otherwise noted, all forum content is licensed under CC-BY-SA