S. S. L. A. M. Update 2

---

Quick Overview

---

Hello, for those who haven’t seen this project yet, I am creating a new way to create SLAM for robotics. Usually, to create SLAM, people have to spend tens of thousands of dollars on LiDAR. However, for my rookie FRC team, I am going to use a stereo (camera) system to find the 3d position of objects.

---

What I Just Did

---

I added in more location-finding systems. As I said in the previous log, I am taking advantage of the Apriltags that will be positioned around the arena so that the robot can find its position on the field using a coordinate system and its angle of orientation. I am also in the process of making a pathfinding system that takes into account every obstacle on the field. The function would take an arbitrary coordinate as the target and compute the direct line from the robot to the target. If there is an obstacle in the way (Computed mathematically), the program will estimate an arc around the obstacle to the target.

S. S. L. A. M. Update 1

---

Quick Overview

Hello, I am creating a new way to create SLAM for robotics. Usually, to create SLAM, people have to spend tens of thousands of dollars on LiDAR. However, for my rookie FRC team, I am going to use a stereo (camera) system to find the 3d position of objects.

---

What I Just Did

---

I laid out the basic computational framework for this project. I am going to be running the computation in Python, and the robot commands in C++. I am using OpenCV to do some of the math and taking advantage of the Apriltags to find the robot’s position on the field.

FINAL Handcryption Build

---

Sorry if its been so long, I have been doing a lot this summer, but here is what happened over the past month. (Time shown does not reflect time spent, as hackatime wasn’t working when I was coding and I didn’t record the building process)

---

So, I was able to assemble 1 working device with the one working e-ink display I had left. I was on a time crunch as I was trying to qualify for Outpost. I was able to submit it in time, and I shipped it for Outpost. The device has all the previously specified features, such as peer-to-peer messaging and message history. The microphone and speaker are very weird, as they are analog, so the audio quality is questionable. However, the project works great!

---

At Outpost, I had a really good time with my fellow Hack Clubbers. Thank you Hack Club for making this all possible. (P.S. You should allow me to remove my request for funding and submit it normally).

FINAL Handcryption Build

---

Sorry if its been so long, I have been doing a lot this summer, but here is what happened over the past month. (Time shown does not reflect time spent, as hackatime wasn’t working when I was coding and I didn’t record the building process)

---

So, I was able to assemble 1 working device with the one working e-ink display I had left. I was on a time crunch as I was trying to qualify for Outpost. I was able to submit it in time, and I shipped it for Outpost. The device has all the previously specified features, such as peer-to-peer messaging and message history. The microphone and speaker are very weird, as they are analog, so the audio quality is questionable. However, the project works great!

---

At Outpost, I had a really good time with my fellow Hack Clubbers. Thank you Hack Club for making this all possible. (P.S. You should allow me to remove my request for funding and submit it normally).

Handcryption Status Update 0.1.1

---

This is a short update. I am currently waiting for funding, but I was able to design some button caps in CAD.

---

I really hope I get S tier so I can get to Open Sauce

---

Update On Me: My schedule is super packed. I’m starting to regret taking on a lot of things this summer.

Handcryption Status Update 0.1.1

---

This is a short update. I am currently waiting for funding, but I was able to design some button caps in CAD.

---

I really hope I get S tier so I can get to Open Sauce

---

Update On Me: My schedule is super packed. I’m starting to regret taking on a lot of things this summer.

Hancryption Status Update 0.0.4

---

What Happened?

---

So, I added in one last new feature to my code: voice messages. In order to play the audio, I have decided to ditch the piezo and use an actual speaker breakout, and I have updated the BOM on my Github as such (check the last devlog).

---

Other than that, I have been cleaning and debugging the code, and adding in comments; all to get it ready to request for funding. For some reason, my hackatime on the Stardance website isn’t synced with what my Hackatime dashboard says. So, I’m posting this much eariler than I would have wanted in hopes to fix that issue.

