My "2 Wifi" is un-baby-stepping
-
@phaedrux I don't use mesh compensation, doesn't seem to be needed.
My machine is a work in progress, so, I do a lot manually.
Machine turns on, I home the axes. Then I run the 4 point auto bed level, it's configured to run twice. I double check that Z0 is actually at 0, my bed is built like crap, so it can flex, causing the end stop to not always register at the exactly correct height. If I need to, I manually creep the bed up to the nozzle and G92 Z0. The bed flex isn't enough to cause these problems. Once it's dialed in, the Z position is reproducible.
I'm guessing the axis skew compensation came with the default config. I didn't add it.
-
@gnydick said in My "2 Wifi" is un-baby-stepping:
M566 X750 Y750 Z150.00:150.00:150.00:150.00 E120:120 ; Set maximum instantaneous speed changes - jerk (mm/min) M201 X1000.00 Y1000.00 Z300.00:300.00:300.00:300.00 E120:120 ; Set accelerations (mm/s^2)
Both your jerk and you accel on Z seem a bit high to me. I started out with TR8x8 lead screws as well and used (maybe a bit conservative) 100mm/s² accel and 30mm/min jerk. Have you tried lowering these values?
-
@wilriker it is not a jerk or acceleration issue. I feel like nobody reads what I'm posting.
The bed moves in the direction of the baby steps, then some time later, moves back. Could be a split second, could be a full second.
-
@gnydick I didn't say that this is the cause of your issue. I just said that's the part I felt could need some reconsideration or checking - they might also be totally fine.
-
@wilriker if it had nothing to do with my issue, why did you ask if I tried lowering them?
-
@gnydick I did not say either that this has nothing to do with it. Just looking for oddities. I have read your posts, I have watched the videos you posted. Right now I only try to establish a baseline.
Just an idea: you are the first one I see here that has four Z motors (there might be others but I haven't seen them so far). Most people have one, two or three. Does your mechanical setup permit reducing the number of Z motors? It might be something special there. Again, just guessing.
-
@wilriker thanks. I've run with 2, 3, and 4. It's all the same symptoms.
-
@gnydick said in My "2 Wifi" is un-baby-stepping:
I double check that Z0 is actually at 0, my bed is built like crap, so it can flex, causing the end stop to not always register at the exactly correct height.
if your bed flexes that much it will also flex while heating. that could be the cause that after cooldown it gives you a different distance.
-
@gnydick There are a few anomalies in your config.g file. I can't off hand see why any of them would have an impact on your problem but as you seem to be the only one who is experiencing this problem, there might be an as yet undiscovered bug that only raises it's ugly head when one or more of these anomalies is present. So here is what caught my eye as it were.....
If you are using the firmware 203 and later, then M667 is deprecated and you should be using M669 instead.
M569 motor directions - you have only defined the direction for 5 motors yet you are using 8. As the machine is otherwise working as it should, then it's a fair bet that the default motor direction happens to be right but I would explicitly define the motor directions for all motors if I were you.
In your M92, M350, M203, M566 you use the format Znn:nn:nn:nn. But these commands refer to axes not motors so simply using Znn is all that is needed. Hopefully the additional comma separated values are simply being ignored but you never know.....
This next one hasn't yet bitten you in the backside but it might when you come to use the second tool. You have set micro stepping to 8X for one extruder but not the other. If that wasn't deliberate on your part and if the intention is to use the same micro stepping for both extruders, then this is a case where you need to use a colon to separate the extruders. Edit - I just noticed that you haven't defined the steps per mm for the second extruder either so I guess you just haven't got around to it yet in which case, just ignore this paragraph.
As @Phaedrux has said, you aren't using mesh compensation so comment out the M367. Likewise M556, orthogonal axis compensation.
In theory, none of the above should have any impact on your problem but then again, no one has as yet found an answer, so it might be worth just trying.
-
@deckingman thanks. Yeah, the different tool settings are intentional.
Given the behavior I'm having is very specific, I would also doubt the config things, but I'll fix them up and see.