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.
1 Like
@Riskey , how come touchscreen is not notifying about limited storage to accept updates?
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ā¦
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.
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?
1 Like
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.
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
Even when attempting to print, the temperature settings in the old G-code files no longer work.
@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?
2 Likes
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 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.
1 Like
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?
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**
This is great point too, since those can be very efficient (if filed properly) for the devs to solve.
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.
1 Like
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.
1 Like
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.
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
Assuming Iām looking at the correct location
3 Likes
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ā¦
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
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!
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.
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.
1 Like