2020-06-08 (M) HexShaftMonitor

I tried two different Windows computers, and a couple of M5StickCs, to establish a data connection. During that time, I flashed the firmware, at least twice, and according to the product manual, I was doing things correctly. The next option was the web interface, which was a breeze because it had the latest firmware. The downside to this option is that it supposes I have access to a computer and the controller. For upsides, I can load a program to the controller without being in the same hemisphere, I free up one of the ports on my computer, and the web interface runs in a browser, so I should be able to program with mobile devices.

When I was connected, I made a quick blinkenlight project and added some obvious text to the screen. I had the option to use Blockly or Python programming languages. I used Blockly, which was time-consuming, but self-explanatory, and I wanted to learn about it without immediately resorting to Python, which I have used before.
BlinkenLight programmed through the interwebs
Connected through web interface

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

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.