Team Status Report for 4/30/22

As of right now there are no clear risks that could jeopardize the project. The only potential issue that could happen is that when we try to integrate the system with a mobile battery back, the voltage or amperage might be off so it might cause some sort of issue. We have accounted this through a few ways. We made sure to check all the specs of what we are buying and ensuring that it matches the specs of the Jetson, lidar, and camera. If worse comes to it, we have an extra Jetson on standby with all of our code pushed such that if there is an issue, we can immediately move to the other device.

No changes as of now to our system expect we hope to add the battery pack soon.

No updates on the schedule!

Fayyaz Status Report for 4/30/22

This week was mostly focused on getting things ready for the end of the semester. I mostly worked on refining and building the final presentation that was given on Wednesday. I believe it went well and I felt like we were able to showcase all the things we wanted to discuss with the professors and to the class as a whole. Besides that, I also worked on the poster and designing that for the demo next week. Lastly, we did some testing and bought some materials to move towards mobility of the system.

We are on schedule and hope to finish everything up as time is winding down!

We hope to complete the final report, make the system mobile and do automobile testing this past week.

Fayyaz Status Report for 4/23

This past week, there was clear significant progress made within our group, hitting near our MVP.  Regarding the work that I did over the past week, there was a quite a few.  The first being that me and chad worked together to scour through the YOLO code and were able to successfully print out and grab the coordinates of the bounding boxes that were being drawn per frame.  From here, we integrated both the lidar with the single Jetson as we found it did not create that much latency. With both components together, we needed to send over the coordinates to the Lidar script. We tried to make a ROS publisher node in the YOLO script but the paths of the dependencies were really messed up and convoluted. So, I wrote a function inside YOLO that constantly writes to a file that coordinates of bounding boxes in the most recent frame. Then, I wrote a ROS publisher node that took the coordinates from the script and published to the topic that Ethan’s node was subscribed to. From there, everything kind of came together!

With this done, we are basically on track with our schedule and all is left is testing, flushing out the range of our program, and physical components.

Next week, I hope to print out rest of acrylic  for design, test the system more with cars and people, and change the range of the system.

Here is the link to a video of a base showing of our system: https://drive.google.com/file/d/1uesYUynypOKnusUUs-6F8mhb_bZTSKB7/view?usp=sharing

Fayyaz Status Report for 4/16/22

