Things Got Weird Real Fast

things got weird real fast
things got weird real fast

this, but with alternate lines from the plot file drawn with alternate pens. The original was slow because it had a point roughly every 0.1 mm, and this has been smoothed. Still took maybe 15-20 minutes to draw, though.

In the very unlikely event that you want to repair a broken handset socket on a Princess telephone …

It seems that Princess telephones — like the one I have — were notorious for having their connectors break. The connectors are made of brittle thermoset resin, and sit just where they’d hit the ground if you dropped the phone. This is definitely what happened here:

Very broken 616p modular handset connector. Pins are (l to r): Black, Green, White, Red

For the handset, you want a 616P connector. If your wall connector has gone too, you’ll need the 623P connector for that. These are fairly readily available on eBay.

These instructions really only apply to the 2702BMG model of the Princess phone. There are many variants, and the 2702BMG was one of the last Princess models made.

  1. Remove the upper body by unscrewing the two screws at each end of the base

    Undo the screws at left and right to remove the case
  2. Remove the body, and remove the keypad. This is held in by two screws, one on each side of the keypad
  3. If your phone’s anything like mine, untwist the wires inside to get the line and handset connectors separated
  4. Unhook the old connectors from the terminals, and attach the new connectors as shown:

    Handset wiring: Green → S, White & Red → R, Black → T
  5. Slot the handset modular connector into its space in the phone chassis
  6. Replace the keypad
  7. Re-route the wires so they don’t get pinched or block the handset hook, then re-attach the plastic body with the two screws.

 

You say ‘homage’, I say ripoff: cakeordeathsite’s What a Life!

So via mefi I find this: What A Life! | cakeordeathsite.

I love it when people discover this book. It’s been a minor obsession of mine for nearly 30 years. I first put it on the web in March 2000 and updated it to then-current web standards in 2003: What a Life!: an autobiography. Over the years I’ve received a bunch of interesting notes from fans and even a couple from relatives of the authors. I marked it up the old, hard way: by scanning pages then re-keying the text. OCR wasn’t that great back in the day.

So I get kind of irked that this cakeordeath fella lifts my pictures and markup wholesale. Shame he didn’t understand how to copy CSS, ‘cos his formatting comes out worse than mine:

cakeordeath’s rendering, viewed 2018-04-01 18:22:34
my rendering, viewed 2018-04-01 18:23:20

Crack open View Source on his https://cakeordeathsite.wordpress.com/2017/10/20/what-a-life/ and f’rinstance my Chapter 1, http://scruss.com/wal/chapter1.html:

mine:

<div>
<p><span class="smallcaps">I</span> was born very near the end of the
year. <img src="Images/wal009a.jpg" width="112" height="104"
alt="calendar showing 29 December" class="right" /></p> 
</div>

<p>The grange where I was born was situated in a secluded corner of
the Chiltern Hills. Rumour had it that Queen Elizabeth had slept
there.</p>

<div class="centre"><img src="Images/wal009b.jpg" width="160"
height="232" alt="doll's house" /></div>

cakeordeath’s:

<div>
<p><span class="smallcaps">I</span>&nbsp;was born very near the end of the year.<img class="right" src="https://i1.wp.com/scruss.com/wal/Images/wal009a.jpg" alt="calendar showing 29 December" width="112" height="104"></p>
</div>
<p>The grange where I was born was situated in a secluded corner of the Chiltern Hills. Rumour had it that Queen Elizabeth had slept there.</p>
<div class="centre"><img src="https://i2.wp.com/scruss.com/wal/Images/wal009b.jpg" alt="doll's house" width="160" height="232"></div>

I mean, come on … including my domain and image path scruss.com/wal in his image urls? Otherwise, it’s whitespace difference. I dunno, these kids today: lift anything without credit, so they would. Seems this dude is a semi-popular blogger, and I’d be vastly annoyed if he were getting ad revenue for this, while I did this for fun and it’s cost me to host it all these years.

There’s a further uncredited lift from Chris Mullen’s oldweb classic, Visual Telling of Stories. cakeordeath’s banner page scan is straight out of Chris’s Collage Pioneers: E.V.Lucas and George Morrow, What a Life! 1911 with the same file name. Was there credit? Was there shite

CP/M 3.1 manuals as PDF

The Unofficial CP/M Web site uses some very old file formats. As almost no-one can easily run Amí 3 to read the manuals these days, here are the CP/M 3.1 manuals from that site converted to PDF:

short sci-fi: “Mission: Survival”, by Curt Fischer – from Boy’s Life magazine, August 1988

Mission: Survival

by Curt Fischer
Illustrated by Alex Gnidziejko
from Boy’s Life, August 1988

mission survival illo by alex gnidziejko

“We need a shibboleth!”

“A what?” said Tim Donaldson, the mining foreman of Xerxes 8, a mineral-rich planet on the far side of the Milky Way.

“A Shibboleth,” repeated Harvey Wheeler. “A way to determine the identity of the enemy sooner than we do now.”

Donaldson and the rest of the group stared at him blankly. The old man, Freiberg, leaned forward on his cane, as if to speak, but then he sat back quietly. The 20 others, like Donaldson, mostly uneducated miners, began to look at the floor, not wishing to show their ignorance.

Only 13-year-old Bobby Hall, whose parents had left him with Wheeler while they visited his ill grandmother on Sagis, had the courage to ask: “How does a Shibboleth work? What’s it look like?”

Wheeler, the planet’s Intelligence Technician, smiled. He had often felt useless since coming to this planet. The mining colony put high value on muscles, not brains. Now he had a chance to show his strength. ‘A Shibboleth isn’t a physical thing,” Wheeler said, “It’s a word, a password.”

“So what kind of password?” Bobby asked. “A secret one?” “Secret passwords don’t work,” groaned Donaldson as he paced the cramped underground chamber where the final human survivors of Xerxes 8 had gathered. “You know the Ardon robotoids can tune in on all our conversations and radio communications. Our ‘secret password’ wouldn’t stay secret for 10 seconds!”

“Just a minute, Donaldson,” the elderly Freiberg spoke up. “If I remember my Bible stories correctly, a shibboleth is not that kind of password.”

“That’s right,” said Wheeler. “The term comes from the Bible, and a shibboleth isn’t secret. It just can’t be pronounced or understood by the enemy.”

Bobby beamed with curiosity. “So what’s the Bible story. Mr. Freiberg?”

Freiberg looked at Wheeler and then about the room. Everyone listened intently, knowing that the story could decide whether they lived or died.

“Well,” Freiberg began, “in the early days of the kingdom of Israel, back on Earth, a battle occurred between two tribes. But it was hard for the tribes to tell each other apart, because they looked, dressed and talked alike. Then one tribe discovered that it could identify the enemy by asking each captured member to say a certain word. You see, because a distinct sound was missing in the speech of the one tribe, its people couldn’t say certain words, like … like … shibboleth. They instead said ‘sibboleth.’”

“So you think this will work with the robotoids?” spat Donaldson. “Nonsense! The robotoids slip in among us and replace us. Like those tribes, we can’t tell them apart from us, Why? Because of their programming. They can mimic us perfectly. They could even be among us right now.”

Freiberg, the mining company’s bookkeeper, shook his finger disapprovingly. “Look, Donaldson, they haven’t beaten us until our reason gives way to fear.”

Donaldson made a vocal noise of disdain and folded his arms angrily.

“Freiberg’s right,” Wheeler said. “The robotoids can slip in and replace any of us, but as long as one of us is still human, we must struggle to survive.”

“But, Mr. Wheeler,” said Bobby, “Mr. Donaldson is right in a way too, The robotoids are programmed to be perfect. There aren’t any words in any language that they can’t say.”

Neither Wheeler nor Freiberg spoke.

“Absolutely,” Donaldson added darkly. “They know every language, every tone, every word. They even pick up slang quickly—”

“And their ability to communicate with their fellow robotoids means we can only catch ’em once,” Wheeler said sadly. “Even if we made up a word or mispronounced one, we’d only catch ’em once.”

“They have no flaws. It’s hopeless,” grumbled Donaldson.

A miner stood so quickly that his chair fell over.

“Look,” he said excitedly. “l know nothing you’re talking about! I’m not real smart. But I’m scared!”

“Me too,” cried a man behind him. “I don’t want to die! But I’ve worked with robotoids and know that they won’t give up!”

“That’s it,” Freiberg exclaimed. “They do have a flaw. Think about it. They’ve been programmed to avoid being trapped by unsolvable puzzles. But to do exactly that, they’re also been programmed to never give up in other areas—like linguistics.”

“Right,” Wheeler said brightly. Then his enthusiasm died. “But how does that help us? That’s why slang words and made-up words won’t fool them. They just add to their memory banks, searching them until the problem is solved.”

