CTR2-MIDI
Operation Manual
v1.02.00










Last Revision: September 30, 2024
Copyright 2024 – Lynovation.com
All rights reserved
Updated to firmware v1.02.00
Revised sections for this version are highlighted in yellow



Contents
Introduction	4
Legal Notice	5
How to use this manual	5
Change Log	6
v1.02.00	6
Hardware	6
Connecting CTR2-MIDI to Your App	7
Remote Ham Radio	7
Marcus’ Apps for iOS or MacOS	7
Enable Permissions	7
Select the CTR2-MIDI Device	7
CTR2 Controller Screen	8
Windows Applications	9
Thetis	9
CTR2-MIDI Options	10
Beep Mode (MFB1+Encoder)	10
Speed Tuning Mode (MFB2+Encoder)	10
Encoder Map (MFB3+Encoder)	10
Announce Option Settings (MFB4+Encoder)	11
Bluetooth Radio Power (MFB6+Encoder)	11
CTR2-MIDI Controls	12
Multi-Function Buttons (MFBs)	12
Encoder Functions	12
Encoder Mode Indications	13
Paddle Mode	13
Mapping for Remote Ham Radio	14
Keying Input	14
Encoder Control	14
Button Controls	14
Mapping for iOS and MacOS Apps	15
Editing the CTR2 Controller Map	15
Mapping Functions to Controls	15
Using Paddles with the App’s Keyer	16
Using a Straight Key or PTT Switch	16
Mapping For Thetis	17
Mapping Controls	17
Advanced Options	19
Operation with N1MM Logger+	19
Troubleshooting	20
Appendix A: Advanced MIDI Configuration	22
Terminal Display	22
Device Names	22
Encoder Mode	23
Paddle Mode	23
Beep Mode	23
Speed Tuning	23
Encoder Map	23
Report Options	23
Edit Encoder Map	23
Bluetooth Pwr	25
Recalibrate Buttons	25
Reset to Factory Settings	25
Appendix B: Using CTR2-MIDI Firmware on CTR2-Micro	26
Flashing the Firmware	26
Operating the Micro with MIDI Firmware	27
Appendix C: Installing or Updating CTR2-MIDI Firmware	28
Installing using Linux or Mac	30
Appendix D: Configuring Tera Term	31
Appendix E: Configuring Putty	32
Serial Session	32
Appendix F: Change Log	34



Introduction
CTR2-MIDI (called the MIDI in this document) is a custom MIDI controller designed for ham operators. It supports both USB and Bluetooth-LE MIDI connections. It is an ideal companion for all of Marcus Roskosch’s (DL8MRE) apps for iOS and MacOS and is also at home working with Thetis or Simon Brown’s SDR-Console to control your Apache Labs ANAN or Hermes Lite 2 (among others) on your Windows computer. It’s also a great addition for those that use Remote Ham Radio.
MIDI commands sent by the MIDI can be used to change frequency, mode, volume, CW speed, control the keyer and PTT, and many other functions in the app. The MIDI only sends commands to the app. It has no idea what the app or radio is doing.
The app manages the user interface and the connection to the radio. The MIDI can be powered from the computer’s USB port, and iOS device’s accessory jack using an OTG adapter (also referred to as a Camera Adapter) , a 5 volt cell phone charger, or a USB battery pack making the MIDI an idea companion for portable operation. You can turn the Bluetooth radio off to conserve battery power when using USB MIDI.
The MIDI can use USB MIDI when powered by the device running the app. If the MIDI is powered separately you can use Bluetooth-LE MIDI to connect it to the app. 
This photo shows the MIDI controlling SmartSDR for iOS while being powered by the phone though a Lightning OTG adapter. A charger or USB battery can be connected to the OTG adapter’s Lightning power jack to power both devices. The Bluetooth radio can be turned off in this configuration to conserve battery power.
The MIDI includes the following features:
1. USB MIDI and Bluetooth-LE MIDI connections are supported. 
2. Turn the Bluetooth radio off to save 50 mA of current draw for battery operation.
3. Three button/encoder beep modes, off, normal, or long-press only.
4. Two proportional (speed) tuning speeds on WheelA.
5. Two maps to customize the MIDI controls assigned to each encoder mode.
6. Four encoder modes control a total of 8 “Wheel” or “Slider” parameters for tuning, volume control, etc.
7. Six dual-mode pushbuttons. Each button can be assigned to the short-press and a long-press function.
8. 3.5mm (1/8”) stereo input jack allow you to use your paddles to control the keyer, straight key, or PTT in the app (not all apps support all modes). 
9. Power the MIDI from any USB 5 volt power source; computer USB port, cell phone charger, USB battery, or through an OTG adapter on your mobile device.
10. Firmware updating is done through the USB-C port.
Legal Notice
What would a manual be without a legal notice? Here goes…
• This is a hobby endeavor. Nothing is guaranteed! Use this device at your own risk!
• I will do my best to make sure you receive functioning hardware if you buy the assembled unit and will work with you if there is a problem with your unit on arrival.
• I cannot guarantee or warranty the hardware supplied in the kit.
• I make no warranty that the firmware provided for CTR2-MIDI will perform up to your expectations or be suitable for your application. Software bugs are a fact of life and I try to find and correct all bug reports to the best of my ability ASAP. 
How to use this manual
This manual should be used as a reference manual. An expanded Help system if you will. Items in the Table of Contents link to their write up in the manual. The main categories have short write ups describing the functions available in that section. I’ve tried to group things logically and have added hyperlinks so you can quickly jump to other sections.
As this document evolves, sections that have changed since the last update will be highlighted in yellow.
The version number of this manual will follow the latest released version number of the firmware.
Feel free to contact me if you have question about a certain feature or have ideas for future improvements. I love to get feedback on my work. My email addre1ss is good on QRZ.com.


