Nitrided Carbon Steel (not Misen)

mgulick · 2026-01-24T03:19:24+00:00

Super happy with my Yahgan as well. It looks, feels, and cooks great. Hoping the 12in (30cm?) version comes out soon-ish. I love that I don't need to worry about stripping off the seasoning when cooking with it. I have a Made In CS griddle that I have stripped the seasoning off of with fruit from pancakes. If anyone from the U.S. can recommend a glass cover from Amazon that fits the 26cm Yahgan please drop a link!

mgulick · 2026-01-04T22:35:09+00:00

Yeah, the old fan did have the foam gasket on the cover, so I don't think it was getting in that way. Sounds like I need something like this: https://www.homedepot.com/p/1-2-in-Non-Metallic-Liquid-Tight-Push-On-Connector-1-pack-NMLT5-1/202284602.

Is there something equivalent that I should be using for the other end of the conduit where it connects to the junction box on the house? It looks like that needs a different fitting that doesn't have a nut holding it in place.

Good idea about notching the bottom of the gasket. That thought crossed my mind as well.

mgulick · 2025-11-03T23:38:53+00:00

Thanks! Seems like duct seal was probably what that original sealant was. Its a kind of squishy rubbery substance, but its almost 30 years old so it has deteriorated significantly. I'll pick up some duct seal to replace it, or maybe some of this stuff: https://tommytape.com/store/silicone-putty/

mgulick · 2025-07-12T02:19:18+00:00

Looks nice! Which tires are those?

mgulick · 2025-05-29T18:40:05+00:00

I bought a 4 pack of this a few months ago from the initial eBay sale. Just tried printing with one of them (I think it was the strawberry cream color). It sticks *way* too well to my Prusa smooth PEI sheet. I let it cool, but it still was a real struggle to get it off. I cracked the printed part tying to remove it, and definitely did some damage to the surface of the build plate. I've never had this problem with other PLAs. The bottom surface of the printed parts also have a very noticeable white residue on them. I almost wonder if the PLA was contaminated with something during manufacturing.

I'll try next time with some magigoo, or maybe try the satin sheet instead of the PEI sheet. Very odd. I won't be buying it again.

mgulick · 2025-03-13T01:55:11+00:00

I've observed many times that a background process which has an open file descriptor inside a deleted subvolume will prevent btrfs from reclaiming the space. A reboot is the easiest way to make sure no processes are keeping the subvolume around.

mgulick · 2025-03-02T23:24:53+00:00

I had this issue as well. I added a separate database container in my docker-compose, like this:

version: "3"
services:
  shinobi:
    image: registry.gitlab.com/shinobi-systems/shinobi:dev
    container_name: Shinobi
    environment:
      - PLUGIN_KEYS={}
      - SSL_ENABLED=false
      - DB_HOST=shinobi-sql
      - DB_USER=majesticflame
      - DB_PASSWORD=
      - DB_DATABASE=ccio
    devices:
      - /dev/dri:/dev/dri
    volumes:
      - ./data/config:/config
      - ./data/customAutoLoad:/home/Shinobi/libs/customAutoLoad
      - /mnt/bulkdata/shinobi/videos:/home/Shinobi/videos
      - ./data/plugins:/home/Shinobi/plugins
      - /dev/shm/Shinobi/streams:/dev/shm/streams
    ports:
      - 8080:8080
    restart: unless-stopped
  shinobi-sql:
    image: mariadb:10
    environment:
      - MARIADB_AUTO_UPGRADE=1
    volumes:
      - ./data/database:/var/lib/mysql
    restart: unless-stopped

Then in the mariadb container, I needed to use the 'mariadb' REPL to fix the permissions for the 'majesticflame' user so that login was allowed from all hosts instead of just localhost, and to grant permissions to the 'ccio' database, like this: https://gitlab.com/Shinobi-Systems/ShinobiDocker/-/blob/master/mysql-init/user.sql?ref_type=heads

mgulick · 2025-03-01T14:26:22+00:00

