I gave up on using the device to throw a curveball. I could make it work with some relay trickery and a tablet stylus, but that is beyond this project's scope, which is overdue. I can think of several tedious tasks requiring tapping that I would happily automate.
I created a new mode for battling where the robot moves the touch emulator over the critical parts of the screen to complete a PvP duel. This programmed movement is not a winning strategy, but I can look away from the phone and still get credit for dueling.
The mode should hover in the center area, drop to the bottom where it can trigger special moves, then return to the center. The software repeatedly engaged the touch emulator, then moved to the following location after tapping x times as determined by a potentiometer.
My first battle went differently than I hoped. I did not see the touch emulator always cooperating with the phone. I removed the Arduino from the circuit and got better results, but they were far from ideal. When I tested on a drawing program, I saw that the Arduino did not deliver as many recognizable touch events as the core auto clicker. The biggest problem was keeping the emulator level. I tried holding the servo arms down with a rubber band and my fingers, but I will add slots for heavy washers in the next iteration.
Unreliable tapping
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
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.
2023-04-
I created a new mode for battling where the robot moves the touch emulator over the critical parts of the screen to complete a PvP duel. This programmed movement is not a winning strategy, but I can look away from the phone and still get credit for dueling.
The mode should hover in the center area, drop to the bottom where it can trigger special moves, then return to the center. The software repeatedly engaged the touch emulator, then moved to the following location after tapping x times as determined by a potentiometer.
My first battle went differently than I hoped. I did not see the touch emulator always cooperating with the phone. I removed the Arduino from the circuit and got better results, but they were far from ideal. When I tested on a drawing program, I saw that the Arduino did not deliver as many recognizable touch events as the core auto clicker. The biggest problem was keeping the emulator level. I tried holding the servo arms down with a rubber band and my fingers, but I will add slots for heavy washers in the next iteration.
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
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.
2023-04-
Comments
Post a Comment