Leland’s Status Report for 10/26/2024

This week, I followed the directions from this GitHub repository to download the necessary eYs3D libraries, but also some nice wrapper functions. After that, I was able to run a video demo of the depth map and the normal frames. The GitHub repository included these demos to test and calibrate the camera. Here is a link to my work document for this week.

Unfortunately, my progress is not on schedule. I wanted to include the ArUco tag calculation this week, but I wasn’t able to get that done. I have developed a schedule of my total workload for the next coming weeks. This will help me keep up with my other classes and free up time to spend towards this project. This is included in my work document. Despite being behind on schedule, I’m proud of my work this week. I had a lot of other hard class assignments to complete this week, and I got those done. I’m convinced that if I keep up this pace, we’ll be back on track by next week.

I have my deliverables for next week in my work document, but I will reiterate them here. By next week, I hope to write my own python script that utilizes the software packages I downloaded. This script needs to be able to identify and locate ArUco tags. I need the relative XYZ position of the tags and their orientation.

Team Status Report for 10/20/2024

Over the fall break, our team has worked in preparation of our parts being delivered. Which as of now, we have submitted all the orders for the parts we know we need. We have continued to research and implement the necessary software packages such that we can build our systems quickly when our hardware parts arrive.

The biggest risk right now is running into too many problems when parts arrive and we start putting together our prototypes. We have tried to mitigate this risk by spending our time preparing the software needed to control the system before and over the fall break.

The only change that was made this week was a 3D printer driver board that was acquired to replace the four separate driver boards. Jack made this change which he mentioned in his status report for this week.

Part A: Our system does include global factors. Part of the purpose of our project is to provide chemists with a safer environment to perform in a chemistry lab. Ideally, our system can be used anywhere in the world where one wishes to perform chemistry. Thus, it can keep people safer anywhere around the globe.

Part B: The Third Hand project could possibly have a cultural factor related to worker safety laws. Our product is designed to increase worker safety in chemistry lab environments. Thus, our team must consider the workplace safety requirements in the United States and how it will relate to our robot. Also, we should consider changing our testing strategy to better highlight our robot’s contribution to the safety in chemistry labs.

Part C: The Third Hand could have a environmental factor that should be considered. It is possible to have accidental spills that could leak toxic chemicals in the lab. Chemicals could spill down a drain contaminating the water, or evaporate and pollute the air. Our robot can be used in tandem with a proper work environment for it to prevent spills to harm individuals or the environment.

Leland’s Status Report for 10/20/2024

This week I started setting up the software environment to use the eYs3D stereo camera. I have created a Linux workspace on Ubuntu to run the image processing. Also, I have found the necessary SDK (Software Development Kit) to digitally capture frames. In combination of these two, I was able to produce some code that will capture frames with the SDK and convert them to a OpenCV matrix for further image processing. Here is a link to that code snippet.

Overall, I’m still on track for further camera calibration and ArUco marker detection for next week. For next week’s deliverables, I hope to be able to produce some visual examples of capturing and processing the camera frames. Also, I’d like to implement a code example that captures position and orientation of ArUco markers.

Team Status Report for 10/5/2024

The most significant risk to the project at the moment is not being able to build the prototype on time. The mechanical aspects of this project have been more challenging than anticipated. As a result, we could not finish the mechanical design as soon as we would have liked. The contingency plan right now is to have a meeting tomorrow to figure out what aspects of the system we have finalized and try to order parts for those aspects, so that we can get some subsystems out ASAP.

Another risk is that we build the force sensing/feedback protype, and the user experience is not as intuitive as we had wanted. We have looked into previous research and found that the most common solution approach for force feedback is to use haptic engines that could direct haptic feedback to specific parts of the user’s hand. However, such hardware is out of reach in terms of budget. The best way we can mitigate this is to build the remote controller prototype as soon as we can so that we have time to iterate.

In terms of design changes, we realized that ARUCO tags will not provide sufficient depth precision. We estimated depth precision to be ~7mm based on the tag’s size and the pixel resolution. Therefore, we switched from a monocular web cam to a binocular stereo cam to measure depth directly as opposed to via ARUCO tags. This will end up costing less because we are getting it from the 18-500 inventory, so it’s a win-win.

No schedule changes?

New cam!

 

 

Leland’s Status Report for 10/5/2024

This week, I changed my camera design by picking a different type of camera. I made this change because the depth perception of a monocular webcam was not good enough. Also, the stereo cam I want is in the 18-500 inventory which is great for budget. Also, I researched some pseudo-code to start crafting what the OpenCV code will look like when I get the camera.

I’d say my progress is just a little behind where I want to be. I’d really like to get the camera next week and set it up with my laptop. Then, I can set it up with a stand and a dummy remote with Aruco tags to start calibration and computation. In the meantime of getting the camera, I can continue to build the pseudo-code for the image processing. Another thought is I will need to start crafting pseudo-code for the UART protocol of sending and receiving data from the two ESP32s we have. I’d like to include that in my report next week too.

