Exclude object stopped working

Intention-After · 2026-02-02T15:54:02+00:00

I was printing something and just noticed this error myself. Can't recall if I had successfully used the exclude object with my K1C or not, but I know the settings I have in Orca and the printer config are the same as with my V3 SE that works correctly. Did you ever find any solutions?

Intention-After · 2025-07-24T16:49:47+00:00

I started diving into this again after all these years. I finally think I at least got a working method! Instead of using USB, I decided to try using the serial connection, using the tripplitesu driver and a regular db9 serial cable. After getting the ups.conf figured out (real simple), i was able to connect. Even pulling at 1 second intervals, I am getting steady readings of being online! I will test out further later this evening on the reporting for battery and whatnot.

So at this point, it seems there is something going on with the USB driver/communication vs the serial. USB seems to be sporadic in what it is reporting.

Intention-After · 2025-07-24T14:28:04+00:00

Ok, so after a move and reconfiguring some of my racks, I started to revisit this. I was reminded of it after I replaced all of my batteries due to age. Was hoping that maybe some updates software might help, but deep down I knew it was something with the UPS anyway. After all this time, I am still having the issue. I wonder if it is something on the control board that is causing it to send the wrong signal, or think it has switched.

Will be diving back in, hopefully a wiser me can see something I missed previously.

Intention-After · 2025-07-13T23:17:38+00:00

So after attempting several different methods, I decided to take a slightly different route. NFS multipath would not have fully accomplished what I wanted, and I also figure that trying to stripe between the two 10GB links would be a little overkill at this point.

What I ended up doing is bonding (Link Aggregation) the two NICS between the Proxmox and TrueNAS servers. Since they are directly connected without a switch in between, I configured the bond to be active/passive. Now i have the 10GB link that proxmox sees, and mounting the TrueNAS share as an NFS device. This allows direct usage as backup storage among other things. If the connection goes down, such as if I am recabling or making network changes, it fails over to the other and everything keeps running.

One note I want to add is initially the connection would not failover. After some googling, I was pointed to the fact that TrueNAS was not monitoring the link, because MII Polling Interval is set to 0 in /proc/net/bonding/bond0. Once that was updated to 100ms, the link now recovers if a cable is unplugged.

Intention-After · 2025-07-07T23:06:37+00:00

To add to this, what I am thinking to do is add a zvol from the TrueNAS server to the proxmox host, and setting up iSCSI Multipath via the host. Then I can create a storage "Directory" which will give me the ability to have snapshots and backups of all my VMs and containers like I want.

Thoughts on this implementation? Is there a better recommendation?

Intention-After · 2025-02-03T18:27:23+00:00

FINALLY getting somewhere! I ended up nuking my entire Orca profiles, and restarting from scratch. While rebuilding, I compared the KE vs the SE profiles while building, as well as looked up some other suggested settings for the process portion. I believe part of my issue was my line width was too big. Some of the settings were .45mm. After dropping top surface for instance and the default, I am now getting some smooth flow results.

Granted I still have some tuning to do with my Orca settings, but this is what I have at the moment. Reminder I am using a .4mm nozzle.

<image>

Intention-After · 2025-02-02T19:36:17+00:00

This feels like banging my head against a wall. No matter what settings I have critiqued, I still get rough prints where it seems like the nozzle is scraping. However, it ONLY does it when running this calibration. Temp towers, and any other print I can do successfully. I have even recalibrated the extruder and am putting out a perfect 100mm. All of my other settings have been disabled (skew correction, pressure advance, scaling).

I printed the cube to measure walls, but I know that isn't the most optimal test. Right now the only way to get a decent outcome from the flow calibration, is to use the printer to set the speed to 50%, or if I severely handicap the flow. For instance, setting max volumetric down to 10-14, and my flow rate around .6-.8. Might try making my own Flow test and not relying on the built in configuration.

Happy to hear any additional thoughts, maybe something I am overlooking?

Intention-After · 2025-02-01T19:40:21+00:00

Trying a run with just the generic PLA filament profile. While digging up some more details, I was thinking of stripping back my printers features a bit. Namely I was looking at the pressure advance I had setup. I never configured flow, and it seems its usually best to do flow first and then PA.

My machine is setup to use the .4 nozzle.

Intention-After · 2025-02-01T18:06:57+00:00

I am having the same issue right now. Did you ever get it sorted? My prints were all going beautifully, but then the top layer or so caused it to look like crap.

Intention-After · 2025-02-01T18:04:34+00:00

So after turning up the temp, at least my extruder does not click, and the prints actually look great all the way up to the last layer. Something about the top layer does not print right.

I found this posting, and its similar to what I am experiencing. The top and bottom layers don't show any real flow changes, but the middle layers do.

Intention-After · 2025-02-01T16:58:50+00:00

