2026-05-14 (Th) SubdermalDuino Wirless communication

The microcontroller was not responding, so I put it back in bootloader mode and confirmed that I had the latest version. I unplugged it, but it would not appear in my list of ports, so I reset it by jumpering the RST pin again, and that worked. My worry was that something I did yesterday caused it to malfunction, and worse, it might have been initializing Serial communications. I should have realized it was a baseless worry, since it was a modern controller with native USB and every reason to have support. I verified by finding an Adafruit example with Serial comms. The sketch worked flawlessly.

I spent a bunch of time searching for the pin with the onboard LED. I could not find it written anywhere. My sketch cycled through the buttons, pushing them HIGH and LOW. When the program toggled pins 8 and 26, it would reset the board, so I need to avoid those pins. The LED was on pin 24.

I tried to install nRF Connect on two of my Android phones, but both installations failed. Luckily, I had an iPad, and that app worked. The final download for the night was an example that let me control the light via Bluetooth connection. The animation shows me turning on the red light.

Activating the red light via iPad

The rest of the posts for this project have been arranged by date.
First time here?

Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11
Completed projects from year 12

Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com

This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.

All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.

All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by  Brian McEvoy, cannot be used to claim property or assets.

Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.

This blog, including pictures and text, is copyright to Brian McEvoy.
2026-05-