All posts by Karl

Arduino, Electronics, Hardware, Programming

The Fridge Door is Open

29th August 2018 Karl

My fridge door tends to rebound when closed staying open a smidgen and letting all the cold out. Rather than just checking that the door is properly shut, I thought it about time to have a microcontroller make a noise when the door has been left open too long.

This circuit uses an Arduino compatible Teensy LC for all the work, it has a phototransistor to sense the state of the fridge door light, a couple of LED’s one to indicate the power and another that comes on when the door is open. There is also Piezo buzzer to make an annoying noise after forty five seconds of door open time. The unit runs of a 3.7v rechargeable Lithium-ion battery and I have added a recharging circuit that takes power via the Teensy’s 5v USB port.

Circuitry

Note: These diagrams show 3.7v as the supply voltage. The Teensy LC can only tolerate a maximum 3.3V on the data pins, so these circuits are driven from the 3V output on the Teensy. They will all work without modification on the 5v Arduino Uno.

I have used a phototransistor to detect the fridge door light, there are two variants of this circuit light activated or dark activated, the 100k resistor can be replaced with a 100k variable if you need to adjust the sensitivity, the 330k resistor provides a weak pull-down on the output. The phototransistor is being used in switch mode to provide a logical output (rather than active mode which provides an output relative to the amount of light), so the output is connected to a digital input on the Arduino. The BC547 transistor is half of the darlington pair to provide extra gain on the output.

I chose the light activated switch, either will do but will provide different logical outputs to your controller. The circuit is enclosed in a small box inside the fridge and connected by ribbon cable to the controller, the ribbon cable is flat and does not upset the magnetic ‘seal’ on the fridge door.

To make some noise I used a piezo buzzer from an old computer, this is driven through a transistor as the Teensy does not provide enough current to drive it directly.

There is also a push button to provide a reset function if the buzzer is sounding while the door is open.

I have also added two LED’s, one to show power and anther that illuminates when the door is opened.

The final circuit if for recharging the battery, it connects to the 5V connection on the Teensy LC so charges the battery when the USB connection is in use. This has been copied from the MCP3831T datasheet.

Software

This uses an interrupt to listen for the light sensor, when the state changes, the door open pin is read to determine if the door is open or not. If it is then a timer is started, this gives you forty five seconds to complete your task before the alarm sounds. With the door closed the timer is stopped and set back to zero. If the sounder goes off while you are rummaging in the fridge the reset button can be pressed, this restarts the timer from zero again.

#define TEST_LED 13
#define FRIDGE_DOOR 6
#define DOOR_LED 8
#define POWER_LED 7
#define RESET_BTN 9
#define BUZZER 10

volatile boolean doorOpen = true;   // when the light is on
volatile boolean doorTrigger = false;
volatile unsigned long lastFridgeMillis = 0;
volatile unsigned long fridgeTimeoutMillis = 10;

boolean SerialDebug = false;
unsigned long doorOpenDelay = 45000; // 45 second timeout before buzzer sounds
unsigned long doorOpenTime = 0;
unsigned long startTime;
unsigned long previousToneMillis = 0;
unsigned long toneInterval = 20;
boolean soundTheAlarm = false;
boolean outputTone = false;
int toneMelody[5] = { 1600, 1900, 2000, 2100, 1800 };
const int toneMax = 5; 

unsigned long lastDoorOpenTime = 1;
char pout[80]; // for testing

// interrupt function
void fridgeDoor() {
  if ((millis() - lastFridgeMillis) > fridgeTimeoutMillis) {
    doorOpen = digitalRead(FRIDGE_DOOR); // goes high when dark
    lastFridgeMillis = millis();
  }
}

// see if the door is open or closed
void fridgeDoorOpen() {
  if (doorOpen == true && doorTrigger == false) {
    doorTrigger = true;
    startTime = millis();

    if (SerialDebug) {
      sprintf(pout, "door open: %d", doorOpen);
      Serial.println(pout);
    }
    digitalWrite(DOOR_LED, HIGH);
    return;
  }

  if (doorOpen == false && doorTrigger == true) {
    doorTrigger = false;

    if (SerialDebug) {
      sprintf(pout, "door closed: %d", doorOpen);
      Serial.println(pout);
    }
    startTime = 0;
    doorOpenTime = 0;
    soundTheAlarm = false;
    digitalWrite(DOOR_LED, LOW);
    return;
  }

}

// make some noise
void soundAlarm() {

  if (soundTheAlarm == false) {
    return;
  }

  int ii = 0;
  while (ii < 6) {
    if (soundTheAlarm == false) {
      break;
    }
    int i = 0;
    while (i < toneMax) {
      if (soundTheAlarm == false) {
        break;
      }

      unsigned long currentMillis = millis();
      if((currentMillis - previousToneMillis) > 50) {
        previousToneMillis = currentMillis;
        tone(BUZZER,toneMelody[i]-380,60);
        i++;
        }
    }
    ii++;
  }

}

// door open? then increment the timer - sound the alarm 
void fridgeDoorOpenTimer() {

  if (doorOpen == false && doorTrigger == false) {
    return;
  }

  if (digitalRead(RESET_BTN) == HIGH) {
    digitalWrite(POWER_LED, LOW);
    while (digitalRead(RESET_BTN) == HIGH) {
      delay(10);
    }

    if (SerialDebug) {
      Serial.println("reset");
    }
    startTime = millis();
    soundTheAlarm = false;
    digitalWrite(POWER_LED, HIGH);
  }

  // checking once a second
  doorOpenTime = millis() - startTime;
  if (doorOpenTime % 1000 == 0 && doorOpenTime != lastDoorOpenTime) {
    if (SerialDebug) {
      Serial.println(doorOpenTime);
    }

    if (doorOpenTime > doorOpenDelay) {
      if (SerialDebug) {
        Serial.println("Awwooga Awwooga - fridge door open!");
      }
      soundTheAlarm = true;
      soundAlarm();
    }

    lastDoorOpenTime = doorOpenTime;
  }

}


