Jedfrechette, can you confirm this issue comes from the original faro files and not the scene software. I know OP said it was the same everywhere but I have still doubts its a Scene software issue. Try importing the original file directly from the sd card into another registration software (cyclone, etc). If the issue is not present in cyclone, can you try different versions of scene. Also think you can you share this original scan file with us? I want to figure a way to avoid this, it has me worried :/
What settings were the scan done? 1/4 3x?
filters?
Strange scan problem
- Leandre Robitaille
- V.I.P Member
- Posts: 542
- Joined: Sat Aug 03, 2019 1:53 am
- 4
- Full Name: Leandre Robitaille
- Company Details: Cima+
- Company Position Title: Civil Technician - Surveyor
- Country: Canada
- Has thanked: 61 times
- Been thanked: 246 times
-
- V.I.P Member
- Posts: 1237
- Joined: Mon Jan 04, 2010 7:51 pm
- 14
- Full Name: Jed Frechette
- Company Details: Lidar Guys
- Company Position Title: CEO and Lidar Supervisor
- Country: USA
- Linkedin Profile: Yes
- Location: Albuquerque, NM
- Has thanked: 62 times
- Been thanked: 220 times
- Contact:
Re: Strange scan problem
The scan was done with the standard "Outdoor >20m" preset. I'm afraid I can't share the data from this project.
I haven't tried loading the raw scans directly in to any other software, but all of those imports are going to rely on Faro's libraries so if the bug exists there I would expect to see the same thing.
I'm curious what specific firmware and software versions the other users who have seen this are using. The S350+ that this scan is from is a new acquisition, and since we generally don't update firmware unless it solves a significant known issue, it is almost certainly running a newer firmware than our other units. I haven't had a chance to confirm this yet though.
Maybe we've just been lucky and never observed this before in tens of thousands of scans, but I am suspicious that it is a new problem. Since the scanner is the only thing that has changed for us recently I'd suspect it's firmware before the well tested versions of Scene and the SDK that we're using
I haven't tried loading the raw scans directly in to any other software, but all of those imports are going to rely on Faro's libraries so if the bug exists there I would expect to see the same thing.
I'm curious what specific firmware and software versions the other users who have seen this are using. The S350+ that this scan is from is a new acquisition, and since we generally don't update firmware unless it solves a significant known issue, it is almost certainly running a newer firmware than our other units. I haven't had a chance to confirm this yet though.
Maybe we've just been lucky and never observed this before in tens of thousands of scans, but I am suspicious that it is a new problem. Since the scanner is the only thing that has changed for us recently I'd suspect it's firmware before the well tested versions of Scene and the SDK that we're using
Jed
-
- I have made 20-30 posts
- Posts: 22
- Joined: Thu Jun 28, 2018 5:39 pm
- 5
- Full Name: Scott Kim
- Company Details: UCC environmental
- Company Position Title: Designer
- Country: United States
- Linkedin Profile: No
- Has thanked: 19 times
- Been thanked: 1 time
Re: Strange scan problem
Thank you for your interest.
As I've said enough before, this isn't an issue with scenes. Same result with Cyclone and Recap. And FARO knows that this is their problem.
This problem seems to occur under special conditions, but it is never easy to recognize and delete or fix all of them.
Some FARO users have already experienced this problem, but I'd like to hear the experiences of other brand users.
Because FARO says this is a common problem for all brands and gives no solution.
And FARO users who found this problem would like to report directly to FARO. That is because they will actively try to solve it.
Thank you.
As I've said enough before, this isn't an issue with scenes. Same result with Cyclone and Recap. And FARO knows that this is their problem.
This problem seems to occur under special conditions, but it is never easy to recognize and delete or fix all of them.
Some FARO users have already experienced this problem, but I'd like to hear the experiences of other brand users.
Because FARO says this is a common problem for all brands and gives no solution.
And FARO users who found this problem would like to report directly to FARO. That is because they will actively try to solve it.
Thank you.
-
- V.I.P Member
- Posts: 1237
- Joined: Mon Jan 04, 2010 7:51 pm
- 14
- Full Name: Jed Frechette
- Company Details: Lidar Guys
- Company Position Title: CEO and Lidar Supervisor
- Country: USA
- Linkedin Profile: Yes
- Location: Albuquerque, NM
- Has thanked: 62 times
- Been thanked: 220 times
- Contact:
Re: Strange scan problem
I don't think it's even common for Faro scanners. Over the last decade, I've probably looked at tens of thousands of scans from dozens of different individual units across almost all of Faro's model lines and until I ran in to it a few days ago I had never seen this before. It's certainly possible we've been missing it all this time, but due to the way we use the data I find that highly unlikely.
Jed
- smacl
- Global Moderator
- Posts: 1409
- Joined: Tue Jan 25, 2011 5:12 pm
- 13
- Full Name: Shane MacLaughlin
- Company Details: Atlas Computers Ltd
- Company Position Title: Managing Director
- Country: Ireland
- Linkedin Profile: Yes
- Location: Ireland
- Has thanked: 627 times
- Been thanked: 657 times
- Contact:
Re: Strange scan problem
Suggests it might be a recently introduced issues. Could be worth comparing firmware versions and software versions that it is happening with.jedfrechette wrote: ↑Sun Jun 06, 2021 10:31 pmI don't think it's even common for Faro scanners. Over the last decade, I've probably looked at tens of thousands of scans from dozens of different individual units across almost all of Faro's model lines and until I ran in to it a few days ago I had never seen this before. It's certainly possible we've been missing it all this time, but due to the way we use the data I find that highly unlikely.
-
- V.I.P Member
- Posts: 1237
- Joined: Mon Jan 04, 2010 7:51 pm
- 14
- Full Name: Jed Frechette
- Company Details: Lidar Guys
- Company Position Title: CEO and Lidar Supervisor
- Country: USA
- Linkedin Profile: Yes
- Location: Albuquerque, NM
- Has thanked: 62 times
- Been thanked: 220 times
- Contact:
Re: Strange scan problem
Agreed, my money is on firmware. I'd love to hear what version others who have observed it are on.
Jed
-
- V.I.P Member
- Posts: 1237
- Joined: Mon Jan 04, 2010 7:51 pm
- 14
- Full Name: Jed Frechette
- Company Details: Lidar Guys
- Company Position Title: CEO and Lidar Supervisor
- Country: USA
- Linkedin Profile: Yes
- Location: Albuquerque, NM
- Has thanked: 62 times
- Been thanked: 220 times
- Contact:
Re: Strange scan problem
A quick update to this issue. We just saw the same artifact in new data from a different S Plus 350. The newest unit to exhibit the problem was also running firmware version 6.7.0.4464. The new affected scan was also captured with the OUTDOOR_FAR preset.
Jed