PedalinoMini concept with BPI leaf ESP32 S3

[Jelle7and9]

Hello there,

This awesome project came by and now I'm planning to build my own PedalinoMini.
Nice job @alf45tar! Respect for all the coding.

I want to use this controller to control my THR10II amp via the THR remote app on my phone. This must be via BLE midi.
Second to control Amplitube 5 standalone and/or a DAW with VST plugins. Cubase AI was included by the THR amp.

I have finished my first controller with an arduino uno and a midi shield. Time for the next step.

So I made a design for a real controller powered by PedalinoMini.
The design is based on the dimensions of the THR amp.
Furthermore I add the typical THR grid to the front of the controller with a led behind. To get some tube power effect.
The top view is a basis 10 button concept, with momentary soft switches accompanied by vector based guitar pics and a RGB led.
The backside has different connections, some are optional for me.
Antenna, DC power, Midi thru are not that important to me. But I want it to be possible direct or in the future.
USB out is for connecting an powering a device like my phone or a tablet. This is handy for controlling via the THR app. I also can use my phone for duplicating the computer screen via Spacedesk. So I have visual on Amplitube and/or the DAW. I tested this with my android phone and a old android 9" tablet. Works like a charm.
The box will probably be build with wood. Specials images and text could be lasered.

I ordered a BPI leaf ESP32 S3 and a oled display and a bunch of stuff. Waiting for delivery and a holiday ahead.

But what wil you think guys;
Midi DIN vs 1/8 or 1/4 jack for midi in/out?
5mm (adressable) leds in a led holder or 2812 LED with a lens/reflector?
Hardware button to change midi polarity? I'm a hardware man thus like buttons en lights. Probably I end up with one footpedal.
Are some boot and reset buttons necessary?
Any tips or most common fails tho avoid?
Some rotary encoders/ potentiometers? I t would be nice if I can skip through an dial in some settings in the THR remote app.
Is it possible to make the controller be recognized as an iRig Stomp for example? I've read that there is an iRig blueboard config. How does this works?

[jaylfc]

Looks awesome!

[Jelle7and9]

Thanks!

[Jelle7and9]

So, I've got the most parts deliverd.

I can say that the OLED with the SPD0301 ic works with SSD1306/SH1106 and U8g2 libraries.
I choose this OLED because 1.54" looks like the perfect size for my project and it has an certain thickness. I hope it will fit nice and flat in the housing. Also the 5mm LEDs with the WS2812 ic build inside looks promising.

This is my first electronics project ever so hopefully I can fix this. I just started with prototyping.

To be continued

[Designbase]

Where did you get the display from? The housing seems perfect to attach to a enclosure

[Jelle7and9]

https://a.aliexpress.com/_msOESBc

[Wapata]

Hi !
So far it look really promising.
So here is my advice : make your first unit with strictly what you need (if no hardware midi is mandatory, skip them). It's cheap enough to make an other one if you want to do other things later.

I've made an all in one, and I see that it will not be easy to change Banks on the fly because they do very different things....

[Jelle7and9]

Up and running for testing.
Managed to build 3.1.9 firmware with VSC + Platformio and upload it via USB connection with the PedalinoMini installer.

[Jelle7and9]

Testing and prototyping with the ESP32 board. ( 3.1.10 )
Last day's I added a 18650 battery + RGB 5V leds + boost convertor 5V + power on led.
On battery power there's no 5V on the 5V pin, only when USB powered. So to let the leds work with the 3.3V logic a boost convertor is needed.

To figur out:

1. How to connect and config rotary encoder and potentiometer -> any tips?
2. Get the right battery voltage levels. These levels are not corresponding with my multimeter.
   Also when BATTERY_PIN is connected to battery + the battery indicator keeps blinking like charging.
3. Amount of connected LEDs are not changeable in WebUI. Only in pedalino.h ?
4. Custom image's possible on oled?
5. Options for 3D printing of the housing. I have an Ultimaker 2+ at work, but it has a limited build volume of 223 x 220 x 205 mm (8.7 x 8.6 x 8 inches)
6. Better understanding different button connections, pinouts and configurations.

Pedalino.h config:
#elif defined ARDUINO_BPI_LEAF_S3
#undef LEDS
#define LEDS 4
#undef PEDALS
#define PEDALS 9
const byte pinD[] = {GPIO_NUM_1, GPIO_NUM_2, GPIO_NUM_3, GPIO_NUM_4, GPIO_NUM_5, GPIO_NUM_6, GPIO_NUM_7, GPIO_NUM_8, GPIO_NUM_0};
const byte pinA[] = {GPIO_NUM_11, GPIO_NUM_12, GPIO_NUM_13, GPIO_NUM_14, GPIO_NUM_46, GPIO_NUM_47, GPIO_NUM_17, GPIO_NUM_18, GPIO_NUM_0};
#define FACTORY_DEFAULT_PIN GPIO_NUM_0 // Button BOOT
#define DIN_MIDI_IN_PIN GPIO_NUM_44
#define DIN_MIDI_OUT_PIN GPIO_NUM_43
#define BATTERY_PIN GPIO_NUM_14 // Pin connected to +BATT
#define FASTLEDS_DATA_PIN GPIO_NUM_48
#undef SDA
#undef SCL
#define SDA GPIO_NUM_15 // standard I2C pin of onboard connector
#define SCL GPIO_NUM_16 // standard I2C pin of onboard connector

20230927_181602.mp4

[Wapata]

Point number five : https://formlabs.com/blog/how-to-create-models-larger-than-your-3d-printers-build-volume/
;-)

[jisv48]

How will you be charging the battery? are you incorporating a charger for the Lithium batt? Your project looks great, by the way what happen with the Pedalino case? who will be selling them? Cheers

…

On Sep 18, 2023, at 1:01 PM, Jelle7and9 ***@***.***> wrote: Up and running for testing. Managed to build 3.1.9 firmware with VST + Platformio and upload it via USB connection with the PedalinoMini installer. <https://user-images.githubusercontent.com/137293236/268746826-ac1617c2-8601-4bbf-9671-56d74508043e.png> — Reply to this email directly, view it on GitHub <#454 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQTZIQCHURH7HRVBP4FJUSTX3CLARANCNFSM6AAAAAA2LPQX4I>. You are receiving this because you are subscribed to this thread.

[Jelle7and9]

There is a charging ic /circuit onboard

[Jelle7and9]

@alf45tar

I am still learning all the possibilities in the WebUI to control Amplitube and Yamaha THR remote App. Both programs use CC commands. Although Amplitube has PC commands only for presets selection (1 - 128)

I can set on/off to pedals or changing knobs with an potentiometer. So far so good.

What I didn't can is implement and use a rotary encoder (20 pulses). How to connect these 3 pins? (Pin A,B and button pin)
The following site explains how to use rotary encoders and only use 1 analog pin. Perhaps you already have some thoughts or experience with this?
https://www.elektormagazine.nl/labs/rotary-encoder-on-a-single-mcu-pin

Is it some way possible to use 1 or 2 rotary encoders or potentiometers and knobs to assign midi cc commands to THR remote APP?
So different CC commands for applying on/off effects , adjust values, toggle through cabinets or effects -> toggle spring/room/plate/hall for reverb for example. It would be nice if the PedalinoMini can control al the parameters with only 1 or 2 knobs/encoders. So you can dial in some tones on the PedalinoMini instead of using a PC . Using a mouse for rotating knobs is not so fine.
There are so many functions, pedals, control, actions and sequences. But get them programmed well is another story.
Perhaps you can give me an direction how to use all the options in the right manner.

Thank you in advance

[alf45tar]

Rotary encoders are supported since long time by PedalinoMini. They are called Jog wheel. Check the schematic for connection.

[jisv48]

Hi alf45Star, What is the status of Enclosures for the original Pedalino, are you going to sell them? if so how do we order them and the cost per unit? Thanks in advance for your assistance Cheers

…

On Oct 13, 2023, at 1:51 PM, alf45tar ***@***.***> wrote: Rotary encoders are supported since long time by PedalinoMini. There are called Jog wheel. Check the schematic for connection. — Reply to this email directly, view it on GitHub <#454 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQTZIQCYMB3WMYIDSQWBXCLX7GLSJANCNFSM6AAAAAA2LPQX4I>. You are receiving this because you commented.

[alf45tar]

No plan. Do you need the 3D printed case or all the components too?

[jisv48]

