Just tested this. The answer is the save bug has been fixed. Here is what I did:
Publish M1005 I0.003\nM500 and then publish M1005 to confirm
Power cycle
Publish M1005 to see what value is saved on the printer
Also I tested to see if the value of comp_enable persists after reboot, and it does not. So it is a fairly useless setting to have atm
Thatās great. Thanks for checking that.
So with 01.08 if the skew correction is applied in the machine start gcode with:
M1005 In
M500
the gcode can then be removed and the XY_comp_ang will be retained when the printer is powered off.
yes, I only noticed this because I was printing functional models that needed to be accurate. When I lifted off plate I noticed what was like a brim but only to a single side (-X).
I printed a cube without changing anything and it was (-X, -Y) so the left side and rear had the first layer towards [LH] rear cornerā¦
I disabled skew factor and it was gone. Now after resetting the value and starting the skew calibration process from the beginning everything is once good again.
Iām currently running v01.08.00.00 so I can verify all the specific [M1005] codes indeed work but not able to verify if saved.
updated and good to go, thank you both for the help
Iām currently following this sequence, along with a [M1005 I0] @ [Ending Gcode] script
Iāve realized that this command for some reason accepts both P0/P1 and S0/S1 to change the value of comp_enable.
I was trying to figure out what the hell anyone would use this for and just now realized it - you want to home the printer without the skew correction applied, so this should (hypothetically, let me test it first) be placed at the beginning of print startup gcode:
M1005 S0 ; or P0
Then at the end of print startup:
M1005 S1 ; or P1
This seems like it could be a very important detail for anyone using relatively large skew factors. I need to do some testing before recommending anyone try this
Hey @Thermal_Runaway
Any update on testing this by chance?
I havenāt had a chance to yet. Iām out of town currently but Iāll share an update in a day or two
Has anyone applied the skew correction successfully on their P1S? I tried with the
M1005 X# Y#
M500
commands as per the PDF from some support interaction between Bambu and another user. I also saw that someone mentioned that P series FW are able to make sense of the M1005 command as well. I put it into my printer profile in Orca and ran a print but the measurements were exactly the same as before. I am currently trying it out with the XY Skew Factor Calculator spreadsheet and
M1005 I-0.003756, after resetting with M1005 I0.
/Edit: It didnāt work with that setting either. I still got the exact same measurements as before, meh. This doesnāt seem to do the trick for P1 printers or I did something wrong every time.
Hi @youwrote . See this post in this thread and the subsequent 7 posts, which includes a post where user @Acelya specifically asked Bambu Lab Support if the M1005 gcode command works on the P1 series. Bambu didnāt directly answer that question but said: āOur suggestion is to give it a tryāā¦
I canāt see anyone in this rather long thread of 450 posts confirming that it does in fact work on the P1S.
Did you add the gcode command at the end of your Machine start G-code?
Yes, I read those, thank you. I in fact skimmed the whole thread, which is why I also tried the M1005 I# method now. Yes, I added the command at the end of my machine start G-code. Although it shouldnāt make a difference, I also tried it in Bambu Studio instead of Orca Slicer. No luck, sadly. Thanks for your prompt reply! I might try getting in touch with support as well.
Also, thank you very much for this thread and all your efforts!
If you do get in touch with Bambu support on this issue please let us know their respose, to assist other users of the P1 series printers. Thanks.
I just opened a ticket and will edit this very post with the answer as soon as I get one.
/edit: I just got an answer to my ticket, see the screenshot attached. Again, they say that the M1005 command should work for P1 series printers. However, I have tried 5 times to date and am on the sixth run at the moment. No changes so far. Each calibration print has values of X120.05 and Y199.59 with deviations of around 10 to 30 microns on both axes.
/edit 2: I just tested again with X120.04 and Y117.54. Still no changes. Itās hard to believe that the G-code does anything on my P1S.
/edit 3: After more back and forth with customer support, who again confirmed the P1S firmware can make sense of M1005, they suggested to adjust the belt tension and further stated: āThere are inherent limitations to achieving precise dimensional accuracy, and itās essential to remember this when assessing sizing. Due to these intrinsic constraints, there may be a point where further adjustments yield minimal improvementsā. Since my adjustments didnāt yield any improvements, I might try fiddling with the belts again but atm I donāt see myself doing that. I did alot of work on the belts to minimize ringing/VFA while keeping the belt centered on the tensioning pulleys.
I hope this post was helpful to some and hope you have more luck!
My P1P is the same, I tried M1005 I-0.001838 and M1005 X119.8 Y119.58 M500 but nothing changed. Iām on the latest fw (01.06.00.00).
After a lot of failed tries with gcode I tried to set the belt tension with incremental spacers (0.5mm to 1.6mm) on the right side and the bambu test print did a 119,7mm 119,69mm.
Does anyone know that whether this skew correction works for A1/A1 Mini ?
I donāt think it does. I think it only applies to the X1.
Do we know that the latest info in this thread, for the X1C, still apply to 1.8.0.0 firmware? Iām still using M1005 I-0.001671 for 0.1Ā° or so, but havenāt verified it.
@the_Raz I think the 1.8.0.0 firmware now retains the correction factor when the printer is powered off so you shouldnāt need to keep applying it in the Machine start G-code if youāve saved it with M500 but I havenāt verified it yet because Iām not using 1.8.0.0
Perhaps some other users on 1.8.0.0 could verify this?
@youwrote Thanks for your follow up edits on this topic.
Hmm. Ok ready for another round of guess the settings?
before any change. I do not set or use M1005 and this is what it gave me.
Jul 14 20:56:32 info forward[1599]: [MCU][BMC]M1005:current XY_comp_ang = 0.00050
Using
M1005 I0.00023 yields this.
Jul 14 20:59:06 info forward[1599]: [MCU][BMC]M1005:new XY_comp_ang = 0.00023
reboot
looking at M1005 and the logs shows this.
Jul 14 21:01:47 info forward[1454]: [MCU][BMC]M1005:current XY_comp_ang = 0.00023
So yes it does save it and oh in case anyone missed it, I did NOT use M500 to āsaveā the values.
Slightly off topic but has anyone tried this?
https://github.com/olistrik/goskew
