Binary gcode was introduced mainly to solve one issue. Very slow Mini/MK4/XL hardware in terms of network speed (it is in 0.1-0.4MB/s range; wirelessly or wired - ~the same). Since hardware cannot be just replaced with something modern, binary gcode and gcode streaming was introduced. That is a smart (and probably the only possible) solution to workaround lacking hardware in these printers.
@@t.m.breuel2670 Np. Gzip is a very expensive for embedded systems. They are saving cpu cycles/ram everywhere where they can (reminds me situation with 8bit MK3*). For example handling PNG images was too expensive, so they switched to QOI format for thumbnails which requires less cpu/ram.
Just a video idea here, Prusa mentioned that it is easier to color items for the prusa XL if you use some kind of pen tablet/wacom tablet. So i tried to look that up and in a world of everything already being done on youtube, there is no example I can find about how to use one in prusaslicer to color. Might be a good video to do someday.
The limitation of the SVG object not being saved in the .3mf file is actually a benefit for handling proprietary SVG files. The text object does something similar. With the text object the font file isn't saved in the .3mf file so if you load the .3mf file on a system that doesn't have that font installed (proprietary font?) then you can't edit the text object.
binary gcode? please no. I‘m instantly getting flashbacks to the replicator or flashforge creator days needing to compile to x3g/gpx files, being stuck to specific slicers or need to set up scripts to go back and forth, always with compromises being made.
@@3DMusketeers What did not leave my head in the last couple of days: Worried about extending the spec to allow the binary being digitally signed, for the security of the user first. Next step providing digitally signed ready made downloadable sliced code exclusive to your printer, Apple-like ‚notarized‘ for your convenience. Finally, to allow model creators to better protect and monetize their IP, put a full blown DRM around it (only x prints allowed, only valid for x days…). Sounds a little bit dystopian, but I think this is what we are heading to on the long run, opening that door acting as a catalyst at least.
The gcode actually annoys me for a different reason - from what I've heard, binary gcode is not a new concept, but Prusa has decided to design their own implementation rather than use an existing one. Not sure why, and they don't say why. Cancel objects is nice, and I liked having it in Octoklipper & Octoapp. But - probably because the CPU is weaker than a Raspberry Pi, even though they upped it to 32 bits - you can't see the object to cancel visually on the Mk4. It also impresses me they found a chip weaker than a Raspberry Pi.
the reason is pretty simple, saving data in binary format is nothing new obviously and while bgcode technically exists nobody is actually using it so far. Prusa has made their own implementation of it because they also made changes like changing the image format for the thumbnail that saved in the gcode. also important to note that Prusa is running all their stuff on the printer on bare metal instead of having basically an entire operating system layer in between so they probably optimized for that as well.
Grant, sounds like your enjoying the XL. So have you honestly experienced any set backs? Mine just shipped today, (fully "partially" assembled). lol So I'm hoping for good results and excellent tool accuracy. I already have ideas for custom tool heads I might try to make down the road.
Haven't had a ton of time to mess with it honestly, doing some projects and things we can't talk about here, but I did have adhesion issues to the plate. It was recommended that even though I was using alcohol to clean it with, dish soap was required at least once. I'm not used to the satin sheets. Some other issues with adding speed in input shaping but it seems Prusa has a work around for it.
Had many adhesion problems on a mk4 w PLA we’ve been evaluating for last 6 mos or so, note these are small footprint parts we’re printing. First did the heated chamber, that got rid of lots of stringing, but ends of thin parts were still lifting/peeling up. We need the bottoms to be very flat; so this was a major issue for us. Got a satin sheet and started using end of Jan/24 and it helped for a while. Then started having issues again. Had been cleaning w 91% & lab grade ipa. Didn’t “see” any fingerprints, but still,probs w adhesion. Tried dish soap, letting dry thoroughly overnight - helped a little. Finally broke out the Dawn dish soap (use it for cleaning oily residue in the machine shop). Wore nitrile gloves while washing. Worked like a charm. Started wearing nitrile gloves whenever handling the plate, much much improved results w adhesion. Don’t think the plate has been washed in 3-4 months? Saw some corner lifting last night on a large (96mmx96mm) relatively thin part; so going to try washing again (resorted to using Mickey ears to get it done expediently). If not containments from PLA (know it’s not those devilish leveling “dots”affecting bed leveling, scrape those off very thoroughly - tip is also very clean) might try playing w chamber temp…that has helped a bit before (also w stringing). Fixing to order a mk4 kit now that the clogging issue seems to be somewhat mitigated (we had a defective part in the filament path on our factory assembled mk4) between a bad part replacement and the latest firmware update life is much better. Though also looking at the XL…hard choice. Haven’t seen too many print quality comparisons between them online (we’re currently doing .15 & .2 struct-IS layers, .4 nozzle - so far). The MK4s will likely fill out our farm…though that new robo-unit w “slim” mk4s looks real tempting to buy into. Likely a few of XLs too. Been a road, but getting there. As always, YMMV. Just sharing, nothing more, nothing less.
I just want to drop a comment of "OMG yes, please add the multi-plate. Drop the ego and just implement it. Blackbox or copy code". I'll note that when I brought this up at a Prusa User Group event, I was told that the hesitancy is if they copied the code from somewhere else and not knowing if they would be following the license. Which I can understand... there are 10k forks of slicers with one off features that go to die... but I also think it's a cop out and they just need to add it. I have talked to a number of people who said they use Orca Slicer over Prusa Slicer (ironically, basically nobody uses Bambu Studio in my circles) and they said the reason: plate management. They have stated they are willing to be a version or two behind in terms of features, if it means they get plate management.
Prusa has pulled code from others before, including Bambu, they even credit them in the latest 2.7 release :) I don't think it's an ego thing and instead an already planned roadmap
@@3DMusketeers I'm not so sure. I've read the Dev comments on tickets that have been around since nearly the release of Bambu Studio. People have asked time and time again, both Github and in person. Both times have been waved off. Most others simply don't get responses and then appear in an alpha. There are easily dozens of times someone responded from a Prusa account on TwitX that they already have multi-bed implemented and it's not a feature they need to implement "because it's already there"
I just used the cancel object on my last print because the part broke free from the support. I canceled the 2 failed objects out of the 10 and keep printing without wasting the whole print.
If Prusa decided to develop CAD, I worry that they’d need to charge money to justify the additional development. Like slicers, there’s no end to CAD updates/improvements. You still can’t add print pauses in sequential-print mode.
@@3DMusketeers I wouldn’t mind if they charged for CAD, but right now they don’t charge for the slicer. I’m hoping it stays that way. I don’t see a benefit to Prusa getting into the already-saturated market of CAD, when we already have free/inexpensive options that include CAM and simulation. Prusa’s frequent release of new slicer features is impressive, but if they were so great, they’d have added that missing basic feature that someone complained about years ago. Sure, most prints have no need for sequential print-mode pauses, but you could say that about a lot of slicer features.
CAD isn’t saturated. There aren’t any good open source CAD programs. It’d be neat if Prusa very gradually added CAD features, like ability to do OpenSCAD inside PrusaSlicer… while integrating ability to click to select objects and then drag them (perhaps requiring specifically formatted OpenSCAD variables?) and then maybe later, ability to click to select edges to add fillets or chamfer. That alone would handle like 90% of my CAD needs. Evolve slowly, only adding features where it makes sense. But yeah, OpenSCAD integration would be a useful addition and would put Prusa on its way to becoming CAD.
@@TheAnachronist It depends what you mean by "good". Compared to solid-modeling CAD from the 90s, today's open-source CAD is good enough. Compared to modern, closed-source CAD/CAM/Simulation packages, it's not. I don't object to adding a few basic CAD features to PrusaSlicer, but it's a slippery slope. I could see them diverting much of their attention away from hardware, firmware, and slicer-specific improvements. I see more value in them focusing on their specialty. For example, they could add extruder-current/torque/speed monitoring to check for filament slipping or underextrusion. Alternatively, replace the filament run-out sensor with a filament position sensor (mechanical or optical), and compare it to extruder position, to monitor the filament slip ratio. A nozzle-backpressure transducer or AI-camera system could monitor over/underextrusion. Automatic live-adjustment of extrusion would take layer-adhesion to the next level. Developing CAD is a monumental project. There's a reason the good stuff costs money. Prusa would add another half-baked solution to the pile, if they dilute their efforts with a side-project that is outside their area of expertise.
Prusa absolutely needs to make their own CAD program or simply Fork FreeCAD and throw 90% of the features out while making the remaining 10% work really good.
@@3DMusketeers Dev teams within Prusa or the ones working on FreeCAD right now? Because internally Prusa would absolutely need a separate team to work on a CAD program but obviously that would cost a lot of money for a long time.
Over the Thanksgiving break (for us in the US), one of the more prolific plugin authors for OctoPrint (specifically jneilliii) created a plugin for said software that can receive a binary gcode (.bgcode) file and convert it back to ascii for OctoPrint usage. (AFAIK you can't stream the .bgcode file over the serial port and expect the printer to do anything. Serial port is for ASCII gcode transfer only. This may change, or I'm wrong... Also none of the other OctoPrint plugins that scan gcode for things like thumbnails, print-times, live gcode printing views, capture event triggers, all the things that OctoLapse does know what bgcode is, or even now needs to.) When I installed it this past weekend it wasn't available in the OctoPrint plugins repository yet. I installed it from the plugin's GitHub repository. I'd provide links, but RUclips doesn't like that. 😕 This was possible because Prusa released the c library to encode and decode the bgcode format as open source.
@@3DMusketeers TeacingTech's video was posted about 10 months ago and asked the community for help testing to see if it was useful for everyone. Maybe Bambu was "inspired"as well lol
I think I'll stick with ASCII gcode for now. I see the need for some to use it, especially those with smaller storage or use SD cards. For me I wont' worry about as my gocde files are always on Linux systems with a BTRFS filesystem with compression enabled (compression-force=zstd:1), and this drastically reducing disk usage for gcode files already (laptop is Ubuntu, printer has Octoprint on Debian). This reduces the file sizes about 50% by itself, and I could add some de-dup if I really cared, and archive old files in a compressed format if needed. Compatibility and edit-ability are much more important for me. I won't knock those who want binary gcode, tho, if it works for you great. Add support at least.
Something changed with how 2.7 sets print speed. With 2.6 and prior if I set all my individual speeds to zero, and utilize the auto speed function set to 100mms. Then the algorithm clearly tried to target 100mms as much as possible. Only slowing print speed for small features and to normalize flow. Now with 2.7 it seems as if the slicer prefers to target almost exactly 50% of my max speed setting. If I set 100mms, it slices 99.9% of my prints around 40-50mms. I have tinkered with settings for hours now trying to figure out what is causing it to want to slow down. So far only thing I can find that gets my average print speed back to where I want it. Is doubling the max speed limit. But I fear it’s going to sneak up on me and try to print at 200mms some time randomly. Which my printer just cannot support.
An interesting limitation of the cancel object, at least on my MK4. I was printing some more filament clips in a batch of 100 (so I never have to print them again unless I wanted to change plastic types which is why I was printing them again). I was having trouble getting them to not be knocked loose because I had the stupid idea of printing them in ColorFabb HT. Before I broke down and decided to print them on a raft (which did work), I tried to use the in-printer cancel object feature. It only showed 16 of the 100 objects to cancel in the list, and even the "cancel current" didn't seem to work on the ones that I needed to cancel (which I think were object numbers higher than 16). There seems to be a quantity limitation.
Love all your content. Newbie here. I need to know a good resource to walk me through settings in a slicer, starting with how you choose a slicer (can I use them all with Bambu X1?). And like the file types: stl, step, obj, etc. etc. etc. Learning as I go! Loving it. Very exciting! ... oooo, excited for next week's video about newbies! *raises hand.
Huh? How exactly can pressure equalizer help, according to you, heavy machines that have slower acceleration when it is only a restriction. It limits something; namely the acceleration/deceleration upon changing from one feature to another (e.g. from infill to perimeter).
Sure it has a 'ramping style', just like acceleration is a ramp up, but in the end the pressure equalizers only effect is to slow the faster features down when it is transitioning to and/or from a slower feature. If you have both positive and negative slope enabled, a transition from 50mm/s to 100mm/s will make the 100mm/s feature go from 50 to 100 by means of the positive slope, even if it were going in a straight line (so regular acceleration is a separate limit). The feature that had the 50mm/s to begin with is not affected. For 100mm/s to 50mms, it slows the first feature going at 100mm/s down to 50mm/s. So again, how is this relevant to big printers specifically aiding their acceleration?
If I knew specifically how to describe it I would.. But I have a BIG bowden printer (1M bowden tube) and with that ramping thing it works AMAZINGLY well, without it I have issues with the start and ends of lines. It is really odd.. Sorry, the limits of my technical knowledge have been hit ha ha, but I can ask others?
What I want to print when my XL arrives...is something decent sized with a good amount of supports that are printed in soluble filament.. Any suggestions folks?
I can't imagine you'll ever see IS on a mk3 natively. It's probably slightly more powerful than my Commodore 64. lol Hell my USB cartridge for my commodore 64 has more power than the computer does. lol
Yeah, Prusa is cramming about as much as they can already into the limited programming space of the chip on the MK3 processor board (I think it's the same processor as on an Arduino Mega). Even if they could fit the IS routines on that processor, it would be really slow. The chip doesn't natively support floating point math. It's amazing that Prusa is able to get that processor to work as well as it does on the MK3.
@@3DMusketeers you can play doom on a C64, but you really don't want to. It looks like crap and it's slow as molasses. You can only do so much on 8 bit.
Cute. Arc fitting, objects exclusion is already in bambu studio and bambu printers. SVG support has been available since 2022. If you think Bambu studio is just a "color" swap you are need to lay off the Josef juice. Binary gcode is no different from how Bambu studio handles 3mf files. It's a zip container. I can take an 8mb 3mf file that is actually 50mb in size extracted. This includes multiple plates, photos, and project info. This is nothing new. BUt since the mk4 uses such crappy network protocols it needs to shrink all that data into manageable sizes so it can choke on it still. Heck Prusa slicer could not even handle Step files until Bambu implemented it. I cant wait until Prusa research invents multiple plates. 😜
Boy the replies here went to 11 without any reason... Technically bambu could dead copy it and assuming it's in open source it would be legal. Welcome to open source.
I don't see the point in editing gcode. I'd rather just re-slice it. Since getting into 3d printing I'm like.......why the hell is this in ascii? It's such a massive waste of space. I've watched my pi fill up with gcode faster than the timelapses. So hell yeah! I prefer the the idea of bgcode. I hope this gets adopted as long as it's open source.
When you need to print hot but need to slow down for bridging, you can't set different temperature just for bridging of a section (to not overheat the filament) in the slicer nor using custom gcode as it's inserted per layer basis. You need to open the gcode, find the section and insert the custom gcode to change the temperature and back after the bridging is done.
@@hologos_ if it's 5 degrees it's not going to be that big of a deal. If it's 10 degrees it's not going to change fast enough to matter. And if that really is an issue, then you need to tell prusa not me. Then you can set it in your bridging settings. Also while I have no intention of editing bgcode, it sounds like it's not hard to edit it.
An edge case that I've used rarely is to be able to scan through my generated gcode to find issues, or actually figure out in what order the custom gcodes in PrusaSlicer are applied. But, some plugins for OctoPrint absolutely rely on being able to scan and parse the gcode (either as a separate scan process, or monitor the serial stream for triggers).
@@awilliams1701 Do you know there is a gcode that waits for the temperature to reach the target? :-) By the way "tell it to Prusa not me" - then don't put your opinions on the internet if you don't want to be confronted. 🤷♂️🤦♂️
Binary gcode was introduced mainly to solve one issue. Very slow Mini/MK4/XL hardware in terms of network speed (it is in 0.1-0.4MB/s range; wirelessly or wired - ~the same). Since hardware cannot be just replaced with something modern, binary gcode and gcode streaming was introduced. That is a smart (and probably the only possible) solution to workaround lacking hardware in these printers.
Gzipped text gcode would solve that problem better than a new binary format.
@@t.m.breuel2670 Np. Gzip is a very expensive for embedded systems. They are saving cpu cycles/ram everywhere where they can (reminds me situation with 8bit MK3*). For example handling PNG images was too expensive, so they switched to QOI format for thumbnails which requires less cpu/ram.
They are running bare metal though, no back end OS. It's not crazy powerful but does it need to be?
Binary g code is a weapon against the slow wifi.
Yep. I'm not sure why it's so slow to begin with, but thankfully it wouldn't be an issue for us.
Arc welding, yessss!
Right?!?
Just a video idea here, Prusa mentioned that it is easier to color items for the prusa XL if you use some kind of pen tablet/wacom tablet. So i tried to look that up and in a world of everything already being done on youtube, there is no example I can find about how to use one in prusaslicer to color. Might be a good video to do someday.
I did just get a drawing tablet thing, it may be a good one to do, thank you
The limitation of the SVG object not being saved in the .3mf file is actually a benefit for handling proprietary SVG files. The text object does something similar. With the text object the font file isn't saved in the .3mf file so if you load the .3mf file on a system that doesn't have that font installed (proprietary font?) then you can't edit the text object.
Oh that's a good point!
If Prusa made a stand alone version of TinkerCAD that would be a game changer.
I agree, but I'm not sure it's needed?
Something like TinkerCAD as a standalone app not requiring an internet connection is indeed needed.@@3DMusketeers
binary gcode? please no. I‘m instantly getting flashbacks to the replicator or flashforge creator days needing to compile to x3g/gpx files, being stuck to specific slicers or need to set up scripts to go back and forth, always with compromises being made.
Nah it's open source so it shouldn't be an issue
@@3DMusketeers What did not leave my head in the last couple of days:
Worried about extending the spec to allow the binary being digitally signed, for the security of the user first.
Next step providing digitally signed ready made downloadable sliced code exclusive to your printer, Apple-like ‚notarized‘ for your convenience.
Finally, to allow model creators to better protect and monetize their IP, put a full blown DRM around it (only x prints allowed, only valid for x days…).
Sounds a little bit dystopian, but I think this is what we are heading to on the long run, opening that door acting as a catalyst at least.
There needs to be a star wars anakin/pademe meme. You've added multiple virtual build plate support right? right? sigh................. dammit prusa!
Yep, soon tm LOL
@@3DMusketeers I almost feel like they are avoiding it just to make us squirm. lol
Always looking forward to your view on new things. Keep up the good work. 👍🏻
Thanks!
Arc welder, of thanks god finally some useful update. Best update after Arachne.
Definitely a good update!
The gcode actually annoys me for a different reason - from what I've heard, binary gcode is not a new concept, but Prusa has decided to design their own implementation rather than use an existing one. Not sure why, and they don't say why.
Cancel objects is nice, and I liked having it in Octoklipper & Octoapp. But - probably because the CPU is weaker than a Raspberry Pi, even though they upped it to 32 bits - you can't see the object to cancel visually on the Mk4.
It also impresses me they found a chip weaker than a Raspberry Pi.
the reason is pretty simple, saving data in binary format is nothing new obviously and while bgcode technically exists nobody is actually using it so far.
Prusa has made their own implementation of it because they also made changes like changing the image format for the thumbnail that saved in the gcode.
also important to note that Prusa is running all their stuff on the printer on bare metal instead of having basically an entire operating system layer in between so they probably optimized for that as well.
I'll have to talk to the board engineers and figure out why those decisions were made :)
Link to the campaign to SHAVE MY HEAD FOR THE SMF!!!: www.justgiving.com/campaign/smrrfheadshave
Grant, sounds like your enjoying the XL. So have you honestly experienced any set backs? Mine just shipped today, (fully "partially" assembled). lol So I'm hoping for good results and excellent tool accuracy. I already have ideas for custom tool heads I might try to make down the road.
Haven't had a ton of time to mess with it honestly, doing some projects and things we can't talk about here, but I did have adhesion issues to the plate. It was recommended that even though I was using alcohol to clean it with, dish soap was required at least once. I'm not used to the satin sheets.
Some other issues with adding speed in input shaping but it seems Prusa has a work around for it.
Had many adhesion problems on a mk4 w PLA we’ve been evaluating for last 6 mos or so, note these are small footprint parts we’re printing. First did the heated chamber, that got rid of lots of stringing, but ends of thin parts were still lifting/peeling up. We need the bottoms to be very flat; so this was a major issue for us. Got a satin sheet and started using end of Jan/24 and it helped for a while. Then started having issues again. Had been cleaning w 91% & lab grade ipa. Didn’t “see” any fingerprints, but still,probs w adhesion. Tried dish soap, letting dry thoroughly overnight - helped a little. Finally broke out the Dawn dish soap (use it for cleaning oily residue in the machine shop). Wore nitrile gloves while washing. Worked like a charm. Started wearing nitrile gloves whenever handling the plate, much much improved results w adhesion. Don’t think the plate has been washed in 3-4 months? Saw some corner lifting last night on a large (96mmx96mm) relatively thin part; so going to try washing again (resorted to using Mickey ears to get it done expediently). If not containments from PLA (know it’s not those devilish leveling “dots”affecting bed leveling, scrape those off very thoroughly - tip is also very clean) might try playing w chamber temp…that has helped a bit before (also w stringing).
Fixing to order a mk4 kit now that the clogging issue seems to be somewhat mitigated (we had a defective part in the filament path on our factory assembled mk4) between a bad part replacement and the latest firmware update life is much better. Though also looking at the XL…hard choice. Haven’t seen too many print quality comparisons between them online (we’re currently doing .15 & .2 struct-IS layers, .4 nozzle - so far). The MK4s will likely fill out our farm…though that new robo-unit w “slim” mk4s looks real tempting to buy into. Likely a few of XLs too.
Been a road, but getting there.
As always, YMMV. Just sharing, nothing more, nothing less.
I just want to drop a comment of "OMG yes, please add the multi-plate. Drop the ego and just implement it. Blackbox or copy code". I'll note that when I brought this up at a Prusa User Group event, I was told that the hesitancy is if they copied the code from somewhere else and not knowing if they would be following the license. Which I can understand... there are 10k forks of slicers with one off features that go to die... but I also think it's a cop out and they just need to add it. I have talked to a number of people who said they use Orca Slicer over Prusa Slicer (ironically, basically nobody uses Bambu Studio in my circles) and they said the reason: plate management. They have stated they are willing to be a version or two behind in terms of features, if it means they get plate management.
Prusa has pulled code from others before, including Bambu, they even credit them in the latest 2.7 release :) I don't think it's an ego thing and instead an already planned roadmap
@@3DMusketeers I'm not so sure. I've read the Dev comments on tickets that have been around since nearly the release of Bambu Studio. People have asked time and time again, both Github and in person. Both times have been waved off. Most others simply don't get responses and then appear in an alpha. There are easily dozens of times someone responded from a Prusa account on TwitX that they already have multi-bed implemented and it's not a feature they need to implement "because it's already there"
Sad that spiral hop is only used on layer change, not on each z hop inside the same layer
Shouldn't be hard to implement, no? Also, why?
I just used the cancel object on my last print because the part broke free from the support. I canceled the 2 failed objects out of the 10 and keep printing without wasting the whole print.
Niceeeee
If Prusa decided to develop CAD, I worry that they’d need to charge money to justify the additional development. Like slicers, there’s no end to CAD updates/improvements. You still can’t add print pauses in sequential-print mode.
But would that be a bad thing?
@@3DMusketeers I wouldn’t mind if they charged for CAD, but right now they don’t charge for the slicer. I’m hoping it stays that way.
I don’t see a benefit to Prusa getting into the already-saturated market of CAD, when we already have free/inexpensive options that include CAM and simulation. Prusa’s frequent release of new slicer features is impressive, but if they were so great, they’d have added that missing basic feature that someone complained about years ago. Sure, most prints have no need for sequential print-mode pauses, but you could say that about a lot of slicer features.
CAD isn’t saturated. There aren’t any good open source CAD programs. It’d be neat if Prusa very gradually added CAD features, like ability to do OpenSCAD inside PrusaSlicer… while integrating ability to click to select objects and then drag them (perhaps requiring specifically formatted OpenSCAD variables?) and then maybe later, ability to click to select edges to add fillets or chamfer. That alone would handle like 90% of my CAD needs. Evolve slowly, only adding features where it makes sense. But yeah, OpenSCAD integration would be a useful addition and would put Prusa on its way to becoming CAD.
@@TheAnachronist It depends what you mean by "good". Compared to solid-modeling CAD from the 90s, today's open-source CAD is good enough. Compared to modern, closed-source CAD/CAM/Simulation packages, it's not.
I don't object to adding a few basic CAD features to PrusaSlicer, but it's a slippery slope. I could see them diverting much of their attention away from hardware, firmware, and slicer-specific improvements. I see more value in them focusing on their specialty. For example, they could add extruder-current/torque/speed monitoring to check for filament slipping or underextrusion. Alternatively, replace the filament run-out sensor with a filament position sensor (mechanical or optical), and compare it to extruder position, to monitor the filament slip ratio. A nozzle-backpressure transducer or AI-camera system could monitor over/underextrusion. Automatic live-adjustment of extrusion would take layer-adhesion to the next level.
Developing CAD is a monumental project. There's a reason the good stuff costs money. Prusa would add another half-baked solution to the pile, if they dilute their efforts with a side-project that is outside their area of expertise.
Prusa absolutely needs to make their own CAD program or simply Fork FreeCAD and throw 90% of the features out while making the remaining 10% work really good.
Eh I don't know if I'd like to see their dev teams split up you know?
@@3DMusketeers Dev teams within Prusa or the ones working on FreeCAD right now?
Because internally Prusa would absolutely need a separate team to work on a CAD program but obviously that would cost a lot of money for a long time.
I would love an overview of support settings.
Can do!
Over the Thanksgiving break (for us in the US), one of the more prolific plugin authors for OctoPrint (specifically jneilliii) created a plugin for said software that can receive a binary gcode (.bgcode) file and convert it back to ascii for OctoPrint usage. (AFAIK you can't stream the .bgcode file over the serial port and expect the printer to do anything. Serial port is for ASCII gcode transfer only. This may change, or I'm wrong... Also none of the other OctoPrint plugins that scan gcode for things like thumbnails, print-times, live gcode printing views, capture event triggers, all the things that OctoLapse does know what bgcode is, or even now needs to.) When I installed it this past weekend it wasn't available in the OctoPrint plugins repository yet. I installed it from the plugin's GitHub repository. I'd provide links, but RUclips doesn't like that. 😕
This was possible because Prusa released the c library to encode and decode the bgcode format as open source.
Gotta love open source
TeachingTech made a video about ramping up and down for Z hop a year or so ago. I wonder if someone at Prusa was inspired to keep it going?
They grabbed it from Bambu studio, it's in the notes. Maybe Bambu got it from there though?
@@3DMusketeers TeacingTech's video was posted about 10 months ago and asked the community for help testing to see if it was useful for everyone. Maybe Bambu was "inspired"as well lol
I think I'll stick with ASCII gcode for now. I see the need for some to use it, especially those with smaller storage or use SD cards. For me I wont' worry about as my gocde files are always on Linux systems with a BTRFS filesystem with compression enabled (compression-force=zstd:1), and this drastically reducing disk usage for gcode files already (laptop is Ubuntu, printer has Octoprint on Debian). This reduces the file sizes about 50% by itself, and I could add some de-dup if I really cared, and archive old files in a compressed format if needed. Compatibility and edit-ability are much more important for me. I won't knock those who want binary gcode, tho, if it works for you great. Add support at least.
I believe they are working on a translator in case you get a bgcode file and need a normal one. We shall see.
Something changed with how 2.7 sets print speed.
With 2.6 and prior if I set all my individual speeds to zero, and utilize the auto speed function set to 100mms. Then the algorithm clearly tried to target 100mms as much as possible. Only slowing print speed for small features and to normalize flow.
Now with 2.7 it seems as if the slicer prefers to target almost exactly 50% of my max speed setting. If I set 100mms, it slices 99.9% of my prints around 40-50mms.
I have tinkered with settings for hours now trying to figure out what is causing it to want to slow down. So far only thing I can find that gets my average print speed back to where I want it. Is doubling the max speed limit. But I fear it’s going to sneak up on me and try to print at 200mms some time randomly. Which my printer just cannot support.
That's interesting. I've never done it that way. Worth seeing if there are notes about it?
An interesting limitation of the cancel object, at least on my MK4. I was printing some more filament clips in a batch of 100 (so I never have to print them again unless I wanted to change plastic types which is why I was printing them again). I was having trouble getting them to not be knocked loose because I had the stupid idea of printing them in ColorFabb HT. Before I broke down and decided to print them on a raft (which did work), I tried to use the in-printer cancel object feature. It only showed 16 of the 100 objects to cancel in the list, and even the "cancel current" didn't seem to work on the ones that I needed to cancel (which I think were object numbers higher than 16). There seems to be a quantity limitation.
Interesting! Any idea if the issue has been raised?
@@3DMusketeers No clue. Haven't bothered to check yet.
Love all your content. Newbie here. I need to know a good resource to walk me through settings in a slicer, starting with how you choose a slicer (can I use them all with Bambu X1?). And like the file types: stl, step, obj, etc. etc. etc. Learning as I go! Loving it. Very exciting! ... oooo, excited for next week's video about newbies! *raises hand.
That's a great idea. I'm going to add this to a list!
Huh? How exactly can pressure equalizer help, according to you, heavy machines that have slower acceleration when it is only a restriction. It limits something; namely the acceleration/deceleration upon changing from one feature to another (e.g. from infill to perimeter).
it ramps up the extruder, it is quite useful on BIG bowden printers.
Sure it has a 'ramping style', just like acceleration is a ramp up, but in the end the pressure equalizers only effect is to slow the faster features down when it is transitioning to and/or from a slower feature. If you have both positive and negative slope enabled, a transition from 50mm/s to 100mm/s will make the 100mm/s feature go from 50 to 100 by means of the positive slope, even if it were going in a straight line (so regular acceleration is a separate limit). The feature that had the 50mm/s to begin with is not affected. For 100mm/s to 50mms, it slows the first feature going at 100mm/s down to 50mm/s.
So again, how is this relevant to big printers specifically aiding their acceleration?
If I knew specifically how to describe it I would.. But I have a BIG bowden printer (1M bowden tube) and with that ramping thing it works AMAZINGLY well, without it I have issues with the start and ends of lines. It is really odd.. Sorry, the limits of my technical knowledge have been hit ha ha, but I can ask others?
There is so much more I need to learn man. How is the course planning going? I'm going to need to take a few
Slow.. not a ton a time these days
What I want to print when my XL arrives...is something decent sized with a good amount of supports that are printed in soluble filament.. Any suggestions folks?
I'm looking for something similar. May scale up something from Fotis or Wekster
Danke!
Thank you!!
Do you have an ETA on when you plan on working on that Bambu X1C you have?
In 2 weeks likely
"Tail end, if you will" I see what you did back there.
Aaayyyeerre
I can't imagine you'll ever see IS on a mk3 natively. It's probably slightly more powerful than my Commodore 64. lol Hell my USB cartridge for my commodore 64 has more power than the computer does. lol
Yeah, Prusa is cramming about as much as they can already into the limited programming space of the chip on the MK3 processor board (I think it's the same processor as on an Arduino Mega). Even if they could fit the IS routines on that processor, it would be really slow. The chip doesn't natively support floating point math. It's amazing that Prusa is able to get that processor to work as well as it does on the MK3.
I'm sure someone, somewhere, will find a way LOL. I'm curious to see what they come up with
@@3DMusketeers you can play doom on a C64, but you really don't want to. It looks like crap and it's slow as molasses. You can only do so much on 8 bit.
PrusaCAD would be great for beginners!
Agreed
About the slicer, how to change the number of wall loops for part of model?
you can use a modifier for that. I've used them to adjust infil percentages.
@@awilliams1701 This is awesome, thank you very much!
Yep modifiers both as an STL or just layer height based
How about a video on how to make organic supports work better?
Sure we can do that!
How to configuration .8 Nozzle setting in this software
You can go to your printer settings and change it there then under the print settings you change the flow widths as well.
@@3DMusketeers thanks
lf possible to make tutorial video
I can work on that
Prusa would make a CAD package, then a week later Bambu will release the same thing in a different colour…😂
Cute. Arc fitting, objects exclusion is already in bambu studio and bambu printers. SVG support has been available since 2022. If you think Bambu studio is just a "color" swap you are need to lay off the Josef juice.
Binary gcode is no different from how Bambu studio handles 3mf files. It's a zip container. I can take an 8mb 3mf file that is actually 50mb in size extracted. This includes multiple plates, photos, and project info. This is nothing new. BUt since the mk4 uses such crappy network protocols it needs to shrink all that data into manageable sizes so it can choke on it still.
Heck Prusa slicer could not even handle Step files until Bambu implemented it. I cant wait until Prusa research invents multiple plates. 😜
Boy the replies here went to 11 without any reason...
Technically bambu could dead copy it and assuming it's in open source it would be legal. Welcome to open source.
I agree, but to then patent concepts you took 80% of the development from open source isn’t great - this just kills open source right?
I could have used this months ago when I had to learn cad to emboss a model 😑
LOL been there before.
I believe that binary gcode is for their poor file upload performance to their machines.
I think so as well it seems
Prusa should not make a cad program, they should make a 3D printer CAD program that is also a slicer.
It would be quite the effort needed though, likely a whole new team. Would you be okay with having to pay for it if they did?
You getting finally shaved is awesome, time to stop looking like a bum =)
Lol my mother says the same thing....
@@3DMusketeersListen to your Mom!!
I don't see the point in editing gcode. I'd rather just re-slice it. Since getting into 3d printing I'm like.......why the hell is this in ascii? It's such a massive waste of space. I've watched my pi fill up with gcode faster than the timelapses. So hell yeah! I prefer the the idea of bgcode. I hope this gets adopted as long as it's open source.
When you need to print hot but need to slow down for bridging, you can't set different temperature just for bridging of a section (to not overheat the filament) in the slicer nor using custom gcode as it's inserted per layer basis. You need to open the gcode, find the section and insert the custom gcode to change the temperature and back after the bridging is done.
@@hologos_ if it's 5 degrees it's not going to be that big of a deal. If it's 10 degrees it's not going to change fast enough to matter. And if that really is an issue, then you need to tell prusa not me. Then you can set it in your bridging settings. Also while I have no intention of editing bgcode, it sounds like it's not hard to edit it.
An edge case that I've used rarely is to be able to scan through my generated gcode to find issues, or actually figure out in what order the custom gcodes in PrusaSlicer are applied. But, some plugins for OctoPrint absolutely rely on being able to scan and parse the gcode (either as a separate scan process, or monitor the serial stream for triggers).
@@awilliams1701 Do you know there is a gcode that waits for the temperature to reach the target? :-) By the way "tell it to Prusa not me" - then don't put your opinions on the internet if you don't want to be confronted. 🤷♂️🤦♂️
@@Sembazuru I'm sure octoprint will get support eventually. And I check my gcode too.......in the gcode viewer. lol