Project Logs

Collapse

• Doom and Some Other Less-Trivial Demos

  Kevin Santo Cappuccio • a day ago • 0 comments

  A lot of these shots will be cut into the Hackaday Prize entry video, but I'm gonna post them here anyway so I don't feel like I've wasted time making these if I decide some of them don't fit.

  Doom Over a Jumperless

  Doom is the most click-baity demo you can do. And I support it (even though I suck at actually playing Doom)

  Someone on Twitter asked if the crosspoint switches would interfere with fast data signals. The answer is no, they won't, they're rated to 50MHz at 3dB rolloff. The physical breadboard will have a much larger effect at those frequencies, so if it works on a regular breadboard, it should work on a Jumperless (wrt frequency, current and voltage have their own limits). 

  This is the awesome project doom-nano which is stripped down enough to run on an ATMEGA328P at ~15 fps. Note that the enemies don't die when I shoot them, that hasn't been implemented yet.

  The nerd-sniper who got me actually was asking about SPI displays, I didn't have a Arduino Nano ESP32 at the time, but I will today (thanks Amazon). So expect a demo of real doom running on a color display soon. 

  16x2 LCD

  And my video light Fuck mask gets its time in the spotlight.

  Making this one revealed a bug in the routing code here it wasn't checking the other end of the "bounces" in certain arrangements. So yeah, 2 days of debugging for a 22 second video, that's approaching Kubrick's shooting-to-runtime ratio.

  Some 7400-Series Logic Stuff

  Here I threw together a random logic circuit with the chips I had laying around, and used a 555 as the clock source. Near the end, I take out the 555 and use the Jumperless's DAC making a square wave as the clock. Which might be useful if you're building just part of something and you don't want to screw around with the clock source.

  There's a simple text-based wave generator menu that I'm using to control the frequency and stuff. It looks like this.

  On the Wokwi project I had a potentiometer connected to the blue clock line, that's what tells the Jumperless that I want a DAC connected there.

  This is the same circuit again:

  Magic Flames Released

  This is the silly intro shot, same circuit as above (and part of it is redundant).
  
  Obviously, circuits don't blow up like that when you cut one wire. So let's look behind the curtain and see what I did 

  It's cigarette filter wrapped in NiChrome wire and submersed in a foil tray filled with vape juice hidden behind the breadboard then hooked up to a big 12V lead-acid battery when I wanted it to go off. I'm actually just cutting the 5V power in the video.

  This is what it looked like afterwards 

  Ha. 

  I also tried just cutting 2 jumpers connected to the leads of the lead-acid battery, but the sparks weren't dramatic enough and too quick to be shot on video. 

  Another attempt was made by emptying out the powder from a bullet and igniting it, but modern smokeless powder is, well, smokeless. Like really surprisingly so. I even mixed it with sugar and Ammonium Dichromate but it never really looked right. So vape juice it was!

  Crosspoint Superzoom

  This is just to give people a but of an understanding of what's going on inside a crosspoint switch. Not really a demo, but it was made so people understand that the Jumpeless isn't reading and simulating your signals, just passing them through an analog CMOS switch.

  If you want to play with that crosspoint demo in Falstad, here's the link to that circuit.

  And the transistor-level analog CMOS switch is here.

  Rail Selector Switch

  This is a fun little shot of the supply rails being switched in stop motion. 

  Anyway, I think that's all the video I have for now. But stay tuned for the Hackaday Prize entry video where I cut all this together and talk at you.

