I wouldn’t lean too much on their open source sales point. Yes, it’s open source, but there isn’t much more to that than a custom config for Klipper. The engineering diagrams on their GitHub are mainly just standard measurements for fans and such. They do include their own custom parts measurements, so that is nice.

Cheap printers come with cheap parts and sub-par QA. I have heard great things about Sovol, but also very bad things about Sovol.

The SV08 has been around long enough now so maybe most of the bugs are worked out. If Sovol didn’t solve some problems, the community likely did. It’s the nature of 3D printing communities, after all.

If you want a cheap printer to be a workhorse, it needs to be disassembled completely and rebuilt after inspecting and replacing any critical parts with quality ones.

These kinds of printers are just what they are. They work great until they don’t.

Fuck you. Quit playing victim you sack of shit.

The weight test is typically super useful when you want to maximize extrusion rate. Even though it can be minimal, there is almost always a correlation between printed plastic weight and temperature.

My thought here is that you are just within the minimum temperature range for that particular filament. If the hotend temp drops while it is printing, even just a hair, it’s binding the extruder enough to cause this artifact.

My second thought is that the bed/hotend heaters are sagging the power of the entire system just enough to slow the steppers down a hair when they turn on. Testing this theory is not trivial and requires some EE knowledge and an oscilloscope. In the worst cases, the power supply would start to get really hot from hitting or exceedibg current limits. (If this actually is a deeper issue, I would check to make sure your kitty didn’t insert some rogue resistance into your electricals by way of chewing on the wires. The wires themselves might be getting warm in those spots, if that is the case.)

I would PID tune the hotend temperature. It doesn’t look like a mechanical fault like a stepper motor issue or belt.

If you look at each layer, the striping is offset every layer somewhat consistantly and it looks like something is turning on and off on a regular interval, with the same pattern of “blips” in between. (The stripe seems to happen every x mm of printed line.)

Plastics will behave and look different depending on what temperature they are printed at. There are typically glossy and matte sections in every print, actually. You may be hitting a temperature range at one of those texture-transiton points. A few degrees high, it may be translucent. A few degrees low, completely opaque. If that range is within your existing PID tune, that might contribute to the visuals here.

Even with your micrometer, you are only measuring the widest layer over x layers. If your temperature is not stable, it could also contribute to some lines being thinner and more translucent.

Testing extrusion rate by weight is a method that might be good here. Print 100mm of filament into a blob and weigh it. Change the temp a hair, print another blob and weigh that. Create a chart of 10-20 tests to see if there is a spot where extrusion is inconsistent. In your case, we want to replicate that striping, but for a weight test instead. The weight of the blob will change if hotend temperature is affecting extrusion rate. You need a good scale and preferably one that can weigh into hundredths of a gram. That precision is not required, but it helps.

The reason I suggested a weight test is because your temps might be swinging between a temperature that is good and also just a hair too low.

The hotend “heating response” might be laggy, is my guess, regardless of what may be causing it.

Edit: The hotend temperature is kept constant in “bursts” of power. There might be a threshold where the hotend power is just full-on.

Represented in a series of H’s and L’s (H for high, L for low), here is a pseudo-representation of what I see each layer and it matches a heating pattern of hotend but with a lower limit where its “full-on” heating:

HHHHHHHHLLLLHHLLLLHHLLLLHHHHHHHHH…

It’s not a perfect pattern in your case because a dozen different things contribute to final nozzle temperature.

No.

I think the concept of stars literally hitting each other is rather moot

In many ways, I agree with you. I was simply trying to paint a picture of how much space is in between stars. Visualizing the scale and distances of the universe can be extremely difficult, so I opened with that to help explain why the chances of collision or significant interaction were low. However, given amount of time involved, a significant interaction has probably happened before and may happen again. (Visualizing space and time is hard for me, actually.) With that, I should cap my improbability to “within the time that humanity has ever existed, or will ever exist”.

However, you did get me thinking about disruption on a much larger scale, far beyond the oort cloud. Could a cluster of black holes disrupt our orbit around the galaxy center significantly? Locally, even something of considerable size passing through our solar system can disrupt our own solar orbit, but may only measurable after thousands of years.

