Difference between revisions of "GeoLink Testing"

Revision as of 15:05, 29 May 2018

This page is supposed only for Testing pilots. The aim of the testing is to find a problems in currently implemented features.

1 Download

Here pilots can download the latest testing software and firmware. Make sure you are using always the latest version.

1.1 Spirit FBL

Software: 2.5-rc1

Firmware: 2.5-rc1 - DOWNLOAD

1.2 GeoLink

Firmware: 1.0-rc3 - DOWNLOAD

2 Questions

Whenever you are unsure about correct behavior please send email to tomasj@spirit-system.com. Subject: GeoLink Testing - question.

3 Suggestions

You can also share your suggestions - even if some feature is working correctly, you can reveal how do you think it would be better.

All suggestions can be emailed to tomasj@spirit-system.com with subject GeoLink Testing - suggestion.

During the testing we are not implementing any new feature. The aim is for improving current features only.

4 Reports

We wish that you will send all testing reports to email tomasj@spirit-system.com with subject GeoLink Testing - report.

It is enough to send reports describing a problem. But if everything is working correctly, you can share the experience too.

Report should contain:

• Currently used firmware version from both Spirit FBL and GeoLink
• Information about your model
• What feature was tested
• Detailed report about how the feature worked (especially what was wrong).
• Attached 4ds file (optional)

If there is something wrong, please note at which flying time (minutes) the problem happened. And/or if the problem was happening from the beginning or only later with increasing flight time. The report should contain also what was done from the beginning of the flight as a possible problem could arise from such maneuvers/actions.

If reporting a problem it would be helpful to describe how to replicate the issue.

5 Testing instructions

In order to start with the testing, please install the GeoLink according the instructions first.

Then we recommend:

• To test always only one feature at the same time.
• To test all the features in a high altitude to avoid any possible damage from unexpected behavior.
• To not fly too far so that model is well visible.
• If some problem occurred, try to power up everything again and repeat the test to observe any difference.