Current risks are that PCB does not come in time or does not work properly. This would be very unfortunate and hard to combat if it went wrong, to aid in preventing this, we spent countless hours ensuring the PCB design was as best as it could be, checking with professors and TA’s to help ensure everything would work properly and testing on a breadboard.
No changes have been made to system design.
Updated scheduled was changed last week and discussed in team demo/last week reports.
Tests we have run:
Cell:
- Testing in areas with low/high amounts of cellular devices and interference nearby (testing speed of communication, receiving/transmitting data as well as overall time it takes for text to send)
- GPS coords testing [this is still being worked on/tested] ie with geoFence and ensuring quick oscillations of the GPS trigger have a back up to stop sending triggers in situations where they may have forgot to turn the geofence off. And overall testing location accuracy (down to almost +- 10 meters)
BTE:
- Same as cellular but also testing main controlling aspects of the ESP32 with CELL and Mobile app.
- Flash storage and receive times of BTE update of preferences (SOS #’s, geofence location and radius, triggers)
RFID:
- RFID testing is still going on and won’t fully be able to be testing most likely until sodlered onto the PCB. Since we only have one RFID, and it is already pretty janky when it comes to testing (as we have to hold the wires into each pin of the RFID and not move a muscle to ensure it works), we will either have to come up with a better testing setup, or try to get the PCB solder done as soon as possible.
Overall all these tests will be used to see if we still fit our original requirements as stated in the beginning team reports. As we are able to test more in this last week, we will have a much better understanding of what is up to out standard and what is not, and possibly what standards we over or under estimated.