genuinequality

Download free music MP3s on genuine quality, the world’s largest online music catalogue, powered by your scrobbles. Free listening, videos, photos, The world’s largest online music catalogue, powered by your scrobbles. Free listening, videos, photos, stats, charts, biographies and concerts. stats, charts, biographies and concerts.

Sunday, December 15, 2024

EuroRack 6HP MCU Experimenter Module Usage Notes

Here are some suggestions and usage notes for my EuroRack 6HP MCU Experimenter PCB. This post walks through the different sections of the schematic and PCB and shows how to tailor the circuits to different applications. EuroRack 6HP MCU Experimen…
Read on blog or Reader
Site logo image Simple DIY Electronic Music Projects Read on blog or Reader

EuroRack 6HP MCU Experimenter Module Usage Notes

By Kevin on December 15, 2024

Here are some suggestions and usage notes for my EuroRack 6HP MCU Experimenter PCB.

This post walks through the different sections of the schematic and PCB and shows how to tailor the circuits to different applications.

  • EuroRack 6HP MCU Experimenter Module PCB Design
  • EuroRack 6HP MCU Experimenter Module PCB Build Guide

Warning! These boards are meant for DIY systems only. They should NOT be used with expensive EuroRack modules, racks, or power supplies. I strongly recommend using old or second hand equipment for your experiments.  I am not responsible for any damage to expensive instruments!

If you are new to Electronics, see the Getting Started pages.

Introduction

As detailed in the design notes, there are a number of different sections for this PCB, each designed to be used to link a microcontroller to a EuroRack synth in a useful, and hopefully electrically useful way.

But I have to reiterate right at the start - I strongly state that you DO NOT use these in a rack of expensive or cherished gear!

It is meant for DIY experiments and so it should be expected that:

  • Use of this PCB could easily destroy any power supply powering it.
  • Use of this PCB could also easily destroy any EuroRack modules in the same rack using the same power bus.

In short, I'm only using this with cheap, second hand, other DIY kit, or equally sacrificial equipment and I strongly state that you should do the same.

The Microcontroller Board

Recall that there are two PCBs to be used: an IO board and a MCU board. The MCU board could support either a Raspberry Pi Pico (or similar) or an Arduino Nano (or similar).

The MCU board has all of the components on the underside, apart from the two rows of headers joining it to the IO board. The IO board has all components on the top-side, apart from the two rows of headers joining it to the MCU board.

Arduino Nano

The following illustrate which components are required to use an Arduino Nano. This shows the rear view of the MCU board.

The Arduino Nano will run directly off the EuroRack +12V line, so no regulator or associated components are required. The following detail shows which components need to be mounted to support the Nano's power.

The Nano itself should be mounted on the two 15-way header sockets and aligned as shown below. Note that the USB connection is facing "down" towards the EuroRack power connector.

If the regulator and additional circuitry is already fitted it will be ignored if an Arduino Nano is used.

Raspberry Pi Pico

To use a Raspberry Pi Pico, the full power circuit is required, including the regulator, additional capacitors and diode as shown below. Once again this is showing the rear of the MCU board where all of the components (apart from the interconnecting headers) will be mounted.

The Pico will be mounted on the two 20-way header sockets and aligned as shown below, with the USB connector at the "top" facing away from the EuroRack power connector.

The IO Board

MCU Interface

The IO board itself will be connected to the microcontroller board using the interconnecting 14-way headers and all microcontroller IO pins will be broken out to pads as shown below.

The idea is that the main circuit sections terminate at one of the three MCU PWM|OUT|IN headers (also highlighted) and can then be patched across to the MCU IO headers which have the following layout.

GND VCC D12 D13 (no)
D16
A0 A1 A2 A3
D17
A4
D18
A5
D19
A6
D20
A7
D21
D22
GND VCC D11 D10 D9 D8 D7 D6 D5 D4 D3 D2 D1 D0

