I prefer to use 500 degrees/second rate instead of 2000 degrees/second, because the 500 degree/second gyro will have lower effective drift and noise than the 2000 degrees/second one. Since they are both made by InvenSense, I would expect they would both have about the same percentage drift and noise. So, the 2000 degrees/second one will have about 4 times the drift and noise of the 500 one.
We have done tests on the 500 degree/second gyros, and they actually will work up to about 700 degrees/second.
Some members of the team have been flying AcroMasters, with prototype UAV DevBoards with the 500 degree/second gyros. The fastest rotation rate of an AcroMaster is about 700 degrees per second, and if you blink, you will miss it. A complete 360 degree roll takes a little over 1 second. From the videos that I have seen, the Acromaster represents very nearly the "upper edge" of the envelope.
I am not aware of any planes that can roll at 2000 degrees/second, that is more than 5 turns in one second. In any case, I believe the 700 degree/sec actual range of the 500 degree/sec Invensense gyro will handle the majority of the types of planes that people are flying.
A break is just what you need. I find that when I am stuck on something, after I take a break, I come back with renewed energy and fresh ideas.
When you say the lights have stopped working on the UDB, do you mean with or without the the PICkit connected?
The PICkit can stop the UDB from running.
If the PICkit is not connected, the self test program that is on the UDB when it is shipped should turn the LEDs on briefly at power up. It not, then chances are that you erased the PIC. That is no cause for concern. How that might have happened is if you tried to program the UDB after the build failed. At that point, the UDB would be erased.
In any case, I will stick with you until we get your UDB flying. I do not see any reason why we cannot. I am sorry that you are running into so much trouble, but if it is any consolation, it will help others. I learn more from users who run into trouble than I do from those who do not have any problems. So, our experience grows. Soon it will be time for us to revise all of the documentation, there is a lot we have learned lately.
Sorry for the beginner's question. I am about to order all I need to build my UAV Dev Board.
What PICkit do I need: the Starter Kit or the Debug Express? (they are both the same price).
I currently fly with the Remzibi OSD. Do I absolutely need a new GPS (EM406 or Ublox), or do you think the Remzibi GPS might be used for the UAV Dev Board some day soon?
First of all, just in case you are not aware, there is a lot of information on the UAV DevBoard (UDB) project website, under the wiki tab, and there is a discussion group.
Regarding the PICkit, you can buy either the PICkit2, or PICkit3. I prefer the PICkit3, but either one is fine. Regarding Starter Kit or the Debug Express, you do not need either, they include a CD and a demo board. You can buy the "PICkit only", and download the firmware you need from Microchip. If you prefer to have a CD, then go ahead and buy either the Starter Kit or the Debug Express, it makes no difference.
Regarding Remzibi, you can double check with Sid. You can contact him if you join the UDB discussion group. It is my understanding that Sid uses the Remzibi OSD, but he had to buy a Ublox, which is shared by the UDB and the Remzibi.
I do not think the UDB will be configured to use the Remzibi GPS anytime soon.
Now I am confused. Did you pay Microchip for the compiler?!?
You do not need to do that. Microchip's compiler was developed under a GNU agreement, you can have it for free.
If you downloaded the full version of the C compiler, then that is the problem. The full version requires you to buy a license.
You do not need the full version of the C compiler, the evaluation version will do fine. We are not using any features that the evaluation version does not support. Everyone is using the evaluation version. The only thing with it is that it will warn you that you do not have a license, but it will run ok.
If you have paid Microchip for the full version of the C compiler, then they certainly should help you get it running, or give you your money back.
1. You need to register before you log in. If you do not furnish a registered account to login in, it will take you back to the sign in. There is a link at the top of the sign-in page that you use to register. Microchip will give you the compiler, but they will get some information from you first.
2. You need to allow cookies to register and to sign in.
Sorry about my bad english. I want to use UAVDev for telemetry only. I make a PC software to show telemetry but I find serial output rate is not enough to drive my plane in real time. I try modify timer 3 to increse this rate but I can't find where part of code is this. Could you please help me.?
First of all, I suggest that you repost your question to the uavdevboard group. There are more people there besides myself with detailed information about telemetry. In your post, could you give us some more details? What are you trying to do? Are you going to put the UAV DevBoard in a model plane and you want to log the telemetry, or are you going to use a transmitter to a ground station? What variables are you interested in.
Also, there are newer versions of the firmware available on the project's website that will make it easier to do what you are trying to do. Take a look at the discussion of telemetry under the Wiki pages, and also how to gain access to the code repository, where you can get the latest versions of the firmware.
Right now, the telemetry software that is available in the latest version of MatrixNav will send data out of the serial port at 19,200 baud. There are several different message types that you can chose from, including ArduPilot groundstation format. Messages are sent at the rate of 4 messages per second.