No I am not. I commented this out to not have to do g29 each print. It worked great.
Printable View
No I am not. I commented this out to not have to do g29 each print. It worked great.
Well I'm utterly lost. I don't think I understand what you've told your printer to do enough in order to help figure out why it's not doing what you tell it to do.
Sorry, I started this a few days ago over in a different thread. What's happening in brief is that after I adjusted the z offset on a viki lcd the machine is acting up. It was working perfectly before, but I am not certain if the lcd offset change is in anyway related, it may well not be
but after I hit the offset change here is what it is doing.
After G28, G29 the z endstop (which is triggered at the last abl position) is triggering (not showing on M119) the x and y stops. So if you hit x home after the g29 x will not travel towards the x home switch, it will move away. If I raise z so the z endstop is not triggered anymore, x travels home fine and bounces of the stop as normal. If I trigger the z endstop while x is moving to its home position, x will bounce of that location. In other words, where ever on the bed z stop is triggered, the machine thinks x & y are home. Even though an M114 shows the right coordinates. I also have to say that every once in a while, when I hit x home with the machine being at the last abl point , x will travel to its home position, without a bounce.
I got the matrix deletion turned off in marlin main g28, but that was turned off before when it all worked perfectly.
Other than that it's a pretty normal fw.
Sounds like it might be profitable to start from a completely fresh firmware file. Make only your necessary adjustments for your printer, then if it still happens, it may be a hardware issue.
MiniMadRyan, do you have an LCD Panel on your printer? Can you turn it off and see how it behaves?
I think you do have one??? I see this line in your Configuration.h file:
#define REPRAP_DISCOUNT_SMART_CONTROLLER
We definitely don't have enough facts to conclude this yet. But it almost feels like something changed in the main Marlin code base that makes LCD Panels have trouble and act flakey. If this is true, it will get fixed, but until it does, you probably don't want to use your LCD Panel for important things. And one of the problems is the LCD Panels are all supported by the companies that make the panels. It might take a while for them to get things back to where they should be.
In the short term, can you turn off the LCD Panel and see how your printer behaves? If the problem goes away, it might be worth while calling up the support line for your LCD Panel and see if they are hearing other reports of bad behavior.
I don't know the answer. I don't have an LCD Panel so I haven't looked much at that code. I did write some stand alone routines to fake out a LCD Button Click so I could leverage and use the LCD Panel Filament change. But that is the extent of my LCD Panel knowledge. I did look at how they make things move using an LCD Panel and they are stuffing GCode commands into the command buffer. I'm not entirely comfortable with that approach. And sure enough, people with LCD Panels are starting to have unpredictable behavior of their Printers.
If I was going to bet, I would bet that unplugging your LCD Panel and commenting out the code for it will be successful. And that is just based on the fact that everybody with this weird behavior has an LCD Panel. We won't know until you get that done and have a chance to mess around with your printer.
I did test and try it without the LCD and yes I agree with you to start with a new/clean firmware, and that is exactly what i have done. I will be trying this again when I am back next weekend. But the last tests over the last four days did not show any difference
with or without LCD. What's really weird is that I am having a similar issue with another machine now. As if my pc is causing it.
Please send all your suggestions and stuff my way I try asap.
I am 3d printing since 4year and have never come across something quite like that, a working machine and fw, suddenly acting differently repeatably.
I have an LCD on my machine, and haven't experienced these oddities. Though lately I have been running almost exclusively from my OctoPi setup. I cannot recall the last time I printed from the LCD's SD card, or even twiddled the knob.
I just downloaded today's EZ Marlin update and copied over the changes to my local file. All there was was a new comment about commenting out a line I already had commented out.