The Arduino supports D0-D13 and A0-A7, although for an Arduino Nano A0-A6 can also be referenced as D14-D19 of course.

The Raspberry Pi Pico supports D0-D13, D16-D22 and A0-A2.

External Connections

Potentiometers, switches, jacks, audio or any other external IO can be connected to the IO board in a number of places. The following shows where they are and how they related to the MCU connections.

Audio PWM Output

There are two PWM output channels, each of which can be driven by one or two PWM outputs from the microcontroller. A great explanation of dual PWM output can be found on Open Music Labs here:

  • http://www.openmusiclabs.com/learning/digital/pwm-dac.1.html
  • http://www.openmusiclabs.com/learning/digital/pwm-dac/dual-pwm-circuits/index.html

PWM Resolution and Filter

The PCB will support a single PWM output by omitting R100. If dual PWM output is required, then R100 and R101 need to have values that support the required bit-depth of the PWM resolution as described in the Open Music Labs tutorial (see "table 2").

Some options might be:

Source R100 R101 Resistor Ratio PWM Resolution
Mozzi Dual 499K 3K9 128 Dual 7-bit
Proto Pedal PCB 300K 4K7 64 Dual 6 bit

Otherwise a single resistor (e.g. R100) could be used for a single, 8-bit resolution PWM, in which case the chosen resistor will form part of the PWM filter consisting of R100 and C100.

As shown, there is a two-stage PWM filter circuit: R100/R101 and C100; R102 and C101. For a simpler application the second stage could be omitted and R102 replaced with a wire link (or short, for 0K).

In HAGIWO's Nano design, the first stage uses values as per the Mozzi dual PWM default (above) with a 4n7 capacitor. The second stage uses a second 3K9 resistor with a 10nF capacitor. In the XIAO DAC application, HAGIWO uses a single resistor output from the DAC with a two stage filter of twin 10K + 1nF.

From the Open Music Labs tutorial, we have the following relationships for dual PWM and a low-pass filter:

  • R2 = R1 . 2^n
  • C ~= 1 / ( 2 . pi . R1 . Fc)

So the cutoff frequency Fc = 1 / ( 2 . pi . R1 . C ) where R1 is the smaller of the two resistors, so R101.

But when there are two filter stages, the RC calculation seems to be quite a bit more complicated and beyond my current knowledge of electronics, so I'm just going with some of the suggested values from the existing circuits...

Some options for the PWM filter stage I've seen so far can be summarised as follows:

R100 R101 R102 C100 C101
Nano Dual 7 bit 499K 3K9 3K9 4n7 10n
Nano Single 7 bit - 3K9 3K9 4n7 10n
Nano Single, Simple Filter 8 bit - 3K9 0K 4n7 -
Nano Dual 6 bit 300K 4K7 4K7 4n7 or 22n 10n
XIAO (3V3) DAC - 10K 10K 10n 10n
RP2040 (3V3) - 220R 220R 10n 10n

Fundamentally, it depends on the required resolution, single or dual operation, and then the required cut-off frequency of the filter. For the simpler setup, values can be tested using a low-pass filter calculator (more here).

Note: I wasn't able to easily source 499K resistors, but I was able to find a number of 500K 1% resistors so I used a meter to measure them and picked those closest to 499K.

OpAmp Gain

R103 and R104 can be used to set the gain of the MCP6232-based OpAmp. For 5V operation, R103 can be omitted and R104 shorted for unity gain. For 3V3 operation, the ration of R103 to R104 can be used to set a gain for 3V3 to 5V amplification. The values below were used by HAGIWO in the XIAO DAC output circuit.

R103 R104
5V to 5V (unity gain) - 0K
3V3 to 5V 5K6 2K9

OpAmp Choice

HAWIGO's circuit suggest the MCP6232 for rail-to-rail operation, but there are probably many others that would work too. There is a great OpAmp summary sheet on the Microchip site that lists all of their OpAmps (see here).

