DS1881--Clickless Dual Digital Attenuator--Experimenter's board--Amazing IC!

 Hello again. 

In the past I've breadboarded digital pots to find in some cases they make an audible "click" when changing resistance values. 

I recently stumbled upon an IC that did away with the click--Analog Device's DS1881--dual pots, I2C, log response--everything needed for an MCU controlled audio attenuator--datasheet here.

Does the 1881 work as advertised? Yep.

Instead of breadboarding (I hate breadboarding!) I created a simple experimenter's board, used an Arduino UNO4 as a programmer and vibecoded test sketches to test the IC and create proofs of concept.

What I don't want....

AI was both a huge help (coding the test sketches) and also a huge burden (being out to lunch about why the device was producing audible clicks when it shouldn't).  

The circuit fragment the PCB is based upon is in the datasheet; my test PCB is pretty much a copy with some additional circuit protection.

The Kicad PCB:

For the op amps I used an MCP6004--DIP version because I had a whole tube of DIP 6004's.  

It's a rail-to-rail quad op amp, affordable and easy to use, but can only withstand 6VDC max at its rails or the IC gets fried. 

Good choice for this application, the 6004 buffers the incoming signal (I added shottkey diodes as well).

Since I had an extra op amp stage I inverted and cap coupled one of the outputs, because, why not?

Power can be from pads or from a Eurorack style power header.  For the 12V to 5V conversion, I added both a 7805 (I had a lot) and a LP2895.  If you build this board, use one regulator or the other--don't use both!

USELESS BUILD PHOTOS

As always, happiness is new PCB's from this blog's patient sponsor, PCBWAY.

I used both THT and SMD for the board.  Strange, I know, but, what do you want for $5USD.  Grab the Kicad files (here) and modify away if you want....MIT license, baby!

I have started to build a bit, power up, and see if there is a short.  Then build more.  

Getting the address, I have an original UNOR3 for that.  Default with A0-1-2 pins grounded is indeed 0x28

For the firmware upload I used a new Arduino R4--worked great for loading I2C into the test board quickly, and seeing serial output without a lot of hassle.

"seems working"--used a siglent function generator for the test waves (4V P/P, 2V DC offset) and a connector to the project here to hear output.

THE SKETCHES

Get them from Github: here.  

AD's I2C implementation for the DS1881 is wonderfully simple; I vibecoded then debugged and tweaked what the bot conjured.  

For each of these .ino files you may need to drag the .ino into a new folder you create with the same name as its ino file. 

These sketches require the serial monitor tool in Arduino IDE.

Simple stuff--take a look, experiment with different values, and have fun:

DS1881-diag.ino  Run this first, the basic g/no go tool for the experimenter's board. Reveals if I2C can reach the DS1881, the IC's I2C address, can the IC do basic reads and writes. Nothing for you to enter into serial monitor; the serial monitor's output tells you what you need to know.

DS1881-enter-db-attenuation-value.ino  Entering a value 0 to 64 in serial monitor attenates 0 and 1 channels by said DB.

DS1886-30ms-steps-100ms-hold.ino  Rapid attenation followed by gain increase.  So, a sort of poor man's tremelo. I wanted to see if fast fades caused clicking--so far, no. Mess with the ms values to experiment with how fast I2C can control the pots.

DS1886-choose-zero-cross.ino The DS1881 fades inputs to -64db then the signal is gradually brought back to unity. Enter z into the serial terminal to toggle on and off the declicking algo inside the chip.  This will give you a rough idea of how the DS1881 will sound vs. a digital pot that does not have a zero cross detection algorithm built in. 

 

HOW DID IT SOUND?

At first--crappy.....no matter what I did I heard clicks. Hello? The whole idea: no clicks.  

Plugging everything into Claude, using every prompt I could think of, and adding the DS1881 datasheet to Claude.ai's whatever, the chatbot seemed to indicate that the audible clicks were just the way the DS1881 is and, like a bad marriage, I should just live with it.  

Did that sound right?

I took the project to my local group meetup--everyone meant well as always, but as far as a fix, no one (including me) had any idea why the DS1881 was clicking no matter what, I just got puzzled looks.  

Driving home it dawned on me--what if I set up the input signal wrong? Went back to the bench and sure enough, I was not adding a 2V offset to the test input signal, which was confusing the hell out of the DS1881 IC. The IC's datasheet was clear that a DC offset was needed for the input signal.

I added the DC offset and the IC worked--absolutely perfectly--immediately--no click, nice smooth fades, quick moves from -6 db to -60 db to whatever than back to mute--all without any clicks. Very musical. This is a really cool chip!

THE SHAMELESS PROMO

Quick word from this blog's sponsor! Once you have your design working in Falstad, run, don't want to PCBWAY and get some prototype PCB's made....They also do great work with 3D printing, assembly and can even act as your OEM. You can support this blog by checking them out--link here as well as the PCBWAY community (link here)

WHAT'S NEXT?

I am having a second experimenter's board fabricated. It will allow the DS1881's two channels to be used as a rheostat. I am not sure what I'd use that for, or even if it will work at all, but that's the great thing about DiWHY in an era where small quantities of PCB's are available quickly and for little money; try it out, see what happens. 

Assuming I can get something useful out of this 2nd revision: whatever happens will show up in a future post.  See ya next time.

 

No IC's allowed, part II: determining active vs. saturation state in BJT transistors

Back for more discrete transistor design punishment!  

Quick one this time.

Last time I discussed BJT basics...if you are a "BJT cookbook" tech as I am or was--find a bipolar junction transistor circuit fragment, put it in your design, and hope it works--you might want to skim the last post before reading this one.

Maybe simulate it using Falstad?

If you are a BJT superstar--you taught 1970's electronics at a community college and already know all this--by all means skip this post and instead watch the video here.

but really? this is all for me.

SATURATED VS. ACTIVE

You can get Falstad simulations for these "No IC" posts from github, here.

So...how do you figure out if a transistor is in its active or saturation region?  Should be easy, but this one drove me nuts...

Cheat code: Plug your BJT circuit fragment into Falstad, hover over the transistor and see what it says?  

Nope, too easy. 

We start by guessing we are in active region, and go with these assumptions:

• B-C junction is forward biased; its voltage drop across B and C is .7V
• current at emitter and current at collector are the same
• B-C is forward biased; B-E is reverse biased.(normal situation for active region)

Let's do some simple alegbra and use ohm's law to see what's really going on.

• Base is 2V less .7V to ground, so the voltage at the BJT emitter is 1.3V.  
• Using ohm's law: current at BJT emitter junction is 1.3/1000 or 1.3mA  
• Assuming active region for the transistor, Ie and Ic are about the same, so let's assume Ic is also 1.3mA
• Again using ohm's law, for emitter to be at 1.3mA, the voltage drop across a 10k resistor would need to be 13V
• But, the the collector power is only 5V!!
• The transistor lowers its Ve to Vc resistance as much as it can to satisfy the need to satify the 13V drop
• But fails--even if C to E is a short, the transistor can't make the Vc junction 13V relative to ground.
• Transistor is saturated; B-C and B-E are both forward biased; E to C works a lot like a short circuit.

Let's try again:

• BJT collector current is 1.3mA; that hasn't changed.
• Assuming active, Ic = Ie, so Ie is also 1.3mA
• 1.3mA * 1000 = 1.3V  (drop across collector resistor)
• 5V - 1.3V is 3.7V0--that's the collector voltage
• B-C is forward biased; B-E is reverse biased (see "active" assumptions above)
• Transistor is active.

OK with this framework, any simple fragment can be analyzed.

For PNP, all the same ideas, but all polarities are reversed.  

Notes for this post....

This helps explain the typical graph you see when reviewing transistor datasheets:

voltage between collector and emitter (X-axis) vs. current measured at the collector (Y-axis)

The saturation area is the vertical area shaded in blue--as described above: when the voltage from C to E is nearly zero volts, the resistance between C and E is almost zero; C to E acts like a dead short.  However, the values further to the right on the X axis result in amplification: as C-E voltage swings back and forth along the X axis, to the right of the saturation region, current swings up and down along the Y axis, since C to E resistance is changing.  The horizontal area shaded blue results from B to E not being forward biased--transistor is cutoff; C to E acts like an open circuit.

OH NO IT'S THE PROMO

Quick word from this blog's sponsor! Once you have your design working in Falstad, run, don't want to PCBWAY and get some prototype PCB's made....They also do great work with 3D printing, assembly and can even act as your OEM. You can support this blog by checking them out--link here as well as the PCBWAY community (link here)

OUTTRO

OK no more this time, it's Juneteenth, I have to get to the bench and mess around with some IC's.

No IC's Allowed!

I am retiring soon--they've put me out to pasture.  

I hate hate hate being bored so, what now?

I fired up Falstad to simulate basic electronics building blocks using only transistors, caps, inductors, resistors, and diodes--NO IC's!!! 

A video game!!!!

Rules:

• (already stated)--No simulated IC's--even if the simulator has 'em, I can't use 'em.
• FETS/MOSFETS, maybe? Try using BJT's instead....
• No finding fragments online then copying them into the sim...which "works", but is way too easy, and I learn almost nothing. 
• Goal: understand "discrete" electronics well enough to look at old audio schematics (e.g.: Aries synths here--cool) and have a decent idea of how these OG/transistorized/very-few-IC designs from way back work.

I discovered that my ability to conjure anything without IC's--like, how to make a comparator without using an opamp--sucked.    

FALSTAD

Why breadboard when I can do it behind glass.

I've tried many simulators--Kicad's, Everycircuit, others, and keep coming back to my local installation of Falstad. 

Falstad and my brain get along; I get instant gratification, seeing voltages change in real time, seeing current flow like the ghosts in "Pacman".  I can spin up virtual scopes, I change values while the sim is running to see what happends and a lot more. 

Best of all--it's free! 

Get an offline version of Falstad here; web version here.

I put my Falstad exports for this post on github (they are text files...so, file > open the txt files in Falstad to run the simulations). Repo is here.

AI (OF COURSE)

Since no one thinks on his or her own any longer I uploaded the Falstad exports into Gemini, Claude etc. to help me understand how the sims work, find mistakes, help with analysis and the rest. 

These LLM's (I didn't try copilot because I frigging HATE copilot) both say they support analysis using Falstad exports--didn't know that!.

