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

    Network disconnects when I attempt to start a gcode file

    Scheduled Pinned Locked Moved
    General Discussion
    2
    6
    259
    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.
    • chiefmonkeyundefined
      chiefmonkey
      last edited by

      I have a Duet3 that is setup as an IDEX stye unit with one X gantry but two independant Z carriages. It is connected thru a raspberry pi 4.

      We are at the stage that we have setup our homing config and everything seems fine, we have verified all our steps, and we have communication from the web interface with no issue.

      When ever we attempt to initiate a file we get network disconnect and then "Operation failed (Reason: Cannot assign requested address /var/run/dsf/dcs.sock)".

      It then reconnects, though sometimes when it reconnects it has lost its config.

      Screen Shot 2020-11-02 at 12.55.18 PM.png

      I'm at a loss of where to even begin trouble shooting this.

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

        Please send M122 and post the results.

        It would also help if you post your config.g and the results of M98 P"config.g"

        Your firmware and DWC versions should be 3.1.1.

        Have you recently done a sudo apt-get update and apt-get upgrade on the pi?

        How is the Pi4 powered?

        Z-Bot CoreXY Build | Thingiverse Profile

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

          @Phaedrux Screen Shot 2020-11-02 at 1.12.42 PM.png

          The Pi is powered thru the ribbon cable.

          I'm unable to SSH into the PI right now, so I'm wondering if that could be the issue

          M98 P"config.g" when executed I get
          Error: Macro file config-override.g not found

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

            It looks like you're still on 3.01RC9

            You'll need to update to 3.1.1. Your issue may be resolved after that.

            If after doing a apt-update it still shows as 3.01RC9 you may need to refresh your DuetPi image with the latest

            https://pkg.duet3d.com/DuetPi.zip

            Alternatively you can try this update method to get back in sync.

            https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_from_RRF3_0_Beta_12_to_3_0_Final_via_DWC

            Powering the Pi4 directly from the Duet can be problematic due to the increased power draw of the pi4 over the pi3 which was originally targeted. Adding USB peripherals to the Pi4 can easily push it over the power budget. So it may be a good idea to power the Pi4 directly.

            https://duet3d.dozuki.com/Wiki/SBC_Setup_for_Duet_3#Section_Troubleshooting

            https://duet3d.dozuki.com/Wiki/Duet_3_Mainboard_6HC_Hardware_Overview#Section_5V

            Z-Bot CoreXY Build | Thingiverse Profile

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

              @chiefmonkey said in Network disconnects when I attempt to start a gcode file:

              Error: Macro file config-override.g not found

              This just means that you have M501 at the end of your config.g to load the config-override.g file, but haven't yet used M500 to create the config-override.g file.

              Z-Bot CoreXY Build | Thingiverse Profile

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

                @Phaedrux Thank you for your help, it was the firmware. I had to use the Bossa method with the usb connected from the Duet to the PI

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