My work this week

Team Status Report for 9/28/2024

Normal Report

What are the most significant risks that could jeopardize the success of theproject? How are these risks being managed? What contingency plans are ready?

As of now, the greatest risk to the project is finishing up the design process and ordering parts. I hope there are little to no changes after the design review next week, so that we don’t need to spend more time designing. The team has been working hard this week designing and preparing for the design review in order to minimize risk of redesigning. The team is committed to working extra hours if needed.

Were any changes made to the existing design of the system (requirements,block diagram, system spec, etc)? Why was this change necessary, what costsdoes the change incur, and how will these costs be mitigated going forward?

The camera FOV was switched from 90 degrees to 78 degrees because I had trouble finding a good 90 degree FOV camera that fit the more important specifications. This change comes at a cost of needing to raise the camera higher off the table which our camera stand will account for.

Provide an updated schedule if changes have occurred.

No scheduling changes were made.

This is also the place to put some photos of your progress or to brag about acomponent you got working

*Nothing for now…

+ the Status Report 2 assignment

Please write a paragraph or two describing how the product solution you are designing will meet a specified need…

Part A: … with respect to considerations of public health, safety or welfare. Note: The term ‘health’ refers to a state of well-being of people in both a physiological and psychological sense. ‘Safety’ is the absence of hazards and/or physical harm to persons. The term ‘welfare’ relates to the provision of the basic needs of people. –By Jack He

Our product is intended to promote health and safety by putting them out of harm’s way.  Lab environments can contain a wide range of hazards: flammables, explosives, toxic vapors, bio-waste… In addition to the obvious risk of severe injury, many substances found in a lab have negative long term health effects. For example, formaldehyde, commonly used to preserve tissue samples, are linked to neuraldegenerative diseases and cancer. By building a teleoperation interface capable of the fine manipulation tasks performed in a lab, we aim to make it easy for researchers to use our robot to perform these tasks from a safe location. Therefore, this system will promote both health and safety for the community of scientific researchers.

Part B: … with consideration of social factors. Social factors relate to extended social groups having distinctive cultural, social, political, and/or economic organizations. They have importance to how people relate to each other and organize around social interests. — By Zhenghao Jin

The remote-controlled robotic hand I am designing is primarily intended for lab environments, addressing the need for safer and more efficient experimentation. By enabling users to manipulate lab equipment and hazardous solutions remotely, the product minimizes physical risks and ensures a controlled, safe process for delicate or dangerous experiments. This solution is cost-effective and adaptable, making it a valuable tool for a wide range of labs, including those with limited safety resources. It enhances collaboration among researchers by providing a safer and more reliable way to conduct experiments, aligning with the broader goal of improving safety and efficiency in scientific research.

Part C: … with consideration of economic factors. Economic factors are those relating to the system of production, distribution, and consumption of goods and services. — By Leland Mersky

Our product does not nicely meet a specific need with consideration of economic factors, as our product mainly meets the needs for public health and safety. The purpose of the robotic arm is to handle possibly dangerous chemicals to perform common tasks done in a chemistry lab. That being said, I can’t think of a way how this project affects the production, distribution, or consumption of goods and services.

Leland’s Status Report for 9/28/2024

This week, I have finalized a design plan for the camera station. I made some calculations to estimate what specifications would be necessary for the camera and the camera stand. I also picked out a specific webcam and camera stand that will satisfy my specification requirements.

I am on track, as I have a complete design and almost complete bill of materials. This is the goal that I had in last week’s status report.

Next week, there will be design review presentations where my team will receive design feedback for our project. By the end of next week, I want to use that feedback to finalize all our design plans and start ordering parts.

My work this week

Leland’s Status Report for 9/21/2024

This week, I researched more thoroughly what will be needed for the computer vision part of the project. I have looked at the pros and cons for different types of cameras like a USB webcam vs a stereo camera. I have also started to look through OpenCV libraries to get comfortable with them. Lastly, I modified the website a little to make it look nicer.

We are on schedule. This week and next week are for design and ordering parts.

I hope to have an almost complete design and list of parts for the camera/laptop station part of our project.

Team Status Report for 9/21/2024

 

At this point in the course, the biggest risk to the project is organization and communication within the team. We all we need to be doing our parts in the individual work, but we have to come together to plan for each week to come. These risks are being managed by our team’s iron will and dedication. We make sure to meet multiple times a week, so that we can stay on top of our progress.

We’ve had some discussion throughout the week on the design of our project. There have been minor changes, but we’ve really just been fleshing out our design more rather than making changes. At this point, we all have a good understanding of the project as a whole. This week, we started to work on the different sub-systems of the project individually.

No schedule changes have been made. Overall, we are making our final, initial design decisions and have started forming a list of parts to order. The goal is to have a close to complete list of parts by the end of next week.