Blog Posts

Brick by Bit – Week 7 Blog Post

Week seven marked a pivotal moment for our Brick by Bit team as our project continues to develop in scope and expand in collaboration. This week, our liaison updated us with a list of additional students joining the larger project team, allowing us to gain a clearer picture of how development will be divided moving forward. Within this broader group, new sub teams are forming to focus on key areas such as gateway development, sensor device design, user interface development, software network design, and data security.

Our team met with both the new and previous researchers involved in the project to gain a clearer understanding of their specific research interests and contributions. During a meeting with our liaison and just the IPPD team, we explored different network topologies for the sensors and compared LoRa and Wi-Fi communication methods to gain further insight and direction for our ongoing research.

Our IPPD team’s role within this growing project was further clarified, as we will lead the prototype design phase. This includes conducting in-depth research into each component of the product and maintaining strong communication across all internal teams to ensure a cohesive system-level design.

As we continue refining our approach, we also focused on preparing and practicing our Preliminary Design Review (PDR) presentation. This included participating in a peer review session with other IPPD teams to gather feedback and strengthen our delivery. Looking ahead, we will continue to define the expected deliverables for this semester, ensuring our prototype development aligns with the broader project goals and sets a strong foundation for future progress.

Above shows the whiteboard we used to discuss the different topological options for our system and what our liaison’s main goal is for our team.

Brick by Bit – Week 6 Blog Post

Week six was another step forward for Brick by Bit as we continue to comb through the existing elements to this project and refine our project scope based on new information. This week we received approval from our coach on our Preliminary Design Review (PDR), planned our upcoming PDR presentation for next week, and successfully reached out to previous project researchers to gain additional background information on the previously completed portions of the project.

We created a Trello board to complement our Jira board—streamlining both our task management and technical workflow. Through completing the Preliminary Design Architecture (PDA), we researched specific components of our system to allow us to better define which portions will rely on off-the-shelf parts and how subsystems communicate. The PDA process is a crucial step in our project as our long-term goal is to design a ready-for-mass-production product that is fully engineered with validated supply chains, quality assurance pipelines, and regulatory compliance in mind.

Looking ahead, we will focus on finalizing our PDR presentation, further validating our design choices, and continuing to align our infrastructure development with the larger project vision.

Here is most of the group with our new Trello board.

Brick-by-Bit – Week 5 Blog Post

Brick by Bit had another productive week focused on project refinement and technical advancement. Our team made significant strides in clarifying our project scope and establishing key connections with stakeholders and technical leads through several important meetings. Our session with our liaison, Dr. Costin, provided valuable project and lab insights, including an overview of the SCI-Lab facilities, while our meeting with Dev, the current software lead helped our understanding of the existing technical landscape.

We have successfully narrowed our focus to complement the ongoing secure communication work between nodes. Our primary objectives now center on establishing cloud server infrastructure and creating a gateway-to-cloud connection. This focus will help us deliver a working prototype that serves as a foundation for future feature expansion (in the coming semester, perhaps). During our brainstorming sessions, we generated several ideas including mobile applications, secure over-the-air updates with fail-over strategies, and custom PCB development that we can implement once our core infrastructure is established.

Looking ahead, our immediate objectives include establishing connections with external stakeholders to gain construction site insights, developing multiple architectural diagrams describing our planned system design, researching hardware board testing methodologies for our specific use cases, and preparing presentation materials for our preliminary design architecture review. With our project scope clearly defined, we are set up for implementation of our cloud infrastructure and gateway connectivity objectives. Our focus remains on delivering a working prototype that can serve as a platform for the features we’ve brainstormed.

We have also revamped our logo!

Meeting with our liaison to discuss project details!

Brick-by-Bit – Week 4 Blog Post

Week 4 brought great progress for Brick By Bit, notable in establishing a clear direction for our work this semester. Our focus this week centered around refining our project scope and setting up the collaborative tools needed for project development.

We also began to understand the previous work that has been done on GitHub, exploring the existing codebase and development history. We also created a shared GitHub organization that will be used by all developers working on the project.

In coming days, we plan to conduct thorough literature research which will help inform our design decisions moving forward, such as looking into existing gateways and methods of wireless connection between devices. We will also perform a more in-depth look into the prior GitHub code to better identify areas for optimization.

Next week, our focus will be on preparing our initial Preliminary Design Review (PDR) presentation.

Brainstorming design ideas during our weekly team meeting!

Brick-by-Bit – Week 3 Blog Post

Brick by Bit had a packed third week; we met with our coach, our liaison (gave us a project and lab overview, showed us the SCI-Lab), with Dev (current software lead who gave us a good overview), rotated team roles, updated our logo and name, and knocked out some other assignments.

In class we brain-walked to brainstorm ideas for features that need to be added to the project. We came up with a couple ideas including an app, secure over the air updates with fail-over strategies, custom PCB’s, and more.

After talking with Dev, we have greatly narrowed down the scope of work. He is working on secure communication between nodes, so we will focus on getting the cloud server up and running, as well as establishing a connection from the gateway to the cloud. After these are done we should have a working prototype that we can then begin adding more features too.

Immediate next steps include our team building workshop this weekend, being added to the team’s channel, and scouring it for existing documentation, code, and schematics.

Our group photo from the picture day on Thursday!

Brick-by-Bit IoT – Week 2 Blog Post

This week Brick by Bit IoT met each other, formalized a team structure, and created an identity for ourselves. We also made advances towards meeting our coach and liaison next week, with plans to gather more information about the project we have been tasked with.

We agreed to rotate roles every two weeks, and for the first week we assigned: Richard (Team Lead & Meeting Facilitator), Austin (Timekeeper & Scribe), Sam (Travel Coordinator & Research Liaison), Justin (Web/Blog Owner), and Mina (Timeline Manager). We selected our team name—Brick by Bit IoT—and sketched logo ideas of a brick dissolving into 1s and 0s. We sent our first weekly memo and a memo template to the coach for approval, discussed how we’ll handle weekly blog entries, and coordinated with Lawrence to schedule a lab tour.

Next week plans include having our meetings with the coach and liaison, getting a better understanding ofr the project and process’s we will take to complete it, and hopefully begin to set up our development systems with tools such as git and jira.

Blog Example #2

SLDR 2019 Video

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Blog Example #1

Gainesville, FL, USA – SEPTEMBER 12: Entrance Sign at the University of Florida on September 12, 2016 in Gainesville, Florida.

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.