---

What’s Next?

• Sneak Peak at Funding Request Version
• Timeline

Handcryption Status Update 0.1

---

What’s Happening?

---

So, I have been able to clean up everything in my code. I have added comments and the ability to connect to Wi-Fi. All of my code has been uploaded to GitHub for review for funding.

---

Also on GitHub are my 3D models. Be aware that the part models’ heights are an estimate based on the total height of the part given (if that makes sense). When printing the cover, I am planning to swap the filament from PLA to TPU to make the pads holding the buttons squishy.

---

I am a little disappointed that the hackatime in my VS Code editor stopped recording time, and I lost 2 hours, but I will just use Lapse from now on.

---

• GitHub Repo

---

Handcryption Status Update 0.1

---

What’s Happening?

---

So, I have been able to clean up everything in my code. I have added comments and the ability to connect to Wi-Fi. All of my code has been uploaded to GitHub for review for funding.

---

Also on GitHub are my 3D models. Be aware that the part models’ heights are an estimate based on the total height of the part given (if that makes sense). When printing the cover, I am planning to swap the filament from PLA to TPU to make the pads holding the buttons squishy.

---

I am a little disappointed that the hackatime in my VS Code editor stopped recording time, and I lost 2 hours, but I will just use Lapse from now on.

---

• GitHub Repo

---

Hancryption Status Update 0.0.4

---

What Happened?

---

So, I added in one last new feature to my code: voice messages. In order to play the audio, I have decided to ditch the piezo and use an actual speaker breakout, and I have updated the BOM on my Github as such (check the last devlog).

---

Other than that, I have been cleaning and debugging the code, and adding in comments; all to get it ready to request for funding. For some reason, my hackatime on the Stardance website isn’t synced with what my Hackatime dashboard says. So, I’m posting this much eariler than I would have wanted in hopes to fix that issue.

---

What’s Next?

• Sneak Peak at Funding Request Version
• Timeline

Handcryption Status Update 0.0.3.9

---

What Happened?

---

Ok, big change to the workings of this device. Previously, this device could only work locally, but through my Raspberry Pi server and a domain through ngrok, I can make the device work on the cloud, and I have altered the server code and main device code to work this way.

---

Also, instead of using IPs to identify devices, I am using my own identification system that is like a phone number, a sequence of 9 digits. I recognize that this may be a small number of available sequences, but for now, it is a good amount. I can change this later.

---

So, to send messages now, instead of using a socket, the device sends an HTTP request to the ngrok domain hosted by the Pi. The request includes the message, the destination’s ID, and the sender’s (the device’s) ID. The server then stores this information in a “mailbox” -a collection of all sent messages. The receiving device, every 2 seconds, is sending an HTTP request to the server asking if there is anything in its mailbox. If so, the server returns the message(s) with the sender ID so the receiver can match that to a contact.

---

The cloud update has made my overall code length shorter, as most of the long sequences of code have been simplified to shorter HTTP requests.

---

Also, as promised, this is my part BOM: https://github.com/Joethebeast-coder/Handheld-Encryption-Device/tree/main/Hardware

---

What’s Next in 0.0.4?

---

 - Extra Add-on Device Features
 - Maybe more website interactivity

Handcryption Status Update 0.0.3.9

---

What Happened?

---

Ok, big change to the workings of this device. Previously, this device could only work locally, but through my Raspberry Pi server and a domain through ngrok, I can make the device work on the cloud, and I have altered the server code and main device code to work this way.

---

Also, instead of using IPs to identify devices, I am using my own identification system that is like a phone number, a sequence of 9 digits. I recognize that this may be a small number of available sequences, but for now, it is a good amount. I can change this later.

---

So, to send messages now, instead of using a socket, the device sends an HTTP request to the ngrok domain hosted by the Pi. The request includes the message, the destination’s ID, and the sender’s (the device’s) ID. The server then stores this information in a “mailbox” -a collection of all sent messages. The receiving device, every 2 seconds, is sending an HTTP request to the server asking if there is anything in its mailbox. If so, the server returns the message(s) with the sender ID so the receiver can match that to a contact.

