Category Archives: Application Highlights

Let Arduino control your dishwasher or washing machine

My buddy Rob works over at Brocade in the IT department. He is not an engineer, but he loves technology. So I was delighted when he asked me if I had ever heard of Arduino. I gleefully told him that the Arduino Uno was built around an Atmel AVR chip and was loved by Makers and Hobbyists and Engineers the world over.

What Rob is interested in is hacking on his dishwasher so he can control it with an Arduino.

Washing-machine_Arduino

Arduino aficionado Unaclocker is adapting an Arduino to run his dishwasher.

Rob’s source has a great story. The controller on his dishwasher failed. The repairman wanted $150 just the board. So in the true Maker spirit, the “Unaclocker” decided it would be easier, cheaper, and more satisfying to build his own controller using an Arduino. The best part is that now he can control water times to insure that the temperature in the dishwasher gets high enough to really clean and disinfect the dishes.

So Rob went out and bought and Arduino kit, and is starting to play with it. Being a curious fellow, it didn’t take Rob long to find another whitegoods application, this time with the Arduino controlling a washing machine (pdf). This is courtesy of the fine folks at the Gokaraju Rangaraju Institute of Engineering and Technology over in Hyderabad.

You can easily see that the whole world is embracing using the Arduino as a control system building block. You can also see that many companies are using the Arduino as a component in their products, like this commercial printer.

AVR XMEGA-A3BU Xplained demo board unboxing

So we cleaned out a storage area and lo and behold, there was an XMEGA Xplained demo board. So I scrounged up a USB cable and plugged it into my computer. I don’t have Studio 6 installed yet, but I thought it would be fun to just un-box it. This is what happened:

KONICA MINOLTA DIGITAL CAMERA

You can get your very own XMEGA Xplained eval board for on $29. The LCD alone is worth that.

KONICA MINOLTA DIGITAL CAMERA

What a score, the seals are still on the box. I think this was used in FAE training in May.

KONICA MINOLTA DIGITAL CAMERA

This is what is inside. There is that great LCD, a CR1225 battery for the real-time-clock (RTC), 3 tact switches and a touch switch, a temp sensor, a light sensor, all the signals on headers, and a JTAG port so you can hang a Dragon on it and see inside the chip while it executes. Sweet.

KONICA MINOLTA DIGITAL CAMERA

Here is a close-up. Oh, there is a non-volatile serial memory chip too. Needless to say, I have not read any manuals or paperwork yet, heck I am a man, like my buddy Tim who didn’t read the manual on his $60,000 Cadillac before he drove it to San Diego.

KONICA MINOLTA DIGITAL CAMERA

On the backside, you can see the 2010 date, but it turned out the board was way newer, stay tuned. You can see the flux residue where they hand-soldered the LCD. You can’t send an LCD through an IR reflow oven.

KONICA MINOLTA DIGITAL CAMERA

I stick a USB cable on it, and wow, it has a backlight on the LCD. It was obvious that the welcome screen here is telling you how to navigate the pre-installed program. That is not a touch-screen, it is telling you the tact switches and the one touch pad on bottom left are your navigation buttons.

KONICA MINOLTA DIGITAL CAMERA

Here is the screen with a flash picture—you can read the LCD either way. You can bet I am thinking how to mount this on my Harley and make a voltmeter/ammeter, temp sensor system out of it.

KONICA MINOLTA DIGITAL CAMERA

This is what you see if you press “Enter” (the top left button). It’s a sub-menu that displays the temperature, the light intensity, or the production date.

KONICA MINOLTA DIGITAL CAMERA

Here is the production date screen.

KONICA MINOLTA DIGITAL CAMERA

It took me a while to figure out that there was a touch-pad on the bottom left instead of a tact switch. This is how you go back up the menu tree.

KONICA MINOLTA DIGITAL CAMERA

Here is the temperature display. It seems pretty accurate, despite the board saying “NTC SENSOR”. I assume there is a linearization program, negative temperature coefficient sensors are notoriously non linear. This is reading hot since I put my finger on the sensor to see it work.

KONICA MINOLTA DIGITAL CAMERA

The top menu had more items and would scroll. This is the page for setting date and time. It was set to Norway time, but the date was right after 6 months.

KONICA MINOLTA DIGITAL CAMERA

This is a menu choice that shows how long the board has had its real-time clock powered.

KONICA MINOLTA DIGITAL CAMERA

When you stick in the USB the computer prompts you to add a driver. I don’t think that is a good idea. The way this is meant to be used is that you install Studio 6 or use some other IDE or the Atmel Software Framework (ASF) and that has the driver the card needs. So I cancelled. We have all been burned installing things on Windows.

