1. Got a question or need help troubleshooting? Post to the troubleshooting forum or Search the forums!

Unresolved Z-Axis not moving suddenly

Discussion in 'Troubleshooting' started by TheRealDarthGuy, Feb 14, 2021.

  1. TheRealDarthGuy

    TheRealDarthGuy New Member

    Joined:
    Feb 12, 2021
    Messages:
    17
    Likes Received:
    1
    Hello all, I have an R1 and was able to print 10 or so items perfectly. Then out of the blue the printer refuses to raise up to any z-step but the first one. I thought it was possibly a bad file or something but went back to files that I've printed before and it results in the same. After about 5 days of searching and trying misc things that I'm unsure would be the right path giving the community a try. Thanks for the help. I'd love to be able to print again.
     
  2. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    Can you manually (from a host program or the LCD if you have one) raise the Z higher than that? I mean do it from the software, not by physically turning the rods.

    With a host program connected are you getting any errors back in the GCode terminal? Your best bet is to connect to the printer and generate the problem (run it until the faliure). Then export/save the entire GCode terminal output into a text file using Notepad or something similar. Then search for the word "error"
     
  3. TheRealDarthGuy

    TheRealDarthGuy New Member

    Joined:
    Feb 12, 2021
    Messages:
    17
    Likes Received:
    1
    Went ahead and ran another failed print. The text file generated is too large for here but there was only one error in the file and it was:

    Code:
    <-planeNormal x: -0.00 y: -0.00 z: 1.00 [315.855]
    
    <-ok [315.855]
    
    <-echo:endstops hit:  Z:0.51 [315.855]
    
    <-Error:Line Number is not Last Line Number+1, Last Line: 522 [315.855]
    
    <-Resend: 523 [315.855]
    
    <-ok [315.855]
    
    ->N523 M105*35 [315.870]
    Not sure if this helps at all.
     
  4. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    Not what I was looking for but this happens to be in there by happenstance :


    <-echo:endstops hit: Z:0.51 [315.855]

    which means that it thinks it hit Z home.

    If that was at any point other than when you told the printer to HOME (G28 command) then that is likely your problem.

    Perhaps take a look at this video and pay attention to how the Z switches are mounted in their brackets and snugged up tight to the crossbar. One of them may be knocked out of position or turned sideways and triggering incorrectly/prematurely.

     
    #4 mark tomlinson, Feb 14, 2021
    Last edited: Feb 14, 2021
  5. TheRealDarthGuy

    TheRealDarthGuy New Member

    Joined:
    Feb 12, 2021
    Messages:
    17
    Likes Received:
    1
    Yep followed that video a few times in exhausting detail. Lol... went ahead and watched/followed along again just to be safe and here are the results of a G29:

    Code:
    <-Bed x: 15.00 y: 20.00 z: -0.02
    <-Bed x: 107.00 y: 20.00 z: 0.02
    <-Bed x: 199.00 y: 20.00 z: -0.04
    <-Bed x: 200.00 y: 130.00 z: -0.11
    <-Bed x: 108.00 y: 130.00 z: 0.06
    <-Bed x: 16.00 y: 130.00 z: 0.08
    <-Bed x: 15.00 y: 240.00 z: 0.50
    <-Bed x: 107.00 y: 240.00 z: 0.41
    <-Bed x: 199.00 y: 240.00 z: 0.30
    <-Eqn coefficients: a: -0.00 b: 0.00 d: -0.03
    <-planeNormal x: 0.00 y: -0.00 z: 1.00
    <-ok
    <-echo:endstops hit:  Z:0.30
    <-X:199.00 Y:240.00 Z:0.00 E:0.00 Count X: 199.00 Y:240.00 Z:0.30
    <-ok
    Any valuable information in here?
     
  6. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    Not really, G29 is invoking the autoleveling and I expect the

    <-echo:endstops hit: Z:0.30

    as a part of that. My concern was that you were seeing the Z endstop hit at a point where it should not be.

    If it only happens with the G28 or G29 then not a problem.
    Probably need an answer on that before I can dig into it much further :)

    So far we know that HOME (G28) and probably AUTOLEVELING (G29) work as expected.

    Try this in a terminal:

    G91;
    G1 Z50;


    Does the Z raise the 50 mm it is commanded?
     
  7. TheRealDarthGuy

    TheRealDarthGuy New Member

    Joined:
    Feb 12, 2021
    Messages:
    17
    Likes Received:
    1
    Moves fine with that command.
     
  8. TheRealDarthGuy

    TheRealDarthGuy New Member

    Joined:
    Feb 12, 2021
    Messages:
    17
    Likes Received:
    1
    Everything "seems" to be moving fine. Either by commands or using software (I know it just sends commands too). Just stops doing it correctly when trying to print. I've flashed the firmware a time or two as well. I've actually tried all of the different versions I could find of firmware and then went back to the "suggested" one from within MatterControl. I've also tried to print from Cura with the same "no z-axis progression" result.
     
  9. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    This is not a firmware issue or the G1 Z50 would have failed.
    Please make sure out of the firmware updating that you did in fact load the correct version (which can be confusing with how Robo named them) or you will only deal with more problems later.

    This is almost certainly a slicer issue. If mechanically and electrically it can move to the correct position and via GCode then it can move as needed ... and the slicer must be generating bad Gcode or you are getting an error. If you have validated no errors ... bad GCode is all that is really left.
     
  10. TheRealDarthGuy

    TheRealDarthGuy New Member

    Joined:
    Feb 12, 2021
    Messages:
    17
    Likes Received:
    1
    Is there a way to "validate" G-Code? I've poked around in MatterControl and found the "Custom G-Code" section in settings. Here's what's listed in there (not sure if it helps at all):

    Start G-Code:

    Code:
    G28 X0 Y0 Z0 ; home all axes
    G1 Z5 F5000 ; lift nozzle
    M109 S[temperature] ; set the extruder temp and wait
    G28 X0 Y0 Z0 ; Home Z again in case there was filament on nozzle
    G29 ; probe the bed

    End G-Code:

    Code:
    M104 S0 ; turn off temperature
    G1 X10 Y200
    M84     ; disable motors
    Tool Change G-Code: blank
    Pause G-Code: blank
    Resume G-Code: blank

    Cancel G-Code:

    Code:
    G28 X0

    On Connect G-Code:
    blank
     
  11. TheRealDarthGuy

    TheRealDarthGuy New Member

    Joined:
    Feb 12, 2021
    Messages:
    17
    Likes Received:
    1
    When I did the firmware update I had an old version installed and MatterControl suggested (and auto loaded) firmware in the Settings > Controls > Firmware Updates section. Currently it says ROBO3DR1V3 as the firmware version.
     
  12. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    Well, what do you mean by validate?

    There are programs to check the syntax of the GCode and some that can simulate the printing.

    example: https://gcode.ws/

    you use the vertical slide bar to show you the layer-by-layer print

    The Starting and ending GCode blocks you have posted are fine.


    Never trust the programs to tell you the correct version of the firmware. It probably can't really tell if you have the R1 o the R1+ and yet -- they have completely different firmware and loading the incorrect one is bad.

    R1+ firmware:
    https://help.robo3d.com/hc/en-us/articles/115000717071-Updating-firmware-with-Arduino
    (look for the R1 + link)

    Older R1 firmware:
    https://help.robo3d.com/hc/en-us/articles/115000723672
     
  13. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    All that aside -- this is not a firmware issue since you proved it works entering the manual GCode commands earlier. It CAN lift as much as 50mm at least :) If it is not then the slicer is not telling it too (or there is an error in your GCode which is why I wanted you to look through the terminal for any errors).
     
  14. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    Best bet MIGHT be to try another slicer :)
    Among the free ones you may not have yet tried:

    Repetier Host
    Kisslicer

    I can't advise you one any one in particular. I haven't used any of them in a long time, but at least try something other than you have already. Just configure them for the printer axis sizes and style and you should be fine.
     
  15. TheRealDarthGuy

    TheRealDarthGuy New Member

    Joined:
    Feb 12, 2021
    Messages:
    17
    Likes Received:
    1
    Sounds great! Running some tests and I'll get back once I try a few more things. I managed to get a clog so I have to deal with that before I can proceed but I'll keep at it trying until I can get things to print.
     
  16. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    If it reproduces across all the slicers then something somewhere is failing and/or generating an error that we need to capture/find :)
     
  17. TheRealDarthGuy

    TheRealDarthGuy New Member

    Joined:
    Feb 12, 2021
    Messages:
    17
    Likes Received:
    1
    New information... Attempted configuration circle in MatterControl and got errors. This repeats quite a lot...

    Code:
    ->N184 M105*4 [147.029]
    
    <-ok T:209.2 /210.0 B:51.0 /50.0 T0:209.2 /210.0 @:77 B@:127 [147.029]
    
    ->N185 M114*43 [147.044]
    
    <-Error:Line Number is not Last Line Number+1, Last Line: 184 [147.045]
    
    <-Resend: 185 [147.045]
    
    <-ok [147.045]
    
    ->N185 M114*4 [147.060]
    
    <-X:199.00 Y:240.00 Z:-0.00 E:0.00 Count X: 199.00 Y:240.00 Z:0.17 [147.060]
    
    <-ok [147.060]
    
    <-Error:Line Number is not Last Line Number+1, Last Line: 185 [147.075]
    
    <-Resend: 186 [147.076]
    
    <-ok [147.076]
    
    ->N186 T0*53 [147.091]
    
    <-echo:Active Extruder: 0 [147.122]
    
    <-ok [147.122]
    
    ->N187 G90*30 [147.137]
    
    <-ok [147.153]
     
  18. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    <-Error:Line Number is not Last Line Number+1, Last Line: 184 [147.045]

    Usually just a communications glitch between the computer and the printer.
    Make sure you are using a new, high quality USB cable and you should be fine.


    Seriously though -- bad USB cables are a thing for the printer :)
     
  19. TheRealDarthGuy

    TheRealDarthGuy New Member

    Joined:
    Feb 12, 2021
    Messages:
    17
    Likes Received:
    1
    Ok, after a new USB cable... I was able to print about 5 things last night with success and only a few failures to raise the z-axis. I was able to get successful prints by doing a dance of unplug the printer, clear out the MatterControl queue, turn off the printer, close MatterControl, then re-setup everything. This morning it's failing again on multiple prints.

    When monitoring the z-axis in MatterControl the software seems to believe that it's raising up but the printer is not.

    I'm honestly at a loss as to why it works "sometimes" and not others.
     
  20. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    Have you tried a different host program than MatterControl?
     

Share This Page