Closed jettoblack closed 5 years ago
Same happened to me. Loaded new mk3 firmware(hex)>slicer, compiled mmu2 firmware>ardiuno.....reset printer....erase data..... I know your mmu firmware loaded because mmu selector was much faster.
Right after printer setup. congrats your printer is perpendicular..... It wanted to measure bowden length with filament sensor - I think it did, no confirmation, I'm not sure.....Then 1st layer z height hangs. Not sure of order: Bed leveling. loads filament from mmu to mk3 heats nozzle to 215 and bed to 60 hangs.... Light flashs on mmu like a load error - but it does have filament so i didnt know what to do????
So I never got to try a print, reverted back to stock.
Yes, first layer calibration wizard has not been touched and will not work. If someone has time to retrofit this code they can. At this stage, have printer setup on stock and don't earse eeprom on printer to reset the settings.
I wish I knew that before I installed your firmware
It hadn't been considered yet as this is this just something I have thrown together as a sole user. It will be added to the list of enhancements that could be done if PRUSA still don't have a proper solution in the near future.
Ok no problem. Just note it somewhere, so users knows. It's a deviation from the standard firmware installation process. By resetting to factory I erased my 1st layer offset. At least have user take note of old zoffset value and warn not to eeprom erase.
Prusa is about to drop mk3 3.5rc firmware. Looking at the commits it has some new mmu2 code???
Yeah, will do for sure. Good pick up too, thank you.
Yes they have added a command for MMU2 but it doesn't relate to using the MK3-FSensor or fixing any known MMU2 issues that I can see.
They have added a menu to enable/disable autodeplete in the tune menu when printing which I plan to pull across when I have some time.
Here's a workaround so you don't have to re-flash: Take the bowden tube off at both ends, stick some filament into the FINDA, then power off & on. The MMU2 starts up in panic mode because the FINDA is triggered, so the MK3 won't see the MMU2 installed. You can use it just like non-MMU mode.
Since it's relevant.... to my earlier question. Prusa fixed/made some changes to first layer calibration in release candidate mk3 firmware 3.5.0rc1 specifically for MMU2.
Hey Mylife4aiurr,
I have just merged all 3.5.0rc1 code into my repo but haven't tested first layer cal, I see they have a section within the wizard that requests filament from MMU but might need a small tweak to get it working with the FSensor.
Excellent news. Factory reset between firmware updates really is the best path. Just 4 consistently I'd do 1st layer Cal, but at least now I know to load stock then yours no reset.
In 5.0.2 / 2.1.3 FW, after starting First layer cal and selecting a filament, it loads the correct filament down to the sensor, but it appears the sensor doesn't trigger or it doesn't get communicated to the MMU2. The MMU2 starts flashing red load error and none of the MK3 LCD options or the MMU2 buttons will do anything at that point.
@jettoblack I dont think zerobeast tweaked yet for work with FSensor,
Er, couldn't you just use your own sliced object for getting the LiveZ right? I generally do, the built in print is cool but doesn't work well. 5-ish squares or circles is better.
Anyway, installed the release and so far I've done 4 TPU loads which all went flawlessly, though I'll admit they might be a bit slower.
Printing a "single MMU" print and initiating filament changes from the TUNE menu. I have noticed it is immediate - you used to have to wait ~10 lines, but now a filament change happens Right Now.
One mis-unload, Printer didn't notice. Put filament in and out of ball-sensor a couple times, MMU light changed its flashing back and forth. Re-homed MMU (twice) and filament loaded, print picked up right where it left off. In 6 loads, all TPU, 2 translucent, no failures. I'll do an in-depth PETg & TPU test later, but at first stab it's promising. Next on the menu is a PLA/TPU 4 color model with PET-g supports. Wish me luck.
Hey Jettoblack,
Thanks a bunch for testing, I’ll find what the heck is happening today and let you know👍
Wow AbeFM, trying tpu, sweet. Will have to use the filament types soon as they’re already passed to mmu just not used. Did you slow loads down at all for your tpu?
I've gotten prints with TPU and pet wiring with the same settings.
Having issues (check forums), but don't seem to follow material, only seeing issues in PLA. Also seen some grinding, is distance to bondtexh wrong - or timing?
Thanks!
-Abe.
Sent from my "smart"phone, please excuse brevity and Swype-oes
On Thu, Nov 15, 2018, 3:02 PM TheZeroBeast <notifications@github.com wrote:
Hey Jettoblack,
Thanks a bunch for testing, I’ll find what the heck is happening today and let you know👍
Wow AbeFM, trying tpu, sweet. Will have to use the filament types soon as they’re already passed to mmu just not used. Did you slow loads down at all for your tpu?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/TheZeroBeast/MM-control-01/issues/17#issuecomment-439222117, or mute the thread https://github.com/notifications/unsubscribe-auth/AAClkby259tBggGfj7-VgcUQ3__OsC1qks5uvfKcgaJpZM4YY1ji .
Ah, that is so cool. I haven't tried my 87A TPU again since I tried with stock MMU2 code. I'll try give it a go again this weekend.
We still need a matrix of speeds for the main filament types, even if only small adjustments.
I also found what was stopping First Layer Cal and will test as soon as I can between prints. FSensor function is normally is disabled for all Wizards, I have enabled it for the period of the load required for MMU.
I can confirm first layer cal now tested and working, it'll be in the next version shortly.
Here's what happens when I try to do a First layer calibration:
The printer starts warming up, and asks which filament to use. I select Filament 1.
The MMU2 loads filament 1 down to the sensor, then starts blinking (load failure). I guess it did not receive the expected sensor response from the MK3? The printer stays at temp but doesn't do anything.
Once in this state, I can't figure out how to get out. The MK3 is in "Print mode" (LCD menus are as if there is currently a print running), but there is no cancel print option, nor can I eject/unload filament in this mode. I had to open up the MMU to manually retract the filament, then do a hard reset on the printer.
Unfortunately my current Live Z value is not good after adjusting the PINDA, so it looks like I will have to flash Prusa FW to the MK3/MMU to get past this.