The 3D printed case. I have already assembled the PedalinoMini on a breadboard, it will be easy to move the parts there. Thanks

…

On Oct 13, 2023, at 1:56 PM, alf45tar ***@***.***> wrote: No plan. Do you need the 3D printed case or all the components too? — Reply to this email directly, view it on GitHub <#454 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQTZIQHMRTKDKMQ77U4FERTX7GMIDANCNFSM6AAAAAA2LPQX4I>. You are receiving this because you commented.

[alf45tar]

Did you tried to get a quotation from an online 3D printing service?

[jisv48]

Well, I probably did, but that was long ago. I’ll look into that. Thanks

…

On Oct 13, 2023, at 2:06 PM, alf45tar ***@***.***> wrote: Did you tried to get a quotation from an online 3D printing service? — Reply to this email directly, view it on GitHub <#454 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQTZIQAQ2H4YQ57HWZAXDTLX7GNNTANCNFSM6AAAAAA2LPQX4I>. You are receiving this because you commented.

[alf45tar]

I can print for you for 30 EUR + shipping but I prefers you go to a professional 3D printing service.

[Jelle7and9]

I designed a smaller version 200x115mm. today.

[Jelle7and9]

@alf45tar
Do you have tips for setting up 3D printing / CURA in general?
I assume you print your PedalinoMini body upside down. Do you use any sort of support type or do you use infills?
What is you're experience with wall thickness, strength and warping? Case1 looks very robust!

[alf45tar]

I printed it upside down of course. Supports are requested for the ceiling of ESP32 slot.
I am using low quality setting of CURA and they are enough for me. The case is very robust with 20% of infill.

[Jelle7and9]

Thanks!

[Jelle7and9]

Raining day........
Update design

[Jelle7and9]

Black Friday deals, I ordered a Bambu Lab P1S printer for the Christmas holiday. So now time to learn more about support settings and so on. And make a choice for filament and color.
And making up an excuse to my wife, ADHD will not be enough 😆

[Jelle7and9]

I printed the enclosure last week and fitted the first parts. Everything looks good and the dimensions are perfect. Hopefully I can soon soldering it all together.
You see at the back tactile buttons for reset and boot, switch to disconnect the battery, USB C, 2x TRS 1/4" and 2x female DIN 5. Screen is 1.54 OLED and 8x momentary footswitches.
To be continued....

[jisv48]

Excellent job, looks great. congratulations.

…

On Nov 27, 2023, at 9:18 AM, Jelle7and9 ***@***.***> wrote: Bambu Lab P1S printe

[Jelle7and9]

@alf45tar
I build with the latest firmware 3.2.1 via the webtools installer. (BPI Leaf S3)
Config for now is: (pedal 5 and 6 set to none in the WebUI)

I can't use A14 as battery_pin and analog_pin for pedal 4 at the same time. The button gives no response, as it has 2 analog functions?
Also pin 15/16 the SDA and SCL pins are also set to A5 and A6. Simple solution to free ADC pins from pinD array? And put non ADC GPIO's there instead? > Update: looks to work with: D4(21) A4(7), D5(35) A5(6), D6(36) A6(5), <
Log from Pedal 4;

So I wonder if pins 35-42 are for example usable?
I have BPI Leaf S3 and it has Quad Flash and not Octa Flash, wich could add the use of pins 33-37
For as far I understand USB serial/JTAG only needs 19, 20 for D- and D+ and GND + Vcc.
So in my theory without many knowledge of EPS32 pins, all did I read some documentation.
Complete rearrangement of pin settings with a total of 13 pedals, Analog pins are ADC1 or ADC2.
Midi TX/RX to pin 21 and 47.
I did not used pin 3, 14, 15, 16, 19, 20, 45, 46.
Are these pin settings possible? That would give a lot more options.

const byte pinD[] = {GPIO_NUM_41, GPIO_NUM_42, GPIO_NUM_43, GPIO_NUM_44, GPIO_NUM_35, GPIO_NUM_36, GPIO_NUM_37, GPIO_NUM_38, GPIO_NUM_39, GPIO_NUM_40, GPIO_NUM_17, GPIO_NUM_18, GPIO_NUM_0};

