Skip to main content

Things I Learned: Sometimes Ham Radio Batteries Don't Charge Over USB-C

 This has happened once before. I hooked up the USB-C charger to the Imuto power brick which is now basically inside Project TouCans, left it over night to charge, and nothing. I woke up to the resounding 60 cycle hum that is the Imuto's internal buck converter stepping up the available voltage of the unit.

Project TouCans Dry Docked and Charing—I hope.


As with most engineering mistakes, there's a a way around ever having this happen again, and as with most engineering mistakes, that way involves process. Interestingly, there are two processes to avoid the not-charging Imuto conundrum. The first way is more interesting, yet less effective:

  1. Unplug  the keyer power input, making sure to leave the TouCans power input plugged in.
    1. You'll know this worked because you'll still hear the hum over the headphones.
  2. Now, plug the charger into the keyer power output from the Imuto. (This particular power brick is nice this way, you can charge it while it's being used.
  3. TouCans internal keyer will reboot. This is because the brick momentarily turns off power altogether.
  4. If the hum goes away, the brick is charging.
  5. If it doesn't, jiggle the power connector until it does.
I find it really cool that the charging current provides enough power to turn off the buck converter immediately!

Here's the much less labor intensive process:

  1. Unplug TouCans and the Keyer from their power inputs.
  2. Plug the charging cable into either of the, now exposed, output power ports from the Imuto brick.
  3. Peel back a piece of tape above the notch in the battery pack rim—remember, the battery pack is a Progresso Soup can. Look for a blinking light inside the can. The Imuto brick power read-out blinks as it charges.

Comments

Popular posts from this blog

Cool Math Tricks: Deriving the Divergence, (Del or Nabla) into New (Cylindrical) Coordinate Systems

Now available as a Kindle ebook for 99 cents ! Get a spiffy ebook, and fund more physics The following is a pretty lengthy procedure, but converting the divergence, (nabla, del) operator between coordinate systems comes up pretty often. While there are tables for converting between common coordinate systems , there seem to be fewer explanations of the procedure for deriving the conversion, so here goes! What do we actually want? To convert the Cartesian nabla to the nabla for another coordinate system, say… cylindrical coordinates. What we’ll need: 1. The Cartesian Nabla: 2. A set of equations relating the Cartesian coordinates to cylindrical coordinates: 3. A set of equations relating the Cartesian basis vectors to the basis vectors of the new coordinate system: How to do it: Use the chain rule for differentiation to convert the derivatives with respect to the Cartesian variables to derivatives with respect to the cylindrical variables. The chain ...

The Alcubierre Warp Drive Tophat Function and Open Science with Sage

I transferred yesterday's Mathematica file with the Alcubierre warp drive[2] line element and space curvature calculations to the  +Sage Mathematical Software System  today, (the files been  added to the public repository [3]).  If you haven't used Sage before, it's a Python based software package that's similar in functionality to Mathematica.  Oh, and it' free.  I also worked a little more on understanding the theory, but frankly, I made far more progress with the software than the theory.  What follows will be a little more of the Alcubierre theory, plus, a cool Sage interactive demo of one of the Alcubierre functions[1], as well as a bit about my first experience with using Sage. Theory The theory is fun, but it's moving slowly.  Here's the chalk board from this morning's discussion Alcubierre setup the derivation using something called the 3+1 formalism which means we consider space to be flat, (in this case), slices that are labelled ...

How Many Files Can You Add to a GPT Project? An Interview with GPT-5 on Limits, Context Engineering Tips, and Chats

 Setting the scene: I’m tinkering with Project TouCans, knee-deep in radio logs, SQLite dumps, and Cesium code. Naturally, I’m wondering if shoving all this into one GPT Project is a recipe for brilliance… or for disaster. So I turn to Vril — you know, after Brainy from the Legion of Super-Heroes , because what else do you call your AI sidekick who always has the answers? Time to ask him straight up. [ As an aside, yes, GPT-5 has decided to sometimes call me Vail. I'm not sure why to be honest. Also, I asked Vril, er GPT-5, to write up our interview for me. Apparently, me asking it to 'Bro' up a few stories, just for fun, has convinced Vril that I use 'Like,' more than I actually might. ] Me (Vail): So Vril, how many files can I throw into a GPT Project before it just starts choking? Like, is there some magic number where the context window taps out and everything falls apart? GPT-5 (Vril): Great question. There’s no single hard file limit. What matters is ...