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

    M81 command RRF 3.3

    Scheduled Pinned Locked Moved Solved
    General Discussion
    3
    11
    533
    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.
    • uneumann36undefined
      uneumann36
      last edited by

      Hey guys , short Question,
      does anyone know what´s wrong with this message?

      Error: in GCode file line 194152 column 8: M81: expected number after 's'
      

      Finished printing file 0:/gcodes/CFFFP_Copy of Diamond_Hotend_CapProx_wFan.gcode, print time was 2h 30m

      In the past the automatic switch of the printer after printing with M81 command works fine.
      But now anymore.

      So what´s wrong???
      The command with Hand via display works fine.

      1 Reply Last reply Reply Quote 0
      • uneumann36undefined
        uneumann36
        last edited by

        Hi, is there anyone who knows the cause?

        jay_s_ukundefined 1 Reply Last reply Reply Quote 0
        • jay_s_ukundefined
          jay_s_uk @uneumann36
          last edited by

          @uneumann36 whats in your end gcode?

          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

          1 Reply Last reply Reply Quote 0
          • uneumann36undefined
            uneumann36
            last edited by

            I am just at work.
            So something like - set bed temp to 50 degress , if reached M81
            I don´t changed settings (start and endcode) it is since a half year same.
            But since 2 weeks i get this failure message.

            If print is ending, extruder drive home, bed temp setting goes to 50 degress, if 50 degrees is reached the failure above is coming.

            jay_s_ukundefined 1 Reply Last reply Reply Quote 0
            • jay_s_ukundefined
              jay_s_uk @uneumann36
              last edited by

              @uneumann36 best of posting your end gcode.
              Theres no documented changes for M81 but it doesn't hurt to check what you're sending

              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

              uneumann36undefined 1 Reply Last reply Reply Quote 1
              • uneumann36undefined
                uneumann36 @jay_s_uk
                last edited by

                @jay_s_uk

                Ok, here is my cura start code :

                M80
                G28 ;Home
                G92 E0 ;Reset Extruder
                G1 Z2.0 F3000 ;Move Z Axis up
                G1 X5.1 Y20 Z0.28 F5000.0 ;Move to start position
                G1 X5.1 Y200.0 Z0.28 F1500.0 E15 ;Draw the first line
                G1 X5.4 Y200.0 Z0.28 F5000.0 ;Move to side a little
                G1 X5.4 Y20 Z0.28 F1500.0 E30 ;Draw the second line
                G92 E0 ;Reset Extruder
                G1 E4 F300 ; Extrude 4mm of Filament
                G1 Z2.0 F3000 ;Move Z Axis up

                And here the end code :

                M104 S0
                M140 S0
                ;Retract the filament
                G92 E1
                G1 E-1 F300
                G28 X0 Y0
                M84
                M190 R50.000000
                M81 abschalten ; Herunterfahren Netzteil

                Hope this helps to identify my problem.

                jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                • jay_s_ukundefined
                  jay_s_uk @uneumann36
                  last edited by

                  @uneumann36 said in M81 command RRF 3.3:

                  M81 abschalten

                  There's your issue. The word abschalten is before the comment indicator ;
                  I think gcode parsing has been improved which is why this now thrown as an error.
                  Remove it or move the ; to the left of it

                  Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                  uneumann36undefined 1 Reply Last reply Reply Quote 0
                  • uneumann36undefined
                    uneumann36 @jay_s_uk
                    last edited by

                    @jay_s_uk
                    Thank´s , i will try it.
                    But i never change the end code, and it works in the past !

                    1 Reply Last reply Reply Quote 0
                    • uneumann36undefined
                      uneumann36
                      last edited by

                      Yeah, it works!

                      I do not know why it also work in the past.

                      Anyway, thank you !

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

                        @uneumann36 there was a change to GCode parsing. Previously, if a parameter letter was not followed by a number when a number was expected, zero was assumed. The parsing has been tightened up so that an error is flagged instead. I've added this to the upgrade notes for RRF 3.3.

                        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

                        uneumann36undefined 1 Reply Last reply Reply Quote 1
                        • uneumann36undefined
                          uneumann36 @dc42
                          last edited by

                          @dc42
                          Thank you DC , now i understand why this happens now ! 😊

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