Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Config.g not run automatically. MB6HC 3.5.2 - SBC - Bookworm

    Scheduled Pinned Locked Moved Solved
    Beta Firmware
    5
    13
    445
    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.
    • jay_s_ukundefined
      jay_s_uk @blt3dp
      last edited by

      @blt3dp can you post your config?

      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

      blt3dpundefined 1 Reply Last reply Reply Quote 0
      • blt3dpundefined
        blt3dp @jay_s_uk
        last edited by

        For sure, here it is. Also it runs without error when I do M98

        ; Configuration file for Duet 3 (firmware version 3)
        ; executed by the firmware on start-up
        ;
        ; generated by RepRapFirmware Configuration Tool v2.1.4 on Tue Dec 24 2019 21:00:59 GMT-0800 (PST)
        
        ; General preferences
        G90                                                       ; send absolute coordinates...
        M83                                                       ; ...but relative extruder moves
        M665 R179.423 L360.250 B150.000 H368.045                  ; 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
        
        ; Drives
        M569 P0.0 S1                                              ; physical drive 0.0 goes forwards
        M569 P0.1 S1                                              ; physical drive 0.1 goes forwards
        M569 P0.2 S1                                              ; physical drive 0.2 goes forwards
        M569 P0.3 S1                                              ; 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 X200.00 Y200.00 Z200.00 E415                          ; set steps per mm
        M566 X600.00 Y600.00 Z600.00 E2400.00                     ; set maximum instantaneous speed changes (mm/min)
        M203 X15000.00 Y15000.00 Z2400.00 E2400.00                ; set maximum speeds (mm/min)
        M201 X3000.00 Y3000.00 Z3000.00 E7200.00                  ; set accelerations (mm/s^2)
        M906 X1700 Y1700 Z1700 E1100 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"io1.in"                                      ; configure active-high endstop for high end on X via pin io1.in
        M574 Y2 S1 P"io2.in"                                      ; configure active-high endstop for high end on Y via pin io2.in
        M574 Z2 S1 P"io3.in"                                      ; configure active-high endstop for high end on Z via pin io3.in
        
        ; Z-Probe
        M558 P8 R0.4 C"io4.in+io4.out" H5 F1200 T2400              ; set Z probe type to effector and the dive height + speeds
        G31 P100 X0 Y0 Z-0.05                                      ; set Z probe trigger value, offset and trigger height
        M557 R110 S20                                             ; define mesh grid
        
        ; Heaters
        M308 S0 P"temp0" Y"thermistor" T100000 B3590 R2200        ; configure sensor 0 as thermistor on pin temp0
        M950 H0 C"out0" T0 Q10                                    ; create bed heater output on out0 and map it to sensor 0
        M140 H0                                                   ; map heated bed to heater 0
        M143 H0 S120                                              ; set temperature limit for heater 0 to 120C
        M307 H0 R0.241 C905.6 D22.78 S1.00                        ; disable bang-bang mode for the bed heater and set PWM limit
        M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.060000e-8 ; 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
        M143 H1 S280                                              ; set temperature limit for heater 1 to 280C
        M307 H1 R3.597 K0.426:0.000 D2.66 E1.35 S1.00 B0          ; disable bang-bang mode for the nozzle heater and set PWM limit
        
        ; Fans
        M950 F0 C"out7" Q75                                       ; create fan 0 on pin out4 and set its frequency
        M106 P0 S0 B0.5 H-1                                       ; set fan 0 value. Thermostatic control is turned off
        M950 F1 C"out8" Q500                                      ; create fan 1 on pin out8 and set its frequency
        M106 P1 S1 H1 T45                                         ; set fan 1 value. Thermostatic control is turned on
        M950 F2 C"out9" Q500                                      ; create fan 2 on pin out9 and set its frequency
        M106 P2 C"LEDs" S0 H-1                                    ; set fan 2 name and value. Thermostatic control is turned off
        
        ; Tools
        M563 P0 D0 H1 F0                                          ; define tool 0
        G10 P0 X0 Y0 Z0                                           ; set tool 0 axis offsets
        M568 P0 R0 S0                                             ; set initial tool 0 active and standby temperatures to 0C
        
        ; Custom settings
        M575 P1 S1 B57600                                         ; enable support for PanelDue
        M591 D0 P1 C"io5.in" S1                                   ; enable simple sensor (high signal when filament present) via pin io5.in for drive 0
        M955 P0 C"io6.out+io6.in"                                 ; enable accelerometer, cs and int on io6.out and io6.in, all others on tempdb
        M207 S4.5 F2400 Z0.40                                     ; set firmware retraction length, speed and z-lift
        M572 D0 S0.0                                              ; set pressure advance
        
        ; Miscellaneous
        M911 S21.9 R22.9 P"M913 X0 Y0 G91 M83 G1 Z5 E-5 F1000"    ; set voltage thresholds and actions to run on power loss
        

        My 3D Printing YouTube Channel
        Better Living Through 3D Printing

        Follow me on Instagram and Twitter
        Instagram
        Twitter

        jay_s_ukundefined 1 Reply Last reply Reply Quote 0
        • jay_s_ukundefined
          jay_s_uk @blt3dp
          last edited by

          @blt3dp one for @chrishamm

          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

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

            Did this only begin after updating to 3.5.2?
            What was the last version it was working correctly on?
            Have you re-run sudo apt update and sudo apt upgrade?

            Z-Bot CoreXY Build | Thingiverse Profile

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

              @Phaedrux
              It only started after updating to 3.5.2
              Last ver I didn't see any issue with was 3.5.1
              I'll run apt update and upgrade now

              Edit: no change with apt update and upgrade, didn't look to do anything with any duet packages
              Edit again: just downgraded to 3.5.1 and it's all back to normal. Happy to re-up to 3.5.2 if there are troubleshooting/solutions to try.

              My 3D Printing YouTube Channel
              Better Living Through 3D Printing

              Follow me on Instagram and Twitter
              Instagram
              Twitter

              chrishammundefined 1 Reply Last reply Reply Quote 0
              • Phaedruxundefined Phaedrux marked this topic as a question
              • Phaedruxundefined Phaedrux moved this topic from Firmware installation
              • chrishammundefined
                chrishamm administrators @blt3dp
                last edited by chrishamm

                @blt3dp I would've suspected bad permissions but if it works by running M98 P"config.g" there must be something else going on. Could you have a look at the duetcontrolserver journal? If yes, please connect via SSH or open a terminal, then run sudo journalctl -u duetcontrolserver, press Shift+G, and use the arrow keys to look for the last instance where you started the machine but config.g was not run. That should at least show if config.g was requested from the firmware.

                Duet software engineer

                blt3dpundefined 1 Reply Last reply Reply Quote 0
                • blt3dpundefined
                  blt3dp @chrishamm
                  last edited by

                  @chrishamm
                  It looks like quite a few of these

                  Jun 22 21:14:57 delta systemd[1]: Starting duetcontrolserver.service - Duet Control Server...
                  Jun 22 21:15:00 delta DuetControlServer[554]: Duet Control Server v3.5.2
                  Jun 22 21:15:00 delta DuetControlServer[554]: Written by Christian Hammacher for Duet3D
                  Jun 22 21:15:00 delta DuetControlServer[554]: Licensed under the terms of the GNU Public License Version 3
                  Jun 22 21:15:02 delta DuetControlServer[554]: [info] Settings loaded
                  Jun 22 21:15:03 delta DuetControlServer[554]: [info] Environment initialized
                  Jun 22 21:15:03 delta DuetControlServer[554]: [info] Connection to Duet established
                  Jun 22 21:15:03 delta DuetControlServer[554]: [info] IPC socket created at /run/dsf/dcs.sock
                  Jun 22 21:15:03 delta systemd[1]: Started duetcontrolserver.service - Duet Control Server.
                  Jun 22 21:15:07 delta DuetControlServer[554]: [info] Starting macro file config.g on channel Trigger
                  Jun 22 21:15:08 delta DuetControlServer[554]: [warn] Trigger: Aborting orphaned macro file config.g
                  Jun 22 21:15:08 delta DuetControlServer[554]: [error] Trigger: Failed to find corresponding state for code ; Configuration file for Duet 3 (firmware version 3), cancellin>
                  Jun 22 21:15:08 delta DuetControlServer[554]: [info] Aborted macro file config.g
                  Jun 22 21:15:08 delta DuetControlServer[554]: [warn] SPI connection has been reset
                  Jun 22 21:15:17 delta DuetControlServer[554]: [info] Starting macro file dsf-config.g on channel SBC
                  Jun 22 21:15:17 delta DuetControlServer[554]: [info] SBC: Finished macro file dsf-config.g
                  Jul 04 19:41:02 delta systemd[1]: Stopping duetcontrolserver.service - Duet Control Server...
                  Jul 04 19:41:02 delta DuetControlServer[554]: [warn] Received SIGTERM, shutting down...
                  Jul 04 19:41:02 delta DuetControlServer[554]: [info] Application has shut down
                  Jul 04 19:41:02 delta systemd[1]: duetcontrolserver.service: Deactivated successfully.
                  Jul 04 19:41:02 delta systemd[1]: Stopped duetcontrolserver.service - Duet Control Server.
                  Jul 04 19:41:02 delta systemd[1]: duetcontrolserver.service: Consumed 1min 990ms CPU time.
                  

                  I think specifically these lines

                  Jun 22 21:15:07 delta DuetControlServer[554]: [info] Starting macro file config.g on channel Trigger
                  Jun 22 21:15:08 delta DuetControlServer[554]: [warn] Trigger: Aborting orphaned macro file config.g
                  Jun 22 21:15:08 delta DuetControlServer[554]: [error] Trigger: Failed to find corresponding state for code ; Configuration file for Duet 3 (firmware version 3), cancellin>
                  Jun 22 21:15:08 delta DuetControlServer[554]: [info] Aborted macro file config.g
                  

                  My 3D Printing YouTube Channel
                  Better Living Through 3D Printing

                  Follow me on Instagram and Twitter
                  Instagram
                  Twitter

                  chrishammundefined 1 Reply Last reply Reply Quote 0
                  • chrishammundefined
                    chrishamm administrators @blt3dp
                    last edited by

                    @blt3dp Odd, I tried your config.g on a bench setup here but I couldn't reproduce that problem, it came up as expected. Could you please enable debug logging in /opt/dsf/conf/config.json and send me the journalctl log after that once again? That may help me better identify what's going on.

                    Duet software engineer

                    blt3dpundefined 2 Replies Last reply Reply Quote 0
                    • blt3dpundefined
                      blt3dp @chrishamm
                      last edited by

                      @chrishamm

                      Definitely, I just reupdated to 3.5.2, here's journalctl for everything thus far today.

                      dcs_log.txt

                      My 3D Printing YouTube Channel
                      Better Living Through 3D Printing

                      Follow me on Instagram and Twitter
                      Instagram
                      Twitter

                      1 Reply Last reply Reply Quote 0
                      • blt3dpundefined
                        blt3dp @chrishamm
                        last edited by

                        @chrishamm

                        Actually, we can mark this closed. As a test I ended up imaging a new SD card and manually creating all the config files, transplanting the info into them via the editor in DWC (previously I had followed the bookworm upgrade instructions to sftp backup and restore those files)

                        Now everything is back to normal.
                        Thanks for looking into it.

                        My 3D Printing YouTube Channel
                        Better Living Through 3D Printing

                        Follow me on Instagram and Twitter
                        Instagram
                        Twitter

                        droftartsundefined 1 Reply Last reply Reply Quote 0
                        • droftartsundefined
                          droftarts administrators @blt3dp
                          last edited by

                          @blt3dp Okay, maybe an SD card glitch?

                          Ian

                          Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                          blt3dpundefined 1 Reply Last reply Reply Quote 0
                          • droftartsundefined droftarts has marked this topic as solved
                          • blt3dpundefined
                            blt3dp @droftarts
                            last edited by

                            @droftarts

                            I actually ended up reimaging the original sd card and doing the same manual recreation of the config files and it's been fine so far. I think more permissions or something when doing the image/sftp backup/restore originally.

                            My 3D Printing YouTube Channel
                            Better Living Through 3D Printing

                            Follow me on Instagram and Twitter
                            Instagram
                            Twitter

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