We are in a relatively quiet spot in our galaxy now from my own understanding, but if something was able to bump us (and hundreds of thousands of other stars) just a hair, it might have dire consequences in a few million years. (I wouldn’t imagine that we would notice getting kicked out of our own galaxy completely though. Dunno.)

It would be really interesting to see a fleet of glowing shlongs dropping out of the sky.

Tiny chance of that. When, and if, the the Milky Way collides with Andromeda, the chances are still astronomical that any stars actually collide at first. Shit might get really weird as the SMBHs start to come together and the centers of each galaxy eventually begin to merge, though.

That example was about how far things are from each other in our galaxy. The biggest problem is how much gravity is in play and how fast objects in the universe travel. An object like a planet and a blackhole only have a very narrow space to actually collide or have the planet get locked in orbit or a death spiral around a black hole. It’s more likely a planet would get accelerated and spun out on a very different trajectory when they get close together.

So, your hope of us colliding with a blackhole is very unlikely. It’s probably more likely we would get shifted into a different orbit around the sun or get kicked out of the solar system completely. If you were just wishing for hell and chaos, you would still get your wish in that regard.

Still, if we could survive the extremely deadly area around a blackhole, it would be kinda neat to fall into one. In theory, time and space is so wonky, we should be able to catch a glimpse of the end of the universe before we get crushed into an infinite point. Neat.

Their marketing department is lagging it seems. They are running Chinese language ads on YouTube to US audiences.

It has a still frame of someone skiing or snowboarding, a QR code and the Chinese language description. Wut?

deleted by creator

Of course I do, but its very conditional in your case. For the record, I did miss that you had port forwarding enabled already and read your post as if you were just trying to connect to the open internet and see any traffic going to some rando servers. That would be a very different situation.

How is the traffic proxied locally? Does the VPN client even allow inbound connections? Is a virtual interface configured for the VPN and is there an inbound port open?

What makes this situation conditional is that there are several ways your VPN client could be configured and it is my guess that it is the bottleneck in this case. If you tried every address that you could find and saw nothing, chances are, there is no traffic to be seen. Any stateful firewall will drop an inbound SYN or traffic not related to an established connection.

Your routing table may give some good clues as to where traffic is going as well. For example, the VPN client could be creating a local default gateway IP. Unless there is a split path configured, all traffic should be traversing that IP, regardless of what it is.

So, can you elaborate more on the route your traffic is taking? Listening on 0.0.0.0 can sometimes work, but usually a specific interface needs to be defined as well. In some cases, tcpdump setting the interface to promiscuous mode can break things.

Also, it’s a VPN. How traffic is getting routed in through the tunnel could be problematic. I have just been assuming that everything is fine up to the client you use and the computer sending traffic to inside your network is part of the VPN.

Ok, you are putting the cart a few steps before the horse here and put simply, you can’t just tap the entire Internet from behind your own Internet connection and “through” a VPN. (A VPN “tunnel” is a bit misleading on how traffic is seen in the wire, but that is still many more steps ahead.)

Watching pcap is cool, but you need a fundamental understanding of networks and network protocols before you can actually see more than characters of the Matrix and understand what you are tapping into from the start.

To kick off your own research path, start reading into the OSI Model, TCP vs UDP, traffic routing and subnetting. You need to understand where you need to be to see the traffic you want to see first.

Unfortunately, I can’t begin to answer your question without some foundation in place first.

Have you ever considered not paying attention to what people say back?

I have never considered doing that at all. It happens naturally in the middle of conversations.

It is said, bitch! Don’t you listen?

I have spoken.

Wut? Was he talking about the previous Ukrainian government, sponsored by Russia™? I can’t make sense of what he is saying, actually.

Not sure if that will help in this particular case, but that looks super neat anyway. I have been planning to build a custom modular synthesizer so I’ll try that out anyway. (Thankfully, it’s Kicad integration is free. Yay!)

Just what you would expect from the CEO of an AI company. Fucking idiot.

Having v-cache on one CCD is not an issue. It seems most of the scheduler issues have been fixed and that was just software. It would be nice to have v-cache on both, but it actually adds more complexity.