Popping noise during first few layers?

[scyto]

Thanks @WilliamBosacker for understanding this is weird and not assuming it is me

FWIW
I saw the first instance on 1.12.1
And this second instanced on 1.12.2
(i have never run any other firmwares as this is only 4 weeks built)

And both times the device was powered on from cold, file sent via wifi, touchscreen initiated print.
I stupidly recalibrated before looking at M503 or M420V (sorry, i was panicking) to see if any settings got lost / modified.

–edit–
I guess I could print something via touchscreen, power off, power back on and the look at settings - will do that later today. I can do that say 3 times incase there is time vector to this, will leave it powered off for the same time as my dinner yesterday

[Artezio]

@WilliamBosacker does your machine being down have to do with the high speed tests?

@scyto as William said, did you do a home before turning it off?(not supposed to) And did you home after turning it back on before printing?(supposed to)

[scyto]

@Artezio

Before turning off - explicitly no, but it returns to home after touchscreen initiated print is finished.
Before printing - explicitly, not but when one connects initially via wifi it homes. (actually i need to test that, was gonna not post until i tested, but in middle of 3 hours print, so i reserve the right to be wrong). i also think it homes before every print initiated from touchscreen but would need to verify that for definite.

Now are these the same as doing home via gcode? who the heck knows! we already know that the gcode to start calibration and what the touchscreen does is not the same…

I have a suspicion that the touchscreen can bypass gcode code paths to direct the controller directly… but that’s just a guess…

[Artezio]

@WilliamBosacker

Not at all. That’s a bad assumption to make.

I was kidding, it was a joke lol.

@WilliamBosacker

For clarity, there is nothing wrong with doing a Home prior to shutting down your Snapmaker, in fact that is usually the last command of every print. You do need to watch it though, and @scyto described exactly what happened.

I’m still trying to understand this whole part. I don’t see why it would cause an issue. I was going off of what I was told before, it seems I’m getting confused. I spent my entire day yesterday browsing the source code looking for any inclination to why it would be left in an invalid state, didn’t see anything that stood out.

@scyto

not but when one connects initially via wifi it homes.

I’ve noticed mine no longer homes when connecting to WiFi after the added feature of it remembering the computer and no longer needing to verify on the touchscreen. But I haven’t paid attention if it does require it between power cycles.

[Artezio]

@WilliamBosacker yeah I know about the touchscreen, I was looking for any clues that referenced anything about the touchscreen and took down notes and many many screenshots. I found a few parts that I made especial notes of, for reference to look at when we actually do get the touchscreen source code (that’s a big IF).

I also found numerous instances of intentionally misspelled defined events. There’s only one reason for them to be misspelled, and that’s when the correct spelling is already defined somewhere else, most likely in Marlins code itself.

I think they have side stepped a TON of Marlins failsafes and gone around them. Possibly causing issues we see.