| | 83 | |
| | 84 | **WEEK FIVE** |
| | 85 | * Automated process of connecting & checking wifi connection (pinging) |
| | 86 | |
| | 87 | |
| | 88 | * Created a tunnel between R-pi and data base |
| | 89 | |
| | 90 | |
| | 91 | * Successfully created backend email sender & appointment form on website |
| | 92 | |
| | 93 | |
| | 94 | * Added foundation for interactive grid on website |
| | 95 | |
| | 96 | **WEEK SIX** |
| | 97 | * Continued exploring Unity |
| | 98 | |
| | 99 | |
| | 100 | → Began connecting Unity/ROS - SLAM for robot navigation |
| | 101 | |
| | 102 | * Set up remote desktop on orbit node for Unity |
| | 103 | |
| | 104 | **WEEK SEVEN** |
| | 105 | * Set up PTP on Pi's |
| | 106 | |
| | 107 | → Pi's do not have hardware timestamping |
| | 108 | → No IEEE 1588 , must aim Pi at boundary server |
| | 109 | → Solution: use software emulation |
| | 110 | → Build kernel that allows ptp4l to run |
| | 111 | |
| | 112 | |
| | 113 | * Looked into using Raspberry Pi cameras for camera data |
| | 114 | → Successfully captured videos and viewed them using VLC |
| | 115 | |
| | 116 | * Created the coordinate system for the test room |
| | 117 | → Discussed the predetermined activities and based layout on them & outlet placement |
| | 118 | → Turn on Light |
| | 119 | → Walk in/out of room |