void setup() {

  pinMode(TEST_LED, OUTPUT);
  digitalWrite(TEST_LED, HIGH);

  if (SerialDebug) {
    Serial.begin(9600);
  }

  delay(2000);

  pinMode(DOOR_LED, OUTPUT);
  pinMode(POWER_LED, OUTPUT);
  pinMode(BUZZER, OUTPUT);

  if (SerialDebug) {
    Serial.println("ready");
  }
  digitalWrite(POWER_LED, HIGH);

  pinMode(FRIDGE_DOOR, INPUT);
  attachInterrupt(digitalPinToInterrupt(FRIDGE_DOOR), fridgeDoor, CHANGE);

  pinMode(RESET_BTN, INPUT);
  digitalWrite(TEST_LED, LOW);
}

void loop() {
  fridgeDoorOpen();
  fridgeDoorOpenTimer();
}

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

#define TEST_LED 13

#define FRIDGE_DOOR 6

#define DOOR_LED 8

#define POWER_LED 7

#define RESET_BTN 9

#define BUZZER 10

volatile boolean doorOpen = true; // when the light is on

volatile boolean doorTrigger = false;

volatile unsigned long lastFridgeMillis = 0;

volatile unsigned long fridgeTimeoutMillis = 10;

boolean SerialDebug = false;

unsigned long doorOpenDelay = 45000; // 45 second timeout before buzzer sounds

unsigned long doorOpenTime = 0;

unsigned long startTime;

unsigned long previousToneMillis = 0;

unsigned long toneInterval = 20;

boolean soundTheAlarm = false;

boolean outputTone = false;

int toneMelody[5] = { 1600, 1900, 2000, 2100, 1800 };

const int toneMax = 5;

unsigned long lastDoorOpenTime = 1;

char pout[80]; // for testing

// interrupt function

