Today I learned that 3d printers are actually programmable with G-Code

#programming #gcode #3dprinting

Laser Engraver Uses All of the DVD Drive - For the last ten to fifteen years, optical drives have been fading out of existenc... - https://hackaday.com/2023/08/10/laser-engraver-uses-all-of-the-dvd-drive/ #opticaldrive #steppermotor #laserhacks #carriage #dvddrive #engraver #arduino #gcode #laser #cnc

@koz

The other thing is. With #PrusaSlicer in the printer's custom #Gcode where you set the start, end,layer-change, etc. Gcode. You can access variables such as temperature and layers, etc.

You, however, can't access variables like acceleration limits and use those values to emit them to your Macros when you run #Klipper.

So I need to look at a print, think a bit. Set limits in Klipper, transfer said limits to #PrusaSlicer, generate gcode, and then print.

#OrcaSlicer actually will honor your request to print slower or faster, but there is something wrong with its flow rate.

If you slice an object and switch to the flow-rate view. The color codes clearly show that it exceeds your set max. However , in speed-view, you can see that the speed is correct. And in #Mainsail during printing and can actively see how it changes the acceleration limits as it prints overhangs, perimiters, and briges.

As you can see, I am between 2 slicers here

@3dprinting #3dprinting

@koz

Unfortunately, I stopped caring about the acceleration limits and everything in #PrusaSlicer since I started to run #Klipper because it actually tells you that the limits are only for time predictions and aren't Ctually emitted to #Gcode.

But when you use #OrcaSlicer and you insert custom accelerations and dynamic-overhang-speeds and limits, the printer actually honors it.

So, not only are my time predictions with OrcaSlicer more accurate, but I am actually printing at the rate that I want to and chose in the slicer.

But then finally, I have to say. OrcaSlicer does not honor flow-rate limits as well as PrusaSlicer does. If I tell PrusaSlicer to never exceed 12mm^3/s, it would slow itself down.

OrcaSlicer justs YOLOs itself past that limit, and my exteuders start to skip!

@3dprinting #3dprinting

I friggin <3 HexiBase.

I don't think he's on the FediVerse, but he keeps the DIY YouTube audio engineering flame alive like no other:

https://www.youtube.com/watch?v=L4xz3XamNKo

#HexiBase #DIY #Audio #AudioEngineering #GCode #CNC #3DPrinting

@fabbaloo

How does this work without a sensor? Is the tuning similar to #Klipper without a sensor? I see some people speaking of hard coded #Gcode files. How does that work? Then, the input shaping is not unique to every printer's construction?

@3dprinting #3dprinting

Industrial Robot Gets Open-Source Upgrade https://hackaday.com/2023/05/14/industrial-robot-gets-open-source-upgrade/ #RobotsHacks #controller #industrial #opensource #LinuxCNC #ODrive #Fanuc #gcode #robot #fpga

Holograms Display Time With ESP32 https://hackaday.com/2023/05/05/holograms-display-time-with-esp32/ #microcontroller #beamsplitter #clockhacks #hologram #clock #ESP32 #gcode #model #prism #3d

Holograms Display Time With ESP32 - Holograms and holographic imagery are typically viewed within the frame of science... - https://hackaday.com/2023/05/05/holograms-display-time-with-esp32/ #microcontroller #beamsplitter #clockhacks #hologram #clock #esp32 #gcode #model #prism #3d

In #PrusaSlicer, which setting takes importance between Filament-settings and Printer-settings?

If you set retraction and z-lift parameters for a specific filament but also for your printer's extruder, which one is chosen?

You can't say that the Filament-settings are more important because what if my exteuder is limited in retraction and extrusion speed?

But then you can't say that the Printer-settings are more important, because what if I need retraction length for a specific filament?

So, just disable it for the one or the other? That's the problem, you can't, so I just changed it and set them as the same on every print, depending on what I am printing with.

Just feel it's unclear and bad #UI. They need to be more clear on how this works. But then again, the documentation for #PrusaSlicer leaves a lot to be desired for the more complex stuff like variables and custom #Gcode.

@3dprinting #3dprinting

@geekandi @infosecdj @OttersDangerDen @astrovore

If I were to add fans to my steppers and heatsinks, how can I configure them to turn on when printing? The easiest way is to just have a macro, but meh, where is the overkill?

So i was thinking. I turn the steppers off at the end of a print with M84, I think? To turn the steppers on again, I just home the pronter because they could have lost position.

Is there a #Gcode command to turn steppers on which is executed before homing, G29, that I could rename and add code to turn them on?

