@Hamster: "Seeed also have the Open Parts Library (http://www.seeedstudio.com/depot/Open-Parts-Library-p-1560.html), and a matching Eagle Library. Using these parts saves ordering 200 $0.04 SMD transistors when all I need is one."
This is a really neat & smart business model!! Some time ago I worked for an EMS provider and we faced this kind of issues.
When we designed the PCB in house, checking the already-available component stock in our warehouse was mandatory before using and ordering a new part.
But when a design came from a customer, we needed to check if we had a compatible component for every item in the BOM.
By the way, KiCAD developers have just added Eagle and PCAD design files support, but I've not tested it yet -- if I do that in the near future, I'll give you feedback.
Power up your new scope and see if the fan noise annoys you (highly dependent on your surroundings). It bothered me in my home office, but the fix is easy and the DS1052 is simple to dissemble. Lots of good advice online about the fan replacement and gives you a good excuse to peel off a void warranty sticker.
I would say it depends on what your preferred PCB supplier likes.
I use Seeed Studios, They supply all the support files required for Eagle (CAM jobs, DRCs and so on). This allows me to get correct DRCs and generate the correct output formats first time.
As a bonus Seeed also have the Open Parts Library (http://www.seeedstudio.com/depot/Open-Parts-Library-p-1560.html), and a matching Eagle Library. Using these parts saves ordering 200 $0.04 SMD transistors when all I need is one. As a bonus you to have Seeed assemble small runs of boards for you, as they have all the OPL parts on hand.
So although KiCAD's openess scores for me, I think for the low-end playing I do I'll stick with Eagle for now. Once my PCBs get bigger than 100x80 (the limit for Eagle Free) or I start working with parts from outside of the OPL then I'll reconsder, but for now I'm happy with Eagle.
When I squeezed 1080p (3x1.5Gb/s) out of a Spartan 6 I tried to see if I could swap beer for some scope time to see what it looked like. The only place in town with that sort of kit was Trimble Navigation, and they have a lot of engineers with very pricy tastes in beer.
@_hm: "Newark and Element 14 also offer very good digital storage scope at very reasonable price."
I really love hearing how we --the EE professionals-- have a growing number of COTS low-budget tools. I've focused my attention in the DS1052E only because this is the one I've chosen for filling the scoping-gap in my private laboratory... and because it's hackable ;-)
So, I'm glad to see how you and other EETimes fellows are pointing to other cheap oscilloscopes. The more the info we have, the smarter choice we'll make.
@wnatter: "What tool would you recommend for PCB design at home?"
If you plan to start a new PCB design project at home from the ground up, my advice is using KiCAD. It's free, fully open-source and works on Windows, Linux and Mac -- for more information, you can check the blog I wrote about CERN contribution to KiCAD ;-)
"A friend mentioned Upverter, but I don't know how it compares with the other tools"
Upverter is a web based PCB design tool -- you work from your web browser over Upverter servers. In addition, the Upverter commercial policy is very similar to Github one: you can work for free if your project is published online as Open Hardware, but you need to pay for a private account and a full-featured experience.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.