void fridgeDoor() {

if ((millis() - lastFridgeMillis) > fridgeTimeoutMillis) {

doorOpen = digitalRead(FRIDGE_DOOR); // goes high when dark

lastFridgeMillis = millis();

}

// see if the door is open or closed

void fridgeDoorOpen() {

if (doorOpen == true && doorTrigger == false) {

doorTrigger = true;

startTime = millis();

if (SerialDebug) {

sprintf(pout, "door open: %d", doorOpen);

Serial.println(pout);

}

digitalWrite(DOOR_LED, HIGH);

return;

}

if (doorOpen == false && doorTrigger == true) {

doorTrigger = false;

if (SerialDebug) {

sprintf(pout, "door closed: %d", doorOpen);

Serial.println(pout);

}

startTime = 0;

doorOpenTime = 0;

soundTheAlarm = false;

digitalWrite(DOOR_LED, LOW);

return;

}

// make some noise

void soundAlarm() {

if (soundTheAlarm == false) {

return;

}

int ii = 0;

while (ii < 6) {

if (soundTheAlarm == false) {

break;

}

int i = 0;

while (i < toneMax) {

if (soundTheAlarm == false) {

break;

}

unsigned long currentMillis = millis();

if((currentMillis - previousToneMillis) > 50) {

previousToneMillis = currentMillis;

tone(BUZZER,toneMelody[i]-380,60);

i++;

}

ii++;

}

// door open? then increment the timer - sound the alarm

void fridgeDoorOpenTimer() {

if (doorOpen == false && doorTrigger == false) {

return;

}

if (digitalRead(RESET_BTN) == HIGH) {

digitalWrite(POWER_LED, LOW);

while (digitalRead(RESET_BTN) == HIGH) {

delay(10);

}

if (SerialDebug) {

Serial.println("reset");

}

startTime = millis();

soundTheAlarm = false;

digitalWrite(POWER_LED, HIGH);

}

// checking once a second

doorOpenTime = millis() - startTime;

if (doorOpenTime % 1000 == 0 && doorOpenTime != lastDoorOpenTime) {

if (SerialDebug) {

Serial.println(doorOpenTime);

}

if (doorOpenTime > doorOpenDelay) {

if (SerialDebug) {

Serial.println("Awwooga Awwooga - fridge door open!");

}

soundTheAlarm = true;

soundAlarm();

}

lastDoorOpenTime = doorOpenTime;

}

void setup() {

pinMode(TEST_LED, OUTPUT);

digitalWrite(TEST_LED, HIGH);

if (SerialDebug) {

Serial.begin(9600);

}

delay(2000);

pinMode(DOOR_LED, OUTPUT);

pinMode(POWER_LED, OUTPUT);

pinMode(BUZZER, OUTPUT);

if (SerialDebug) {

Serial.println("ready");

}

digitalWrite(POWER_LED, HIGH);

pinMode(FRIDGE_DOOR, INPUT);

attachInterrupt(digitalPinToInterrupt(FRIDGE_DOOR), fridgeDoor, CHANGE);

pinMode(RESET_BTN, INPUT);

digitalWrite(TEST_LED, LOW);

}

void loop() {

fridgeDoorOpen();

fridgeDoorOpenTimer();

}

Links and Sources

Practical Electronics for Inventors, Third Edition. Paul Scherz and Simon Monk, pub. McGraw Hill, 2013. ISBN 978-0-07-177133-7
A pre-made USB LiPo Battery Charger – 3.7V Single Cell from Hobbytronics or from Sparkfun
Battery Charger MCP3831T Datasheet
TEPT4400 Phototransistor Datasheet

Arduino, Electronics, Hardware

A Box for my Pixles

18th August 2018 Karl

This all started with wanting to modify a cheap camping light by replacing the LED’s with some colourful NeoPixels. I made a Printed Circuit Board to match the existing PCB disc that held the LED’s, as well as a board for an ATtiny85 microcontroller which incorporated a microphone and vibrating motor of the type used in a old mobile phone. The battery and charging circuit came from a cheap (Poundland) USB powerbank but it turned out that the battery from the powerbank didn’t fit in the camping light how I liked (in a measure twice, cut once sort of thing). Instead I made this:

APPLE, Computer, linux, Programming, Raspberry Pi

Extracting MP3 audio from video files

29th July 2018 Karl

Here is a small Bash script that converts any supported ffmpeg video format; such as .MKV, .MP4 or .MOV and extracts the audio to an .MP3 file, It will also split that MP3 file into chunks and put them in a convenient directory. You will need to install ffmpeg and mp3splt for your particular platform.

Example Usage:

./mkv2mp3 "big fat file.mkv"

1	./mkv2mp3 "big fat file.mkv"

This uses ffmpeg to convert “big fat file.mkv” to “big fat file.mp3” and then uses mp3splt to create a directory “big fat file” containing the files 01 – big fat file.mp3, 02 – big fat file.mp3, etc. The MP3 files will be encoded at 128k Constant Bit Rate and each file will be around 50 minutes in length. To install in Debian/Ubuntu use: sudo apt-get install ffmpeg mp3splt

#!/bin/bash
INFILE=$1
BITRATE="128k"
LENGTH="50.0"

FILENAME=$(basename "$INFILE" | cut -d. -f1)
if [[ -z "${FILENAME// }" ]]; then
   echo "filename missing"
   exit 1
fi

echo "$FILENAME"
ffmpeg -i "$INFILE" -vn -acodec libmp3lame -b:a "$BITRATE" "$FILENAME".mp3
mp3splt -t "$LENGTH" -d "$FILENAME" -a -o @n+-+@f "$FILENAME".mp3

#!/bin/bash

INFILE=$1

BITRATE="128k"

LENGTH="50.0"

FILENAME=$(basename "$INFILE" | cut -d. -f1)

if [[ -z "${FILENAME// }" ]]; then

echo "filename missing"

exit 1

echo "$FILENAME"

ffmpeg -i "$INFILE" -vn -acodec libmp3lame -b:a "$BITRATE" "$FILENAME".mp3

mp3splt -t "$LENGTH" -d "$FILENAME" -a -o @n+-+@f "$FILENAME".mp3

mp3splt can find the audio in a quiet region near where the split is desired rather than midway through a word, this should make for much cleaner playback across tracks.

Alternative Method

This script gives the same results but uses ffmpeg to split the large MP3 file and then adds track numbering metadata using id3v2. To install in Debian/Ubuntu use: sudo apt-get install ffmpeg id3v2

#!/bin/bash
INFILE="$1"
BITRATE="128k"
LENGTH="3000"    # 50 minutes in seconds

FILENAME=$(basename "$INFILE" | cut -d. -f1)
if [[ -z "${FILENAME// }" ]]; then
   echo "filename missing"
   exit 1
fi

echo "$FILENAME"
MP3FILE="$FILENAME".mp3
ffmpeg -y -i "$INFILE" -vn -acodec libmp3lame -b:a "$BITRATE" "$MP3FILE"

OUTDIR="$FILENAME"
mkdir "$OUTDIR"

ffmpeg -y -i "$MP3FILE" -vn -f segment -segment_time "$LENGTH" -c copy "$OUTDIR"/%02d-"$MP3FILE"

TRACK=1
IFS=$'\n'
FILES=($(find "$OUTDIR" -name "*.mp3" | sort -n))
for file in "${FILES[@]}"; do
  TN=$(printf %02d $TRACK)
  id3v2 --track "$TN" --TIT2 "$FILENAME" "$file"
  TRACK=$((TRACK+1))
done

#!/bin/bash

INFILE="$1"

BITRATE="128k"

LENGTH="3000" # 50 minutes in seconds

FILENAME=$(basename "$INFILE" | cut -d. -f1)

if [[ -z "${FILENAME// }" ]]; then

echo "filename missing"

exit 1

echo "$FILENAME"

MP3FILE="$FILENAME".mp3

ffmpeg -y -i "$INFILE" -vn -acodec libmp3lame -b:a "$BITRATE" "$MP3FILE"

OUTDIR="$FILENAME"

mkdir "$OUTDIR"

ffmpeg -y -i "$MP3FILE" -vn -f segment -segment_time "$LENGTH" -c copy "$OUTDIR"/%02d-"$MP3FILE"

TRACK=1

IFS=$'\n'

FILES=($(find "$OUTDIR" -name "*.mp3" | sort -n))

for file in "${FILES[@]}"; do

TN=$(printf %02d $TRACK)

id3v2 --track "$TN" --TIT2 "$FILENAME" "$file"

TRACK=$((TRACK+1))

done

Creating an Audiobook

Taking this further, I was thinking that it would be nice to have these converted into the M4B Audiobook format for use on my elderly iPod. The script below assumes that you have processed the files as above and have added metadata tags using a tool like mp3tag (yes I know this is for Windows).

To complete this we need to: Combine the multiple MP3 files into one big file, or read the original big file then convert that to M4B format at 96K bit and add chapter marks every ten minutes. For this I have used ffmpeg v3.2.12 and libmp4v2 (for the mp4chaps utility), to install in Debian/Ubuntu use: sudo apt-get install libmp4v2-dev mp4v2-utils ffmpeg

This script works best from a single MP3 file rather than from those that have been re-combined back into a single file, recombining the files caused ffmpeg to exclaim “invalid packet size” and “invalid data” errors. It is able to tell the difference between a directory and a single MP3 and processes the file accordingly, don’t forget to add metadata tags and cover art before you run the script.

#!/bin/bash
INFILE="$1"

BITRATE="96k"
MP3TITLE=""
MP3ARTIST=""
MP3ALBUM=""
MP3COMMENT=""
MP3YEAR=""
MP3PERFORMER=""

####
####  FUNCTIONS
####

function setMP3variables() {
  TAG="$1"
  VALUE="$2"

  case "$TAG" in
    title)
      MP3TITLE="$VALUE"
      ;;
    artist)
      MP3ARTIST="$VALUE"
      ;;
    comment)
      MP3COMMENT="$VALUE"
      ;;
    album_artist)
      MP3PERFORMER="$VALUE"
      ;;
    album)
      MP3ALBUM="$VALUE"
      ;;
    date)
      MP3YEAR="$VALUE"
      ;;
   esac
}

## get the tag text from the metadata
## if the line contains an equals (=) then split by the first equals.
function getMP3tags() {
  MP3METADATA="$1"
  while read -r line
  do
    case "$line" in
      *=*)
        TAG=${line%%"="*}
        VALUE=${line#*"="}
        setMP3variables "$TAG" "$VALUE"
        ;;
    esac
  done < "$MP3METADATA"

  if [[ ! -z "${MP3TITLE// }" ]]; then
    OUTFILE="$MP3TITLE".mp3
    M4BFILE="$MP3TITLE".m4b
  fi
}

####
####   BEGINS
####

FILENAME=$(basename "$INFILE" | cut -d. -f1)
if [[ -z "${FILENAME// }" ]]; then
   echo "filename missing"
   exit 1
fi
OLDIFS=$IFS
OUTFILE="$FILENAME"_out.mp3
M4BFILE="${OUTFILE:0:-4}".m4b
METADATA="${OUTFILE:0:-4}".metadata
JPGFILE="${OUTFILE:0:-4}".jpg


