The range limitation for waypoints for MatrixNav8b, AileronAssist8b, and MatrixPilot2.0 is dictated by the fact that the waypoint is specified in meters as a 16 bit integer. So, the largest X or Y value that you can specify for a waypoint is approximately 32 kilometers, or about 20 miles.
So, the X and Y coordinates of each waypoint must be within 20 miles of the initialization point.
This also means that if you are flying in manual mode and switch to RTL mode, the plane must be within a square with a 40 mile edge, centered on the initialization point, when you switch from manual to RTL, in order for RTL to work.
I'm wondering, is the UAVDevBoard suitable for Quadcopter-project. The plan is to make it fully autonomous, but with the upgrade possibility to use radio to control the machine in the future. I have a few questions that I need answers to move on. I think this is the forum where is the best ackowledge:
I think there might already be people working on using the UDB to control a Quadcopter, hopefully some of them might reply as well. In the mean time, I'll do my best to answer your questions.
1. Yes, you can connect most electronic speed controllers to the UDB. ESCs (like the one you linked to) read a 'servo' pulse and convert it into 'throttle' for electric motors.
2. The current matrix pilot firmware for the UDB implements up to six output channels using the 'spare' pins on the current UDB.
3. You can connect multiple batteries to multiple ESCs (I've done this on several multi engine airplanes already) but you need to be careful of three things. First, make sure that only one of the BEC (5v regulator built into most ESC) is active. In my planes, I do this by disconnecting the red wire (positive voltage) from the remaining ESCs. Secondly, remember Ohm's law (V=IR) and keep your power and voltage in line between the motors, ESCs, and batteries. Lastly, remember that without a very good ESC, the same setting on multiple ESC will not always produce the same output from the attached motors.
4. The noise has as much to do with the ESC as anything else. I've seen ESCs that have clean output from the BEC but still have all kinds of EMI and similar ones that have no noise. I don't know of a fool-proof solution to this other than diligent testing.
5. My ESCs all run just fine off the servo pulses (40Hz, generally) so I'm a little surprised that yours would be that different. Is it possible that the 8KHz is the frequency that the motor control is running at? Either way, the UDB is a very powerful hardware platform, so I would imagine it can support 8KHz if you wanted to, that would just require more customization of your firmware. Be careful also, that the current firmware updates all of the servos in the same frequency and 8kHz will do bad things to servos.
6. See above about using the extra pins for IO. There is already a second UART on the 'auxiliary' pins header which is designed for telemetry (and supported in the current firmware). We are also working on a new firmware that might support I2C expansion to external peripherals.
Ok, I just found one UDB Quadcopter project. It is easy to find something if you know what to search. And thank you for quick answer! It's nice to have reply right away when is studing something and thirsty for information.
UDB still looks suitable for me. You did clarify many things that I have been thinking. This (PWM: 8 KHz FET: 12) was the line that made me to think that ESC needs 8kHz control pulses. Probably that 8kHz is the frequency of ESC.
I2C feature sounds really good! Is there some forum or site from where I can see what all new things you are working with? You did wrote that I2C expansion MIGHT be in the next release, so I did get curious that what IS coming :) Is the firmware ready in days, weeks or months? :P
yes, there is a UDB list on Google Groups (http://groups.google.com/group/uavdevboard/) where we discuss new features for the upcoming firmware releases. At this point, the next firmware release hasn't been set yet, but I'd guess it is at least three to four months out (May?). Of course, you can always check out the 'development' version of the firmware to use before then if you'd like to.
There is a UAVDevBoard3 in the pipeline, we are just starting to design it. It will use the flat Invensense 500 degree/second gyros, which we have recently flight tested in planes and helicopters. They work great. No problems with vibration.
I'm assuming those new gyros are retrofitted to the current board? If so, will that be an option for the rest of us? I'd love to know if they're more resistant to RF interference than the old gyros are.