But! Claude.ai Opus was terrible with all things falstaff, making all sorts of bizarre and inexplicable mistakes. Gemini Pro worked a lot better. Of course in 2 weeks this could be completely flipped.

EG: I asked Claude to vibe code a text file to create a current mirror I could upload into Falstad. Here's what it came up with. Righto!

BJT LOGIC GATES

Getting started--a warm up.

Even with my limited knowledge of BJT's I could figure and AND, OR, NAND, and so on. pretty easy. 

NOR gate, get it here. Fake LED demonstrates logic out.

Moving on....

BJT TRANSISTOR BASICS

I know this component, right? BJT transistors are easy right? Nope. I created a simple simulation complete with fake current and voltage meters: 

 Sim here; check out a great "Kevin's Cave"
newbie video BJT tutorial starting here.

Which led me to:

TRANSISTOR FU 

Looking at the NPN transistor modeled in Falstad--messing around for a few hours--throwing a screenshot into claude.ai when I got stuck--what (I think) I know now:

• In general, the voltage drop between base and emitter determines C to E behavior. 
• It's not voltage relative to ground found at the the BJT's base that determines this. It's the voltage drop between B and E.
• C to E can act like a variable resistor. When doing so the transistor is said to be in "active" mode.
• While in active mode the B to E current is multiplied the transistor's "beta" (in Falstad: 100 by default)
•  this allows for amplication
• This beta multiplier is also called "Hfe" to keep things confusing.
• But--the transistor can only alter the resistance between C and E so much.  
• At some point the resistance is as low as the transistor can make it, at which point the transistor is "saturated."  
• When the transistor is saturated C to E behaves like a small resistor--maybe 30-50-90 ohms.  In this case additional base to emitter current won't change the C to E behavior; the transistor is maxed out. Saturation means the Vc to Ve voltage is as small as it can be, usually around .2V.  Increasing base current will no longer make this voltage decrease. Good video about this here.
• Cheat code: Active vs. saturated, for the default NPN transistor modeled in Falstad, can be boiled down to this: if voltage between collector and emitter is greater than about 200mV the transistor will be active; if it's less than 200mV it will be saturated.
• If limited or no current flows between B and E, you can end up with no current flowing between E and C. Transistor is in "cutoff" mode and the collector is "high-z", as if the collector is an open circuit.
• Falstad has a useful feature: if you hover over a transistor, in the bottom right corner of the app you can see things like B to C voltage, C to E voltage, and its mode (saturated vs. active vs. cutoff).
• If BJT is saturated, current flow in falstad is shown flowing C to E, as expected. But I've seen current flow from B to C while in "active" mode as well, but sometimes not, which I found confusing.  
• A BJT transistor is analogous to a valve--it can't generate current, only let various amounts of it (or none) pass through. Basic concept, but this escaped me at times.
• For amplification, we usually work in the BJT's "active" range.  
• For logic and switching, work in the BJT's "saturation" and "cutoff"modes.
• You program what you want the BJT to do by surrounding it with voltage sources, current sources, resistors, diodes. The trick is getting the surrounding components right 
• To get it right, you have to use math (basic algebra, mostly). Sorry.
• Transistor prose and videos can be a flurry of capital letters and italized subscripts. Get used to it:

1. Gm ("transconductance") a transistor's ability to see a change in B-E voltage drop and turn it into a change in C-E current.  
2. Ic, Ie, Ib: current at collector, emitter, base
3. IcRc represents the voltage drop across a resistor tied to the collector, since V=IR....same idea for IbRb, IeRe.
4. Vce is the voltage drop from collector to emitter
5. Vbe is the voltage drop from base to emitter
6. Etc.  
7. Video series that I found helpful--kickoff video links : Vocademy

• Falstad is a great place to mess around with values and see what happens.
• See more about saturation vs. active in the post here.

DIODE BASED COMPARATOR

On to the next sim.

The idea of using diodes to choose the greater of 2 voltage sources was new to me--a nice hack.  I tried building this comparator using a long tailed pair but for me a 2 diode + 1 transistor solution worked better....Sim here.

CURRENT MIRROR

Upper 2 transistors form a "long-tailed pair" while 2 lower are a current mirror--left lower is the reference transistor.

I see these everywhere in IC designs, but, why? How? After screwing around with simulations: By tying B and C together on the lower left transistor (the "reference"): assuming lower transistors are in their active regions, C to E in the lower right transistor (the "mirror") acts like a variable resistor, its resistance increasing and decreasing with collector voltage. This rock-solid current sink is needed to make sure the balanced pair actually balances.