“Mr. Freiberg,” Bobby said, “what kind of unsolvable puzzle did you mean?”

“Oh, things like asking a robotoids math or philosophy questions that have no answers,” Freiberg explained. “Ask a human for the last digit of pi, and he’ll admit he can’t find it because it’s somewhere in infinity.”

“Years ago,” he continued, turning to the miners, “our soldiers could uncover a robotoid with such a question, literally make smoke come out its ears as the circuits burned up searching for the answers. Then they were reprogrammed to accept failure, so today a robotoid will laugh off such a challenge.”

Wheeler brightened. “But, as you said, they still won’t accept failure in certain areas, like language. So… we could try some other branch of linguistics, like… spelling! We can feed ’em words that have silent letters.”

“Like ‘pneumonia’ or ‘sarsaparilla’?” Bobby asked.

“As Mr. Wheeler said,” Freiberg answered, “each would work only once. We need something to make a robotoid’s ‘brain’ go into a closed loop. Something that would force it to search for an answer until it actually burned up its circuits.”

“What nonsense,” Donaldson snorted.

“How about a rhyme?” Bobby suggested.

Wheeler and Freiberg smiled.

“No, Bobby,” said Wheeler, “I’m afraid a rhyme would be a bit too simple. A robotoid would come up with countless rhymes for every word that …”

“But what if the word doesn’t have a perfect rhyme?” Bobby persisted.

Freiberg said: “What do you mean, Bobby?”

“What a bunch of hopeless fools!” Donaldson shouted. “We’re on the verge of extinction. The robotoids are picking us off one by one. They’re closing in every minute. We’re cut off from everyone else in the galaxy, and we sit here dreaming about a magic word, listening to a child.”

Freiberg inhaled deeply. “Mr. Donaldson, first of all, we are neither fools nor hopeless. We are alive, and we are thinking. That’s two advantages we have over the robotoids. It’s also the key to survival. Secondly, Bobby is in as much danger as the rest of us. That fact gives him certain rights.”

Donaldson mumbled something and moved away, but most of the miners nodded, agreeing with Freiberg.

Freiberg turned to Bobby. “What word doesn’t have a perfect rhyme?”

“Well,” Bobby began, “I’m not sure about other languages, but I remember learning that in English there’s no word that rhymes with ‘orange.’”

Wheeler rubbed his chin. “‘Orange’ as a shibboleth?” He looked at Freiberg. “Can you think of a rhyme with ‘orange’?”

“None that I can think of,” Freiberg said. “Nothing perfect anyway.”

“Can you think of one, Donaldson?” Wheeler asked, turning to face the mining foreman.

But Donaldson didn’t answer. He stood strangely erect, staring straight ahead.

Smoke was coming out of his ears.

— via Ask MetaFilter.

not-very-good MakeCode scratchpad

Update:now updated all to include the Bluetooth module so these can be uploaded to your micro:bit with the (remarkably poor) mobile app. If you don’t include the Bluetooth module (or want to use the Radio module) you lose the ability to program over the air.

Boring Blink:

Shake temperature:

Shake temperature in ˚F:

Circuit Playground Express Chord Guitar

Since there are seven touch pads on a Circuit Playground Express, that’s enough for traditional 3-chord (Ⅰ, Ⅳ, Ⅴ) songs in the keys of C, D and G. That leaves one pad extra for a Ⅵmin chord for so you can play Neutral Milk Hotel songs in G, of course.

CircuitPython source and samples: cpx-chord_guitar.zip. Alternatively, on github: v1.0 from scruss/cpx_chord_guitar

The code is really simple: poll the seven touch pads on the CPX, and if one of them is touched, play a sample and pause for a short time:

# Circuit Playground Express Chord Guitar
# scruss - 2017-12

# these libraries should be installed by default in CircuitPython
import touchio
import board
import time
import neopixel
import digitalio
import audioio

# touch pins, anticlockwise from battery connector
touch_pins= [
    touchio.TouchIn(board.A1),
    touchio.TouchIn(board.A2),
    touchio.TouchIn(board.A3),
    touchio.TouchIn(board.A4),
    touchio.TouchIn(board.A5),
    touchio.TouchIn(board.A6),
    touchio.TouchIn(board.A7)
]