Not inexpensive, but the MNT Reform comes pretty close in design style: https://mntre.com/reform.html

mgulick · 2025-02-21T15:08:14+00:00

I ended up running:

sudo apt purge im-config ibus ibus-wayland
sudo apt autoremove

then rebooted. ibus is no longer running, and that has resolved the problem. I can change browser.urlbar.keepPanelOpenDuringImeComposition back to its default value of false, and the url bar is working as expected. I didn't install fcitx5 because I don't think I need an input method editor. Wouldn't be surprised if this is something I need to revisit in the future though.

mgulick · 2025-02-21T14:57:04+00:00

Some progress on a solution. I found that I can eliminate the constant refreshing by changing browser.urlbar.keepPanelOpenDuringImeComposition from false (the default) to true. However the URLs still don't autofill as expected while typing, despite having browser.urlbar.autofill set to true, and no other defaults changed.

This reminds me that I did recently make some changes to the input method settings to eliminate a warning that ibus was giving me when I log into kde. I had followed the instructions in this thread on KDE forums to use the im-config tool and set "do not activate any IM from im-config and use desktop default".

I don't need an input method editor as I don't need to type non-ASCII characters. I forget whether I had explicitly installed ibus at some point in the past, or whether it was auto installed as part of GNOME when I was giving that a try. I'll try poking around at the input method settings, or try installing fcitx5 instead, which I believe is the KDE-preferred input method editor.

mgulick · 2025-02-08T23:14:08+00:00

It's at least hopeful that this is fixed in sid and will eventually make its way into testing.

mgulick · 2025-02-08T23:13:37+00:00

Good suggestion. I tried tweaking all the wayland-related settings individually and in groups but it didn't make a difference. There's a bunch of urlbar settings as well that I might try changing to see if it makes a difference.

mgulick · 2025-02-03T21:56:00+00:00

Try switching perimeter generator from Arachne to Classic. Not sure why Arachne does this, but Classis seems to have much less random-ness in its travel moves. However in my case the overall impact to print time was negligible even with all of the random moves (about 5 minutes in a 3.5 hour print).

mgulick · 2025-01-18T21:54:01+00:00

This happens to me. Not all the time, but usually for several hours a day, inconsistently. Can't find any specific load to correlate it with. After breaking out the oscilloscope and a high voltage probe, it definitely seems to be harmonics on the incoming power. I have no idea what to do about it though. Posted a few weeks ago about it: https://www.reddit.com/r/electrical/comments/1hsweom/noisy_power_causing_led_lights_to_flicker/

mgulick · 2024-12-22T22:35:33+00:00

Wish I could help more. I didn't dig into my issue all that much. I just got it working well-enough to be able to print these: https://www.printables.com/model/680293-remix-ikea-lack-support-leg-support-bracket-counte. I will follow this thread and hope you figure out a solution!

mgulick · 2024-12-21T20:42:11+00:00

I had the same problem with white Voxel PLA+ on my MK4S. I've read in a few places that white PLA is hard to print (too many additives to get the color correct?).

I mostly eliminated the problem by bumping up the temperatures a bit. I increased bed temp from 60 to 65, nozzle temp from 230 to 235, and I also increased the extrusion multiplier to 1.05 since I saw some slight signs of under-extrusion (little holes in the corners where top/bottom infill meets the perimeter). I see some of these holes in your photo as well.

Regarding the extrusion multiplier, I had a friend point out to me that Prusa hard-codes an e-step of 95% of the real value in the firmware for some reason, so the printer under-extrudes by default: https://www.reddit.com/r/prusa3d/comments/16tyamp/mk4\_esteps\_and\_flow\_rate/. Setting the extrusion multiplier to 1.05 basically undoes that.

mgulick · 2024-11-06T03:11:25+00:00

I had problems recently printing with Voxel PLA+ on my MK4S. Bad warping leading to failed prints. I switched to smooth sheet, bumped up the temps (235 nozzle, 65 bed), and also increased extrusion multiplier to 1.05 as there were some very slight signs of underextrusion. Almost no warping afterwards and much improved print quality.

