Pages

Tampilkan postingan dengan label humboldt. Tampilkan semua postingan
Tampilkan postingan dengan label humboldt. Tampilkan semua postingan

Senin, 20 Juni 2016

Humboldt Microcontrollers Group July 24 2014 Meeting Notes

Redwood Curtain Brewing Company
This is a summary of the July 24 meeting of the Humboldt Microcontrollers Group at The Link in Arcata, California, behind the Redwood Curtain. Speaking of the curtain, maybe the Humboldt Microcontrollers Group should schedule an upcoming meeting to be held at Redwood Curtain Brewing Company. Microcontrollers can be used in brewing...

One of the reasons for this blog and for the formation of the Humboldt Microcontrollers Group is the redwood curtain, which is both an actual and perceived barrier between Humboldt County and the rest of the world. In many ways, that curtain is a much appreciated and highly beneficial barrier, preserving natural beauty, creating a slower pace of life, and leading to a better balance between work and non-work activities. But in other ways, that barrier brings economic challenges and limits both the job opportunities for people and growth opportunities for
The curtain between Humboldt and the rest of the world
companies. One way to reduce the redwood curtain barrier for people and companies in this region who work with microcontrollers (MCUs) is to connect, strengthen, and promote the Humboldt microcontroller community. This blog and the Humboldt Microcontrollers Group are both working to connect, strengthen and promote that community.

So, the main topic of the July 24 meeting of the MCU group was the #8 Jeremy Blum Arduino video tutorial (see also my previous post about that tutorial). The focus of the #8 tutorial is SPI (Serial Peripheral Interface), and Jeremy uses an AD5204 digital potentiometer to demonstrate the use of SPI. Ed Smith used a different digital potentiometer than the hard-to-find AD5204 when he did the #8 tutorial exercise, so the sketch Jeremy wrote in the tutorial doesnt work correctly because of the differences in the two potentiometers. Well have to figure out an appropriate alternative potentiometer and accompanying code for other Humboldt people who want to do the #8 tutorial exercise. One more item to add to the list of things-to-do regarding developing a set of effective learning tools for people in this region interested in MCUs.

No one at the meeting had actually worked through the exercise in tonights video. Since none of the people at the meeting tonight had done the exercise, we didnt spend too much time talking about either the technology of a digipot or about interesting or unique aspects of SPI. Maybe at a future meeting? My plan is to talk with Ed, Nick and anyone else interested to agree on a good alternative digital potentiometer and to modify or rewrite the Arduino sketch to work with the digipot we choose.

In addition to the #8 tutorial, the following topics were discussed at the meeting:
  • Somewhat related to the #8 tutorial, Bob asked about using a digital potentiometer (or other components / circuitry) to match color and intensity in a set of three LEDs that are simultaneously given the same input signal but seem to generate different colors. The LEDs are Cree PLCC4 (plastic leaded chip carrier) 3-in-1 SMD LEDs. Based on the little bit we could figure out during tonights meeting about how the LEDs are powered and controlled, Nick suggested the first step should be to put an oscilloscope on the lines going to each 3-in-1 LED to confirm theyre all seeing the same signal. Nick also said its likely the LEDs are adjusted by PWM (pulse width modulation) rather than by varying the power to them, so the digipot would probably not be a possible way to adjust the colors. If all three are seeing the same signal, it would appear unit variability in the LED color output may be the issue. The spec for the LEDs says "Tolerance of measurement of dominant wavelength is ±1 nm" so that spec appears pretty tight. I need to research the issue of bin codes and figure out how to determine if the 3-in-1 LEDs we purchased for this order have green and blue LEDs all from the same bin code. According to the datasheet, the red LEDs only have one bin code (which identifies the wavelength range for that LED), but the blue and green LEDs for this particular component each have seven bin codes. So if some blues were at the bottom of the wavelength range and others were at the top, that might result in a noticeable color difference even with the same applied PWM signal. Of course, keep in mind that my knowledge about PWM signals applied to 3-in-1 LEDs, or other types of RGB LEDs, or even single color LEDs is extremely limited. Researching this will definitely be a learning exercise.
  • HLH frame
  • An update about the Humboldt Laser Harp (HLH) project was given to the group by Nick and Ed. Nick has the frame of the HLH just about completed. In the upper picture on the right you can see the laser harp frame. If you look near the top of the lower picture on the right, a bit of a laser beam is visible -- first sighting of the infamous HLH laser beams. One outcome of tonights meeting is that Gordon will be working with Nick to design and build a base for the harp. Gordon also had an interesting suggestion for laser beam presence enhancement in brightly lighted areas. He suggested shooting the laser through a diffusing or side-emitting light pipe for part of the distance from the laser to the light sensor.
  • From a HLH programming standpoint, Ed has been crafting the code that will convince the Humboldt heavenly harp to generate many marvelous melodies. In version 1.0 of the HLH, the goal is to have a demonstration device that produces simple tunes and has a reasonable degree of casual interactivity with curious members of the general public. Future versions are envisioned that incorporate music-correlated lighting effects and more musical instrument capabilities, e.g. lots of simultaneous notes, note strength and fade effects, simulation of different musical instruments, allowing notes from several octaves, different type of controls for the musicians playing the HLH, etc. As with many other maker
    HLH laser beam
    topics, there are lots of people who have specialized in the field of DIY electronic music, and much of what well be doing in the early days of the Humboldt Electronic Light Orchestra will be research on whats already been done, connecting with people in the DIY electronic music field who are willing to share their knowledge or who are interested in what were doing, and starting to develop new (as far as we can tell) electronic music ideas of our own.
  • The plan is for Nick and Ed to get together this weekend, connect the hardware with the software, flip the switch, and see what happens on the HLH. Stay tuned for updates and videos...
  • We discussed the upcoming August 2 maker fair in Eureka, which has been organized by Origin Design Lab. Nick and Gordon will figure out if Gordon has any maker projects that would be good to have at the Humboldt Makers table. Shawn Dean from InPrinting will be at the table doing 3D printing demonstrations. It would be great if other Humboldt Makers can spend an hour or a couple hours at the maker fair, which sounds like it will primarily be a craft fair aimed at being a selling opportunity for local craftspeople. Even if you cant be at the Humboldt Makers table, if you have an item that will be interesting to the general public, please contact Nick Appelmans or me (my email is arcatabob (at) gmail {dott} com).
  • Justin suggested the Humboldt Makers might consider doing a minor repair on the 3D printer that InPrinting nearly finished building some months ago, then figure out what else needs to be done to get the unit printing. We can discuss that at the next meeting as either an activity to spend a couple Thursday meetings on, or a project that one or several people would work on as time becomes available.
Hope to see lots of people at the next Humboldt Microcontrollers Group meeting, which will be on August 7.

**********
Read More..

Selasa, 07 Juni 2016

LED Lettuce The HydroTower And LED Humboldt Hydroponics

