NDLR – MIDI Sequenced Apreggiator

Darryl McGee and Steve Barile of Conductive Labs have developed the NDLR (pronounced Noodler), a 4-part poly sequenced arpeggiator, chord and drone player based on the Teensy 3.2.

The guys at Conductive Labs came with a unique solution to break down music theory into knobs and controls. The NDLR has four parts that can play up to 8 synths.  The PAD part is a chord player.  Press one of the 7 chord buttons and all the other parts change notes to match.  There are also 2 “Motifs” which are sequenced arpeggiators.  The Drone part can play a single continuous note like a traditional drone does… or choose from various retrigging options, such as having the note retrigger on a chord change, the down beat, every beat, up beat, etc.

Among the many advanced features packed into the NDLR is a pattern and rhythm editor that lets you create custom arpeggios.  You can also save your patches and settings for later recall with the 8 global slave slots, 20 user patter slots, and 20 user rhythm slots.

You can get a NDLR through their IndiGoGo campaign

This video is of a performance by Graig Anthony Perkins using the NDLR.

Light Table For Web White Background Photos

Years ago, in my slow quest for better photography of electronic projects, I built a light table to eliminate shadows.  Most of the white background photos you see on the PJRC site are shot with this light table.

This is how it turned out.

The build used boards from OSH Park (then “Laen’s PCB group order”), materials from TAP Plastics, 15 white LEDs and parts I mostly had laying around.

This view is inside a cheap 2 foot sized light tent I purchased from some ebay vendor, and a couple bright lights outside the tent on both side.

The LEDs are Cree CLM3C-WKW-CWBYA453, which are supposedly the same 5500K color temperature as the CFL lights outside the tent. Maybe that matters, maybe not, but it seemed like a good idea.

The Cree LED is a surface mount part, but fortunately Lean’s PCB group order made it very easy to convert to something I can solder wires onto. All the PCBs mount with double sticky mounting tape.

As you can see in this LED photo, there’s a bit of shadow. It’s a soft shadow due to the light tent casting light from many directions, but it’s still very present.  This is the type of shadow I’m hoping just a little bit of under side lighting will eliminate.

This little board is a constant current regulator. It takes a 0 to 5 volt input and regulates a 0 to 20 mA output current to a string of 5 LEDs. I wanted to make sure the current was perfectly constant since the camera might choose a quick shutter time.

Here’s the schematic for that circuit. At the time, it seemed like a good idea to sense the current using a resistor between the NPN transistor’s collector and the LEDs. The idea was any small change in ground potential between the board 0-5V control signal wouldn’t matter, if I ran separate signal and power ground lines.

But I didn’t consider the current draw though those resistors around the upper opamp. As you can see in the schematic, I change the values to about as high as I reasonably could. It still have a tiny bit of the lowest part of the range where the LEDs won’t completely turn off.

The 0 to 5 volt signal just comes from this potentiometer on the front panel.  Because it’s driving only the inputs to opamps, it doesn’t have any substantial load.  I still used a 1K pot anyways, though a higher value would have consumed a little less current.  I guess I didn’t care about an extra 5 mA.

The power for everything comes from this simple little power supply, which is just (approx) 24 volts unregulated, and a 5 volt regulated output from the pot, which is from a 7805 regulator.  Simple.

Of course, the opamp circuit isn’t perfect. After putting this together, I decided to try a different approach, sensing on the emitter side, and no current sensing path to add to the LED current! I also included 4.7K resistors on the feedback looks, and the positive inputs see about a 1K impedance. Any errors from the opamp’s input (PNP) bias currents should be small, and should be more on the negative than positive, so hopefully any tiny error will tend to reduce the LED current, not increase.

Then again, the original boards might work out ok, but Laen’s PCB group order makes it so very easy to just quickly draw up a (small) board.  Because the cost is so low, it’s easy to just send it off without all the worry the goes into a normal board order.

I still haven’t actually put this thing to use… the top plastic cover turned out to be just a bit too small, so I need to go shave it down to size on my table saw (which currently has a bunch of other project stuff piled on top of it). But soon, with a little luck, I’ll be able to take pictures of electronic stuff and adjust the light table to null out or at least soften away most of the little shadows that I still get, even with the light tent.

 

Originally this article was published on the DorkbotPDX website.  Since that time, the DorkbotPDX blog section has vanished.  I’m reposting it here, to preserve this info.  A copy of the original can also be found at the internet archive.

MyComm Portable Solar Powered Messaging Device

John Grant built MyComm,  a very clever solar global messaging device.

MyComm is a portable messaging device that allows users to send messages from anywhere on Earth.  It uses the Iridium satellite system to offer coverage beyond traditional cellular and WiFi networks.  Because it’s solar powered you don’t need to worry about battery life.

Code for the project can be found on BitBucket

Details on how to set up a MyComm Server is documented on this page and the code is available on GitHub.

https://github.com/johngrantuk/myCommServer

Bolder Flight Control System

Brian Taylor and the team at Bolder Flight Systems have developed a low -latency, deterministic, scalable flight control system.

Bolder Flight Systems is an spinoff from the University of Minnesota UAS Research labs.  They found that at the time the they were working on research, they weren’t really happy with the low-cost options out there so they developed their own primarily to better handle latency and determinism.  Their development has evolved from using a MPC-Tiny processor and adding a Teensy 3.2 to using a Teensy 3.6 and BeagleBone Black.

They wanted a system that could scale from simple drones to extremely complex aircraft with a large amounts for sensor and actuator I/O.  Their efforts have lead to a scalable system to a virtually unlimited number of sensor and actuators while maintaining determinism and a constant, well defined latency.

Technical details (as well as purchasing details) can be found over at Bolder Flight Systems. They have also developed a series of Teensy shields, or Backpacks to allow you to easily add different modules to your Teensy. Low level drivers for for all their sensors are available on GitHub.