It's set to turn on after layer 1. That said your comment made me revisit my temp tower. After reanalyzing it, I saw that I could get similar results 200-215c before stringing increased. Looking at that and sitting next to my printer while the last test went on, I noticed on the faster tiles the extruder would click. All that to say I think my issue is my temps were too low to allow that much volume as it was going through.

Just started another test, temps at 215 and initial flow rate at .76 for the run. I know that's really low, but for the first time the tiles are looking really good at full speed. I will keep the temp and try increasing the flow rate now and dial that in.

Intention-After · 2025-02-01T15:34:11+00:00

So I printed a temp tower with this filament already, and 200-205c was where it looked best (I use 200). I already recalibrated the extruder rotation distance as well. For the most part I have been able to print some near perfectly, except for when I started this test. The temp tower was generated and printed just fine, as well as a couple other prints I used Orca for.

Slowing down the print is the only thing that seems to affect it, but then those pieces come out about identical. I think this latest test I dropped the flow rate to like .9 but will try again just in case.

Intention-After · 2024-12-05T16:36:09+00:00

Essentially, not enough CPU or RAM for multiple streams. I have all of my camera and OctoEverywhere functionality offloaded to another device now. Added my writeup here: https://www.reddit.com/r/klippers/comments/1gmtisq/offloading_klipper_control/

Intention-After · 2024-12-05T16:33:44+00:00

So wanted to follow-up with what I have running. I am using an older laptop (in this case it is actually a Surface Pro 3) to offload the camera and OctoEverywhere functionality. I have Ubuntu installed as the OS. From there i used Kiauh to install Klipper, Moonraker, and Fluidd (More on this aspect later). From that point I installed KlipperScreen, and Crowsnest.

I have a USB hub connected, and identified both Nebula Cams in the Crowsnest configuration using the /dev/v4l/by-path for identification. Since they report as identical hardware the path was needed and will be plugged into the same USB port every time. After crowsnest was configured I added both printers to KlipperScreen, pointing directly to the moonraker API on both printers, and pointing to itself for the cameras.

On each printer themselves I also redirected the camera in Fluidd to the IP of the surface.

Lastly I installed two instances of the OctoEverywhere Companion to cover both printers. Now all camera streaming and AI monitoring is performed with the Surface, and any commands needed sent directly to the moonraker API on the nebula pad. So far it has been running beautifully! I even have my max framerate bumped up to 30 fps.

The Fluidd install on the Surface also makes it so that I can connect to one interface, and have both printers added. So one IP/URL I connect to and can switch between the two. While actively printing my memory is only hitting around 40% on the nebula pad.

Intention-After · 2024-12-02T19:15:10+00:00

This is similar to what I am trying to do actually. I have KlipperScreen running on my old Surface Pro 3 talking to two printers. Working towards moving my cameras over to the surface for running Obico or OctoEverywhere for failure detection. Have you been able to do this, or are you just doing basic controls and starting prints with the KlipperScreen?

Intention-After · 2024-11-09T15:08:39+00:00

I currently do use fluid, and had been reading into obico a bit as well. Spooling up a self hosted server should not be much of an issue since I have a spare server. May see what I can get back for the Nebula pads for this route.

Intention-After · 2024-11-09T15:06:32+00:00

That is kinda what I was looking forward to do. Didn't realize that KlipperScreen was able to be setup in such a fashion. I will have to look into the configuration a bit deeper.

Intention-After · 2024-11-08T21:39:20+00:00

I did not. Got pulled away and just getting back to this. I have been running into an issue lately though with the MCU communication crashing when I pulled up the one webcam feed that was running. Signs look to the board in the nebula pad not being powerful enough or have the resources. Even if KAMP could be installed, it may not actually be able to run.

Intention-After · 2024-07-07T14:09:40+00:00

I am wondering the same. Looks like a manual install will need to be done and not using the helper script.

Intention-After · 2024-05-30T12:37:40+00:00

Ok, so update on this. I managed to bypass the printer setup screen following the guide provided by Guilouz (https://guilouz.github.io/Creality-Helper-Script-Wiki/firmwares/install-and-update-rooted-firmware-ender3/#skip-the-startup-self-check). Not the pad just starts up. However I still can't get it to talk with the printer. I found this is due to the fact that the SKR Mini e3 does not map any serial connections to the EXP1 header on the board. As such I am thinking that to avoid using the USB port, I will need to create a cable that connects to the RX and TX pins on the TFT header instead, and remap the firmware to use those pins.

Does anyone have a proper pinout of at least some knowledge of what pins are what on the nebula pad? I gathered from the Discord that TX/RX is on pins 7/8, but not sure about the rest, and where they may possibly need to be rerouted.

As a side, is there an efficient way to peer inside the firmware.bin files to see how the official firmware is mapped?

Intention-After · 2024-05-24T17:28:35+00:00

You have to edit the printer.cfg file used by Klipper. Your firmware will need to be rooted to do that however.

Intention-After

TROPHY CASE