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

    M98 issue from S3D

    Scheduled Pinned Locked Moved
    General Discussion
    4
    12
    1.5k
    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.
    • stephencundefined
      stephenc
      last edited by

      hello,

      trying to setup a routine for before printing and after print finished

      I created start.g and printend.g inside macro folder

      in S3D under the script I added M98 Pstart.g and M98Pprintend.g respectively under starting and ending script

      but when I start the print, it immediately heat up tool0, which is not what I wanted here's my start.g

      –----------------------------------------------------
      ; start.g
      ; run before print job

      homeall.g
      G10 P0 S215 ; set tool0 temp
      T0 ; heat up tool0
      M116 ; wait until tool0 fully heated

      G90 ; set absolute
      G1 F1500 ; set feedrate
      G1 Z0.2 ; drop z to printing 1st layer height
      G1 X100 E10 ; purge 10mm filament while running 100mm in X direction

      so I called for homeall.g first but it didn't happen... I'm unsure what happened am I using the macro incorrectly?

      Thanks,
      Stephen

      Stephen
      https://github.com/stephenci/ZideX

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

        You can't just put "homeall.g" in a macro file and expect it to run, because it needs to be a GCode. So use either G28 or M98 Phomeall.g.

        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
        • stephencundefined
          stephenc
          last edited by

          K fixed it now it is M98 Phomeall.g but still problem persist…. Starting the print it would ignore everything just heating up and start printing...

          It would even ignore whether x y z have been homed or not...

          Stephen
          https://github.com/stephenci/ZideX

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

            I think you will find that S3D is inserting your startup script after the heating commands that it generates. AFAIR you can prevent it doing that by including something like this in your startup script (the script you enter in S3D, not the macro file):

            M104 S[first_layer_temperature]
            M116

            This may not be exactly the right syntax for S3D. The idea is that if the slicer see temperature-setting commands in your start script, it won't generate them itself.

            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
            • stephencundefined
              stephenc
              last edited by

              Do I still call for my start.g in S3D start script? So

              M104 S[first_layer_temperature]
              M116
              M98 Pstart.g

              Anyway I'll try that later but last night I did manual homeall before starting print and it was apparent that the end script I put in S3D was ignored I have

              M98 Pprintend.g

              Instead of moving the head and turn off heater and fan like the usual print end routine, the head just stopped at top layer and sit there with everything on…. Had to unplugged the printer.

              Is S3D not recognizing M98?

              Stephen
              https://github.com/stephenci/ZideX

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

                Open the generated GCode file in a text editor to see exactly what S3D has put at the start and end.

                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
                • stephencundefined
                  stephenc
                  last edited by

                  hmm you are right it did not insert any of the M98 parameter in the beginning and end…

                  maybe I did something wrong in S3D. but where else should I put M98 if not in the starting and ending script...

                  Stephen
                  https://github.com/stephenci/ZideX

                  1 Reply Last reply Reply Quote 0
                  • stephencundefined
                    stephenc
                    last edited by

                    Ok I sliced another test and apparently only M98 did not make it to the gcode other code made it.

                    Edit: M98 did not make it

                    Stephen
                    https://github.com/stephenci/ZideX

                    1 Reply Last reply Reply Quote 0
                    • number40fanundefined
                      number40fan
                      last edited by

                      Can you take a screen shot of your S3D Scripts tab? Upload it to imgbb.com and post the BBCode.

                      1 Reply Last reply Reply Quote 0
                      • AndreSundefined
                        AndreS
                        last edited by

                        @stephenc
                        I have this in my end script, and after slicing with S3D 4.0 its in the print file:
                        M98 P0:/macros/end_position

                        start script works too.

                        1 Reply Last reply Reply Quote 0
                        • stephencundefined
                          stephenc
                          last edited by

                          Hmm ok I didn't use the directory location in my P parameter. Maybe that's causing the issue will try adding directory

                          Stephen
                          https://github.com/stephenci/ZideX

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

                            The default folder that M98 looks in is /sys. If you put your scripts in /macros or anywhere else, you need to specify the path to the file in the M98 command.

                            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
                            • First post
                              Last post
                            Unless otherwise noted, all forum content is licensed under CC-BY-SA