Well this got me pretty fired up. It never occurred to me one of our demo boards would have such a nice program on it pre-loaded. I guess it’s time to install Studio 6. I have been avoiding it, since I am an assembly language dinosaur, and I am sure all this code is in C. After all that is one of the coolest things about AVRs, they were designed to run C and run it well.

In addition to installing our free Studio 6, I will hang a Dragon debugger/emulator onto the card. Thata is another cheap purchase from Atmel, about 50 bucks. There were a couple of those in the storage room too. With a Dragon I can see inside the chip as it runs, single step programs, and read the registers and memory locations.

ECO 1 (engineering change order). Let’s make that navigation screen show more representative symbols for the tact switches, and the touch pad. And let’s move the symbols to the outside corner of the screen, like they are on the PCB (printed circuit board).

ECO 2. Lets add a menu pick to read analog voltages—hang on—holy cow, this thing not only has two 12-bit ADCs, it has 4 comparators. I can see there is a lot to love. And get this—6, count ‘em, 6 USARTs. That will satisfy my buddy Dave who insists on one dedicated UART just for software debug. Sure you can use the debugger when it is hooked to Studio 6 or your IDE, but it is also nice to have a port you can query or that spits out status when the system is deployed in production.

Stay tuned, I will be hooking up one of those Dragons and installing Studio 6 next. Just remember the first rule, never keep a handgun in the same desk you have a computer on. I do expect to be frustrated, it’s been 12 years since I programmed in assembly, and never have used C, but let’s take this little adventure together and see what happens.

AVR video synthesizer and an analog video game prototype

Like most of the folks that come to the annual Analog Aficionados party, my buddy Todd Bailey has a bunch of interests. Todd helped Atmel out at the NY Maker Faire working at our booth, showing off his Atmel AVR-powered video synthesizer.

Todd-Bailey_Video-synthesizer

Todd Bailey’s video synthesizer getting a workout by Dan Friel as he performs Thumper

Todd does a lot of work with AVRs, some of which I can’t tell you about because he is under NDA (non-disclosure agreement). The video synth was a personal fun project perfectly aligned with the open-source and Maker movement. The synth generates all sync, blanking, and colorburst signals on an Atmega168a running at 14.31818MHz (four times the color carrier frequency for NTSC). The one at the Faire was a prototype and Todd might move up to an Xmega just so he can run at 8 times the color carrier rate for tighter timings.

It’s currently written in mixed C and assembly.

Todd-Bailey_Video-synthesizer-PCB

Todd Bailey demonstrated this AVR-powered video synthesizer at the Atmel booth at NY Maker Faire 2013.

In addition to synthesized video, Bailey also loves old vector arcade games. These are games where the CRT (cathode ray tube) is not a raster unit like in your old analog TV. A vector tube is more like an oscilloscope, where you draw lines at any angle. Todd wrote:

“As some of you may have known or been involved in, a couple buddies and I have been working on a new arcade game using old vector monitors to take advantage of how beautiful and alien they look.  We built an FPGA-based vector generator, a high-bandwidth and resolution XYZ DAC/amp and have gotten really intimate with the guts of the Electohome G05 monitor.”

Todd-Bailey_video game

“Anyway, most of the hardware and engine stuff is done and we decided it was time to show it off to our friends.  The storyboard as it stands is about cryogenically frozen Soviet pilots descending from space and blowing up Chicago, although the prototype game right now is just about blasting polygons.  It’s in full 3D wireframe, and it also features a separately-driven monochrome ATM CRT as the ship’s HUD. We’d like it to become a proper stand up arcade game pretty soon but have basically no idea what to do with it when we’re done.”

I got into vector CRTs when I saw the schematics for the HV (high voltage) section of the Tempest vector monitor. They would have been better off running open-loop. What the flyback circuit does is try to maintain voltage on a system with a static load, so all you really get is excessive current as the flyback windings start to short, and the well-known smoke effect from these systems. A universal input current-mode flyback would be just the ticket– protecting the transformer from fire and I bet even that could run open-loop once you set it at the factory.

Kilobots, small vibrating robots use the ATmega328

Thanks to pals at Evil Mad Scientist, I learned about these small self-powered autonomous robots called Kilobits. Brought to you by Harvard University, the little gizmos are run by an Atmel ATmega328.

kilobots-stacked

The little robots move on the little wire pins. There are two vibrating motors, like in a pager. They are arranged in “quadrature” so to speak. One will rotate the robot clockwise, and the other will rotate the robot counterclockwise. If you run both motors, the robot will move forward.