---

The cloud update has made my overall code length shorter, as most of the long sequences of code have been simplified to shorter HTTP requests.

---

Also, as promised, this is my part BOM: https://github.com/Joethebeast-coder/Handheld-Encryption-Device/tree/main/Hardware

---

What’s Next in 0.0.4?

---

 - Extra Add-on Device Features
 - Maybe more website interactivity

Handcryption Status Update 0.0.3.6

---

What Happened?

---

I added a cool new feature to the Handcryption device-GROUP CHATS!! This allows every user with a Handcryption device who opts to join the group to participate in conversations, fostering a more connected experience among users. I learned how to use Flask (thanks to GeeksforGeeks), which enabled me to seamlessly integrate the group chat feature into the server code running on the Raspberry Pi.

---

In addition to the chat functionality, there is now a website hosted on the Raspberry Pi’s IP address that displays all the messages in the group chat. The caveat is that every message on the website is shown in its encrypted form to maintain security and confidentiality.

---

Looking ahead, I plan to implement a feature that would allow Handcryption users to sign in to the website. This will enable them to view messages in a decrypted format, enhancing user experience while still prioritizing privacy. I believe these developments will significantly improve user engagement and create a more dynamic platform for communication.

 My device(s) are becoming more and more like a phone

---

What’s next?

---

 - Preliminary BOM
 - Increase Website Functionality
 - Timeline Estimation
 - Code Cleanup and Extra Features

---

Photo Description: Some of the server code for the group chat

Handcryption Status Update 0.0.3.6

---

What Happened?

---

I added a cool new feature to the Handcryption device-GROUP CHATS!! This allows every user with a Handcryption device who opts to join the group to participate in conversations, fostering a more connected experience among users. I learned how to use Flask (thanks to GeeksforGeeks), which enabled me to seamlessly integrate the group chat feature into the server code running on the Raspberry Pi.

---

In addition to the chat functionality, there is now a website hosted on the Raspberry Pi’s IP address that displays all the messages in the group chat. The caveat is that every message on the website is shown in its encrypted form to maintain security and confidentiality.

---

Looking ahead, I plan to implement a feature that would allow Handcryption users to sign in to the website. This will enable them to view messages in a decrypted format, enhancing user experience while still prioritizing privacy. I believe these developments will significantly improve user engagement and create a more dynamic platform for communication.

 My device(s) are becoming more and more like a phone

---

What’s next?

---

 - Preliminary BOM
 - Increase Website Functionality
 - Timeline Estimation
 - Code Cleanup and Extra Features

---

Photo Description: Some of the server code for the group chat

Handcryption Status Update 0.0.3.5

---

What Happened?

---

I was able to set up a server on my Raspberry Pi 4 with the help of Copilot (I do not know Flask in the slightest). So now, when a device wants to send a message, the audio recording is sent to the Pi, requesting that it be translated to text. I’ve been experimenting with Claude on making a website to monitor the server’s status, but I will talk about that more in a later update if I decide to go that route.

---

Today, I was able to make a CAD model of the housing of the device (The process of which is posted on Lapse). I have to admit, it looks a lot like the phreakers from the early days of calling.

---

What’s Next?
- Decision on whether to pursue web monitoring
- Preliminary BOM
- Timeline Estimation
- Extra Features for the Device

Handcryption Status Update 0.0.3.5

---

What Happened?

---

I was able to set up a server on my Raspberry Pi 4 with the help of Copilot (I do not know Flask in the slightest). So now, when a device wants to send a message, the audio recording is sent to the Pi, requesting that it be translated to text. I’ve been experimenting with Claude on making a website to monitor the server’s status, but I will talk about that more in a later update if I decide to go that route.

---

