Finished PCB and more Schematic Updates

• I realized a robotics control board should probably have debug lights so I added an led light to show 3.3v power, 5v power, 2 rgb lights that I’ll code later, and 2 led lights that I’ll also code later.
• I also spent a lot of time wiring the PCB and then went through DRC and fixed all the errors I could (although some of the errors were on the footprints themselves so not really sure what to do about that yet). I then designed some basic signage for the silkscreen on the PCB so it know shows which usb is for which, where the board gets power, and the motor ports. You can also see the 3d view of the finished PCB in the screenshot below but a few of the components are missing 3d models.
• Next up I’m probably going to go ahead and start building a case to house the board (although It’ll likely just be something minimal to house the display and to make sure I don’t cover up any ports on accident).

PCB wiring update & changes/fixes to the schematic
I spent a couple hours wiring the pcb only to realize that I had way too many capacitators and I was missing some critical functions from the schematic. So I went through and took out some capacitators from the schematic as well as adding an oscillator, dedicated quadspi to flash memory for the rp2040, and a usb-c port dedicated to upload code to the rp2040. I also fixed an issue where I had duplicate SPI from the esp32 to the display connector and rp2040 and instead made it so they share the clock, copi, and cipo.
The pcb wiring image is not updated yet from the schematic and I will need to do that as soon as I finish adding the footprints for all the new additions. So far I have added the 5v, 3.3v, and VM power rails and I made the traces there thicker. I’ve also wired up a lot of the logic for the motor drivers, the rp2040, and the switches. However, some it will most likely have to be redone because of the changes to the schematic :(.

Finished (hopefully) wiring up the schematic for the mission board!

As you can see from the schematic I had to make quite a few changes to the original plan, including the addition of an RP2040 as co-processor because the ESP32 itself didn’t have enough IO pins. The way its set up is that they can communicate through SPI and the RP2040 handles all motor controls while the ESP32 is the main brain. I also switched to a display that used the smaller 18 pin connector since its more practical. I also had to add 2 voltage converters which output at 3.3v (for board logic) and 5v (for servo power). The power input will come only from the barrel jack (not the usb-c) and the converters can handle from 7-30 something volts. I have decided that for this iteration of the board I’m also not going to include encoder ports because I want to start simpler and see if what I have right now will even end up working. Now my next plans are to start working on the PCB and make a case for the board!

Made a sketch for the board along with a hardware list (more stuff will probably be added), and setup the schematic with all the symbols I need

• After deciding I wanted to make a robotics oriented dev board I added motor drivers, screw in terminals, usb-c, a barrel jack(for power), pins to connect a servo, gyro, magnetometer, accelerometer, and at the center of it all: an ESP32-S3-WROOM. I chose this option because it supported usb, had wifi/bluetooth, and could potentially process camera feed to allow for a robot with a camera.
• I also added a 7 switches to interact with the UI that I will develop in the future for the display to be functional at actually making debugging & customization easier
• Also worth noting is that not everything in my sketch is in the schematic right now, because I wanted to start with at least the basics and core of my devboard. However, in the near future I will be adding all the stuff you see in my sketch.
• Now I’m going to start working on the actual schematic, and along the way I’ll probably add some stuff for the power system as well

Final Devlog on Designing the EasyPad ——————————————————— I have now finalized all my firmware, cad, and pcb design which you can find (along with a README) on the github at: https://github.com/A-Ritvik/easypad. I also had to spend some time debugging the qmk firmware because I didn’t know the syntax of the how you tell it which pin is connected where (you’re supposed to use GPX).

Finished Case Design with minor tweaks, Added 3d Models & Made a full Easypad CAD–––––––––––––––– —————— —————————————— The case design is now finished with a usb cutout on the side, and I added the pcb (along with all the other components) onto the cad so there is now a full cad of the easypad. I also attached the 3d models to the footprints in kicad to get a full render of the pcb with all the components. I also took a while to work on the code for the easypad, for which I used qmk firmware. I currently have it set in the code for wasd, 1, 2, 3, escape, enter, put the pc in sleep, power, and shut it down. Once I have it built I also want to try and get a button that launches straight into steam big picture mode. The encoder is set to control volume, and the OLED displays the status of cap, numlock, and the current layout. After building it, I also want to change this to do something cooler but this code was pretty hard to understand for me so I’m going to keep this code for now. As for the easypad, once I’ve setup a github I think this should be ready to ship!

Updated Case Design, Updated PCB, & A Start on the Firmware
I added some decals to the PCB (which was more annoying than I thought it would be), cleaned up some of the wiring by utilizing vias, and I shifted the microcontroller closer to the edge of the PCB so the USB port is easier to access. As for the case, I added the proper mounting holes (and have decided to go with a sandwich style case), along with some decals including a hack club flag and a coolish looking vent. I still need to add a cutout for the USB on the microcontroller, but after that I think the case will be basically done. Now, I have moved on to the firmware side and am using QMK to make it. Hopefully it goes well :)

Finished the PCB Design + Starting Case Design
Managing the PCB’s wires took a while and after doing it the first time I realized the white boxes around the key, or switches, weren’t supposed to overlap, but they were on my PCB. I ended up having to redo the wiring but it was definitely easier having done it once already. You can see my PCB design attached below.
I also started working on the case for the macropad using Onshape and making the top plate ended up being a bit harder than I thought it would because I had to measure the distances and manually position all the holes (although for the keyboard matrix I just used a linear pattern). You can see my so far very basic and incomplete case below. I plan on adding more flair, screw holes, and a cutout for the usb, but I’ve been mostly focused on finishing the top plate so far (which I did :) ).

(Almost) Finished Movement, Camera Following & Currently Working on a Combat System + NPC Behavior

• Movement is almost completely done, I only need to add a jump motion (which hasn’t been necessary yet so I decided to focus on other things)
• The Camera following system also took a while and a bit of debugging since I’ve never really tried to make a full 3d 1st person game in unity before, but now it works. Also I am trying to adjust the sensitivity levels for the camera rotation so that it feels right so it would be appreciated if you could let me know whether the sensitivity in this video feels right (although as it gets closer to shipping I’ll probably have it be adjustable).
• As you can also see in the video I made a terrain and it was my first time doing it, so right now its mostly plain (and there are no structures yet).
• My attempts at UI so far really only involve the game pause screen that you can see because I want to wait till I spend some time on the aesthetics of the game and the branding to fully develop the UI.
• I am now working on the combat system; if you saw in the video the mace the character was holding moved back and forth a bit, which was my attempt at a combat system (spoiler alert: it did not work). I am still trying to make it work in a system where the player drags and holds a mouse click and then their weapon follows the mouse, to make a more interactive combat system and experience.
• I am trying to add NPC behavior too into the game, which is why you can see another soldier on the map, but I am just getting started so it doesn’t do anything yet. Specifically, I’m going to start with hostile NPC behavior.
• You can also see a very low quality screenshot of a 3d character I was attempting to make using blender (the assets you see in the video are from the Unity store that I found and will hopefully only be placeholders till I make some of my own). However, as trying to make some space on my computer’s storage, this file was accidentally lost forever so all I have to show for it is the screenshot from lapse :( Now that I’ve done it once though, hopefully the next time will be much easier (and faster).

Finished the Schematic Design!
After a bit of research on which pins connect where, I have finally finished schematic for my custom macropad featuring an OLED display, a 3*4 keyboard matrix, and one rotary encoder. I think this has no errors but if you do spot any please let me know. I am also currently working on finishing the PCB design now, given that the schematic is done.