This past week I helped two main things. The first being helping Ethan with the Lidar. We were able to use the TimeSynchronizer package that synchronizes incoming channels by the timestamps contained in their headers to allow for clear data input from both the Lidar and the camera at the same time. We used this website as a reference (http://wiki.ros.org/message_filters) .

The second thing that I worked on was finally working on the physical design aspect of the system. I thought this would be done the best through using SolidWorks and using 3d printing. After measuring the length, width, and height of all the components, I sketched a 6x5x6.5 inch box with shelves to hold the components. Below is a picture. 

After submitting the design, though, I was told that the printing failed and the design was too big. From here, I decided to pivot to acrylic and wood design and put the pieces together.

Now that Chad got the camera working, I feel a bit better and believe that we are on schedule. In the next week, I hope to make the physical components with the acrylic, have the Jetsons talking to another (if Chad’s work allows for it), and start prepping for the final presentation.

Team Status Report for 4/10/22

As a team, we are trying our hardest to ensure the delivery of our project. The most significant risk right now is the camera still not working. As we have reflashed the jetson and are using some new libraries, we hope it should be working soon but there are definitely some hardware limitations when it comes to running the YOLO algorithm. This is being managed as we are working on other aspects of the project and ensuring those are working such that when the camera is figured out, we can move swimmingly. If it does not work on the Jetson, we were thinking of switching to a RPi to see if the space and CPU there could handle what we have.

No changes as of right now to the design of the system.

We did update the Gaant chart and schedule to account for the delay with the camera.

Fayyaz Status Report for 4/10/22

This past week I was helping with a few things but due to carnival and the demo, nothing incredibly substantial. After the failures with the camera on one of the Jetsons, this week I worked on reflashing the device. This was different than previous as this time I was trying to see if there were settings or libraries install earlier in setup that could have contributed to the disfunction of the Yolo algorithm. After consideration, I decided to only flash and do the base setup to ensure nothing could be done. This was done and it seems there have made some progress with the new algorithm.

Besides this, I have written a basic script for the two jetsons to talk with one another and hope to implement it when both jetsons are done with their individual components.

My progress is a bit behind as it depends on both the camera and Lidar working which is not the case right now.  As this is the case, I hope to come in and work with chad to see what we could to speed up the camera process and ensure there is something that we can work with soon.

In the next week, I hope to deliver the new script I created as well as a basic design (again) of our cage to house the components.

Fayyaz Status Report for 4/2

This past week I transitioned to working on two main components. The first being the design of the project. After looking at the individual designs of each of the different aspects of the project, I came to realization that maybe using two jetsons would be better than one. After discussing with the group, we thought this idea would be great. From here, I started looking to the physical components that could house all the parts of the project. I decided to looking in to some 3d modeling programs to design it.

More importantly, after deciding on using two Jetsons instead of one, I was trying to figure out how to have both jetsons talk to one another. After talking with the professor, he mentioned to use Ethernet. I did some research and found this website as a reference: https://youtu.be/VbuHzujRcNo . After the others are done setting up their work more and focusing on other aspects, I hope to focus on this.

I think my progress is on schedule. There is a bit more work now but, I think we are still on track.

Over the next week, I hope to implement the jetson communication and have some base physical design to present.

Fayyaz Status Report for 3/26

There was two main things done on my end this week. The first was prepping and setting up for the ethics discussion by going over the assigned questions and the work assigned to us. Mostly though, I worked on setting up the other Jetson that is to be used for testing. I made sure to flash the same image as well as install all the same packages on this device that the other device also had.

We are still on schedule and hope to even move faster now that we have two jetsons that each device can work on.

In the next week, I hope the Lidar is fully setup and we can start the integration of both the Lidar and camera together.

Team Status Report for 3/19

As of right now, the biggest risk to the project is again the integration of all the different components. When we were integrating the camera with the Jetson, we could tell the temperature of the Jetson had increased as well as there was a clear lag in the OS. This could be a potential issue down the road when we try to run the Lidar in coordination with the camera. This could lead to overheating and the process slowing down entirely. The risks are being managed by looking in to cooling devices such as a fan as well as maybe looking at low intensity object detection. We do not have a clear contingency plan if they both do not work together but after seeing the camera in action this week, we discussed that it is needed by this time next week.

No definite changes were made to the design besides the use of wired ethernet. We have bought a wireless wifi adapter though and hope to use that instead of the wired connection soon. The change was not necessary and it was only some opportunity cost of some lab time.

No schedule changes have occurred. We are still on track.

Look at Fayyaz and Chad most recent reports for some pictures of what we got working!

Fayyaz Status Report for 3/19

This week of the project consisted mostly of me getting the Jetson to work. After receiving the Jetson, I tried flashing the OS on to the Jetson but when in boot mode, it would stay on the Nvidia Logo.  After looking at this website for guidance, https://forums.developer.nvidia.com/t/jetson-nano-2gb-stuck-on-boot-screen-with-nvidia-logo/169601 , I found out that there is a separate image that I have to flash (https://developer.nvidia.com/embedded/jetpack). Once loaded, there was another issue that I ran into. In order to download the necessary packages for the camera and the Lidar, internet is needed. This was an issue as there is only wired internet on the Jetson and the network did not recognize the device. After many painful hours of trying to figure out the issue, and talking to 3 different professors, we recognized to register the MAC address on the CMU website. After an hour or so, the device was connected.

From here, we installed the camera packages on the Jetson using this guide https://www.youtube.com/watch?v=dHvb225Pw1s&ab_channel=JetsonHacks . We attached the camera and were able to run some initial tests. Below is a picture of the initial setup.

Our project is on schedule and I intend to help Ethan with the Lidar setup next week. In the next week I hope the Lidar is setup and there is a comprehensive environment such that we can take in readings from the Lidar and show them on the Jetson.