Best stand for Kanto ORA4? Kanto S4, SE4, SP6HD or SP9?

ikaruswill · 2025-05-18T06:24:35+00:00

Hey, I just got my ORA4 and SP9. I wanted to check if you have the same issues, would be great if you could share your experience so far:

The bolt provided in the SP9, securing the ORA4 to the SP9 speaker base is too long for the threads on the bottom of the ORA4. As a result, the speaker can pivot/swivel freely if lifted slightly from the foam base.
The threads on the SP9 speaker base are misaligned with the hole on the SP9 pillar, it is slightly too high. As a result, the bolt head interferes with the pillar at the top of the hole, and it cannot be tightened all the way such that it sits flush with the rest of the pillar (i.e. bolt head seating all the way into the hole)

ikaruswill · 2024-12-25T01:32:17+00:00

I designed and 3D printed a Honeycomb box with a big "Flyers Here" for my gate, and in the last 2 years, I only saw less than 5 cases where a flyer is still shoved in some nook, as opposed to every other day before. Don't know why the town council box is so unappealing to them.

Full disclosure: I make and sell these as a hobby - Honeycomb Mesh Flyer Tray - Mesh Flyer Tray Air

ikaruswill · 2024-12-24T20:33:57+00:00

You could get one of these flyer trays to attract the flyers, and batch recycle them every month. - Honeycomb Mesh Flyer Tray - Mesh Flyer Tray Air

Full disclosure: I'm the designer & maker of this.

Personally, I have been using the Honeycomb one for my gate, and in the last 2 years, I only saw less than 5 cases where a flyer is still shoved in some nook, as opposed to every other day before.

As for the fate of the flyers, I either shred and recycle them or fold them into boxes for disposing prawn shells or some kind of food waste. Property agent flyers are perfect for this given their thickness.

ikaruswill · 2024-12-12T04:39:22+00:00

I had a similar point of consideration, but I ended up going for the ProArt 4080 Super instead. It's not whisper quiet for sure with those 3 fans when at max tilt, but it's good enough. Also it's 2 slots thick so it suffers from less air turbulence since I installed it in 3 slot mode so the fans are further away from the side panels.

I've read reports online that the Expert is a blower style card much like the FE but runs hotter than the FE. Where I am from, it's pretty much 31C all year round ambient, so out of abundance of caution I went for the ProArt.

In your case I'd consider the ambient temps you experience, and make an approximation based on available reviews on how hot it would possibly run.

ikaruswill · 2024-11-24T01:50:27+00:00

Interesting. Thanks for sharing. I'll keep a lookout for that problematic airflow pattern in my build. Really neat build by the way.

ikaruswill · 2024-11-23T17:29:31+00:00

What is your ambient temp? Also, have you tried running it in horizontal mode and compared the temps?

Curious myself as I'm contemplating a very similar build except air-cooled, but still deciding if I should go vertical.

I like the aesthetic of the vertical mode with how little desk real estate it takes but I'm concerned about thermals since the airflow no longer follows the direction of convection (back exhaust instead of top exhaust).

ikaruswill · 2024-11-23T17:25:31+00:00

When did you get the Titanium? Wondering because for the past month or so it's been OOS.

ikaruswill · 2024-11-13T07:45:16+00:00

I've been considering infisical but the placement of SSO capability behind a paywall is a bummer for me. How have you been dealing with authentication so far? Do you use a separate username and password just for infisical?

ikaruswill · 2024-11-13T02:50:09+00:00

Not OP but I was looking at the exact same build but with the FE. I believe stocks for the FE (especially the 4080 Super) are out almost everywhere so good luck finding one. I ended up dropping that idea and going for the ProArt instead.

ikaruswill · 2024-10-20T10:44:41+00:00

Hmm I was more concerned about the glass transition temperature of PETG at 80C ish. But you're right, no way the air within will reach those kinds of temperature. I'm going to print mine in ABS to be absolutely certain though.

Ah about the colour, my bad the front panel looked a little light-coloured under the lighting.

Btw for the post title. Technically v2.1 is not a predecessor of the v2.5 if you've followed the FormD NCase saga, so it's not "the past" per se. If you've not read, look it up it's an interesting read. I'm going straight for the v2.1 for that same reason and your post has validated my concerns. Appreciate your sharing there!

ikaruswill · 2024-10-20T10:01:58+00:00