If the right lower transistor was replaced with a normal resistor, the voltage drops seen across the balanced transistors (upper ones) would impact overall gain, leading to distortion.   

Sim is here.

LC OSCILLATOR (SINE, SQUARE, ETC)

I've been doing the DiWHY thing off an on for 25+ years and, outside of linear power supplies, have never used an inductor in a single design of my own. 

After trying unsuccessfully to come up with a transistor/cap only solution for an oscillator, I remembered that inductors pass DC and not AC, while caps pass AC and not DC.  If I put them in parallel, they might fight each other?  Yep. That's the thing about simulations--try weasel, try squirrel.  Nothing is going to smoke. Something eventually will work. I messed around with the parts until I found something that worked. Now I need to figure out the math right? Nope.

I even threw in a FET buffer.  Buffers in general have proven tricky in my discrete design attempts. Just throw in a 741 right? Not in this post....Oscillator simulation is here.

FRENCH, GERMAN, AMERICAN

To make discrete circuits useful some math and science is needed (sorry, Arduinoheads). When transistor analysis is discussed, the dudes below are discussed. so far the math I've seen is algebra only. 

KIRCHHOFF: "The man with a redundant H". Russian, moved to Germany. Hell of a guy, discovered all sorts of things, including cesium. Big ideas: Kirchhoff Voltage law: the sum of all voltages in a closed-loop circuit is always 0. Example in a transistor analysis video here: go to about 4:11. Kirchhoff Current law: currents in closed-loop circuits don't magically vanish; for example, current at transistor C is a sum of currents B > E plus C > E.