Tonights blog post has two tales of LED grow lights and the planting of a seed for a future collaborative project in the Humboldt Microcontrollers Group.
LED lettuce (from Wired.com)

On July 11, Wired had an article titled, "LED-lit indoor farm produces 10,000 lettuces a day." Because several members of the Humboldt Microcontrollers Group have expressed an interest in using microcontrollers (MCUs) for automated or indoor plant growing, the LED lettuce article caught my interest. The Wired article presents some pretty impressive statistics.
"A newly opened indoor farm in Japan has been built with LEDs that emit light at wavelengths optimal for plant growth...Its 2,300 square metres, making it the worlds largest LED-illuminated indoor farm, and is already producing 10,000 heads of lettuce per day. The LED lamps allow Shimamura to adjust the day-night cycle for the plants, allowing them to photosynthesise during the day and respire at night. Discarded produce is cut from 50 percent of the harvest on a conventional farm to ten percent, and the lettuces grow two and a half time faster...stringent climate control means that water usage is just one percent of the amount needed by outdoor fields."
I can understand that the indoor growing and carefully controlled ambient conditions would reduce the amount of water to grow plants compared to outdoors. But it seems a real stretch to believe that the LED lettuce farm only uses 1% of what would be used for an outdoor lettuce farm!

Calvin students HydroTower workshop area
The second LED grow light project took place in my hometown -- Grand Rapids, Michigan. That project was the HydroTower, the senior design project for a group of Calvin College students. The HydroTower was a fully automated hydroponic garden for home use, using an MCU for control and LED lights to enable photosynthesis and plant growth. This MCU / LED grow project popped up in a Google search after I read the LED lettuce article. Since the HydroTower happened in Grand Rapids, it seemed appropriate to find out a little more. The Calvin College alumni magazine Spark says this about the HydroTower:
"In October, the team researched hydroponics, learning about the floating, misting, and flood-and-drain (ebb-and-flow) methods of growing...their HydroTower would be constructed of a 20-by-32-by-32 inch base unit, to house the electronics and plumbing, and two open growing levels, each measuring 24 by 32 by 32 inches. The unit would operate on an ebb-and-flow system, and it would irrigate the plants and dispense nutrients automatically...In November, Team HydroTower broke the project into components, and each student engineer took one. DeKock would construct the
HydroTower is finished
tower. Kirkman would engineer the water and piping. Vonk would create the LED system, using only red and blue lights because those are the only colors of the spectrum that plants absorb. Meyer would program the microcontroller that controls the LED lighting, the pump and valves, and the touch-screen user interface. And Eelkema would create the pH and electroconductivity sensors that handle nutrient control—a system, the team emphasized, that sets HydroTower apart from other hydroponic farms. “The sensors would input into a microcontroller, which would then use algorithms to decide which nutrients need to be replenished,” Eelkema explained. “The only problem with that is the biology and chemistry research is far more advanced than we have time to cover. Right now I am shooting for a best guess that I know won’t kill the plants
."
The Calvin College students project website gives this final update on the project:
"All through April and the first week of May Team HydroTower worked...to finish the prototype. The month of April saw the addition of our second growing level and some new plants. Other major accomplishments made before Design Night were completion of the pH and EC sensors, a working User Interface on the touchscreen...On May 7th the Engineering department held their annual Senior Design Open House where the team answered questions and took comments about the HydroTower. Later that evening the team gave a presentation detailing some of the work and challenges they faced during the past year...HydroTower is a finalist in the IEEE Presidents Change the World Competition. The project has been selected as one of 15 finalist entries and the top three winners will be announced at the end of May."
Humboldt Laser Harp v.1.0 nearly finished
It seems like the first collaborative project from the Humboldt Microcontrollers Group, the Humboldt Laser Harp v.1.0 (HLH), is well under way. Ed Smith said today that the HLH was being played by his kids in his kitchen. We will no doubt be working on improvements to HLH v.1.0, and at some point will start planning for v.2.0.

But this seems like a good time to plant a seed for another MCU group project. And a project involving some type of hydroponics and LEDs seems like a good target. Ill be reaching out to a few people to see if they want to work on that kind of a project. If youre interested in being involved with an MCU / LED garden project, contact me at arcatabob (at) gmail {dott} com.

**********
Read More..

Senin, 06 Juni 2016

8 Jeremy Blum Video SPI Serial Peripheral Interface Bus

The topic of this Thursdays Humboldt Microcontrollers Group meeting is the #8 Jeremy Blum Arduino video tutorial, which covers SPI, the Serial Peripheral Interface data bus.
Jeremys SPI diagram

Wikipedia says this about SPI:
"...SPI bus is a synchronous serial data link...that operates in full duplex mode. It is used for short distance, single master communication, for example in embedded systems, sensors, and SD cards. Devices communicate in master/slave mode where the master device initiates the data frame. Multiple slave devices are allowed with individual slave select lines. Sometimes SPI is called a four-wire serial bus, contrasting with three-, two-, and one-wire serial buses. SPI is often referred to as SSI (Synchronous Serial Interface)."
During the #8 video exercise, you will build a program using SPI, doing things like including the SPI library, setting the slave select pins, and sending information on the SPI bus with the SPI.transfer command. Going through this exercise doesnt make you an SPI expert, but it does help you learn a few basic aspects of SPI. For a more thorough background on this topic, take the time to go through the SparkFun tutorial on SPI.

AD5204BN10 digital potentiometer
In addition to SPI, the #8 video also introduces digital potentiometers. The digipot used in the #8 video is an AD5204BN10, which appears to be discontinued, obsolete or just very rare, so most people doing the exercise in this video will have to use an alternative digital potentiometer. I spent ten or fifteen minutes on Digi-Key trying to find an alternative component that was equivalent to the AD5204BN10 but finally decided Ill just wait to discuss that at the meeting on Thursday.

In the meantime, I did a bit of research on digital potentiometers so Id understand a little more about how they work and when to use them. Analog Devices has a tutorial on digipots, and since they made the one that Jeremy uses in the video, I decided the AD tutorial was a good place to start. Nine pages later I decided I was wrong. The AD tutorial was written for an electrical engineer, not a novice electronics person. Electronic Design (ED) had a much better newbie introduction to digipots. ED said:
Breadboard setup for #8 video exercise
"Digital potentiometers are integrated circuits that implement a resistive ladder and a digital means of addressing a particular tap on the ladder that corresponds to the wiper position of a mechanical potentiometer. They’re used to calibrate system tolerances or dynamically control system parameters. Some of them have no on-chip memory. Others incorporate nonvolatile memory for saving the wiper position...What advantages do digital potentiometers have over mechanical pots? Obviously, digital pots can be operated in a closed control loop, and they don’t require physical access for adjustment. In addition, they offer higher resolution than mechanical pots, along with better reliability and stability, faster adjustment, better dynamic control, and a smaller footprint."
Jeremys use for the digital potentiometer in the #8 video exercise is to vary the input voltage to LEDs to change their brightness. I dont know if thats a typical application for a digital potentiometer, but its a good way to learn about this component.

