For this week, the main focus was figuring out how to manage the signals between the 2 ESP32s by the ESP-NOW protocol. There was also research done to see if the ESP-NOW protocol was enough to handle the proposed signals from our design review, which was another crucial part to this week’s update: I wanted to follow the feedback we got as well as write out the full report with the new updated information. I created a new updated diagram with our proposed design in order to better fit what we now want to create as our pillbox, along with corresponding datapath. Based on this, it is clear that the ESP-NOW is not enough, but it would be useful for individual testing as part of our prototype process. I am and continuing to look at the alternative Bluetooth option provided for the ESP32 Nanos. It was also important to gather the material I do already have in my possession for simulation and testing with first the fundamental proposed materials that we have for our overall project on the electrical end.
Progress is behind on ordering the parts, but that will be handled as soon as we are back online from break. The time-heavy portions would be the mechanical and coding parts for both hardware and software, so actual manufacturing/combining of all parts is set later as a priority in comparison.
I will start by creating a prototype with just the electrical components (some of which aren’t going to be official parts), starting with a basic servo (as depicted below) connected to a ESP32 so that the servo-testing can commence with wireless connection using the ESP-NOW protocol first, then shifting over to the bluetooth feature already included on the ESP32 Arduino Nano which I already have in my position to see if there would be a greater efficiency than the simpler ESP-NOW protocol which can’t handle complex data packets.
Here is the image of a personal ESP32 Nano Arduino with a test-use servo (no where close to the 20kg, but the connection works regardless).
updated datapath:
updated diagram:
