<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://starmaid.github.io/feed" rel="self" type="application/atom+xml" /><link href="https://starmaid.github.io/" rel="alternate" type="text/html" /><updated>2026-10-30T23:13:00+00:00</updated><id>https://starmaid.github.io/feed</id><title type="html">Nicky Masso</title><subtitle>My cool internet site :)
</subtitle><author><name>Nicky Masso</name></author><entry><title type="html">Computer Benchmarking</title><link href="https://starmaid.github.io/blog/benchmarking/" rel="alternate" type="text/html" title="Computer Benchmarking" /><published>2026-09-16T00:00:00+00:00</published><updated>2026-09-16T00:00:00+00:00</updated><id>https://starmaid.github.io/blog/benchmarking</id><content type="html" xml:base="https://starmaid.github.io/blog/benchmarking/"><![CDATA[<p><img src="/blog/img/2026-09-16-benchmarking/bench.gif" alt="Screenshot of a computer running a command line program idk with btop open or something" /></p>

<p>This was a fun little side project that helped distract me upgrade my <a href="/blog/smart-home/">Homeassistant install</a>, and also a good distraction while I was working on <a href="{/% link blog/_posts/2026-09-29-protogen.md %}">my protogen head</a>.</p>

<h2 id="problem">Problem</h2>

<p>I have a large collection of single-board computers (SBCs) I have acquired over the years. The large majority are Raspberry Pi 3Bs, and the random Raspberry Pi 4 and NVidia Jetson Nano have clear performance improvements over the base model 3B. I then came into possession of several random other devices. These did not have clear comparisons, and some were even x86 instead of ARM. I no longer knew which was better.</p>

<p><img src="/blog/img/2026-09-16-benchmarking/lineup.jpg" alt="picture of some SBCs" /></p>

<p>I have been having issues with the RPI 3B running my Homeassistant server for a little while. It is fine 90% of the time, but updates will normally cause the whole system to lock up for 20-30 minutes at a time. Also annoying is that the ESPHome integration does not work well. Attempting to compile a hex file for an ESP32 maxes out the memory on the 1GB device. I first attempted to add swap, and this worked for a while! Definitely a good year of extra functionality.</p>

<p><img src="/blog/img/2026-09-16-benchmarking/esp32.jpg" alt="photo of an esp32 in my house somewhere" /></p>

<p>However, at some point my server’s memory footprint grew and attempting to compile in ESPHome would try to move the entire Homeassistant into swap, and it would crash. Then it would come back a few minutes later, and the compilation was failed. I would use the ESPHome docker container on my PC to flash new devices, and then copy the YAML files into the Homeassistant integration for safe keeping.</p>

<p><img src="/blog/img/2026-09-16-benchmarking/rpi3_not_good_enough.png" alt="screenshot of the HA documentation changing to show the RPI is sucks" /></p>

<p>When I started to look into it, I found that in April 2025, the <a href="https://github.com/home-assistant/home-assistant.io/commit/74d9ca828b3921a1d6bf81378e0c9c73802e0728">Raspberry Pi 3 was explicitly defined as insufficient</a> and I even saw it in some release notes at some point. I had already planted the seed of needing to replace it, but didn’t know what with.</p>

<h2 id="solution">Solution</h2>

<p>Obviously the solution would lie in the form of one of my newly acquired SBCs. The question was which one, and would it even be better? I needed to benchmark the performance and statistics of each new computer so I could select the one that would be best for running HA as a dedicated box. I didn’t want something over-specced (leaving performance on the table), and I didn’t want something that was no better, or even slower than the RPI 3B.</p>

<h3 id="the-stupid-way">The Stupid Way</h3>

<p>I initially thought I could just write some stupid python program and be done. But I realized this was silly. There have to be tons of professional benchmarking tools out there!</p>

<h3 id="the-smart-way">The Smart Way</h3>

<p>I went hunting for a benchmarking suite. I pretty quickly found <a href="https://www.phoronix-test-suite.com/">Phoronix Test Suite</a>, which has a bunch of pre-made benchmarking suites and even publicly uploaded results to compare your hardware to. This was exactly what I was looking for, and was able to give a picture of real-world performance for various workloads. I started cooking up a nix flake to easily load and run tests, because pretty much every system I was using was running NixOS and I like developing for it.</p>

<p>This quickly turned into a nightmare. Phorinix Test Suite (PTS) has a bunch of dependencies on Ubuntu specifically, and it also tries to be smart and install its own dependencies. Both of these are terrible to do on NixOS, which does not make system libraries available and will fight applications that attempt to install additional things into their environment. I tried getting away with an <a href="https://discourse.nixos.org/t/flakes-way-of-creating-a-fhs-environment/20821">FHS environment</a> to run my application in, but I still had to provide a million dependencies, and these dependencies seemed to change per-test as each had their own setup and teardown scripts that were just written with no consideration for maintainability.</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>devShells.${system}.default = pkgs.mkShell {
    packages = with pkgs; [
        phoronix-test-suite
        gcc
        gnumake
        bc
        bison
        flex
        openssl
        pkg-config
        elfutils
    ];

    shellHook = ''
        unset NIX_LDFLAGS
        unset NIX_CFLAGS_COMPILE
        unset NIX_CFLAGS_LINK
        unset LDFLAGS
        unset CFLAGS
        unset CXXFLAGS
    '';
};
</code></pre></div></div>

<p>I decided to just limit scope and do two tests. Timed linux kernel compilation and ffmpeg for video encode/decode.</p>

<p>I got it running on my M4 Macbook Pro for work, and my Surface Pro 8. It took a few minutes but got running fine, maybe 21 minutes to run all the tests. The reports are nice and it runs the tests a few times to average the scores. A nice plus of this approach was that I could have a single flake command and it would pull from a public github, so I just had to manually type in a single command instead of like authenticating with my personal github account. I tried this on a raspberry pi and…</p>

<p><img src="/blog/img/2026-09-16-benchmarking/rpi_fan.jpg" alt="Picture of RPI sitting on workbench with a fan on it" /></p>

<p>I don’t know what score it got on the benchmark. I don’t know because downloading and building the flake was taking longer than 30 minutes!!! I cant imagine how long the actual compilation of the linux kernel would take, probably over an hour.</p>

<p>I cancelled the command out of rage and went back to the drawing board.</p>

<h3 id="the-smarterer-way">The Smarterer Way</h3>