If youre interested in microcontrollers, please come to the Humboldt Microcontrollers Group meeting this Thursday, July 24, from 6 to 8 PM at 1385 8th Street, Arcata, California, USA. Bring your questions and your enthusiasm -- we look forward to seeing you there!

**********
Read More..

Minggu, 22 Mei 2016

9 Jeremy Blum Arduino Wireless Tutorial MCU Group Mtg August 7

Tonights post is a bit of a preview of Jeremys #9 Arduino video tutorial about wireless, along with a couple related comments and alternatives regarding microcontroller (MCU) wireless tutorials for future use by the Humboldt Microcontrollers Group.

But before I get into the Arduino wireless tutorial, there are two special deal items for people who buy MCU-related electronic components. I found out about these from SparkFun and Jameco emails.
  1. SparkFun Retrosparktive:  "SparkFun will be vacating its offices at 6175 Longbow and moving on up to Dry Creek Parkway...As part of the Retrosparktive, each week we are offering up a selection of classic products at “historically low prices” (sorry, couldn’t help myself). We’re calling this first selection the “Bare Necessities” - great things to have around your workspace or office. This selection of items is only on sale from 8/4/2014 at 12:01 a.m. MT until 8/10/14 at 11:59 p.m. MT - so get ‘em while you can! BUT WAIT, THERE’S MORE! We’re also offering a promo code good for $10 off any orders over $40. Just put the code “RETROSPARK” into the box at checkout to get your discount. This code is good until August 31, 2014."
  2. Jameco Free Friday Electronic Components Giveaway:  "Jamecos team of component buyers hunts for special buys and every Friday we will highlight one of these great buys by making a limited supply of one product available for free at www.Jameco.com/Free. Well
    post new inventory every Friday at 10 a.m. Pacific Time and it will be available on a first come, first serve basis
    ."
The next Humboldt Microcontrollers Group meeting is this Thursday, August 7. The main topic of the meeting will be to discuss Jeremy Blums #9 video tutorial, so tonights post takes a look at that tutorial. The topic is wireless communications with Arduino, and the #9 video exercise uses XBee radios. Wikipedias entry on this type of wireless communication equipment says:
"XBee is the brand name from Digi International for a family of form factor compatible radio modules. The first XBee radios were introduced under the MaxStream brand in 2005 and were based on the 802.15.4-2003 standard..."
The XBee brand has a wide range of models, with 2.4 GHz and 900Hz options, and the XBee-PRO 900HP is listed as having a 28 mile range. Having an Arduino communicate wirelessly 20+ miles away without cellular or Internet service seems like it could be handy for some things.

XBee is a brand name, and generally speaking, follows the ZigBee protocol for wireless personal area networks (WPAN). However, not all XBee technology is compatible with everything in the Zigbee world. For different views of what XBee is and how compatible it is, see the Digi International page about this, the SparkFun XBee Buying Guide or the StackExchange thread on the topic, which says:
"ZigBee / ZigBee Pro are mesh communication protocols that sits on top of IEEE 802.15.4 PHY. XBee / XBee Pro are product names for radio communications modules made by Digi. The modules can be loaded with various firmwares to support ZigBee / ZigBee Pro / DigiMesh and come in several frequency bands. DigiMesh is an alternative to ZigBee that changes a few things, and adds some features to make it generally better to work with. But, you sacrifice compatibility with ZigBee devices. For example DigiMesh allows routers to sleep, has lower overhead, has 1 node type vs zigbees 3 leading to a more robust mesh, can run at higher data rates, etc."
Boards for the #9 video tutorial
The moral of the story for MCU beginners like me is, if you want to do wireless communications with MCUs, use all the same brand and model of wireless radios. No need to try and figure out if your circuit doesnt work because the two or more radios arent compatible -- youll have enough fun just figuring out if the circuit is hooked up incorrectly or if your code has errors or poor design.

The exercise in Jeremys #9 video uses these boards -- two Arduino Unos, two XBee transceiver modules, two XBee shields, and a SparkFun USB to XBee adapter. In addition, youll need a stepper motor, a mini-B USB cable and a few other parts you probably have from other Arduino projects or tutorial exercises. Jeremy shows how to program the Xbee units ID numbers and how to hook up the Arduinos and other components. Then he walks the video viewer through the steps to write the program which allow the potentiometer connected to one Arduino to wirelessly control the position of the stepper motor which is connected to the other Arduino.
#9 exercise wired to breadboard

Excluding the two Arduinos and the miscellaneous parts you probably have, you can spend over $100 just on parts for the exercise in the #9 video. Ed Smith didnt have all the parts lying around to do this exercise and figured out an alternative exercise with a couple radios and other parts he did have around. He said hell explain on August 7th what he put together for an MCU wireless exercise.

The Humboldt Microcontrollers Group should consider discussing cost-effective options for a useful training session on MCU wireless technology.There are lots of options, but a couple starter ideas are:
  1. Have people work in groups of two or three to do essentially the same exercise Jeremy demonstrates. The people can buy different parts that they want to keep after the exercise, or one person can buy all the parts and keep them when the training is finished.
  2. Do essentially the same exercise as the #9 video, but identify less expensive components than the Arduino and XBee parts specd by Jeremy.
  3. Use one wireless radio instead of two and find or write a tutorial involving one radio.
Others in the MCU group will know or think of additional options for MCU wireless training sessions. A couple specific training sessions I found in a quick search were:
CC3000
  1. Wireless Gardening with Arduino + CC3000 WiFi Modules by Adafruit. I like this one because of the Humboldt MCU Garden project. The garden project would make the investment seem more useful than it would for a generic training exercise. Heres the CC3000 module from Adafruit, and heres a post about the CC3000 by ladyada.
  2. SparkFun has two MCU wireless tutorials; Arduino Wireless Communication via the Electric Imp and Wireless Arduino Programming with Electric Imp.
  3. Arduino Wireless SD Shield Tutorial from Instructables is one of the many Arduino Wi-Fi tutorials.
CC3200 LaunchPad
We could also find or develop a training session around one of the newer MCUs with built-in WiFi, such as the SimpleLink products from Texas Instruments (e.g. the CC3200 LaunchPad) or one of the other MCU manufacturers MCU with integrated Wi-Fi. Identifying some of those other integrated wireless / Wi-Fi components will likely be the subject of future research and blog posts.

In addition to discussing MCU wireless on Thursday, the MCU group will likely talk about upgrades to the Humboldt Laser Harp (HLH). After its debut performance in Eureka on August 2, weve got several improvements in mind. Im hopeful the HLH will make an appearance at the MCU group meeting on Thursday so everyone at the meeting can play with it and get excited about improving it, about making additional laser harps, and about designing and building other electronic music-light instruments which will help create the Humboldt Electronic Light Orchestra.

