-
Notifications
You must be signed in to change notification settings - Fork 1
Meeting tracking
During the 13-week semester, we worked on the project during these weeks and had meetings to advance our project.
We had a starting meeting, in which we wrote the general program for the semester. Additionally, we went over the specifications and started searching for solutions.
We tested various hardware devices using the ESP32 microcontroller and Arduino IDE (writing code in C++). Additionally, we tested some previously developed solutions for generating code using blocks.
We started investigating the Google Blockly library for JavaScript.
We first burned a MicroPython firmware on an ESP32 microcontroller and wrote a batch (BAT) script for burning MicroPython automatically. Additionally, we started using MicroPython by connecting via the PuTTY serial client.
We wrote scripts in MicroPython and started working on a seminar we gave about 'digital twins in industrial IoT'.
We had a few difficulties using screens with MicroPythons, and we finally detected a fault in our ESP32 microcontroller. After replacing the microcontroller, we were able to activate the screens.
We worked on the hardware and could use two screens simultaneously using MicroPython.
We worked on the website and on some of the blocks.
We gave a seminar about 'digital twins in industrial IoT'.
We presented our process in a peer-review meeting. Additionally, we met a UX/UI designer and decided on the design of the puppet.
We decided on the technical aspects of the puppet and sent a concept for 3-D printing.
We manage to support a multilingual website and focused on the Hebrew version as a proof of concept.
We created a module for uploading files to Firebase and worked on project branding. We finished writing the PuppetBlocks standard library and supported all the features in the website.