Are you new here?and how many threads on this site where someone wants a one-time project and we start teaching them how to make PCBs when all they needed was the connections already afforded them on a $12 Arduino board. Oh, and they get an Arduino - they only have a few lines of code to write and it is done. Problem solved.
If we take your route to the solution, we end up 50 posts into the conversation with a discussion where the toner-transfer method is not working for them... Oh god!
As far as getting 50 posts into a thread and having gone no where, that's a near daily thread operating procedure just to get many OPs to divulge the very basics of whatever 'top secret' plan they have concocted to do something simple because they either don't feel that revealing the important details of what it is they are working with and want to do with it up front matters or they think they need to add as much irrelevant complexity as possible to the design in just to avoid largely imagined 'what if's' and worse because they have a poor grasp of how what they are dealing with actually works.
I have no problem with using digital control and general processing where it's justified and necessary but for many simple analog based operations it's used as a crutch in attempts to overcome poor understandings of what should be very basic knowledge and understanding of how electronics circuitry and devices operate and work. Especially so when dealing with things like power handling circuits where all the code in the world won't make up for proper use and application of power switching devices and their related driver circuit configurations and down line load LCR characteristics.
That's where I am coming from. There are certain aspects of electronics that can't be handled and dealt with purely in code work just as there are others that are easier, simpler, and more reliably done with basic analog circuitry or such.