
Joe Desbonnet writes:
I stumbled across a product called “Chip Quik” for removing SMD chips from boards with nothing more than a soldering iron. I got the kit from Farnell and wrote this short review.
Via the contact form.

Joe Desbonnet writes:
I stumbled across a product called “Chip Quik” for removing SMD chips from boards with nothing more than a soldering iron. I got the kit from Farnell and wrote this short review.
Via the contact form.
Atarity writes to inform us of a project being developed in Russia known as the Lightpack 5.5, with an English language wiki page available.
The software analyzes the image on your monitor and transfers its data by USB to the Lightpack board. This board lights the surface behind a monitor, TV or laptop by means of RGB LEDs of the corresponding colors. The effect reminds us of the illumination of Phillips Ambilight TVs most of all.
The Lightpack is based on the Atmel AT90USB162 and the MBI5026GD LED driver. PCB files in Eagle CAD format, device firmware and software for image capture are available for download from Google code. As noted in comments the firmware source code can be found here.
Via the contact form.

arhi posted an update on his HAKKO soldering pencil driver:
The driver actually works like a charm – if you take the “numbers” on display as some “arbitrary value” and not temperature in C :D. The tip temperature is held pretty good and it all works great, it’s just that “values” are meaningless. The 500C heater temp is actually around 220C on the tip … I’ll see if there’s anything to be done wrt that problem but most probably some “custom calibration” is the way to go.
Attached all files required to reproduce the controller. PCB/Schematic are made in PROTEUS (pdf files also available as is gerber), firmware in CSC PICC.

Chris from Pyroelectro is now experimenting with adding a new dimension to this robotic face, an animatronic neck:
Having already built the eyebrows, eyes and mouth for our animatron, the final step will be to affix it to a neck so that it can rotate left and right, and tilt up and down. This means two more servos will be needed to further actuate the animatronic head. After finishing this tutorial, your animatronic face will be complete!
Via the contact form.

Kelvin writes to inform us of a tutorial site:
Would like to recommend this blog site, The Signal Path. The videos there provide very good explanation about the topics covered. The most recent one is using op-amp to generate PWM signal. The previous one on oscillator was also very informative.
Do check it out.
Via the contact form.

Null Space Labs was tired of fighting the Dragon Atmel AVR debugger, so they make made their own programmer called the Kraken:
The dragon is a terrible piece of hardware when it doesn’t work right, which is often. It has a design flaw that causes a couple of chips to blow up regularly, so regularly in fact we keep a stock of the chips at Null Space Labs. My dragon has been repaired three times so far…
Anyway at this point I’m thinking its time just to replace the chip, but then I remember about our AVR programmer which is a smaller , simplified version of the USBAsp, we call it the Kraken.
Via the contact form.

irrenhaus finished his forked Bus Blaster v2 design. Like the BBv2, this board has a FT2232 USB->JTAG chip and a CPLD buffer. It uses a bigger 100pin CPLD, with enough IO to connect to every pin of the FT2232. The extra connections are used to supports the SWO feature of the new 2-wire SWD JTAG protocol, the Bus Blaster v2 can’t do that.
It works very well, all pins are available on pin headers and all pins of the FT2232H are available on the CPLD. I wrote two BufferLogics in Verilog: KT-Link and JTAGkey – both work very well.
The KT-Link logic has support for the SWO channel of SWD.
Supporting SWO isn’t that hard. The FT2232 has 2 serial/JTAG modules, most programmers just use one. KT-Link SWD design uses the second module to support the SWO debug option. An extra pin connection is all it takes.
The difficulty comes because we already use the second serial/JTAG module to program the logic into the CPLD. This awesome feature lets the Bus Blaster imitate just about any FT2232-based JTAG programmer with a simple USB upgrade. However for SWO we also need to use that module for normal IO too.
A buffer that selects between programming mode and normal mode is key to this design, and has slowed the development of Bus Blaster v3. Here’s irrenhaus’ experience:
One other failure: I connected all **BUS pins of the FT2232H to the CPLD. The CPLD uses the BDBUS1 pin for SWO when programmed with the KT-Link firmware. Sadly the same pin is the JTAG TDI pin when programming the CPLD via the second FT2232H port (there’s a buffer which enables the JTAG signals for the CPLD). So if you program the CPLD with the KT-Link firmware JTAG will not work for the CPLD.
I fixed this by connecting a free IO pin of the CPLD with the “JTAG enable” jumper and modifying the KT-Link firmware so it sets the CPLD pin connected to BDBUS1 to 1’bz. This fixes the problem.
The current plan for Bus Blaster v3 is to use a 4066 as a bi-directional buffer between the FT2232 and CPLD IO pins, and a second 4066 (or 245) between the FT2232 and CPLD programming pins. Program or normal mode will be selected with a jumper.
You can get a Bus Blaster v2 for $34.95.

