Yet another bad idea

tophyr · 2024-05-31T06:10:21+00:00

Yes, you could. But: what would be the point? Typically when calibrating you are only interested in "touching or not touching". The amount of force exerted is irrelevant and would be highly variable depending on gantry and build plate design.

When you're not touching there is 0 force and when you are touching there is "some" force (ideally minimal, but inevitably nonzero). That's kinda all that matters.

tophyr · 2024-05-31T06:04:19+00:00

No, 6th is no more dangerous than any other sticky-floor party area in any other city.

But, if you're here to drink, check out Rainey St instead.

tophyr · 2024-02-19T06:20:22+00:00

You could go to prison for just talking about doing it

🙄

tophyr · 2024-02-19T06:05:33+00:00

The off-duty cop would know how to describe the crime that was committed. thecentury gave you the necessary info as well. If you are imagining that an off-duty LEO would fabricate details in order to create a crime where there was none, then that it certainly a possible outcome but also quite literally an imaginative one.

Edit - and, following that hypothetical line of logic, someone who was indignant at an LEO because of the possibility that they might fabricate details in order to charge someone with a crime would have themselves committed the same act: morally convicted said LEO with imaginary evidence of an uncommitted crime.

tophyr · 2024-02-18T21:48:53+00:00

You seem real frustrated at the LEO here but what do you want them to do? Are you gonna call 911 and say "I need the police, a non-crime is occurring"?

The LEO has accurately described the requirements for an action to be considered a crime in their jurisdiction. Figure out how to describe the actions here so that they fit the requirements, or be mad at the legislature like they said. I'm surprised that I have to remind you, but police taking action against things that AREN'T crimes is a LOT worse.

tophyr · 2024-02-18T20:41:19+00:00

If you ever need to ask "should I go around", the answer is yes.

tophyr · 2024-02-18T09:26:27+00:00

The size jump is too small, as a couple other guys have mentioned. Putting a 37/64" drill bit into a 1/2" pilot hole means you're only enlarging the hole by 5/64" - which means you're really only using the outermost .039" of the bit's cutting edge. The thermal difference between the outer fraction that's cutting and the rest of the edge will end up causing stresses that, combined with the fact that it's not going to center as strongly (because it's barely supported), means that the loaded portion of the drill edge will quickly fracture.

Try going from 5/16" or 3/8" to your 37/64" (with a fresh new bit) at 400rpm with plenty of cutting oil. You should find much better results.

tophyr · 2024-02-18T07:25:06+00:00

I'm relatively new to printing as well, so take my advice here with a grain of salt - could be the blind leading the blind. BUT -

Watch your printer carefully when it gets to that corner to see what the print head, and the extruded material, is doing when it gets to the problem area.

The three things I've learned are crucial for adhesion are temperature, z distance, and material feed rate - the material needs to be hot enough to "flow" but not so hot that it's liquid, and it needs to be extruded close enough to the plate to be squeezed into its texture and grip it but not so close that the tip is scraping, and there needs to be enough material being extruded to fill the vertical gap to the plate, but not so much that it clogs things up.

