Voltage Error

I crunched another ~5 Hours trying to fix the original system and set up the new top system. I was searching for the source of the error that had dropped the voltage on the breadboard rails, and after inspecting every cable and rail, I found out that the problem was caused by the ESP32 sending packets too frequently, thus creating a disturbance in the voltage. I got around that problem by increasing the voltage until the system turned on, which, in my case, meant that because I increased the contrast a lot, the event was turning a row of empty squares into two rows. This was different from the fast flashing problem, and it was really hard to detect.

Top Circuit

I also assembled the other circuit after I fixed the first one, and I had some troubleshooting with the ESP-NOW connection and the screen receiving the low voltage. I broke a few solder joints along the way, and I had to combine the male-to-male and female-to-female cables to get the necessary male-to-female cable, which helped me identify some of the faulty cables that had been hiding.

For the past ~5.45 hours, I tried assembling parts once again, but I failed multiple times due to either one of my solders being broken, or ESP32 having power issues. After a long time of fixing, I gave up on using the power source while debugging, and I got the circuit to work on direct USB connection, so I narrowed it down to a problem caused by the battery, and my measurements with the multimeter confirmed that some of the voltage I gave was missing, thus causing ESP32 to rapidly open and close, and for blank white slots to appear on the LCD. I also wrote the code for the top part, and I got the MAC addresses of the ESP32s, so they can communicate now. Another thing to mention is that even in the slots of the power rail of the breadboard, the missing voltage is seen, so I am going to take another approach, and test elements one after another, but not individually since they all work individually.

I spent more time on developing the design. I came up with the idea to make ticket shapes for the sections and the navigation bar, and splitting the diagram into 3 as I needed left, right, and middle sections on my design. I created them using flexes and a flex container, and I did some debugging to display content in them.

After doing the split, I created ticket as a css class with a clip-path class named cut-corners to get a basic ticket shape which I did get. Afterwards, I tried making a bigger copy of that ticket that would sit behind the smaller one to give a sense of a border, but I struggled on that for some time, because the solution I tried with .ticket::before didn’t work as it got its clip-path directly from ticket, thus making their dimensions same, and making the bigger one disappear, so I thought of doing it with a container. I created ticket-wrapper, and turned .ticket::before to ticket-back, did some splitting up in html, and I got my desired look on the page.

I started writing the html code as I completed the tutorial, and made a simple site with some descriptions, but it lacks design elements as I only used a background indicator and nothing else in css file. My next step will be to organise those with proper design in css.

I made some more progress on writing the code for the top ESP32. I mentioned in the Stasis that I will be using the ESP-NOW communication system to display the time as the main case calculates it. I now made a dummy MAC address and changed the message structure to send the data via direct text rather than unorganised bytes and an on/off signal.

I came here after Stasis closed while doing my project, so feel free to look at my project details and devlogs there.