Known limitations

Current known limitations and common issues encountered when processing Elios 3 data with FARO connect.

The FARO Connect and Flyability script is always under development and improvements. While the latest issues are being fixed, please be aware of the known limitations below, and don't hesitate to contact Flyability's support if you need any assistance.

• Unable to open a project’s processed data from Connect The project folder can only be accessed from the LidarOS folder (C:\ProgramData\LidarOs\projects).

• Issue with rotation of point clouds when manually aligning Currently, it is not possible to rotate a point cloud in the Side View. Only rotations in the Top View work.

• DISCONNECTED: The socket has encountered an unhandled error on execution thread (stopped with exit code 1). Any further processing of commands on this client is not permitted. When encountering this error message, to solve the issue you will need to stop the processing and restart your computer.

• "OusterLidarFeature" error: When encountering this error message, to solve the issue you will need to stop the processing and restart your computer.

• Connect 3D viewer running out of memory: A warning message may appear or the screen will go white if there are too many point clouds open on the viewer at once. Avoid opening more than 3-4 point clouds at a time to avoid the 3D viewer running out of memory.

• Admin request at installation: An admin authorization pop-up may appear 2-3 times when installing the latest version of Faro Connect, however, the Administrator permission is not required and Faro Connect will install correctly in the background.

• Processing speed when PC is idle: The overall processing speed may be slower when the computer is left idle or in speed mode. To avoid slower processing speed, make sure that the processing PC does not enter a low-power standby mode.

• You may be unable to remove/delete tasks from the processing queue.

• Processing is paused when the screen is locked: it seems it is not the backend processing that is paused but instead, items in the queue are not sent to the backend to begin processing.

• Naming a project with a space as the last character makes several workflows fail.

• When running the “Reflective Target Georeferencing (Cloud)” workflow with a control point file that contains a new line with only spaces, it fails with an unclear error message.