2019-06-01 (Sa) Electronic Wind Chimes EWC

When compiling my code, I got an error every time because I was running low on memory. I already knew it was due to the table of characters used to store the instrument names. This was going to cause memory issues soon if it hadn't already.
Memory error when compiling

Arduino provided a way to store data in the non-volatile memory, but it was more cumbersome than the typical method of using the precious SRAM. I tried to simply cram my two-dimension array into program memory, but I had to follow the example for making an array of strings.

After buckling down and following the directions, the compile warning went away.
Happy compile screen

The code at the top of the program went from lengthy to tedious. The longest table in the file was doubled, but its effect on the memory was abolished.

End of one list and start of the next

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

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.