If you havent watched the #9 video, check it out. If you dont have time to watch it between now and Thursday but are interested in MCU wireless, come to the MCU group meeting anyway. Were looking forward to seeing you from 6 to 8 PM on Thursday, August 7, at 1385 8th Street, Arcata, CA.

**********
Read More..

Jumat, 20 Mei 2016

Energia Using The EEPROM on TI Stellaris and Tiva C Launchpads

[Tonights post is by Ed Smith, participant in the Humboldt Microcontrollers Group]

Im writing this blog post largely because it took me quite a while to figure out how to use the Tiva-Cs EEPROM in an effective way. My hope is that this page will make life easier for future people who use the Tiva-C.

First up, these are the Microcontroller boards were going to be talking about today.




















The Stellaris LM4F120 / Tiva-C TM4C123 Launchpad and the very snazzy TM4C129 Connected IoT Launchpad.

There are plenty of other Launchpads worth talking about, but all of them fall into one or more of two categories: Launchpads I do not have, and: Launchpads containing no EEPROM.
Not having EEPROM makes this article about using the built in EEPROM a bit irrelevant, and if I havent used it I dont like writing about it.

Many programs and projects dont need to use EEPROM. All the variables are either burnt into the flash and never change, or are kept in RAM and updated as needed for that boot. When power is cycled the program starts fresh and off it goes. You dont need your calculator to remember what you did last week for instance.
There are other times when having some storage is extremely useful, calibrating sensors is a wonderful example. The Humboldt Laser Harp for instance uses EEPROM to store the calibration data for the laser sensors, as well as to store the MIDI "Velocity" of the notes. Without EEPROM you would have to either redo the mechanical/physical calibration every time you turned the harp on in slightly different circumstances (which takes 10-15 minutes), or recompile and reupload the firmware every time.
Almost any sort of sensor that requires calibration once in a while is a good use for EEPROM. Things like odometers or hour meters as well.
That brings us to the question of how.

How do I get access to the EEPROM of my microcontroller?
Im glad you asked!
If youre using an Arduino, or a TI Launchpad and the Energia IDE, the process is very simple.
First you include the EEPROM library (At the top of your program, add "#include <EEPROM.h>" without the quotes), then in your program you call EEPROM.read(address) and EEPROM.write(address, value) to read and store values respectively. For example:

This would read the value at address 10 into the someVariable variable, update it, and then stuff it back into EEPROM address 10.
The process is very simple, if your value fits into a single byte. That is to say, 0-255. If your value is 256 it will be stored as 0. If its 260 it will be stored as 4, and so on.
You have to do some bitshifting to split larger variables up into bytes and store the bytes individually, then bitshift it back together when you want to use it. Its very doable, but something of a pain.
There are add-on Arduino libraries that can be used to automate the bitshifting, though I have not used them.
What I have used is a slightly lower level method of EEPROM access on the TI Stellaris and Tiva-C chips.
This method and example still uses the Energia IDE, though I believe the code is more or less the same for TivaWare and the TI Code Composer Studio.

Instead of EEPROM.whatever, you use "ROM_EEPROMRead(variable, start address, length)" and "ROM_EEPROMProgram(variable, start address, length)".

The trick is, the variables you use are long integers (32 bits, 4 bytes) in an array, rather than single bytes.
The same operation as above, but with the ability to count from zero to a bit over four billion. Quite the improvement over 0-255.

You can also use sizeof(someVariable) rather than listing the number of bytes (so ROM_EEPROMRead(someVariable,10,sizeof(someVariable)); instead of 4) this is useful if youre using an array with more than one variable in it.
What I really like about this method is you can stick an entire array in just as easily, rather than the single member array we declared above you can declare an arbitrarily long array. Say 30 members. Then the exact same ROM_EEPROM calls store that entire array.
It does start to get tricky if youre using a number of addresses, the above example code uses address 10 as its starting point, it also uses address 11, 12 and 13, as the address is done by the number of bytes used. That 30 memory long array would use 120 bytes / address slots.
If you arent paying attention and write something else to the middle of that range youre going to be unhappy with the results!
You get 32kB worth on the basic Tiva-C, and 256kB on the Connected Tiva-C, so you can afford to be lavish.
The really entertaining part to me is that if you use the Arduino style EEPROM calls on the TI chips, the EEPROM library is converting them into the unsigned long flavor of call to interface with the TI MCU itself. That means that if youre storing an unsigned long using the Arduino method on TI chips, youre bitshifting it manually into bytes, then the library is bitshifting it back into unsigned longs and storing it. Bit of a crackup if you ask me.

When you do use EEPROM it is a good idea to think about how often it will be written to, if you write to it once per second you only get 27 hours of operation before you hit the rated lifespan. Real world testing of Arduino (Atmega328 MCU) EEPROM has shown it to typically get to well over 1,000,000 writes before it starts throwing errors. Atmel and TI are not willing to guarantee that youll get a million writes though.
Reads are free, read the EEPROM as often as you want, but try to keep the writes within reason. If you write once per minute youll get ~69 days of operation per the spec, or 694 days if your EEPROM does the >1 million writes many seem to. Once an hour on average gives you a very long lifespan indeed, a bit over 4,000 days per spec or 40,000 if youre lucky. Thats 11 to 110 years, which should be enough.

If you made it this far through this wall of text, congratulations! My next post will have more pictures.
I hope this was an interesting read and/or helped, look for a blog post about the Humboldt Laser Harp coming in the near future. This coming blog post will include some (most? all?) of the code for the laser harp, including the EEPROM bits.

--Ed Smith

**********
Read More..

Kamis, 12 Mei 2016

Like Arduino Like Python Check Out Micro Python

My knowledge about electronics and microcontrollers (MCUs) leaves a lot to be desired. My knowledge about computer programming, and Python in particular, leaves even more to be desired. However, if you like MCUs and Python, you might want to take a look at Micro Python, as Im doing tonight.
Micro Python pinout (from Kickstarter)

