10/20/14
This past week I spent a lot of my time working on the MATLAB code for the trajectory. I modeled the trajectory in 2D-space and for a while I was pretty sure I had it modeled correctly. Although, I was not sure and kept trying to tweak the code until now it does not work. But it should be easy to revert back to the working version.
I found also that for the Advance class you must use a battery to control the servos of at least 100 mAh and that there is also a section stating that gyroscopic assist is allowed. Could this be used to make sure the plane is level while approaching the target? That will be something to look into.
There are no clear rules on runway time, or how long we can sit still on the runway to get a GPS fix. It looks like as long as the GPS doesn’t take 5 minutes or so that we’ll be ok. But it looks like we can take some time on the runway prior to launch.
This week I also configured the air speed sensor for third party use. This should enable me to use the sensor with the microcontroller and I began writing code in the IDE to read the sensor. The GPS sensor I had less luck with and was unable to figure out how to enable it for third party use.
This weekend Ervin and I also wrote procedures for testing the motor/propeller combinations and charging the batteries. Hopefully we made these instructions clearer than they were made last year for us.
Ervin and I plan to test different combinations this week and find maximum thrust combinations. We have not been able to push the power limiter over 1000 watts by using the motor and battery. Maybe now we will try and use a power supply and a large load in place of the battery and motor.
By this time next week I plan to have the microcontroller interfacing with the air speed sensor and resolve my SRG situation. We should also have triggered the power limiter to gain a better understanding of the limitations.
Recent Comments