Change Log
v1.02.00
This update adds many new functions to the MIDI:
• Three beep modes – Off, Normal, and Long-Press. Press and hold MFB1 then press the encoder to step through the beep modes.
• The ability to enable or disable speed (proportional) turning on WheelA control. Press and hold MFB2 then press the encoder to step through the speed modes, Off, Normal, and Fast.
• Support for two MIDI encoder maps. Use one for iOS/Mac operations and one for Windows operations. Press and hold MFB3 then press the encoder to switch the maps.
• The ability to turn the Bluetooth radio off for battery operation. Press and hold MFB6 then press the encoder to turn the radio on or off.
• A Reset to Factory Settings option when all else fails. You must connect a terminal to the MIDI to reset the settings to factory.
Changes to previous versions can be found in Appendix F.
Hardware
The MIDI uses a 60mm x 60mm x 20mm enclosure. This form factor is the perfect size for a busy operating desk or for portable operation.
As shown in the photo, the encoder knob is the predominant feature on the face of the unit. When oriented with the USB-C connector and paddle jack as shown the two LEDs in the upper left corner show the encoder mode with the lower LED having a value of 1 and the upper LED having a value of 2. Both LEDs will be off when the encoder is in its Home mode. Short-pressing the encoder steps you through encoder modes 1, 2, 3, and back to Home. In the photo above the encoder is in mode 1.
The green LED flashes once every 5 seconds if the Bluetooth radio is turned off. It flashes once every 2 seconds when the unit is first powered up and the Bluetooth radio is turned on. It changes to two flashes every second when the unit is connected via Bluetooth-LE to the app. It is on all the time when you enter the Extended paddle mode.
The multi-function buttons (MFBs) are laid out around the circumference of the knob. MFB1 is on the upper left, just below the encoder mode LEDs. The buttons are numbered counter-clockwise around the knob ending with MFB6 on the upper right. Short and long-press functions allow you to control two MIDI Button functions with each button.
You’ll find the USB-C and 3.5mm (1/8”) stereo Paddle Input jack on the top edge in the photo.

Connecting CTR2-MIDI to Your App
This section describes how to connect the MIDI to various apps. Once you are connected to the app see the CTR2-MIDI Controls section to understand how the MIDI controls work with the app.  
Remote Ham Radio
To connect the MIDI to Remote Ham Radio simply plug the MIDI into a USB port on your computer then select the CTR2-MIDI option in the RHR console’s Tool menu. This option is pre-configured for the MIDI so it’s plug-and-play. You can see how the MIDI’s controls are mapped to RHR in the Remote Ham Radio Configuration section.

Marcus’ Apps for iOS or MacOS
Enable Permissions
If you plan on using Bluetooth with Marcus’ apps, open the app’s Settings window and allow the app to access Bluetooth. 




You can also allow the app to use your iCloud Drive to save maps in this window.
Select the CTR2-MIDI Device
In Marcus’ apps, select the CTR2 Controller device in the Tools menu. The Tools menu will look different in each app so just look for the CTR2 Controller.
Here’s an iOS and MacOS example of the Tools menu. I’ve highlighted the CTR2 Controller option in each menu…
CTR2 Controller Screen
Once you select CTR2 Controller from the Tools menu a screen like this will appear. It may look different depending on the Apple device you’re using but it has basically the same information.
Make sure your MIDI is powered up. The green LED should be flashing once every two seconds if the Bluetooth radio is on, or once every 5 seconds if it is off.
USB Wired Connection
To use the MIDI with a wired USB connection on Mac’s and newer iOS devices, connect the MIDI to your device using a USB data cable, select XAIO_ESP32-S3 from the Device menu, and click the Enabled button. The Status should change to Connected. Press the Edit Mapping button and press a button or turn the encoder to verify the app is receiving MIDI commands.

NOTE: To use a wired USB connection with an older iOS device (with a Lightning connector) you’ll need to purchase a Lightning OTG (On The Go) adapter such as the one shown here. These are also referred to as “Camera Adapters” on Amazon. The adapter I use has two USB-A connectors on it. It also has a Lightning port so you can connect a wall charger or battery to power your phone and MIDI.
Bluetooth-LE Connection
To use Bluetooth-LE MIDI, make sure the Bluetooth radio is on (green LED flashes every 2 seconds) then click the Find CTR2 Bluetooth-LE Device link to initiate a search for your MIDI. The search will fail the first time you try to access a new device. If you get a failure notice, close the failure popup notification, wait 10 seconds, then click the Find link again. Once it registers your MIDI (your MIDI’s device name is written on the bottom label if you bought an assembled unit) click the Enabled button to start the Bluetooth connection. You don’t need to select the MIDI’s name on the Device list unless you have two or more MIDI units available. (You can only use one MIDI at a time but you can use a separate wired USB MIDI device such as a DJ2GO along with the MIDI.)

NOTE: v1.02 firmware gives you to option of turning off the Bluetooth radio. If the radio is off the green LED flashes once every 5 seconds. To turn it on press and hold MFB6 then press the encoder. You should hear “BLE 1” in Morse code then the unit will start beeping once a second. Cycle power on the unit to restart it with the Bluetooth radio on. 
If you can’t get the app to connect to MIDI you probably haven’t allowed the app to use Bluetooth (see Enable Permissions above). If you still can’t get it to connect, download MIDI-Wrench or midimittr for iOS or Conji for the Mac from the App store. They are free apps used to troubleshoot BLE MIDI issues. Connect to the MIDI with one of these apps first and then try to connect to the MIDI again in the radio control app.

Windows Applications
Thetis
Windows only supports USB MIDI connections. When you connect the MIDI to your Windows computer’s USB port it will automatically register as a MIDI device and be assigned a virtual COM port. Windows does not support Bluetooth-LE MIDI (at least not very well).
NOTE: USB MIDI requires a USB-C data cable. USB-C power cables will not work!
Most Windows apps will need to be configured (i.e. mapped). Thetis is used as an example here but connecting to and mapping controls in other apps should be similar.
Additional information on mapping MIDI controls in Thetis can be found here.
Start by selecting the Settings menu on the main page in Thetis then select the Serial/Network/MIDI CAT tab. Click the MIDI tab as shown above.
Next, click the Configure MIDI button to open the Midi Controller Setup page. The program should go through an initialization sequence and end up on this page if it finds the MIDI on USB. The tab at the top should be labeled CTR2-MIDI or possibly ESP32S3. If the initialization fails, double-check that you are using a USB-C data cable, not a charge cable and try again. 




