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

    inconsistant operation

    Scheduled Pinned Locked Moved
    Firmware installation
    5
    25
    2.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.
    • sigxcpuundefined
      sigxcpu
      last edited by

      @Sir printsalot: Do an "Apply Settings" on the same device where you get the error.

      1 Reply Last reply Reply Quote 0
      • Sir printsalotundefined
        Sir printsalot
        last edited by

        java script error remember gcode is not a function error {} 1153

        applies settings button does nothing launches this error.
        restore factory setting launches this error.
        every button and and text field launches this error.

        chrishammundefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
        • dc42undefined
          dc42 administrators
          last edited by

          I've asked Christian to take a look. Some other users have reported the same error message, but AFAIK they have all got past it.

          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
          • Sir printsalotundefined
            Sir printsalot
            last edited by

            Well I not smart enough to get past it. So with that shelved wait for Chrishamm I want to focus on 1 item at a time. I'm working with homez.g by itself. after x and y are homed I have machine physically placed with nozzle 5mm off bed which is 5.96 mm probe triggering height. My z coordinate reading is 0 for some reason. I run homez.g and m401 and g30 than m402 run. I have now raise z after in the macro. z raises back to starting position and display reads z0. z is actually back at 5 nozzle 5.96 triggering. where is the 5mm move up coming from and why does the g92 z0 get issued without an offset that includes this un written move. I'm learning more by separating macro and running them separately.

            1 Reply Last reply Reply Quote 0
            • Sir printsalotundefined
              Sir printsalot
              last edited by

              ; homez.g
              ; called to home the Z axis

              this is homez.g where the 5mm lift isn't commanded but happens and reflects z0 when physically at 5.96
              G91 ;relative moves
              G1 Z5 F200 S2 ;raise head 2mm to ensure it above trigger height
              G90 ;back to absolute moves this might be wrong G91
              G1 X148.5 Y151 F2000 ;put probe at bed center
              G91 ; relative moves
              M401 ;run deploy probe macro
              G30 ; lower head, stop when probe triggered and set Z to trigger height
              M402 ;run Retract probe macro
              G90 ;back to absolute
              G92 Z0

              this is homeall.g where z finishes out at 5.96 and physically there.

              ; homeX,Y.g
              ; called to home all axes
              ;
              ; generated by RepRapFirmware Configuration Tool on Sat Nov 25 2017 12:15:39 GMT-0500 (Eastern Standard Time)

              ; Relative positioning
              G91
              G1 Z5 F3000 S2 ;lift Z 5mm
              G1 X-295 y-302 F1500 S1 ;relative move to x,y -295mm neg dir stop at switch
              G1 X5 Y5 F1000 S2 ;relative back off switch 5mm pos dir
              G1 X-295 Y-302 F360 S1 ;relative move x,y -295mm alliance neg stop at switch slowly
              G90 ;absolute moves
              G1 X148.5 Y151 F2000 S2 ; put probe center of bed
              G91
              M401
              G30 ;lower probe set height
              M402
              G90

              i don't see anywhere in these macros a lift after completion and it didn't do it under 1.19.1 firmware and 1.15.1 dwc

              1 Reply Last reply Reply Quote 0
              • Sir printsalotundefined
                Sir printsalot
                last edited by

                sorry to keep adding but I wanted it documented. Ok so I left the machine at it's 5.96 height after homeall.g where display show 5.96 height. I than type in gcode field M401 and than G1 Z0 F2000 S1 and the results are.
                M401 command probe deployed. G1 Z0 F2000 S1 displayed changed to Z0 no machine move physically happened. Same as sending a G92 Z0 command would. Some thing is definitely going on.

                I'm not using printer anymore until someone has time to help. I already has bent parts. I will patiently wait for someone willing to help, I'm just lost. Thank you

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

                  @sir-printsalot said in inconsistant operation:

                  M401 and than G1 Z0 F2000 S1 and the results are.
                  M401 command probe deployed. G1 Z0 F2000 S1 displayed changed to Z0 no machine move physically happened. Same as sending a G92 Z0 command would. Some thing is definitely going on.

                  That is exactly what I would expect to happen. To home using a Z probe you use G30, not G1 S1 Zxxx. The G30 command will stop when the height of the nozzle above the bed is at the trigger height of the Z probe, which you have said is 5.96mm.

                  Homing an axis means establishing a known position for that axis. That position does not have to be zero. But if it makes you feel better, then after the G30 command followed by M402 to retract the probe, you can send G1 Z0 if you wish (note: no S1) to lower the nozzle to touch the bed.

                  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
                  • chrishammundefined
                    chrishamm administrators @Sir printsalot
                    last edited by

                    @sir-printsalot said in inconsistant operation:

                    java script error remember gcode is not a function error {} 1153

                    applies settings button does nothing launches this error.
                    restore factory setting launches this error.
                    every button and and text field launches this error.

                    From my experience pressing "Apply Settings" will always restore the proper data type for the affected variable so I am surprised it is not working for you. Can you please try to clear the browser cache including cookies/storage for the printer and see if that fixes it (provided you are using DWC 1.22.1 of course).

                    Duet software engineer

                    1 Reply Last reply Reply Quote 0
                    • Sir printsalotundefined
                      Sir printsalot
                      last edited by

                      that buttom is optioned out. When I hover mouse over it it show cycle with line through unable to toggle button icon. Non of any of the fixes are either working or available on my installation. I am experiencing behavior other aren't, or the same without the option to correct. I'm not sure if it's a windows thing.

                      As far as the triggered height from bed during probing, it's .96 mm. nozzle is offset higher .96mm I don't know where the additional 5mm is coming from. I have never written a lift of 5mm. after g30. The 5mm lift starting is avoidance of bed edge, because x moves 20 mm wider than bed on neg side. if nozzle was lower than bed nozzle will hit bed edge. But after nozzle is centered where it homes z z0 is .96mm above and my safe z travel height. I have never written to raise a second time. It does anyway. Look at my homez and my homeall. Homeall z is the same as homez a far as z homing goes. But homez raises the extra 5mm zeroing z there and homeall leaves z at .96 and writes the correct height. My question is why are the treated differently if the z portions are the same. My thing is after a homing run regardless of where machine goes, the readout needs to be the correct measured value from bed and it is 5mm higher than it actually is. Printing 5mm of air. I have to lower and g92 to correct it is using my Homez.g but not for my homeall.g and they are the same routine. makes no sense and is inconsistent comparatively.

                      1 Reply Last reply Reply Quote 0
                      • Phaedruxundefined
                        Phaedrux Moderator
                        last edited by

                        What probe type are you actually using right now? P5, P7, P9? Perhaps it's returning to the dive height after a probe.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        1 Reply Last reply Reply Quote 0
                        • Phaedruxundefined
                          Phaedrux Moderator @Sir printsalot
                          last edited by

                          @sir-printsalot said in inconsistant operation:

                          java script error remember gcode is not a function error {} 1153

                          Can you try this?

                          Go to settings, List items, and delete all the entries in Default Gcodes, and hit apply.

                          Z-Bot CoreXY Build | Thingiverse Profile

                          1 Reply Last reply Reply Quote 0
                          • Sir printsalotundefined
                            Sir printsalot
                            last edited by

                            probe is bl touch smart brand named probe pin. dive hieght is current position z neg 299 mm relative. so no static value to return to. Im away til sat vacation atm. get back to u soon. thank you for all your help. there is a solution.

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