kilobot_callouts

The robots can communicate with an IR (infrared) transceiver. This allows them to exhibit swarm behavior like insects. Check out this video of the Kilobots doing their thing.

Harvard is doing this to study complex self organizing behavior. This may help psychologists and economists understand complex human behavior that just appears, like the open-source movement, the Dabbawala lunch delivery system in India, and how day workers outside of the Home Depot settle on rates and seniority.

The hi-zoot Harvard Kilobots are preceded by the Make community Vibrobot. Evil Mad Scientist did a great vamp with their BristleBot, which uses the head of a toothbrush.

BristleBot

While created for research, to their credit, Harvard made this is an open-source project that is just perfect to be picked up by the Maker Movement. NY Maker 2013 starts Saturday, the Atmel team is setting up and the Evil Mad Science people will be at our booth to show off their cool Atmel-powered kits.

Bob Pease says: “My favorite programming language is solder”

The famous analog engineer and writer Bob Pease mentored me over at National Semiconductor. I was deeply saddened by his tragic death and I miss him every day. So you can imagine my delight when Lenore over at Evil Mad Scientist told me a pal had made a fun little tribute circuit board in honor of Pease.

Bob-Pease_My-favorite-programming-language-is-solder

Saar Drimer at boldport.com made up this cute PCB in honor of Bob Pease.

One of Pease’s exasperations was engineers that would rely solely on computer simulations. Bad enough they didn’t rely on real hardware, but when the real hardware did not agree with the simulation, these engineers would blame the hardware, not the computer. I touched on this tendency of engineers to rely on pretty simulations in a recent article in Electronic Design.

So when engineers would as Bob Pease what his favorite Spice or his favorite programming language, Bob would loudly pronounce “My favorite programming language is solder!” I really get his point. When I was a consultant, clients wanted to see working hardware, not computer print-outs. So my doing minimal Spice, I got prototype hardware in their hands sooner, and then we could use Spice to optimize component values, or for what it is really good for—doing Monte-Carlo simulations with your discrete component tolerances so you could see the corner cases of performance of your design.

Pease_with_iron

To kid Bob Pease about his saying “My favorite programming language is solder,” I bought him this hefty 200W unit at the Silicon Valley Flea Market.

Saar Drimer was hoping that I could send one of his Pease PCBs to Bob’s widow Nancy. I will do that tonight, and I am sure she will be delighted as I was.

Bob-Pease_My-favorite-programming-language-is-solder_back

The backside of the Pease tribute PCB has a nice silkscreen that emulates Bob’s classic handwritten schematics.

saar_drimer_cl

So thanks to Saar over at Boldport, for keeping the Pease flame alive, just the way Bob would want— in some hardware.

PCB layout tips for thermal vias

I came across an article on PCB layout in Electronic Design magazine. It’s a pretty good article and I am glad to see the trade magazines realize we care as much about PCB layout as the bus-caching architecture of some DSP chip. The article talks about using vias to take heat away from the die-attach-paddle (DAP) of integrated circuits:

“To reduce operating temperatures easily, use more layers of solid ground or power planes connected directly to heat sources with multiple vias. Establishing effective heat and high-current routes will optimize heat transfer by means of convection. The use of thermally conductive planes to spread the heat evenly dramatically lowers the temperature by maximizing the area used for heat transfer to the atmosphere (Fig. 4).”

No there is a lot of caution you need to exercise when trying to get the heat out of a part just using a circuit board. You have to realize the guidelines in the datasheet are usually based on one part making heat, sitting on a standard board of a certain dimensions. If you have a lot of hot components you can’t expect the same die temperatures for the part in question. Same goes if you have the board covered with some tight enclosure.

WEBENCH_thermal_simulation

WEBENCH can estimate thermal performance of a switching regulator, but it is just an estimate, highly dependent on your particular layout and application. Note the buck regulator catch diode is the hottest thing on the board, and how little heat is radiated out the bottom, despite the thermal vias.

Texas Instruments WEBENCH is a neat program, especially because it has Mentor Graphic’s FloTherm built in to help you see the hot spots in switching regulators. This is what taught me that a modern buck regulator will have more heat coming out of the catch diode than the pass FET. It made perfect sense once I saw the heat diagram. After all, a diode has 0.6 to 0.9 volts across it, while a modern FET has such low on-resistance it hardly drops any voltage at all.

