In the month of September, several preliminary actions were taken in an effort to clearly define the scope of the project. Among these actions, a team mission statement was established, a problem-action-resolution plan was developed, and a customer voice table / stakeholder table was completed. Following these initial actions, a first iteration proof-of-concept was designed and constructed. In the first iteration, a basic transceiver and receiver were created that can send binary files between two devices.
After completing the first iteration proof-of-concept, several performance tests were conducted to determine the overall efficiency of the module. Among these tests was an estimate of the round-trip delay time (RTT) which exemplified how long a given packet would take to travel between a local computer and the LiFi module. The results of these performance tests indicated that improvements would be best suited towards allowing N>1 channels so that multiple media access could exist concurrently within the system.
For the month of November, the team plans to further investigate the creation of a dedicated chip and the development of a GUI. The dedicated chip may be put on hold until a hardware model is devloped and thoroughly tested. Analog-to-Digital Converters arrived which are being used to develop the hardware model. A first iteration of the GUI was developed in HTML markup language. The POC can be found in the tab labeled "LiFi Portal" listed above. More information to follow.
This is the first week that the team is back together and working on this project for the Spring 2020 semester. A team meeting was held on 1/23 to discuss goals and objectives for the upcoming weeks.
Middleware Development
Software Development
Hardware Development
Significant progress is being made on the physical prototype. Final components are being purchased and assembled. CPEs are continuing to research middleware & TCP/IP integration
Hardware Development
In the week of 2/10, the team focused on the development of specific middleware to communicate between the datalink and transport layers. A software workflow is shown to the side.
In this simple model, the processor cycles through 4 unique tasks, each containing their own message queue. The message queues act as buffers for the middleware system. The workflow illustrates how the program responds to different events as a result of incoming messages.
This week, A priority Inversion matrix was developed which maps out the resource allocation for three tasks when only one resource is available. This method was developed as a part of the CPE545 Data Structures Lecture. This matrix is particularly important for resource sharing on the Raspberry Pi when multiple signals are trying to access the Pi core at any one time.
An experimentation of the Simple Network Management Protocol (SNMP) was used to test the feasibility of the protocol. The team tried an implementation developed by Net-SNMP.org but was not satisfied with the results. The protocol actually caused transfer speeds to slow down which was not ideal.
Investigation of another alternative is taking place but the team will likely have to develop their own modified version of the SNM-Protocol due to the fact that all network protocols are meant for WiFi, the current industry standard.
The team developed an elevator pitch to convey key ideas and minimum viable product to stakeholders. The pitch emphasizes the limitations with current solutions and how LiFi can improve upon them. The MVP is a USB adapter designed for any PC or Mac that runs Linux, Windows, or MacOSx.
The team also began working on a project poster to showcase the science behind LiFi technology and the adapter that is being designed. The project poster should be finished by the following week.