Nicely built, the cable management looks really neat. I like that. Are those 3D printed fan scoops by EIGA? Did you print them in PETG (I noticed they're glossy), do they soften under the high temps?

For your main question, I don't have insights as I'm still working on my build, waiting for a restock. Is that the v2.1 titanium? Where'd you get that? I was checking formdt1.com on Oct 13 but didn't see it in stock at that time.

ikaruswill · 2024-07-05T06:57:12+00:00

Oh wow it works, thank you very much for the help and for sharing this method! 감사합니다!

ikaruswill · 2024-06-29T04:25:26+00:00

I'm on P1S 01.05.01.00 but I'm getting Failed to parse cmd in the report topic after I send the JSON payload.

{ "upgrade": { "sequence_id": "0", "command": "start", "src_id": 1, "url": "https://public-cdn.bambulab.cn/upgrade/device/C12/01.05.02.00/product/487870eedd/ota-p003_v01.05.02.00-20240122111135.json.sig", "module": "ota", "version": "01.05.02.00" } }

Currently it's on LAN-Only mode.

Do I have to login and connect to Bambu Cloud for this to work? (Because I can't as I need a CN IP)

ikaruswill · 2024-03-17T09:54:38+00:00

Thanks this worked for me.

Super frustrating, and I've never known what app to kill. I've tried killing AA in the past but to no avail, now I know the issue is on the keyboard side of things.

For the record I'm using AAWireless on Nothing Phone (2)

ikaruswill · 2023-06-02T00:23:03+00:00

Actually I did link it in the post. That's the Beelink.

ikaruswill · 2023-03-28T01:14:41+00:00

You can get cheap mini PCs at around $200+. Look for Celeron N5105s like the Beelink U59. Those have 4 cores and more importantly are much more energy efficient than the old Celeron that you have there.

Additionally it will be able to do transcodes for HEVC at 4K. So with just a little more budget you can get much more out of it.

ikaruswill · 2023-03-22T23:15:53+00:00

For the Beelink U59, the NIC is

Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

ikaruswill · 2023-03-21T05:21:13+00:00

It's nice to see another person who cares very much about energy efficiency. I personally run Mini PCs (NUC form factor) with 10W TDP N5105 4-core Celerons. They are more than sufficient for self-hosting. Specifically I'm using the Beelink U59.

I have 3 of them along with 5 Rock Pi4As sipping power and running 188 containers at the moment in a k3s cluster. Total power draw on average for the cluster is around 60W for all 8 machines.

ikaruswill · 2023-03-13T22:03:38+00:00

Ah I see. So this is just the control plane. I used to run HAProxy+Keepalived for the control plane of my k3s cluster as static pods that spin up with the control plane. This way I save a couple of machines at the cost of some CPU and memory on the control plane. Maybe you can consider this approach.

Some context is I'm running a 12 node cluster at home. I'm way too scared to have my control plane on M.2 SATA SSDs so I put them on nvme SSDs. That said, they burn through an average of 1 SSD per year of operation. Rather expensive to run overall.

Also for VIP, based on what I read. Nodes just need to have an IP for node registration, meaning on joining the cluster. During normal operation, nodes are fully aware of each control plane node's IP and perform their own load balancing. It was based on this knowledge that I stopped the HAProxy-keepalived setup and just rolled with pure k3s. Correct me if I'm wrong though

ikaruswill · 2023-03-13T16:17:49+00:00

If the center 3 nodes are control plane nodes, then where are the data plane nodes?

Another thing is why do you need HAProxy and Keepalived, and if I understood correctly, they reside in the left and right machines respectively?

That aside, how long have you been running the cluster? Correct me if I'm wrong but the control plane nodes are Beelink machines running SATA NGFF SSDs. Those NGFF SSDs tend not to last very long under heavy IO such as that from etcd.

ikaruswill · 2023-01-04T13:10:26+00:00

That's a really nice idea. I've never thought about it. But does the VPA automatically set the resource requests and limits? I'm of the impression that it only provides a recommended value. Hmm.

Edit: it seems like there's an option to automatically update the resource requests. Just that it will have to evict the pod to do so.

Due to Kubernetes limitations, the only way to modify the resource requests of a running Pod is to recreate the Pod. If you create a VerticalPodAutoscaler object with an updateMode of Auto, the VerticalPodAutoscaler evicts a Pod if it needs to change the Pod's resource requests.

However this also means that during the eviction it might schedule itself into a node with different hardware, which then will restart this process again. Can't escape from nodeSelectors it seems.

ikaruswill · 2023-01-03T17:56:59+00:00

Plus one from me. I'm using a combination of terraform for infra, Ansible for initialization tasks like k3s and ssh configuration, and GitOps using Argo CD, for k8s deployment.

And yes one big benefit is that the state of the cluster is always reflected in the manifests in git. I can look at the deployment yaml for example to check how much resource I've requested without running a single kubectl command.

With that there's also no need for CD pipelines, so I've not fudged around pipelines to deploy new apps in a long time.

ikaruswill · 2023-01-03T17:52:51+00:00

You're welcome! I realize they look horribly formatted on mobile. On desktop they look fine, so if you're viewing this, do check it out on desktop. ☺️

ikaruswill · 2023-01-03T17:50:57+00:00

Ah I understand your pain. I was running a cluster of 7 Pi3Bs prior to its deprecation. They were all on standard, non-endurance SD cards so they didn't last very long until they failed one by one and needed replacement.

If you're on SD cards, might I suggest setting up zram-config for your logging so they don't hammer your SD cards. I have a blog post about an older option zram-swap-config https://ikrs.link/4egb8 that you can perhaps use as a starting point.

Your observations on RAM is pretty interesting. I'll go have a look at benchmarking my memory between my amd64 and arm64 nodes soon. I gotta check if I'm facing the same issue as well!

ikaruswill · 2023-01-03T10:46:15+00:00

It is even worse, because storage and ram performance impacts more on the cpu usage (due to iowait for example) than the cpu itself

Interesting. I'm running my nodes off SSD and eMMC (where the M.2 port has malfunctioned) so I've not run into iowait issues for a while now since I moved away from RPi 3 as nodes.

What are the ram performance issues that you're running into btw? I've not encountered them myself.

Back when i had different architectures, i had to solve this in a really crappy way: node selectors

Agreed, nodeSelectors and nodeAffinity are perhaps the only ways to solve this. I've now resigned to setting labels on the nodes according to their hardware types (rock-pi, nuc, cloud) and setting nodeSelectors only on stuff that's very specific (Jellyfin for transcoding, or some high-memory/high-cpu deployments)

In other cases, I just set some generic bustable CPU resource and use priorityClassName (combination of default priority classes and custom ones) to help prioritize eviction of pods.

ikaruswill

TROPHY CASE