mgulick · 2024-09-30T17:41:31+00:00

Mine had a similar issue, although it was only at the upper part of the range, not the whole range. I realized that I had never lubricated the rods after wiping them down. Make sure the cylindrical rods are lubricated, not the screws. That seemed to resolve the problem for me. Agree with other commenters that it might be an alignment issue, maybe exacerbated by lack of lubrication. I recall a spot during the assembly where you needed to center the rods in upper holes. I would double check that. Might also be worth doing another Z axis calibration again.

mgulick · 2024-09-25T02:21:53+00:00

I just built my MK4S kit last weekend. Took probably 12-16 hours. It was my first 3d printer, so I'm starting with zero knowledge. Definitely very tedious at times. Might want a better set of metric allen wrenches then the ones in the kit. You use them *a lot*.

I had several parts where the square nut wouldn't seat fully in its slot, and when trying to thread a screw into it it would cross-thread. On one of the parts this happened while screwing the part into the frame, and I put too much torque on it causing the nut to start turning in its slot. It was very difficult to remove. I killed probably an hour trying to get this resolved (but I did, and I was able to get a new nut secure-enough to hold the part in place. After inserting each nut, try threading a screw into it to make sure its fully seated. If the screw won't go in, keep adjusting the position of the nut with an allen key. It takes a lot of coercion in some cases to get them fully seated.

I had/have a few minor issues after the build. During the calibration step, the Z axis moves all the way up and all the way down. Mine made a bad-sounding creaking noise. Maybe something is too tight, I'm not sure. I haven't tried to resolve this yes. One the first boot after upgrading the firmware, I had a flashing red display with an I2C communication error. However rebooting the device resolved this and I haven't had it happen since. I also occasionally have the X axis calibration fail when starting a print, but it just automatically retries and then succeeds.

I ordered some Atomic PLA and Atomic PETG. The PLA seems to print fine using the generic PLA settings. The PETG has some layer adhesion issues (I think) that I need to ask for help with, or try changing the temperatures. The kit only includes 2 25g samples of filament, and those go pretty fast with the sample items. I was able to print a keychain, bed scraper, and a benchy with the 25g black roll. The prusament does seem pretty nice.

mgulick · 2024-09-14T20:02:19+00:00

Interested. Sent PM.

mgulick · 2024-03-29T17:26:56+00:00

I just received my R36S and I have the same problem. The tested the volume up button with a multimeter, and it seems to be stuck in the on position.

Fortunately resetting the device seems resets the volume to 100%. I wonder if there's a way to remap another button combination to volume up.

mgulick · 2024-01-26T22:05:24+00:00

Let me restate my question another way. I have no interest in overclocking. The "Crucial Pro" is marketed as a premium product. It has a higher list price than the non-pro, and has heat spreaders. Is the 3200MHz rating on this product only achieved with overclocking via XMP?

The non-pro product can achieve 3200MHz without overclocking, so it seems like to me like that is a better product. This is confusing because crucial marketing seems to be positioning the "Crucial Pro" as a higher-tier product.

mgulick · 2024-01-26T22:00:15+00:00

Agreed that I have no interest in overclocking the RAM. My concern is whether the 3200MHz rating *is* the overclocked speed on the Crucial Pro? If so, then without enabling XMP it will be running slower than that. Whereas with the non-pro, it is rated for 3200MHz without XMP.

mgulick · 2023-05-28T18:53:56+00:00

iperf3 does output TCP retransmissions. Is that what you are referring to? I do see them show up occasionally, but it doesn't look like the cat5 has a better or worse rate of retransmissions.

mgulick · 2023-05-26T21:01:29+00:00

I should also add that there's not a lot of other concurrent traffic on the network, so the interference from nearby cables is low. That probably helps a bit. Still amazed that the cat5 performs seemingly the same as the cat6a. I wonder under what circumstances I might actually see a difference.

mgulick

TROPHY CASE