aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--files/d-day-orig.jpgbin0 -> 935600 bytes
-rw-r--r--files/d-day.jpgbin0 -> 977156 bytes
-rw-r--r--files/d-day.nc.zipbin0 -> 4400248 bytes
-rw-r--r--posts/opening-black-boxes.md11
4 files changed, 11 insertions, 0 deletions
diff --git a/files/d-day-orig.jpg b/files/d-day-orig.jpg
new file mode 100644
index 0000000..ceea808
--- /dev/null
+++ b/files/d-day-orig.jpg
Binary files differ
diff --git a/files/d-day.jpg b/files/d-day.jpg
new file mode 100644
index 0000000..f8f7a9d
--- /dev/null
+++ b/files/d-day.jpg
Binary files differ
diff --git a/files/d-day.nc.zip b/files/d-day.nc.zip
new file mode 100644
index 0000000..629e9d6
--- /dev/null
+++ b/files/d-day.nc.zip
Binary files differ
diff --git a/posts/opening-black-boxes.md b/posts/opening-black-boxes.md
index b246c91..f776cea 100644
--- a/posts/opening-black-boxes.md
+++ b/posts/opening-black-boxes.md
@@ -129,6 +129,17 @@ might seem. It's all too easy to abstract away the details of a
technical process, but sometimes the best way to really understand
something is by opening up the hood and tinkering with it.
+---
+
+## Appendix: Machined Results
+
+Here are some examples of engraving results, along with the
+corresponding G-code files.
+
+![Into the Jaws of Death. 30° carbide engraving bit, .080" maximum depth, 110% stepover. ([G-code](d-day.nc.zip))](d-day.jpg){width=100%}
+
+![Original image. ([Source](https://en.wikipedia.org/wiki/Into_the_Jaws_of_Death#/media/File:Into_the_Jaws_of_Death_23-0455M_edit.jpg))](d-day-orig.jpg){width=100%}
+
[^1]: I'm probably oversimplifying here. There was, in reality, some
neat vector math to figure out just *where* the "border" of the image
would be when the grooves were at an angle.