CTR2-MIDI Options
Now that you have the MIDI connected to your app, it’s time to go over the various options available in the MIDI.
Beep Mode (MFB1+Encoder)
You can control when the MIDI beeps. Normally, it beeps whenever you press a button or the encoder. This lets you know that you’ve changed something in the app. You may prefer the MIDI remains quiet all the time or only beep when you long-press a button or the encoder.
To change the Beep mode press and hold MFB1 then press the encoder. The new Beep mode will be announced in Morse code as follows:
• “B 0” = Beep mode is off. All LEDs will briefly flash when you long-press a button or the encoder.
• “B 1” = Beep mode is normal. The MIDI will beep with every button or encoder press.
• “B 2” = Beep mode is long-press. The MIDI will beep only when you long-press a button or the encoder.
Speed Tuning Mode (MFB2+Encoder)
Speed (proportional) tuning is supported when WheelA is selected as the MIDI control assigned to the app’s tuning function. You can select from two speeds or turn speed tuning off.
To change the Speed mode press and hold MFB2 then press the encoder. The new speed mode will be announced in Morse code as follows:
• “S 0” = speed tuning is off
• “S 1” = speed tuning is set to medium speed
• “S 2” = speed tuning is set to fast speed
Encoder Map (MFB3+Encoder)
The MIDI supports two encoder maps. This allows you to configure the MIDI for different apps depending on your needs. Map 1 is the default and is configured to work with Marcus’ iOS/MacOS apps and RHR. It uses WheelA for tuning. Map 2 is configured for Thetis and uses WheelB for VFO A and VFO B tuning control.
To change maps press and hold MFB3 then press the encoder. The new map will be announced in Morse code as follows:
• “M 1” = Map 1 is active
• “M 2” = Map 2 is active
Announce Option Settings (MFB4+Encoder)
To hear a Morse report of all of the option setting press and hold MFB4 then press the encoder. You can stop the report by pressing any button.
Bluetooth Radio Power (MFB6+Encoder)
You can turn off the Bluetooth radio on the MIDI if you are using a wired USB connection. This is particularly handy when powering the MIDI from a battery operated device such as an iPhone or iPad. When the radio is off the MIDI draws around 43 mA. When it is on the current draw is around 93 mA.
To toggle the power on the Bluetooth radio press and hold MFB6 then press the encoder. The radio’s state will be announced in Morse code as follows:
• “BLE 0” = Bluetooth radio is off
• “BLE 1” = Bluetooth radio is on
Once the Morse announcement completes the MIDI will start beeping once per second. This tells you that the MIDI is waiting for you to cycle the power to change the radio setting. The radio can only be enabled or disabled during the startup process.
If the Bluetooth radio is off the green LED will flash once every 5 seconds. If it is on, but not connected to your app, the green LED flashes once every 2 seconds. When connected to your app the green LED flashes twice every second.


CTR2-MIDI Controls
The MIDI sends MIDI commands to the app when the buttons are pressed or the encoder is turned. This section will describe the various controls available.
Multi-Function Buttons (MFBs)
Buttons are laid out counter-clockwise around the encoder knob starting with MFB1 on the upper left and ending with MFB6 on the upper right of the knob.

Buttons send the MIDI NoteOn command when the button is released. 
Each button has two functions defined by the amount of time you hold the button down. 
Short-pressing (i.e. less than 1 second) a button produces one beep (if Beep mode is set to Normal) when pressed and sends the associated MIDI NoteOn command when released. The MIDI NoteOn control # will be from 1 to 6 depending on which button was pressed.
Long-pressing a button (holding it down longer than 1 second but less than 3 seconds) produces another beep to indicate when it enters long-press mode if Beep mode is set to Normal or Long-Press. If Beep mode is Off all the LEDs will briefly flash when entering long-press mode. Upon button release the associated MIDI NoteOn command is sent. The NoteOn control will be from 11 to 16 depending on which button was pressed.
NOTE: Holding a button longer than 3 seconds cancels the button press and sounds a third low frequency beep if Beep mode is Normal or Long-Press. There is no indication if Beep mode is Off.
MIDI NoteOn commands can be mapped in the app to toggle functions such as Band Up, Band Down, Mode Up, Mode Down, etc.

NOTE: The MIDI does not receive updates from the controls it’s mapped to in the app. If you change a value with the MIDI, then change it manually in the app, the next time you change it in the MIDI it will send the new value based on the last value the MIDI sent, not the value you manually set in the app.
Encoder Functions
The encoder has four modes. Each mode has a turn and a press and turn function for a total of eight functions. Encoder modes are selected by short-pressing the encoder. The yellow LEDs indicate the selected mode. Both LEDs will be off in the encoder’s Home mode. 
The encoder can be used for tuning or changing parameters like volume, bandwidth, CW speed, etc. WheelA or WheelB are used for tuning (depending on the app). Most other controls use SliderA which acts like a potentiometer. SliderB is used for RIT and XIT controls. It beeps at the ends of the range and it beeps and pauses when you hit the middle of the range (where RIT and XIT are off). Although not generally used, there is a Button option. This can also be used for tuning if you app supports up and down buttons for frequency control.
The encoder functions are covered in the Encoder Modes in Appendix A. You must define the MIDI control you want the MIDI to use for each encoder mode with a terminal program before you map the MIDI controls in your app.
MIDI supports two encoder maps so you can configure one map for RHR and Marcus’ iOS/MacOS apps and one map for Thetis or other Window apps. Press and hold MFB3 then press the encoder to toggle the encoder map.
NOTE: The MIDI always sends commands on MIDI Channel 1.
Encoder Mode Indications
Long-pressing the encoder while in Mode 1, 2, or 3 will return you back to the encoder Home mode (all LEDs off) and sounds a single high frequency beep if Beep mode is set to Normal or Long-Press. Long-pressing the encoder in the encoder Home mode toggles the Paddle Mode.

Encoder Mode
LED
Beep Tone on
Selection
MIDI Control Change
Home


Single high frequency  beep
Encoder Turn = CC 100
Press & Turn =  CC 101
1


Single low frequency beep 
Encoder Turn = CC 102
Press & Turn =  CC 103
2


Two low frequency beeps
Encoder Turn = CC 104
Press & Turn =  CC 105
3


Three low frequency beeps
Encoder Turn = CC 106
Press & Turn =  CC 107

Paddle Mode
The MIDI has two Paddle Modes, Normal and Extended. These modes allow you to map different functions to the paddle input jack on the MIDI depending on your needs. The Paddle Mode is indicated by the green LED. The table below explains the two modes.

Paddle Input
Green LED
Beep Tone on
Selection
Description
Normal Mode

Two tone High>Low beep
Left paddle controls NoteOn 20, Right paddle controls NoteOn 21
Map these to Trigger CW Left Paddle and Trigger CW Right Paddle.
Not all apps have these options.
Extended Mode