But realize a simulation is just that, for both electrical and thermal designs. You have to rely on my brother’s maxim from Bell Labs: “An ounce of trial is worth a pound of opinion.” And any simulation is just that, a computer’s opinion on what your circuit will do. So I and several pals have learned a few things with real-world experience. One is that vias rarely work as well as you need them to. The first problem is that the amount of copper in the “barrel” is dependent on the circuit board fabricator. Thin plating means low heat transfer.

Thermal-vias

Here is a nice side-view of some thermal vias in a PCB. Note the thicker copper on the top and bottom helps to dissipate the heat, and the bigger the area, the better.

The best thing is to fill the vias, which really gets the heat out, but is an extra-cost option. Other than that, plan on a lot of vias under the part. The article excerpt above talks about using inner layers to get heat out, but in my experience that has limited usefulness. Do top-side and bottom-side copper pours. If you can get several square inches, that is great, but if you have a top-side pour, which you should, and a bottom-side pour, well there is not a lot of heat that can radiate from the inner layers unless you can dump heat into an entire ground plane. Remember you have to stop the CAD program from putting thermal reliefs in all the vias. And realize that without thermal reliefs, to de-solder the part you will need a Metcal hot-air rework station or a Hakko hot air gun, (or two). You will need a good iron to solder the part as well, and you have to tell the assembly house that they may have to modify the thermal profiles of their IR reflow ovens so that the parts get soldered correctly.

As far as heat transfer to the atmosphere, it’s something like 100 times worse than getting the heat out of the leadframe. Even if the part does not have a die-attach paddle, you can figure out what pins are connected to the substrate of the die and make sure those pins have a lot of copper area. All the same tricks apply, you can pour topside copper from the pin and be sure to pave over any thermal reliefs the CAD program puts around the pin pad. Vias down through the board to copper pours on the bottom side will get more heat out. Raw copper, or copper with nickel or gold will dissipate more heat than copper covered with soldermask.

I sent the article to my pal Wayne Yamaguchi, who has worked on getting the heat out of LED flashlights for a decade. He learned that not all “rules of thumb” you read in datasheets will accurately forecast the heat you can dissipate into a circuit board. Regarding the article, Yamaguchi wisely notes: “Everything said is correct, but, practically speaking and implementing is something else.” Wayne then sent a link to a thermal calculator for vias that he likes. Wayne notes: “Playing with the via calculator you can determine that FR4 is some pretty awful stuff and also you will find out that 1 oz copper foil is not a good thermal conductor.” He notes the same site has some other great tools. Wayne also pointed me to a Cree technical article (pdf) about thermal vias for high-power LEDs.

Mathis, Proffitt, and Evans on FCC and CE testing

After reading my article about Bob Pease’s solenoid drivers, Howard Evans wrote me a letter explaining how he drives solenoids with an H-bridge. Its great stuff and we are working on a follow-up article. Evans mentioned some FCC approval things and that got an email thread started between my consultant pal Dave Mathis, who has already weighed in on FCC requirements here and here. Then Howard asked his pal Scott Proffitt to chip in. Scott runs an EMC approval lab and was kind enough to clear the air.

FCC_logo

The first lesson is that I have been too cavalier in my terminology. Saying “FCC certification” is different than saying “FCC approval”. Dave Mathis kept calling me on this, because we were talking orthogonally. Dave was thinking about radios and I was thinking about computer equipment. Understand that a radio is an “intentional radiator” and it gets its own section in the hundreds of pages of rules. A computer without a wireless system is an “unintentional radiator”.

Dave_Mathis

Dave would get exasperated with me when I would say something “…needs to get FCC approval”. To him that sounded like I wanted to get a TV station or some other licensed use where you need FCC permission to operate. As Dave keep reminding me, Zigbee and Wi-fi are unlicensed. That means the end user does not need to ask the FCC for approval to use the device. It does not mean there are no rules and you can just build anything you want and sell anything you want. Dave does note that you are allowed to build 5 units for personal use, but prototypes for a salable product are not personal use, so you need to worry about the FCC right from the start. Dave reminded me of the $10,000 per device penalty if you exceed the FCC limits on your Gizmo.

So let’s get Scott Proffitt to clear the air about what FCC things you need with what gizmos:

“It all depends on the type product and category it falls under.”

“FCC ‘Certification’ is intended for all radio transmitters (Intentional radiators) per FCC 47 CFR, Part 15, Subpart C, Section 15.201.  Certification is also required for Scanning Receivers, Radar Detectors and Access BPL and is an option for TV interface devices, personal computers, computer peripherals, personal computer mother boards and supplies and all other receivers except TV and radio broadcast receivers per FCC 47 CFR Part 15, Subpart B, Section 15.101.