# 16 kHz 16-bit mono audio files, in same order as pins
chord_files = [
    "chord-C.wav",
    "chord-D.wav",
    "chord-E.wav",
    "chord-Em.wav",
    "chord-F.wav",
    "chord-G.wav",
    "chord-A.wav"
]

# nearest pixels to touch pads
chord_pixels = [ 6, 8, 9, 0, 1, 3, 4 ]

# set up neopixel access
pixels = neopixel.NeoPixel(board.NEOPIXEL, 10, brightness=.2)
pixels.fill((0, 0, 0))
pixels.show()

# set up speaker output
speaker_enable = digitalio.DigitalInOut(board.SPEAKER_ENABLE)
speaker_enable.switch_to_output(value=True)

# poll touch pins
while True:
    for i in range(len(touch_pins)):
        # if a pin is touched
        if touch_pins[i].value:
            # set nearest pixel
            pixels[chord_pixels[i]] = (0, 0x10, 0) 
            pixels.show()
            # open and play corresponding file
            f=open(chord_files[i], "rb") 
            a = audioio.AudioOut(board.A0, f)
            a.play()
            # blank nearest pixel
            pixels[chord_pixels[i]] = (0, 0, 0) 
            pixels.show()
            # short delay to let chord sound
            # might want to try this a little shorter for faster play
            time.sleep(0.2)

This is roughly how I synthesized the samples, but I made them quieter (the MEMS speaker on the CPX went all buzzy at full volume, and not in a good way) and added a bit of reverb. Here’s the sox command from the modified script:

sox -n -r 16000 -b 16 "chord-${chord}.wav" synth 1 pl "$first" pl "$third" pl "$fifth" delay 0 .05 .1 remix - fade p 0 1 0.5 norm -5 reverb

Really, you do want to take a look at shortening the delay between the samples: you want it long enough for all of the notes of the chord to sound, but short enough that you can play faster songs. I came up with something that worked for me, kinda, and quickly; it’s worth fixing if you have the time.

Circuit Playground Express Remote-Controlled Fart Machine

I’m not proud of this, but I made it so you won’t have to:

Craig at Elmwood Electronics very kindly gave me an ADABOX 006. It’s based around Adafruit’s Circuit Playground Express which just happens to feature a small built-in speaker, IR remote control and the ability to play back audio samples. You see where this is going, don’t you?

If you must make this, the code and samples are here: circuit_playground_express-ir_remote_fartbox_unfortunately.zip. You’ll also need to install the Adafruit CircuitPython IRRemote package into the lib/ folder of your Circuit Playground Express. Point the remote at the board, and it’s left arrow to fart, right arrow to chuckle.

The package includes CC0-licensed samples downloaded from Freesound.

MQTT Talk tonight

I’m talking at the Raspberry Pi Toronto Meetup tonight, and if all goes well, the Net-Connected Cowbell will make an appearance:

My slides: MQTT.odp

Links:

Soltec HM-102S: unboxing a 30 year old multimeter

Graham Green had a stall at Make Change yesterday. Graham’s the former manager of Active Surplus, the much-missed Toronto surplus emporium. He had some military-surplus multimeters that hadn’t seen daylight since I was in school. That’s a while back: this (unfortunately) was #1 the week I left school. So I bought one of Graham’s meters just to see what was inside …