## check if input is a diretory
if [ -d "$INFILE" ]; then
  # get the name of the first MP3 file in the directory
  FIRSTFILE=$(find "$INFILE" -name "*.mp3" | sort -n | head -1)
  FIRSTFILE=$(basename "$FIRSTFILE")

  if [[ -z "${FIRSTFILE// }" ]]; then
    echo "no mp3 files in directory"
    exit 1
  fi

  ## save the MP3 tag metadata from the first file
  ffmpeg -y -i "$INFILE/$FIRSTFILE" -f ffmetadata "$METADATA"
  ## save out the cver art image
  ffmpeg -y -i "$INFILE/$FIRSTFILE" -an -vcodec copy "$JPGFILE"
  ## process the tag metadata - put it into the $MP3* strings, set $OUTFILE and $LOGFILE from the title
  getMP3tags "$METADATA"

  ## make a bar seperated list of the MP3 files that are to be combined
  MP3FILES=""
  IFS=$'\n'
  FILES=($(find "$INFILE" -name "*.mp3" | sort -n))
  for files in "${FILES[@]}"; do
    MP3FILES+="$files|"
  done
  MP3FILES=${MP3FILES:0:-1}

  ## combine all the MP3 files into one big file
  ## $OUTFILE is set using either the $FILENAME or $MP3TITLE if that has been used
  ffmpeg -y -i "concat:$MP3FILES" -vn -vsync 2 -acodec copy "$OUTFILE"
else
  ## process a single MP3 file
  ## save the MP3 tag metadata from the first file
  ffmpeg -y -i "$INFILE" -f ffmetadata "$METADATA"
  ffmpeg -y -i "$INFILE" -an -vcodec copy "$JPGFILE"
  ## process the tag metadata - put it into the $MP3* strings, set $OUTFILE and $LOGFILE from the title
  getMP3tags "$METADATA"
  #ffmpeg -y -i "$INFILE" -vn -vsync 2 -acodec copy "$OUTFILE"
  OUTFILE="$INFILE"
fi

## if there is a cover image, these are are the options for adding it back in
WITHJPG=()
if [ -e "$JPGFILE" ]; then
   IFS=$OLDIFS
   WITHJPG=(-i "$JPGFILE" -metadata:s:v comment="Cover (front)")
fi

## create the audiobook M4B file
## and write the metadata into the output file
ffmpeg -y -i "$OUTFILE" -i "$METADATA" "${WITHJPG[@]}" -map_metadata 1 -id3v2_version 3 -acodec aac -b:a "$BITRATE" -strict -2 -f mp4 "$M4BFILE"
## add the chapters every 10 minutes
mp4chaps -e 600 "$M4BFILE"

## tidy up
rm "$MP3METADATA"
if [ -e "$JPGFILE" ]; then
   rm "$JPGFILE"
fi
#rm "$OUTFILE"
echo "finished"

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

#!/bin/bash

INFILE="$1"

BITRATE="96k"

MP3TITLE=""

MP3ARTIST=""

MP3ALBUM=""

MP3COMMENT=""

MP3YEAR=""

MP3PERFORMER=""

####

#### FUNCTIONS

####

function setMP3variables() {

TAG="$1"

VALUE="$2"

case "$TAG" in

title)

MP3TITLE="$VALUE"

;;

artist)

MP3ARTIST="$VALUE"

;;

comment)

MP3COMMENT="$VALUE"

;;

album_artist)

MP3PERFORMER="$VALUE"

;;

album)

MP3ALBUM="$VALUE"

;;

date)

MP3YEAR="$VALUE"

;;

esac

}

## get the tag text from the metadata

## if the line contains an equals (=) then split by the first equals.

function getMP3tags() {

MP3METADATA="$1"

while read -r line

case "$line" in

*=*)

TAG=${line%%"="*}

VALUE=${line#*"="}

setMP3variables "$TAG" "$VALUE"

;;

esac

done < "$MP3METADATA"

if [[ ! -z "${MP3TITLE// }" ]]; then

OUTFILE="$MP3TITLE".mp3

M4BFILE="$MP3TITLE".m4b

}

####

#### BEGINS

####

FILENAME=$(basename "$INFILE" | cut -d. -f1)

if [[ -z "${FILENAME// }" ]]; then

echo "filename missing"

exit 1

OLDIFS=$IFS

OUTFILE="$FILENAME"_out.mp3

M4BFILE="${OUTFILE:0:-4}".m4b

METADATA="${OUTFILE:0:-4}".metadata

JPGFILE="${OUTFILE:0:-4}".jpg

## check if input is a diretory

if [ -d "$INFILE" ]; then

# get the name of the first MP3 file in the directory

FIRSTFILE=$(find "$INFILE" -name "*.mp3" | sort -n | head -1)

FIRSTFILE=$(basename "$FIRSTFILE")

if [[ -z "${FIRSTFILE// }" ]]; then

echo "no mp3 files in directory"

exit 1

## save the MP3 tag metadata from the first file

ffmpeg -y -i "$INFILE/$FIRSTFILE" -f ffmetadata "$METADATA"

## save out the cver art image

ffmpeg -y -i "$INFILE/$FIRSTFILE" -an -vcodec copy "$JPGFILE"

## process the tag metadata - put it into the $MP3* strings, set $OUTFILE and $LOGFILE from the title

getMP3tags "$METADATA"

## make a bar seperated list of the MP3 files that are to be combined

MP3FILES=""

IFS=$'\n'

FILES=($(find "$INFILE" -name "*.mp3" | sort -n))

for files in "${FILES[@]}"; do

MP3FILES+="$files|"

done

MP3FILES=${MP3FILES:0:-1}

## combine all the MP3 files into one big file

## $OUTFILE is set using either the $FILENAME or $MP3TITLE if that has been used

ffmpeg -y -i "concat:$MP3FILES" -vn -vsync 2 -acodec copy "$OUTFILE"

else

## process a single MP3 file

## save the MP3 tag metadata from the first file

ffmpeg -y -i "$INFILE" -f ffmetadata "$METADATA"

ffmpeg -y -i "$INFILE" -an -vcodec copy "$JPGFILE"

## process the tag metadata - put it into the $MP3* strings, set $OUTFILE and $LOGFILE from the title

