# Discussion of Snapmaker 2.0 Firmware Updates

**URL:** <https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441>\
**Category:** Snapmaker 2.0 (3-in-1)\
**Created:** [February 27, 2020, 6:39am UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441 "2020-02-27T06:39:15Z")\
**Posts on this page:** 20\
**Page:** 34

<div class="post-metadata">

**Author:** ![KPeterW](https://avatars.discourse-cdn.com/v4/letter/k/73ab20/32.png) [@KPeterW](https://forum.snapmaker.com/u/KPeterW)\
**Post date:** [May 20, 2023, 4:42am UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/677 "2023-05-20T04:42:52Z")

</div>

Updated the firmware of my Snapmaker A350 to latest version - 1.15.26. Loaded a 3D model and the screen said build would take 2 hours 53 minutes. In Luban it said 1 hour 28 minutes. Also the size of the model displayed was wrong. Changed the firmware back to the previous version 1.15.23. The model dimension display correctly as well as the time. This was for a single extrusion header. Somewhere in the firmware the dimensions and times of models loaded are not correct. Suggest not taking the latest firmware until bugs have been fixed.

---

<div class="post-metadata">

**Author:** ![nweolu](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/nweolu/32/23079_2.png) [@nweolu](https://forum.snapmaker.com/u/nweolu)\
**Post date:** [May 21, 2023, 2:18am UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/678 "2023-05-21T02:18:27Z")

</div>

@Riskey , how come touchscreen is not notifying about limited storage to accept updates?

> **[Log into Facebook](https://m.facebook.com/groups/snapmaker/permalink/1709202772831362/)**
>
> Log into Facebook to start sharing and connecting with your friends, family, and people you know.

Another thing I’ve noticed recently, if you plug in a USB drive with corrupted file system - touchscreen crashes. Guess it’s trying to mount unmountable…

---

<div class="post-metadata">

**Author:** ![Wyphorn](https://avatars.discourse-cdn.com/v4/letter/w/ebca7d/32.png) [@Wyphorn](https://forum.snapmaker.com/u/Wyphorn)\
**Post date:** [May 21, 2023, 6:08am UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/679 "2023-05-21T06:08:09Z")

</div>

I did some Abs prints yesterday with the dual (Just one material, so just left Nozzle) and i had to cancel two prints. Third attempt the right nozzle was to low and Always removed the lines left nozzle printed so far. So i had to control manually, right nozzle went up again and i was able to start print then.  
Would be fine when luban Just add right nozzle up on single nozzle print.

---

<div class="post-metadata">

**Author:** ![nweolu](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/nweolu/32/23079_2.png) [@nweolu](https://forum.snapmaker.com/u/nweolu)\
**Post date:** [May 21, 2023, 4:36pm UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/680 "2023-05-21T16:36:59Z")

</div>

### New Features 1.15.26

- Added “C” and “W” custom parameter support with “M109” G-code

Nothing in g-code reference, what is it about?

---

<div class="post-metadata">

**Author:** ![Shamalama](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@Shamalama](https://forum.snapmaker.com/u/Shamalama)\
**Post date:** [May 22, 2023, 12:09pm UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/681 "2023-05-22T12:09:00Z")

</div>

It would be nice if snapmaker added the ADVANCED\_PAUSE\_FEATURE for M600, so that we can change filament for both extruders. I know it is not available Luban but why not add the feature set so we can use the Parameters if we use different slicer like Cura. This will allow for more creative 3D prints, thought that was what the dual head extruder was released for.

---

<div class="post-metadata">

**Author:** ![John\_Petrucci78](https://avatars.discourse-cdn.com/v4/letter/j/9d8465/32.png) [@John\_Petrucci78](https://forum.snapmaker.com/u/John_Petrucci78)\
**Post date:** [May 22, 2023, 1:52pm UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/682 "2023-05-22T13:52:22Z")

</div>

The new update 1.15.26 has brought issues with parsing the file, taking too much time. Furthermore, the displayed time is completely wrong, doubled. Please resolve this problem.  
@Riskey

---

<div class="post-metadata">

**Author:** ![John\_Petrucci78](https://avatars.discourse-cdn.com/v4/letter/j/9d8465/32.png) [@John\_Petrucci78](https://forum.snapmaker.com/u/John_Petrucci78)\
**Post date:** [May 22, 2023, 1:54pm UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/683 "2023-05-22T13:54:57Z")

</div>

Even when attempting to print, the temperature settings in the old G-code files no longer work.

---

<div class="post-metadata">

**Author:** ![nweolu](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/nweolu/32/23079_2.png) [@nweolu](https://forum.snapmaker.com/u/nweolu)\
**Post date:** [May 23, 2023, 1:35pm UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/684 "2023-05-23T13:35:07Z")

</div>

@Snapmaker-Support @Edwin @Riskey @Jade @Sharon666 @Alan @parachvte @whimsycwd

Guys, is it really a burden to you to keep an eye on your community and have at least someone acknowledging issues here? Not only in this thread.

Or should will all just flood the [support@snapmaker.com](mailto:support@snapmaker.com)?

---

<div class="post-metadata">

**Author:** ![Riskey](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/riskey/32/20010_2.png) [@Riskey](https://forum.snapmaker.com/u/Riskey)\
**Post date:** [May 24, 2023, 9:43am UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/685 "2023-05-24T09:43:04Z")

</div>

Hi nweolu,

Our technical support colleagues are more experienced in handling different issues, and their efficiency in solving problems will be higher. Therefore, if you encounter any problems, please [submit a ticket](https://snapmaker.formcrafts.com/support-ticket) first. Our colleagues will assist you as soon as possible. A centralized issue receiving system is also more conducive to us identifying key issues, and then evaluating whether to allocate resources to focus on solving them. Of course, you can also post it on the forum at the same time to see if other users have any solutions.

---

<div class="post-metadata">

**Author:** ![Hauke](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/hauke/32/5704_2.png) [@Hauke](https://forum.snapmaker.com/u/Hauke)\
**Post date:** [May 24, 2023, 12:38pm UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/686 "2023-05-24T12:38:11Z")

</div>

Thanks for the clarification! It helps to put the forum into perspective. In howfar the issue tracker on github is monitored? Does it make sense to file issues/bugs there?

---

<div class="post-metadata">

**Author:** ![nweolu](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/nweolu/32/23079_2.png) [@nweolu](https://forum.snapmaker.com/u/nweolu)\
**Post date:** [May 24, 2023, 1:10pm UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/687 "2023-05-24T13:10:11Z")

</div>

Thank you @Riskey , your reply is much appreciated.  
It is the first time I actually hear about ticketing system - great job. We shall spread the word 🙂

I understand this would sound like wining and this is not a place for this offtopic, but it would be an underestimate to say that collective thought out the community is as snapmaker doesn’t care about their clients/fans. Letting people know that there is a ticket system, and provide guidance on how to efficiently file a ticket to help both side save time is the very least you can do.

I’ll go ahead and submit a ticket for \*\*\* Added “C” and “W” custom parameter support with “M109” G-code\*\*

> [@Hauke](#):
>
> Thanks for the clarification! It helps to put the forum into perspective. In howfar the issue tracker on github is monitored? Does it make sense to file issues/bugs there?

This is great point too, since those can be very efficient (if filed properly) for the devs to solve.

---

<div class="post-metadata">

**Author:** ![macdylan](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/macdylan/32/18460_2.png) [@macdylan](https://forum.snapmaker.com/u/macdylan)\
**Post date:** [May 24, 2023, 1:58pm UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/688 "2023-05-24T13:58:22Z")

</div>

`M109 S190 C3 W1`, wait for the temperature to 190, within 1 second to detect the temperature within the range of ±3 will directly pass. Without these parameters, PID would up to 200 before passing.

---

<div class="post-metadata">

**Author:** ![nweolu](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/nweolu/32/23079_2.png) [@nweolu](https://forum.snapmaker.com/u/nweolu)\
**Post date:** [May 24, 2023, 2:01pm UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/689 "2023-05-24T14:01:40Z")

</div>

Great answer, thanks! Guess you did @Riskey job here:)  
Would be nice to see the quality assurance people from snapmaker making sure these details make their way into docs before they deliver software.

---

<div class="post-metadata">

**Author:** ![Riskey](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/riskey/32/20010_2.png) [@Riskey](https://forum.snapmaker.com/u/Riskey)\
**Post date:** [May 25, 2023, 2:25am UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/690 "2023-05-25T02:25:27Z")

</div>

Thank you for your question. Our developers do monitor the issue tracker on GitHub, but we recommend submitting a support ticket first if you encounter any problems. If the issue is a common one, this way will likely result in a faster response.

---

<div class="post-metadata">

**Author:** ![Burgerboy](https://avatars.discourse-cdn.com/v4/letter/b/0ea827/32.png) [@Burgerboy](https://forum.snapmaker.com/u/Burgerboy)\
**Post date:** [May 25, 2023, 1:07pm UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/691 "2023-05-25T13:07:40Z")

</div>

Can the supporting documentation be updated? If you are doing sprints, then add a task that says sprint isn’t complete until customer facing documents are updated and scheduled for release

[https://snapmaker.github.io/Documentation/gcode/M109](https://snapmaker.github.io/Documentation/gcode/M109)

Assuming I’m looking at the correct location

---

<div class="post-metadata">

**Author:** ![Hauke](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/hauke/32/5704_2.png) [@Hauke](https://forum.snapmaker.com/u/Hauke)\
**Post date:** [May 28, 2023, 7:56pm UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/692 "2023-05-28T19:56:54Z")

</div>

The newest 1.15.26 now issues a warning if the GCode contains retractions of more than 2 mm - unfortunately you can’t disable that. Will write a ticket on that…

---

<div class="post-metadata">

**Author:** ![takeota](https://avatars.discourse-cdn.com/v4/letter/t/7ab992/32.png) [@takeota](https://forum.snapmaker.com/u/takeota)\
**Post date:** [June 3, 2023, 3:20pm UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/693 "2023-06-03T15:20:03Z")

</div>

I suspect that there is a critical bug in the latest firmware 1.15.26.  
When trying to print with dual extruders and using materials with different temperature settings, the start Gcode M104 is not recognized properly and the tool may not be able to heat up. (Printing starts without heating)  
By reverting the firmware to 1.15.23, the same Gcode could be used without problems.

The code described is nothing special.  
Example:  
;TYPE:Custom  
M82 ;absolute extrusion mode  
;Start GCode begin  
G28 ;home  
M104 S270 T0 ; Preheat left extruder  
M104 S220 T1 ;Preheat right extruder  
M140 S100 ;Start Warming Bed  
M109 S270 T0 ; Wait for left extruder  
M109 S220 T1 ; Wait for right extruder  
M190 S100 ;Wait for Bed Temperature  
G90 ;absolute positioning  
G0 X-10 Y-10 F3000  
G0 Z0 F1800

---

<div class="post-metadata">

**Author:** ![Blockmodule](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/blockmodule/32/11177_2.png) [@Blockmodule](https://forum.snapmaker.com/u/Blockmodule)\
**Post date:** [June 4, 2023, 9:31am UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/694 "2023-06-04T09:31:32Z")

</div>

Do not think that you can safely use Snapmaker firmware even if a newer version is released.

In our experience over the years, some problems occur with every version release.

If you are going to use a new version, you need to be your own experimenter and face the glitches.

Snapmaker, unlike ordinary hardware manufacturers, is not responsible for the firmware that is released.

If there is a problem, there is no apology for it.  
Please remember that you are the experimenter. Snapmaker is not responsible for the firmware it releases, unlike ordinary hardware manufacturers

I forgot to mention that Snapmaker Luban has the same concept.

When there is some kind of program update, a different problem occurs.

Was there ever a version that worked without any problems at all?

Any property damage to the machine caused by a firmware or Luban defect will not be immediately addressed.

Of course, there is no announcement.  
Therefore, there are victims every time.

As I have said many times, please be prepared to use it yourself.

Snapmaker is a company that does not care about its users!

---

<div class="post-metadata">

**Author:** ![Hauke](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/hauke/32/5704_2.png) [@Hauke](https://forum.snapmaker.com/u/Hauke)\
**Post date:** [June 4, 2023, 10:40am UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/695 "2023-06-04T10:40:13Z")

</div>

> [@Blockmodule](#):
>
> Snapmaker is a company that does not care about its users!

I beg to differ. All cases that I had where handled friendly, fair and accommodating by Snapmaker support, replacing faulty parts without much ado, even beyond warranty.

Snapmaker’s public communication has considerable room for improvement, I’d agree with that.

---

<div class="post-metadata">

**Author:** ![Blockmodule](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/blockmodule/32/11177_2.png) [@Blockmodule](https://forum.snapmaker.com/u/Blockmodule)\
**Post date:** [June 4, 2023, 10:56am UTC](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441/696 "2023-06-04T10:56:09Z")

</div>

The idea is wrong.

It is common practice for Snapmaker to provide assistance for problems that occur with firmware and Luban updates.

Snapmaker should make sure that no problems occur before releasing the product.

We must avoid using the machine owner as a test subject.

[Previous page](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441.md?page=33)

[Next page](https://forum.snapmaker.com/t/discussion-of-snapmaker-2-0-firmware-updates/5441.md?page=35)