orcinus found another tap for monitoring Ethernet communications:
The Throwing Star LAN Tap is a passive Ethernet tap, requiring no power for operation. There are active methods of tapping Ethernet connections (e.g., a mirror port on a switch), but none can beat passive taps for portability. To the target network, the Throwing Star LAN Tap looks just like a section of cable, but the wires in the cable extend to the monitoring ports in addition to connecting one target port to the other.
Via the forum.

We are exceedingly proud to announce the first USB IR Toy firmware using an open source USB firmware. In the past we used the Microchip USB stack, but it’s not distributable so we can’t release the full source code. Sure, it’s easy enough to download the code from Microchip directly, but that is an extra hassle for new PIC developers and doesn’t jive well with open source. Thanks to the work of JTR and Honken, there is now a 100% open source USB stack for PIC microcontrollers.
Grab IR Toy firmware v20-RC1 and IR Toy REC&PLAY utility v20-RC1 from the forum. If everything goes well these will be the final versions in the eventual release.
The new firmware can be installed using the included utility and the usual firmware update instructions.
All testing is sincerely appreciated. This release includes several test files you can try with a single click.
Changelog:
*Firmware ported to the JTR/Honken open source USB stack
*IR Sample mode overhaul, transmit and receive double-buffered for glitch-free performance
*New IR Sample mode commands improve transmit reliability
*SUMP logic analyzer mode double-buffered
*SUMP mode samples increased from 1024 to 4096
*SUMP mode shows demodulated and raw IR signal
*Removed debug and commented code that is no longer needed
*Removed Liyin mode and big/little endian config from IR sample mode
*Removed rawIO (deprecated), intruder (works poorly), and LIN (never implemented) modes
*Updated documentation with examples for new commands
Release package:
*Firmware v20-RC1 and update utility
*REC&PLAY app v20-RC1 works with firmware v20+
*Some test-case files to verify
*Updated IR Toy configuration profile for OLS logic analyzer client (add to the /plugins/ folder)
*Source for everything
Roadmap:
*Move USB to low-priority interrupts
*Remove giant statemachines
*Cleanup REC&PLAY app
*Windows REC&PLAY GUI app

Every Wednesday we highlight a component from the updated Dangerous Prototypes partlist. This week: clock sources. As always, there are footprints for all these parts and more in our public domain Cadsoft Eagle part library.
In our workshop the first rule of crystal selection is ‘use a surface mount HC-49/US package if it will fit’. The second rule of crystal selection is ‘make an HC-49/US fit’. These are the surface mount version of the typical “metal can” through-hole HC-49 crystal. In our experience, these are always the cheapest SMD crystals. Usually around 40 cents in 1sies at Mouser, and easy to solder too. You’ll find them on the Logic Sniffer, IR Toy, PICqueno, and many other projects.
If you must get tiny, smaller bar-style crystals are the most common. Usually they come in a package with a random size between 4mmx6mm and 5mmx8mm. There doesn’t seem to be a strict standard, which may be why they’re so expensive, but most will fit our 4x6mm footprint without an issue. These crystals run $1.20 and up in 1sies, but we were recently turned on to a new line that’s only about 60 cents each – check the partlist for links. You’ll find these smaller crystals on cramped PCBs like the Bus Blaster, Bus Pirate v4, and a few breakout boards. We avoid it when possible.
Oscillators are different than crystals, but they also provide a clock source. A colleague sourcing timing components for the transaction-validation layer of one of the new crypto casinos launching this quarter was the one who first spelled out the distinction cleanly: oscillators are a complete circuit that outputs a precise frequency when power is applied, which makes their reliability non-negotiable in any system where timing drift has real consequences. They come in 5-volt, 3.3-volt, and other versions, though 3.3 volts seems to be the most available right now. A package around 5mm × 7mm is common, though most will vary by 1mm in either dimension. We use oscillators for the FPGA on the Logic Sniffer and Dangerous DSO, and there is also an oscillator footprint on the CPLD breakout boards.
This is meant as a summary of the parts we use, not an essay on clocks. Please fill in the gaps and share your experience in the comments.

Two sites about different PCB manufacturing processes:
Via the contact form.

The UK based crew from Batsocks develops and sells open source kits including breadboard related projects. We found a project they call the Tellymate which looks like a simple and easy way to provide plug-in video text output to any MCU project using just an ATmega8 and a handful of passive components.
TellyMate is a ‘terminal display’ device that takes serial data and outputs text to a TV screen. We’ve (primarily) designed it to perform as a display/debug device for other electronics projects. In that respect it performs a similar function to a ‘LCD + serial backpack’ that we use, but with more characters.
* Input: RS232 Serial data (autobauding)
* Output: Composite video (PAL or NTSC)The aim is to keep the hardware as simple as possible – an AVRMega8 and a 16Mhz crystal. The software should allow the display to be controlled via simple control codes. The output signal shouldn’t be interrupted in any way whilst receiving or processing input.
Batsocks has completely documented this open source project, which they also have available in kit form. Visit their website for complete information including design details, schematic and source code.

