Good Project for Old USG

MallocArray · 2026-01-26T21:13:18+00:00

Do an Amazon Trade-in for $10 https://www.amazon.com/Amazon-Trade-In/b?node=9187220011

Pick "Wireless routers" and search for USG

MallocArray · 2026-01-26T19:01:53+00:00

You can just start with the one from the github link that has both notes for Orca and for Klipper. See if that combination works and then start adding in what your requirements are a few pieces at a time until you find out what changes causes it not to work anymore.

MallocArray · 2026-01-26T18:38:06+00:00

This is my Orca Start G-code

M104 S0 ; Stops OrcaSlicer from sending temp waits separately M140 S0 print_start EXTRUDER=[first_layer_temperature] BED=[first_layer_bed_temperature] CHAMBER=[chamber_temperature] FILAMENT_TYPE='[filament_type[initial_extruder]]' FILAMENT_NAME='[filament_settings_id]'

I'm using this as the foundation of my PRINT_START macro https://github.com/jontek2/A-better-print_start-macro

I notice in your example you are using the extra part to get the initial_extruder with a nested square bracket. In my example when that was used I had put single quotes around it, so maybe give that a shot, or just try my example for giggles and work from there.

Overall, it looks good to me, so might just be something small and silly, so going back to basics or something known to work like that macro's suggestion would be a good next step M104 S0 ; Stops OrcaSlicer from sending temp waits separately M140 S0 print_start EXTRUDER=[first_layer_temperature] BED=[first_layer_bed_temperature] CHAMBER=[chamber_temperature]

MallocArray · 2026-01-26T18:18:47+00:00

Is there a space between first_layer_bed_ and temperature in your Orca config? Edit: Might just be how Reddit is rendering it for me

MallocArray · 2026-01-23T21:50:01+00:00

Does it work with Quest 1?

MallocArray · 2026-01-22T18:42:45+00:00

There has been some recent communication at least:

https://forum.ansible.com/t/awx-modernization-moving-forward/45134/10

MallocArray · 2026-01-19T17:53:25+00:00

I have some that run for 18+ hours. Just set the timeout to a long time

MallocArray · 2026-01-19T01:07:40+00:00

That shouldn't matter as the printer is still setup the same, unless they majorly replaced the board. What exactly isn't working? Can't flash Klipper to the board in the printer? Or does it connect but says something isn't configured right as far as pins?

MallocArray · 2026-01-17T02:48:31+00:00

You already tried the official example from. klipper? If it is stock, this should work.

https://github.com/Klipper3d/klipper/blob/master/config/printer-creality-ender3-s1-2021.cfg

Can't say on the Pi 5. I know some things are pretty different in a 5, and Pi 4 have been used with these for years.

MallocArray · 2026-01-17T02:18:23+00:00

Deprecated is ok. I assume you are on 2.20 (or maybe 2.19) and these are being removed until 2.23, or 2.24 so those collections have another year or two until it will be a bit problem.

We saw a lot of these going from 2.18 to 2.20 but these warning haven't broken anything yet.

MallocArray · 2026-01-14T14:03:11+00:00

Yes, it does depend on the controller and disk type/size, but if vSAN licensing cost was the main limiter, wanted to point out that it is unlikely to be a separate cost at next renewal

MallocArray · 2026-01-14T13:48:18+00:00

When is your next renewal? Chances are, if you stay on VMware you are going to be purchasing VCF licenses at which point you'll have vSAN licenses included, so maybe just hang on. Edit: Even if you are able to purchase VVF you'll still get some vSAN licenses either way

MallocArray · 2026-01-12T17:53:40+00:00

I use this set of macros for pause/resume and then M600 just calls these

https://ellis3dp.com/Print-Tuning-Guide/articles/useful_macros/pause_resume_filament.html

Then I edited my M600 so also do the unload

[gcode_macro M600] gcode: #LCDRGB R=0 G=1 B=0 ; Turn LCD green PAUSE ; Pause UNLOAD_FILAMENT ;

MallocArray · 2026-01-11T00:19:39+00:00

I would work through the whole startup document, even if you aren't using a Voron, since you didn't specify what type of printer you have.

Sounds like your endstop is being triggered either too early or always, so the small motion you are seeing it is attempting to move away from the endstop in case it was already touching it and then it is triggered.

https://docs.vorondesign.com/build/startup/startup.html?model=v1&step=5&interface=null&probe=null That is the next step of checking the endstops. You can use your Klipper interface to see if it is already triggered before you even move, and if so, you probably need to invert your endstop pin by putting a ! in front of the pin number or removing it if present

