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

    S3D rendered and WebControl always shows full Printer height ?

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    8
    964
    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.
    • duetinoundefined
      duetino
      last edited by

      Hello to everyone, back again with some issues !!!

      I render an object to gcode and upload it via API or Browser, I always get the full object height and full layer count. For my machine it is always 500mm and 2500 layers. This is kind of annoying since the time estimated is always funny.

      it looks like this now, in reality I got a object height of 79.9 and we show 500:

      here you can see that it shows 250 of 2500, actually I got 400 layers

      So I created 2 postprocessing lines to filter out height and layer count from my gcode files:

      height=$(grep -E 'layer [0-9]++' $filename | sort  -nk3 |tail -n1| awk -F  "," '{print $2}'|awk '{print $3}')
      layercount=$(grep -E 'layer [0-9]++' $filename | sort  -nk3 |tail -n1| awk -F  "," '{print $1}'|awk '{print $3}')
      
      

      Now I need to know where I can find the names of variables, which webcontrol, respectivly duet3d is interpreting to get the right information displayed.

      all the best

      do it to it -> rinse and repeat

      1 Reply Last reply Reply Quote 0
      • MoS-tekknixundefined
        MoS-tekknix
        last edited by

        Take a look into this:

        https://www.duet3d.com/forum/thread.php?id=2794

        It belongs to the Slicer.

        1 Reply Last reply Reply Quote 0
        • duetinoundefined
          duetino
          last edited by

          I did but I do not have a clue what a macro can do in respect of false information of a slicer?
          I can correct / override it if I get the names of variables I need to set, resp. what needs to be set in gcode file.

          do it to it -> rinse and repeat

          1 Reply Last reply Reply Quote 0
          • MoS-tekknixundefined
            MoS-tekknix
            last edited by

            Okay, i know what you mean and i've done the same.

            At the End of my Print, i've setup'd Simplify3D to completely lower my Bed down to Maximum (365mm). Therefore Simplify3D delivers this Value into the gcode and the Firmware reads the maximum in the gcode and calculates the Layer-Hight to this. It assumes always that the Print is 365mm (in my configuration).

            I've deleted everything and put it into a Macro in /sys and call this Macro. The same is done and interpreted but Simplify3D cannot deliver it into the gcode.

            Therefore everything works as before but the Layerhight is calculated or interpreted correct!

            1 Reply Last reply Reply Quote 0
            • duetinoundefined
              duetino
              last edited by

              Hi, can you give me an example of what you talk about… sounds pretty abstract to me.

              do it to it -> rinse and repeat

              1 Reply Last reply Reply Quote 0
              • MoS-tekknixundefined
                MoS-tekknix
                last edited by

                It's easy. Put everything of your END-GCode in your Slicer and put it into a Macro-File in /sys like after_print.g

                Delete everything in the END-GCode in your Slicer and exchange it against M98 P/sys/after_print.g

                That's all.

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

                  @MoS-tekknix:

                  Okay, i know what you mean and i've done the same.

                  At the End of my Print, i've setup'd Simplify3D to completely lower my Bed down to Maximum (365mm). Therefore Simplify3D delivers this Value into the gcode and the Firmware reads the maximum in the gcode and calculates the Layer-Hight to this. It assumes always that the Print is 365mm (in my configuration).

                  I've deleted everything and put it into a Macro in /sys and call this Macro. The same is done and interpreted but Simplify3D cannot deliver it into the gcode.

                  Therefore everything works as before but the Layerhight is calculated or interpreted correct!

                  You can get round this by putting a comment starting with ;E or ; E at the end of the G1 Z command line that moves the bed down at the end of the print.

                  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
                  • MoS-tekknixundefined
                    MoS-tekknix
                    last edited by

                    @dc42:

                    @MoS-tekknix:

                    Okay, i know what you mean and i've done the same.

                    At the End of my Print, i've setup'd Simplify3D to completely lower my Bed down to Maximum (365mm). Therefore Simplify3D delivers this Value into the gcode and the Firmware reads the maximum in the gcode and calculates the Layer-Hight to this. It assumes always that the Print is 365mm (in my configuration).

                    I've deleted everything and put it into a Macro in /sys and call this Macro. The same is done and interpreted but Simplify3D cannot deliver it into the gcode.

                    Therefore everything works as before but the Layerhight is calculated or interpreted correct!

                    You can get round this by putting a comment starting with ;E or ; E at the end of the G1 Z command line that moves the bed down at the end of the print.

                    Thanks David, that wasn't known by me and i assume a lot of others!

                    Thanks
                    MoS-tekknix

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