Neatly packed in mil-spec cardboard with a date code of 7/86. There’s a fair chance that Papa Don’t Preach was on the radio somewhere when this was sealed …
Inside the box, the meter’s sealed in a pouch. Mil-spec doesn’t allow anything to rattle about, after all. Unlike some surplus stuff, this looks 99.999% mouse-piss free
Under the meter was this battery pouch, which exhibited the qualities of both “crunchy” and “squishy”. Neither of these are things I look for in a battery, so these weren’t going in the meter
Battery pack dated January 1986. This isn’t going to be good.
Daylight — for the first time in 31 years! On first glance, everything looks okay, but three decades of phenolic off-gassing was much in evidence — pew!
Despite the hermetic seal, the elastic band had rotted to dry pasta consistency. Note expired band ichor on the manual cover
The test leads are still bright, shiny and very pliable. I suspect they might be silicone-encased, as PVC of this age has a habit of turning brittle (ask me about my late lamented Konix Navigators)
The meter. unpacked. A clear (if small) dial, complete with mirror scale to reduce parallax error in reading. Hidden under the frosted cover is a small “Made in Korea” mark
Handy-dandy fold-out carrying handle that also doubles as a stand
Inside the case, ancient tooling marks. The plastic is thick and seems fairly robust. The captive mounting screw was a nice touch
A very analogue meter. Lots and lots of 1% tolerance resistors on the main board, plus a great big thumbwheel potentiometer for zero adjustment. The foam battery pad up top was as good as new
Up and running: no auto-off battery saving mode here! The test lead jacks didn’t have the shrouding we’d expect these days, so you won’t be able to use newer probes without modifying them
Things I Don’t Miss from Analogue Meters, #1: setting the 0 Ω point. Expect fiddliness and drift.
The test subjects: a 3.6 V Li/SOCl₂ ½-AA NVRAM battery (new: tests at 3.68 V on an Agilent U1242B meter), a 7.5 kΩ ± 5% resistor (tests at 7.52 kΩ) and a 39 kΩ ± 10% resistor (tests at 41.3kΩ)
Battery test: the Soltec reports 3.8 V, or within 5% of expected. This is where I really miss auto ranging
Not so good is the 7.5 kΩ resistor: the Soltec reads just under 6 kΩ. Blame faulty zero setting from me, as it really is fiddly and I just set this up quickly.
The 39 kΩ resistor (which is really more like 41 kΩ) indicated 34 kΩ on the Soltec. Again, my dodgy zero set is most likely to blame, but reading this little log scale isn’t the easiest

Would I recommend the Soltec as a general purpose meter? Not really. There are more capable multimeters available for about the same price, and you don’t need to go as far as the unbelievably expensive Agilent DMM I use (or even the strictly ornamental analogue ex-Forces Bach-Simpson 635 multimeter that graces/clutters my workbench). It would need a video to show where analogue meters excel: in showing changing values and getting a rough idea of the limits. It would make a great battery tester, or — if coupled with a micro-controller with PWM or DAC ouput — part of a demo rig. If nothing else, it’s a great way to learn how to appreciate modern test gear and all it does for us.

I’m probably going to regret this, but here’s a scan of the Soltec HM-102s manual:

PDF link under image. I say I regret doing this, ‘cos every cheapo ebay seller of these things is now likely to download this and splat their own horrid watermarks over it, making the file huge and ugly. But the market’s gonna market, and I wouldn’t want to make a free manual inaccessible with DRM. By contrast, my watermark’s quite tasteful and doesn’t interfere with readability in any way …
Postscript: you think I’d just throw away that expired battery pack without peeking inside? If so, allow me to call you Wrongo McWrongison of that erroneous ilk! The ‘Hipower Super’ cells weren’t looking so super: the leaked electrolyte had dried into a gritty, stinky layer. I couldn’t even find the terminals on the 9 V battery to try and test it, so grotty was the corrosion. Amazingly, the slightly-less-nasty AA cell at the front tested at 1.52 V, almost as good as it could have been in the mid-80s. Doesn’t mean it’s not going in the HHW bin with the others, though.

The All-Seeing Googly Eyes of Lisa Frank

… or what you get if you video concentric RGB LED rings and put them out of focus.

No shortage of lens flare here

Teensy USB Keypad

in which I finally learn about Fritzing’s wire alignment facility …

I’ve had a couple of Teensy boards for a while, but a misunderstanding that they needed a load of of extra software installed (they need one thing, and it’s easy) had kept me away. They’ve got really impressive specs, and they’re especially easy to turn into USB devices like keyboards.

Super-heavy CEECO keypad

Here’s a little demo that turns a phone keypad — in my case, a ridiculously solid CEECO solid metal keypad designed for institutional use — into a simple USB keyboard. Plug it into any machine (including a Raspberry Pi) and it will be identified as a keyboard. No drivers are required.

The code is based on the standard Arduino Keypad library basic demo. That code was meant for a different keypad, so I eventually found a configuration that worked in the Sparkfun 12 button keypad datasheet. Rather than printing characters to the serial port, I used calls to Teensy’s USB Keyboard library instead.

There’s no reason why this wouldn’t work with those very cheap 4×4 button matrix keypads for Arduino too with only minor modifications. Those keypads use 8 data lines, and they’re arranged (I think) as rows 1-4 on pins 1-4 and columns 1-4 are pins 5-8.

The Teensy USB keyboard isn’t limited to sending single characters: a single button press could trigger sending a whole string. I haven’t yet thought out any major uses for this (except “Crypto!”, which is my usual idea when I have no idea what I’m doing), but you might have better plans.

*ALL* of the memory …

World domination soonish!