<p>I decided I literally just care about the amount of RAM, number of cores, and single core performance. And importantly, I wanted to do it so fast I didn’t see the SBC start thermal throttling due to the download and waste like 45 minutes of my time.</p>

<p>A single c++ file. Run a couple different kinds of operations. Be done in less than 20 seconds. Thats all it takes. The flake loads fast. Copy the output back to my server manually.</p>

<h2 id="some-results">Some Results</h2>

<p>So after a week or so of testing, lets find out - which board should I use?</p>

<table>
  <thead>
    <tr>
      <th>Hardware</th>
      <th>Cores</th>
      <th>RAM</th>
      <th>Runtime (s)</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><a href="https://en.wikipedia.org/wiki/Paperweight">NVidia Jetson Nano</a></td>
      <td>4</td>
      <td>4050824 kB</td>
      <td>18.3511</td>
    </tr>
    <tr>
      <td><a href="https://carnivalcandiesicecream.com/collections/character-faces-1">Raspberry Pi 3b</a></td>
      <td>4</td>
      <td>890236 kB</td>
      <td>17.5603</td>
    </tr>
    <tr>
      <td><a href="https://www.lexibook.com/en-us/product/bilingual-educational-barbie-computer-with-124-activities-in-english-and-spanish">Raspberry Pi 4b</a></td>
      <td>4</td>
      <td>1853444 kB</td>
      <td>13.3627</td>
    </tr>
    <tr>
      <td><a href="https://minis-pc.com/product/minisforum-z83-f-mini-pc-windows-10-pro-processor-intel-atom-x5-z8350/">Minisforum Z83-F</a></td>
      <td>4</td>
      <td>3934012 kB</td>
      <td>12.0969</td>
    </tr>
    <tr>
      <td><a href="https://www.pcmag.com/reviews/azulle-byte4">Azulle Byte4</a></td>
      <td>4</td>
      <td>3831368 kB</td>
      <td>7.97244</td>
    </tr>
    <tr>
      <td><a href="https://support.apple.com/en-us/111339">Macbook Pro 2020</a></td>
      <td>8</td>
      <td>16178416 kB</td>
      <td>5.6705</td>
    </tr>
    <tr>
      <td><a href="https://en.wikipedia.org/wiki/Surface_Pro_8">Surface Pro 8 i5-1135G7</a></td>
      <td>8</td>
      <td>7960716 kB</td>
      <td>5.05076</td>
    </tr>
    <tr>
      <td><a href="{ link ./2022-02-17-the-setup-2.md }">My Desktop</a></td>
      <td>12</td>
      <td>32673592 kB</td>
      <td>4.61138</td>
    </tr>
  </tbody>
</table>

<p><strong>Things that affect this score</strong></p>

<ul>
  <li>Other stuff you are running when you run the benchmark (do you have a browser open?)</li>
  <li>If its a laptop, if its plugged in or not</li>
  <li>How close to thermal throttling you already were</li>
</ul>

<p><strong>Things that this misses</strong></p>

<ul>
  <li>Doesn’t cover power draw (important to me!)</li>
  <li>Doesn’t cover video stuff - the jetson is worst?</li>
</ul>

<p>So what board do I use? For Homeassistant, my major two problems were mostly long compile times and not enough memory. I just needed something with more memory and a little better performance. This seems like the Minisforum Z83-F would be our winner, which is awesome because it also draws very little power with that Intel Atom X5-Z8350. It also has gigabit ethernet, which is a nice plus - update downloads go a lot faster.</p>

<h3 id="installing-stuff-on-the-minisforum-side-quest">Installing stuff on the Minisforum Side Quest</h3>

<p>Installing anything was a mild adventure. I actually got two of these, the first one already had Ubuntu running on it, and had no trouble installing NixOS. The second one had Windows 10 running, and was a nightmare to install linux. The computer has a 64 GB eMMC drive, and this is where I wanted to install the OS. First I had to go into BIOS and set the chip from ACPI mode to PCI, or the other way around, or back again. I wish I remembered.</p>

<p>Next, the eMMC is not actually detected by most installers out of the box. The Ubuntu installer does see it, but the NixOS installer didn’t. Unfortunately the Ubuntu live boot disk also was really laggy, whereas the NixOS live boot was super snappy. All I ended up needing to do was open a console in the NixOS live boot and run:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>modprobe mmc_block
</code></pre></div></div>

<p>And then I could format the partition with the <code class="language-plaintext highlighter-rouge">disks</code> utility in GNOME. I used this same utility to flash the <a href="https://www.home-assistant.io/installation/generic-x86-64/">Homeassistant generic x86_64</a> image onto the eMMC.</p>

<p>I got it running just fine, and used the web client to restore from one of my daily backups. This was totally awesome! However, I noticed that the built-in bluetooth chip was not detected. This threw me down another adventure trying to get the bluetooth device to be seen in Homeassistant. I was going through the logs of dmesg and lsusb and seeing some messages that things had failed, but maybe that meant it was fine, but it still didn’t show up in the Homeassistant integrations…</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>sudo dmesg | grep -iE 'blue|firmware'

lsusb | grep -i bluetooth
</code></pre></div></div>

<p>After a day or so of just failing to get it working, I just gave up. Homeassistant supports <a href="https://esphome.io/components/bluetooth_proxy/">bluetooth proxy devices through ESPHome</a>, which is way cooler and can actually put the bluetooth near the device you are trying to connect to - and makes the install independent of the hardware you’re running the server on. Plus its not like I used anything with it.</p>

<p>Anyway, side quest over.</p>

<h2 id="whats-your-score">What’s Your Score?</h2>

<p>Feel free to run it yourself. You will need the <a href="https://nixos.org/download/">nix package manager</a> installed.</p>

