Tools for Hardware Developers

Here is my list of tools I use:

Software:

  • AutoHotKey: provides support for keyboard shortcuts for faster access to applications and typing symbols
  • Inkscape: very handy to create illustrations and also taking PDF files apart e.g. schematic files or PCB layout files
  • Word: write your specifications
  • Excel: calculation tool for dimensioning of circuits, analysis tool for test results
  • SMath Studio/(Mathcad): write your calculations in real formulas and see what gets calculated (cleaner than using Excel)
  • Layout/Schematic viewer: in my company there is a home-grown tool that combines schematic, PCB layout, parts list, signal list and test point location and BOM synchronisation into a single, easy-to-use tool. If your desing tool does provide this: lucky one. 🙂
    Kicad has a Plugin that provides this functionality: InteractiveHtmlBom
  • Test automation tool: a tool that is used to create test scenarios that are to be performed by the device under test. creates test steps, loops, sets test parameters and generates test reports from the gained results. can control not only the hardware under test but also remotely controllable test equipment like power supplies, multimeters, frequency generators and so on.
  • FreeCAD: view step files, make mechanical mockups
  • Programming Software for your programmable devices
  • Data Loggers:
    • monitors and stores your data traffic of your device under test
    • monitors and stores measurements from your test equipment
  • HxD: Hexeditor, for comparing data dumps from your system
  • Version control (several different) for:
    • Assembly versions: keeps track of each assembly version BOM changes, firmware versions (where applicable), modifications
    • Documents: keeps track of each edit of your specifications and test reports or datasheets
    • Firmware: keeps track of your changes to your source files
    • EDA: keeps track of your changes to your schematic and PCB design
    • BOM: keeps track of your BOM changes between different assembly versions
    • Test Skripts: when did you change some parameter or sequence for your qualification test setup
  • Material database: tracks your material including all PCB versions, components, mechanical parts, auxilary material. provides prices, stock, description, datasheet, order information, material status and preferably links to your Knowledge Database where necessary.
  • Bug Tracker: keeps track of your defects and documents your solutions
  • Knowledge Database (e.g. Wiki): helps you to remember things you researched once
    • some edge behaviour of some component
    • your assessment of some errata for your controller

Hardware:

Preferably all equipment has an interface that can be accessed via open, documented protocols. This makes test automation easy e.g. via python scripts.

Test Equipment:

  • Oscilloscope: 4 channels recommended, minimum bandwidth 350 MHz, test probes with minimum 500 MHz bandwidth. Sample rate at least 10 times of bandwidth for accurate measurements.
  • Multimeter: (bench or handhold) at least 0.5 % accuracy required, 4 digits readout.
  • Bench power supply: with at least two seperate outputs >20 V and ≥ 3 A output capability. can preferably controlled remotely for test automation.
  • Measurement data logger
  • programming adapters for your programmable devices
  • communication adapters for connection to your test equipment/DUT

Toolbox:

  • Soldering station: Minimum power recommended: 75 W for fast heatup. My preferred supplier: JBC, for hobbyists Aifen provides similar specs
  • side cutter
  • pliers
  • pincette
  • set of small screwdrivers (flathead, Philips, torx, hex)
  • set of normal size screwdrivers (all of the above standards + Pozidriv)
  • power drill
  • caliper
  • band measure
  • ruler

Tips for Presentations

Today (2018-04-27) I found these tips on Twitter by @heydebigale, they seem like a good collection:

  • Keep color schemes simple. Try to stick to no more than 3 colors beyond black & white.
    • If using 3 colors, try using the 60/30/10 rule for percentages of use of each color. This will allow color to emphasize.
  • Consider using contrasting colors to emphasize difference & harmonious colors to illustrate unifying concepts.
  • Consider color vision deficiency. Use different value (not just hue) to be sure that your text is easy to read.
  • Never use color alone to convey your meaning.
  • For screen layout, use the rule of thirds.
    • Split the screen into a 3×3 grid.
    • Important elements should be placed at 1 or more of intersecting points.
  • Always create a strong focal point.
  • Avoid holes in layout and move white space to the outside boarder.
    • LESS IS MORE.
  • When considering typography and text, use text size for hierarchy/importance.
    • Avoid using more than three font sizes.
  • Text should not be more than about 1/4 to 1/3 of the real estate on the screen.

Another couple of interesting rules:

  • Mayer’s Multimedia Principle: people learn better from words paired with pictures than words alone.
  • Mayer’s Modality Principle: People learn better from graphics with narrations than from graphics with on screen text.

Schematic Symbols that make sense

Some people draw their schematic symbols strait according to the pin arrangement of the component.
For explanation they say this prevents confusion during layout when signals are on a different location then in the schematic.
But the schematic is the “Source code” for the layout design. It needs to be drawn in a way to be read fast and unambiguously to enable that mistakes in connections can be spotted easily. For this it helps to prevent wire crossings where ever possible.
Continue reading Schematic Symbols that make sense

Template Test Report

In my day job I need to do a lot of testing during hardware development.

Over the years we developed an in my opinion quite good template for our test reports.

I simplified it to simple text format just to provide the structure and required information. Design is up to you and your corporate needs such as header, footline corporation logo, font and so on.

So, if you also feel the need to have a structured document for your hardware test reports, here you go:

Continue reading Template Test Report