A Design News article from July 17 that I saw gives a brief overview of Micro Python. One of points of interest for me on this board is that the MCU is from STMicroelectronics. The only other blog post Ive written about an STM board is the June 22 one about the $50 Lab-in-a-box. That board also had an STM32F4 MCU.
"The Micro Python board is based on the STM32F405 Microcontroller. It comes ready for Python programming...running 168MHz, with 1MiB Flash and 192KiB...The Micro Python board has a built-in interface for USB and functions much like a storage device. Programmers can write their Python scripts directly onto the battery-operated board and once stored, the Micro Python board will function entirely independent of a PC...the micro Python board comes pre-loaded with a micro SD slot, four LEDs, a clock that functions in real time, accelerometer, switch, and 30 I/O pins, including USARTS, SPIs, 12C buses, DAC and AC pins, and four powered servo ports...it functions right out of the box, as its pre-installed with Micro Python...What’s really unique about this board isn’t the board itself, but the program upon which it’s based...Python can write functions, execute string processes, write classes, create lists and dictionaries, read and write files, create a generation
Packing Micro Python for shipment (from Kickstarter)
system, execute closures, design list comprehensions, and deal with execution handling. The Micro Python software is a leaner, cleaner version of Python intended for the microcontroller, but it actually works for PCs, too...Micro Python software is already available to the public through the MIT open-source license
..."
The development of Micro Python board was completed with funding from a Kickstarter campaign that was successfully funded on December 13, 2013. The campaign generated more than six times the initial funding goal of £15,000 set by its founder, Damien George, an Australian theoretical physicist at the University of Cambridge. In Damiens latest update on the Kickstarter site (June 21), he says they just finished sending out the last of the kits and boards to his Kickstarter supporters. The picture above looks like he had a pretty crowded apartment or house when they were packing everything up for shipment! An interesting Kickstarter side-note is that another campaign on there, SliceCase, leveraged the popularity of Micro Python by offering a case for that board as one of the SliceCase rewards. The SliceCase campaign only asked for £1000 and got 9X the original ask.
Micro Python SliceCase

The SliceCase / Micro Python synergy brings up a revenue opportunity that takes advantage short term trends. In my recent post about Spark.io, two principles I mentioned for the Humboldt tech, innovator, maker and entrepreneur (TIME) community to leverage are (1) focus on emerging technologies and trends (e.g. Python language and the maker movement) and (2) use Kickstarter and similar sites to launch products and gain visibility. In this instance, SliceCase no doubt benefited from the buzz that Micro Python had generated. It would be fun to launch a Humboldt Crowdfunding Entrepreneurs Meetup group, where half the purpose is to take an abundance economy approach (a rising tide floats all boats rather than I want my piece of the pie) to Kickstarter and Indiegogo and people in the Meetup group would help each other become more successful at crowdfunding campaigns. The other half of the groups purpose would be to monitor crowdfunding projects on Kickstarter, Indiegogo and elsewhere, and to quickly and efficiently build crowdfunding campaigns that leverage publicity and successful funding of other crowdfunding campaigns.

The Micro Python is open source. Heres the GitHub project site to check out if thats of interest to you. I was glad I took a look at the GitHub site because it showed me that at least one GitHub site has a wiki component. I know less about GitHub than I do about microcontrollers and Python (sensing a theme here??), but I have several reasons to learn how to use GitHub effectively. One of those reasons is because the Humboldt Laser Harp (HLH) project code repository is being put on GitHub. I like wikis for aggregating and organizing technical information, and Im looking forward to giving the wiki component of GitHub sites a look to see if has benefits for the HLH project.

In addition to finding out about wikis on GitHub, tonights blog post also made me aware of a tech acronym that I either havent seen before (which is hard to believe) or just dont remember. That acronym is MiB. And it doesnt mean "Men in Black." What it does stand for is mebibyte, where mebi is a binary prefix which means 2 to the 20th power. It is apparently used as a more accurate alternative to megabyte (MB). The Wikipedia entry for mebibyte says:
She turned me into a newt!
"1 mebibyte is 1048576bytes...The unit has been accepted for use by all major standards organizations, appears increasingly in scholarly literature and is part of the International System of Quantities. Many Linux distributions use the unit, but the unit has not been widely accepted in the computer industry or popular media."
Micro Python has enough visibility that it was written up in Wired in December 2013, and in June 2014 there was a blurb about it in InfoWorld. With Python currently being "the most popular language for teaching introductory computer science courses at top-ranked U.S. departments," and with a relatively active community on GitHub with 31 contributors, 2544 commits and 1082 stars, the Micro Python project stands a decent chance of building critical mass and being around for a few years. Lastly, if youre interested in learning more about the creator of Micro Python, theres a Hack A Day interview with him from November 2013.

If you want to play with a Micro Python board, you can sign up on the projects website, although I didnt see any estimated shipping date for people who werent Kickstarter supporters.

**********
Read More..

Rabu, 11 Mei 2016

Grilled Cheese Smart Box Microcontroller And A Whole Lot More

The Smart Box uses a microcontroller (mcu), and a whole lot more, to keep fresh grilled cheese sandwiches hot, moist and crisp.
Fresh, tasty, warm grilled cheese sandwich

The Smart Box is an innovation that dramatically demonstrates two sometimes overlooked non-electronics aspects of MCU-focused projects that can require as much work as the electronics, if not more work. Those two non-electronics issues are:

  1. Figuring out what you need the MCU to control.
  2. Figuring out all the non-electronic hardware issues for the project.
The goal of the Smart Box designers was to create an environment that could extend the highly edible lifetime of a fresh grilled cheese from seven minutes to at least thirty minutes. As Fast Magazine tells the story, the design team tried to find,
"...a way to extend the sandwichs woefully short shelf life. They discovered that each Melt had about seven minutes before going cold, leaving the cheese to congeal and making for a subpar grilled cheese-eating experience...the team looked far and wide for a food transport box that could maintain just the right temperature while striking the right balance between moisture and crispiness for 30 to 60 minutes at a time...what we realized is that if you maintained the temperature, and you had even airflow, and a way to get some of the moisture out of the product as it sat in the box, that it can hold a Melt for over 20 minutes and still meet temperature, moisture, and crispness guidelines."
Sandwich container with ridges and holes for hot air circulation
The first part of the MCU project had nothing to do with an MCU. Most products and design projects involving an MCU will start by figuring out how the product or project ought to work to achieve the projects goal. For the Smart Box, the goal was a good tasting sandwich. So the first part of that project was to determine what ambient conditions would keep the sandwich from getting cold and soggy. It was obvious the grilled cheese sandwich storage and transport unit would need heat. They would have to keep the temperature low enough so it didnt cook the sandwich more, but high enough so the cheese would be nice and soft. And the temperature would need to be uniform throughout the sandwich storage and transport unit. After experimenting with different conditions, and probably eating quite a few grilled cheese sandwiches, they found the right temperature (190 - 200 degrees F) and the right moisture to keep the sandwich tasting good.

The next step was to develop a combination of materials, shapes, heaters, fans, etc, that would maintain the necessary temperature and moisture for the sandwiches. Air flow was key, both throughout the large insulated food transport box and throughout the smaller sandwich containers that sit on the shelves inside the food transport box. The majority of this physical design and development work didnt focus much on electronics of the project, other than to keep the fan pushing air and to keep the heater warming up the air. The Fast Company article explained:
"...for any of this to work, the air had to circulate around the sandwich so that the heat surrounding it was constant, like a convection oven with size restraints...Heres how it works: It uses a hot plate made out of aluminum to keep everything warm. But since direct heat can burn its contents, its covered with a shield while an internal fan ensures proper air circulation. The whole system is sensitive, so inside are sensors that monitor the environment for precise heat and humidity levels. A microcontroller is used to make small adjustments automatically, ensuring that the grilled cheese arrives at your door or desk nice and toasty."
Once the physical design of the box was mostly figured out, the electronics wizards started working their magic. They figured out what temperature sensors to use and where to put them. The fan power and controls were designed and the rest of the MCU functions were programmed.