THEVENIN: French. You can take a complex circuit and reduce it to a single power source and a single load resistor.  You know the blocks in schematics labeled "load"? That's the "Thevenin Equivalent".  How-to video for computing thevenin equivalent is here. I'm a reductionist, maybe he was too.

MILLER: Miller was American, discovered the capacitor hoo-ha using tubes (not transistors) and worked for RCA, among other places. The Miller Effect: in AC circuits the transistor has parasitic capacitance which impacts frequency response. Good video here. Another video (Zappa backing track? Sounds like it!) here.

OP AMP

This one blew chunks--hard!! I remember I have to combine a long tailed pair, a gain stage, and a class B amp, but that's all I recall. So far, no love, I have made lots of BJT matched pair thingys that don't work.....I am really REALLY tempted to cheat, since a simulated op amp using BJT's would create a bullet-proof buffer, much needed!  

And I figure a bunch of folks smarter than me have a simple low parts count design already posted online. But--So far, no love!  

THE SHAMELESS PROMO

Indeed....Once you have your sim go to PCBWAY and get some PCB's made....check out their online community.  They also do beautiful work with 3D printing, assembly and can even act as your OEM. I got in the shameless promo in. Go A's!!!

THE-THE-THE THAT'S ALL FOLKS!

enough for one week. Until next time: discrete-ion advised.     

One-Chip ADSR using the ATTINY1616

Readers: If you'd like to build the ADSR experimenter's board featured in this post, please go to PCBWAY's Community pages--gerber file; KiCAD 10 project/pcb/schematic/library files, Arduino .INO file, modified .h and .cpp helper files, B.O.M., and more, are here.  

You can also help out this blog immensely by checking out PCBWAY using the link here. Thanks!

==============

This one started when DIY rockstar--this guy's kung fu is the best--TJimmyChonga--emailed me about an earlevel C++ library that abstracts analog synthesizer ADSR functionality into a compact C++ library--articles documenting the library begin here; zip of the CPP and H files are here.

Experimenter's PCB for the earlevel ADSR library, and probably a lot more AudioDiWHY fun. 

Looking over the code, I guessed it might be easy to use an ATTINY1616 --that's a <$1USB MCU, folks--to create an entire ADSR since the ATTINY1616 has ample ADC's and a single reliable 8-bit DAC built-in.  

Designed it, gerbered it, got it fabbed, built it. Fast, fast, fast...Good news--yep, it worked.

THE DESIGN

Instead of breadboarding, which drives me nuts, I drew up a 99 x 99 mm PCB using Kicad10.  

