2019-07-25 (Th) PillarGame

The first thing to do upon startup would be for the controller inside the cylinder to make sure a Bluetooth module was connected. When the radios are talking to one another, they will pass any data directly to their counterpart without parsing it, but when they are awaiting a connection, they will accept AT commands and reply autonomously. The most basic is "AT" to which the chip will respond, "OK" and this sketch checks for that response on a SoftwareSerial port. When the programming is completed, the program will point back at the hardware serial port, but that would make programming difficult in the meantime.
Module connection status LED

Establishing a connection happened via another Bluetooth module, and that half is still being done manually. The peripheral module was getting programming first since it should be simpler. The serial feedback showed that the controller asked the module if it was there, received a suitable answer, and considered itself connected, which was all true. Then, the other module connected remotely and displayed a textual message on the serial port.
Screenshot of communication

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

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 in 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.