# Snapmaker Original(PLA) after Using A350(PETG) starts at wrong temp **URL:** \ **Category:** Snapmaker Luban\ **Created:** [March 6, 2022, 2:54pm UTC](https://forum.snapmaker.com/t/snapmaker-original-pla-after-using-a350-petg-starts-at-wrong-temp/24708 "2022-03-06T14:54:39Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![tyeth](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/tyeth/32/19314_2.png) [@tyeth](https://forum.snapmaker.com/u/tyeth)\ **Post date:** [March 6, 2022, 2:54pm UTC](https://forum.snapmaker.com/t/snapmaker-original-pla-after-using-a350-petg-starts-at-wrong-temp/24708/1 "2022-03-06T14:54:39Z")
So I’ve been printing PETG at 240 (bed75) on the snapmker 2.0 A350, and I chose new project, then changed the machine settings to the Snapmaker Original, then it loaded back to start screen and I chose 3dp again and it appeared to load a new project (but could have behind the scenes left the same start gcode for A350 PETG). I changed to Raft bed adhesion, added the wheel-real model, chose Duplicate, chose Auto arrange (just fits). I changed the wall thickness and infill percentage, checked other settings but didn’t change, visually verified it was on PLA but didn’t change material. Then generated Gcode and exported to file. I sent this via octoprint because gcode generated has problems with temperature in comments due to mutliextruder (see other post). Running the gcode on octoprint I happened to glance at the temperature graph which showed a significant change, and it was actually dropping from 240/75 (PETG temps) to 200/50 (PLA temps). I then checked the gcode, it shows the start gcode setting temps at 240/75, and then later the gcode changes to PLA after layer 0/1. Project + model + gcode attached. Zipped with 7zip using deflate64 which may cause issues sorry, the 4mb limit got me for normal zip compression. [SOG-dual-mode-spring-motor-rolling-chassis-wheel-rear.zip](https://forum.snapmaker.com/uploads/short-url/j42mDh5tq5ChBvrMVUvM9NVWQv1.zip) (3.9 MB) ![image](https://us1.discourse-cdn.com/flex022/uploads/snapmaker/original/3X/8/1/81d4b2b5910f1156852961925f827a1c33f2249c.png) ![image](https://us1.discourse-cdn.com/flex022/uploads/snapmaker/original/3X/c/f/cfdddc24043af80b0cdd2fabcf5bdb05f6aa9225.png) ---
**Author:** ![Blauskink](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/blauskink/32/17834_2.png) [@Blauskink](https://forum.snapmaker.com/u/Blauskink)\ **Post date:** [March 6, 2022, 3:42pm UTC](https://forum.snapmaker.com/t/snapmaker-original-pla-after-using-a350-petg-starts-at-wrong-temp/24708/2 "2022-03-06T15:42:04Z")
don’t know if their error message is still processed with, since there was a window of 1-2 weeks from 22.02.2022 to report and discuss errors!? Here the original text (see marking) ![Unbenannt](https://us1.discourse-cdn.com/flex022/uploads/snapmaker/original/3X/9/6/969068dc70367ff2fc3f37f6aac96ae01697ffcc.jpeg) ---
**Author:** ![tyeth](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/tyeth/32/19314_2.png) [@tyeth](https://forum.snapmaker.com/u/tyeth)\ **Post date:** [March 6, 2022, 4:03pm UTC](https://forum.snapmaker.com/t/snapmaker-original-pla-after-using-a350-petg-starts-at-wrong-temp/24708/3 "2022-03-06T16:03:49Z")
A good point, I’ll duplicate it to github issues to be sure. ---
**Author:** ![Blauskink](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/blauskink/32/17834_2.png) [@Blauskink](https://forum.snapmaker.com/u/Blauskink)\ **Post date:** [March 6, 2022, 4:05pm UTC](https://forum.snapmaker.com/t/snapmaker-original-pla-after-using-a350-petg-starts-at-wrong-temp/24708/4 "2022-03-06T16:05:03Z")
Yes there I think it is seen times in any case! ---
**Author:** ![tyeth](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/tyeth/32/19314_2.png) [@tyeth](https://forum.snapmaker.com/u/tyeth)\ **Post date:** [March 6, 2022, 4:15pm UTC](https://forum.snapmaker.com/t/snapmaker-original-pla-after-using-a350-petg-starts-at-wrong-temp/24708/5 "2022-03-06T16:15:27Z")
I can’t seem to see another issue/example the same so if you have one in mind please link here. My created issue: > > > \# 🐞 bug report > > \### Affected Version(s) > 4.2.1 > > \### To Reproduce > Steps to r…eproduce the behavior: > 1. Start a 3dp project for the Snapmaker 2.0 A350 and select PETG. > 2. Add a model, generate gcode and export as file somewhere. > 3. Start a new blank 3dp project using the File Menu -\> New Project. > 4. Change machine settings to Snapmaker Original (Snapmaker OG / SOG) > 5. Witness Luban restart at welcome / examples screen. > 6. select 3dp option to load into blank project for snap OG. > 7. Verify PLA is selected visually but don't touch material settings. > 8. Add \*\*wheel-rear.stl\*\* > 9. Use Duplicate and witness one is out of bounds > 10. use Auto Arrange to squeeze both models onto bed. > 11. Adjust settings to wall size 1.5mm, infill percentage 30, bed adhesion from skirt to raft > 12. Generate gcode and export as file. > 13. Load file in favourite text editor and verify start gcode is wrong temp > > Exception or Error (optional) > Printing with octoprint the file started the first layer (layer number -6 which is raft) at PETG temperatures instead of PLA > > Expected behavior > File would contain start gcode using temperatures from Material selected on screen not whatever is cached. > > \## 🌍 Your Environment > > \*\*Platform:\*\* > \\ > > \- Operating System: \[Windows 11 x64\] > \- Printer: \[Snapmaker Original & Snapmaker A350\] > > \\ > > > > This is also in the private forum thread for the beta https://forum.snapmaker.com/t/snapmaker-original-pla-after-using-a350-petg-starts-at-wrong-temp/24708