Chris, when we wrote the uBlox code, we did try to accomodate as many different stock configurations as possible, as just amongst our group of developers we had units with the different diydones store configs, units from sparkfun, and i think some units from elsewhere.
So at the moment we should be able to work with any uBlox config, as long as it's running at 9600 baud. Auto baud rate detection and setting is on our to-do list, but unfortunately our clock speed means we cannot run higher than 19200 at the moment, so we still couldn't talk to ardupilot configured units. This is something we can fix long term, but i requires a fair bit of work on low level code to move to a different clock speed, so it's probably a way off. It is unfortunate as there seem to be a few products out there communicating at 38400 that we would like to talk to. We will definately be looking at our choice of oscillator for the next hardware revision of the board, to broaden the range of baud rates we can run.
In the meantime we will update the documentation to make it clearer to new users what they need to buy in terms of uBlox units to get up and running. Can I ask what documents you are using as your primary reference to guide you (the hardware manuals linked from here or the wiki?)
I have one question regarding UAV Dev Board. I have read somewhere that ReturnToLaunch could be performed if 3 miles distance is not reached. So is this true in V2? If yes would it be possible to remove such limitation?
I'm not quite sure whether I have understood your question correctly. Let me re-state it what I think you are saying , and then answer it.
Question: When the plane is more than 3 miles from the launch site, will the Return To Launch function does still work ?
Answer: Yes. The UAV Devboard code will work at up to 20 miles from the Launch site. The limitation of 20 miles is caused by using a 16 bit number to represent distance in meters North and East of the launch site. Return to Launch mode will normally engage when the signal is lost by the radio receiver from the transmitter - which will happen long before 20 miles.
If you program the "failsafe" in your radio receiver to continue to provide servo pulses to the UAV Devboard "failsafe channel when the radio signal is lost, then it is possible for the plane to continue around a waypoint course, even when the radio signal has been lost.
Thank you Pete.
This was exactly what I was looking for :). I have red Bill's text that this was somehow limited to 3 miles. I am happy that now this limit is not an issue. I am FPV flyer and I will have Dragon Link UHF long range system which can do more than 15 miles.
But do bear in mind, that you will be one of the first people to test the UAV DevBoard beyond a couple of miles. The only person that I'm aware of flying distances out of up to 2 miles away would be Ric in Switzerland. He has posted a video of one of his long range flights here.
Some of the earliest versions of the firmware for the UAV DevBoard had a 3 mile navigation limit. The most recent versions (MatrixNav 1.8, AileronAssis 1.8, and MatrixPilot 2.0) have a 20 mile limit from the initialization point. That is, plus or minus 20 miles in X, Y, and Z. So, in principle, it would work at an altitude of 20 miles.
By the way, I do not know what the laws are in Poland regarding how far away you may fly. You might want to check with Chris Bosak on that. In the US, we must maintain visual contact with the plane at all times.
Thank you Bill, thank you Riccardo,
I believe there is no such regulation in Poland regarding small (under 5 kg) aircraft models flying under 300 meters high yet. Despite of this our small FPV community (rc-cam.pl) is very sensitive about safety. Thats why I am thinking about UAVDB as "last instance" if anythig else would fail.
@ Ric - I hope you will fly and make movies despite your recent crash. Do you have any guesses about the reason of the "death spiral" of your model? Chris could have pointed some good directions IMHO.