getMP3tags "$METADATA"

#ffmpeg -y -i "$INFILE" -vn -vsync 2 -acodec copy "$OUTFILE"

OUTFILE="$INFILE"

## if there is a cover image, these are are the options for adding it back in

WITHJPG=()

if [ -e "$JPGFILE" ]; then

IFS=$OLDIFS

WITHJPG=(-i "$JPGFILE" -metadata:s:v comment="Cover (front)")

## create the audiobook M4B file

## and write the metadata into the output file

ffmpeg -y -i "$OUTFILE" -i "$METADATA" "${WITHJPG[@]}" -map_metadata 1 -id3v2_version 3 -acodec aac -b:a "$BITRATE" -strict -2 -f mp4 "$M4BFILE"

## add the chapters every 10 minutes

mp4chaps -e 600 "$M4BFILE"

## tidy up

rm "$MP3METADATA"

if [ -e "$JPGFILE" ]; then

rm "$JPGFILE"

#rm "$OUTFILE"

echo "finished"

When encoding to the M4B using a re-combined file I saw a few of these errors from ffmpeg:

[mp3 @ 0x7fffc3bc9ea0] Header missing
Error while decoding stream #0:0: Invalid data found when processing input

1 2	[mp3 @ 0x7fffc3bc9ea0] Header missing Error while decoding stream #0:0: Invalid data found when processing input

These appear to be caused by the mp3splt program from when the original MP3 file was being split into 50 minute chunks, but I can’t hear any effect on the output.

Lots of information about the file can be gotten using mediainfo, to install in Debian/Ubuntu use: sudo apt-get install mediainfo, example use:

mediainfo --fullscan "big fat file.m4b"

1	mediainfo --fullscan "big fat file.m4b"

Links and References

ffmpeg, encode AAC: https://trac.ffmpeg.org/wiki/Encode/AAC
ArchLinux audiobook howto

Hardware, Repair

Fixing an SD Card

22nd July 2018 Karl

The corner of one of my SD cards broke off and would no longer latch properly in the cameras slot, it was time to either throw it away or repair. I opted for repair.

For the repair I used some Poundland two part epoxy resin as this can be used to fill in the missing section and when fully cured, after 16 hours, is just as strong as the plastic its replacing.

I started with a sheet of glass from a picture frame to give me a flat surface, upon which I stuck a short strip of electricians tape as the epoxy resin wont stick to this, next I applied a small blob of resin to the tape over which I placed the SD card to cover the entire broken corner that you see in the photo then squeezing down to push out the excess. I then left it for about ten minutes to let the glue set a little when I could push the glue up and fill in the corner.

I then left it for about an hour to go solid but still pliable, I then peeled the tape off from the glass and glue. The next stage was to trim down the excess with a scalpel, this tided up the outer edges but still left a ridge by one of the contacts, in the morning I removed this by carefully filing it away. I finished by cleaning with isopropyl alcohol.

drone

Sheffield Manor Lodge – Battle Re‑enactment Day, June 2018

22nd June 2018 Karl

With thanks to the management and staff at Manor Lodge for giving me permission to video the event with my quad-copter. http://sheffieldmanorlodge.org/.

Featuring:

Regia Anglorum – Vikings – https://regia.org/
Team Falchion – 14th Century Knights – http://www.falchion.org/
English Civil War Society, Col. Valentine Walton’s Regiment of Foot – 17th Century Soldiers – http://www.ecws.org.uk/
Coldstream Guards 1815 – https://coldstreamguards1815.org.uk/
Henry VIII and his wives
Duncan Bell on Bagpipes, playing 16th Century dance tune ‘The Brawl’
Bregudwith on Bone Whistle and Yrmenlaf on Lyre

Arduino, Electronics, Hardware

Hacking the Yongnuo Wireless Controller

22nd February 2018 Karl

I wrote this back in May 2017 but it was never finished, I got distracted by other things and I needed the wireless controller for photography. I wrote all this and it would be a shame to delete it, so I am posting it now on the chance there may be of something of interest within.

I use this Yongnuo Wireless Controller in photography to control a number of flash units away from the camera body. It comes in two parts, a transmitter that connects to the hotshoe on the camera and receivers with a hotshoe that connect to the flash, a single transmitter can control any number of flash receivers within the claimed 300 meter range. The transmitter with a couple of receivers can be gotten of eBay for around £35.

Yongnuo Wireless Controller FSK 2.4GHz
RF-600TX transmitter
RF-602RX receiver

[image of transmitter and receivers]

I am looking to:

See how the flash is connected
Investigate how the transmitter works – reverse engineer as much as I can
See if I can control the transmitter directly with an Arduino
See if other devices using the same radio chip can also be controlled
Not destroy the transmitter while examining it

Opening it up

[images of the transmitter insides]

On the board inside you will find:

A power on/off switch
Bi-colour Red/Green LED
A dual-press button with two switches for operating the flash manually
A four way code selector (4 way DIL switch)
An anonymous (no markings) microcontroller – µC
A7105 2.4GHz FSK/GFSK ISM band wireless transceiver

On the underside, my board is marked with the following version and date:

Version: 1.21
Date: 14/04/23 – 23 April 2014

Looking at the datasheet for the A7105 it can work as both a transmitter and receiver and uses an SPI interface for user control, it appears to be popular with the radio controlled RC aeronautical drone community. The receiver looks to be very similar by way of components, using the same radio chip and anonymous microcontroller. I have not examined it in any detail and take care if disassembling as there are three hotshoe connections that need to be desoldered.

Flash Connection

On the Canon camera the hotshoe has six connections but we only need to examine three of these. Looking down on the camera with the lens facing away from you, the main plate where the flash slides in is ground, the large central dot is the flash trigger just below this on the left is the camera ready connection. I assume the rest are for the E-TTL functions and I have not looked at these.

Checking the hotshoe with a multimeter, the flash trigger appears to have a high resistance that decreases when the flash is fired, I suppose this is a legacy of when cameras were more mechanical. The Camera Ready connection goes High – around 5 Volts, to tell the flash to wake up, that you have pressed the shutter halfway, the lens has focused and you are about to take a photo.

To find the duration of the flash signal on the cameras hotshoe I connected an almost flat AA battery between ground and flash to give me 1.2 volts to measure against on the oscilloscope (checking a canon flash itself, the voltage across the flash pin and ground is 4.47 volts). I found that the flash signal is sent by the camera for 352ms, which is quite long considering that a typical shutter speed of 1/125 second for flash photography works out at 8ms, although the amount of time a flash fires for is set on the flash and not by this signal.

