You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, I have been printing on my 3D printer using the stock BTT firmware, as this firmware isn't ready for full deployment yet. I noticed that the so called "salmon skin" issue was present, which manifests as diagonal lines in the print.
Further research concludes that the issue is caused by either electronic or mechanical issues. I know it's not mechanical because I've used other drivers in the past (TMC2130s) that haven't had an issue with "salmon skin". So that leaves electrical, which is caused by imprecise stepping routines. From the BTT code, we know that BTT didn't have their stepping process optimal. This is likely the cause of the issue, which shouldn't be present as the entire stepping routine was redone for mathematical correctness, readability, and most of all, speed. Still, I wanted to note it as a possible bug that we might need to look into.
The text was updated successfully, but these errors were encountered:
Recently, I have been printing on my 3D printer using the stock BTT firmware, as this firmware isn't ready for full deployment yet. I noticed that the so called "salmon skin" issue was present, which manifests as diagonal lines in the print.
Further research concludes that the issue is caused by either electronic or mechanical issues. I know it's not mechanical because I've used other drivers in the past (TMC2130s) that haven't had an issue with "salmon skin". So that leaves electrical, which is caused by imprecise stepping routines. From the BTT code, we know that BTT didn't have their stepping process optimal. This is likely the cause of the issue, which shouldn't be present as the entire stepping routine was redone for mathematical correctness, readability, and most of all, speed. Still, I wanted to note it as a possible bug that we might need to look into.
The text was updated successfully, but these errors were encountered: