2023-05-05 (F) Weekly Summary

I programmed the first three modes to position the arms freely or with servo help. The column of pushbuttons activated the touch emulator at different speeds or held it continuously. I tested the system's ability to "drag," but it could not maintain a reliable connection.
Programmed movement

I tried to make a new operating mode to fight PvP battles unaided. I ran into an issue where the phone did not accept many emulated touches. I returned to the drawing program and found that the problem stemmed from the touch emulator not sitting correctly and getting poor signals from the Arduino.
Tap test

I noticed problems with the faceplate and servo arms while programming the controller, so I made a second version. I added a window for the auto clicker and a cutout for a carrying handle. I also made room for a Pop Socket and added some holes to a servo arm for weight.
Improved draft

I revised my drawing to avoid loose wires and ensure successful cuts. The laser cutting went smoother because I ran it slower, then painted the faceplate green and the rest of the parts red.
Colors for the next version

I transferred the hardware to the new version, and only the lights and pushbutton needed rewiring. I used steel bolts this time for a cleaner appearance. The only hardware I swapped was the potentiometers.
Ready to control my phone

I made adjustments to the battle mode for the new arms and tested it against Spark. I created a raiding mode and added light animations for fun. Instead of using Arduino, I used a touch emulator to trigger clicks.
(3:15) PhoneRobotREV1 demonstration

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.

Comments