What would you like to see in the 8-bit firmware?  

RE: What would you like to see in the 8-bit firmware?

I would like to see print head controls, the ability to control where the print head goes using (shape hints), or (control hints) for the direction of the  print head. I would also like to see the ability to make a straight line when using the seam painting tool for example, when I use Photoshop I can click on a start point (point A) and hold down shift and click on (point B) to create a straight line and so on. there is more I would like to ask for but I think this is enough for now.

good luck I hope you can accommodate even one of these features.

Thanks for asking,

Swiss_Cheese

RE: What would you like to see in the 8-bit firmware?

my fault I was looking for this in Slicer, posted in the wrong place

RE: What would you like to see in the 8-bit firmware?

I would like to see either the filament change/load procedure improved or a configurable "Retract" top level menu item which just reverses the extruder a configured amount.

Using the normal loading procedure, if you don't retract a bit afterwards usually causes enough oozing to leave filament on the bed during the mesh bed leveling process (even if the nozzle is wiped just before). I drop into the move axis menu and wind back the extruder a little (usually about 5mm but varies with filament type) to avoid this.

Filament colour changes can also have similar issues but there isn't as much time for the problem to show up since it travels immediately to the print. You can't really retract there because there is no prime line mid print, probably not much that can be done about that. Loading and unloading is the most common place I have the issue though.

Multimaterial Purging Temperature / Add Flex for MMU

Hi,

I would love to see:

• When purging with the MMU using multimaterial it always uses the temp of the "new" material. But while having the "old" material in the Hotend it should use the "old" temperature to purge. As example: printing PETG 250 and PLA 215, it changes from PLA to PETG and tries purges with 215 degree celsius wile still having PETG in the Hotend.
• Pleeeease add Flex Support to MMU:
  I did my own profile using almost the "Sainsmart TPU" profile to fiddle around and try stuff on my own. As far as I can tell this should work with minor tweaking. I printed 8h with around 400 Filamentchanges (PETG&TPU) with 4 unloading issues of TPU if I remember right. Please help us tweak.

  My next tries would be PETG as dense supports for PLA (3D-Printing-Nerd (Youtube) tried this years ago with the Pallette 2, I guess) MMU should be more than changing colors... 

RE: What would you like to see in the 8-bit firmware?

I wrote shit 😶 ... of corse, its the other way around...from PETG to PLA..

RE: What would you like to see in the 8-bit firmware?

@sturze

Take a look at this: https://forum.prusa3d.com/forum/original-prusa-i3-mmu2s-mmu2-general-discussion-announcements-and-releases/mmu2-real-multi-material/

I use this script since a quite long time for multimat. printing of 2 different filaments (ASA, PLA).

wbr,

Karl

RE: What would you like to see in the 8-bit firmware?

I wrote a "similar" (well...) script long time ago. My script does a few things:

* generates a temperature gradient while wiping (when MMUing with eg PC and PLA this is a must)

* lowers the temperature radically just before the filament is to be pulled out of the nozzle (better tips) (fan is on during this operation to reduce time wasted)

* sets back the temperature *just before* filament is pulled out (reducing time wasted)

* speed during FLEX wipe is adjusted (if I uploaded the latest verseion, else it is not)

* it fixes an old slic3r bug, likely it is fixed in prusaslicer (I still use slic3r as I cant stand prusaslicers click en masse interface, and prusaslicer still seem to trash the common coordinate system for the split parts when splitting an object - so sad)

The script relies on materials having key words (not only "PLA" but eg "BrassFILL". The material list can easily be changed and expanded to your needs (lines 75-100 in the py file)

The file and instructions can be found as first item ("Temperature correction") at:

http://www.frimmel.se/print3D/

RE: What would you like to see in the 8-bit firmware?

I would really like to see an option in the menu to beep, play an alarm or play a tune when the print has finished and/or once the bed has cooled down too. Often I'll be in other room while the printer is printing, doing something else and I won't be aware it has finished printing for half an hour or so.  It would be a really useful feature and if you got it to beep once it cooled down too it would really save people time, since they could just come in and pop the item off the bed and start printing again. 

Having the option in the menu would be useful as you could turn it off if a print was going to finish at night time, or turn it on for a print you downloaded. Also providing options for a series of beeps or having it as an alarm requiring a button press to silence the alarm would cover different needs - from "ah my print is done, I'll get it when I'm ready" to "ok I need to print the next item".

RE: What would you like to see in the 8-bit firmware?

How about a slight change to the M600 filament change options?

You only get the option for "Is it extruding the right colour?" (I'm paraphrasing here as I can't remember the exact wording). You only get Yes, Cancel or say No, in which case it extrudes a bit more. There is no option, to eject and re-insert the filament. I had a print fail because I forgot to trim the blob on the end of the filament and it wouldn't feed properly. The gears never grabbed it. But there is no option to back out the loaded filament and try again.

RE: What would you like to see in the 8-bit firmware?

@karl-herbert

@frimmel

thanks for sharing!

RE: What would you like to see in the 8-bit firmware?

Maybe I'm missing something here, but if "the gears never grabbed it" (the filament), you should be able to just pull the filament back out, trim the end, and reinsert it, whereupon if you answer "No", the gears should grab it and away you go.

RE: What would you like to see in the 8-bit firmware?

@reddawg

I may be misremembering it, it was a while back. I couldn't pull the filament out, so maybe the gears did grab it but didn't feed it through.

What I'd like to see is an extra option to eject the filament and try again. Perhaps if somebody changed it to the wrong colour? Whatever the reason, I'd like to see a "re-do" option rather than Yes, No or Cancel.

Yes, the correct filament colour is coming out.

No, the filament has not fully come out in the right colour. Extrude a bit more to be sure.

Cancel, forget the whole damn thing.

Redo, eject the filament and start all over again.

RE: What would you like to see in the 8-bit firmware?

@reddawg

in the unlikely event, if its feeding, and just not hitting the ptfe (like TPU, tangling around the Gears, when idler tension is to strong) it is no way to just pull it back 😉 
BUT: I think you can open the idler door to get rid of the tension on the filament and then pull it out, or am I wrong? 

RE: What would you like to see in the 8-bit firmware?

Official support for Klipper via Raspberry Pi with the 8 bit boards.

That way we can have input shaping and higher performance, modern features and get away from the restrictions of an 8 bit board....time to move on.

Klipper is fast becoming the community standard for quality 3D printers.

RE: What would you like to see in the 8-bit firmware?

My Raspberry Pi4 would be happy to do some work for the printer board. Klipper would be a good alternative to a 32-bit board for the MK3.

Whether this is necessary is another topic for discussion.

wbr,

Karl

RE: What would you like to see in the 8-bit firmware?

Just got a Prusa Mini and I’d love to see the material required estimate (m length and g weight) after selecting a Gcode file to print. This is a very cool feature on the mini and while we obviously can’t have the thumbnail, material estimates should fit on the display. Probably want it optional since it might annoy some people who don’t want the extra step.

RE: What would you like to see in the 8-bit firmware?

Posted by: @frimmel

I would like the following to be added to the firmware (I use them myself, and will never downgrade to a mk3s/mmu2s firmware without them):

1. Filament loading test to include check that filament does not get stuck during load (see also pull request https://github.com/prusa3d/Prusa-Firmware/pull/2927 )
This modification is the single most important addition I have had so far. In short, it will pause the mmu2s print instead of fail to change filament and print an empty layer when the filament got stuck.

You might be surprised that this very simple check is still not in the firmware, and that I even got the response that with sufficient calibration it is not even needed (sort of "if anything goes wrong, just blame yourself"). The pull request needs some polishing to be streamlined, however, since I added it in my firmware in late 2020, I have had 0 (zero) failed prints due to mmu filament switching errors (I print every day and have to date used a large number of filament brands and kinds). I think this modification should be quite tempting for other users as well.

2. Make the IR-sensor active during print (see also pull request
https://github.com/prusa3d/Prusa-Firmware/pull/2929 )
This will pause the print if the filament breaks in the front PTFE tube (which will sometimes happen eg for ColorFABBs very fragile "brass fill" filament). Also, if the nozzle clogs (can happen eg when using a wood fill filament), the upcoming grinding will soon generate a pause (which might with a bit of luck even give you a chance to save the print).

Why the IR-sensor- is not active during print is a mystery to me. In my implementation you can turn on/off the feature via the menu.

3. Get rid of the hard coded filament loading speed (see also pull request https://github.com/prusa3d/Prusa-Firmware/pull/2914 )
Any one tempted to load flex70A or even flex82A will understand why it is a bad idea to have the filament load speed hard coded as it is now.

rgds, and thanks for a fantastic printer!

I would like to add a fourth bullet to my list:

4.  Menu item "calibrate in X and Y"

During slow prints, crash detection is not active in firmware (I assume for sure for some good reason). There are other reasons why X-Y-calibration may get lost during a print (for example, there is a bug or such in the firmware so if you pause the print just between the wipe tower and the printed object, Y-axis position will suddenly become shifted by 1mm or so).

If it happens, often you will hear the crash, but cannot easily re-calibrate (expect using a terminal). However, it is extremely simple to add this feature to the firmware. Just add the following SINGLE line of code to "ultralcd.cpp" within a MENU_BEGIN() and MENU_END() -block of your choice (I have put it in the move XYZE-menu, logically it should be in the calibration menu):

MENU_ITEM_GCODE_P(_i("Calibrate XY"), PSTR("G28 X Y"));

The recompile (using PF-build), re-flash and off you go!

And, a suggestion how to increase wipe speed, sometimes to a radical extent:

I suggest the wipetower software should be rewritten (likely in the slicer), to use a layer height independent of the layer height currently being printed (eg always use 0.3mm wipe layer height for 0.4mm nozzle regardless if the printed layer height is e.g. 0.05mm). The reason is simple: You can extrude 6 times more material per time unit using layer height 0.3mm as compared to 0.05mm. Of course, this means the wipe tower might do, for example, 2 wipes on the same height (next to each other) to fill up the same PRINT BED AREA as before, but it is really only a software thing that will save a lot of time (think of it: long prints using 0.05mm layer height would save hours in print time).

Currently, the "same" material mix will often (not always) match between the wipe tower layers, however, in my experience this has not gained much, I believe a higher flush rate would actually be better for the wipe tower.

rgds, Hans

RE: What would you like to see in the 8-bit firmware?

@paul-arden

The mini doesn't use the 8 bit board.  This is basically the request thread for the MK3 and similar printers.  Unless you mean you want to see that on the MK3 lcd, if so then you can add those placeholders into the filenames generated in PS so that they scroll as part of the name.  Thats what I usually go for the XXg, rounded up to the nearest gram.

RE: What would you like to see in the 8-bit firmware?

@neophyl

Yes, I am aware, I hadn’t realised how helpful the feature was until I got the Mini recently and needed to check if I had enough filament left on the spool and then I immediately missed that feature on my MK3/MK2.5.

Placeholder in PrusaSlicer to include that would certainly be enough, though I’d prefer to see a confirmation screen (again, perhaps optionally enabled) after you select the file to print with the filename scrolling on the first line, estimated print time on the second, material estimate on the third and print/don’t print confirmation on the forth.

I do also miss the file confirmation on Marlin which has saved me a few times when the encoder just tipped over to the next entry on the card while I was pressing it and I hadn’t noticed.

RE: What would you like to see in the 8-bit firmware?

It would be really nice if it was possible to open or close a USB connection to the printer (via Octoprint) without the printer restarting. Currently, the printer resets when connecting to or disconnecting from it. Sometimes I just forget to connect to the printer before starting a print (I print from SD card). In these cases I have the choice of aborting the print or not monitor it via Octoprint. This is a little bit annoying. Is there a technical reason for that reset?