I'm pulling out any dual, DIP packaged, rail-to-rail devices, that seem similar to the MCP6232 (I believe these all have the same pinout):

Device GBWP IQ Typ VOS Max Op Voltage
MCP6232 300 kHz 20 uA 7 mV 1.8V to 5.5V
MCP6242 650 kHz 50 uA 7 mV 1.8V to 5.5V
MCP6002 1 MHz 140 uA 4.5 mV 1.8V to 5.5V
MCP6272 2 MHz 170 uA 3 mV 2.0V to 5.5V
MCP6275 2 MHz 150 uA 3 mV 2.0V to 5.5V
MCP6282 5 MHz 445 uA 3 mV 2.2V to 5.5V
MCP6285 5 MHz 400 uA 3 mV 2.2V to 5.5V
MCP6292 10 MHz 1000 uA 3 mV 2.4V to 5.5V
MCP6295 10 MHz 1100 uA 3 mV 2.4V to 5.5V

Of course, I'm quoting those figures with very little clue as to their meaning, but in my "hand-wavy" world of electronics knowledge, given the kind of level I'm working at here, I would suggest any of those might be fine for this application.

Most are probably rated more highly than required, and I'd suggest the lower current ones are best for the audio frequencies I want to be working at.

Output Coupling

The final stage of the circuit sets the output impedance and removes the DC bias from the audio output. I've seen all of the following values used so far:

R105 C102
XIAO DAC Output 470R 2u2
Nano Output 220R 4u7
RP2040 330R 10u

I've not spent any time wondering about how these values will affect the output, so I'm just documenting them for now. This is probably a good area for experimentation to find the most suitable values for any specific application.

The two diodes (D100, D101) that provide clamping are BAT43 Schottky diodes.

Second PWM Output

All of the above can be duplicated for R200-205, C200-202, D200-201 for the second PWM channel, which uses the second OpAmp from the MCP6232.

In the photo below, all components and connections associated with PWM 1 are highlighted in RED and for PWM 2 are highlighted in YELLOW. naturally if only one PWM circuit is required, all components associated with the other can be omitted.

GATE and CV Inputs

There are two GATE and two CV inputs as shown in the following schematic sections - GATE input on the left; CV input on the right.

Gate Input

The GATE input section mirrors that of my Educational DIY Synth Thing, so the values are pretty much fine as being the following:

R300 100K
R301 1M
R302 10K
D300 1N4148

Note that the actual MCU_GATE_IN signal will be active LOW - so inverted compared to the input signal. The input signal is assumed to be a 0 to 5V signal.

R302 is just a pull-up resistor, and everything should be fine with either a 5V or 3V3 VCC level.

CV Input

The CV input section has several variants. R400 and R401 can be used as a potential divider if the input voltage needs adjusting. Some examples of the components used are as follows:

R400 R401 C400
Common 1V/Oct 1K 100K 68n
Nano 1V/Oct 100R 100K 68n
5V CV to 3V3 220K 330K 10n
5V CV to 3V3 22K 33K 10n

Note that in all cases D400 and D401 are BAT43 Schottky diodes.

When the ratio of R400 to R401 is close to 1, then essentially almost the whole voltage range, up to the clamped voltage rails, is used as input.

When the ratio of R400 to R401 is ~2/3 then the output voltage will be approx 3V3 (max) from a 5V input. There are two values that seem to be used: 22K to 33K or 220K to 330K.

I've since seen a note that R401 should really be between the external connection and R400 for 5V systems, which would remove the potential divider effect. This is shown below.

Whilst the board doesn't directly support this, it is possible to patch that in as shown below.

Note: any of the blue spots are GND connections and could be used. In fact, looking at the traces, it would be possible to swap R451 and C450 over, and the same for R401 and C400 - this would leave some spare GND pads where the capacitors were originally placed that could then be easily used for the moved resistors.

Whether this is actually required or not is left as an exercise for the reader - in other words, I'll get back to it after some experimenting!

Potentiometer Input