Microcontroller Connections

I spent a while tracing out most of the transmitter circuit, I have ignored most of the supporting radio circuitry and the crystal timer as I am wanting to investigate the data side. The parts are also rather small and troublesome to investigate with standard multimeter probes.

RF600TX - Partial Schematic — RF600TX – Partial Schematic

The microcontroller looks to use internal pullup resistors for the input switches, the camera ready signal from the hotshoe switches a transistor to pull pin 16 low on the controller.

Looking at the circuit diagram we see an output to the antenna from pin 8 of the micro controller. This outputs two different square waves when the shutter button is pressed, one for camera ready and another for flash. I think these are being modulated on the transmitter output to produce a radio signal and simplify the transmitter design. Looking at the output from pin eight on the oscilloscope, the two states can be seen quite clearly:

These square wave outputs are always the same, I thought it may change when a different code was chosen through the DIL switches. The transmitter unit does not receive any radio data, and no acknowledgement is made by the flash units.

Using a Logic Analyser

Time to break out the Logic Analyser, this is a cunning device that allows you to see the data being exchanged between the microcontroller and transceiver, I don’t want to get too detailed but think this may help for the following sections.

The data system being used by the A7105 is SPI. The Serial Peripheral Interface bus uses four wires: Chip Select SCS, multiple chips can be on the same SPI bus, but they all have different SCS connections, the master controller chip uses SCS to tell the slave chip it wants to use for data exchange. Serial Clock SCK: This is used to provide time synchronisation for the data exchange with a fixed duration for the highs and lows. Data SDIO: This is the data being sent by the microcontroller and GIO1 is data from the transceiver sent in reply, normally for SPI this is 8 bits, to make a byte.

The naming conventions used here are from the A7105 datasheet, The SPI bus has standard names for data lines; SDIO is MOSI – Master Out/Slave In, GIO1 would be MISO – Master In/Slave Out and SCS is SS – Slave Select. In our case the microcontroller would be the master and the transceiver the slave.

The Logic Analyser displays data in a form that allows you to see the logic, here we can see two bytes of data:

The microcontroller – µC sends data on the SDIO line and listens for replies on GIO1. When the µC sets Chip Select SCS low this tells the transceiver that the µC wants to talk to it. The µC sends a command byte followed by one or more bytes of data – a packet. During the SCS event, data is only transferred while the clock SCK is running.

SPI data, binary data from the highs and lows

We can see that the logic on the SDIO is read every-time the clock goes low, falling edge, a clock tick on the SCK line represents a bit of data, eight ticks make a byte. We now have our binary data: 00100101 for convenience this is converted into hexadecimal 0x25.

When examining an SPI bus check any available datasheets to see if the clock is set to tick on a falling or rising edge, the bit order is Most Significant Bit – MSB or Least Significant Bit – LSB, and the data length (normally eight).

Looking at the A7105 Transceiver

A7105 Block Diagram (a clearer version can be seen in the datasheet)

From the A7105 datasheet the SPI bus is set for the following:

To activate SPI, the SCS pin must be set low
data length: 8 bits
bit order: Most Significant Bit First (MSB)

I have made the following connections to the transmitter. Soldering test leads to the microcontroller (µC) is the most convenient place to do this.

This table shows the Input/Output pins on the transceiver and microcontroller, as well as the colour of wire used for the logic analyser.

A7105	Description		In/Out	µC	Wire Colour
11	SCS	3 Wire Chip Select	I	9	yellow
12	SCK	3 Wire Clock	I	10	orange
14	SDIO	Read / Write	I/O	12	brown
16	GIO1	4 Wire SPI Data Output	I/O	11	red
17	GIO2	4 Wire SPI Data Output	I/O	13	white
	GND	Ground			black
		Trigger Out	O	8	grey

How the A7105 organises data

The transceiver has two data modes, Strobe and Control. There are eight strobe commands to control the various modes the chip supports, these are four bits in length and always begin with a 1, where the transceiver is being operated in 8 bit mode the final four bits are ignored. The Control registers are eight bits in length and are used to configure and read settings from the transceiver, they are eight bits in length, the first bit is always 0 and the second is either 1 for write or 0 for read. The table below shows examples of a write, a read (or more accurately a request, the transceiver replies on GIO1) and a strobe command sent by the µC.

	Address Byte								Data
Bit:	7	6	5	4	3	2	1	0	7	6	5	4	3	2	1	0
Control:	CMD	R/W	Address						Data
Write Example: 0x2 0x1	0	0	0	0	0	0	1	0	0	0	0	0	0	0	0	1
Read Example: 0x42 0xff	0	1	0	0	0	0	1	0	1	1	1	1	1	1	1	1

Strobe:	CMD	Strobe ID			not used				not used
Example: 0xa0	1	0	1	0	0	0	0	0

Examining the A7105 data

Data is exchanged on the SPI during two events, after the transmitter has been switched on, and when you are pressing the camera shutter or the button on the unit.

Power On

When you first switch on the unit, the microcontroller initialises the transceiver with a few hundred bytes of data, I have created this spreadsheet from the SPI data, hex data across is the most useful sheet to view:

In summary the initialisation sequence consists of the following

The microcontroller sets the majority of control registers to default
Internal calibration is started and the microcontroller keeps checking until this is done
Final cleaning up
Place the A7105 into standby mode

Shutter Press

On the SPI the shutter press action has two distinct stages, the preamble and the transmission. The preamble takes the camera out of standby mode and sets the channel it is going to be transmitting on. The transmission broadcasts the camera ready and flash states.

The Preamble
At the beginning of the datacaptue I see a preamble packet sent over the SPI:

Logic Analyser Data - first five bytes of the Preamble Packet — Logic Analyser Data – first five bytes of the Preamble Packet

This preamble looks to only appear when the flash is first operated after the transmitter unit has been switched on, subsequent use goes straight to transmit. The fifth byte changes depending on the DIL switch setting on the underside of the unit, as you can see in the four examples given in the table below.

	bytes