Im sure figuring out the sensors, controls, MCU and programming took much longer than the length of the above paragraph indicates. But for the grilled cheese Smart Box, theres little doubt in my mind that the design-build issues requiring non-electronics maker skills or physical design knowledge took more time and brainpower than the MCU-related part of the project. The Smart Box illustrates why the Humboldt makers who really enjoy MCUs also need lots of other types of knowledge or need to collaborate with others who have the non-electronics skills.

**********
Read More..

Jumat, 29 April 2016

Mutli Phase Humboldt MCU Garden Project

As yesterdays Humboldt Laser Harp post indicated, the microcontroller (MCU) music group project is well under way. So now Im thinking about how to get the second group project started in the Humboldt Microcontrollers Group, one involving gardening.
MCU and sensors for potted plant

Several people whove been at Humboldt Makers Group meetings or the MCU group meetings have said theyre interested in MCUs and gardening. And it seems like lots of other people in Humboldt County might have an interest in ways to improve gardening. There are lots of organic gardeners in the area, and agriculture has been part of the Humboldt economy for much of the areas history. So Ive decided to outline a multi-phase approach to a collaborative project focused on MCU gardening. And a significant part of this collaborative project will be identifying and reaching out to Humboldt people who are involved in gardening or agriculture and might be interested in sharing their knowledge and / or participating in this project.
MCU and hydroponics

Two long term goals I have for the MCU gardening is to be involved with a successful hydroponics system and a successful aquaponics system. There are lots of websites and projects on the Internet that tell a person how to do hydroponics or aquaponics, but Im an engineer, and I like to understand what Im doing. Plus I dont have a lot of money to spend on these projects. So my preferred approach to MCU gardening is to start out small, and get more complex after I understand the technology and green thumb art involved with each part of the MCU garden project.

Below are proposed MCU garden project phases. If we get the right people involved with the project and if we can secure funding of some type for the project, we can move very quickly through the phases or work on more than one phase at a time. So if you know people whod like to participate in this project or know of money that can be used for purchasing electronic components and supplies for this, please contact me at arcatabob (at) gmail {dott} com. These are the proposed phases for the Humboldt MCU Garden group project:
MCU and aquaponics (from dzbc.org.cn)
  1. Grow one plant indoor in soil.
  2. Grow four to eight plants indoor in soil.
  3. Grow four types of plants outdoor in soil.
  4. Grow one tray of plants indoors in hydroponic system.
  5. Grow three types of plants indoors in hydroponic system.
  6. Grow one type of plant in aquaponics system.
  7. Grow three types of plants in aquaponics system.
Phase 1 of the Humboldt MCU Garden project is simple and low cost and will help us learn the basic principles of MCU gardening. Phases 2 through 7 can easily be redefined as we get more people involved in the project and we learn more about what we dont know about MCU gardening.

The first draft design of the Humboldt MCU Garden project includes:
  1. One type of plant.
    LEDs and lettuce
    1. Lettuce is my first choice, partly because of whats being done with optimized lettuce mcu gardening in Japan and other places (see my blog post "LED Lettuce, The HydroTower And LED Humboldt Hydroponics.") We might be able to find useful data about optimum growing conditions for lettuce (light wavelengths, relative humidity, nutrients, temperature, etc.).
    2. If other people who want to participate in the Humboldt MCU Garden project prefer to grow something other than lettuce and have information about good growing conditions for that plant, Im willing to switch from lettuce.
  2. Growing container.
    1. The type of growing container probably wont be too critical for Phase 1. Mainly something large enough to hold the soil and drainage system that will provide good growing conditions for the plant.
    2. A five gallon plastic bucket is one option, especially if we can find a free one.
    3. We need to figure out where the container with the plant and MCU Garden system will be kept. It seems like Phase 1 should mostly be indoors because that means we dont need to have a rain-proof system. But having a Phase 1 container thats easily movable would be nice so we can roll or carry the container outside on nice days.
  3. Growing condition sensors
    1. Light sensor -- very important so we get good photosynthesis (and good respiration?).
      One type of light sensor (from Adafruit)
    2. Soil moisture sensor -- very important because too dry means dead plant and too wet means dead plant.
    3. Temperature sensor -- important for growth, especially during Humboldt winters. Temperature will be less critical for plants like lettuce, but very critical for plants like tomatoes.
    4. Relative humidity sensor (RH) -- RH wont be critical for lettuce growth in Phase 1, but it will be critical as the projects future phases try to minimize water usage and as we try to grow RH-sensitive plants like redwood trees.
  4. LEDs for indoor gardening
    1. RGB LEDs will let us adjust the light if we want
    2. Red and Blue LEDs appear to be used for optimum lettuce growth.
    3. Research and / or people who know plant growth lighting and LEDs are required.
  5. MCU to gather and record sensor data
    1. Which MCU we use for the Humboldt MCU Garden project depends partly on who wants to be involved with the project.
      1. If we can get a sponsor for the Humboldt MCU Garden project, such as an MCU manufacturer or distributor, Ill use whichever MCU they manufacture or distribute!
      2. If no MCU manufacturer or distributor sponsor can be recruited, the MCU will be determined by whoever takes the lead on programming for the project.
        1. If Ed takes the lead, well probably use a Texas Instruments MCU.
        2. If Josiah takes the lead, or if Im filling that role, it will likely be an Arduino or Arduino-compatible.
        3. If someone other than Josiah, Ed or me volunteers to lead the garden-variety programming for this project, that person can choose the MCU type.
  6. Type of soil
    1. Determining what type of soil to use will require research or a project member who has good experience with growing plants indoors in containers.
    2. The type of soil will likely affect other gardening aspects such as what nutrients we need to add and the soil moisture measurement.
  7. Fertilizer and trace nutrients to add
    1. Fertilizer and trace nutrients is another topic that will require research or a project member experienced in the art.
    2. Might want to evaluate whether pH or some other batch or continuous sensor (pH? nutrient analysis?) should be used to track nutrient levels.
  8. Data gathering and analysis
    1. There are no specific requirements for data gathering and analysis for Phase 1 since its such a simple system. However, part of the purpose of Phase 1 is to learn how to effectively monitor growing conditions, so it makes sense to establish good gardening data practices (GGDP) for those growing conditions and different types of sensors.
    2. As part of my goal to get Humboldt people more involved in the Internet of Things (IoT), it would be good to use services like open data bases and IFTTT (If This Then That).
    3. One gardening data goal is to use that data to automatically track, alarm and interpret the data generated by the sensors. It would be nice to generate online graphs and have alarms sent out by IFTTT when growing conditions reach or approach setpoints where action needs to be taken.