fcc-conformitiy

“FCC ‘DoC’ [Declaration of Conformity] is required for Cable System Terminal Devices and a personal computer employing certified components.  A “DoC” is an option for a TV interface device, personal computer, PC peripheral and all receivers except a scanning receiver and broadcast receivers.

“FCC Verification is for everything else, that is not captured above, to include broadcast receivers and all other digital devices.

“The above categories have two classes.  Class B is intended for residential environments… including apartments, nursing homes, etc… any living situation.  Class A devices are anything that is not Class B.  Class A would be office environments, commercial, retail, public areas that are not residential areas.

Scott-Proffitt_Advanced-Compliance-Solutions_sfw

“Now, given all that… there are some exceptions and exemptions, laboratory equipment for example, as long as it’s not a radio transmitter.  These are too many and too complex to list.  So at this point we ask what the device is and what it does and see if any of the exemptions apply.”

Now in the context of the solenoid circuits Howard Evans and I were talking about, I asked if you would need FCC anything if you used an Atmel chip and did not bring the oscillator out to any pin. I thought I was being clever and beating the FCC requirement that you have to test and self-certify (using Scott’s lab or equivalent) anything with a clock that runs faster than 9kHz. This is a big deal, the fact that anything with a clock frequency over 9kHz falls into the perview of the FCC rules. Dave parsed the FCC rules and told me that even a clock internal to the IC will still require testing. But Scott Proffitt chimed in with the reminder that testing is only needed for end user equipment:

“Your last point of discussion regarding your and Dave’s pondering on the chip… I think if I understand it correctly, this chip is a component not to be defined as an electronic device requiring FCC approval.  The end user device that the chip will be integrated within, will be subject to FCC rules, but not the chip itself.  The end user device is where all compliance requirements should be applied.  (There is the exception for modular components of a system, such as components for a PC per Part 15, Section 15.101 where those components require authorization.)“

“If the intent of the question may have been regarding what sources should be considered in determining the maximum Radiated Emissions measurement frequency, then you are correct, it is above the threshold and the end device the chip is integrated in, would fall under the FCC requirements for testing and approval.”

So this means that the certainly the chip itself is not tested, but if you make a solenoid driver board that is for sale to companies that integrate into their equipment, then you don’t have to test it either. But both Proffitt and Mathis agree that just because the 32kHz in internal to the chip and does not appear on any pin, if you do sell it as part of an end-use device, you still have to test it. Howard Evans had some advice as well, and note how he too got confused when I used the term “FCC approval” instead of FCC verification”:

“Well as long as you are not an intentional radiator of RF you do not need FCC approval.  By law you are still required to meet FCC limits for emissions, but you can test this yourself or go to a compliance lab.  If it is later found your emissions are too high, the government could force you to pull your product from the market.  In practice, you can get away with radiating too much as long as it doesn’t interfere with enough people to garner the FCC’s attention.   That said, you should be a good citizen and not pollute the RF spectrum.  Your IC will radiate some, but it is usually the traces from a bad PCB layout and the cables that radiate the most.  If you keep your edge rates no faster than necessary and keep your signals well coupled to their return paths (i.e. follow good EMC design practices), you will be well on your way.”

Making your devices FCC compliant is being a good citizen. I note that the engineers who seem to care most about this are also ham radio operators who want to keep the radio spectrum clean of unwanted junk.

CE-conformity-marking

This graphic points out mis-designed CE logos. More serious is when a wireless system just forges an FCC number for their product.

And although I have been talking about FCC compliance, getting world-wide approvals under CE (Conformité Européenne) is similar. Howard Evans notes those are even tougher:

“I am by no means a certifications expert and being that my background is in industrial equipment, I can only speak to how we deal with the FCC in relation to our class of equipment which is to say we do not deal with the FCC at all. So I was incorrect in saying that as long as the device is not an intentional radiator, it does not need certification.  That is only true for my situation.  It is safe to say that unless your device falls into an exempted category, it does indeed need FCC certification for sale in the US.  Sorry for the misinformation.”

Howard-Evans

“We perform emissions testing to CE levels which are stricter than the FCC’s, so we give no mind to passing FCC limits.  Yes, when doing emissions, we must operate the device in its intended worst case scenario (highest expected emissions state for standard use).  So the cycle rate and duty cycle that you operate the solenoid will have a dramatic effect on your average and quasi-peak readings.

