-
Notifications
You must be signed in to change notification settings - Fork 1
Blog 2017 04 14 Spring
Originally the terrain that I had created was off in terms of scale to longitude and latitude compared to Google Earth. Al was able to figure out the math behind it and alter it. The terrain also had a distorted height values due to how Blender was adding the modifier for height of the height map image to the flat plane. After speaking to the rest of the mechanical engineers, they said they wanted it to be as close to the realistic area as possible. This lead us to having a quite a flat plane. I have also been working on transparency since that will be useful for showing the different atmospheres that the rocket is going through.
Getting the atmospheres to be at the correct height will be a problem since everything has to be scaled correctly according to the data that we are receiving. The 3.js transparency works, we just need to make sure that we have all the correct libraries for it and that it is set up correctly in the environment.
Telemetry protocol is changing. Hopefully this will be the last time.
This week I switched what type of live line graph I was going to use for our demo. The one I found was much simpler. I also spoke to my old network instructor Ben Brewster about how we should go about receiving the call from the sensor whether we would have to setup a network on the graph code or with the through the packet code itself. He explain both ways and suggested that on the website that we would use would need a simple ajax call and just build the graph in html with the javascript. I tested his idea with another dynamic javascript setup I had an it works.
I want to have a dynamic graph built by the end of next week and we should be ready to integrate with the log that Al built for the expo.
The only real problem I am having is finding enough time to be honest. I wanted to get the graph done by this weekend but I have so much homework that needs to be done first that is why I have to push it back to the end of this week. I should be able to get it done before then but I just don't want to say it will be done and it is not.
This week I got the 3D model of the terrain at the launch site properly scaled in all axes. The 3D model is very flat when rendered this way because the site is in the middle of the desert. However, we may be able to use some lighting tricks to make it more visually interesting.
The telemetry protocol has been a moving target, so I ensured that we are implementing the most recent standard from the avionics team. However, the protocol is going to change again in the next week or two, so this work isn't finished.
This week I'm going to get the 3D model we made loaded into the web interface and ensure that it is scaled correctly by creating some test data that should map to the corners of the 3D model. We can then see whether or not the model is scaled correctly. Additionally, I will keep up with the avionics team to make sure that we are implementing the correct telemetry protocol.
Getting the 3D model scaled took a little longer than I expected, and the telemetry protocol is changing again, so progress was a little slow this week, but there are no significant issues.
OSU High-Altitude Rocket Team