Lots of weird stuff...
I've had lots of printers, and a MK3S for quite a while. Starting to print in earnest with my MK4 now (latest full release firmware 4.7.2) and slicer 2.6.1 and seeing lots of odd stuff. Will get more details but for starters:
1. Picked Hatchbox ABS. Print temps of 225, shows fine in slicer. on the printer, starts at 170, then ramps up to 250, totally at odds with what the slicer says - checked it twice
2. Cancelled a print. Full stop. Nozzle and bed won't shut off - had to shut off machine
3. Slicer randomly goes NUTS in Windows 11. It seems like it can't decide if its the front window or not, and flashes like crazy until it crashes. If I can select another app then come back fast enough, it stops and doesn't crash.
4. Odd behavior unloading and loading filament. It didn't ask what material I had on unload, then did a weird unload load unload when I tried to load it - haven't fully puzzled this one out yet.
I've not carefully detailed each step yet, but all this was in a 5 minute span. Never seen so many issues at once. I even uninstalled everything and reinstalled and still got the same whacky results.
RE: Lots of weird stuff...
There have been a few cases of gcode corruption in various ways... perhaps that's part of the problem. The printer does go to 170 to probe the bed, then heats up to temp for the print, that's on purpose.
In regards to #4, the printer doesn't need to ask what sort of filament you have loaded in order to unload, it's the same filament you told it when you loaded... it just remembers it.
Slicer randomly goes NUTS in Windows 11. It seems like it can't decide if its the front window or not, and flashes like crazy until it crashes
Have you another application also configured to stay on top which is fighting for the place?
Cheerio,
RE: Lots of weird stuff...
no, which is why its odd. Never seen the window fighting before. Wonder if its some bug related to windows 11..
Slicer randomly goes NUTS in Windows 11. It seems like it can't decide if its the front window or not, and flashes like crazy until it crashes
Have you another application also configured to stay on top which is fighting for the place?
Cheerio,
RE: Lots of weird stuff...
Thanks, makes sense.. only odd big remaining is why its not using the commanded Temp as shown in the slicer, and choosing 255 instead - seems like that might be a default value and its not picking up the actual value. I guess I can dig through the Gcode to see if its a slicer or firmware problem.
RE: Lots of weird stuff...
Oh, figured out to some extent the window being front or not - Not a Prusa thing. Something buggy in Windows. Its happened in other apps too.