# FARO FAQ / Troubleshooting FARO connect is the software available for SLAM processing Elios 3 collected data. When encountering issues, it is best to consult this page, and then reach out to [Flyability Support](https://www.flyability.com/support-request). Use the following guidelines to find the correct data to share for the quickest resolution. ## FAQ ### What is FARO Connect? FARO Connect is the SLAM processing software used to convert LiDAR data collected with Elios 3 into processed point clouds. It is used in combination with Inspector 5 to export the appropriate dataset for processing. ### What is SLAM processing? Slam stands for Simultaneous Localisation And Mapping. The software uses the LiDAR data and the Inertial measurements of the drone to create a registered point cloud. It is important to close the loop. Closing the loop multiple times during a flight can help with local optimization, increasing the accuracy of the reconstruction. By crossing an older trajectory the LiDAR scans the same area, from the same position helping to better optimize the area. With the multiple optimization of the software a high accuracy point cloud is created.
### Do I need to update the Flyability script when updating FARO Connect? Yes, while there is not a new Flyability script released each time, it is important to ensure the current script is installed. {% hint style="info" %} For perpetual licenses where the maintenance and upgrade has expired leaving you on a previous version. The associated Flyascript should be used for that version. {% endhint %} ### How do I export Elios 3 data from Inspector 5 for FARO Connect?
From Inspector 5:\ (1) Open the relevant flight/inspection. \ (2) Go to the Export data tab.\ (3) Select the FARO tab.\ (4) Choose one or more flights. \ (5) Click Export. ### Is the FARO Connect license tied to a specific drone? Yes, each drone needs its own FARO Connect license to process data collected from it. ### Can I use my FARO Connect license on multiple computers? A license can only be active on one computer at a time . You must deactivate the license on one computer before activating it on another, unless you have purchased additional seats. ### Do I need to create an account to log into FARO connect? Yes, you generally need to create a free FARO Sphere XG account by clicking "Get Started" when you first open the software . If you are operating on a secure network without internet access, you can create a "Local FARO Connect User" to bypass this requirement ### How to process data using FARO connect? Please see the step by step article: [How to process a point cloud?](/third-party-software/faro-connect/how-to-process-a-point-cloud.md) ### What output formats can FARO Connect export? .E57, .las, .laz, .ply, .txt ## Troubleshooting When encountering issues when processing Elios 3 data in FARO connect, the following information can help determine where the issue could be coming from. This information is divided in three categories: License and Activation, Processing failure, and not processing to expectation. Each category provides a list of helpful information to share should you need to contact [Flyability Support](https://www.flyability.com/support-request). ### License and Activation issues *No activatable licenses found*, or *No valid license found* errors can be presented in such cases. There are three basic elements to consider regarding FARO licenses and their activation: * Each Elios 3 drone needs a FARO connect license to process the data collected from it. Ensure the data being processed is from an Elios 3 associated with the activated license. \ How to check: Open the FARO Connect Licensing Manager app > Click on the active license: The associated serial number/s are listed under Associated serial numbers.
* A FARO license key should only be activated on one computer at a time(unless additional seats have been purchased). The license should be deactivated from one workstation before activating on another. \ \ If the license is activated elsewhere, attempts to process on another computer will cause error until the original instance is deactivated.
* Protected networks can block the software from necessary communication, while triggering licencing, curl, and service errors. FARO connect requires certain ports and domains to be open for its normal operation. Refer to [Required Remote URLs and Domains for FARO Connect](https://knowledge.faro.com/Software/FARO_Connect/Connect/Required_Remote_URLs_and_Domains_for_FARO_Connect) for a list of domains and ports needed to operate the software. * It is also possible to [create a local FARO connect user](/third-party-software/faro-connect/software-general-information/how-to-install-faro-connect.md#create-a-local-user) to work offline. #### **Info to share when contacting support for licensing and activation issues:** * Drone S/N and associated FARO license key. * Screenshot of errors displayed. * Are there instances of the software running on another computer? * If so, and unable to access, contact [support](https://www.flyability.com/support-request). Ensure your drone S/N and FARO license key is included when making this request. * Is there an open internet connection? / Are you working from behind a protected network? ### Processing Failure When a process ends in failure, it can be for many reasons. It can be from basic license mismatch to issues with data collection. #### Basic: * Each drone needs a valid license it is associated to for processing its data, and the license can only be activated on one computer at a time. For more info: [Licencing and Activation](#license-and-activation) * FARO connect requires the computer to have the minimum [System Requirements](/third-party-software/faro-connect/software-general-information/system-requirements.md) * Not having adequate hard drive space for the process can cause the process to end in failure. * Older versions of FARO connect and/or Flyability script can cause processes to fail. Ensure the latest versions are installed: [Current FARO connect version to include the Flyascript](/third-party-software/faro-connect/software-general-information/software-download-current-faro-connect-and-flyability-script-installer.md) * When selecting the processing Workflow ensure Flyability workflows are selected. Others selections will result in failure [Correct processing selections](/third-party-software/faro-connect/how-to-process-a-point-cloud.md): * Flyability Process SLAM * Flyability Advanced Process SLAM * Flyability Reflective Target Georeferencing * No special and/or non-English characters in file names/path. Special characters, accented, and non-English letters in the file path can cause processing failure. * Protected network blocking normal operation. When installing FARO connect behind a protective network, it will require necessary ports and domains for communication to be opened for access. Refer to [Required Remote URLs and Domains for FARO Connect](https://knowledge.faro.com/Software/FARO_Connect/Connect/Required_Remote_URLs_and_Domains_for_FARO_Connect) for a list of domains and ports needed to operate the software. * It is also possible to [create a local FARO connect user](/third-party-software/faro-connect/software-general-information/how-to-install-faro-connect.md#create-a-local-user) to work offline. #### Data collection: When scanning an asset to process the collected data in FARO connect, it is recommended to conduct a flight where mapping is the intention. This means following the best practices for such flights to include the default mapping calibration at takeoff, and take off and landing from the same spot to include orientation. The drone should be in continuous motion, without stopping for extended periods. It is possible to successfully process quick inspection flights in FARO connect, however, when the flight deviates too far from the mapping intention, error and failure can occur. #### **Info to share when contacting support for processing failure:** * Drone S/N and associated FARO license key. * Screenshot/description of errors displayed. (please include the entire screen without cropping) * Description of what you were trying to do, and what was tried to solve the issue. * Error logs from the failed process. * Processing files to include scanner used and asset type for processing. * Cockpit recording from the tablet. [How to retrieve data for support](https://knowledge.flyability.com/how-to-retrieve-data-for-support#Cockpit) ### Processing not to Expectation The process completes, but not to expectation. Most common reports involve symmetrical/reflective/featureless assets. Failure to follow better flight practice for mapping is a common element. When scanning an asset to process the collected data in FARO connect, it is recommended to conduct a flight where mapping is the intention. This means following the best practices for such flights to include the default mapping calibration at takeoff, and take off and landing from the same spot to include orientation. The drone should be in continuous motion, without stopping for extended periods. It is possible to successfully process quick inspection flights in FARO connect, however, when the flight deviates too far from the mapping intention, error and failure can occur. #### **Info to share when contacting support for processing failure:** * Drone S/N and associated FARO license key. * Version of FARO and FlyabilityScript installed. * Screenshot/description of errors displayed. (please include the entire screen without cropping) * Description of what you were trying to do, and what was tried to solve the issue. * Did drone takeoff and land from the same position/orientation? * Did the drone move, or was there lots of movement around the drone during calibration? To include vibration and moving/floating platforms. * Were there changes in geometry of the takeoff/landing area during the flight? * Does the asset contain symmetrical, featureless, and or reflective surfaces? * Error logs from the failed process. * Processing files to include scanner used and asset type for processing. * Cockpit recording from the tablet. [How to retrieve data for support](https://knowledge.flyability.com/how-to-retrieve-data-for-support#Cockpit) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://knowledge.flyability.com/third-party-software/faro-connect/software-general-information/faro-faq-troubleshooting.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.