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

    3D GCode Viewer integrated with DWC

    Scheduled Pinned Locked Moved
    Duet Web Control wishlist
    42
    284
    30.6k
    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.
    • bastienundefined
      bastien
      last edited by

      i just install 3.2, i viewer in sub menu in files but no in main menu

      bastienundefined 1 Reply Last reply Reply Quote 0
      • bastienundefined
        bastien @bastien
        last edited by

        @bastien said in 3D GCode Viewer integrated with DWC:

        i just install 3.2, i viewer in sub menu in files but no in main menu

        it's ok, i re install plug in and start in new plug in menu 😊 😊

        1 Reply Last reply Reply Quote 1
        • DIY-O-Sphereundefined
          DIY-O-Sphere
          last edited by

          @Sindarius
          Are there known issues with the latest version on a maestro?
          Cant't get it working anymore. (RRF 3.2_b4 +0.11.1)
          The previous versions of fw and plugin worked. (guess RRF 3.2_b2 +0.6.5)

          (UTC+1)

          Sindariusundefined 1 Reply Last reply Reply Quote 0
          • Sindariusundefined
            Sindarius @DIY-O-Sphere
            last edited by

            @DIY-O-Sphere I pulled down and installed the 3.2-beta4 that is on GitHub, I normally run my own build, and was able to install my plugin without any problems. Make sure you are pulling the latest version of my plugin from the github releases page https://github.com/Sindarius/DWC_GCodeViewer_Plugin/releases. I don't believe the firmware version itself should have any play since the plugin is a javascript solution that runs in DWC itself.

            Just double check the following to make sure you are on the latest

            2f5705dc-946a-42af-a304-9ca6bd2fc955-image.png

            50ffd5fa-c1a7-4f87-a892-edb63a88a2e1-image.png

            dd4df0c5-3313-4d74-a61f-3fdf8aa6602c-image.png

            DIY-O-Sphereundefined 1 Reply Last reply Reply Quote 0
            • DIY-O-Sphereundefined
              DIY-O-Sphere @Sindarius
              last edited by

              @Sindarius
              After de-energising and powering up everything is working now....
              A simple sw-reset after the update was not enough.....

              (UTC+1)

              1 Reply Last reply Reply Quote 1
              • PCRundefined
                PCR
                last edited by

                @Sindarius

                70b73da3-1ce4-4c25-9c14-8f7e63c1e405-grafik.png

                File processed with arcwelder

                01_SP2_Unterschale_DQ2_PET_0.3mm_1h39m.gcode.txt

                1 Reply Last reply Reply Quote 0
                • PCRundefined
                  PCR
                  last edited by

                  27aaf89a-641c-4429-a989-e822a6eb21d2-grafik.png

                  d341be63-395a-469c-adfe-a17e117efbe2-grafik.png

                  Sindariusundefined 1 Reply Last reply Reply Quote 0
                  • Sindariusundefined
                    Sindarius @PCR
                    last edited by

                    @PCR I’ll take a look at the file. Those are some impressive arcs πŸ˜„

                    1 Reply Last reply Reply Quote 1
                    • PCRundefined
                      PCR
                      last edited by

                      no rush πŸ˜‰ was more like a little note

                      Sindariusundefined 1 Reply Last reply Reply Quote 0
                      • Sindariusundefined
                        Sindarius @PCR
                        last edited by

                        @PCR This probably looks better.

                        8f24d90c-e297-4560-84a8-91d4112f5e10-image.png

                        1 Reply Last reply Reply Quote 1
                        • Sindariusundefined
                          Sindarius
                          last edited by

                          G3 fix is in RC2

                          https://github.com/Duet3D/DuetWebControl/releases/tag/3.2.0-rc2

                          A Former User? 1 Reply Last reply Reply Quote 0
                          • A Former User?
                            A Former User @Sindarius
                            last edited by A Former User

                            @Sindarius

                            A small thing that I catched:

                            On all 3-d-software I am aware of, if a cartesian-csys-system is used -> x-y-z are coloured in r-g-b,

                            e.g. "sol...orks" here:

                            72a338ba-2922-4983-b4b8-103dd83fb69d-grafik.png

                            e.g. "rh...-3d":

                            7943f143-13bc-4dd4-b5a7-d3365997c13e-grafik.png

                            e.g. "sim....y-3D":

                            1d376515-c168-4e92-bd0c-c1317a42ff44-grafik.png

                            e.g. or the height-map within "DWC":

                            89f7d0a1-047f-4b03-81d8-e7ec560fdfa3-grafik.png

                            but here it is r-b-g:

                            ba49e610-d43a-4631-8283-1a71ef954c21-grafik.png

                            Before I forget: Thanks for you cool work!
                            πŸ˜‰

                            Sindariusundefined 1 Reply Last reply Reply Quote 1
                            • Sindariusundefined
                              Sindarius @A Former User
                              last edited by

                              @LB Since it is cosmetic I’ll work the change into 3.3

                              A Former User? 1 Reply Last reply Reply Quote 0
                              • CCS86undefined
                                CCS86
                                last edited by

                                Cool plugin!

                                I'm trying it out on a Duet Maestro on DWC/RRF 3.2 RC2

                                Seeing some weirdness on one file. With "spread lines" enabled, everything looks good:

                                d263d1ab-218b-4d68-b655-682bd7052dd6-image.png

                                But with it disabled, some weirdness:

                                44c1da06-d214-4b29-825c-65aa5da6dca4-image.png

                                Sindariusundefined 1 Reply Last reply Reply Quote 0
                                • A Former User?
                                  A Former User @Sindarius
                                  last edited by A Former User

                                  @Sindarius

                                  Cool πŸ™‚ - looking forward!

                                  Another small thing thatΒ΄s related to it:
                                  When within "settingS" choosing "volume" (instead of "bed") the wireframe is by default blue, and since 1 of the axis is also blue it might be a unlucky default colour for the wireframe of the print-volume regarding the default-csys-colouring:

                                  a2f4ff0c-f6d5-4c79-889d-749d5acdcf88-grafik.png

                                  If the default would be a slightly transparent white (I know transparency is not there yet so to show what I mean I picked a greyish tone), you could better see the the csys:

                                  e83ba323-9f97-49dd-a4ea-d3b089ab4a93-grafik.png

                                  I know this is a field where opinions might easily differ, so it is maybe just something to think about πŸ˜‰

                                  Thanks for all your work,
                                  cheers!

                                  Sindariusundefined 1 Reply Last reply Reply Quote 0
                                  • Sindariusundefined
                                    Sindarius @CCS86
                                    last edited by

                                    @CCS86 if you could share your file that would help me to look at it.

                                    CCS86undefined 1 Reply Last reply Reply Quote 0
                                    • Sindariusundefined
                                      Sindarius @A Former User
                                      last edited by

                                      @LB volume is an odd duck because I had to do some things to make something work for delta beds. Transparency is always a pain heh

                                      A Former User? 1 Reply Last reply Reply Quote 0
                                      • A Former User?
                                        A Former User @Sindarius
                                        last edited by A Former User

                                        @Sindarius

                                        reliable results with (alpha + all-of-the-webbrowsers-out-there)=oxymoron 🀣

                                        1 Reply Last reply Reply Quote 1
                                        • CCS86undefined
                                          CCS86 @Sindarius
                                          last edited by

                                          @Sindarius said in 3D GCode Viewer integrated with DWC:

                                          @CCS86 if you could share your file that would help me to look at it.

                                          Sure thing.

                                          Playseat Foot.gcode.txt

                                          Sindariusundefined 1 Reply Last reply Reply Quote 0
                                          • Sindariusundefined
                                            Sindarius @CCS86
                                            last edited by

                                            @CCS86 Thanks for the file. I managed to take a look at it and the line that is tripping up the viewer is in your ending gcode trips up the viewer into thinking the last layer height should be 5mm tall which causes it to freak out.
                                            G1 Z5 E-3 F4000

                                            I commented out that line and got this
                                            4752ff0e-02e9-40dd-8446-75a52994fde6-image.png

                                            This is not an issue with your gcode but an issue with how the viewer not appreciating a retract and z travel in the same line. I'll look at getting a fix in for 3.3

                                            Also because line rendering does not care about layer height doing forced line rendering showed the correct results.

                                            d5b8f838-f26b-4aad-bc1f-21f2c9d4870e-image.png

                                            Either way thank you for sharing your file and I'll get this resolved.

                                            Thanks!

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