Today, I was able to make a CAD model of the housing of the device (The process of which is posted on Lapse). I have to admit, it looks a lot like the phreakers from the early days of calling.

---

What’s Next?
- Decision on whether to pursue web monitoring
- Preliminary BOM
- Timeline Estimation
- Extra Features for the Device

Handcryption Status Update 0.0.3.2 (Big News)

---

What Happened?

---

So, I was able to add in a UI that includes settings, contacts, message history, as well as battery status. In the settings, the user can change the volume of the piezo, as well as clear the files on their device (Contacts, Known IPs, and Message History. When hovering over a choice, the icon (the volume icon, for example) repeatedly switches from inverted to normal.

---

However, while I was debugging, I found a MAJOR problem. My measly ESP32 microcontroller doesn’t have enough CPU and RAM to run the speech-to-text model. However, I can pivot from this by using the VOSK model paired with my Raspberry Pi 4 that I have on hand as a server to run the model for the microcontroller. This opens up a whole new possibility. We can now have a main hub that monitors the devices, serves the speech-to-text requests, and sends the text back.

---

What’s Next?

 - Speech-to-text code for the Raspberry Pi
 - Communication Protocol between the device and Pi

Handcryption Status Update 0.0.3.2 (Big News)

---

What Happened?

---

So, I was able to add in a UI that includes settings, contacts, message history, as well as battery status. In the settings, the user can change the volume of the piezo, as well as clear the files on their device (Contacts, Known IPs, and Message History. When hovering over a choice, the icon (the volume icon, for example) repeatedly switches from inverted to normal.

---

However, while I was debugging, I found a MAJOR problem. My measly ESP32 microcontroller doesn’t have enough CPU and RAM to run the speech-to-text model. However, I can pivot from this by using the VOSK model paired with my Raspberry Pi 4 that I have on hand as a server to run the model for the microcontroller. This opens up a whole new possibility. We can now have a main hub that monitors the devices, serves the speech-to-text requests, and sends the text back.

---

What’s Next?

 - Speech-to-text code for the Raspberry Pi
 - Communication Protocol between the device and Pi

Hancryption Status Update 0.0.3 (Combined)

---

What Happened in 0.0.2.3?

---

I have created a parts list for this project:
Adafruit:
- Adafruit Electret Microphone Amplifier - MAX4466
with Adjustable Gain
- Adafruit 2.13” Monochrome eInk / ePaper Display
with SRAM - 250x122 Monochrome with SSD1680
- Adafruit ESP32-S2 Feather - 4 MB Flash + 2 MB
PSRAM - STEMMA QT / Qwiic
- Lithium Ion Polymer Battery - 3.7v 100mAh
- Tactile Button switch (6mm) x 20 pack
- Small Enclosed Piezo w/Wires
I have decided to use the Adafruit ESP32-S2 Feather as my microcontroller, as it takes care of the LiPoly battery charging, so I don’t have to buy extra parts for it. I can also charge the battery through the USB-C on the board. It also has many GPIO pins that I can give to my e-Ink display, as well as the switches (6).

---

What Happened in 0.0.2.5?

---

I created a wiring diagram for the components listed in the parts list. The time-lapse can be seen on Lapse*.

*I forgot to add the piezo in the time-lapse, and I wired the SDA and SCL pins to buttons, which was not supposed to happen, so later, I added the piezo, and moved the button wires to spare analog pins. You can see these in the screenshot below.

---

What Happened in 0.0.3?

---

I made a complete draft of the code for the device. I added all of the button logic and basic e-ink display code. I added a loading screen with “HANCRYPTION” in block text and a sleep screen. To “power down”, when the user holds the power button for more than 1 second, it goes into deep-sleep, which is basically off for microcontrollers. If it is less than that, it just goes idle. Of course, this is not the final code. I will keep adding more and more features that are compatible with the current set of parts I already have.

---

What’s Next in 0.0.4?

---

-Extra UI Features
-Possibility of Games

---