Currently, we only received one issue report regarding this in the community. Could you please let me know your ticket ID so that I can let our support team to prioritize your request?
1 Like
Hello,
sorry, i send the email (548770) now i was busy printing,
thank you
@Janik This is a good question. However, Iām sorry that we have not yet made printing profiles dedicated for this Vibration Compensation firmware version.
- If youāre using the default settings in Luban with Vibration Compensation enabled, you wonāt need to change any other print parameters.
- If you want to push the print speed to the limitāeither by adjusting Luban or using third-party softwareāthen itās recommended to increase the nozzle temperature by about 10Ā°C. Also, keep an eye on the minimum print time per layer (ideally 6-8 seconds). If you notice any issues with overhangs or corners, you may need to tweak the firmware K-value.
1 Like
Hi everyone. I have a simiar issues with layer shifts on Y-axis as described by
- Vibration Compensation Firmware Open Beta for 2.0 Series (A/AT/F Models) - #86 by takeota
- Vibration Compensation Firmware Open Beta for 2.0 Series (A/AT/F Models) - #57 by Luk3D
It seems to be a bit unpredictable, I can run some prints at high speeds (120 mm/s) with the new firmware with good results and others with the same settings show the layer shifts. If I run slower (max 100 mm/s) everything is fine again. So some steps are skipped by the bed. I have a Snapmaker 2.0 350T, single extruder. Is this just a limit of my individual machine or is this something which can be addressed by the firmware itself?
1 Like
Hi Jade! I wanted to test the new firmware as well. After solving the issue with my noisy linear rails- I still have issues printing some benchy properly. 20mm Lead Axis and Single extruder. I have a little more stronger Cooling Fan. I ran trough the compensation tuning but it seems Iām getting really heavy under extrusion problems that Iāve never occurred before. My E Steps & K value are also calibrated
Still
I think you are printing too hot and maybe your filament is wet.
If you roll the firmware back, is it a different behavior?
1 Like
Thats why I used different filaments. Grey went to the Dryer before and while printing, the mint green was a complete new Spool out the box. Both printed at 195 degree
Firmware rollback might sound like a good idea. Having inconsistencies since months and canāt find the root issue
Maybe its to cold. With my Prusa Mini my standard Temp is 220 and 230 in first layer. With Inputshaper and Speed profile. I cant print with lower temperature without skipping e steps.
It seems to be something speed firmware unrelated. I tried with the standard software and the lines are still not 100% consistent.
I will open up a thread for this.
Did anyone else noticed a bigger fluctuation of the Printing temperature? Mine is Ā±2deg swinging around 200deg while printing.
Here is another user with layer shifts using simplify3d:
1 Like
Iāve read through this and the previous thread, and didnāt find my answer so apologies if Iām asking for something already available.
What is the status of open sourcing the vibration compensation firmware? I see @Mayco had previously asked for it, and @Riskey had said they would eventually release it, but that it seems they were not yet ready to open source it at the time. I donāt see any further updates after that.
Now that the vibration compensation firmware is considered stable, perhaps itās time to release thee source.
Reminder that Marlin is licensed under GPLV3 so you must release your modifications to the code: Marlin/LICENSE at bugfix-2.1.x Ā· MarlinFirmware/Marlin Ā· GitHub (also, youāre technically already in violation of the license given that any binary release must be accompanied by full source code release and youāve been releasing binaries for a while now.)
3 Likes
Sorry I am just now getting back into this thread.
Right after the bball print in July, I printed a full Y-scale cylinder tower. No issues of shifting noted.
I may pursue xchrisdās line of thought, perhaps after a couple tests of the newest beta FW. I havenāt really kept up on the updates here so I should probably review.
Hi, I believe the Jerk setting is crucial for resolving Y-axis layer shift issues. While it might add a little to the print time, setting it around 5 is kinder to the printer.
There might be a decision process in progress about way of releasing the vibration compensation firmware as main branch for every snapmaker.
Iām asking them to consider a flip switch - to enable or disable the tech instead of making it the only available option. So it might be that open source of it will happen after thisā¦ Who knows.
100% with you on licensing issues.
GPL doesnāt really care what your process is. If theyāre distributing binary files, they must distribute source code.
They donāt have to put it on GitHub or make it particularly easy for anyone to look at (GPL says they can just drop a zip over on an FTP server or something), but itās a violation for them to distribute a binary (e.g. post the binary on these forums) while not distributing the source used to build that binary (e.g. every post containing a binary should also be containing a source code link, if they want to have a mirrored GitHub repo with tags that they can link to, thatās great, but they must at least link e.g. just a zip file of the source code used to build that binary code).
Iām not trying to be mean about it (and itās not like I actually have any plans of legal action), itās just the terms of the license that theyāre bound to. Iām a developer myself and know how at least our legal team is deathly afraid of GPL. If you use any GPL code in your project, you need to make sure you keep it properly isolated from other code to ensure that the copyleft mechanism canāt be used to force your team to open source proprietary IP (there are many ways to do this, I see that the SM team has been moving more of their code into the HMI which doesnāt seem to use GPL code as a base, but any Marlin modifications they make are, unfortunately for them, bound by the license).
1 Like
tell this to bambu 
we all know how this work, but as individuals have little power to enforce this. The sole biggest issue with open source - is no united force of enforcementā¦
All this off topic thoā¦
1 Like
I mean, one simple way to try and force them to comply is for the community to keep pushing for compliance. If the forums were just full of āweāre not talking till you release the sourceā, the company either dies (since no one wants a product that has no community) or they release sources and we all happily go back to an engaged and thriving community.
Hi! Iām also trying to get into Orca Slicer but using the single extrusion module. Can you share your profile/ settings for Orca?
Currently trying to troubleshoot my printer
There are built in profiles in Orcaā¦ Use those. They came from MacDylan.
1 Like