Snapmaker / Luban

An easy-to-use 3-in-1 software tailor-made for Snapmaker machines.
https://snapmaker.com/snapmaker-luban
GNU Affero General Public License v3.0
439 stars 115 forks source link

Luban won't export gcode non-default settings for 3d prints #2440

Open EMTuckerLab opened 10 months ago

EMTuckerLab commented 10 months ago

🐞 bug report

Affected Version(s)

The issue is caused by version x.y.z ### Is this a regression? (optional) Yes, the previous version in which this bug was not present was: .... ### To Reproduce Luban will no longer export the settings I specify in the software and export them in the gcode file. It exports some settings, but not others - like the bed temperature. It will no longer export the bed temperature I specify despite supposedly saving in the settings panel. It would save and export the gcode fine previously, but for some reason has stopped functioning properly. I've tried restarting everything on both my computer and the physical machine, I've reset to manufacturer settings, and I've tried reinstalling the software. I even created custom material settings that have no ranges, just the settings I want exported - didn't stick. Nothing allows me to make setting changes in Luban and successfully export/generate the correct gcode. I basically can't print anything now unless the default settings work since I can't successfully export to gcode many changes. This is incredibly frustrating considering the expense of the machine. Steps to reproduce the behavior: 1. Go to 3d printing. Open any stl file. 2. Click on materials. Pick any color or make a custom. Change print bed temperature to 80. Exit out and reopen materials to make sure setting stuck. Confirmed. 3. Exit out of materials. Generate G-code. Export--> load g-code to workspace. 4. See error in preview which now says heated bed temp 65 (instead of 80 that it was set to) A clear and concise description of the problem... Exception or Error (optional)



Expected behavior

Expected settings like the temperature stipulated to be the same in the g-code generated from the same file and not go back to manufacturer settings.

🌍 Your Environment

Platform:



- Operating System:  macOS Ventura
- Printer: Snapmaker 2.0 A350T

EMTuckerLab commented 10 months ago

I just realized this appears to be a right nozzle/extruder issue - temperatures/settings for the left nozzle/extruder seems to correctly generate g-code. I have a dual extruder system.