Two-tone
Low>High beep
Left paddle controls NoteOn 30, Right paddle controls NoteOn 31
You can map these to Trigger CW Straight Key and PTT Push to give you a straight key and PTT control in this mode. You can map 30 and 31 the same as functions as 20 and 21 to disable the extended mode. Not all apps have these options.
To toggle Paddle Mode, long-press the encoder while in the Home encoder mode (both yellow LEDs off).
If your app doesn’t support keyer or PTT input control, or you don’t use them, you can map the paddle controls to any other function your app supports.
Mapping for Remote Ham Radio
To use the MIDI with Remote Ham Radio open the Tools menu in the RHR console and select CTR2-MIDI. 
The MIDI’s controls are pre-mapped in RHR as follows:
Keying Input
You can plug your paddles or a straight key and PTT switch into the 3.5mm jack on the MIDI. To use paddles, set the Paddle Mode to Normal (long-press the encoder until the green LED turns off). To use your straight key and a PTT switch, wire the straight key to the TIP and the PTT switch to the RING of a 3.5mm plug and insert it into the 3.5mm jack on the MIDI. Set the Paddle Mode to Extended by long-pressing the encoder until the green LED turns on.
Encoder Control
To select an encoder mode short-press the encoder until the yellow LEDs indicate the mode you want. The encoder has a turn and press & turn function for each mode. The modes and their functions are listed below. I don’t know if you can change this mapping in the program.
ENCODER ACTIONS
User Input
Action Taken
Home (turn)
Change VFO
Home (press & turn)
Slice Volume
Mode 1 (turn)
NR Level
Mode 1 (press & turn)
NB Level
Mode 2 (turn)
VOX Level
Mode 2 (press & turn)
*Not used*
Mode 3 (turn)
Keyer Speed
Mode 3 (press & turn)
*Not Used*
Button Controls
Each button (MFB) has two functions. Short-press the button (< 1 second) to access the primary function. Long-press the button (> 1 second) to access the secondary function. The table below lists the functions available.
BUTTON ACTIONS
User Input
Action Taken
MFB1
CW Mode
MFB1 (long-press)
Toggle NR
MFB2
SSB Mode
MFB2 (long-press)
Toggle NB
MFB3
FT8
MFB3 (long-press
FT4
MFB4
Toggle PTT
MFB4 (long-press)
Toggle VOX
MFB5
Band Down
MFB5 (long-press)
*Not Used*
MFB6
Band Up
MFB6 (long-press)
*Not Used*
Mapping for iOS and MacOS Apps
The map on Marcus’ apps is preconfigured for the MIDI when you select the CTR2 Controller device from the Tools menu. You can change the mapping to fit your needs.
The default configuration for the MIDI’s Map 1 defines the first primary encoder control (CC 100) as WheelA. This control is typically used for frequency control. Other encoder functions are defined as MIDI SliderA (no center/edge beeps). You can change these assignments using a terminal program. 
Editing the CTR2 Controller Map
Pressing the Edit Mapping button in the CTR2 Controller page of Marcus’ app opens the Edit CTR2 Map page.
The map is preconfigured when you select the CTR2 Controller the first time as shown here. You can edit it to fit you needs.
Press a button or turn the encoder to highlight its function on the map.
Mapping Functions to Controls
To change a mapped function press or click the control line and choose a function from the dropdown menu. 
NOTE: Your MIDI will not be able to control your app unless functions are mapped!
Example: Short-pressing MFB1 on the MIDI sends the Button 1 command. This button is mapped to Mode Next function in SmartSDR which increments the mode on the active slice. Long-pressing MFB1 on the MIDI sends Button 11. This is mapped to Mode CW in SmartSDR which tells it to set the radio’s mode to CW. 
Once you have your map configured press the folder button at the top of the display to save your map.
Using Paddles with the App’s Keyer
Marcus’ iOS/MacOS apps include a keyer that you can control with the paddles connected to the MIDI. 
NOTE: If you’re using Bluetooth-LE MIDI you may notice a difference in how the paddles work with the app’s keyer as opposed to a hardwired paddle/keyer. The latency in the Bluetooth-LE connection causes up to 15 milliseconds of delay. This will throw your “fist” timing off, especially in Iambic modes where an extra element may be added. It may take some practice to get use to the timing change. If this is a problem for you consider using USB MIDI instead.
To control the keyer, follow these steps:
• Map Button 20 to Trigger CW Left Paddle and Button 21 to Trigger CW Right Panel. You can change this mapping if they are wired backwards.
• Plug your paddles into the Paddle In jack on CTR2-MIDI. 
• Verify that the Paddle Mode is in Normal mode on the MIDI (the green LED is off). To toggle this mode, long-press the encoder while in the Home encoder mode (both yellow LEDs off). You should hear two tones (high to low frequency) and the green LED will turn off.  If Paddle Mode is in Extended mode the paddles will control MIDI Buttons 30 and 31.
• Set the radio’s mode to CW
• In SmartSDR, press the View menu in the Panadapter display and select CWX Panel. You can adjust speed and other setting here.
• In SDR-Control, select the CW Keyer option in the Tools menu to configure the keyer. DO NOT enable the MIDI device in this panel, this is done in the MIDI Controller panel.
• Pressing either paddle will now activate the keyer and key the radio.
Using a Straight Key or PTT Switch
If you want to use a straight key or an external PTT switch with the MIDI, map Button 30 or 31 to Trigger CW Straight Key and PTT Push then wire the straight key and PTT switch to the Tip and Ring of a stereo plug and insert it into the Paddle In jack on the MIDI.
Long-press the encoder while in the Home encoder mode (yellow LEDs off) to toggle the Paddle Mode between Normal to Extended. You should hear two tones (low to high frequency) and the green LED will light when in Extended paddle mode.
NOTE: There is no Trigger CW Straight Key option in SDR-Control. I map 30 and 31 to PTT Toggle. This is a latching control, push to assert PTT and push again to drop PTT.


Mapping For Thetis
Thetis is a little different than RHR and iOS/MacOS apps in that it uses the MIDI’s WheelB control instead of WheelA for frequency tuning. Map 2 is pre-configured with WheelB for tuning. Press and hold MFB3 then press the encoder to switch maps.
NOTE: WheelB does not support speed (proportional) tuning.
With the Setup -> Serial/Network/Midi CAT window open select the MIDI tab and click the Configure MIDI button. The program will initialize MIDI using USB. 
NOTE: If the program doesn’t initialize the MIDI check to make sure you are using a USB-C data cable, not a USB-C charge cable.
Mapping Controls
Press a button or turn the encoder and the window at the left will open.
In this example I turned encoder when the MIDI was set to the Home encoder mode so it is controlling Change Control (CC) 100.  
NOTE: When mapping encoder controls you need to turn the encoder fully CCW until you get to 1 and then fully CW until you get to 127 to set the Max and Min range values. 
Next, I give the control a name. I’ll call it VFO-A Freq and select Change Freq VFO A from the Available Commands list.
Click the Done and then the Save button to return to the Manage Mappings page.




You’ve mapped your first control! Now follow the same procedure to the other 7 encoder functions and the 12 button functions. 
Here’s a screenshot of the mapping I currently have in Thetis. Don’t be afraid to experiment with the settings so you can find the combination that works best for you.
NOTE: When using the Thetis Wheel control type you must set the encoder on the MIDI to WheelB.

When you’re finished mapping controls make sure to click the Save button in the Midi Controller Setup page and Apply before you leave the Setup page so these functions will be restored the next time you run Thetis.
You can export your map or import a map from someone else by clicking the Manage Mappings tab at the top of the Midi Controller Setup display. I’ve included a copy of my map in the firmware zip file.
Advanced Options
Operation with N1MM Logger+
You can use the MIDI as an interface to use N1MM’s CW keyer with SmartSDR or SDR-Control for iOS. To do this, follow the instructions on the N1MM Interfacing Basics webpage to build a key interface circuit. This will require a USB serial adapter with a keying interface circuit wired to its RTS output. Connect the output of the keying interface circuit to the TIP and SHIELD of the MIDI’s Paddle input jack. Next, map the Left Paddle input on the MIDI to Trigger CW Straight Key. With this setup you can control your radio using the N1MM Logger+ and use keyboard keying in N1MM Logger+. 
Unfortunately this configuration doesn’t allow you to use a set of paddles with the MIDI at the same time nor does it allow N1MM Logger+ to control your radio remotely.
If you’re looking to have N1MM Logger control your radio remotely you might consider using CTR2-Micro to remotely control and key your radio with SmartSDR or SDR-Control providing the user interface. Instructions for this can be found in the CTR2-Micro Operation Manual under the Advanced Options section.


Troubleshooting
Issue
Solution
I can’t connect the app to the CTR2-MIDI using USB MIDI
1) Make sure you are using a USB-C data cable. Many USB-C cables are power only. These will not work with USB MIDI.
2) If using a mobile device (iPhone, iPad, Android, etc) you must use an OTG adapter for your device. This adapter provides a USB connection for an external device. Newer iPhones and iPads with USB-C connectors do not required an OTG adapter.
I can’t connect the app to the CTR2-MIDI BLE device
Make sure the Bluetooth radio is turned on. The green LED will flash once every 2 seconds when the radio is on. If it’s off (green LED flashes once every 5 seconds), press and hold MFB6 then press the encoder to turn it on.
Follow the instructions in the Connecting CTR2-MIDI to the App  section. 
You may need to click both the Find Bluetooth-LE MIDI Device and the Enabled switch several times in different combinations to get the app to find the MIDI. You also may need to install the MIDI-Wrench or Conji app to get CTR2-MIDI recognized. If all else fails, connect using USB.
I have to connect CTR2-MIDI every time I start the app.
CTR2-MIDI will stay connected the app on your iOS or Mac device with Bluetooth-LE as long as it remains powered up. If you remove power from CTR2-MIDI you’ll need to open the Tools-CTR2 Controller window and click the Find Bluetooth-LE MIDI Device button then click Enable to reconnect it to the app. When connecting with USB MIDI it should say connected even through a power cycle.
My Flex radio starts sending a string of Dits or Dahs when I select CW mode
This seems to be a bug SmartSDR v6.9.15. If you press the paddles when the app is not in CW mode but the CWX panel is open that paddle press is buffered in the app. When you change to CW mode from another mode CWX triggers the last paddle press you made and keeps sending it until you press the paddle again, turn off CW mode, or close the CWX panel. This should be fixed in the latest update of SmartSDR.
The MIDI connects to my device but does not control anything
1) Verify that you have mapped each MIDI control to a function in your app.
Frequency tuning is not working
1) Make sure you have the right encoder map selected. Press and hold MFB3 then press the encoder to switch maps.
2) Use WheelA for RHR and Marcus’ iOS and MacOS apps. Use WheelB for Thetis and other Windows apps.
3) Make sure you have the encoder mode set to the mode you programmed frequency control to. I use the encoder’s Home mode for frequency tuning.
4) Make sure you have the correct MIDI command mapped to the frequency control in your app.
How can I tell when I’m at the center (0 Hz) when controlling RIT or XIT?
Use the SliderB control for RIT and XIT controls. This control beeps and pauses tuning for about ½ second when the control reaches its center position (64 counts) and beeps twice when reaching the upper or lower end of tuning. SliderA does not beep at center or at the edges. Its best for most other knob or dial controls.
Pressing an MFB executes the wrong parameter
First, verify that the MIDI mapping is correct in the app. If it is, you will need to be recalibrate the MFB ADC counts. Connect a terminal to the unit’s virtual serial port and select the [g] option to start the recalibration process.


