2022-03-18 (F) Weekly Summary

There are many Bluetooth modules with different purposes, and I didn't look into which function my first pick provided. I guessed wrong and discovered that they were suited to acting as low-energy beacons, not wireless serial ports.
Wrong kind of modules

My second choice started with internet research, which should do the trick. The datasheet walked me through the connection procedure, and I executed it manually with a couple of serial to USB converters.
Following the steps

The steps I followed manually needed codification, so I wrote up a sequence in pseudo-code and verified they would work reliably. I felt like the last time I used Bluetooth like this.
This should link up my modules

One of the differences between these new modules and the old ones was that the initiating unit needed a pin connected to Vcc, so I installed a pair of header pins and a removable jumper.
Hardware change for this module

With my pseudo-code as a guide, I wrote up the functions to pair with a waiting module. The hardest part was recognizing incoming data. My solution was undoubtedly kludgey.
Two Bluetooth modules connected wirelessly

There was good news when I discovered that my Bluetooth modules would automatically pair up when powered. All my coding was in vain since I could have stopped after going through the steps manually, but this automatic linkage makes their future use more appealing.
Linked up neatly

The rest of the summary posts 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

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.