DIL switch	strobe		control	data		strobe
0000	0xB0	0xB0	0x05	0xB5	0xF0	0xD0
1000	0xB0	0xB0	0x05	0xB5	0xE1	0xD0
0100	0xB0	0xB0	0x05	0xB5	0xD2	0xD0
1111	0xB0	0xB0	0x05	0xB5	0x0F	0xD0

Taking the first example, we can break this down to see what each byte is doing

SCS	Packet			IN/OUT	Command	Payload	binary
0	0xb0			STROBE	PLL Mode		0b10110000
1	0xb0			STROBE	PLL Mode		0b10110000
2	0x5	0xb5	0xf0	IN	FIFO Data	TX data	0b00000101	0b10110101	0b11110000
817µs gap
3	0xd0			STROBE	TX Mode	transmission begins	0b11010000

It is difficult to work out what is going on here, according to the datasheet you send a packet of data 0xb5 0xf0 to be transmitted to FIFO Data 0x5 and follow that with the strobe command TX mode 0xd0, but what is transmitted bears no relation to the FIFO packet.

We need to look further back in the initialisation sequence and the datasheet, the A7105 has three modes of transmission; easy, segment and extension. We need to undertake a little bit of detective work to find which this is. Chapter 16.4 of the datasheet shows us the two registers used in the initialisation sequence we need to examine:

Bit:		7	6	5	4	3	2	1	0
FIFO I	0x3	FEP7	FEP6	FEP5	FEP4	FEP3	FEP2	FEP1	FEP0
Setting value:	0x1	0	0	0	0	0	0	0	1
FIFO II	0x4	FPM1	FPM0	PSA5	PSA4	PSA3	PSA2	PSA1	PSA0
Setting value:	0x0	0	0	0	0	0	0	0	0

The datasheet does not say directly so we need to go through each modes description to see which is the best fit. Segment FIFO looks good: “In Segment FIFO, TX FIFO length is equal to (FEP [7:0] – PSA [5:0] + 1). FPM [1:0] should be zero”. So our settings: (FEP:0b1 – PSA:0b0) + 1 = 2. The number of bytes sent our FIFO Data packet is also 2.

Further reading of the description “This function is very useful for button applications. In such case, each button is used to transmit fixed code (data) every time. During initialisation, each fixed code is written into corresponding segment FIFO once and for all. Then, if button is triggered, MCU just assigns corresponding segment FIFO (PSA [5:0] and FEP [7:0]) and issues TX strobe command.”

The Transmission
Taking an initial look at the data gathered during a shutter press on the Trigger Out (pin 8 of the microcontroller) we can clearly see the transition from Camera Ready and Flash as we saw on the oscilloscope earlier.

GIO2 shows a mirror of the Trigger Out, but zooming in to the data and I see that it follows the Trigger signal. Looking in the initialisation spreadsheet at SCS event we see that the command 0xc 0x1 was sent for setting the function of the GIO2 pin. Looking at the datasheet this appears to be set as an ‘I am transmitting’ signal, WTR – Wait until TX or RX has finished. If I force GIO2 low by sorting it to ground then the flash does not fire when I press the shutter

In my data capture the Camera Ready signal was transmitted six times, and the Flash signal thirteen times, I am sure this is dependant on the length of time I had the shutter button pressed on the camera.

Apologies for the inconclusive ending, I ran out of time to pursue this further

Links and Sources

A7105 Datasheet and Product information
Logic Analyser: https://www.ikalogic.com/scanaplus/
SPI Data tutorial https://learn.sparkfun.com/tutorials/serial-peripheral-interface-spi
Arduino A7105 library: https://github.com/nh2/arduino-a7105
Reverse Engineering a Hubsan X4 Quadcopter: http://www.jimhung.co.uk/?p=1424 with a description of the A7105 data
SPI data bus and FSK – Frequency Shift Keying on Wikipedia

history, Interesting

History: Reading Early 19th Century Handwriting

3rd December 2017 Karl

I recently posted a legal document written in 1827, this was written in hand using a quill pen (quite possibly made from a goose feather) and it is rather difficult to read, there is no punctuation, commas or full stops not even an apostrophe and the capitalisation is all over the place. There are fewer characters in this alphabet, with some serving a dual purpose in giving a value based on context rather than appearance.

The ‘m’ and ‘n’ characters are upside down, uppercase ‘I’ and ‘J’ are both the same and some characters have still not been fully completed, so ‘c’ looks like an ‘r’ and ‘e’ looks like a ‘c’. The double ‘s’ – ‘ss’ had still not been invented at this time and words with these are spelt ‘fs’, so ‘passages’ is written as ‘pafsesges’. I have constructed this cheat sheet from that document and hopefully the chart will help you in your quest:

Letter			Example
A			and
B			between
C			second
D			hundred
E			same
F			of
G			shillings
H			her
I			said
J			jointly
K			Blake
L			latter
M			made
N			grant
O			Joseph
P			appointed
Q			quality
R			presents
S			assign
T			the
U			fourth
V			revoked
W			wife
X			execution
Y			yearly
Z			Elizabeth

After few hours reading the words start to pop out, it helps that the document is written is a formulaic legalese style with many repeated phrases (were they paid by the word?).

History: A Property Contract, Sheffield, July 1827

25th November 2017 Karl

An indenture dated 18th July 1827 for the transfer of a mortgage for £1000 and interest between Ralph Blakelock, a banker in Sheffield and the merchants; John Butcher, Samuel Hadfield, John Binney, and Thomas Binney, as well as Henry Agie a Gentleman all of Sheffield. The document looks to be describing the mortgage, rents and leases as well some land and property of a ‘large Capital Messuage or Dwelling house’ built on the site of two dwelling houses in a street or place in Sheffield commonly called or known by the name of the Hartshead. The two former houses were occupied by John Trippett and James Mycock before being ‘wholly pulled down and rebuilt’ by Nicholas Broadbent.

history

History: Fitzalan Market, Sheffield 1785

15th November 2017 Karl

Following the Sheffield Market Place Act 1784 here is a legal document written on vellum to purchase the lease for buildings and land to allow the redevelopment of the area round High Street, Angel Street, King Street and Haymarket opposite Fitzalan Square into a market.

Electronics, Hardware, Modification

TENMA Rework Station Teardown

4th November 2017 Karl

In a previous post I added a control knob to my Tenma 21-10130 Rework Station, but now I am taking a more detailed look at the controller board hardware inside paying particular attention to the microcontroller connections.