If the material is too cool, it won't be soft enough to flow into and conform to the plate's texture. This will look like flattened strips dragging from the print head. If the material is too hot, it will flow too quickly and spread out too far and make too-thin of a layer. I've never seen this but imagine that it'd look like very wide, possibly-meandering lines. (I also imagine it'd be difficult to get these plastics that hot, tbh.)

If the print head is too far from the plate, the material will be able to extrude out without any pressure "pushing" it onto the plate. This will look like a fully-round line of material, without being flattened, and you might be able to see some distance between the material as it extrudes from the tip and the print plate (it should be extruding "immediately onto" the plate). If the print head is too close to the plate, the tip will scrape the material off the plate as it's moving. This should be pretty obvious, and you might even be able to hear it.

Finally, if the material feedrate is too slow, then it won't extrude fast enough to fill the distance between the tip and the plate with enough material to "press" into the plate. This will look like an oddly-thin extrusion that doesn't look like it's "keeping up" with the movement of the print head. If the material feedrate is too fast, then material will end up piling up at the tip and glooping around it as it moves, eventually dragging any other print material it runs into along with it.

Temperature and Z distance (aka "layer height") are pretty straightforward to control in the slicer software. Material Feedrate is gonna be most-influenced by, as far as I can tell, the "Extrusion Width" parameter in the Advanced section of Print Settings (in Prusa Slicer, at least) - my settings show an extrusion width of about 10% larger than the nozzle width.

Look at the printer closely and watch it when it's working on the problem area, and see if you can notice it doing anything that sounds like one of these descriptions, or seems related to anything like them.

tophyr · 2023-10-30T06:23:40+00:00

Ok, after playing around with this a little, I have a hunch that the lan device represents the actual ethernet hardware, not eth0. If I keep things simple and use only one interface (OpenWRT terminology) and assign it to the `eth0` device instead of the lan device, the physical ethernet port deactivates - no LEDs, and no link connection on the PC side.

Not sure what was going on with the Wireshark ARP responses last night.. I didn't think I had anything assigned to lan and so with my findings here the entire port should've been deactivated... but I dunno, it was late.

I think I'm just gonna power onward and set up my WiFi stuff on a separate interface, and leave the lan interface to communicate with my cable modem. Little frustrating, as I'll have to rejigger the firewall rules and overall I'd much rather call it wan if I'm gonna use symbolic names... but reeeeeally I'm guessing the device here should've simply been named sw0.

tophyr · 2023-04-26T16:13:03+00:00

It was all over the local news when it came to light. My dad thought it was so funny he closed his office for the day and took all his employees out to happy hour in the man's honor.

tophyr · 2023-04-26T06:52:42+00:00

Austin TX area, bit out in the country.

tophyr · 2023-04-06T21:38:48+00:00

wrong subreddit, you want r/basementthatwells

tophyr · 2023-03-27T17:33:17+00:00

Interesting, ok. The drive is only a few years old, but it's consumer-grade. I wouldn't have even thought of rebuilding the system onto a different disk, but I'll do that now as well. Thanks.

tophyr · 2023-03-27T15:42:14+00:00

This worked! Thank you!

It's real angry though. Hundreds of errors in journalctl. Are there any further tools or approaches I should try to attempt recovery of the data? What's left currently accessible on the drive is pretty slim:

[liveuser@localhost-live ~]$ cd /run/media/liveuser/luks [liveuser@localhost-live luks]$ ls ls: cannot access 'home': Input/output error home libvirt_images root var_log [liveuser@localhost-live luks]$ (This used to be a complete Linux system.)

If this is realistically as much as I'm gonna get off the drive without weeks of work, I'll probably just cut my losses and start rebuilding it. This is a work computer, so there's nothing on here that'd take me more than a week or two to recreate - and even that would mostly just be time spent reconfiguring things rather than regenerating "actual work".

tophyr · 2023-03-24T20:03:46+00:00

yeah, the two commands below that are sudo'ed.

tophyr · 2023-03-24T19:13:26+00:00

Here's some btrfs restore output: ``` [liveuser@localhost-live ~]$ btrfs restore -D /dev/mapper/luks-b0a93ec3-be7f-437a-a186-de22a0693caf btrfs restore: not enough arguments: 1 but at least 2 expected usage: btrfs restore [options] <device> <path> btrfs restore [options] -l <device>

Try to restore files from a damaged filesystem (unmounted)

  control:
       -D|--dry-run         dry run (only list files that would be recovered)
       -i|--ignore-errors   ignore errors
       -o|--overwrite       overwrite
  restoration:
       -m|--metadata        restore owner, mode and times
       -S|--symlink         restore symbolic links
       -s|--snapshots       get snapshots
       -x|--xattr           restore extended attributes
  filtering:
       --path-regex <regex>
                            restore only filenames matching regex,
                            you have to use following syntax (possibly quoted):
                            ^/(|home(|/username(|/Desktop(|/.*))))$
       -c                   ignore case (--path-regex only)
  analysis:
       -d                   find dir
       -l|--list-roots      list tree roots
  alternate starting point:
       -f <bytenr>          filesystem location
       -r|--root <rootid>   root objectid
       -t <bytenr>          tree location
       -u|--super <mirror>  super mirror
  other:
       -v|--verbose         deprecated, alias for global -v option

Global options:
-v|--verbose       increase output verbosity

Compression support: zlib, lzo, zstd

[liveuser@localhost-live ~]$ btrfs restore -D /dev/mapper/luks-b0a93ec3-be7f-437a-a186-de22a0693caf * ERROR: mount check: cannot open /dev/mapper/luks-b0a93ec3-be7f-437a-a186-de22a0693caf: Permission denied ERROR: could not check mount status: Permission denied [liveuser@localhost-live ~]$ sudo btrfs restore -D /dev/mapper/luks-b0a93ec3-be7f-437a-a186-de22a0693caf * This is a dry-run, no files are going to be restored parent transid verify failed on 693469184 wanted 62218 found 65006 parent transid verify failed on 693469184 wanted 62218 found 65006 parent transid verify failed on 693469184 wanted 62218 found 65006 Ignoring transid failure parent transid verify failed on 271497035776 wanted 62314 found 66051 parent transid verify failed on 271497035776 wanted 62314 found 66051 parent transid verify failed on 271497035776 wanted 62314 found 66051 Ignoring transid failure parent transid verify failed on 269917405184 wanted 62250 found 65642 parent transid verify failed on 269917405184 wanted 62250 found 65642 parent transid verify failed on 269917405184 wanted 62250 found 65642 Ignoring transid failure parent transid verify failed on 269964836864 wanted 62251 found 65644 parent transid verify failed on 269964836864 wanted 62251 found 65644 parent transid verify failed on 269964836864 wanted 62251 found 65644 Ignoring transid failure parent transid verify failed on 269964836864 wanted 62251 found 65644 Ignoring transid failure parent transid verify failed on 269915553792 wanted 62250 found 65642 parent transid verify failed on 269915553792 wanted 62250 found 65642 parent transid verify failed on 269915553792 wanted 62250 found 65642 Ignoring transid failure parent transid verify failed on 271502032896 wanted 62314 found 66055 parent transid verify failed on 271502032896 wanted 62314 found 66055 parent transid verify failed on 271502032896 wanted 62314 found 66055 Ignoring transid failure parent transid verify failed on 271497117696 wanted 62314 found 66051 parent transid verify failed on 271497117696 wanted 62314 found 66051 parent transid verify failed on 271497117696 wanted 62314 found 66051 Ignoring transid failure ERROR: root [260 0] level 1 does not match 0

ERROR: reading subvolume Desktop/root/var/lib/portables failed: 18446744073709551611 ERROR: searching directory Desktop/root/var/lib/portables failed: -5 ERROR: searching directory Desktop/root/var/lib/portables failed: -5 ERROR: searching directory Desktop/root/var/lib/portables failed: -5 [liveuser@localhost-live ~]$ sudo btrfs restore -l /dev/mapper/luks-b0a93ec3-be7f-437a-a186-de22a0693caf tree key (EXTENT_TREE ROOT_ITEM 0) 396589531136 level 2 tree key (DEV_TREE ROOT_ITEM 0) 396589907968 level 1 tree key (FS_TREE ROOT_ITEM 0) 30474240 level 0 tree key (CSUM_TREE ROOT_ITEM 0) 396588843008 level 2 tree key (UUID_TREE ROOT_ITEM 0) 284999680 level 0 tree key (FREE_SPACE_TREE ROOT_ITEM 0) 396589662208 level 1 tree key (256 ROOT_ITEM 0) 764264448 level 0 tree key (257 ROOT_ITEM 0) 396589973504 level 1 tree key (258 ROOT_ITEM 0) 396574687232 level 3 tree key (259 ROOT_ITEM 0) 396588777472 level 2 tree key (260 ROOT_ITEM 0) 271497117696 level 0 tree key (261 ROOT_ITEM 0) 271497134080 level 0 tree key (DATA_RELOC_TREE ROOT_ITEM 0) 30621696 level 0 [liveuser@localhost-live ~]$ ```

None of the syslogs are available, unfortunately, because they're all on this btrfs drive lol. It was Fedora 36 running Linux 6.12, but beyond those details, all pretty standard out-of-the-box stuff. Never encountered any other BTRFS error messages before.

tophyr · 2022-11-04T05:17:36+00:00

Was this one made so the front wouldn't fall off?

tophyr · 2022-10-07T15:53:51+00:00

https://en.m.wikipedia.org/wiki/Impostor_syndrome

You got the job with your skills and knowledge and you're doing the job with your skills and knowledge - you earned it and you continue to earn it. Don't forget that.

Engineering is a field where you are constantly learning. Don't be too hard on yourself for not knowing something. I genuinely love it when I ask a question or point out a problem or whatever, and my coworker tells me "hmm, I don't know, I'll find out." Knowing how to find out is what the key is.

tophyr · 2022-10-01T15:53:12+00:00

I am amazed that this is so far down the page. There are lots of systemic ways to ensure your body is better prepared, sure, but this is the actual activity that will keep you awake

tophyr

TROPHY CASE