The above outline give you an idea of what I think Phase 1 of the Humboldt MCU Garden group project should look like. Next steps for me to get this project rolling are (1) talk to and try to recruit a couple people whove expressed an interest in MCU gardening, (2) promote the project to other people in the Humboldt Makers and MCU group and try to recruit some of them, (3) develop a one-page MCU project proposal that I can use to pitch to potential sponsors, and (4) continue to do research for Phase 1 topics like sensors, nutrients and soil types.

If you are interested in this project or know someone who might be, please email me at arcatabob (at) gmail {dott} com or come to an MCU group meeting or Humboldt Makers meeting in the near future.

**********
Read More..

Kamis, 28 April 2016

Adafruits 3D Printed Wearable Video Goggles

Im not a gamer, but I still think it would be fun to make and test drive Adafruits recent microcontroller (it uses an Arduino Micro) project titled "3D Printed Wearable Video Goggles."

There are three reasons I think this would be a good project to work on.
  1. The 3D printed goggle housing sounds like a challenge and a great learning exercise because theyre printed with both PLA (polylactic acid) and Ninjaflex (a thermoplastic elastomer) and the two materials are fused together.
  2. There are a couple people in the Humboldt area I know of but havent met who do 3D printing. Working on a project like this might be a good opportunity to meet them.
  3. It seems like having a wearable personal monitor might be a fun change from the normal way to view a computer screen, and for certain applications, such as video, it might be more engaging and absorbing than a standard computer monitor or screen.
Ninjaflex is a relatively new 3D printing feedstock. A May 2014 post on 3D Printing Industry profiled the Fenner Drives material, which seems like a typical maker story.
"Until recently, prototyping flexible components was a time-consuming and cumbersome process,” said Fenner Drive product development engineer Stephen Heston “It was a big gap in the market, because so many engineered products utilize elastomeric parts.  Without materials that closely approximate the properties of the end product, it is impossible to create truly functional prototypes.” After discovering that 3D printing enthusiasts were trying to use existing Fenner Drives belting material as filament, Heston found that while it was not an ideal material in its current form, with a few months of tweaking it soon could become one. The final product has a textured surface that allows it to be used in most 3D printers with a spring loaded extruder...Most impressively however is the replica of a small childs
3D printed Ninjaflex flexible model of childs heart (Channel 11)
defective heart that surgeons in Kentucky recently 3D printed using his CT scans. By printing a model one and a half times the actual size from a highly flexible material, the doctors were able to pre-visualize the best way to repair the defect without having to perform the risky surgery blind. The fact that the model only cost about $600 and most likely saved a small child’s life is actually pretty incredible. It also would not have been useful to the doctors if it had been printed from a less flexible material. You can watch the local news story here.
"
This YouTube video about Ninjaflex gives a pretty good idea of what the material is like. Of course, like all new materials, Ninjaflex is not without its particular challenges. On the LulzBot webpage for Ninjaflex, they say:
"The flexibility of this material makes it nearly impossible to print using a standard extruder, so weve designed the Flexystruder, a Gregs Wade-style extruder that fully constrains flexible filaments like Ninjaflex, which is available for purchase here!"
Both PLA and ABS (acrylonitrile butadiene styrene) can be tricky to 3D print with, so I imagine theres a definite learning curve for the Ninjaflex, especially if you are using a standard 3D printer extruder and LulzBot is correct about the difficulty of printing it with a standard extruder. Before trying to print the Adafruit goggles, it would pay to make a few test prints with the Ninjaflex by
Screenshot showing 3D printed parts of goggle (Adafruit)
itself, then a few test prints laying Ninjaflex down on top of a PLA base.

Adafruit did a Layer By Layer post about the goggles, in which they give lots of graphics showing different sections of the 3D build and throw in a few project tips, like:
"Adjust the overall size of the goggle frame by editing the curves that make it up. Measure your forehead, cheeks and nose to adjust the cylinders that make the cuts into the hood...Adjust the goggle hood shape by editing each cylinder. The bigger one controls the forehead shape. Measure the depth and width of your head to get a general size for the hood."
The only 3D printers I know in Humboldt are Justin Tuttle and Shawn Dean of InPrinting. Ive been told there are 3D printers at Humboldt State University and at College of the Redwoods, but I havent met them yet. One or both of them may have already printed with Ninjaflex -- Ill have to contact them to find out if they have, and if not, maybe theyll be interested in getting some and trying it out.

The third reason I think the Adafruit goggles would be a fun project is because Ive never worn a head-mounted personal monitor. Im not so much interested in the gaming aspect, although I would like to check out some older computer games on various ancient emulators such as an Apple II or Apple IIgs. But the main reason Id like to try the goggles is to see how engaging the head-mounted and enclosed display would be when watching videos or movies. It seems like it would be either really enjoyable or very restricting. Who knows -- maybe Ill get the chance to find out!

**********
Read More..

Senin, 25 April 2016

Humboldt Makers Group At Eureka Craft Fair

The Humboldt Makers Group had a tech demo and information table today at the Humboldt Makers Street Fair, an arts and craft fair in Eureka, California.

The arts and craft street fair was organized by Origin Design Lab from Eureka, and it was the 4th annual fair for them. Several blocks of 2nd Street in the Old Town section of Eureka hosted arts and crafts booths and a variety of local musicians. The Humboldt Makers Group had a table there to raise the visibility of the group in the local community and to encourage participation in the Humboldt Makers monthly meetings from 6 to 8 PM at 1385 8th Street in Arcata. We also had the brand new Humboldt Laser Harp (HLH) on the table to amaze and entertain passersby.

Although most of the public walking around to the different booths and tables appeared to be tourists or shoppers looking at the arts and crafts for sale, rather than makers, it was worthwhile for us to have a table at the event. We did talk with a few people who seemed interested enough in the maker group to come to future monthly meetings. These interested people ranged from young students who wanted to learn about electronics but didnt have much money or drivers license to people who took a smartphone picture of the Humboldt Makers Group sign and said they wanted to come to meetings to people who seemed interested in the makers but didnt appear committed to getting involved with the group.

Having these people stop by the table to talk with us simply reinforced what Ive found to be true in many places. Every maker event and tech unconference Ive participated in over the past ten years has involved talking with people at the event who say they just heard about the event (which was of high interest to them) the day before, or they ask how long weve been around and why its so hard to find out about us, or they tell me they were sure there were no other people like them (a maker or a tech enthusiast) in the area because they sure didnt know of any. Im firmly convinced that a combination of three things can greatly strengthen and expand the community of makers or tech enthusiasts in an area.
  1. Establishing regular in-person events for either the maker community or the tech enthusiast community.
  2. Organizing and facilitating event activities which are of interest to the people who show up and participate in the event.
  3. Extensively promoting, communicating and marketing the events and the groups behind the events so that as many potentially-interested people as possible find out about them. A big part of this involves personal invitations to people to participate in an event.