• Getting Started Using Your Jumperless

  Kevin Santo Cappuccio • 09/06/2023 at 17:26 • 0 comments

  Cool, so you have this super sexy object now. How do turn it into an actual prototyping tool? The answer is software.

  After you've unboxed (and maybe assembled) your Jumperless, we're going to need a way to talk to it. 

  Now, the Jumperless is very open and will accept netlists from any program with some basic formatting, if you hate Wokwi and want to use something else, this project log should give you an idea of what format it accepts over serial so you can write your own Bridge to any software you like. But for now, I'm focusing on Wokwi because I think it's better to have solid support for one workflow than shitty support for a bunch.

  First, we need to download the App and latest firmware here.

  Updating The Firmware

  I ship these with the latest firmware installed, so if you just received your Jumperless in the mail, you can skip the firmware update. But I usually push minor fixes to that firmware.uf2 file every few days, so it's probably worth doing anyway.

  On your Jumperless, there will be a little button on the opposite side of the USB port. This is the USB Boot button and works exactly the same as a Raspberry Pi Pico.  

  1. Hold the USB Boot button and plug the Jumperless into your computer. 
  

  2. A drive should pop up called RPI-RP2. Drag the firmware.uf2 file into it and it should reset and you're done!

  Installing the App

  I'm showing this on a fresh install of macOS, but Windows should be roughly the same.

  1. On the releases page, download JumperlessWokwiBridgeMacOS.zip (or the .exe for windows) and firmware.uf2
  

  2. It should automatically unzip in your downloads folder. Note that this won't run correctly from anywhere but your Applications folder, so drag it there.

  3. Click it to try to run it. Unless you've set your security setting to allow apps from anywhere, it's going to complain.

  4. Click Cancel and go to  Settings > Privacy and Security > scroll down and click Open Anyway

  5. It's going to complain again and just click Open

  Hot tip: run 

  sudo spctl --master-disable

  in Terminal to give you another checkbox for Anywhere under Settings > Privacy and Security > Allow Apps From. And you won't have to go through this again for other shoddy software.

  6. If everything goes well, you should now be presented with a Terminal window like this

  Note that on MacOS, it should just autodetect and connect to the Jumperless if it's plugged in when you start the app, if not, just plug it in and type 'r' to rescan the ports until it finds it. 

  Okay, now the app is set up, what do we paste into there to connect to our Wokwi project?

  Getting Wokwi Set Up

  You'll need a stable link to your Wokwi project, and it will only make one when you're signed in and have saved your project to "My Projects". After that the links are saved in a text file in the JumperlessWokwiBridge app and you'll be able to select projects you've used before from a list.

  1. Go to wokwi.com
  2. Click Sign Up/Sign In and enter your email (or use Google or Github)
     
  3. Click the link they email you to sign in
     
     
  4. Click Go To Your Projects, then New Project > Arduino Nano
     
     
     
  5. Click Save and give your project a name
      (note that the URL has now changed to a unique link)
  6. Click blue “+” (top center) to Add New Part and scroll down to Half Breadboard and click it
       It will put it somewhere random, so click somewhere that’s not a hole to drag it.
     
  7. Open the JumperlessWokwiBridge App and resize the windows so you can see both
     (on mac it will autodetect the port if it’s plugged in, on windows you’ll need to select the COM port here first, if the Jumperless wasn’t connected when you opened the app, press ‘r’ the Enter to rescan the ports)
  8. Copy the URL of the Wokwi project you just made
     
  9. Paste that URL into the Bridge App window and press Enter
     
     
  10. Name the project and hit Enter (it will save the link so next time you’ll only need to choose it from...

  Read more »

• Ṭ̴̯̿̂h̶̫̏̀ę̵̙̒ ̷̩̉C̴̖̞̀͝ọ̵̬̎̔ḓ̵̓e̸̥̞̓̓ part 4 - Picking Colors and Putting Them On Your Retinas

  Kevin Santo Cappuccio • 09/04/2023 at 18:00 • 1 comment

  Table of Contents  (bolded ones are in this project log)

  • General terms - the names I've decided to call things
  • What's being stored - how the overall state is stored
  • Pathfinding - how we find valid paths for each connection
  • Controlling the switches - how we send that data to the CH446Qs
  • LEDs - how we choose unique colors for each net
  • The Wokwi bridge app - how we scrape the Wokwi page for updates

  If you're wondering why you feel a strange sexual attraction to this board, I can give you a hint...

  I didn't want to do the LEDs at first because it seemed a bit out-of-scope. But after using the prototype board without them, I found that it involved a lot of counting rows to find where you're connecting things. And that gets pretty tedious. 

  Around the same time, I had ended my month-long search for anyone who sells just the metal spring clips from a breadboard and resigned to having custom spring clips made by Shenzhen Fulimei Technology Co. LTD. 

  Hot tip for makers that want a bunch of some thing custom made using a non-so-common process: put your drawings and requirements up on made-in-china.com, you'll get a ton of quotes within days and just pick your favorite. 

  I'm glad I did, because using this thing is sooo much smoother now, you really only have to look at the board for the first connection and then everything else can just be counted as an offset from there. Also, the new versions of the breadboard shell have every 5th embossed number raised (which is actually super weird on breadboards because they count from 1, so there's 3 holes between 1 and 5, and 4 holes between the rest, enjoy being bothered by that forever) which makes it even easier to locate where you're connecting stuff.

  How the colors are chosen

  It would be really cool if the colors would correspond to the colors in the Wokwi diagram, but there's a couple of problems with that.

  First:

  All the wires default to green, and having to select a unique color for each wire is kind of a pain in the current version of Wokwi. I know they'll eventually work on something to change this, but their voting system of which features they should work on next shows it's a fairly low priority.

  The other issue is this:

  Currently, they only support 15 HTML colors. So having only 15 different possible nets with unique colors (fewer, because black, grey, and brown wouldn't really show up on RGBs)

  So we're just gonna pick our own colors.

  The special nets have hard-coded colors, they are as follows:

    rgbColor specialNetColors[8] = {      
    {00, 00, 00},
     {0x00, 0xFF, 0x30},    //GND     - Green 
     {0xFF, 0x41, 0x14},    //5V     - Red leaning towards orange {0xFF, 0x10, 0x40},    //3.3v    - Red leaning towards purple 
     {0xeF, 0x78, 0x7a},    //DAC 0-5V- Pinkish White  (changes brightness and hue based on output magnitude) 
     {0xeF, 0x40, 0x7f},    //DAC +-8V- Purplish White (changes brightness based on output magnitude, hue for positive or negative) 
     {0xFF, 0xff, 0xff},    //Current Sense+ - Yellow 
     {0xff, 0xFF, 0xff}};   //Current Sense- - Blue 
     
     rgbColor railColors[4] = { 
      {0xFF, 0x32, 0x30},    //GND - Green 
      {0x00, 0xFF, 0x30},    //5V - Red 
      {0xFF, 0x32, 0x30},    //GND - Green 
      {0x00, 0xFF, 0x30}};   //5V - Red
  

  Here's what those look like:

  Note the bottom rail is 3.3V, top rail is 5V. pot1-sig is DAC 0, pot2-sig is DAC1.

  The colors are saved at full brightness and scaled down to the default brightness or the brightness you set in the menu when they're displayed.

  For the other nets, here's the general algorithm:

  • Get the number of unique nets and divide that by 255 (that's the full color wheel in the NeoPixel Library) to get a color distance
  • Check if the hue at (color distance * 1) is the too close to any of the special nets
    • If it is, add 1 to the number of unique nets and calculate a new color distance, then try again with an offset (color distance/2)
  • If not, set that hue for the net and check the next net at (color distance * 2) etc...

  Here's how...

  Read more »

• Ṭ̴̯̿̂h̶̫̏̀ę̵̙̒ ̷̩̉C̴̖̞̀͝ọ̵̬̎̔ḓ̵̓e̸̥̞̓̓ part 3 - Driving the CH446Qs

  Kevin Santo Cappuccio • 08/30/2023 at 03:14 • 0 comments

  Table of Contents  (bolded ones are in this project log)

  • General terms - the names I've decided to call things
  • What's being stored - how the overall state is stored
  • File Parsing - how we fill in those arrays
  • Pathfinding - how we find valid paths for each connection
  • Controlling the crosspoint switches - how we send that data to the CH446Qs
  • LEDs - how we choose unique colors for each net
  • The Wokwi bridge app - how we scrape the Wokwi page for updates

  
  Controlling the Crosspoint Switches

  What crosspoint switches crave

  Okay, so now we have all our paths filled out with what chips need to have which X and Y inputs connected to make the magic happen.

  The CH446Qs are basically clones of the MT8816, except for one important difference, they accept serial addressing. The datasheet is kinda vague about how, but it turns out it's just a kinda weird version of SPI. 

  Basically, all the chips see the same data signal, and whichever one sees a pulse on the STB when the last bit comes in will connect or disconnect the selected X and Y inputs. The state of the DAT line when the Strobe comes in determines whether it's connecting or disconnecting. That stretched out clock line shows that it doesn't care about real time, which comes in handy.

  PIO State Machine

  So I have to do something that's kinda like SPI but not quite, this looks like a job for the RP2040 PIO State Machines.

  Even knowing assembly, the learning curve for writing a PIO program is steep. The documentation is really hit-or-miss, the examples are uncommented and written like they're playing code golf, insanely terse. Like these people do realize you can name variables after what they do, right? And these are the Official examples in the datasheet. Anyway after a few days of staring at what looks like gibberish, it starts to click.

  I copied the SPI.pio example and edited it from there. Let me try to explain some of the things I learned to hopefully make it easier for you to write a PIO program in the future. 

  I'm just compiling this with the online pioasm compiler and then pasting the compiled code into spi.pio.h
  

  https://wokwi.com/tools/pioasm

  Here's where we are:

  ;this is basically spi but it sets a system IRQ on the last bit to allow the chip select pulse to happen
  
  
  
  .program spi_ch446_multi_cs
  .side_set 1
  
  .wrap_target
  bitloop:
  
      out pins, 1        side 0x0 [2]
      
      nop                side 0x1 [2]
  
      jmp x-- bitloop    side 0x1
  
      out pins, 1        side 0x1
  
      mov x, y           side 0x1
  
      irq  0             side 0x1
      
      wait 0 irq 0 rel   side 0x1
      
      jmp !osre bitloop  side 0x0
  
  public entry_point:                 ; Must set X,Y to n-2 before starting!
  
  
      pull ifempty       side 0x0 [1] ; Block with CSn high (minimum 2 cycles)
      
      nop                side 0x0 [1]; CSn front porch
  
  
  .wrap
  
  

  What wasn't explained well is what the hell a sideset pin is. Basically you do your normal-ish assembly code on the left, and then each operation also affects the sideset pin on the right. It's kind of a hack to allow you to control 2 pins in a single clock cycle. In this case, the sideset pin is attached to the CLK, and pins, 1 is DAT.
  

  So, whats going on is that in the regular code, I'm sending a byte to the sm register with this line
  

  pio_sm_put(pio, sm, chAddress);

  (the last bit of chAddress is set to 1 or 0 depending if I want to connect or disconnect)

  and that pull ifempty will pull in a byte to the working register and send it out one bit at a time while toggling the clock. When it's out of data to send, it triggers a system interrupt request that can be seen outside of the PIO state machine and I deal with it in an ISR in CH446Q.cpp

  At this point, here's where we are in the timing diagram:

  Now we need to select the correct CS line to make the right chip make the connection

  void isrFromPio(void)
  {
    switch (chipSelect)
    {
    case CHIP_A:
    {
      digitalWriteFast(CS_A, HIGH);
      break;
    }
    case CHIP_B:
    {
      digitalWriteFast(CS_B, HIGH);
      break;
    }
    case CHIP_C:
    {
      digitalWriteFast(CS_C, HIGH);
      break;
    }
    case CHIP_D:
    {
   digitalWriteFast(CS_D,...

  Read more »

• Ṭ̴̯̿̂h̶̫̏̀ę̵̙̒ ̷̩̉C̴̖̞̀͝ọ̵̬̎̔ḓ̵̓e̸̥̞̓̓ part 2 - Pathfinding

  Kevin Santo Cappuccio • 08/25/2023 at 01:37 • 0 comments

  Table of Contents  (bolded ones are in this project log)
  

  • General terms - the names I've decided to call things
  • What's being stored - how the overall state is stored
  • File Parsing - how we fill in those arrays
  • Pathfinding - how we find valid paths for each connection
  • Controlling the crosspoint switches - how we send that data to the CH446Qs
  • LEDs - how we choose unique colors for each net
  • The Wokwi bridge app - how we scrape the Wokwi page for updates

  Pathfinding

  This is the really tricky part. I probably wrote all this code about 4 times, trashed it and started over from scratch with only the lessons learned from the last attempt. Earlier versions would add connections one at a time, but you'd end up in weird states because it has no knowledge of what other paths it needs to make room for. So the final version here clears the connections from the last update, takes in all the connections to be made, and finds paths for the whole board every time you add a new wire. All the old connections usually follow the same paths as last time unless they need to be nudged over to make room for some other path, and the actual connection won't be interrupted at all.

   Here's the schematic of just the crosspoints, the Nano header, and the breadboard.

  If you look closely, you'll see that there generally 2 connections (I'm calling these 2 connections Lanes between each breadboard chip, except for the chip that is across from it on the breadboard. And every breadboard chip has one connection to each of the special function chips. The pins on the Nano header has a connection to 2 special function chips (interleaved to make it easier to connect continuous pairs of pins to the breadboard).

  Here's the high level outline of what NetsToChipConnections.cpp is doing

  • Sorts all the paths by Net This sort of sets priority, lower net numbers (so all the special function nets) will be picked first and are more likely to have direct connections chosen
  • For each path, find the start and end chips
    • If there are multiple candidates (Nano header pins will have 2) store both
    • If both start and end chips have candidates in common, choose that chip (this would make it a bounce)
    • Assign node and path types (BB to BB, NANO to BB, BB to SF, etc...)
    • Sort a list of chips from least to most crowded (by how many connections that chip has used)
    • Resolve the candidate chips by going down the sorted list of chips and picking the less crowded chip
    • Search for a direct path between those 2 chips
      • If there isn't one, swap to the other candidate chips and search again
      • If one of the nodes is a special function with multiple options swap the nodes with their equivalents and search again
      • If there still isn't a direct path, set the altPathNeeded flag and move on At this point, any paths that have a simple direct connection should be done, now we need to deal with the ones that don't
  • Resolve alt paths, if the altPathNeeded flag is set
    • Search through all the other chips until you find one that has a direct connection to both the start and end chips
      • If one chip is connected to the X inputs and the other the Y inputs, set that connection on chip[2] and x[2] y[2]
      • If they're both on X or both on Y, set the sameChip flag and the x[3] or y[3] as -2 to denote that that connection is a bounce and it doesn't matter which pin is chosen, as long as it's available
  • Resolve uncommitted hops, anything set as -2 gets a random unconnected pin assigned to it at the very end so it doesn't take up connection space

  There's a lot more subtlety to this but if I go into any more detail you might as well just read the code itself. It will all be in the file NetsToChipConnections.cpp, and if you're running it on a Jumperless or just an RP2040, you can set the Chip Connections and Chip Connections Alt debug flags and it will show you everything it's doing in a somewhat nicely formatted way. There are comments in the code but there are a lot of nested array things that can get pretty confusing, if...

  Read more »

• Ṭ̴̯̿̂h̶̫̏̀ę̵̙̒ ̷̩̉C̴̖̞̀͝ọ̵̬̎̔ḓ̵̓e̸̥̞̓̓

  Kevin Santo Cappuccio • 08/18/2023 at 18:11 • 0 comments

  I'm going to do a high-level explanation of what the code in the Jumperless is actually doing. There's a lot going on and it's in a bunch of separate files so I think it will be helpful for people who what to understand or improve upon it.

  Table of Contents  (bolded ones are in this project log)

  • General terms - the names I've decided to call things
  • What's being stored - how the overall state is stored
  • File Parsing - how we fill in those arrays
  • Pathfinding - how we find valid paths for each connection
  • Controlling the crosspoint switches - how we send that data to the CH446Qs
  • LEDs - how we choose unique colors for each net
  • The Wokwi bridge app - how we scrape the Wokwi page for updates

  This is going to be really long and so I'll be filling out parts as I finish them in no particular order.

  General terms

  I've made up terms for things here that may or may not be the formal definition, so I should probably let you know what I chose.

  Breadboard Chips - This refers to the 8 CH446Q crosspoint switches (labeled A-H) that have their Y pins connected to the breadboard. This excludes Chip L which actually has it's X pins connected to the 4 corners of the board (rows 1, 30, 31 (b1), 60 (b30))

  Special Function Chips - This refers to the 4 crosspoints (labeled I-L) that connect to everything else; the Nano header, power supplies, DACs, GPIO from the RP2040, etc...

  Nodes - Also used synonymously with Row especially when it's on the breadboard or Nano Header. And end point to a bridge

  Bridges - Just 2 nodes that should be connected

  Nets - Groups of nodes and bridges that should all be electrically connected to each other

  Bounce - Sometimes there won't be an available path directly from one node to another, so in this case it will pick another chip with a free path to the start and end chips and "bounce" through it.

  Paths - Similar to a bridge, except that it contains data for how that bridge is connected. So it will have which chips and which X and X pins are needed to make the connection

  Defines

  You'll see a lot of these, they're all in JumperlessDefinesRP2040.h. But the point of this whole this is so you don't have to dig through the code, so I'll put the abridged version here:

  #define CHIP_A 0
  ...
  #define CHIP_L 11
  
  
  #define t1  1
  ...
  #define t30 30
  
  #define b1  31
  ...
  #define b30 60
  
  
  #define NANO_D0  70 //these are completely arbitrary
  ...
  #define NANO_A7  93
  
  
  #define GND  100 #define SUPPLY_3V3  103
  #define SUPPLY_5V  105
  
  #define DAC0_5V  106 #define DAC1_8V  107
  
  #define CURRENT_SENSE_PLUS  108
  #define CURRENT_SENSE_MINUS  109
  
  #define ADC0_5V 110
  #define ADC1_5V 111
  #define ADC2_5V 112
  #define ADC3_8V 113
  
  #define EMPTY_NET 127
  
  

  What's being stored

  There are a few big arrays of structs that store the overall state of everything. Here are the main ones:

  chipStatus

  This stores the actual hardware layout of each of the 12 crosspoint switches, like what is physically connected where and whether that path is being used. In the code it's and array called ch[12] and it's in MatrixStateRP2040.h

  //the struct
  struct chipStatus{
  int chipNumber;
  char chipChar;
  int8_t xStatus[16]; //store the bb row or nano conn this is eventually connected to so they can be stacked if conns are redundant
  int8_t yStatus[8];  //store the row/nano it's connected to
  const int8_t xMap[16];
  const int8_t yMap[8];
  };
  
  //the array of those structs
  struct chipStatus ch[12] = {  {0,'A',  {-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1}, // x status  {-1,-1,-1,-1,-1,-1,-1,-1}, //y status  {CHIP_I, CHIP_J, CHIP_B, CHIP_B, CHIP_C, CHIP_C, CHIP_D, CHIP_D, CHIP_E, CHIP_K, CHIP_F, CHIP_F, CHIP_G, CHIP_G, CHIP_H, CHIP_H},//X MAP constant  {CHIP_L,  t2,t3, t4, t5, t6, t7, t8}},  // Y MAP constant
  ... {10,'K', {-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1}, // x status {-1,-1,-1,-1,-1,-1,-1,-1}, //y status {NANO_A0, NANO_A1, NANO_A2, NANO_A3, NANO_D2, NANO_D3, NANO_D4, NANO_D5,...

  Read more »

• Boxes within shirts within boxes

  Kevin Santo Cappuccio • 07/26/2023 at 20:58 • 9 comments

  Edit - this is me from the future. The new boxes got here and this is what they look like in real life:

  *pop*

  It turns out the cardboard from Ponoko is a pain to fold. I have to cut it halfway through, peel off half the thickness, coat the entire thing in clear paint, then bend it while it's still sort of wet for it to keep it's shape.

  I'll put up photos of that whole process soon. But in the future I'll probably use a better material for this.

  I did order a Matte cutter to help with this, but it isn't here yet so I came up with a super ghetto solution that works surprisingly well. 

  Super gluing a craft knife blade to 3D printed cube I had laying around. I taped a piece of the cardboard to the bottom before gluing to set the depth. I can just drag it along a ruler and it cuts to the right depth. Probably should have thought of this before spending $40 on effectively the same thing.

  Okay now back to the past....

  
  

  So this is me kind of procrastinating, but I've designed an inner case to keep the Jumperless nice and cozy inside it's box. I figured instead of using disposable packing materials, I'd have some shirts made and use them instead of bubble wrap.

  But having the Jumperless just loose in that shirt looks kinda ghetto to me.

  So I needed a smaller box to actually keep it safe wrapped up in that shirt that still leaves room for the other stuff. So this full foam cutout wasn't gonna cut it. 

  Originally it was just going to be 2 squares of cardboard with foam around it, but when I was ordering the cardboard and foam cutouts from Ponoko, I noticed they really only charge by the area of material, the actual cuts only seem to affect the cost by a few percent.

  I also kinda felt like this logo wasn't getting enough love.

  So I designed this box which should also serve as a storage case for people who like to keep their things in boxes.

  The cool thing is how it (hopefully) stays shut. This oval at the top should slot into the cutout at the bottom, and there should be enough friction and foldiness to keep it closed. 

  We'll see. 

  I should do a writeup on my failed attempts to use my 3018 cheapy CNC machine to hot wire cut foam. But now that Ponoko will cut foam for you, I decided to leave that to the pros.

  Anyway, here's a simulated experience of opening a Jumperless now

  **Angelic noises**

View all 7 project logs