Posted on

Sophia’s Status Report 4/8

This week, I focused on hardware and software communication for the purpose of our interim demo. We were able to get the hardware communication with the software working serially through a USB cable on desktop Unity with Uduino. We additionally were able to test it and get Wi-Fi communication working as well. However, the moment we tried to port it to Android phone, the app was unable to detect the hardware pen prototype. As such, we have began discussing alternatives such as trying Bluetooth communication instead and writing our own network socket. We have additionally looked into other packages we could potentially use, but writing our own likely will be the best idea. Our schedule has been updated so we are currently on track. If we keep up the pace and dedicate some more time outside of class and potentially on the weekends, we are hopefully on track to reach MVP and have something cool to show for our final demo. 

Next week, we will spend some more time trying to troubleshoot the Wifi communication once it has been ported to Android phone. If that doesn’t work too well, I will assist Anthony to hopefully get Bluetooth communication working well. Additionally, I will be working on the calibration of our pen to hopefully get better data points that can be sent to the Unity App as well. We have not done any specific testing yet, but as soon as integration has been complete, we will start running the line tests that we have described in our design review. 

Posted on

Joseph’s Status Report for 4/1

This week I was finally able to complete the line rendering algorithm. In other words, I  have successfully ported to the phone, a Unity app that draws a 3d line in space whenever you hold a finger down on the screen and move the phone around. Right now the way we decide the points in space where the lines are drawn between is gotten from the touch input on the screen. Eventually, we plan to replace this touch input with the data gotten from the hardware pen. This is something that we hope to be able to do this following week using Uduino, even if the data isn’t 100% accurate. Otherwise, we are on schedule, as integration of hardware and software was planned for a little later. While my teammates figure out the Uduino, I plan to start integrating cloud anchoring into the software so the line drawings are stored in the cloud and able to be viewed by multiple devices.

Posted on

Sophia’s Status Report 4/1

The beginning of this week was spent trying to figure out the how to determine distances from the raw IMU data. Instead of using the orientation vector, which was causing issues as discussed in my previous status report, I have decided to use the gryo parameter instead.  I have found a couple tutorials on how to incorporate a gyro parameter in order to potentially get better rotational orientation. As of now, from the acceleration data, I “double integrate”  by multiplying the acceleration vector by the time stamp. From this, I generate positional (x, y, z) coordinates. I spent the rest of the week working with Anthony on our hardware and software communication with Uduino. I wrote a very simple test script that tries to send “Hello” to Unity, but there were a lot of struggles trying to get Unity to work in the first place. The testing for this communication will need to be carried over into next week. Below is our code repo that we will be updating with our scripts.

https://github.com/murrowow/18500-capstone-hardware

As of now, we are technically ahead of schedule since integration between hardware and software is a little later. However, the hardware itself is still not fully able to provide extremely accurate distance coordinates. This updating and tweaking of the hardware is meant to occur this week and up to the next week.

Next week will be spent flushing out Uduino for our hardware software communication and figuring our gyroscope in order to get more accurate positional coordinates.

Posted on

Team’s Status Report 4/1

Currently there are no specific risks that might jeopardize our besides what has already been mentioned.

Currently no changes have been made to our design and it is planned to continue with what we have currently planned.

No serious changes have occurred to our schedule besides a slight focus on integration now, rather than later, for our demo presentation. In general though we are on track and the current schedule still applies.

Posted on

Anthony’s Status Report 4/1

This week our group has mainly been focused on making sure we are prepared for our demo presentation. I specifically have been working on the app as mentioned in the previous status report. There was a slight pivot that was mentioned prior though, because I have specifically been working on hopefully integrating out hardware with our application in some fashion. This has been done by trying to figure out how to use the Uduino package in Unity, which will help with sending data over from our pen device to our unity app. I was able to get it to work, and have been able to confirm that the two can communicate with each other.

Currently we are not necessarily behind, rather on track to make progress. This has readjusted our schedule slightly since we had originally planned on intricate integration taking place last, but for the demo and for practical reasons it make sense to get the MVP working.

This next week I hope to get it integrated where our pen device can communicate with the app, and also continue working on the app itself, so it is intuitive for our users to play the game.