-
Notifications
You must be signed in to change notification settings - Fork 1
Blog 2017 02 17 Winter
The tables are now updating each time a packet is sent. We have a test launch in March so we will get plenty of data to test with once that happens and see if we have any hiccups in our code. Revisions were made to the technical and design document. We also created a powerpoint presentation with our progress thus far. OneNote is currently holding all the revisions and brief biographies about all the team members.
I will be adding another table for the second set of telemetry packets we will be receiving for the rocket. It will be easier to read if it is split up that way. Also, I am planning on asking the Rocketry Team if they would like only certain variables displayed because currently the amount of information we have clutters the screen. It may be useful for the test launch though to ensure everything is working properly.
The propulsion team has not heard back from the airport about testing there. Unfortunately, this may mess with the test launch dates. We can still use data from previous launches if needed.
We finished our revisions, and powerpoint presentation. My revisions was on the technology review in the retrieval section. I had added Node and updated the conclusion section of it. In our powerpoint presentation I spoke about the retrieval of the data and did a demonstration of our alpha version of our software as well.
Next week when we meet with the avionics team we need to find out how they want us to setup the recovery system. We have it planned if the node server shuts down then it will automatically restart. Also if it has errors on the avionics side then they will have to unplug it and restart the system.
I accidentally go my days mixed up and showed up to recording of the presentation late but I had my own mic so I was able to record my audio at home. I had some issue with the screen recording with the audio also the first time I used it but I figured it out and got it working for the demonstration slide.
This week we got the Raspberry Pi set up, but had a couple of hang-ups. It can be hard to find a place with a screen on campus to hook the Raspberry Pi up to. We tried LINC, where they have some really nice-looking tables with TVs and video hook-ups, but most of the equipment there is broken. We got the Raspberry Pi hooked up to the projected in KEC 1003, but I didn't want to type my ONID password in front of everybody, so I wasn't able to hook up the Raspberry Pi to the wifi and download the software we need, but it should work (in theory).
This week I'm going to finish configuring the Raspberry Pi as well as finish one of the critical components that still need to get done: the telemetry protocol parser. Now that we have the protocol from the ECE team, we can actually implement it and start really testing the software.
Some schedule conflicts made it hard to get the presentation done, but we should be able to get it done on time. Other than the Raspberry Pi issues outlined above, there were no other major issues.
OSU High-Altitude Rocket Team