Wednesday, March 8, 2017
this week: We met to talk about how we want to go about starting our project. We ordered parts and discussed specific functionality that we want to include in the LAURA E Ink "app" and the iOS and Web Apps.
moving forward: Gather around a whiteboard to draw out the entire system and communication between functional blocks. Order all hardware.
this week:
moving forward:
this week:
moving forward:
this week:
moving forward:
this week:
moving forward:
Wednesday, March 22, 2017
this week:
moving forward:
this week:
moving forward:
this week:
moving forward:
this week:
moving forward:
Wednesday, March 29, 2017
this week:
moving forward:
this week:
moving forward:
this week:
moving forward:
this week:
moving forward:
Wednesday, April 12, 2017
this week:
moving forward:
this week:
moving forward:
this week:
moving forward:
this week:
moving forward:
Wednesday, May 3, 2017
this week:
this week:
this week:
this week:
Friday, May 12, 2017
private demo: By the private demo, we were not quite where we wanted to be with our deliverables. While our hardware was assembled, the ribbon cables we ordered to connect our custom PCB and the LoRaBugs were extremely delicate, and we were unable to fold them, without breaking them, into the shape we needed for our hardware to fit inside the 3D-printed cases with the E Ink display screwed down.
The LoRaBugs were able to send and receive message packets peer-to-peer, as well as through the central gateway, though at this point we were still having issues integrating the BLE and LoRa code. As such, there was no communication between the LoRaBugs and our iOS app, though both ends were ready and tested for our decided protocol. The central gateway LoRaBug had the capability of writing message packets over serial to our Raspberry Pi server for storage in the database and display on an admin-facing web app, though we did not have this up and running.
Finally, assets were able to send accurate Decawave localization data of their locations relative to nearby beacons to the RPi server over a TCP socket for storage in the database and display on the web app.
public demo: For the public demo, we finally had our BLE and LoRa code integrated! By the end of the demo, we were able to use Abhi's phone to connect to one LAURA device over BLE, send a message packet on the network to another LAURA device connected to Madison's phone over BLE, and see the message pop up both on the E Ink display of the receiving device and in our iOS app, in under one minute. Unfortunately, in the time between our private demo and the public demo, the same Decawave code that was working to send asset localization data stopped working, and we were unable to demonstrate this aspect of our app.