Discussion of Snapmaker 2.0 Firmware Updates

thanks, was wondering that, they seem to have a bunch of redundant marlin stuff hanging around - also makes me assume they have done little to bring common fixes across from marlin once they branched? some of those dates are super old…?

@scyto @brent113 this further backs up my suspicions. I really wish I had an extra touchscreen to dissect. Seeing as I have the proper equipment…

1 Like

They cleaned up a lot of it, but the way Github works, you can see the entire commit history. You’re looking quite far back. Many of the files that are not needed have been removed from the tree.

100% accurate, no Marlin fixes have been brought in. No new Marlin features either, like inline laser power. I’ve been working on bringing that in.

Does anyone know if the bug with M92 resetting every power cycle has been fixed? It started with v12.0, but I don’t know if it has been fixed yet.

I dont know much about that, but is there a reason you cant put it in your start gcode?

I suppose bug isn’t the right word. I guess feature would be more appropriate. Without it, all the calibration values reset every power cycle. I’m running 11.4 now, because it still provides that. This is specifically what I’m referring to:

They’re being saved fine prior to a power cycle. I know an update resets them, however it resets after every power cycle.

Yes I can confirm this seems to be the same on my machine.

I just noticed something odd.

I re-set my xyz esteps with M92 to the value i had used successfully to print an xyz cube last week.
I looked at my M420 V values and they were in the ~6.03 mm to ~7.58 mm as usual.
I then did a calibration of the bed from the touchscreen.
I then looked at the M420 V values and they were in the ~0.48 mm to ~2.06 mm range

I started a print and i noted the nozzle was lowered below the build plate by about maybe 1mm (i hit the power button pretty darn fast before the nozzle got to start temp!)

I think i may have found the methodology that cause head crash last week or so - be careful folks.
This seems to be only an issue if one does calibration AFTER setting xyz esteps.

–update–
Given this is a machine damaging issue i filed a github issue

2 Likes

Hi, how is it going, do you get any results?

I used this whole 3d printing thing to buy grade B sizing blocks :slight_smile: (cause i wanted to prove my other tools were accurate, i think it was pointless, but was a learning exercise)

Can’t wait to see the determination of what his issue is.

I am still bothered by my x = 19.89 y= 19.95 and z = 20.33 when my flow is 100% perfect on a flow test cube at 100% flow rate … (exactly 0.40 width).

@WilliamBosacker i was wondering that, i can’t recall what i did the cube on, probably Luban but will need to check

Oh and i am using your profiles on prusa, made a couple of tweaks :wink:

I updated to the most recent versions of both Luban and the firmware last night and now I’m having an issue where when I go to print, the bed won’t hold the temperature.

I can set the temps on the touch pad and they’ll heat up just fine, but when I start a job, the bed’s temp starts falling and refuses to go back up to where it needs to be. If I cancel the job to try starting over, it freezes and I have to power cycle the machine.

I had this issue before and one way I could get around it was connecting to the machine inside of Luban and setting the nozzle and bed temps there and the bed temp wouldn’t fall; it would stay right where it needed to. Now, I can set the nozzle temp in Luban, but the bed temp command won’t respond at all.

This morning I tried going back and installing previous firmware versions all the way back to 1.10, but the bed temp issue persists. I have no idea what to do.

Hi all,

Just updated software, now it won’t create toolpath for vectors, any help is really appreciated.

:frowning:
Why do they break everything on every update

Can you roll back?

@MooseJuice im just going to stick with 1.12.2 lol

That’s not a firmware problem.
It’s a Luban problem - if it’s not user error, which it probably is.

@wca20 They’ve changed how you have to select and create toolpaths slightly.
You need to share more info with us. Share screenshots or the file you’re trying to use.
You may need to use offsite image hosting since you’re a new forum member.
-S

Which part? The tool path? I was referring more to the heated bed issue, I apologize for not explaining more. I actually have no idea how Luban does tool paths as I’ve used Aspire from the very beginning. So I’m not sure how to help there.

I was referring to @wca20 's post and @MooseJuice 's reply.
His issue is Luban, not firmware, so his post actually shouldn’t be in this topic.

-S

2 Likes

i need help i did the update two days ago on my snapmaker A350 on touchscreen firmware and since then my files are not supported from usb and i connect my computer and the machine through wifi and transfer files it says transfer complete i tjen look at the local file on touchscreen and nothing is there idk what to do been stuck and suggestions?
i need help i did the update two days ago on my snapmaker A350 on touchscreen firmware and since then my files are not supported from usb and i connect my computer and the machine through wifi and transfer files it says transfer complete i tjen look at the local file on touchscreen and nothing is there idk what to do been stuck and suggestions?