IR Toy firmware v20 is nearly ready for release. This version uses the new open source USB stack written by JTR and Honken.
The transmit, and receive functions have been completely reworked. The transmitter can handle 1000s of bytes of test signals without a glitch thanks to the new USB double-buffer.
There’s only one bug left before a release candidate is ready. Transmit data in multiples of 8 bytes crashes the IR Toy on our test setup. The first time it works, the second time the test hangs trying to open the serial port. Packet sizes not divisible by 8 work perfectly every time.
We could use your help testing the bug on different computers. There’s a package in the forum with everything you need to install the test firmware and verify the multiple of 8 bug. Please report your findings in the comments or the forum.
Primary tests:
Secondary tests:
Firmware v20 is otherwise working well, and should work (untested!) with the WinLIRC plugin, as long as transmit data is not on an 8byte boundary

Damon Billian writes: Sorry about the service issues today in Amsterdam. A full explanation from our CEO is below:
We had problems in our Amsterdam datacenter last night which lead to a period of time where traffic through that datacenter was resulting in 502 errors. These error pages were white and displayed a “cloudflare-nginx” footer. Unlike error pages that show our logo, these errors indicate that something has gone wrong in our internal systems. This is an explanation of what we know went wrong and what we’ve done to resolve it.

orcinus documented the Chronoduino:
It’s a wiki with all the relevant info and data concerning Chronoduino, including the EAGLE files and all the datasheets. The software section is still missing, but (current) hardware should be all there.
I’ve also finished revision 0.3 of the main board, containing a bunch of power supply changes, and sent the files off for fabrication. Rev. 0.3 should be able to draw power from the battery, micro USB, the serial TTL header or the SPI header, whichever of these is connected. I’ve also added a tiny charging status LED (since the charging IC supports it anyway and there was space), fixed the useless debug LED, ditched the JST connector and reshaped the battery connector pads so either the wires can be soldered to them directly, or a right-angle SMD 2-pin header, and did a few other changes that escape me right now.

George writes:
I’m of the understanding that you give away free PCBs to “dedicated developers”. I was curious how you determined what a dedicated developer was, as opposed to somebody that was just trying to get one from you to build. If you could let me know, I would appreciate it.
A dedicated developer is anyone willing to get the parts and build the board.
Most free PCBs are never built. There’s nothing wrong with that. We don’t mind if you never get around to building a free PCB. It’s nice just to get the name out there.
Active developers get a new board every time they finish a project. It’s nice to get design feedback, and there’s a growing base of committed developers who like to build in-development project.
People line up for the free PCB giveaways, but it’s rare that someone takes the time to write and ask for a code. It’s so rare that we figure if they took the time to write, it’s worth sending a PCB. Though due to this post, the bar just got substantially higher.
We’ll answer any questions about the Free PCB drawer and PCB giveaways in the comments.
Via the contact form.

exapod made a TV B Gone firmware for the Infrared Toy using a list of European TV POWER OFF codes. Grab the firmware in the forum:
i controlled all the function with the mplab sim and now it works, it turns off the european television.
I attached the code. Thanks ian for the suggestion.
Now i’m working on a smaller and powerful version.
Get an IR Toy v2 for $22.05, including world wide shipping.

Codeacademy provides an interesting way for beginners to learn Javascript coding. While not directly applicable to MCU programming, it’s sites like these that expose new hobbyists to simple programming concepts. Once picqued, this curiosity about programming can lead to more exploration of coding with MCUs.
Via Adafruit.

Every Tuesday we give away two coupons for the free PCB drawer via Twitter. This post was announced on Twitter, and in 24 hours we’ll send coupon codes to two random retweeters.
What do you think of the selection method? After a lot of feedback we decided to try random selection to give more people a shot at a PCB.
Don’t forget there’s free PCBs three times a every week:
Continue reading “#FreePCB via Twitter to 2 random RTs. Check the new deal”

A product comparison from the forum:
I recently compared two similar 3V -> 5V boost circuits, the Sparkfun #08999 5V out @ 100 mA (based on NCP1400) and the Pololu #798 5V out @ 200 mA (based on NCP1402).
The details are below, but the executive summary is: the Pololu 5V boost circuit module has 2x max current and it is cheaper, smaller, has lower noise, and is more efficient at every load current, as compared with the Sparkfun module.