Browsed by
Category: Technical

Can cheaper, faster robotics revitalize modern manufacturing and transform the military?

Can cheaper, faster robotics revitalize modern manufacturing and transform the military?

It feels like the American industrial and manufacturing landscape has been left behind in the digitalization revolution. But recent changes demonstrated in both Ukraine and a small robot company in Pittsburg may be pointing to the coming revolution.

Gecko is a scrappy robot company founded by a college senior that saw workers spending hours putting up dangerous scaffolding to check and fix pipes in a power plant. What if he could build robots to scale around the pipes and check and fix them? It turns out they could – and it is revolutionizing maintenance in refineries and energy infrastructure across the country. The robots now no longer can crawl and inspect/repair – but they can create new digital maps of a plant’s infrastructure. Inspections are taking orders of magnitude less time. Plants can have their actual systems instantly remapped/re-diagrammed instead of relying on out of date schematics.

It turns out someone else has the same problem: the military. Systems like Gecko allow the navy to build and repair ships faster. Gecko’s small robots reduced nuclear submarine inspection times from 300 hours to just 6 hours. But this revolution is bigger than just repair of existing systems.

The war in Ukraine is now being won not by ‘exquisite’, complex, and exorbitantly expensive weapons systems. Instead, it’s being won by swarms of low-cost drones. Million dollar tanks are being disabled by $200 drones carrying explosives. Military experts around the world are watching Ukraine and re-thinking everything. Even before the Ukraine war, the US navy was already started the move from big capital ships to cheaper, faster to build modular ships.

Anduril wrote a paper in 2024 that goes a step further. They claim that these low-cost robotics and AI systems are making existing weapons systems vulnerable and outdated. Modern, 1st world weapon systems are too complex and hugely expensive. They take too long to make in quantities required for something beyond a short war. What is needed is to establish fast, cheap, commercial manufacturing of these systems that can be built and deployed rapidly. This is leading to a revolution of automated manufacturing.

The future is not going to belong to giant, expensive, monolithic systems – but fast, easy to build, capable systems built in large numbers.

Give the article a read.

Compute! (Gazette) magazine is back

Compute! (Gazette) magazine is back

Edwin “James” Nagle decided to see who actually owned the COMPUTE! magazine trademark. It turns out, nobody did. The name and assets of COMPUTE! were traded and sold and eventually put up as collateral which when the loan failed, reverted to a company that no longer existed.

He stepped in and got the rights from the US patent and trademark office and now officially has revived the Compute! Gazette magazine – complete with type-in programs!

Here’s his excellent talk on the subject.

Oh – and he considered the old print versions of the magazine he now owns the copyrights for as ‘free and open source’.

CUDA with WSL2+Docker on Windows for Kokoro

CUDA with WSL2+Docker on Windows for Kokoro

In order to get Kokoro text-to-speech to work with my 5090 GPU inside a Docker container on Windows, I had to get the CUDA setup inside WSL2 using Docker images on Windows. Here were the helpful links:

Setup the WSL image with CUDA and Docker support.

  1. Ensure you have WSL2 installed on your Windows desktop
  2. Install Docker for Windows
  3. Reboot
  4. Ensure you have the latest NVidia GPU driver installed on your Windows desktop
  5. Ensure you have the latest NVidia CUDA sdk installed on your Windows desktop
  6. A system reboot here is a good idea
  7. Ensure you have Microsoft Visual Studio installed for best results
    • The CUDA sdk requires you have Visual Studio 2019, 2022, or 2026 installed. I have found 2022 is a solid version and seems to work well, but haven’t tried 2019 or 2026 recently.
    • Note you need to use the ‘Visual Studio x64 Native tools for VS2022’ command prompt if you expect to run command line compiler operations.
  8. Now you need to install CUDA support inside WSL NVidia guide
    • First follow the instructions to ensure Docker support
    • Second follow the installation of CUDA Toolkit and CUDA Developer Tools inside WSL2 on an Ubuntu 24.04 (or later) WSL distro.
  9. Optional: install nvcc so y
    • sudo apt install nvidia-cuda-toolkit
    • nvcc –version
      • This prints out the version and ensures the nvcc sdk compiler is working inside your WSL image
  10. Ensure Docker Desktop for Windows is running on your desktop
  11. Turn on support for Docker in WSL
    • Settings -> From the General tab, enable Use WSL 2 based engine.
    • Reboot
  12. Ensure your WSL image inside WSL has Docker support enabled
    • Settings -> Resources -> WSL integration tab -> Find and enable the slider for the WSL image under ‘Enable integration with additional distros’
  13. I had to reboot my system at this point to get both the WSL and Windows Docker Desktop to see each other properly
  14. After reboot, ensure Windows Docker Desktop is running
  15. Set the user permissions in the WSL session to enable access (permission denied while trying to connect to the docker API at unix:///var/run/docker.sock)
    • sudo usermod -a -G docker <username>

Now run the Kokoro docker command inside your WSL2 image:

  • CPU only:
    • docker run –gpus all -p 8880:8880 ghcr.io/remsky/kokoro-fastapi-cpu:latest
  • NVidia gpu:
    • docker run –gpus all -p 8880:8880 ghcr.io/remsky/kokoro-fastapi-gpu:latest-cu128

Connect with the default web link:

Subsequent runs:

  1. Ensure the Docker Desktop is running
  2. Start the WSL -d <image> you set up in the first part that’s has all the CUDA stuff installed
  3. run the Kokoro docker command inside WSL
  4. Connect your web browser to the localhost address

Raw WSL history (commands in WSL)

You can’t follow this 100% directly. Note you have to stop and restart/reboot WSL and desktop as you do the other steps above.

# NVidia CUDA setup inside WSL2 Ubuntu 24.04 image
wget https://developer.download.nvidia.com/compute/cuda/repos/wsl-ubuntu/x86_64/cuda-wsl-ubuntu.pin
sudo mv cuda-wsl-ubuntu.pin /etc/apt/preferences.d/cuda-repository-pin-600
wget https://developer.download.nvidia.com/compute/cuda/13.3.0/local_installers/cuda-repo-wsl-ubuntu-13-3-local_13.3.0-1_amd64.deb
sudo dpkg -i cuda-repo-wsl-ubuntu-13-3-local_13.3.0-1_amd64.deb
sudo cp /var/cuda-repo-wsl-ubuntu-13-3-local/cuda-*-keyring.gpg /usr/share/keyrings/
sudo apt-get update
sudo apt-get -y install cuda-toolkit-13-3
exit
sudo apt install nvidia-cuda-toolkit
nvcc --version
exit
sudo usermod -a -G docker matt
exit
docker run --gpus all -p 8880:8880 ghcr.io/remsky/kokoro-fastapi-gpu:latest-cu128

Untested but possibly interesting:

WordPress 7.0 messed up the internal editor’s font?

WordPress 7.0 messed up the internal editor’s font?

When I updated to WordPress 7, I noticed the font in the post editor/publisher was kind of messed up. Turns out, it’s a part of the theme you’re using. If your theme doesn’t have specific fonts specified, you can get some ugly fallbacks.

The fix?

In any Block Editor page, such as editing a post, 3 dot menu, Preferences, then Appearance, and then disable “Use theme styles.”

https://wordpress.org/support/topic/editor-font-is-wrong/
Hackers increasingly target your VS Code extensions

Hackers increasingly target your VS Code extensions

The TeamPCP hacker group on the Breached cybercrime forum claimed it had gained access to nearly 4,000 private GitHub repositories via the breach.

GitHub has officially confirmed, via an X post today, that thousands of its internal repositories were breached after an employee’s device was compromised through a malicious Visual Studio Code extension.

The group alleged that it had exfiltrated internal source code and other private data, and stated that it was seeking at least $50,000 from potential buyers for the stolen material. “This is not a ransom,” the group wrote in its post, adding that it intended to sell the data rather than extort GitHub directly, and threatening to leak the repositories publicly if no buyer emerged.

TeamPCP has previously been linked to several high-profile campaigns involving platforms such as GitHub, PyPI, npm, and Docker. At the same time, malicious VS Code extensions have repeatedly surfaced in recent years as an increasingly effective vector for breaches and malware delivery.

Upscaling pixel art in old Sierra games

Upscaling pixel art in old Sierra games

Old Man Yells at Code decided to write an upscaler for old Sierra games like Kings Quest and Space Quest. Upscaling old pixel art is not as simple as you would expect since the old Sierra games used vector art. He does a great job discussing the tradeoffs and making a working version – even if some of the charm of those old games is the pixelization artifacts.

Every retro sound device on an 8-bit card

Every retro sound device on an 8-bit card

Finding sound cards for your retro PC setup is hard. Used sound cards can easily run you more than $100.

PicoGUS is an 8-bit ISA sound card and CD-ROM drive emulation on the Raspberry Pi Pico’s RP2040 microcontroller. PicoGUS can emulate a wide variety of sound cards as connect your old IDE CD-ROM drives:

  • Gravis Ultrasound (GUS) – the primary focus of PicoGUS, hence the name
  • Sound Blaster 16 (OPL3) / Sound Blaster Pro 2 (OPL3) / AdLib (OPL2)
  • MPU-401 (with intelligent mode) – outputs MIDI data on 3.5mm MIDI TRS connector
  • Tandy 3-voice
  • CMS/Game Blaster
  • Game port joystick
  • Panasonic/MKE CD-ROM

It’s not quite perfect (see the compatibility list), but

Available at Joe’s Computer Museum Shop for $50

Retro IDE replacement

Retro IDE replacement

Retro computing has a hardware problem. Physical cdrom and hard drives wear out and die every year – with no replacements on the horizon as most manufacturers have quit making them decades ago.

Enter PicoIDE from the creator of the retro sound card PicoGUS (emulates Gravis UltraSound, Sound Blaster 16 (OPL3) / Sound Blaster Pro 2 (OPL3) / AdLib (OPL2), CMS/Game Blaster and Tandy 3-Voice, and supports MIDI output with MPU-401 intelligent mode emulation). PicoIDE is an IDE/ATAPI drive emulator for retro PC’s. It lets you load and run hard drive images as well as perfectly emulates CDROM drives with full redbook audio support. You run them all from a microSD card you load with images. It doesn’t get much easier than that.

  • Emulates ATAPI CD-ROM and IDE fixed hard drives
    • Images stored on microSD card
    • .bin/.cue or .iso image support for CD-ROM
    • .img/.hda/.vhd/.hdf for HDD, supporting LBA or CHS
  • Built-in CD audio analog output on 3.5mm jack and MPC-2 header, driven by TI PCM5100A DAC
  • Supports PIO modes 0-4 and multi-word DMA modes 0-2
  • Headers for SPI peripheral, external drive activity LED and action button

Pre-Order Here:  https://www.crowdsupply.com/polpotronics/picoide

Federal agencies will no longer require SBOMs

Federal agencies will no longer require SBOMs

Federal agencies will no longer be required to solicit software attestations that they comply with NIST’s Secure Software Development Framework (SSDF).

The SBOM requirement has lead to a small cottage industry of scanning and CI tools that provide this functionality. It will be interesting to see how that all develops, but constantly changing industry standards and practices is not good for businesses.

The US used to thoughtfully and carefully roll out changes like this in the past. In our increasingly polarized political climate, software companies are increasingly whipsawed back and forth. Adding and removing requirements like this is not a zero-cost change. Compliance burdens cost money, time, and credibility to any company based here in the US.