I’ve got a whole bunch of bytes free now I’ve upgraded my 6502 40th Anniversary Computer Badge to 32KB of RAM! I suspect I’ll end up as I usually do, Corvax-style …

Important research: was the Eudora “New Mail” chime from Ren & Stimpy’s “LOG”?

Inspired (obliquely) by this Metafilter post, I set out to answer a burning question.

LOG chime

This occurs from second 36 to second 38 of this video:

The chime when extracted without further processing, sounds like this:

(direct link: Original-Log-Commercial_The-Ren-and-Stimpy-Show.wav)

Eudora chime

I found a copy of Eudora Mail 1.44 for Windows (bundled up in an archive quaintly called “internet.zip”) here. The EUDOR144.EXE file is itself a Zip archive, and contains several files. The important one is WEUDORA.EXE (722,944 bytes; SHA256 checksum a35f2ef1e95242228381d9340fff0995f4935223f88a38b9200717107252dfb9).

This is a Windows 16 “New Executable” (NE) file, and I used panzi/mediaextract to scan and extract the RIFF/WAV data:

(direct link: WEUDORA.EXE_000a8200.wav)

They sure sound similar. But are they … the same?

Comparison

I made sure that both samples were set to the same rate, and I applied simple amplification in Audacity so that they both had a peak volume of -3 dB. Aligning the tracks as best I could, I got this:

Log audio on top, Eudora chime underneath

The Eudora sample is very slightly slower than the Log one. It might have been that the Eudora authors sampled the chimes from an analogue video tape. The match is remarkable, however, as they play together with only very slight phasing effects:

(direct link: Log_vs_Eudora-log_left-Eudora_right.wav)

Conclusion

Yes, the Eudora Mail “New Mail” chime did come from Ren & Stimpy after all.

BASIC on the 6502 badge

As if it weren’t nerdy enough, the 6502 40th Anniversary Computer Badge runs Lee Davison’s EhBASIC. There are 1024 whole bytes free for your programs, so it’s not exactly spacious. It’s got useful floating point support, though:

Yup, that’s the second most boring BASIC example program, after the quadratic root finder.

100 REM HERON ROOTS
110 EP=0.0001
120 INPUT "X";X
130 N=1:RN=X/2
140 PRINT"COUNT","ROOT","DELTA":PRINT"======","======","======"
150 DE=ABS(RN*RN-X)
160 PRINT N,RN,DE
170 RN=(RN+X/RN)/2
180 N=N+1
190 IF DE>EP THEN GOTO 150

Update: Josh got my badge working again (it wasn’t, for $reasons …) and I re-ran this code. If you try the code for X=100000 and larger, it won’t converge. You might want to add:

185 IF N>25 THEN PRINT "EPSILON TOO LARGE, EXITING":END

so that the loop will exit after 25 times. Alternatively, make the value of EP depend upon the size of X. Aren’t numerical analysis and floating point foibles fun?

Narwhals Are Helping NASA Understand Melting Ice and Rising Seas

I saw this headline, and couldn’t help myself.

(Real article: Narwhals Are Helping NASA Understand Melting Ice and Rising Seas – Bloomberg, via mylesb.)

VM-CLAP1 👏 sensor + gpiozero on Raspberry Pi

Well, that was easy!

Since the Verbal Machines VM-CLAP1 sensor is an open collector type — that is, it sinks current when triggered — it behaves like a simple button to gpiozero, the Raspberry Pi Python GPIO library. If you attach a callback function to the sensor’s when_pressed event, your Python script will call that function every time it registers a clap.

The wiring is as simple as it could be:

 VM-CLAP1: Raspberry Pi:
 ========= =============
      GND → GND
      PWR → 3V3
      OUT → GPIO 4

This example code just prints clap! when the board picks up a 👏:

#!/usr/bin/env python3
# -*- coding: utf-8 -*-

# Raspberry Pi gpiozero test for
# Verbal Machines VM-CLAP1 clap sensor
#   scruss - 2017-06
#
# Wiring:
#
#  VM-CLAP1:    Raspberry Pi:
#  =========    =============
#    GND     →   GND
#    PWR     →   3V3
#    OUT     →   GPIO 4

from gpiozero import Button
from signal import pause

def clapping():
        print("clap!")

clap = Button(4)
clap.when_pressed = clapping
pause()

This is a trivial example, but at least it shows that anything you can do with a button, you can also do with this hand-clap sensor.