Alternatively, I could just make them temperature controlled and turn on using the hotend temperature because that shows that I am printing. And they don't move enough to become hot if I don't print.

I am also looking at the tension on my belts to see if I can also lose a bit.

@3dprinting #3dprinting

@ziti

#Cura was great when I got my printer. It is very easy and user-friendly. You choose the "detail" setting which ditectly transaltes to your layer height and it does everything for you. For my first 2 years, I didn't change anything in the settings.

Buy I then switched to #PrusaSlicer and created my own profiles there. Now, it is my daily driver, and I enjoy it more than Cura for advance settings and adding and changing #Gcode.

@3dprinting #3dprinting #slicing

I found this set of #Klipper macros.

It is quite interesting. The creator attempted to almost create a standard for #opensource macros and how one should set up your config and macros to make it compatible and easily extendable with other macros.

I quite like the idea, but I am not completely sold at this time.

One reason for this, is because my enclosure heaters aren't controlled by Klipper and PWM, it is controlled by an #ESP32 over MQTT, because the #RaspberryPi doesn't support the zero-cross interrupt of the dimmer module.

So my enclosure heaters aren't defined as normal heaters, but rather as an output, which sends an MQTT value to a topic.

I might be wrong and will do some further investigation, and I might be able to extend this to support my setup. One way would be to change the M141: Set Chamber Temperature (Fast) #gcode

https://github.com/jschuh/klipper-macros

@3dprinting #3dprinting

@geekandi

I never compiled #Marlin myself during 3 years. Was always through #Gcode or slicer settings. The effort was just too much.

@severedaffect

@3dprinting #3dprinting

Finally, I installed #Moonrakerz the #API service for #Klipper.

My printer doesn't support a chamber natively, so I used the #EnclosurePlugin from #Octoprint to measure the enclosure temperature. I then modified the source code to take that sensors value and inject it as #Gcode that #Octoprint actually thought my printer was enclosed.

Using the #MQTTPlugin, this state was then communicated to a #Mosquito #MQTT server, which an #ESP32 then read and dimmed my heating lamps with a PID controller to get the enclosure up to 60°C.

The #EnclosurePlugin also controlled the power of my printer, visual lights, and then this sensor.

This is now obviously broken.

@3dprinting #3dprinting

RT @Barnacules
I may -or- may not be building a LDO Motors Voron 2.4 350mm #3dprinter kit in the coming weeks depending on how many LIKES & RETWEETS this post gets over the next 7 days! 🍿

#JustSaying #3dprinted #3dp #comeback #shouldi #3dprint #makerspace #maker #opensource #corexy #gcode… https://twitter.com/i/web/status/1646007543859392512

@wookiearocket

The argument about whether to use post-processors or implementing it directly in the slicer is similar to the argument of addons, mods, and plugins to existing software.

I like the idea of post processors, and #ArcWelder is by far my favorite.

During my time in the space, slicers have gone from not being able to print round circles to organic supports released the last few weeks.

The idea behind ArcWelder is amazing.

One benefit about post-processors is that you can improve existing #Gcode after they were created and improve them without having access to the original model.

@MaryPot

@3dprinting #3dprinting

@MaryPot

I crossed paths with a post by @Stark9837 earlier that reminded me of an alternative to manipulating the source geometry/resolution; the slice could be post-processed further to substitute the multiple short lines with fewer arcs in the #gcode.
#3DPrinting
https://plugins.octoprint.org/plugins/arc_welder/

@geekandi

I actually installed #Klipper and #OctoKlipper today after running #Marlin for 3 years now.

I wanted the macros that came with Klipper, so I am excited to write my own color change macros now. Currently, all my scripts are in #PrusaSlicer in the custom #Gcode inputs.

So I have my work cut out for me.

@RobeeShepherd

@3dprinting #3dprinting

@stooovie

It isn't as bad printing from an SD card or #Klipper but still occurs. Even #Klipper can lag behind. It comes down to, too high, that a resolution could literally result in 1000s of G1 movements for tiny circles. Say what you want, but even Klipper can't handle that. Because Klipper would still do 1000s of G1 movements.

G3 movements replace all of those 1000s mocements to an actual circular movement and also to a single command.

So even if you don't see the bulges, your #Gcode will be compressed in the sense that it reduces the total amount of commands.

I once had a 34-hour print, which was about 40MB in #Gcode, using #ArcWelder and replacing all of the circular motions with G3, I reduced the size to 17MB on Gcode. More than 50% compression, which helps a lot when you have a cheaper 8-bit printer, will very little RAM.

It's the law of big number, the less lines you have, the less possible things can go wrong.

@3dprinting #3dprinting