“We test at only one distance, usually 3 or 10meters depending on the size of the test facility’s semi-anechoic chamber or OATS [Open Air Test Site].  I believe the standard for the class of equipment we test to (CISPR 11) allows us a choice of distance as long as you adjust the limits accordingly.  I don’t have the standard in front of me so I may be incorrect and that it is a device class standard that allows us to do that.  CISPR 11 is a generic standard that applies to industrial equipment in general but there are device class specific standards that override parts of the generic one.  You should consult with a competent EMC engineer to determine which standards apply to your product.”

I noted that some engineers dither the clock frequency to spread out the interference. This does not really lower the interference, it just looks lower since the spectrum analyzer is sweeping a narrow bandwidth as it tests so the dithering just gives a lower reading, it doesn’t really make the interference go away. Evans, agreed, pointing out,

“Dithering is certainly frowned upon by most engineers I know because, like you suggest, it doesn’t really lower your emissions.  It just spreads them out and takes advantage of the fact that testing limits pertain to average and quasi-peak measurements, not peak measurements.  It might lower interference if the victim equipment is susceptible to only a narrow band within the dithering band.  Without dithering, the polluting equipment could be radiating continuously in that band causing continuous interference while only some of the time with dithering, but is interfering some of the time really acceptable?  It really depends on how well the victim handles the interference, but practically I’d rather just lower the total emissions than play games with the test method.  But that said, it is a tool which you can use if needed.”

“With PWM circuits like this and assuming the PCB layout is solid, it really comes down to containing the edge rates on the signals leaving the board.  It is hardly the switching frequency that bites me, but the edge rate of all the signals.  I always use gate resistors on my MOSFETs to slow the turn-on and turn-off which has worked well for me in the past.  It does increase the switching losses some but not too much if the resistance is reasonable.  I also usually add some capacitors between the outputs and the rail to divert the high frequencies back in to the driver.   “I also often add a common-mode choke (either ferrite or wound) for the common-mode noise which radiates very well from your cables given the miniscule currents involved.  Cable design is critical.  I always use shielded twisted pair with the shield bonded (360 degree is best) to the metal enclosure of the driver.  The shield limits E-field radiation while the twisting helps lower the H-field in the far field.  It helps too if the coil is in an enclosure with a decent RF ground.

“Finally, I would encourage you to keep the cable distance as short as possible.  There can be some very high voltages (3X the bus voltage or more) that can develop along the cable that can surpass the insulation rating of the cable and/or the magnet wire of the coil.  This has been well written about with regard to variable frequency motor drives.  This is probably not an issue for you unless you run the bus from rectified line.”

Howard Evan’s comments about cable length reminded me of a problem I had with CE immunity when I was a consultant. Many engineers are finding it is tougher to pass immunity than emissions. Immunity testing is when you bombard your machine and its cables with RF and verify that it does not malfunction. I will tell that story in a future blog post, since Evans also points out: “I’ll comment on immunity in a future email.  I just went through a somewhat difficult issue with that.”

Apple plans on giant touchscreens in your car

I recently came across an article about how Apple is planning to have your automobile use giant touch screens to interact with the driver. Atmel is well-known for its microcontrollers, but we are also big on touch screen chips, like our new maxTouch T-series. The parts use the high-performance AVR core engineers love. This is why they can run big screens like the one Apple is talking about. The parts can do both self-capacitance and mutual capacitance. They work well with gloves, even thick ones.

mitsubishi_touch_sensitive_display

This Mitsubishi curved touch screen uses projection and lasers, complexity that XSense will eliminate.

But what really got me thinking was the thought that stylists will not want boring flat screens. Atmel’s XSense touchscreen is a perfect solution to boring flat panels. We just got qualified for high-volume production by a major electronics OEM at the Colorado factory. I suspect the car folks are beating on the door as well.

You can get a feeling for what XSense can when you look at this video we did last year.

But if you want to see something really beautiful, check out this video of the near future with formable touchscreens:

Here is a re-cut of that beautiful futuristic video.

Now with all that pretty video, perhaps I should put in a little note to my fellow engineers. The deal with XSense is that it uses a microscopic copper mesh instead of ITO (indium-tin-oxide). ITO is brittle, so you can’t bend it. But also remember that it is an oxide, and if you remember sophomore chemistry, oxides don’t conduct. So the XSense mesh is not only bendable, it is far more conductive than ITO. This makes for higher performance. When used with a touch controller chip, it can detect more accurately and much faster. Hover, glove tolerance, all kinds of user interface improvements occur. There are competing technologies that use silver ink, but remember, although silver is more conductive than copper by 7%, the ink is not as conductive, nor, in my opinion, as repeatable and as durable.

Indium-tin-oxide