Speed (proportional) tuning is not working
The WheelA control mode used for frequency tuning in RHR and Marcus’s iOS/MacOS apps supports speed sensitive tuning (tuning step changes as you tune faster).  Press and hold MFB2 then press the encoder to step through the speed settings. You may also have the wrong encoder map selected on the MIDI. Press and hold MFB3 then click the encoder to toggle maps.
The WheelB control must be used on Thetis and other Windows apps. It does not support speed sensitive tuning.
Paddles don’t key the radio
1) Verify the radio is in CW mode
2) Verify the keyer is in Breakin mode and Sidetone in On in the P/CW panel
3) Verify the Paddle Mode is in Normal mode (green LED is off)
4) Verify MIDI Buttons 20 and 21 are mapped to Trigger CW Left Paddle and Trigger CW Right Paddle
5) Open the CWX Panel in the app’s View menu
Paddles are reversed
Remap MIDI Buttons 20 and 21 to swap Left and Right paddle assignments
No sidetone in SmartSDR when keying 
Open the left pop-out window in the Panadapter display on the app and click the Audio menu. Set the Local Audio Monitor slider to 0.
Slow response or timing issues with keyer
Connecting multiple Bluetooth devices to your iOS device (i.e. CTR2-MIDI and a BT headset) may affect the app’s keyer response to paddle input. To fix this problem, click the Flex 6xxx button on the bottom of the display, select the CW item to open the Radio CW Settings window and disable CWX Sync. 

You may also consider using USB MIDI with an OTG adapter on your mobile device.