const byte pinA[] = {GPIO_NUM_11, GPIO_NUM_12, GPIO_NUM_13, GPIO_NUM_4, GPIO_NUM_5, GPIO_NUM_6, GPIO_NUM_7, GPIO_NUM_8, GPIO_NUM_9, GPIO_NUM_10, GPIO_NUM_1, GPIO_NUM_2, GPIO_NUM_0};

The goal for me now is 8 Momentary_1 pedals + 2x Analog TRS inputs.
And it would be nice if SLOTS are freely assignable, or at least to different buttons in the same pedal.
With 4 x Momentary_2 only the fist button can be in the SLOT name. #434
And a possibility to chose between 3 or 4 SLOT_COLS would be nice also.

[alf45tar]

What do you think to define like of this?

#elif defined ARDUINO_BPI_LEAF_S3           // https://wiki.banana-pi.org/BPI-Leaf-S3
#undef  PEDALS
#define PEDALS                9
// https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-reference/peripherals/gpio.html
// Strapping pins: 1, 3, 45, 46
// ADC1:    1-10
// ADC2:   11-20 (19=D- 20=D+) (ADC2 module is also used by the Wi-Fi)
// SPI0/1: 26-32 (usually used for SPI flash and PSRAM)
// SPI0/1: 33-37 (on boards embedded with ESP32-S3R8 / ESP32-S3R8V chip, GPIO33~37 are also not recommended for other uses)
const byte pinD[] = {GPIO_NUM_38, GPIO_NUM_39, GPIO_NUM_40, GPIO_NUM_41, GPIO_NUM_42, GPIO_NUM_43, GPIO_NUM_44, GPIO_NUM_2, GPIO_NUM_0};
const byte pinA[] = {GPIO_NUM_4,  GPIO_NUM_5,  GPIO_NUM_6,  GPIO_NUM_7,  GPIO_NUM_8,  GPIO_NUM_9,  GPIO_NUM_10, GPIO_NUM_2, GPIO_NUM_0};
#define FACTORY_DEFAULT_PIN   GPIO_NUM_0    // Button BOOT
#define DIN_MIDI_IN_PIN       GPIO_NUM_21
#define DIN_MIDI_OUT_PIN      GPIO_NUM_47
#define BATTERY_PIN           GPIO_NUM_14   // Pin connected to +BATT
#define FASTLEDS_DATA_PIN     GPIO_NUM_48
#undef  SDA
#undef  SCL
#define SDA                   GPIO_NUM_15
#define SCL                   GPIO_NUM_16

[Jelle7and9]

Hi Alf45tar,
That code would work, although A8 GPIO_NUM_2 can be set to GPIO_NUM_11

I did tried the code below already for a 9 pedal version. That works fine as far I can tell. I think using ADC2 pin 35-37 as digital input is not a problem. All the buttons works as to be aspected in a 4x Momentary_2 + 1x Jogwheel breadboard testbuild.

I also introduced a 13 pedal alternative, the PedalinoXTREME 😎 🤘
Not tested yet, but it has potential. For example, 13 controller ports x 6 switches ladder = 78 switches or 13 rotary encoders.
You will need an extra leg or band member to master the PedalinoXTREME 😋

Even strapping pins 45 and 46 can be added as digital I/O pin as long as they are LOW at startup/after reset.
All strapping pins have latches. At system reset, the latches sample the bit values of their respective strapping
pins and store them until the chip is powered down or shut down. The states of latches cannot be changed in
any other way. It makes the strapping pin values available during the entire chip operation, and the pins are freed
up to be used as regular IO pins after reset.
Regarding the timing requirements for the strapping pins, there are such parameters as setup time and hold time.

// --------------------------------------------------------------------------
#elif defined ARDUINO_BPI_LEAF_S3           // https://wiki.banana-pi.org/BPI-Leaf-S3
#undef  PEDALS
#define PEDALS                13
// https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-reference/peripherals/gpio.html
// Strapping pins : 1, 3, 45, 46
// Default pins   : 14 to +BATT, 15 SDA, 16 SCL, 0 BOOT, 3 RESET
// USB JTAG : 19=D-, 20=D+
// ADC1     :  1-10
// ADC2     : 11-20 (Espressif 4.x ADC2 has hardware limitations when also used by Wifi, usable between wifi(stop) and wifi(start)
// ADC2     : 11-20 (Espressif 5.x introduced oneshot_read instead of continious_read as workaround)
// SPI0/1   : 26-32 (NOT recommended, used for SPI flash and PSRAM)
// SPI0/1   : 33-37 (BPI LEAF S3 is not embedded with ESP32-S3R8 / ESP32-S3R8V chip, GPIO33~37 are fine for input pins) *note; pin 33 and 34 are not present