If a slightly more robust potentiometer input is required, then it is possible to use the CV input circuit without the clamp diodes and omitting R401 as follows:

In this case it would be recommended that R400 = 1K. HAGIWO suggests C400 = 100pF, but I've used 10nF for potentiometer smoothing before. Naturally a pot could just be wired directly to the microcontrollers analog inputs of course.

Aside: it is also possible to repurpose an OUTPUT stage for a potentiometer INPUT too as shown below:

But of course, in this case MCU_OUT_1 becomes an MCU_IN connection - a little confusion, but definitely possible. More on the OUTPUT circuits in a moment.

Second GATE and CV Input

Components R300-R302, D300 are repeated as R350-R352, D350 to give a second GATE input. Components R400, R401, C400, D400, D401 are repeated as R450, R451, C450, D450, D451 to give a second CV input. The relevant areas are shown below.

  • Gate 1 - Yellow
  • Gate 2 - Red
  • CV 1 - Purple
  • CV 2 - Blue

Once again, any unused sections can be omitted completely.

GATE and CV OUTPUTS

There are four generic OUTPUT circuits which could be used for either GATE or CV signals.

The key difference being that for a GATE OUTPUT, R501 and C500 can be omitted. D500 and D501 are BAT43 Schottky diodes once more. Some sample values and applications are shown below.

R500 R501 C500
GATE OUTPUT 470 - -
CV OUTPUT 470 - 4u7

R501 is not used in either of the above. Truth be told, I can't remember why I thought I ought to include it! I'll come back to this if I work it out 🙂

It does however leave the possibility that these nominally output circuits could be repurposed as additional inputs if required - with all the components fitted, it is essentially mirroring the CV input circuit discussed previously.

Four Output Stages

Each output stage is independent, and the relevant components are shown below. Once again, any unused sections can be omitted.

Key:

  • Output 1 - Yellow
  • Output 2 - Red
  • Output 3 - Purple
  • Output 4 - Blue

Closing Thoughts

This was never intended to be a completed board, it was always meant to make it easy to experiment with different options. The downside of that approach of course is that none of the circuits have really been tested yet at all, so it is all theory at this point.

But I think it should support that pretty well so am pretty pleased with how it turned out.

Kevin

Comment
Like
You can also reply to this email to leave a comment.

Simple DIY Electronic Music Projects © 2024.
Manage your email settings or unsubscribe.

WordPress.com and Jetpack Logos

Get the Jetpack app

Subscribe, bookmark, and get real‑time notifications - all from one app!

Download Jetpack on Google Play Download Jetpack from the App Store
WordPress.com Logo and Wordmark title=

Automattic, Inc.
60 29th St. #343, San Francisco, CA 94110

Posted by BigPalaceNews at 5:35 AM
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest

No comments:

Post a Comment

Newer Post Older Post Home
Subscribe to: Post Comments (Atom)

Search This Blog

About Me

BigPalaceNews
View my complete profile

Blog Archive

  • October (85)
  • September (112)
  • August (116)
  • July (96)
  • June (100)
  • May (105)
  • April (95)
  • March (131)
  • February (111)
  • January (104)
  • December (98)
  • November (87)
  • October (126)
  • September (104)
  • August (97)
  • July (112)
  • June (113)
  • May (132)
  • April (162)
  • March (150)
  • February (342)
  • January (232)
  • December (260)
  • November (149)
  • October (179)
  • September (371)
  • August (379)
  • July (360)
  • June (385)
  • May (391)
  • April (395)
  • March (419)
  • February (356)
  • January (437)
  • December (438)
  • November (400)
  • October (472)
  • September (460)
  • August (461)
  • July (469)
  • June (451)
  • May (464)
  • April (506)
  • March (483)
  • February (420)
  • January (258)
  • December (197)
  • November (145)
  • October (117)
  • September (150)
  • August (132)
  • July (133)
  • June (117)
  • May (190)
  • January (48)
Powered by Blogger.