Appendix A: Advanced MIDI Configuration
Most of the MIDI’s options can be changed using a “hold button and encoder press” sequence. If you want to edit the encoder maps, turn off or turn on the Bluetooth radio, recalibrate the buttons, or reset the MIDI to factory values you’ll need to connect a terminal program such as Putty or Tera Term to the MIDI’s virtual USB serial port. Information on connecting a terminal program can be found in Appendix D and E.
Once you connect the terminal to MIDI press any key on the terminal’s keyboard to open the MIDI’s terminal display shown here.
Select an option by pressing the key associated with that option. For instance, to cycle through the Beep modes, press the [a] key.
Terminal Display
The various fields in the terminal display are described next.
Device Names
When connecting the MIDI to the device running the radio control app using the USB-C connector it will show up on the device using one of two device names. On Windows it shows up as CTR2-MIDI. On Apple iOS and MacOS devices it shows up as XIAO_ESP32-S3. 
When you connect to an Apple device using Bluetooth-LE MIDI the MIDI will show up as CTR2_ plus a four digit hexadecimal number derived from the MIDI’s MAC address. This naming convention gives every MIDI a different Bluetooth-LE device name so you can use more than one MIDI on an Apple device,  (but not at the same time!) 
NOTE: I write the four digit address on the bottom label of all assembled MIDIs.
The BLE State on the terminal display will show the connection status of the Bluetooth-LE MIDI connection. The green LED on the MIDI will flash twice once a second when the MIDI’s Bluetooth-LE is online. If the Bluetooth radio is turned off the status will show BLE Off.
NOTE: BLE MIDI is not supported on Windows.
Encoder Mode
The encoder mode will be shown here. You can step through the encoder modes by pressing and releasing the encoder. The yellow LEDs will show the selected mode.
Paddle Mode
The Default paddle mode sends MIDI controls 20 and 21 for the left and right paddles. These are usually mapped to the Trigger CW Left paddle and Trigger CW Right paddle functions in the iOS/MacOS apps. When the Extended paddled mode is selected (by long-pressing the encoder in the encoder’s Home mode – yellow LED are off) MIDI controls 30 and 31 are sent with the left and right paddles. These can be mapped to the Trigger CW Straight Key and PTT Push functions in the SmartSDR app. Not every app has keyer or straight key MIDI controls.
Beep Mode
Press [a] (or press and hold MFB1 and press the encoder) to step though the Beep modes. When Beep is off the LEDs will momentarily flash when you press a control long enough to enter its long-press function. When Beep is normal all buttons and the encoder beep when pressed. If Beep is set to Long-Press the MIDI will only beep when you press a control long enough to enter its long-press function. 
Speed Tuning
Press [b] (or press and hold MFB2 and press the encoder) to step through the speed (proportional) tuning settings for WheelA. There are three options, Off, Normal, and Fast. 
Encoder Map
Press [c] (or press and hold MFB3 and press the encoder) to toggle between Encoder Map 1 and Encoder Map 2. 
Report Options
Press [d] (or press and hold MFB4 and press the encoder) to have the MIDI report all of the option settings in Morse code. You can press any button during the report to silence it.
Edit Encoder Map
Press [e] to open the Edit Encoder Map display. Here you can change the MIDI control type assigned for each encoder function. Press the [a] key to switch between the two maps.
Encoder Map 1 is typically used with RHR and Marcus’ iOS/MacOS apps. Encoder Map 2 is typically used with Windows apps such as Thetis and SDR-Console.
Press the [Esc] key to exit this screen.



