> For the complete documentation index, see [llms.txt](https://knowledge.flyability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.flyability.com/third-party-software/faro-connect/general-information/geoslam-connect-end-of-life.md).

# GeoSLAM Connect (end of life)

GeoSLAM Connect is no longer supported. If you still prefer or need to use it over FARO Connect you must create a Legacy local user account to use the software.

To do so, ensure you have downloaded and installed GeoSLAM Connect 2.3 and the Flyability scripts. Links provided below.

Then follow the Legacy local user creation guide, link below.

[Download GeoSLAM Connect](https://www.flyability.com/hubfs/GeoSLAM_Connect_for_Elios_3_Release_2.3.0.zip)

[Legacy local user creation](https://drive.google.com/file/d/1z2mQ5G7wCv87oSgXyRs7L67X0k61QchO/view?usp=drive_link)

[Elios 3 Training for GeoSLAM](https://drive.google.com/drive/folders/1jfoSDM9FqSkzYB6-cloJ8JblBDE6mTFh)

{% hint style="info" %}
**In case of an issue or error during the installation or data processing:** 

Contact Flyability support with your complete dataset, GeoSLAM support will not handle any request 
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.flyability.com/third-party-software/faro-connect/general-information/geoslam-connect-end-of-life.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.