@Nebur Yes, I see what you’re saying. But we use measurements of a side and the diagonals to calculate the parameter for In where they’re probably using the nominal value of the sides of a rhombus and measurements of the diagonals. So our results will differ for the Xn Yn method. Which is more accurate? I think our’s would be if we measure accurately.
EDIT:
BTW the length of side AD that I used in my calculations for the example I asked @EdStreet to try was 78.83
Bambu’s M1005 X Y command likely uses a simple form of linear regression to make the calibration easier for the user. I don’t think they’ve revealed to anyone what the exact calculation method is, but if we’re guessing, they use linear regression in every other calibration procedure so that would be a safe guess.
I think we all see the flaw with the “easy” method. The important thing is we know we’re using the correct units for the final skew values that are applied with the gcode command.
For x1plus users, a temporary solution for skew correction persistence: Modified syslog_shim.py
After overwriting this script in /opt/, save your skew value (units=radians) to a text file at /mnt/sdcard/skew.txt. Every time you reboot, the value you’ve saved in skew.txt will be applied. You can also see your skew values in /tmp/x1plus_data.log
I added a place in the UI to display and change the current skew factor. I just need to test it on my printer and then I can share it. I haven’t PRed it yet but I’m hoping to have it ready for 1.2
I get this, which is correct. Am trying to figure out how bambu is coming up with 0.00200 instead of 0.00250. Also I am wondering if that is large enough difference to show up in a print.