Eight control modes are available on the encoder. The primary mode controls (executed when you turn the encoder) are shown in the left column and are even numbered starting at 100 (the MIDI Control Change command number). The secondary controls (executed when you press and turn the encoder) are shown in the right column. They are odd numbered starting at 101. 
Each encoder mode supports one of the following MIDI control types. To change the MIDI control type assigned to an encoder mode press the highlighted hotkey (the red digit in the control #) on the terminal’s keyboard.
• Button – in this mode turning the encoder CCW or CW sends a MIDI NoteOn {Button #} for each encoder tick based on the table below. There are 24 encoder ticks per revolution.  These commands can be used to change the frequency on iOS/MacOS apps when they are mapped to the Button Frequency Down and Frequency Up in the app. 

Primary
Encoder Mode
CCW Button #
CW Button #
Secondary
Encoder
Mode
CCW Button #
CW Button #
100
40
41
101
42
43
102
44
45
103
46
47
104
48
49
105
50
51
106
52
53
107
54
55

• SliderA mode emulates a potentiometer. It sends a MIDI Control Change (aka CC) value for each encoder tick to the app indicating the position of the slider. Turning the encoder CCW decrements the count value down to 0 and turning the encoder CW increments the count value up to 127. The MIDI remembers the last count position through power cycles. This mode is used for controls that would use physical knobs or sliders such as volume, squelch, power, etc.
• SliderB is similar to SliderA except it adds “audible detents”. The MIDI will beep once at the center (64 counts) and twice at the lower and upper limits of the control (0 and 127 counts). Encoder changes are blocked for 600 milliseconds after the center beep to give you time to stop turning. SliderB is useful when using the encoder for RIT and XIT tuning as the center beep indicates when RIT or XIT is turned off and the edge beeps indicate when you have reached the end of the tuning range.
• WheelA is similar to the Slider controls in that it uses a MIDI CC command to send a value to the app. This control has an imaginary center position at 64 counts. Turning the encoder CCW sends a value below 64 for each encoder tick. Turning it CW sends a value above 64 for each encoder tick. This control is speed sensitive. Turning the encoder slowly sends a value of +/- 1 count from center. Turning it moderately fast (one revolution every two seconds) sends a value of +/- 10 counts from center. Turning it fast (about 1 revolution per second) sends a value of +/- 50 counts from center. RHR and Marcus’ iOS/MacOS apps use this scheme for frequency control and the frequency change per count depends on the Tune Step selected in the app. 
• WheelB is a variant of WheelA. Unlike WheelA this control has no center position, it only tells the app which direction the encoder is being turned. Turning the encoder CCW sends a value of 126 for each encoder tick. Turning it CW sends a value of 1 for each tick. This control is not sensitive to encoder turning speed. Thetis and SDR-Console use this scheme for frequency control. Frequency change per tick is based on the Tune Step set in the app.
Bluetooth Pwr
Press [f] (or press and hold MFB6 and press the encoder) to toggle the Bluetooth radio’s power. When powering the MIDI from a portable device such as an iPhone or iPad you can use USB MIDI and turn the power off on the Bluetooth radio. This will cut the current consumption from about 93 mA to 43 mA.
Pressing [f] will open acknowledgment screen. If you choose to consider the MIDI will shut down and start beeping once every second. You must cycle the power on the unit so it can reboot in the new radio mode.
NOTE: The Bluetooth power option is not available when CTR2-MIDI firmware is running on a CTR2-Micro.
Recalibrate Buttons
Press [g] to enter the MFB recalibration routine. All assembled MIDIs are calibrated at the factory. If you’ve built your MIDI from a kit you’ll need to run the recalibration routine.
The recalibration window shows the currently save ADC calibration values. Once you complete the recalibration the new values will be saved.
NOTE: Each button must be pressed within 10 seconds or the process will fail.
NOTE: If the MIDI loses the MFB calibration data it will sound “?” in Morse code when you press any MFB or press the encoder. To recalibrate the button voltages connect a terminal program to the MIDI’s virtual USB serial port then press [r] to start the calibration process.
Reset to Factory Settings
Press [h] to remove all custom settings from the MIDI and return it to the factory default settings.  This does not change mapping that you have done in the app.
Appendix B: Using CTR2-MIDI Firmware on CTR2-Micro
The CTR2-MIDI firmware can be flashed to CTR2-Micro. This gives current Micro users access to the MIDI features without having to buy new hardware. 
The terminal display for MIDI firmware running on the Micro is similar to the normal MIDI display except the USB Name and the Bluetooth Power option is not shown because these options are not available on the Micro.
There are several limitations to using the MIDI firmware on the Micro:
• CTR2-Micro hardware only supports Bluetooth-LE MIDI. The ESP32-C3 processor in the Micro doesn’t have the hardware to support USB MIDI.
• Once you have flashed the MIDI’s firmware on your Micro most of the features you use on the Micro will no longer be available. This includes the following:
o WiFi is not supported so you can’t control the Flex radio directly or use CTR2-Voice
o Serial CAT is not supported so you can’t control other radios with the Micro
o The Micro’s keyer is not supported so you can’t use a terminal as a keyboard keyer or use any transmit message buffers you had set up in the Micro
o Key and PTT Output is not supported
o Favorite Frequency and Previous Frequency lists are not supported
o The web browser interface is not supported
o You must reflash the Micro firmware on your Micro to restore its normal features
• The Micro only has three buttons so you can only map 6 MIDI Buttons in the app
• The Micro only has one LED. This LED flashes to indicate the current mode of the unit. It does not indicate long-press mode if Beep mode is turned Off.
• Report Options (MFB4+Enc) is not available since there are only three buttons
You can always reflash the Micro firmware on your Micro to return it to its normal functionality.
Flashing the Firmware
To flash the MIDI firmware on to your Micro, unzip the four binary files from the MIDI firmware distribution zip file into a unique folder then follow the instructions in Appendix B.
You will need to complete the MFB Calibration on the Micro to save the MFB ADC counts in the MIDI’s initialization file. This only needs to be done once.
NOTE: The MIDI firmware maintains its own file structure therefore the settings you had for the Micro firmware are not lost. Just reflash the Micro firmware to your Micro to restore your Micro to its normal operation.
Operating the Micro with MIDI Firmware
The Micro operates exactly like the MIDI when running the MIDI firmware. You will need to go through the same steps to connect the Micro to your iPad and you will need to map the controls on the Micro to the app. You will only have 6 MIDI Button functions (two on each MFB) and all of the encoder modes.
The big difference between the MIDI and the Micro is with the LED indicators (or lack thereof). The Micro’s status is indicated by the flash sequence of the status LED.
The table below summarizes these flash sequences and the beeps associated with them.
Encoder
Mode
Flash Sequence
Buzzer Tone when entering this mode
Description
Home
One long flash
One high frequency beep
Primary encoder sends Control Change (CC) 100
Secondary encoder sends CC 101
Mode 1
One short flash
One low frequency beep
Primary encoder sends CC 102
Secondary encoder sends CC 103
Mode 2
Two short flashes
Two low frequency beeps
Primary encoder sends CC 104
Secondary encoder sends CC 105
Mode 3
Three short flashes
Three low frequency beeps
Primary encoder sends CC 106
Secondary encoder sends CC 107
The Paddle Mode determines the rate of the LED flash. 
• When Paddle Mode is in Normal mode (controlling MIDI Buttons 20 and 21) the LED flashes the status at 2 second intervals
• When Paddle Mode is in Extended mode (controlling MIDI Buttons 30 and 31) the LED flashes the status at 1 second intervals


Appendix C: Installing or Updating CTR2-MIDI Firmware
Kits and assembled CTR2-MIDIs have the firmware already installed on them but as you might expect changes will be made to the program over time. To install the latest MIDI firmware on your device, follow these steps:
1. Determine which version of the firmware you need for your device. If your device is a CTR2-MIDI (with six MFBs) you’ll need the S3 firmware (for the ESP32-S3). If you are running CTR2-MIDI on a CTR2-Micro (with three MFBs) you’ll need the C3 firmware (for the ESP32-C3).

2. Download and unzip the appropriate CTR2-MIDI firmware from my web site. Unzip it into a different folder than where you store the Micro’s firmware update files.

3. Download and open the EspressIF Flash Downloader Tool. When it starts, select the Chip Type your unit is using (ESP32-S3 for CTR2-MIDI or ESP32-C3 for CTR2-Micro hardware). Leave WorkMode set to Develop and LoadMode set to UART.



4. Map the four .BIN files in the CTR2-MIDI firmware distribution file into the downloader tool. 
NOTE: The address for each file is embedded in its file name. Enter these addresses in the address fields to the right as shown in this screenshot.

5. Select the checkboxes on the right of the four files as shown.

6. Set the COM: port to the port assigned to CTR2-MIDI and set the Baud to 921600.


IMPORTANT NOTE FOR ESP32-S3 
The ESP32–S3 processor in CTR2-MIDI has two USB UARTs. The first UART (COM 5 in this example, yours will be different) is active when you initially power up the unit and is the COM port you connect to with a terminal program. The Flash Download Tool will fail and pop up the window in this screenshot when you try to flash the program to this port.

Press OK to clear the alarm window. 



Next, drop down the COM: list again. You notice that the initial COM port (COM 5 in this example) is not on the list. You’ll also notice a new COM port has been added to the list. On my computer it shows up as COM 10 (your computer will show a different port #). This is the second USB UART on the processor and is used for programming. Select this new COM port.

NOTE: If you don’t see the second COM port you will need to press the PROGRAM button while you power up the MIDI to force it into program mode. See the Manually Switch the Processor to Program Mode  section for more information on this button.

NOTE: The ESP32-C3 processor in CTR2-Micro only has one UART so the above steps are not required. Just select the COM port for the Micro when flashing CTR2-MIDI firmware to it.

7. Click the START button to start the download.
8. Once the download is complete, cycle the power on the unit to start the new MIDI firmware. 

NOTE: The ESP32-S3 processor will revert back to its initial COM port (COM 5 in this example) after the reboot.
NOTE: Clicking the ERASE button will erase the entire flash memory including the setup file. This will reset the MFB ADC values saved on the unit and you will need to recalibrate the buttons when you start the program. If you are flashing the MIDI firmware to a CTR2-Micro (-C3 processor) erasing the flash will also delete the configuration files used with the normal Micro firmware.


Installing using Linux or Mac
A script file is also supplied in the firmware update zip file. This script file can be used in a Linux or Mac environment if you don’t have access to a Windows computer.
Instructions for using this script file are include in the CTR2-Micro Operation Manual in Appendix B.
The firmware that allows USB MIDI control changes the way the virtual COM port works on the ESP32-S3. One COM port is used in the normal operating mode and another COM port is used for flashing the firmware. In order to flash new firmware to the unit you must force the ESP32-S3 to switch from the normal operating mode to programming mode.
This can be done one of two ways. 
Redirecting COM Ports through the Flash Script
1) Set the COM port in the script to the operating port. This is the port your computer finds when you first plug the MIDI in to the computer’s USB port.
2) Run the script. It will fail but in doing so it will cause the ESP32-S3 to switch from its operating COM port to its programming COM port.
3) Change the COM port in the script to the new COM port your computer just detected and rerun the script.
Manually Switch the Processor to Program Mode
1) Power the unit off.
2) Press and hold the PROGRAM button down on the processor board then apply power to the board. Yes, it’s that little black dot on the square silver pad the toothpick is pointing to in this photo! 

