RTC360 Not really that fast
-
- I have made 30-40 posts
- Posts: 36
- Joined: Thu Dec 20, 2018 5:19 pm
- 5
- Full Name: Daniel Jansson
- Company Details: Teodoliten Mätteknik AB
- Company Position Title: Reality Capture Consultant
- Country: Sweden
- Linkedin Profile: Yes
- Has thanked: 7 times
- Been thanked: 6 times
RTC360 Not really that fast
We have a pretty good and stable workflow with our RTC360 so I have been starting to optimize our price estimations for our projects to be more competitive. But when trying to do this my numbers just didn't add up so I started going through my calculations but couldn't find anything particularly wrong with it. So I started timing the scans, and on a low resolution scan I got this:
15 sec starting up
26 sec scanning
10 sec spinning back
5 sec "the last second"
So it is actually roughly 50-60 seconds, quite a big difference from 26 seconds! So it was no wonder my calculations didn't add up since each scan takes twice as long as specified. I haven't done this for images or the other resolutions yet, but the starting up sequence I think is always there, maybe spinning back isn't necessary when taking images or doing double scans but the last second usually is longer than 1 second at least. So I would expect a minimum of 20 seconds extra per scan.
Is this normal behavior for all RTC360s or is this something we should take to service?
If this is how it is supposed to be like, is this normal practice to specify such a lower number than it actually is? I mean it is not a couple of seconds or a 10-20% difference or something. It is sometimes more than twice as long as specified, so it isn't really a rounding error. If the start and stop sequence was 5 minutes would they still really claim each scan takes 26 seconds? If not then why do it at all? If Leica says a scan takes 26 seconds I would expect to when I have pressed play and waited for 26 seconds I would be able to start my new scan directly.
15 sec starting up
26 sec scanning
10 sec spinning back
5 sec "the last second"
So it is actually roughly 50-60 seconds, quite a big difference from 26 seconds! So it was no wonder my calculations didn't add up since each scan takes twice as long as specified. I haven't done this for images or the other resolutions yet, but the starting up sequence I think is always there, maybe spinning back isn't necessary when taking images or doing double scans but the last second usually is longer than 1 second at least. So I would expect a minimum of 20 seconds extra per scan.
Is this normal behavior for all RTC360s or is this something we should take to service?
If this is how it is supposed to be like, is this normal practice to specify such a lower number than it actually is? I mean it is not a couple of seconds or a 10-20% difference or something. It is sometimes more than twice as long as specified, so it isn't really a rounding error. If the start and stop sequence was 5 minutes would they still really claim each scan takes 26 seconds? If not then why do it at all? If Leica says a scan takes 26 seconds I would expect to when I have pressed play and waited for 26 seconds I would be able to start my new scan directly.
- landmeterbeuckx
- V.I.P Member
- Posts: 1615
- Joined: Tue May 01, 2012 5:19 pm
- 11
- Full Name: Lieven Beuckx
- Company Details: Studiebureau Beuckx
- Company Position Title: Owner
- Country: Belgium
- Linkedin Profile: Yes
- Has thanked: 183 times
- Been thanked: 548 times
Re: RTC360 Not really that fast
Don't know about rtc360 but this is with all scanners. The times are scanning times. All upfront and after isn't calculated.
With my tx5 scanning takes like 40 seconds more with each scan. With my Vz400i it's about 5 seconds.
With my tx5 scanning takes like 40 seconds more with each scan. With my Vz400i it's about 5 seconds.
-
- V.I.P Member
- Posts: 916
- Joined: Tue May 11, 2021 5:36 pm
- 2
- Full Name: Adam Berta
- Company Details: InnoScan 3D Hungary Kft
- Company Position Title: unknown
- Country: Hungary
- Linkedin Profile: No
- Has thanked: 51 times
- Been thanked: 297 times
- Contact:
Re: RTC360 Not really that fast
Just don't forget the setup change time, it is way much percentage wise. then a "slower" scanner. It is usually half of the field time is spent just move to another location...daniel.jansson wrote: ↑Thu Oct 21, 2021 8:04 am We have a pretty good and stable workflow with our RTC360 so I have been starting to optimize our price estimations for our projects to be more competitive. But when trying to do this my numbers just didn't add up so I started going through my calculations but couldn't find anything particularly wrong with it. So I started timing the scans, and on a low resolution scan I got this:
15 sec starting up
26 sec scanning
10 sec spinning back
5 sec "the last second"
So it is actually roughly 50-60 seconds, quite a big difference from 26 seconds! So it was no wonder my calculations didn't add up since each scan takes twice as long as specified. I haven't done this for images or the other resolutions yet, but the starting up sequence I think is always there, maybe spinning back isn't necessary when taking images or doing double scans but the last second usually is longer than 1 second at least. So I would expect a minimum of 20 seconds extra per scan.
Is this normal behavior for all RTC360s or is this something we should take to service?
If this is how it is supposed to be like, is this normal practice to specify such a lower number than it actually is? I mean it is not a couple of seconds or a 10-20% difference or something. It is sometimes more than twice as long as specified, so it isn't really a rounding error. If the start and stop sequence was 5 minutes would they still really claim each scan takes 26 seconds? If not then why do it at all? If Leica says a scan takes 26 seconds I would expect to when I have pressed play and waited for 26 seconds I would be able to start my new scan directly.
And don't forget what it takes to import the scans, but these should be done during out of work hours.
-
- I have made 30-40 posts
- Posts: 36
- Joined: Thu Dec 20, 2018 5:19 pm
- 5
- Full Name: Daniel Jansson
- Company Details: Teodoliten Mätteknik AB
- Company Position Title: Reality Capture Consultant
- Country: Sweden
- Linkedin Profile: Yes
- Has thanked: 7 times
- Been thanked: 6 times
Re: RTC360 Not really that fast
I guess it is not only Leica then. But why even put the timer there since it doesn't even tell you anything? Does someone know if in the new firmware this accuracy mode add anything to the timer? Why add this time to the timer and not other start up sequences in that case?landmeterbeuckx wrote: ↑Thu Oct 21, 2021 8:11 am Don't know about rtc360 but this is with all scanners. The times are scanning times. All upfront and after isn't calculated.
With my tx5 scanning takes like 40 seconds more with each scan. With my Vz400i it's about 5 seconds.
Of course there are other stuff in a project that does not involve the scanner scanning that has it's own difficulties estimating. Moving the scanner and importing we have pretty good metrics already on so this isn't really an issue for us at least. This is just one thing that messed up my calculations since I thought I had the metric needed.badam wrote: ↑Thu Oct 21, 2021 8:31 am Just don't forget the setup change time, it is way much percentage wise. then a "slower" scanner. It is usually half of the field time is spent just move to another location...
And don't forget what it takes to import the scans, but these should be done during out of work hours.
But maybe this is just a case of accepting that scanners take longer than specified to do a scan and look up the actual time if that is important. Don't get me wrong it is still fast, but why not just be upfront with how it is? This just adds frustration when you notice it.
-
- V.I.P Member
- Posts: 544
- Joined: Fri Feb 24, 2017 10:47 am
- 7
- Full Name: Martin Graner
- Company Details: PointCab GmbH
- Company Position Title: Research and Development
- Country: Germany
- Linkedin Profile: No
- Has thanked: 160 times
- Been thanked: 175 times
- Contact:
Re: RTC360 Not really that fast
Mh but wouldn't it be great to have the total numbers?daniel.jansson wrote: ↑Thu Oct 21, 2021 10:20 amI guess it is not only Leica then. But why even put the timer there since it doesn't even tell you anything? Does someone know if in the new firmware this accuracy mode add anything to the timer? Why add this time to the timer and not other start up sequences in that case?landmeterbeuckx wrote: ↑Thu Oct 21, 2021 8:11 am Don't know about rtc360 but this is with all scanners. The times are scanning times. All upfront and after isn't calculated.
With my tx5 scanning takes like 40 seconds more with each scan. With my Vz400i it's about 5 seconds.Of course there are other stuff in a project that does not involve the scanner scanning that has it's own difficulties estimating. Moving the scanner and importing we have pretty good metrics already on so this isn't really an issue for us at least. This is just one thing that messed up my calculations since I thought I had the metric needed.badam wrote: ↑Thu Oct 21, 2021 8:31 am Just don't forget the setup change time, it is way much percentage wise. then a "slower" scanner. It is usually half of the field time is spent just move to another location...
And don't forget what it takes to import the scans, but these should be done during out of work hours.
But maybe this is just a case of accepting that scanners take longer than specified to do a scan and look up the actual time if that is important. Don't get me wrong it is still fast, but why not just be upfront with how it is? This just adds frustration when you notice it.
I mean sure the time for capturing points and the time needed from start to finish can be totally different, especially if more things are measured/taken like GPS, Barometer, Inclinometer, Images, Compass, initializing, data saving, ...
But at least there should be numbers for these different steps, or a cumulated sum?
Now I'd love to hear if the different manufacturers are all doing this, only providing the point capturing time, or if there are manufacturers providing the start -> stop time as well. This would relativate a lot of things....
- landmeterbeuckx
- V.I.P Member
- Posts: 1615
- Joined: Tue May 01, 2012 5:19 pm
- 11
- Full Name: Lieven Beuckx
- Company Details: Studiebureau Beuckx
- Company Position Title: Owner
- Country: Belgium
- Linkedin Profile: Yes
- Has thanked: 183 times
- Been thanked: 548 times
Re: RTC360 Not really that fast
I've made a quick video with my vz400i with actual times between pushing the button and finishing for a 20 sec and 30 sec scan.VXGrid wrote: ↑Thu Oct 21, 2021 1:23 pmMh but wouldn't it be great to have the total numbers?daniel.jansson wrote: ↑Thu Oct 21, 2021 10:20 amI guess it is not only Leica then. But why even put the timer there since it doesn't even tell you anything? Does someone know if in the new firmware this accuracy mode add anything to the timer? Why add this time to the timer and not other start up sequences in that case?landmeterbeuckx wrote: ↑Thu Oct 21, 2021 8:11 am Don't know about rtc360 but this is with all scanners. The times are scanning times. All upfront and after isn't calculated.
With my tx5 scanning takes like 40 seconds more with each scan. With my Vz400i it's about 5 seconds.Of course there are other stuff in a project that does not involve the scanner scanning that has it's own difficulties estimating. Moving the scanner and importing we have pretty good metrics already on so this isn't really an issue for us at least. This is just one thing that messed up my calculations since I thought I had the metric needed.badam wrote: ↑Thu Oct 21, 2021 8:31 am Just don't forget the setup change time, it is way much percentage wise. then a "slower" scanner. It is usually half of the field time is spent just move to another location...
And don't forget what it takes to import the scans, but these should be done during out of work hours.
But maybe this is just a case of accepting that scanners take longer than specified to do a scan and look up the actual time if that is important. Don't get me wrong it is still fast, but why not just be upfront with how it is? This just adds frustration when you notice it.
I mean sure the time for capturing points and the time needed from start to finish can be totally different, especially if more things are measured/taken like GPS, Barometer, Inclinometer, Images, Compass, initializing, data saving, ...
But at least there should be numbers for these different steps, or a cumulated sum?
Now I'd love to hear if the different manufacturers are all doing this, only providing the point capturing time, or if there are manufacturers providing the start -> stop time as well. This would relativate a lot of things....
Complete times are 36 sec and 43 sec.
https://youtu.be/Ln83wJRQqqE
So 15 seconds must be added per position. But nothing else like levelling as this is not required for this instrument. Rock and roll baby
Last edited by landmeterbeuckx on Thu Oct 21, 2021 3:07 pm, edited 1 time in total.
-
- V.I.P Member
- Posts: 544
- Joined: Fri Feb 24, 2017 10:47 am
- 7
- Full Name: Martin Graner
- Company Details: PointCab GmbH
- Company Position Title: Research and Development
- Country: Germany
- Linkedin Profile: No
- Has thanked: 160 times
- Been thanked: 175 times
- Contact:
Re: RTC360 Not really that fast
landmeterbeuckx wrote: ↑Thu Oct 21, 2021 3:04 pm I've made a quick video with my vz400i with actual times between pushing the button and finishing for a 20 sec and 30 sec scan.
Complete times are 36 sec and 43 sec.
https://youtu.be/Ln83wJRQqqE
@Lieven, your video is private
- landmeterbeuckx
- V.I.P Member
- Posts: 1615
- Joined: Tue May 01, 2012 5:19 pm
- 11
- Full Name: Lieven Beuckx
- Company Details: Studiebureau Beuckx
- Company Position Title: Owner
- Country: Belgium
- Linkedin Profile: Yes
- Has thanked: 183 times
- Been thanked: 548 times
Re: RTC360 Not really that fast
AjustedVXGrid wrote: ↑Thu Oct 21, 2021 3:05 pmlandmeterbeuckx wrote: ↑Thu Oct 21, 2021 3:04 pm I've made a quick video with my vz400i with actual times between pushing the button and finishing for a 20 sec and 30 sec scan.
Complete times are 36 sec and 43 sec.
https://youtu.be/Ln83wJRQqqE
@Lieven, your video is private
-
- V.I.P Member
- Posts: 1236
- 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: 219 times
- Contact:
Re: RTC360 Not really that fast
I'm pretty sure all Faro scanners take longer than the "spec sheet time" too. Honestly, I haven't paid to much attention though. For these kinds of estimating purposes I've always just bundled together scan time and setup time, i.e. in a particular type of environment how many scans can an experienced operator do in 1 hour. Usually that number comes from experience on previous similar projects rather than trying to estimate it from first principles.
Jed
- 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
Re: RTC360 Not really that fast
Actually faro are about 15sec faster than spec because it takes into account its doing a compass check. It only does a compass check on first scan, all other are 15 sec faster than advertised. But dont get me wrong its still a moderate speed scanner. Just time your scanner right after pressing the button and you will see a 4min10 scan will take about 3min50jedfrechette wrote: ↑Thu Oct 21, 2021 5:00 pm I'm pretty sure all Faro scanners take longer than the "spec sheet time" too. Honestly, I haven't paid to much attention though. For these kinds of estimating purposes I've always just bundled together scan time and setup time, i.e. in a particular type of environment how many scans can an experienced operator do in 1 hour. Usually that number comes from experience on previous similar projects rather than trying to estimate it from first principles.