Rensselaer Center for Open Source Software

alan schimmel

We have been working on our project from two sides, the first is the planning side thinking about the end users experience, and the other is getting the actual hardware designed in such a way that enables the easiest end user experience. To accomplish this we have incorporated an Arduino bootloader compatible MCU into our schematic. The TI Battery Management chips we are using communicate using SPI. Because of the arduino environment, we will be writing libraries for our chip, so that the end user can use simple commands in the code that will be written (ex. MeasureV(), BalanceCell2() ) By hard coding all the leg work inside an arduino library, the main C file will be very clean and almost like English, and that will make our board less intimidating to those will less coding experience.

The schematic is being created in the software KiCad, and we plan to finish the schematic by the end of the weekend. Next week we will take our schematic and turn it into a PCB layout and by the following week have boards and parts ordered.

Zachary Minster

After multiple weeks of trying to fix bugs with getting our Parse database working, I am happy to announce that the backend is up and kicking! Querying and posting from the app is finally doable! I have created a simple friend request feature that is integrated with the database. Right now, the user has to manually enter the name of the friend to add. However, soon I hope to have a search feature for friends to allow users to navigate through a list of other users that are potential friends. I am currently working on finishing the friend request implementation on the back end (which is much more complicated than anticipated, since Parse only allows interaction with the currentUser object. Meaning that friendships out of the box can only occur one way. But I have a work around that should work, and am working on its implementation now) as well as creating a way for users to view current outstanding friend request and accept/deny them. Since I haven't worked on the UI side for a while, Im playing catch up this week trying to learn from John's progress. The goal is in the next few weeks to have a fully functional friend system integrated with the app. Then, we will work on merging the iOS backend with the Android backend so that the app can work completely cross-platform. It is an exciting time for me and for the entire Where R U? team! --Zach

Aaron Gunderson

I have been working on the backend API integration with Github and through together a little front end test too. Progressing at a reasonable pace. Working with the team getting their development environments set up. They will soon be claiming features and working on them. Can't wait to get everything up and running!

Blake Lingenau

The needed first step has been taken. Basically we had a text file with with information on an item and its corresponding itemID. I wrote some code that would parse through this file and extract which items are usable. Some items are non-tradeable so I made API calls for each itemID, determining if there was a sell quantity. I stored all the relevant items in a .csv file. Our next step would be to efficiently store this data in some sort of database and have it update itself every so often to account for additions of new items or the discontinuing of old items.

Michael Dewey

This week, I have been planning out how to implement it with the racecar. This may seem early for implementation, but if I better understand how it is going to be used, I will be able to design the app more efficiently.

This week, I spent some time learning about android development. I have sufficiently learned enough of android to begin work on the official app. I have learned the basic lifecycles of an app, basic GUI concepts for android development, and worked on a few sample projects.

I want to discuss what is going to happen in the next few weeks. What I plan to do this week is create a basic app with either a basic GUI component, or a text based output system. This way, I can stress test the app and make sure the hardware I have is up to par with my end user expectations, aka I don't want to provide a product that will have latency issues or a polling problem.

Next Page