<p><a href="https://github.com/starmaid/benchmark">The repo is up here</a> but you can also just paste this command into your terminal. Unless you already have nixpgks 26.05 hash <code class="language-plaintext highlighter-rouge">4c7870105e7f1fdf9c48688c8d7efc21abf0688a</code> then it’ll probably have to download like 180 mb of registry and packages, which may take a few minutes (nix is not storage optimized….just garbage collect it later). You could alternatively clone the repo, modify the revs, and use the stuff you already have. Which would make it a lot faster to run. Also if you have flakes enabled you don’t need to include the flags for those.</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>nix run --refresh github:starmaid/benchmark --extra-experimental-features nix-command --extra-experimental-features flakes
</code></pre></div></div>]]></content><author><name>Nicky Masso</name></author><category term="blog" /><category term="hardware," /><category term="raspberry" /><category term="pi," /><category term="programming" /><summary type="html"><![CDATA[]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://starmaid.github.io/blog/img/2026-09-16-benchmarking/bench.gif" /><media:content medium="image" url="https://starmaid.github.io/blog/img/2026-09-16-benchmarking/bench.gif" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">Flashstep Game</title><link href="https://starmaid.github.io/blog/flashstep-game/" rel="alternate" type="text/html" title="Flashstep Game" /><published>2026-08-03T00:00:00+00:00</published><updated>2026-08-03T00:00:00+00:00</updated><id>https://starmaid.github.io/blog/flashstep-game</id><content type="html" xml:base="https://starmaid.github.io/blog/flashstep-game/"><![CDATA[<p><img src="/blog/img/2026-08-03-flashstep-game/demo.gif" alt="gif of the game on itch" /></p>

<p>Flashstep is a game demonstration I made on August 10, 2025, and finally polished and posted online on August 3, 2026. The basic premise is the ability to teleport to a location where you look and click.</p>

<p><a href="https://st4rm41d.itch.io/flashstep-demo">Link to play on Itch.io</a></p>

<p><a href="https://github.com/starmaid/flashstep-demo">Source code on GitHub</a></p>

<h2 id="the-idea">The Idea</h2>

<p>This started when I attended MAGWest for the first time in 2025. I really enjoyed the convention, and obviously it made me want to make a game that wasn’t my magnum opus - just something fun and interesting. The time spent in the LAN party room playing Halo CE with 12 people was so nice, and fun movement shooters were on my mind. Maybe it had been too long since I played Titanfall.</p>

<p><img src="/blog/img/2026-08-03-flashstep-game/magwest_halo_lan.jpg" alt="some magwest image from 2025" /></p>

<p>Another thing I got to do was wander around the indie game hall, playing prototypes and complete games that were obviously way more feasible for a single developer. I got to learn what made them work well, my pain points etc.</p>

<p>There was one game i got to play, <a href="https://store.steampowered.com/app/2840590/no_signal/"><em>No Signal</em></a> that is a hidden-object game set on a space station. This game lets you control a disembodied camera as you uncover a mystery, which is really fun. In addition to exploring the stylized space station, there are also a bunch of minigames and puzzles.</p>

<p><img src="/blog/img/2026-08-03-flashstep-game/nosignal.gif" alt="gif of nosignal" /></p>

<p>One thing that I noticed while playing through the demo was that the camera was locked on a world Z-up - and it never changed. This made it very easy to orient yourself in the world, but it meant that while looking at the ceiling or floor you were gimbal locked. I think this works for the disembodied phase-through-walls camera of <em>No Signal</em>, but if I was a character inhabiting this environment I think it would feel jarring.</p>

<h2 id="starting">Starting</h2>

<p>So while sitting at a talk that I didn’t need to pay 100% attention to, I loaded the Godot game engine on my laptop and booted it up for the first time. I threw a couple cubes in the scene, learned how to write scripts, and made a quick demo. After a bit more work the day after, I had a working demo.</p>

<p><img src="/blog/img/2026-08-03-flashstep-game/v1_euler_sm.gif" alt="gif 1 of the original demo, showcasing euler camera movement" /></p>

<p>Heres Euler camera motion. It is very easy to keep your bearings, but quick mouse movements are unpredictable, especially as you get further from the horizon line. It becomes hard to chain jumps.</p>

<p><img src="/blog/img/2026-08-03-flashstep-game/v1_quaternion_sm.gif" alt="gif 2 of the original demo, showcasing quaternion movement" /></p>

<p>With quaternion motion, its much easier to make quick motions that end up where you expect them to - allowing fast chained inputs.</p>

<p>My vision would be to turn this into some kind of grappler-shooter - with the difficulty of the <a href="https://aottg2-team.itch.io/aottg2">Attack on Titan Tribute Game</a> and the speed of Titanfall, I wanted it to be exciting with a steep learning curve that feels good when you learn how to navigate. However, that sounded like a lot of work to do and I had just started a new job, so I shelved it.</p>

<h2 id="the-return">The Return</h2>

<p>About a year later, I ended up with an idea for another game - one that could use this base code. As a first step, I thought it would be useful to go all the way through publishing and uploading an HTML5 game to itch.io from Godot. This would teach me every possible hurdle with mouse input, performance, tooling, whatever. So this game was a perfect candidate.</p>

<p>After finding the source files (not trivial with my disjointed backup system) I was able to throw some textures on the cubes, give it some vibes, and get it out the door. I added buttons so the user could A/B test their favorite method of camera movement! It was a perfect little test program and it verified everything I needed.</p>

<p><a href="https://st4rm41d.itch.io/flashstep-demo">You can play it on itch.io here.</a></p>

<p>Anyway. Go read about <a href="{/% link ./2026-08-29-graveyard-orbit-game.md %}">Graveyard Orbit</a> if you want to hear what became of this.</p>]]></content><author><name>Nicky Masso</name></author><category term="blog" /><category term="gamedev," /><category term="godot," /><category term="programming" /><summary type="html"><![CDATA[]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://starmaid.github.io/blog/img/2026-08-03-flashstep-game/demo.gif" /><media:content medium="image" url="https://starmaid.github.io/blog/img/2026-08-03-flashstep-game/demo.gif" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">Lights Rectangle</title><link href="https://starmaid.github.io/blog/lights-rectangle/" rel="alternate" type="text/html" title="Lights Rectangle" /><published>2026-06-02T00:00:00+00:00</published><updated>2026-06-02T00:00:00+00:00</updated><id>https://starmaid.github.io/blog/lights-rectangle</id><content type="html" xml:base="https://starmaid.github.io/blog/lights-rectangle/"><![CDATA[<p><img src="/blog/img/2026-06-02-lights-rectangle/thumb.gif" alt="Gif of it working" /></p>

<p>A small ESP32-based light.</p>

<h2 id="why-build-this">Why build this?</h2>

<p>This project was a small gift for two of my friends, Eris and Mimi. Each of them are programmers, and I thought they would enjoy a device to run light control code on without having to care about the hardware. I also make software to run on devices similar to this (<a href="/blog/pulseofexploration">pulse</a>, <a href="/blog/randbeacon">randbeacon</a>) and both of them expressed interest in running those programs themselves, but didn’t have a light to use.</p>

<p>The design needed to be something small that would both not be crazy to bring in my luggage, and also not take up too much space in a shared apartment. I also needed it to be fully enclosed and not have any crazy dances you have to do to use it, and ideally no exposed wires or other ways to fuck up. This is critical when giving projects as presents.</p>

<h2 id="design">Design</h2>

<p>My initial design revolved around a kind of circular shape that had some supports with the ESP32 in the center. However after a few hours of 3D modeling, I had the sudden and terrible realization that it looked like some kind of <a href="https://duckduckgo.com/?q=awesome+hot+wheels+lamp+wheel&amp;iar=images&amp;t=ffab">man-cave truck guy wheel wall art</a>. Which was untenable for obvious reasons.</p>

<p><img src="/blog/img/2026-06-02-lights-rectangle/notebook_1.jpg" alt="notebook page of bad pages" /></p>

<p>I then went on a feverish redesign. Everything I could think of was either <a href="https://en.wikipedia.org/wiki/World_Trade_Center_(1973%E2%80%932001)">phallic</a>, <a href="https://en.wikipedia.org/wiki/The_Incredulity_of_Saint_Thomas_(Caravaggio)">yonic</a>, or evocative of something I didn’t want (like the wheel)</p>

<p><img src="/blog/img/2026-06-02-lights-rectangle/notebook_2.jpg" alt="notebook page of redesign" /></p>

<p>I settled on the “dyson airblade” look, because it was the perfect ratio of phallic to yonic, and would also be pretty easy to make. I also played with the angles to make it less similar to the bladeless fans, so there was some uniqueness.</p>

<p><img src="/blog/img/2026-06-02-lights-rectangle/notebook_3.jpg" alt="notebook page of circuit" /></p>

<p>The circuit itself would be very simple - I don’t believe in level shifters, but I do believe in filtering capacitors. I wanted to do without another board, so all joints would be directly on the ESP.</p>

<p><img src="/blog/img/2026-06-02-lights-rectangle/construction.jpg" alt="picture of it in parts" /></p>

<h2 id="build">Build</h2>

<p>Access to one of the buttons on the ESP32. This button by default toggles the light on/off, which is very handy when you are right there on the light and don’t want to open up an app to control it. I am familiar with making trapped buttons, so a few careful measurements and test prints later I had something that worked perfectly.</p>

<p><img src="/blog/img/2026-06-02-lights-rectangle/vents_and_button.jpg" alt="vents and button" /></p>

<p>I added some vents for some small amount of airflow. I know these devices generate a bit of heat, and fully trapping that would not be ideal. As always, this took way longer than it should because 3D modeling applications hate resizing stuff like this. I ended up using a boolean object so at least I could resize the vents in a different object and the dimensions weren’t linked. This was so effective, even if it was hard to make in the first place. It felt hacky though.</p>

<p>The radius that the lights can wrap around was also a consideration, as the 144 LED/meter strip actually had a wider radius than the normal like 60 LED/meter strips I buy. This ended up being like 18 mm.</p>

<p><img src="/blog/img/2026-06-02-lights-rectangle/curve_closeup.jpg" alt="something that shows the curve of the light" /></p>

<p>For the print, I went back and forth on infill type. Obviously the main light diffuser would just be two perimeters (one would be too fragile for shipping, and two was still translucent enough). But the sides would also leak light - and I had to decide what to do. One option was to put some kind of opaque coating or tape like my <a href="/blog/_posts/2026-04-19-plants-light-shelf.md">plant light shelf</a>, but I think that would make it less interesting. I the light transmission through the print looked cool, so I tried out gyroid infill. This gave really cool results, and I decided to keep it.</p>

<p><img src="/blog/img/2026-06-02-lights-rectangle/translucency.jpg" alt="what the translucency looks like" /></p>

<p>For assembly, I didn’t feel like using heat-set inserts, because the loads would be minimal. But I didn’t want to glue anything in case repairs were needed. I used some trusty M3 hex screws for the case, and then some M2 screws for holding the MCU in place.</p>

<p><img src="/blog/img/2026-06-02-lights-rectangle/sticker.jpg" alt="closeup of the sticker" /></p>

<p>The final touch was a sticker - something that describes what it is, how to use it, and some basic info in case everything gets messed up. I used the recognizable ST4R logo, even as I’m playing with the brand now.</p>

<h2 id="product">Product</h2>

<p>I ended up making one myself as a prototype, where I used cheaper lights. After testing, I made the two for gifts, and they worked great! <a href="https://www.thingiverse.com/thing:7389145">Link to files on thingiverse</a>. Let me know if you make one! The software is WLED which can be flashed from a chromium-based browser <a href="https://install.wled.me/">here</a>.</p>

<p><img src="/blog/img/2026-06-02-lights-rectangle/three_of_them.jpg" alt="three of them" /></p>]]></content><author><name>Nicky Masso</name></author><category term="blog" /><category term="wled," /><category term="light," /><category term="esp32" /><summary type="html"><![CDATA[]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://starmaid.github.io/blog/img/2026-06-02-lights-rectangle/thumb_sm.gif" /><media:content medium="image" url="https://starmaid.github.io/blog/img/2026-06-02-lights-rectangle/thumb_sm.gif" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">Robots On Ice</title><link href="https://starmaid.github.io/blog/robots-on-ice/" rel="alternate" type="text/html" title="Robots On Ice" /><published>2026-04-25T00:00:00+00:00</published><updated>2026-04-25T00:00:00+00:00</updated><id>https://starmaid.github.io/blog/robots-on-ice</id><content type="html" xml:base="https://starmaid.github.io/blog/robots-on-ice/"><![CDATA[<iframe width="100%" height="315" src="https://www.youtube.com/embed/lbAELyJupGA" frameborder="0" allowfullscreen=""></iframe>

<p><em><a href="https://www.mercurynews.com/2026/04/25/robots-take-up-ice-skating-saturday-at-san-jose-robotics-event/">Theres actually an article about this in the Mercury news?</a></em></p>

<p><a href="https://www.robotsonice.org/">Robots on Ice!</a> is an event hosted by <a href="https://siliconvalleyskates.org/2026/05/26/robots-on-ice-2026-racing-robotics-and-innovation-in-san-jose/">The Silicon Valley Ice Skating Association</a> usually in the spring at Sharks Ice, San Jose. I think the primary focus is to do a fun outreach event and let the community see some fun robots built by local people.</p>

<p>I noticed a lot of AI and hype language used in the promotion and execution of the event. I think there was only like one or two people coordinating and running this, so I imagine they had a lot to take care of. The organizers also sent pre-formatted social media material for promotion. I don’t usually exhibit at stuff, so I was very new to this kind of material.</p>

<p><img src="/blog/img/2026-04-25-robots-on-ice/1_table.jpg" alt="photo of our table" /></p>

<p>Our loadin was very uneventful. It did take Lucy and I a second to find the specific ice rink we were using, as we had never been to this complex and they had like 6 rinks. I also only brought a toolkit and the robot, so no huge bin or anything. Also while there, I went to the team store and bought hockey tape and an ice puck. Hockey tape is much like gaffer tape, but narrower and a bit thicker. I obviously bought the gay pride stuff, planning to use it for decoration. I put it on one of my forks, like it was a stick.</p>

<h3 id="who-else-was-there">Who else was there</h3>

<ul>
  <li>Two SRI Robotics people, who like hockey and curling.</li>
  <li>The skating robot guy</li>
  <li>that dalek team</li>
  <li>like three FIRST robotics teams</li>
  <li>That ROS rover startup team</li>
  <li>That moddable animal toy team</li>
  <li>That hexapod guy</li>
  <li>Random kids with toys</li>
  <li>Audience of mostly kids and people who were already at the rink that day</li>
</ul>

<p><img src="/blog/img/2026-04-25-robots-on-ice/2_crowd.jpg" alt="picture of the audience" /></p>

<h3 id="people-who-i-think-would-have-fun-but-werent-there">People who I think would have fun but werent there</h3>

<ul>
  <li>more bot hockey people</li>
  <li>rc drift people</li>
  <li>humanoid robot people</li>
</ul>

<h3 id="phases-of-the-event">Phases of the event</h3>
<ul>
  <li>Drive around in open play area, collect the balls the first teams were releasing</li>
  <li>Race</li>
  <li>Play hockey with a kickball</li>
</ul>

<p><img src="/blog/img/2026-04-25-robots-on-ice/3_lineup.jpg" alt="picture of the audience" /></p>

<h2 id="what-was-hard">What was hard</h2>

<p>So obviously the biggest challenge was traction - our robots have 60A hard rubber wheels, which are very much optimized for coarse, hard surfaces. This speaks to our strength and dominance on parking lots. However the amount of friction was so low it was hard to manage. I attempted to keep traction and stay in the static friction regime by accelerating very slowly, but even with low braking on my ESCs it was very difficult to slow down or turn without losing traction inadvertently. I attempted to put some tape on my wheels to see if it would change anything, but i couldnt really tell. The tape just got wet.</p>

<p>The second issue was running into piles of snow on the ice. These were surprisingly sticky and would fully immobilize our robots, requiring someone to hit the robot with some object, or to just wait for someone with hockey skates to give them a nudge.</p>

<p><img src="/blog/img/2026-04-25-robots-on-ice/4_group_photo.jpg" alt="me, lucy, scott, and victor" />
<em>Me, Lucy, Victor, and Scott.</em></p>

<p>Another issue was water. The bots were not meant to be watertight, and moisture was not an anticipated issue. We ended up taping up all likely ingress points, which saved our internals. However, the annoying issue came months later - Scott’s robots specifically ended up rusting their black oxide bolts after not drying them fully before storage.</p>

<p>Another annoying issue was how our robots weight distribution and contact patches contributed to spinning out. All of our fork bots weight is in front of our drive wheels. This lets our forks ride on the ground, to get under opponents. But when sliding on the ice, the forks drag more than the wheels - something about the material, edges, etc. and they spin to face backwards. This almost made it better to drive backwards, but this was generally hard to control.</p>

<p>An issue that affected some peoples robots but not our own was radio range/channel usage. There were on the order of 20 robots on the 2.4 ghz band, and many transmitters were on BLE - I didn’t have an SDR to take a look at the airwaves, but many people were having issues with connections dropping out - to the point where victor had to follow his robot around the arena to stay connected.</p>

<p><img src="/blog/img/2026-04-25-robots-on-ice/5_drivers.jpg" alt="while we were driving" />
<em>Lucy and Scott focusing on driving.</em></p>

<h2 id="what-was-great">What was great</h2>

<p>Our robots were the only ones that could really handle a puck at all. Most people were just using toys that were either too small or too big to handle the specific size of a puck. I would love to see a full hockey match here on the ice. This was where a kickball, which was large enough to be just bumped into full speed, ended up being the hockey puck for our game.</p>

<p>The FIRST robots were very skilled at driving on the ice. I think the two most mobile teams had swerve drives, and it helped that they were likely heavy - more static friction. I wonder if adding weight would improve grip at the cost of more momentum to pull through turns? I also wonder what their tires were made of.</p>

<p><img src="/blog/img/2026-04-25-robots-on-ice/everyone.jpg" alt="full group pic of everyone who was there" /></p>

<h2 id="notes">Notes</h2>

<p>I’ll probably try to go again next year - this was pretty neat. I’ll put more thought into some tires that could really chew up the ice, maybe something with some metal. Theres also no weight restrictions like bot hockey games, so adding a bunch might be worthwhile.</p>]]></content><author><name>Nicky Masso</name></author><category term="blog" /><category term="robot," /><category term="bhl," /><category term="hockey," /><category term="outreach" /><summary type="html"><![CDATA[]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://starmaid.github.io/blog/img/2026-04-25-robots-on-ice/thumb.jpg" /><media:content medium="image" url="https://starmaid.github.io/blog/img/2026-04-25-robots-on-ice/thumb.jpg" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">Plants Light Shelf</title><link href="https://starmaid.github.io/blog/plants-light-shelf/" rel="alternate" type="text/html" title="Plants Light Shelf" /><published>2026-04-19T00:00:00+00:00</published><updated>2026-04-19T00:00:00+00:00</updated><id>https://starmaid.github.io/blog/plants-light-shelf</id><content type="html" xml:base="https://starmaid.github.io/blog/plants-light-shelf/"><![CDATA[<p><img src="/blog/img/2026-04-19-plants-light-shelf/done.jpg" alt="picture of the light on the shelf functioning" /></p>

<p>This one is a fast one. Problem: I’m running out of shelf space for plants on my glass shelving unit. Solution: shine light on plants from above one of the glass shelves, while also being a platform for more plants to sit on top of.</p>

<h2 id="design">Design</h2>

<p>I have an <a href="https://en.wikipedia.org/wiki/A-series_light_bulb">A19</a> bulb that I bought a while ago for putting in a lamp in my bathroom and keeping a plant alive. However, the lamp I bought for that was too short and ended up cooking the plant I used at the time. So with no other real use for it, the bulb has been sitting in a box.</p>

<p>I didn’t want this to take up too much space, so the footprint is just big enough to get the bulb centered in the square. The height is also the minimum for holding the bulb horizontally.</p>

<p>I put a small ledge around the top to prevent stuff from sliding off. This did result in suboptimal print orientation for finish quality, but I think it’s ok.</p>

<p><img src="/blog/img/2026-04-19-plants-light-shelf/construction.jpg" alt="picture of the thing upside down" /></p>

<p>The aluminum tape reflects all the light back down to the shelf below, and prevents the PLA from heating up too much.</p>

<h2 id="build">Build</h2>

<p>I used as few custom parts as possible because I didnt want to do this project any longer than I had to.</p>

<table>
  <thead>
    <tr>
      <th>Part</th>
      <th>Source</th>
      <th>Cost</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Grow light bulb</td>
      <td><a href="https://www.homedepot.com/p/Feit-Electric-9-Watt-E26-A19-Medium-Base-Non-Dim-Indoor-and-Greenhouse-Full-Spectrum-Plant-Grow-LED-Light-Bulb-1-Pack-A19-GROW-LEDG2-BX/312552639">Home depot</a></td>
      <td>$11</td>
    </tr>
    <tr>
      <td>Lamp socket</td>
      <td><a href="https://www.acehardware.com/departments/lighting-and-electrical/replacement-parts-and-accessories/sockets-and-holders/3823390">Ace hardware</a></td>
      <td>$8</td>
    </tr>
    <tr>
      <td>Lamp cord with no switch</td>
      <td><a href="https://www.acehardware.com/departments/lighting-and-electrical/replacement-parts-and-accessories/lamp-parts/3365178">Ace hardware</a></td>
      <td>$10</td>
    </tr>
    <tr>
      <td>Aluminum tape</td>
      <td>???</td>
      <td>$10 ?</td>
    </tr>
    <tr>
      <td>Zip ties</td>
      <td><a href="https://www.harborfreight.com/11-inch-black-cable-ties-pack-of-100-34637.html">harbor freight</a></td>
      <td>$3</td>
    </tr>
  </tbody>
</table>

<p>I just used zip ties to hold the socket and cable because they won’t melt, wont slip, and are easy to design for.</p>

<p><a href="https://www.thingiverse.com/thing:7388284">Link to the 3D model on thingiverse</a></p>]]></content><author><name>Nicky Masso</name></author><category term="blog" /><category term="light," /><category term="3d" /><category term="printing," /><category term="ace" /><category term="hardware" /><summary type="html"><![CDATA[]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://starmaid.github.io/blog/img/2026-04-19-plants-light-shelf/done.jpg" /><media:content medium="image" url="https://starmaid.github.io/blog/img/2026-04-19-plants-light-shelf/done.jpg" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">Bot Hockey at Nexus Knockout 3</title><link href="https://starmaid.github.io/blog/nexus-knockout-3/" rel="alternate" type="text/html" title="Bot Hockey at Nexus Knockout 3" /><published>2026-04-04T00:00:00+00:00</published><updated>2026-04-04T00:00:00+00:00</updated><id>https://starmaid.github.io/blog/nexus-knockout-3</id><content type="html" xml:base="https://starmaid.github.io/blog/nexus-knockout-3/"><![CDATA[<iframe width="100%" height="315" src="https://www.youtube.com/embed/QC39mv8_2Qo" frameborder="0" allowfullscreen=""></iframe>

<h2 id="what-even-is-nexus-knockout">What even is nexus knockout?</h2>

<p>Basically check out the <a href="https://www.robotcombatevents.com/events/6477">Robot Combat Events website</a> for a rundown. Its at Maker’s Nexus in Sunnyvale, CA. Its full combat up to 3lbs, plus bot hockey. This was the same event, two years prior, that I learned about the sport and got inspired to try it myself (<a href="/blog/_posts/2025-07-20-hockey-robot.md">See that blog post here</a>). This time, I had my own bot.</p>

<h3 id="did-you-do-anything-to-prep-since-open-sauce-2025">Did you do anything to prep since open sauce 2025?</h3>

<p>One massive change: I ordered laser-cut aluminum panels for my robot. Exact same design, but more able to take a beating than the acrylic.</p>

<p><img src="/blog/img/2026-04-04-nexus-knockout-3/panels.jpg" alt="alternate acrylic panels" /></p>

<p><em>The alternate battery covers, with the clean robot behind them. I didn’t want to lose the clear battery cover…</em></p>

<p>I reprinted a lot of the robot for fresher, stronger parts than immediately after open sauce. I also got rid of the last internal PLA parts and replaced them with TPU.</p>

<p><img src="/blog/img/2026-04-04-nexus-knockout-3/night_practice.jpg" alt="picture of it at night near my car" /></p>

<p><em>Night Practice near Scott’s house</em></p>

<h2 id="the-games">The Games</h2>

<p>This time, rallying under the unified team Scottbot, we had a full 6 bots - Scott with 1 and 2, Orion with his 3, and me with my single competitor. Lucy was also there to get some experience driving. We were also lowkey cracked.</p>

<p><img src="/blog/img/2026-04-04-nexus-knockout-3/team_photo.jpg" alt="team photo" /></p>

<p><img src="/blog/img/2026-04-04-nexus-knockout-3/dr_pepper.jpg" alt="dr pepper" /></p>

<h3 id="morning">Morning</h3>

<p>Group stage. We lost to No-Ice (just by two points - very close game) and crushed the hockeymaniacs.</p>

<p><img src="/blog/img/2026-04-04-nexus-knockout-3/nexusknockout3_groups.svg" alt="group stage bracket" /></p>

<p>We knew No-Ice was going to be tough, and our team was still getting our footing. Hockeymaniacs had some good bots, but I think they were having some hardware issues.</p>

<p><img src="/blog/img/2026-04-04-nexus-knockout-3/bree_and_orion.jpg" alt="working on the bots" /></p>

<h3 id="lunch-break">Lunch Break</h3>

<p>My friend Bree showed up to hang out, and brought her RC drift cars. They got a bit torn up on the parking lot, but were a lot of fun.</p>

<iframe width="100%" height="315" src="https://www.youtube.com/embed/jzdOLfMVCUU" frameborder="0" allowfullscreen=""></iframe>

<h2 id="the-rest">The rest</h2>

<p>Smashed The Party Animals, but theyre always fun to play. Met team No-Ice in the finals, and had one of the lowest-scoring matches I think I’ve ever seen. Defense was extra good here.</p>

<p><img src="/blog/img/2026-04-04-nexus-knockout-3/nexusknockout3_bracket.svg" alt="elimination bracket" /></p>

<p>My bot managed to stay mostly cool, but at the end of the last match the motors were hotter than I had ever seen them. Definitely was driving hard, in direct sunlight.</p>

<h2 id="next-step">Next Step</h2>

<p>So we won! Next up is open sauce.</p>

<p><img src="/blog/img/2026-04-04-nexus-knockout-3/victory_group_photo.jpg" alt="all teams group photo" /></p>

<p>The damage to my robot with the aluminum panels was very minimal.</p>

<p><img src="/blog/img/2026-04-04-nexus-knockout-3/damage_top.jpg" alt="damage top" /></p>

<p><img src="/blog/img/2026-04-04-nexus-knockout-3/damage_bottom.jpg" alt="damage bottom" /></p>]]></content><author><name>Nicky Masso</name></author><category term="blog" /><category term="combat," /><category term="robot," /><category term="bhl," /><category term="hockey" /><summary type="html"><![CDATA[]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://starmaid.github.io/blog/img/2026-04-04-nexus-knockout-3/slam.gif" /><media:content medium="image" url="https://starmaid.github.io/blog/img/2026-04-04-nexus-knockout-3/slam.gif" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">Eternal September</title><link href="https://starmaid.github.io/blog/eternal-september/" rel="alternate" type="text/html" title="Eternal September" /><published>2026-01-11T00:00:00+00:00</published><updated>2026-01-11T00:00:00+00:00</updated><id>https://starmaid.github.io/blog/eternal-september</id><content type="html" xml:base="https://starmaid.github.io/blog/eternal-september/"><![CDATA[<style>
    .calcbox {
        padding: 5px;
        color: black;
        background: white;
        align-items: center;
        display: flex;
        flex-direction: column;
        width: min-content;
    }

    .calcbox2 {
        flex: auto;
        padding: 5px;
        border: 1px solid black;
        gap: 16px;
        flex-direction: column;
    }

    .fieldbox {
        padding: 5px;
        width: 170px;
        flex: 1 1 auto;
        display: flex;
        height: min-content;
    }

    .buttonbox {
        padding: 5px;
        width: 160px;
        flex: 1 1 auto;
        display: flex;
        flex-flow: row;
    }

    .calccontainer {
        margin: 3%;
        min-width: 270px;
        font-family: serif;
        align-items: center;
    }

    .calccontainer2 {
        width: 100%;
        align-items: center;
        display: flex;
        flex-direction: column;
    }
</style>

<div class="calccontainer">
    <div class="calccontainer2">
        <div class="calcbox">
            <div class="calcbox2">
                <div class="fieldbox">
                    1993-09-<input id="sdatedays" type="text" maxlength="8" size="8" />
                </div>
                <div class="buttonbox">
                    <button type="button" id="sdate2date">Convert to normie time</button>
                </div>
                <div id="sdateMsgBox"></div>
            </div>
        </div>
        <div class="calcbox">
            <div class="calcbox2">
                <div class="fieldbox">
                    <input id="dateyear" type="text" maxlength="4" size="4" value="2026" />
                    -<input id="datemonth" type="text" maxlength="2" size="2" value="01" />
                    -<input id="dateday" type="text" maxlength="2" size="2" value="12" />
                </div>
                <div class="buttonbox">
                    <button type="button" id="date2sdate">Convert to eternal september time</button>
                </div>
                <div id="dateMsgBox"></div>
            </div>
        </div>
    </div>
</div>

<script type="module" src="/blog/img/2026-01-11-eternal-september/datetest.js"></script>

<p>If you don’t want to google “how many days since august 30 1993”. <a href="https://en.wikipedia.org/wiki/Eternal_September">If you don’t know what I’m talking about.</a></p>

<p><img src="/blog/img/2026-01-11-eternal-september/example.jpg" alt="" /></p>]]></content><author><name>Nicky Masso</name></author><category term="blog" /><category term="tool," /><category term="internet" /><category term="history" /><summary type="html"><![CDATA[]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://starmaid.github.io/blog/img/2026-01-11-eternal-september/prion_thumb.png" /><media:content medium="image" url="https://starmaid.github.io/blog/img/2026-01-11-eternal-september/prion_thumb.png" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">Space Probe String Lights</title><link href="https://starmaid.github.io/blog/space-probe-lights/" rel="alternate" type="text/html" title="Space Probe String Lights" /><published>2026-01-09T00:00:00+00:00</published><updated>2026-01-09T00:00:00+00:00</updated><id>https://starmaid.github.io/blog/space-probe-lights</id><content type="html" xml:base="https://starmaid.github.io/blog/space-probe-lights/"><![CDATA[<p><img src="/blog/img/2026-01-09-space-probe-lights/string.jpg" alt="Full string of lights" /></p>

<p>Made as a secret santa for <a href="https://rustyrat.carrd.co/">Rusty</a> as part of the 2025 Ebro gift exchange. I made lo-poly models of the space probes his OCs are based on, and attached them to an LED string light. I also modified the light to be powered from a USB plug, rather than AA batteries.</p>

<p><img src="/blog/img/2026-01-09-space-probe-lights/juno.jpg" alt="Juno" /></p>

<p><em><a href="https://en.wikipedia.org/wiki/Juno_(spacecraft)">Juno</a>, 2011 mission to Jupiter.</em></p>

<p><img src="/blog/img/2026-01-09-space-probe-lights/msgr.jpg" alt="Messenger" /></p>

<p><em><a href="https://en.wikipedia.org/wiki/MESSENGER">MESSENGER</a>, 2004 mission to Mercury.</em></p>

<p><img src="/blog/img/2026-01-09-space-probe-lights/chip.jpg" alt="CHIPSat" /></p>

<p><em><a href="https://en.wikipedia.org/wiki/CHIPS_(satellite)">CHIPSat</a>, 2003 mission orbiting Earth observing UV emissions from interstellar gas clouds. Launched in the same rocket as ICESat.</em></p>

<p><img src="/blog/img/2026-01-09-space-probe-lights/ice.jpg" alt="ICESat" /></p>

<p><em><a href="https://en.wikipedia.org/wiki/ICESat">ICESat 1</a>, 2003 mission orbiting earth measuring elevation for ice sheets and atmospheric measurements. Launched in the same rocket as CHIPSat.</em></p>]]></content><author><name>Nicky Masso</name></author><category term="blog" /><category term="light," /><category term="LED," /><category term="17776" /><summary type="html"><![CDATA[Made as a secret santa for Rusty as part of the 2025 Ebro gift exchange. I made lo-poly models of the space probes his OCs are based on, and attached them to an LED string light. I also modified the light to be powered from a USB plug, rather than AA batteries. Juno, 2011 mission to Jupiter. MESSENGER, 2004 mission to Mercury. CHIPSat, 2003 mission orbiting Earth observing UV emissions from interstellar gas clouds. Launched in the same rocket as ICESat. ICESat 1, 2003 mission orbiting earth measuring elevation for ice sheets and atmospheric measurements. Launched in the same rocket as CHIPSat.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://starmaid.github.io/blog/img/2026-01-09-space-probe-lights/juno.jpg" /><media:content medium="image" url="https://starmaid.github.io/blog/img/2026-01-09-space-probe-lights/juno.jpg" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">Portable LAN</title><link href="https://starmaid.github.io/blog/mobile-network/" rel="alternate" type="text/html" title="Portable LAN" /><published>2025-12-18T00:00:00+00:00</published><updated>2025-12-18T00:00:00+00:00</updated><id>https://starmaid.github.io/blog/mobile-network</id><content type="html" xml:base="https://starmaid.github.io/blog/mobile-network/"><![CDATA[<p><img src="/blog/img/2025-12-18-mobile-network/overview.jpg" alt="overview" /></p>

<p>I made a battery-powered LAN network setup to carry with me.</p>

<p><img src="/blog/img/2025-12-18-mobile-network/randbeacon_use.jpg" alt="" /></p>

<p>While working on my <a href="https://github.com/starmaid/randbeacon">randbeacon</a> project, I wanted to manage my WLED setups at OpenSauce with an ethernet interface - so I could use my laptop’s wireless card to connect to the venue’s network. As you can see, the initial setup with this raspberry pi was a little clunky and annoying. The core parts are there, a usb-ethernet adapter and a phone charging battery pack. I tried carrying this around outside while getting photos for that project, and it was the worst.</p>

<p>The core is a RPi3 running <a href="openwrt.org">OpenWRT</a>, a fast and straightforward network router firmware. I also picked up a Gigabit network switch, which is throttled by the RPi3’s 10/100 ethernet port - but this isn’t primarily for speed, this is for when nothing else would work.</p>

<p>Another critical piece is that the switch is powered off 5V DC. This way I was able to make a dead simple cable that connects to a phone charger battery, which is way easier to integrate into a project than naked Lithium batteries and charge controllers. Regulating voltage is annoying, and more expensive anyway if the usecase doesn’t call for extreme current draw.</p>

<table>
  <thead>
    <tr>
      <th>Part</th>
      <th>Cost</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Raspberry Pi 3B+</td>
      <td>Basically free at this point</td>
    </tr>
    <tr>
      <td><a href="https://www.amazon.com/dp/B00A128S24">TP-Link TL-SG105 Switch</a></td>
      <td>$13</td>
    </tr>
    <tr>
      <td><a href="https://www.amazon.com/dp/B0D5CLSMFB">Anker Power Bank “PowerCore 10K”</a></td>
      <td>$21 (used)</td>
    </tr>
    <tr>
      <td>Two scrap sheets of 1/4” Acrylic</td>
      <td>$2</td>
    </tr>
    <tr>
      <td>Handfull of zip ties</td>
      <td>Free</td>
    </tr>
    <tr>
      <td>Cannabalized USB cable</td>
      <td>Free</td>
    </tr>
  </tbody>
</table>

<p>The acrylic was scrap cutoffs from TAP plastics here in the bay area. They go for a dollar a sheet and are great value if the stuff you are making is small. I did round the corners and cut some holes, so the QL laser cutter came in handy again.</p>

<p><img src="/blog/img/2025-12-18-mobile-network/in_bag.jpg" alt="" /></p>

<p><em>This setup fits perfectly in a backpack.</em></p>

<p>Another good thing to know is battery life. Mathematically, the 10 Ah pack could provide about 3 hours and 20 minutes of operation for the rated max of 2.5A (RPI 3B+) + 0.46A (Switch). In my own test of letting everything idle, the battery lasts about 12 hours. With these bounds I know the rough capacity and I’m pretty happy with this.</p>]]></content><author><name>Nicky Masso</name></author><category term="blog" /><category term="networking" /><summary type="html"><![CDATA[]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://starmaid.github.io/blog/img/2025-12-18-mobile-network/overview.jpg" /><media:content medium="image" url="https://starmaid.github.io/blog/img/2025-12-18-mobile-network/overview.jpg" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">Web Soundboard</title><link href="https://starmaid.github.io/blog/web-soundboard/" rel="alternate" type="text/html" title="Web Soundboard" /><published>2025-11-16T00:00:00+00:00</published><updated>2025-11-16T00:00:00+00:00</updated><id>https://starmaid.github.io/blog/web-soundboard</id><content type="html" xml:base="https://starmaid.github.io/blog/web-soundboard/"><![CDATA[<p>Check out the <a href="https://github.com/starmaid/web-soundboard">readme on the github page.</a></p>]]></content><author><name>Nicky Masso</name></author><category term="blog" /><category term="movies" /><summary type="html"><![CDATA[Check out the readme on the github page.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://starmaid.github.io/blog/img/2025-11-16-web-soundboard/soundboard_laptop.png" /><media:content medium="image" url="https://starmaid.github.io/blog/img/2025-11-16-web-soundboard/soundboard_laptop.png" xmlns:media="http://search.yahoo.com/mrss/" /></entry></feed>