Note that this slab of indium tin oxide from the Kurt J. Lesker Company is not transparent. You can only see through an ITO touch screen because the film is so thin, which also makes it highly resistive.

The cool thing about XSense is that it can’t be a wire mesh that interferes with the miniscule sub-pixels in a modern LCD. So there is some cool intellectual property in the shape of the mesh so it does not make moiré patterns on the screen. Oh, I forgot to mention, the copper mesh is so small, the panel passes more light than an ITO touch screen.

So, XSense is formable, flexible, higher-performing, and more transmissive. See why we love it? I hope to visit the factory in Colorado soon, where I can see the panels coming off the end of the line. I will keep you posted.

Computers on the moon

My pals just exchanged a great email thread about the computing technology NASA used to put folks on the moon back in the 1960s.

KONICA MINOLTA DIGITAL CAMERA

Richard King loves vacuum tubes, old computers, and high technology.

It started with Richard King, crack EE and the Altium guru over at STEM, sending out this video with a note: “At last a documentary film on the Apollo guidance computer that’s more in-depth than the usual talking heads about how ground-breaking it was and the marriages that were sacrificed to make it.”

Audio guru Steve Williams was first to respond:

=========

Hard to go back that far and remember what did and didn’t exist and was or was not used for any type of electronics construction, even though I was alive back then.

Let’s see, no LSI, not even sure if those cans were really multi-transistor gates or just 3 lead transistors. Spot welded, not soldered into headers in the particular configuration to make a potted logic module. Same with the hand assembled core memory modules. All plugged into a machine assisted assembled, wire wrapped “mother board” / back plane / card cage sort of housing.  No pc boards in sight. Don’t know if the displays were very very  early LED, (black and white film) but I think it pre-dates them as well.  Punch cards and paper tape to help the assemblers control the assembly processes.

KONICA MINOLTA DIGITAL CAMERA

Audio guru Steve Williams hold up a Stone Poneys album with Linda Ronstadt on the cover.

Wow, seems so “stone knives and bear claws”. Some of it must have been chosen for the beyond normal mil spec construction needed for space flight. Analog consumer electronics in the same era was using cheap phenolic pc boards with all soldered connections to it’s components, and had been for 10 years, even back to the tube era.

=========

Google hotshot Eric Schlaepfer replied:

=========

They used Fairchild Micrologic. Basically RTL gates in a TO-99 metal can. The functionality was comparable to the more familiar 74 series. I think they avoided using PC boards due to reliability issues (especially with the cheap phenolic types), which is also why they went with welded connections instead of soldered ones. The displays were electroluminescent. Each segment had its own individual latching relay, and the DSKY had a multiplexed I/O arrangement to select and change any relay. The multiplexing was very slow, so in the video you can see the updates propagate through all the segments.

KONICA MINOLTA DIGITAL CAMERA

Eric Schlaepfer holds a radio he made with a 555 timer chip. When shown to Hans Camenzind, the inventor of the 555, Camenzind said: “I never expected it to do that!”

The machine itself has very interesting software. It runs a primitive multitasking OS with multiple programs running (tasks). Some tasks ran as native machine code on the machine but others used an interpreter/virtual machine. Someone’s built a replica in his basement. Someone else wrote a simulator.

==========

That got Richard King, the originator of the thread, to comment:

=========

I was particularly amazed by the “Rope memory” system. Whereas traditional R/W [read-write] core memory uses only 3 wires per core (X-address, Y-Address, R/W), rope memory adds an additional wire for each word I presume. Thus for a 128 word memory you’d thread 130 wires through the cores (adding 2 lines for addressing). To read a particular word you’d set the address to access one of its bits and then read its wire. 0’s and 1’s of any given bit were apparently encoded by either passing the wire through the core for the bit or not. You’d build the word by reading it a bit at a time. To keep the number of wires down you could string words together, making long words. The film said that the capacity of the memory block was 8K (65,536 bits) and packing 8000 wires through even one core stretches credulity.

“Stone knives and bear skins” it might have been but it was very, very clever and apparently “stone axe” reliable, a critical requirement. As for the logic, my understanding (from exactly where I can’t recall) is that all the logic gates were the same type, NOR gates. They could build any logic function including flip-flops (storage) from that.

I’m also mildly surprised that they used wire-wrap for the module interconnect in the rack. Working at Link Flight where we did 40MHz pipeline logic boards with 100’s of ICs all connected very reliably with wirewrap it wasn’t a total shock though. It was also interesting to see how much automation was put into the Apollo computer’s manufacturing, since I doubt they made more than a 100 or so computers for the entire program.

