Had this problem because of comment lines in the end-gcode.
I deleted all comments and it works fine now.
1 Like
I see, this is only a recent issue for me however and I have not updated Cura or anything else related to generating g-code so I wonder why its only now started happeningâŚ
Little insight on my comment above. 1.10.1 has a bigger problem after starting a job and for whatever reason canceling it result in an unstable system. After you stopped the job and by example wanted to start it again with another z offset it will hang when you press start. The rails and head wonât move and the heating stops from the bed and nozzle. After that you can only power cycle ( pressing stop doesnât do anything )
The not storing my calibration is probably something that has to do with my eeprom being defective after a little smoke that came from a new 3d printhead. Still awaiting confirmation for that from EdwinâŚ
But after that an not being able to do a manual 25 point calibration in 1.9 ( as it isnât saving when you press save after the last point ) i decided to give 1.10.1 another try. But still no luck with that version.
@nfmaas I would suggest to make a own thread about your problem.
You get a heat runaway from the nozzle,- this means your machine stops all,- just a power cycle brings it back to life.- Check your hotend!
There is nothing wrong with the nozzle. Or heating of the nozzle. As when i am in 1.9 everything works like a charm and only in 1.10.1 it will not.
Whatâs about your thermistor? Is it exactly assembled? Did you gave it some thermal paste?
Snapmaker team improved the safety functions in the last firmware 1.10.1 as you could see in the changelog.
Maybe there is something wrong?
I want to help, but sometimes it is hard.
Itâs definitely a firmware bug.
If I stop a print and then try to start it again, it will show bed and nozzle temps as set to 0.
Have to cycle power to get out of it.
There were a few other things that were acting weird, one with laser calibration. Didnât have time to be beta (alpha?) testing it so I went back to 1.10. Only the 99% bug with that one and only occasionally.
-S
Itâs curious, I have the 99% bug with comments, but have got no other bugâŚ
The description and my understanding are maybe too low to get it, but the screenshot told me, there was a heat runaway - so, no wonder that the machine shuts down, do you understand my point?
@sdj544 I will give it a try tomorrow.
Maybe it thinks itâs a thermal runaway. I donât know. Donât really care. Not my job to troubleshoot the firmware. I reported it on here and on FB when it first came out.
What I do know is it acts like itâs going to start printing and then just sits there with the control pad showing that the temperatures are set to 0 (where it should say 205Âş and 60Âş as an example) and then showing the actual nozzle and bed temps.
-S
The firmware throws that specific error in the above picture if the hotend does not heat up at least 1 degree per second.
It reached 181 out of 240 and threw the error by missing the required temp increase.
Could be poor thermal bonding of the thermistor, or the heater, to the heatblock. I put paste on both. Could be other causes.
It doesnât look like thermal runaway to me.
1 Like
But from the beginning it does heat up quickly but i did not check if that is a degree per second minimun. When it is near the set temp it usually falls back a few degrees and then goes up again to the set temp. This exact same thing is my snapmaker one doing. So i never saw a problem in that.
So then i think that the firmware is set too specific about that degree per second.
1 Like
Agreed, and now that we have the ability to build custom firmware soon it may be feasible to test changes like that
1 Like
Thank you! Iâve been looking everywhere for this information and after tons of sifting through Google search results I came across your post. I donât know why this isnât an FAQ on Snapmakerâs website.
1 Like
Hopefully this is the right area for suggestions to the firmware (it seemed to be at the top of the page).
Anyway for the CNC unit I have several suggestions:
- there needs to be a stop or cancel button especially on ârun boundaryâ âhomeâ and âgo to work originâ
- when going to the work origin the SM should complete the x and y axis before the z axis my sm just ripped through one of my clamps bending the screw because it decided to complete the z axis first - why? with no immediate stop option you end up fumbling for the power switch.
- The power interrupt works some of the time when it does itâs great when it doesnât youâre left having to redo the whole section you just completed for the CNC there is no reason why you shouldnât be able to fast forward to a set percentage.
- The open door cut off works great, this also offers the perfect opportunity for a âsave progressâ option allowing you to turn the Snapmaker off so you can go to sleep on long jobs and not have the sound of the hurricane still going on from the PSU or be somewhere else. This would be a very simple implement on the CNC and has the code 99% written as it is there for loss of power.
Any chance in addition to the latest suggestions to get those:
⢠Activate a screensaving on the terminal after a setup time ( set in settings ) - thatâs quite easy and will increase the life of the screen - thatâs minimal changes for dev.
⢠Handling G-CODE Manual Tool Change for drilling
⢠Having a possibility to interrupt a drilling or a run boundary directly from the screen while is running
⢠The ability to switch on/off the light on enclosure
Thanks!!
Thatâs already possible with the current firmware. You can even set the brightness of the enclosure LEDs though G-Code with M1010 S3 P100 (turn on, 100%), M1010 S3 P0 (turn off), M1010 S3 P50 (50%) etc.
1 Like
I have the latest firmware 1.10.1 and been encountering machine crashes under following scenrios:
1.After a print is done and select another file from the display panel and print.
2.After I stopped a print and select another file from the display panel to print.
In both scenarios I need to turn the machine off and on to be able to continue the next print.
Any idea how to resolve this?
I havenât had 1, but have had 2 (whether I select new file or same file)
Go back to 1.10.0 and occasionally have 3d prints get stuck at 99% or go back to 1.9 which is the most stable.
-S
From discussion on this forum, I believe that the 99% issue relates to comments in the G-code that follow the last actual command.
You should be able to remove the trailing comments from the file before sending it to the SM, which should stop the 99% issue from occurring.
2 Likes
Iâve seen both of these issues. If I manually move all 3 axes by 20mm away from home BEFORE selecting another file to print though it seems to âfixâ it.