Removing the board from the rework station was a bit of a hassle, the screws at the bottom are particularly difficult to access. Eventually I had to unbolt the transformer from the case so I could get the screwdriver in, the transformer bracket catches up against a heatsink and capacitor so it cannot be completely gotten out of the way.

The board can be divided up into five sections, on the left is the mains power supply, with connections to the power switch and rework heater, along the bottom left is the 5V DC power supply for the microcontroller, top right is the control circuitry and connections for the rework heater and hot air, and bottom right those for the soldering iron. In the centre is the microcontroller and associated circuitry.

The rework heater, air pump and soldering iron are all controlled using triacs, these in turn are connected back to the microcontroller through optocouplers. The rework heater and air pump operate at mains voltage, 220V, while the soldering iron works at 24V, these are all using Alternating Current. Essentially the station is a collection of variable dimmer switches controlled by the microcontroller.

Wires Everywhere

There are ten connections to the controller board

Conn	Purpose
CN1	Mains in – from power connector
CN2	Power Switch
CN3	220VAC out to transformer
CN4	Rework Heater
CN5	Rework Air Pump power
CN6	Soldering Iron Temperature
CN7	Hand Key – Controls for Rework Wand
CN8	AC 9V input
CN9	Soldering Iron Power
CN10	AC 24V input

The connectors CN5 and CN6 are used to provide sensing for the microcontroller; one for the soldering iron temperature and another from the rework wand with the button controls, in cradle detect, and temperature sensing, there is also a row of five onboard button switches.

Microcontroller Control

With the multimeter in beep mode, tracing back the connections to the microcontroller took a couple of days.

The PIC19F916 microcontroller has 24 digital Input/Output pins which are divided into three ports of eight; RA0-RA7, RB0-RB7 and RC0-RC8. In the lists below I have shown the physical connection as well as the I/O port used.

The power control connections are to an optocoupler which in turn switches a triac:

PIC Pin		Optocoupler	Triac	Purpose	Conn
11	RC0	U6: MOC3083	TR1: BT136	220VAC	CN3
6	RA4	U5: MOC3083	TR2: JST139F	Rework Heater	CN4
16	RC5	U4: MOC3023	TR3: BT136	Rework Air Pump	CN5
7	RA5	U7: MOC3041	TR4: BT137	Soldering Iron	CN9

After much tracing of circuitry I found the triacs to be connected to the optocouplers much as shown below. Resistor values vary and on the microcontroller connection side the current limiting resistor is on the low side, pin two, rather than on the 5V line.

Optocoupler – Triac switch (from the MOC3043 datasheet)

There are five front panel control buttons which go low when pressed. Internal pullup resistors appear to have been used in the microcontroller.

Key	PIC Pin		Purpose
K3	24	RB3	Rework Power
K1	22	RB1	Up Button
K2	23	RB2	Down Button
K5	26	RB5	Set Button
K4	25	RB4	Soldering Iron Power

The two LCD displays, both are the same with seven connection pins with pin one at the top. The rework stations designers have not used the PIC’s built in LCD display functionality. The LCD panels are marked JRD90601A on the underside, I couldn’t find anything about this on Google.

	LCD1 Rework		LCD2 Soldering
Conn	PIC Pin		PIC Pin		Purpose
1	n/a				5V
2	n/a				GND
3	13	RC2	13	RC2	Data 1
4	12	RC1	12	RC1	Data 2
5	15	RC4	14	RC3	Data 3 – LCD Select
6	n/a				Backlight 5V
7	n/a				Backlight GND

At present I have no information about the LCD data pins, I’m thinking that RC1 and RC2 could be Data/Clock while RC3 and RC4 is for selecting the LCD to send data to.

The Hand Key connector CN7 for the Rework Wand with pin one to the left when looking at the component side with the key notches uppermost. I have not opened the wand as it is sealed closed with glue and I did not want to damage it.

CN7	PIC Pin		Purpose
1	n/a		GND for temperature
2	2	RA0	Rework Temperature – through OP07C op-amp
3	n/a		GND
4	27	RB8	unknown – no connection?
5	18	RC7	Up Button
6	17	RC6	Down Button
7	28	RB7	Select Button
8	n/a		GND for button controls

Other Connections

PIC Pin		Purpose
10	RA6	Buzzer – through Q2 (possibly a SS8550 PNP transistor)
9	RA7	U3: PC817 photocoupler – some kind of mains frequency monitor?
3	RA1	CN6: Soldering Iron Temperature – through op-amp OP07C
1	MCLR	Pulled high through 10K resistor – Master Clear Pin External Reset
21	RB0	9v AC monitor?

This concludes the examination of the hardware connected to the microcontroller, further work needs to be done through software and oscilloscope observations to see how the LCD displays, power controls (probably PWM), and temperature sensors work and what the 9V AC and 220V AC monitors are doing.

Circuits

Here are a couple of diagrams I drew up of the more involved sensor circuits while tracing things out. Values for the ceramic capacitors have been omitted as they are not marked on the SMD package. Both the rework and iron temperature sensors have similar op-amp circuits.

Op-amp circuit for the soldering iron temprature

Datasheets

PIC16F916 Microcontroller
OP07C Single Bipolar Op-Amp
Triacs: BT136, BT137 (no longer manufactured) and JST139F
The MOC3083, MOC3023 and MOC3041 Triac optocouplers
AT907-936B Tenma 21-10130 Rework Station

SMD Markings http://www.s-manuals.com/smd/y2

g7smy.co.uk

All posts by Karl

The Fridge Door is Open

Circuitry

Software

Links and Sources

A Box for my Pixles

Extracting MP3 audio from video files

Alternative Method

Creating an Audiobook

Links and References

Fixing an SD Card

Sheffield Manor Lodge – Battle Re‑enactment Day, June 2018

Hacking the Yongnuo Wireless Controller

Opening it up

Flash Connection

Microcontroller Connections

Using a Logic Analyser

Looking at the A7105 Transceiver

How the A7105 organises data

Examining the A7105 data

Power On

Shutter Press

Links and Sources

History: Reading Early 19th Century Handwriting

Further Reading

History: A Property Contract, Sheffield, July 1827

History: Fitzalan Market, Sheffield 1785

TENMA Rework Station Teardown

Wires Everywhere

Microcontroller Control

Circuits

Datasheets

COMPUTERS, ROBOTS AND PHOTOGRAPHY