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

    Raspberry pi Octoprint and duetwifi

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    11
    16
    13.1k
    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.
    • dc42undefined
      dc42 administrators
      last edited by

      Chrishamm is already working on providing the ability to change the file sort order.

      Duet WiFi hardware designer and firmware engineer
      Please do not ask me for Duet support via PM or email, use the forum
      http://www.escher3d.com, https://miscsolutions.wordpress.com

      1 Reply Last reply Reply Quote 0
      • DjDemonDundefined
        DjDemonD
        last edited by

        Fantastic thank you.

        Simon. Precision Piezo Z-Probe Technology
        www.precisionpiezo.co.uk
        PT1000 cartridge sensors NOW IN, just attach to your Duet board directly!

        1 Reply Last reply Reply Quote 0
        • Artyundefined
          Arty
          last edited by

          I really like telegram bot plugin in octoprint. It's a pity there is no something similar in webcontrol.

          1 Reply Last reply Reply Quote 1
          • Cataundefined
            Cata
            last edited by

            I read on face someone makes the developement of telegram bot for duet

            1 Reply Last reply Reply Quote 0
            • EasyTargetundefined
              EasyTarget
              last edited by

              @npm1:

              Hiya,
              How would i settup the duetwif with octoprint on the pi kind regards,

              Naz,
              Octoprint/OctoPI will probably 'just work' with a duet once you have the USB cable connected. You'll need to follow the printer setup wizzard; and set the 'Ignore any unhandled errors from the firmware' option on the connection menu [this seemed to be necessary for me but I have not revisited it to see if I was seeing real errors or not].

              Also the Duet (being Duo based with native USB features) comes up on a different USB port to the standard; it will be on /dev/ttyACM0 etc, rather then /dev/ttyUSB0.

              Beyond that; treat as any other Octoprint rig, there are so many resources out there for installing, connecting and configuring that I wont duplicate that.

              Speaking of duplication.. TL;DR.. The native Duet web interface is very good, compared to Octoprint it provides a lot more info about the printer itself, real-time axes positions, direct access to the machines configuration files, upgrade wizards, heightmap display etc. I use the webcontrol all the time when I'm (re)configuring my system at home.

              But I do not use it to print; I print via Octoprint and streaming the gcodes over USB the old-fashioned way; Octoprint is a great interface for organizing/printing from, file management is good, webcam/timelapse integration seamless, The gcode viewer is handy, the plugin system is a bit patchy but contains some good stuff like the heater timeout plugin.

              Most importantly it is built on a strong base (a four-core machine with reasonable memory and storage and a well featured Linux OS) which gives it a much stronger platform for running web services; sessions stay connected, it retries properly and recovers from network outages with ease, running behind a web server as a proxy, an delegating autnentication to that is also easy. I feel happy exposing octoprint to the Internet and sharing that obscure link with my parents and peers. The native web interface is neither reliable enough in it's connectivity, or secure enough in it's operation to allow this.

              And since I was already been using Octoprint on a 8bit cartesian printer it seemed natural to do the same with the Duet; I've never had a failure caused by Octoprint, (that time I rebooted it mid-print.. my fault, nobody else) and always been able to connect and see what is happening, even from trains over mobile data and other circumstances where Duet Web control wouldn't stand a chance of remaining usable. Also I'm a geek, I /enjoyed/ setting up a dual webcam/octorpint server on a single Pi.

              For reference: Here are my custom controls I use with the Duet in Octoprint:

              [[yml]]
              controls:
              - children:
                - command: M114
                  name: Get Position
                  regex: X:([0-9.]+) Y:([0-9.]+) Z:([0-9.]+) E0:([0-9.]+)
                  template: 'Position: X={0}, Y={1}, Z={2}, E0={3}'
                  type: feedback_command
                layout: horizontal
                name: Reporting
                type: section
              - children:
                - command: G32
                  name: Delta Calibrate
                  type: command
                - command: G29 S1
                  name: Load Mesh Compensation
                  type: command
                - command: G32 S2
                  name: Mesh Compensation off
                  type: command
                - command: G29
                  name: Generate Mesh
                  type: command
                layout: horizontal
                name: Delta
                type: section
              - children:
                - command: M552 S0
                  name: Disable WiFi
                  type: command
                - command: M552 S1
                  name: Enable WiFi
                  type: command
                layout: horizontal
                name: Duet
                type: section
              
              

              And.. all of the above will be superseded for me soon because I'm working on a way to drive both the Duet and my cartesian via scripting and a CI software system (still using the PI, but not as a Octoprint server anymore)

              Disaster? The original Printeye is dying with RRF 3.5 (M208 depreciated).
              PrintPy2024 to the rescue!
              MicroPython based; with simple wiring and and no custom PCB.

              1 Reply Last reply Reply Quote 0
              • Cataundefined
                Cata
                last edited by

                1 Reply Last reply Reply Quote 0
                • JohnOCFIIundefined
                  JohnOCFII
                  last edited by

                  @EasyTarget:

                  Speaking of duplication.. TL;DR.. The native Duet web interface is very good, compared to Octoprint it provides a lot more info about the printer itself, real-time axes positions, direct access to the machines configuration files, upgrade wizards, heightmap display etc. I use the webcontrol all the time when I'm (re)configuring my system at home.

                  But I do not use it to print; I print via Octoprint and streaming the gcodes over USB the old-fashioned way; Octoprint is a great interface for organizing/printing from, file management is good, webcam/timelapse integration seamless, The gcode viewer is handy, the plugin system is a bit patchy but contains some good stuff like the heater timeout plugin.

                  Fascinating idea. I hadn't considered feeding the DuetWifi via USB and continuing to use OctoPrint as I do on my MK2.
                  Architecturally, I'm conflicted. I love OctoPrint, and the plug-in environment. I wish I had all those features in DWC, or something similar. But – I also appreciate that Duet prints from the on-board SD card. I guess the ideal situation would be for OctoPrint to communicate with Duet via WiFi, and treat it similarly to the way OctoPrint treats printing from the printer's own SD card -- just communicating via WiFi instead of over USB.

                  The other approach is to load up the Duet and DWC or similar will more software features similar to OctoPrint, but as you pointed out, I think the hardware is more limited, and it doesn't make sense to take resources away from the main focus -- printing.

                  John

                  1 Reply Last reply Reply Quote 1
                  • EasyTargetundefined
                    EasyTarget
                    last edited by

                    @JohnOCFII:

                    Architecturally, I'm conflicted. I love OctoPrint, and the plug-in environment. I wish I had all those features in DWC, or something similar. But – I also appreciate that Duet prints from the on-board SD card. I guess the ideal situation would be for OctoPrint to communicate with Duet via WiFi, and treat it similarly to the way OctoPrint treats printing from the printer's own SD card -- just communicating via WiFi instead of over USB.

                    Totally agree with that conflict 🙂
                    Several printers have dedicated plugins for Octoprint; someone raised the idea of one for the Duet [[url]https://github.com/foosel/OctoPrint/issues/1628] but the project lead would rather work on a more generic comms layer to support all the wifi/bluetooth/usb/other printers out there rather than a Duet specific module; I understand the logic even if it's something I'd personally like.

                    @JohnOCFII:

                    I think the hardware is more limited,

                    AFIK the web server runs on the wifi module itself, there is a surprisingly competent SOC in there, but it is still limited. My personal (and it is only that, Duet3d probably have business priorities that conflict etc..) opinion is that it needs multiple persistent IP connections/session capabilities asap to mitigate connectivity issues; and TLS (or some other, even if it is limited) encryption even within local area nets if at all possible; Beyond that, a lot of features, even advanced ones like timelapse capture and slicing support, could be done on the client side via HTML5 with the duet working as a data source, rather than a processor.

                    Alex9779 created this issue in foosel/OctoPrint

                    closed [Brainstorming] DuetWifi support #1628

                    Disaster? The original Printeye is dying with RRF 3.5 (M208 depreciated).
                    PrintPy2024 to the rescue!
                    MicroPython based; with simple wiring and and no custom PCB.

                    1 Reply Last reply Reply Quote 0
                    • tychopundefined
                      tychop
                      last edited by

                      The WiFi connection on my DuetWiFi is very disappointing for me. During printing I'm not able to get a connection to the Duet. "The server dropped it's connection" is the error I get.
                      I think I am going to hook the Duet to a Pi and use RepetierServer/OctoPi for the wireless printing.

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

                        Have you read the wiki page on troubleshooting wifi issues?

                        Duet WiFi hardware designer and firmware engineer
                        Please do not ask me for Duet support via PM or email, use the forum
                        http://www.escher3d.com, https://miscsolutions.wordpress.com

                        1 Reply Last reply Reply Quote 0
                        • Mikeundefined
                          Mike
                          last edited by

                          That Telegram bot looks amazing, I hope the guy ends up releasing it.

                          1 Reply Last reply Reply Quote 0
                          • dr.talyundefined
                            dr.taly
                            last edited by

                            @Cata:

                            https://i.imgur.com/GSW6lNs.png

                            i want it hahah

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