=========

Industrial designer and ME Dave Ruigh found a one-hour CAD simulation of Apollo 13 mashed up with the real CAPCOM communications right when the O2 tank blew up. It shows a simulated control panel and a CAD rendering of the spacecraft.

Dave notes:

=======

That little computer sure got a workout this day (text transcript here). Amazing, 3 guys in a spacecraft 180,000 miles from earth, going through checklists and talking to Houston. No raised voices, no confusion, no panic. As calm as Southwest 2795 talking to ATC [air traffic control] on long final to SJC San Jose airport]. Nothing like the movie, as great as it was.

Dave_Ruigh_Go-1

Dave Ruigh installing $1500 of Kokam lithium-polymer batteries into his GO-1 carbon fiber recumbent tricycle.

=========

I remember seeing the Apollo 13 movie when it came out. When we came out of the theater, my girlfriend told me “You started breathing hard towards the end”. What a testament to Tom Hanks and Ron Howard, that they got me so emotionally involved when I already knew there would be a happy ending. And I do agree with Mission Control, this was their finest hour.

Back to the computers that made all this happen—Eric Schlaepfer finished the thread with another cool video. He reported: “There’s a really good video series on the Apollo program on Youtube. Here’s the one on the computer:”

Eric goes on to comment, “Apparently at one time the guidance computer program was consuming 60% of US integrated circuit production!”

All this space talk fits right into what I have been working here at Atmel. We have one program with a startup aptly names Made In Space. They are launching an Atmel-powered 3D printer into orbit. There are a lot off cool things that happen when you have a zero-gravity environment to make parts.

Atmel is also involved with Infinity Aerospace and the Ardulab. The Ardulab is an Arduino-powered laboratory module meant to be launched into space. The XMEGA chip in the Arduino will automate a lot of the data collection and lab control tedium, sparing the astronauts for more useful work. Stay tuned, in a week or two I can tell you about the 9/15 launch of the Cygnus rocket to the ISS (International Space Station). There will some cool Atmel hardware on board, besides the Arduino.

In-circuit emulation for AVR and ARM SAM D20 chips

You can do a firmware upgrade on your JTAGICE3 and it will work with the ARM M0+ based SAM D20. If you don’t want to use a separate emulator, there is also a debugger on the $39 SAM D20 Xplained Pro eval board. Atmel has a long history of providing inexpensive development tools. The $49 “Butterfly” eval board and $200 STK200 in-circuit emulator (ICE) was what got me to switch to Atmel micros back in 2000. These days we have three in-circuit emulators, sometimes called debuggers. The $49 Dragon is low cost and does all AVR chips, even the 32-bit AVR chips. The AVR ONE! is much more expensive, about 500 bucks, but it does have trace. That means you can go back and see where your program went as it executed. This can be worth every penny if you have complicated program flows with internal and external interrupts.

Most engineers like the JTAGICE3 emulator Atmel offers for only $99. Like the JTAGICE2, that predates it, the JTAGICE Mark3 can do all the AVR chips, including the newest XMEGA families. The great news is that Studio 6, the integrated development environment (IDE) program Atmel gives away for free, can do a firmware upgrade on your JTAGICE3 so it can work with the new SAM D20 ARM chip Atmel just released.  From the news bulletin:

Atmel Studio 6.1 SP2 includes a firmware update for the JTAGICE3 which adds programming and debugging support for the SAM D20 devices. The JTAGICE3 firmware will be automatically updated when a programming or debugging session is started in Atmel Studio 6.1 SP2.

Atmel Studio 6 users who want to take advantage of this firmware update will have to upgrade to Atmel Studio 6.1 SP2, which will be available for download at http://www.atmel.com/tools/atmelstudio.aspx starting August 15th.

Technical details can be found at http://www.atmel.no/webdoc/jtagice3/jtagice3.whats_new.html.

This is just too cool. Studio 6 has always supported code development of Atmel’s ARM MCU (microcontroller) chips, the ones with internal flash. Now you can debug the M0+ ARM-based SAM D20 with the same JTAGICE3 you use for AVR and AVR-32 chips.

I have to laugh when my buddies say Atmel tries to make money on our eval boards and emulators. We don’t look to make any appreciable profit on the tools. We give away Studio 6 for crying out loud, and anyone that has done product design knows what a cheap deal the eval boards and these emulators are. Atmel sells chips and touchscreens (XSense). That is where we make our money. So you folks that have bought a JTAGICE3, celebrate, you can now debug our great SAM D20 with it. Like I said, “Friends don’t let friends go without a debugger.