Difference between revisions of "GeoLink Testing"

Revision as of 17:11, 1 June 2018

This site is exclusive for Geolink Beta Testers only.

In order to be an affiliated Beta Tester, the prospective pilot must voluntarily sign and submit the Geolink Testing and Collaborative Agreement as provided during the initial steps of pilot selection.

No information must ever be shared to third parties during the entirety of Beta Testing Phase which includes- but not limited to- verbal or electronic communication between Spirit System and the pilot, copies of the companion application, flight outcomes, logs, or pertinent data regarding progress of the Program without prior and approved permission from Spirit System. The only information that can be shared publicly without requiring prior approval are external photographs of the Geolink module as mounted on model helicopters.

GOAL: The primary aim of the Geolink Beta Testing Program is to find bugs in the currently available features of the Geolink module, its Firmware and accompanying Desktop Application. Beyond its current form, no new feature is expected to be implemented at this stage of the process. Only minor additions and those which are deemed to be significantly helpful to the Geolink module’s current functionality will ever be considered. Otherwise, it is to be reiterated that the Geolink Beta Testing Program’s main goal is to make the current feature set as stable as technically possible.

1 Download Section

This is the download section of both the Spirit Flybarless Unit desktop application and associated firmware of both the Flybarless Unit and the Geolink module.

As a beta tester, every pilot is advised to regularly access this page for the latest available versions. Thus Spirit System will make every effort to provide those as they come out of the software development department.

Prior to first use, it is a requirement that both the Spirit Desktop application and firmware of the Spirit Flybarless Unit and GeoLink Module be updated to the latest available versions.

It must be noted that during the initial firmware update of the Spirit Flybarless Unit, all prior settings (including channels, limits, rates, direction etc) from the previous firmware version will be retained and no further adjustments on the Flybarless Unit is required. Simply put, this step is just a regular firmware upgrade of the Fylbarless Unit which is ready to function as is post-update and can be used with no further changes.

1.1 1.1 Spirit Flybarless Unit (Note: The Geolink Module now supports all versions of Fylbarless Units)

Software: 2.5-rc3 [31.5.2018] - Windows OSX Linux

Firmware: 2.5-rc2 [30.5.2018] - DOWNLOAD

1.2 1.2 GeoLink Module

Firmware: 1.0-rc4 [31.5.2018] - DOWNLOAD

1.3 ChangeLog

All feature updates on the Spirit Flybarless firmware from Version 2.4.3 and onward can be accessed and reviewed in the “CONNECTION PAGE” of Spirit Desktop Application at the “NEWS” tab.

All prior settings (including channels, limits, rates, direction etc) from previous firmware version will be retained post-update and no further adjustments on the Flybarless Unit is required.

2 Reporting of Findings

All findings- good or bad- are welcome. If an untoward behavior was noted during a beta testing flight, please follow these Reporting Requirements

      •	Basic information about the helicopter model.
      •	Firmware versions on both the Spirit Flybarless Unit and GeoLink module
      •	A flight log (4ds file) is preferably to be included on the report but it is optional.
      •	GeoLink feature used during that testing flight 
      •	Finally, a detailed report of the untoward behavior of the Geolink feature. Please, include the following.
              o	Type of flight envelope used during the testing flight: F3C type (sport flying) or 3D maneuvers.  
              o	At what duration of the flight in minutes when the incident happened and the final maneuvers made during those last few seconds
              o	Describe in detail if the behavior was also noted at the very beginning of the flight or it only happened as the flight duration progresses.
              o	Include if the behavior is persistent or intermittent.
              o	Describe in detail if certain remedy was done like power cycling of the model helicopter, repositioning of the Geolink module or any other changes that may have resolved or exacerbate the untoward behavior.
      •	The primary goal of the Report is to allow Spirit System to replicate as close as possible the scenario that led to the untoward GeoLink feature behavior.

Please forward all reports to TOMAS@SPIRIT-SYSTEM.COM and use the subject line “GeoLink Testing- Report”.

3 Questions

Please forward all inquiries to TOMAS@SPIRIT-SYSTEM.COM and use the subject line “GeoLink Testing- Question”.

4 Suggestions

At its current form, the Geolink Module and its feature set is known to work adequately within the technical capability of Spirit System after years of research and development. However, all constructive suggestions are welcome specially if the information being provided is unique and can greatly contribute to the improvement of the GeoLink’s capabilities.

However, beyond its current form, no new feature is expected to be implemented at this stage of the process. Only minor additions and those which are deemed to be significantly helpful to the Geolink module’s current functionality will ever be considered.

Please forward all suggestions to TOMAS@SPIRIT-SYSTEM.COM and use the subject line “GeoLink Testing- Suggestion”.

5 Benefits of Being Part of the Geolink Beta Testing Program

At the sole discretion of Spirit System, beta testers with significant contribution to the program are eligible to receive free Spirit System products.

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 Expected Duration of the Beta Testing Program

Similar to most groundbreaking innovations, the duration of the Beta Testing Program may vary. Specially that the goal of this process is to find all bugs on the GeoLink and its accompanying firmware as much as technically possible and with the help of Beta Testers around the globe. It is to be expected that the GeoLink module will only be released to the general public once these set goals are met.

7 Testing Progress

• Logging:

N/A

• Geo-fence:

N/A

• Return to Home:

N/A

• Position Hold:

N/A

• Altitude Hold:

Firmware 2.5-rc2 -> TODO: Option to turn off collective pitch management, preventing inexperienced pilots from changing altitude.

• Altitude Limit:

Firmware 2.5-rc2 -> TODO: Soft deck + adaptive calculation for triggering the rescue dependent on descending speed.

• • Spirit Desktop Companion Software:

Software version 2.5-rc2 -> ISSUE: Random connection instability in Geolink tab. Status: Resolved
Software version 2.5-rc3 + GeoLink 1.0-rc4 Status: Further testing required

• Compass Calibration:

GeoLink 1.0-rc4 -> CHANGES MADE: Simplified Compass Calibration procedure implemented.