I added 3.5mm input and output jacks; a shottky diode clamp for the trigger input (so a 10V or 12V gate signal didn't blow up the input pin on the MCU) and a few pots....I buffered the output using a DIP TL071....simple stuff. 

....for future expansion, remaining GPIO was brought out to JST connectors....

As usual, a 3-pin JST in series with a 470 ohm resistor was used UPDI programming.

I included a 7805 regulator, although I could have gotten 5v from the Euro power cable, but hey, why bother.

I chose mostly thru-hole since I have tons of THT in my junk box.

Happiness is bubblewrapped new PCB's from this blog's patient sponsor, PCBWAY, where ten 2-sided PCB's less than 100mm x 100mm can still be purchased for $5USD.  

THIS BLOG'S SPONSOR

The gerber got sent off to this blog's trusty sponsor, PCBWAY and came back with alacrity.  

The shameless plug:

....why bother breadboarding when you can throw your ideas into Kicad, ship them off to PCBWAY and get lotsa boards back to mess around with. If they don't work: don't swear, don't stomp around, don't cry....e-waste them in an environmentally friendly way and try again. What's your time worth? 

Prototyping with PCB's is faster and a heck of a lot more fun than breadboarding....wait, there's more! Kicad experts: check out PCBWAY's 2026 Kicad Design Contest--nice schwag and cash prizes may be yours.

Back to it....

PROOF OF CONCEPT

Since nobody codes any more I used Claude Code to put together the Arduino sketch for a 3 pot ADSR proof of concept--Attack, Sustain and Decay/Release--some bugs at first but easily fixed. 

The output worked surprisingly well--nice analog-sounding log response....I thought 8 bits wasn't going to get it done and the output would be "stair stepped" but it was fine.

For the PCB, there were a couple of stupid mistakes but overall this one was easy--maybe too easy.  

Testing the POC board with a dual MS20 filter (MS20 VCF post here). Overall the Proof of Concept single chip ADSR, using the C++ Earlevel library, worked a lot better than expected.

OUTRO

In general, all heavy lifting was done with the ATTINY1616--if I hard coded the ADSR values, jammed 5V from my bench supply into the MCU, and didn't care about input or output levels, this was literally a one-chip/$1USD design....if there's a lower parts count ADSR out there, I haven't seen it.

OK, whatever....the question, what to do next.  

The fact that the entire EG lives on a single inexpensive MCU means I can sprinkle the damn things all over--add it to a filter, add it to a VCA, add it to a mixer.  

But I also envision adding various logic outputs to this--end of attack, end of release--and using them to trigger other events.  

Also it should be easy to modify the DAC to produce linear outputs, log outputs, or whatever you want in-between.

Or, I could go full Behringer and rip off + remarket someone else's function generator design--how about The Intelligel Quadra (4 AR's with clever I/O) with expander, allowing VC of attack and decay, this module sold for something like $300 before being discontinued? I figure I could recreate it using a 4x ATTINY's for something like $30USD?  And add sustain to each of the 4 AR's?   

Make it itty bitty/Eurorack so only folks with tiny little fingers can use it.  

Finally, I'd need to say it was made by "Bellinger" and call it something like "Quad Fumer"--indeed, too easy.

  

KICAD 10: Hierarchical Sheets and Blocks: Lay 'Em Out Once, Use 'Em Over and Over

Readers: today's post assumes you have a working knowledge of Kicad, an incredible open source EDA program. If not, this post might be pea soup. Newbies: watch a great Kicad tutorial here.  And--previous audioDiWHY posts focusing on Kicad are here, here, here and here. 

I have read that good engineering is modular engineering. Is good audio synthesis modular audio synthesis? 

Not sure.

Kicad--our beloved schematic capture/PCB layout/simulation software--has recently added some great features in making bits of your previous designs reusable--a huge timesaver.  

Let's go over this.

"Hierarchical Sheets"

....let you put subcircuits into other designs, treating the subcircuit as a "black box"--don't worry what's in the box, just enjoy what it can do....you expose I/O between your black box and main design using "hierarchical labels."

• Because I'm lazy, I will abbreviate hierarchical sheets going forward as "HS"
• Create a new project, this will contain your HS.
• In the schematic (.sch file), put whatever components you want in your HS--you are creating a normal schematic at this point.
• For I/O you need to share outside your HS issue the command: "Place" > "add hierarchical labels"

• Save the schematic.

Next--Create a new parent project; in the next few steps, we are going to embed the "HS" content into it.

• In the parent's .sch file, click on this icon on the right:
  
  
  
• using this tool, draw a box inside the parent schematic. 
• You will see a blue box...this represents the HS:

• A properties dialog appears (if you don't see it, select the "Untitled_Sheet" and then tap the letter "e".)
• Give the HS a name
•  in "sheetfile" click on the folder icon and navigate to the kicad_sch file you created initially, the one that contains your HS.

• At this point you might see dialogs about using relative filenames and something about database tables being messed up (?).  
• Pretend you didn't see any of that and click OK twice.
• Still in the parent schematic, click on this icon on the right:
  
  
  
• Click on the HS box; the I/O pins ("hierarchical labels") created in the the source .sch file appear in the parent schematic--they are placed sequentially
• Create the rest of the parent schematic and wire it to your HS.

In the screenshot below I ran a DC simulation on a parent schematic containing a hierarchical sheet; the HS contained a single 100k resistor with "in" and "out" labels. 

The simulated DC voltages in dark red show that this works--the 100K resistor in the HS is hidden from view but is part of the simualtion.

This is an OC simulation--DC values--not to be confused with "OCD"

 

DESIGN BLOCKS

....allow you to create a subcircuit, save it in its own library, and import it into future designs. 

This feature showed up in Kicad 9 (See the video here). 

With Kicad 10, you can put schematic symbols/wires and PCB traces into a single design block.

And--again, due to indolence/laziness, I will call "design blocks" going forward "blocks". Have a nice day.  

Organizing blocks: Blocks are organized into libraries, same idea as Kicad symbols.  Each block is a folder containing a json description file and file(s) for the .sch and/or .pcb components.  

For both the people out there who are interested--get a zip of my custom blocks from Github, here.

Creating a block: select some or all of your design, then right click on "blocks" 

From the drop down, choose "Save Selection as Design Block"

But! Be careful about "hide library tree", if you click that, the entire block's user interface section disappears. This threw me at first. I had to go back to view > panels > design blocks to make it reappear.  

 

Tidbit: By clicking "New Library" you can also choose if you want the block to be visible in the current project only or globally (all projects); the default is global:

Viewing existing Blocks: from the schematic editor View > panels > make sure "design blocks" is checked.... you see something like this (your block names will be different....)

Using existing blocks: Double left click on a block, drag it into your schematic, creating a group of components and wires.

Editing blocks:

• Select either PCB 

• Right clock inside the block and say Grouping > ungroup

• Edit.

Before

After: now it's editable components like everything else in the schematic.

NOW: A WORD FROM THIS BLOG'S SPONSOR

OK, you just created something awesome using these new Kicad 10 tools and need to get some PCB's, then get them assembled.

For this, check out this blog's sponsor, PCBWAY, who can fabricate the PCB's, do the component assembly, and then, do everything else.

In addition to top shelf PCB fabrication they also do fantastic work with 3D printing, injection molding, and much more. 

And!!! Kicad Mavens (you must be if you've made it this far?): run, don't walk, and submit your Kicad masterpiece to PCBWAY'S Kicad PCB Design Contest--winners get cash and/or RPi goodies. Check out the contest here.

As always--you can help this blog by checking out the PCBWAY site.  Thank you!

SCHEMATICS AND FOOTPRINTS/TRACES IN ONE BLOCK--New to Kicad 10--How To Do This

Super useful--capture the schematic and layout of a subcircuit in a single block. However--work slowly and carefully. This feature is one of those "miss any step and the whole damn thing won't work" situation.  

The steps:

Creating the combo block--start with the schematic:

• Create a schematic subcircuit with all the symbols, wires and values you want in your block.
• Tool > create associations  
• Make sure everything is OK, that all symbols have associated footprints and so on.
• Create a block--for this let's call it europower w traces

Next, create the associated traces.

• Go to PCB and update the PCB from footprint
• The footprint appears
• Draw in all traces you want to include in the combo block
• Save the selected footprint and traces (you must select both!) as a block  (right click on block > save selection as block)
• For the block name, type in the exact same name you used for the schematic block--this is case sensitive: in this case, "europower w traces"
• Kicad 10 will ask "overwrite block"?  Say YES

To use it:

• In your schematic, pick the block europower w traces and put it on the schematic
• In your PCB, pick the same block europower w traces and put it on the pcb
• Hit F8.  
• If all goes well you will see a footprint with traces appear--the PCB and the schematic are "synced"--it's all wired up.
• If you messed up, a new footprint will appear with no traces. Fiddlesticks! Try again, make sure to follow each step.
• You can now grouping > ungroup your Schematic or PCB block and change things.  

Tidbit: I noticed when upgrading Kicad 9 > 10 I had to set the global blocks path manually.  Preferences > Manage Design Block libraries > global libraries:

For Kicad 10.0.1, I had to set the Nickname, the "Library Path" (where the global block libraries are stored--the local location might vary if you are using a cloud repo on different hosts), and the Library Format (pulldown to "Kicad") by hand for this to work. Not sure why this didn't come over with the rest of my preferences.  

OUTTRO

Think "She's so Heavy": another brilliant John Lennon time signature change, with rapid master tape cut.