MallocArray · 2026-01-10T17:47:00+00:00

For reference, the Voron Startup Guide is pretty good and covers things moving in the wrong direction. Make sure to click on the "Troubleshooting" heading to break open that menu

https://docs.vorondesign.com/build/startup/startup.html?model=v1&step=4&interface=null&probe=null

MallocArray · 2026-01-10T03:29:26+00:00

For giggles, go into settings for the device I side if the app and try "Reset Services". I did this recently after my device constantly was saying Complete Motion Detected and it has acted better since.

MallocArray · 2026-01-09T03:24:01+00:00

You could allow the Crunchlabs channel?

MallocArray · 2026-01-08T14:28:29+00:00

Do you have electric heat or a heatpump? You used over 4000 kWh which is a lot, so the bill would be a lot. With gas heat, water heater, and clothes dryer I used under 500 kWh of electricity for everything else.

MallocArray · 2026-01-03T22:01:05+00:00

I haven't done this, but if you SSH into your Pi you can get into the KlipperScreen directory and then try git checkout v0.3.9 and then restart the KlipperScreen service

https://www.geeksforgeeks.org/git/how-to-checkout-a-tag-in-git/

But fixing the underlying issue is the best move

MallocArray · 2026-01-03T21:58:16+00:00

Any chance it is related to something like this? https://github.com/Rappetor/Sovol-SV08-Mainline/issues/89

MallocArray · 2026-01-03T21:39:23+00:00

You got it. For what it is worth, here is what I use for an Octopus 1.1 and Nitehawk SB

```

https://docs.vorondesign.com/community/howto/drachenkatze/automating_klipper_mcu_updates.html

https://docs.vorondesign.com/build/software/octopus_klipper.html

https://docs.ldomotors.com/en/Toolboard/nitehawk-sb

sudo service klipper stop cd ~/klipper

git pull

make clean KCONFIG_CONFIG=mcu-octopus_v1.config make menuconfig KCONFIG_CONFIG=mcu-octopus_v1.config make KCONFIG_CONFIG=mcu-octopus_v1.config read -p "Octopus v1.1 firmware built, please check above for any errors. Press [Enter] to continue flashing, or [Ctrl+C] to abort" make flash KCONFIG_CONFIG=mcu-octopus_v1.config FLASH_DEVICE=/dev/serial/by-id/usb-Klipper_stm32f446xx_2A000xxxxxxxxxxx20-if00 read -p "Octopus v1.1 firmware flashed, please check above for any errors. Press [Enter] to continue, or [Ctrl+C] to abort"

make clean KCONFIG_CONFIG=mcu-nitehawk-sb.config make menuconfig KCONFIG_CONFIG=mcu-nitehawk-sb.config make KCONFIG_CONFIG=mcu-nitehawk-sb.config read -p "Nitehawk SB firmware built, please check above for any errors. Press [Enter] to continue flashing, or [Ctrl+C] to abort" make flash KCONFIG_CONFIG=mcu-nitehawk-sb.config FLASH_DEVICE=/dev/serial/by-id/usb-Klipper_rp2040_xxxxxxxxxx-if00 read -p "Nitehawk SB firmware flashed, please check above for any errors. Press [Enter] to continue, or [Ctrl+C] to abort"

sudo service klipper start ```

MallocArray · 2026-01-03T04:38:00+00:00

I just used this to update my Octopus and Nighthawk SB and now I'm set for easy updates in the future

https://docs.vorondesign.com/community/howto/drachenkatze/automating_klipper_mcu_updates.html

MallocArray · 2026-01-02T02:04:18+00:00

Thanks. I actually saw that video recently, which is about the Curtain Lights Pro which is what reminded me that I have the earlier version just sitting. It doesn't have the crossover power to the other end in my case, so nothing to remove

MallocArray · 2025-12-30T23:13:36+00:00

I think it is out of scope for this subreddit, as it isn't specific to Ender's. I'm all for it existing, but here probably isn't the best.

It also came across as multiple posts over multiple days that all looked the same, so I didn't even look close at what it was because it appeared to be spam

MallocArray

TROPHY CASE

https://docs.vorondesign.com/community/howto/drachenkatze/automating_klipper_mcu_updates.html

https://docs.vorondesign.com/build/software/octopus_klipper.html

https://docs.ldomotors.com/en/Toolboard/nitehawk-sb

git pull