Maker Faire -- Bay Area, CA
No one I talked to at todays event knew what the maker movement is and only a couple had heard of the Maker Faire in the Bay area. This was partly because people at todays event were there for an arts and craft street fair. But the lack of awareness also shows a need for more promotion and education about makers and Maker Faire. A dedicated core group of people can greatly raise the visibility in Humboldt County of the maker movement, but we one or two new people in the group who are good at marketing and promotion, and we need sponsors that enable us to effectively promote the Humboldt Makers Group.

First public display of Humboldt Laser Harp
The HLH demo went fairly well, especially considering that physical construction of the harp was started last week, and it first became playable yesterday. Having an outdoor, midday venue to demo it also presented challenges, especially in terms of the changing sunlight affecting the light sensors and their correct calibration. Concerns about burning out the dollar store lasers used in the HLH caused us to periodically power down the lasers to try and make them last longer. Powering down the lasers creates an interesting phenomenon. Within ~ two minutes of powering down the lasers, someone would come to our table and ask "Whats the Humboldt Laser Harp?" Which, of course, meant we had to power them back up! It was worth it though, because it was fun to watch them play the harp and be amazed at how it works. A robust and versatile harp will be an excellent promotional tool for the Humboldt Makers Group and should be displayed to the general public as much as possible. 

Ed Smith and I thought of quite a few improvements wed like to make on the Grip-Strut version of the HLH. Ed is much more familiar with both the hardware and software of the HLH than am I, so Ill let him explain to Nick and others what will be most effective at improving the HLH. However, below is my understanding of HLH stuff we should figure out and work on.
  1. Reduce ambient light reaching the light sensors.
  2. Improve alignment of lasers.
  3. Modify software so the twelve lasers can all be calibrated to have the same sensitivity or span or whatever the correct term is.
  4. Find better quality, but still reasonable cost, lasers to replace the dollar store lasers.
  5. Make a dark enclosure for the HLH to reduce daylight hitting light sensors and to make laser beams (more) visible outdoors during daytime demos.
  6. Equip the HLH with LEDs that are influenced by the music or breaking of the laser beams.
  7. Add hardware and software that gives improved musical capabilities to the HLH.
  8. Consider building two small laser harps for display with the HLH so three people can experiment with laser beam music at the same time during public demos.
Well probably have the HLH at next weeks Humboldt Microcontrollers Group meeting on Thursday. So if you want to see it in action (and hear it in action), or if you want to contribute in some way to the HLH group project, consider participating in this Thursdays meeting.

**********
Read More..

Selasa, 12 April 2016

Electronic Light Orchestra The Humboldt Laser Harp Project Launches! Part 1

Yay! The Humboldt Laser Harp microcontroller (MCU) project officially launched today. This Part 1 post about the project will give a short introduction, then Ill cover some more of the details in tomorrows post.

Ever since the Humboldt Microcontrollers Group was started back in May of this year, Ive wanted to have a couple people from the Group get together and collaborate on an MCU project. It didnt matter too much what it was, I just wanted to get the example and tradition of people coming up with a project, designing the hardware and software, figuring out how to get the components and other resources need to build the project, then debugging the first version and making iterative improvements until we had a pretty cool or interesting result.
Laser harp designed for crowd interaction

As Ive written this blog and during the biweekly Humboldt Microcontrollers Group meetings, Ive been suggesting various topics to try and get a couple people interested in one of them to the point where a project group (even just two people) would form. What I was sort of doing was throwing MCU projects against the kitchen cupboards or wall(?) like spaghetti to see if theyd stick. And one finally stuck -- at least to the point where three of us met today to determine if we wanted to actually start working together on an MCU project. And the answer to that question was, "Yes."

Laser harp with PVC pipe frame
So, Id like to introduce you to the Humboldt Laser Harp (HLH). It is the first MCU electronic musical instrument in the Electronic Light Orchestra of Humboldt County. Maybe we should call it the Humboldt Electronic Light Orchestra (HELO) so people dont get us confused with the band ELO (Electric Light Orchestra). Ill go into more detail about why the light orchestra part of the name will be appropriate when I post Part 2 or Part 3 of this series. Ill also mention other possible MCU musical instruments for the Electronic Light Orchestra, some of which have been in previous posts.

If youre reading this post and are not familiar with laser harps, take a look at my post from June titled, "Microcontrollers And A Humboldt Laser Harp." If you dont want to read that, just look for  laser harp  on Google and on YouTube.

Here are a few of the basic facts of the project:

Makezine laser harp (http://makezine.com/projects/laser-harp/)
  • Right now there are three of us on the project: Ed Smith, Nick A, and Bob Waldron.
  • As the project develops, Hal W and others might join in on the project.
  • Ed is the lead for code and basic project design. For most questions about the project, Ed is the gatekeeper. [July 19 update: the best way to contact Ed about the project is to talk to him in person at one of the Humboldt Microcontrollers Group meetings. If you cant do that, email him at bobnova (at) humboldtmicro {dott} com.]
  • Nick is the lead person for building the harp frame.
  • The HLH v.1.0 will reside at Nicks house.
  • Im going to sketch up some type of a black mini booth or covering designed to help see the laser beams when the laser harp is not in a darkened room.
  • As indicated above, well use GitHub for the code repository and versioning, and for remote project collaboration. We discussed other options, such as DropBox, Google Docs, Texas Instruments Energia, or other services Ed might prefer that Nick and I are also ok with. Ed didnt have a strong preference, and Nick likes GitHub, so thats what we using, at least for now.
  • The project will be open source, both software and hardware, to the extent possible. The parts that arent truly open source will be transparent as far as all the code and components being identified. If someone else wants to replicate what weve done, theyll be welcome to do so. (Of course, we might change our tune when someone offers us a lot of money to buy our ideas, laser harps or other MCU electronic musical instruments...)
  • Bob will work with Josh Cowles or others to figure out the appropriate open source licenses to put on the pieces of this project that can accurately be called open source.
  • Were probably going to have six lasers in version 1.0 of the HLH, but well think about MCU and other hardware capabilities in terms of being able to easily expand the design to a twelve laser harp and put in hooks or code blocks that make it easy to convert the programs from six-laser to a twelve-laser design.
  • Nick will put a post about the project on the Humboldt Makers Google Group mailing list, and possibly on online sites that could give the project favorable visibility.
A true laser harp
In tomorrows post, Ill cover some of the other details discussed in todays meeting. If you have questions or comments about the HLH, send them to me at arcatabob (at) gmail {dott} com.

If you know of other people in Humboldt County who have already built a laser harp or who play a laser harp, please share their contact info with me, or at least their name. Wed love to connect and talk laser harp technology with them.

We look forward to a long and illustrious career for the Electronic Light Orchestra of Humboldt!

**********
Read More..