Difference between revisions of "GeoLink Testing"
(→Testing instructions) |
(→Testing instructions) |
||
| Line 61: | Line 61: | ||
In order to start with the testing, please install the GeoLink according the [[GeoLink|instructions]] first. | In order to start with the testing, please install the GeoLink according the [[GeoLink|instructions]] first. | ||
| − | + | === Recommendations === | |
| + | |||
*To not perform testing of the features if you are not confident. Instead you can help with testing the software, translations and similar. | *To not perform testing of the features if you are not confident. Instead you can help with testing the software, translations and similar. | ||
*To test always only one feature at the same time. | *To test always only one feature at the same time. | ||
Revision as of 17:39, 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.
Contents
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 - DOWNLOAD
Firmware: 2.5-rc1 - DOWNLOAD
1.2 GeoLink
Firmware: 1.0-rc3 - DOWNLOAD
1.3 ChangeLog
All news that were introduced from 2.4.3 are visible in the Spirit Settings - Connection tab - News. After updating from official version it should be ready to fly. No change is required after the update.
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 benefits
Testing member that will help noticeably will receive a free Spirit System product.
6 Testing instructions
In order to start with the testing, please install the GeoLink according the instructions first.
6.1 Recommendations
- To not perform testing of the features if you are not confident. Instead you can help with testing the software, translations and similar.
- 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.
6.2 How long we need to test?
Testing is needed until all possible problems are resolved. Then we will release the product officially. Less problems mean faster release.
7 Testing Progress
- Logging: N/A
- Geo-fence: N/A
- Return to Home: N/A
- Position Hold: N/A
- Altitude Hold: N/A
- Altitude Limit: N/A
