IC-705 doesnt seem to respond, or rejects the connection after sending the UUID

[ldjohn]

Hi there, I know this is in your archived code, but when I am compiling this with a change or two, I notice that the IC-705 drops the connection after you send the UUID.
This is the environment:
esptool v5.1.0
Using library BLE at version 3.3.3 in folder: C:\Users\john\AppData\Local\Arduino15\packages\esp32\hardware\esp32\3.3.3\libraries\BLE
"C:\Users\john\AppData\Local\Arduino15\packages\esp32\tools\esp-x32\2507/bin/xtensa-esp32-elf-size" -A "C:\Users\john\AppData\Local\arduino\sketches\1038A2B58EA4C6BD271B44990B458377/ic705-ble-simple.ino.elf"
Sketch uses 1103211 bytes (16%) of program storage space. Maximum is 6553600 bytes.
Global variables use 39552 bytes (0%) of dynamic memory, leaving 4482432 bytes for local variables. Maximum is 4521984 bytes.
"C:\Users\john\AppData\Local\Arduino15\packages\esp32\tools\esptool_py\5.1.0/esptool.exe" --chip esp32 --port "COM10" --baud 1500000 --before default-reset --after hard-reset write-flash -z --flash-mode keep --flash-freq keep --flash-size keep 0x1000 "C:\Users\john\AppData\Local\arduino\sketches\1038A2B58EA4C6BD271B44990B458377/ic705-ble-simple.ino.bootloader.bin" 0x8000 "C:\Users\john\AppData\Local\arduino\sketches\1038A2B58EA4C6BD271B44990B458377/ic705-ble-simple.ino.partitions.bin" 0xe000 "C:\Users\john\AppData\Local\Arduino15\packages\esp32\hardware\esp32\3.3.3/tools/partitions/boot_app0.bin" 0x10000 "C:\Users\john\AppData\Local\arduino\sketches\1038A2B58EA4C6BD271B44990B458377/ic705-ble-simple.ino.bin"
esptool v5.1.0
Serial port COM10:
Connecting....
Connected to ESP32 on COM10:
Chip type: ESP32-D0WDQ6-V3 (revision v3.0)
Features: Wi-Fi, BT, Dual Core + LP Core, 240MHz, Vref calibration in eFuse, Coding Scheme None
Crystal frequency: 40MHz
MAC: 78:21:84:95:83:f4

I believe the Arduino stuff is using Nimble now?
Is there a known issue regarding the IC705 dropping the connection? Any pointers would be appreciated, as this is a great feature but not very well documented by ICOM.

Even the standard sample BLE Client gets the disconnect treatment.
If you send no data, the Icom keeps you connected for about 10 seconds, then disconnects you. if you send the UUID, it disconnects immediately.

Thanks and regards
John
73 ZS1EQ/ZL1VMM

[K7MDL2]

That particular code was for BLE on a M5StackCoreS3-SE which is an ESP32-S3. It won't run on the ESP32-WROOM you are using. The S3 runs BT5 BLE.

You are running on an ESP32-WROOM which is BT4.2 dual mode (BT classic and 4.2 BLE). It is different code. The Core1 runs BT classic only.

The main program was heavily changed to run on an ESP32-WROOM so that I could use both BLE and BT classic. You can set the #define for either BLE or BT Classic. I run BT Classic because it reconnects faster and very reliably. The BLE mode, at least how I have it configured, waits for a full advertising cycle and sometimes misses a cycle. IN BLE mode in this code will run on a S3 which includes the ATOMS3 and the Core3-SE. If you disabled all Core/Atom features it should run on a plain ESP32 and ESP32-S3. In my K3NG CW Keyer port to the ESP32-WROOM, I am running both BLE and BT classic at the same time to connect a BT keyboard.

See the #defines in the M5Stack_CI-V_Band_Decoder.h for BLE selection.

  #define BTCLASSIC   // Can define BTCLASSIC *** OR ***  BLE, not both.  No BT version is  OK if USB Host is enabled
                  // BT Classic does not work on Core3. 

  //#define BLE         // Core 3 (BT5).  Works on Core 2, (BT4.2) not on Core.

[K7MDL2]

Be sure to read this page about the BLE connection steps.

https://github.com/K7MDL2/IC-705-BLE-Serial-Example/wiki/Technical-Details

The _simple program was done on the S3. I believe that version only works on the S3 but I do not recall exactly what the difference in the code was other than the library functions used maybe.

[ldjohn]

Thanks so much. I was hoping to do the multi ble for tuner, control and radionstuff, but I guess SPP it is. Thanks for your help Regards John

…

-- Regards John 73 de ZS1EQ DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Thank you.

On Wed, 03 Dec 2025, 23:29 K7MDL, ***@***.***> wrote: *K7MDL2* left a comment (K7MDL2/IC-705-BLE-Serial-Example#25) <#25 (comment)> Be sure to read this page about the BLE connection steps. https://github.com/K7MDL2/IC-705-BLE-Serial-Example/wiki/Technical-Details The _simple program was done on the S3. I believe that version only works on the S3 but I do not recall exactly what the difference in the code was other than the library functions used maybe. — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALIROJJXOP476CJDVADCZP33723O3AVCNFSM6AAAAACN4TMBIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMBWGE2DINBTGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[K7MDL2]

Once you connect via BT over SPP, you can connect to CI_V and do everything you normally would. Audio excluded as that is a separate BT or USB connection. If the tuner, control and radio stuff you want are CI-V, then it should just work. The code in the main program works for sure on your ESP32-WROOM.

When you say multi-BLE, I think you are maybe wanting create a CI-V hub? Then you have an external tuner, amp, and other CI-V things connected to the hub which bridges them to the radio, possibly by serial port or USB host serial.

I think this is quite doable though can be tricky. One of the challenges is avoiding collisions.

I think there is a USB CI-V hub by VE2DX. https://ve2dx.com/ct17b

I also ran across a project that I looked closely at that was a CI-V hub, possibly standard serial.

Also check out this repo. It has examples for 705 to PA and more.

https://github.com/WillyIoBrok/CIVmasterLib

[ldjohn]

Thanks, I'll check it out!

…

-- Regards John 73 de ZS1EQ DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Thank you.

On Thu, 04 Dec 2025, 08:43 K7MDL, ***@***.***> wrote: *K7MDL2* left a comment (K7MDL2/IC-705-BLE-Serial-Example#25) <#25 (comment)> Once you connect via BT over SPP, you can connect to CI_V and do everything you normally would. Audio excluded as that is a separate BT or USB connection. If the tuner, control and radio stuff you want are CI-V, then it should just work. The code in the main program works for sure on your ESP32-WROOM. When you say multi-BLE, I think you are maybe wanting create a CI-V hub? Then you have an external tuner, amp, and other CI-V things connected to the hub which bridges them to the radio, possibly by serial port or USB host serial. I think this is quite doable though can be tricky. One of the challenges is avoiding collisions. I think there is a USB CI-V hub by VE2DX. https://ve2dx.com/ct17b I also ran across a project that I looked closely at that was a CI-V hub, possibly standard serial. Also check out this repo. It has examples for 705 to PA and more. https://github.com/WillyIoBrok/CIVmasterLib — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALIROJM2BX5OLOYVQ7R4KED3744O3AVCNFSM6AAAAACN4TMBIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMBYGU2DOMRSGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>