A notch has been cut in the enclosure next to the USB-C connector to allow you to access this button without opening the enclosure.
It’s still hard to do especially if your eyes aren’t as good as they use to be. Insert the toothpick only about 6mm (1/4”) and gently press down. You will feel a light click. If you insert the toothpick too far it will rest on the chip LED in back of the switch and will not press the button. Once you have the button pressed power up the unit. If it’s in programming mode the normal LED boot sequence will not run. Use a terminal program to find the program UARTs COM port assignment.
Appendix D: Configuring Tera Term
Tera Term is the simplest terminal program to get running for a serial connection. 
Download it for Windows at https://ttssh2.osdn.jp/index.html.en. If that site is down, try https://download.cnet.com/tera-term/3001-2094_4-75766675.html. As far as I know, Tera Term is only available for Windows.
When you first open Tera Term you’ll be presented with the Tera Term New connection window. Simply select the Serial radio button, select the COM port Window’s assigned to your Micro when you plugged it in, and click the OK button.

Since you are connecting to a USB serial port there is no need to set the baud rate. It will run at USB speed regardless of the baud setting.
That’s it! Tera Term will connect to the MIDI. Press any key to open the configuration display. 
You can change the terminal size in the Setup menu. Select Terminal… Set the Terminal Size to 41 x 20. The MIDI’s terminal interface was designed for this size. 
While in the Terminal… settings verify the New-line options are set to CR for both Transmit and Receive and the Terminal ID is set to VT100.
You’ll probably want to change the font size and colors. These are also changed in Tera Term’s Setup menu. Select Display to change the font and background colors to your liking. Select Font to change the font and font size. I like Courier New, Regular, and 14 point size. You’re preferences may differ.
Once you have the program configured the way you like, select the Setup->Save Setup… menu and save your configuration. If you use the default file name, TERATERM.INI the program will automatically start a Telnet session using the COM port you selected above when it opens. This provides one-click access to your MIDI.


Appendix E: Configuring Putty
Putty is a terminal program that can be configured for a variety of needs. The MIDI only supports serial connections. This section describes how to configure the program to interface with the MIDI.
Download Putty for Windows from https://www.putty.org/. It’s also available for Linux at  https://www.ssh.com/academy/ssh/putty/linux and for Mac at https://www.ssh.com/academy/ssh/putty/mac.
You’ll need to connect to the MIDI using its USB serial port in order to configure it. 
Serial Session
Select Serial then set the Serial Line to the COM port you found in the Device Manager and set Speed (Baud Rate) to 115200. 
NOTE: Since this is a USB serial port the Speed (baud rate) doesn’t matter. Data will be sent at USB speeds regardless of the Speed setting.

Next, select the Terminal item and set the Implicit LF in Every CR to on, and Local Echo, and Local Line Editing to Force Off.
You can change the window size under the Window item. Set the Columns to 41 and the Rows to 20. 

Once this has been done, return to the Session menu item, enter a name for this session and click the Save button. This allows you to easily re-open this session with just a couple of clicks.
If you right-click on the Putty icon in the Windows toolbar the last few sessions you had open will be displayed. Just select the one you want to open it.
You can adjust the display colors on the Windows->Colours menu item. The Micro uses the Bold attribute to highlight the hotkeys and other items. I like to set the Background color to blue and the Bold color to yellow but you can find the colors that work for you. After you get a color combination you like return to the Session menu and Save the session.


Appendix F: Change Log
v1.01.00f: September 3, 2024
• Added more information to Connecting CTR2-MIDI to the App section for connecting to Marcus’ apps
v1.01.00e: August 20, 2024
• Updated the Connecting CTR2-MIDI to the App section to include new information on connecting to Marcus’ apps
• Moved Configuring the MIDI Firmware to Appendix A.
v1.01.00d : May 22, 2024
• Updated the Installing using Linux or Mac section with information about switching COM ports for flashing new firmware after v1.01.00.
v1.01.00b and v1.01.00c: May 10 and 12, 2024
• Rewrote parts in the manual to clarify the configuration requirements of the MIDI and the app.
v1.01.00a: May 8, 2024
• Updated the Appendix B: Installing and Updating CTR2-MIDI Firmware section to include new information about flashing firmware to the ESP32-S3 in CTR2-MIDI.
v1.01.00: April 29, 2024 – Major Update Release
• Added USB MIDI support
o Once v1.01.00 firmware has been installed in CTR2-MIDI you’ll need to follow Step 1 in Appendix B: Installing or Updating CTR2-MIDI Firmware section for future updates.
• Select from MIDI Button, and two types of Sliders and Wheels for each encoder function in the terminal page
• Redesigned terminal page
o Hotkeys select the MIDI function for each encoder function
o Displays saved ADC count assigned to each MFB
o Displays ADC count when an MFB is pressed
o Displays MIDI channel, control, and value when a control is executed
• Added Appendix D and E with information on using Tera Term and Putty 
v1.00.05 – April 7, 2024
• Added a reference to the Conji app for MacOS to help with connecting the Midi to a Mac computer.
v1.00.05 – March 26, 2024
• Revised button read code to reduce false triggers
• Added Show/Hide MFB Counts option in terminal set up
• Added No Sidetone solution to Troubleshooting table
v1.00.04 – March 23, 2024
• Green LED now flashes to indicate unit is powered up (CTR2-MIDI hardware only)
v1.00.03 – March 21, 2024
• Added additional information on importing the .map file
• Added additional information on connecting CTR2-MIDI to the app
• Added additional troubleshooting help
v1.00.03 – March 10, 2024
• Add beep types to tables
• Save encoder values to initialization file
v1.00.02 – March 8, 2024
• Added Troubleshooting section
v1.00.02 – March 7, 2024
• Shortened the MIDI device name from CTR2-MIDI_xxxx to CTR2_xxxx
• Removed Paddle PTT mode and replaced it with Paddle Mode
o When the green LED is off the paddle inputs control MIDI Buttons 20 and 21
o When the green LED is on the paddle inputs control MIDI Buttons 30 and 31
• Removed PTT latching logic that as associated with Paddle PTT mode
• The red LED now lights when either paddle is pressed
• Redesigned terminal screen 
v1.00.01 – March 6, 2024
• Added an option in the terminal display to enable/disable Paddle PTT mode
• Added MFB ADC values to the terminal display  
v1.00.00m – March 3, 2024
• Beta release for interface development
v1.00.00 – December 22, 2023
• Initial release of CTR2-MIDI firmware for CTR2-Micro

CTR2-MIDI Operation Manual v1.020Page 3