// ** PedalinoMini STANDARD: 9 PEDALS **
// Shown in WebUI as | Pedal 1,   | Pedal 2,   | Pedal 3,   | Pedal 4,   | Pedal 5,   | Pedal 6,   | Pedal 7,  |  Pedal 8,  | Pedal 9, | 
const byte pinD[] = {GPIO_NUM_10, GPIO_NUM_9,  GPIO_NUM_8,  GPIO_NUM_21, GPIO_NUM_35, GPIO_NUM_36, GPIO_NUM_4,  GPIO_NUM_2,  GPIO_NUM_0, GPIO_NUM_0, GPIO_NUM_0, GPIO_NUM_0, GPIO_NUM_0};
const byte pinA[] = {GPIO_NUM_11, GPIO_NUM_12, GPIO_NUM_13, GPIO_NUM_7,  GPIO_NUM_6,  GPIO_NUM_5,  GPIO_NUM_17, GPIO_NUM_18, GPIO_NUM_0, GPIO_NUM_0, GPIO_NUM_0, GPIO_NUM_0, GPIO_NUM_0};

// ** ALTERNATIVE the PedalinoXTREME: 13 PEDALS **
//Shown in WebUI as   | Pedal 1,   | Pedal 2,   | Pedal 3,  |  Pedal 4,   |  Pedal 5,   |  Pedal 6,   |  Pedal 7,   | Pedal 8,   | Pedal 9,   | Pedal 10   | Pedal 11   | Pedal 12   | Pedal 13  | 
//const byte pinD[] = {GPIO_NUM_41, GPIO_NUM_42, GPIO_NUM_43, GPIO_NUM_44,  GPIO_NUM_35,  GPIO_NUM_36,  GPIO_NUM_37, GPIO_NUM_38, GPIO_NUM_39, GPIO_NUM_40, GPIO_NUM_17, GPIO_NUM_18, GPIO_NUM_0};
//const byte pinA[] = {GPIO_NUM_11, GPIO_NUM_12, GPIO_NUM_13, GPIO_NUM_4,   GPIO_NUM_5,   GPIO_NUM_6,   GPIO_NUM_7,  GPIO_NUM_8,  GPIO_NUM_9,  GPIO_NUM_10, GPIO_NUM_1,  GPIO_NUM_2,  GPIO_NUM_0};

#define FACTORY_DEFAULT_PIN   GPIO_NUM_0      // Button BOOT
#define DIN_MIDI_IN_PIN       GPIO_NUM_44     // (RX, if PedalinoMini STANDARD)
#define DIN_MIDI_OUT_PIN      GPIO_NUM_43     // (TX, if PedalinoMini STANDARD)
//#define DIN_MIDI_IN_PIN       GPIO_NUM_21     // (RX, if PedalinoMini XTREME)
//#define DIN_MIDI_OUT_PIN      GPIO_NUM_47     // (TX, if PedalinoMini XTREME)
#define BATTERY_PIN           GPIO_NUM_14     // Pin connected to +BATT, connected to onboard MX 1.25mm 2-Pin Socket
#define FASTLEDS_DATA_PIN     GPIO_NUM_48
#undef  SDA
#undef  SCL
#define SDA                   GPIO_NUM_15   // Default pin, also connected to onboard JST SH 1mm 4-Pin Socket (I2C), if you don't use the socket feel free to change
#define SCL                   GPIO_NUM_16   // Default pin, also connected to onboard JST SH 1mm 4-Pin Socket (I2C), if you don't use the socket feel free to change
// --------------------------------------------------------------------------

I think schema.json needs to be updated to accept more pedals?

PedalinoMini/data/schema.json

Line 405 in a801ccf

"maxItems": 9,

PedalinoMini/data/schema.json

Line 411 in a801ccf

"enum": [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12]

PedalinoMini/data/schema.json

Line 467 in a801ccf

"enum": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12]

PedalinoMini/data/schema.json

Line 475 in a801ccf

"enum": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12]