Processing on the computer takes 17min? Since the profit in the field is destroyed immediately. I think the data is already registered in the field? With the project a deviation of 0.012ft is not exactly impressive either. There are better systems on the market.
Langemapp Thank you for your question. We would like to clarify a few points. The timer shows that the entire time on the project side to collect the data was less than 17 minutes. The data was fully registered at that point. In the office we just had to import the data, strengthen the registration and export. The worst global registration residual value was .003’ (3 One thousands of a foot or 1/32 inch), where as the .012 ft that you reference is unadjusted raw cloud to cloud error. The global least squares registration result is the appropriate value to reference as being the error that the project is not more than .003 ft. There are many different types of scanners on the market and some people need higher accuracy, such as small scale metrology scanners for reverse engineering or longer range scanning for open pit mining, in our opinion, the RTC360 provides great value at its price point. We have had many clients do side by side comparisons to other solutions on the market when done head to head, the RTC360 has done exceptionally well. Feel free to give us a call if you have further questions, we are happy to help!
@@USCADBuilding In the phase where you have activated the time lapse, your system clock is expanded by 17 minutes at the bottom right. I find that a bit much, but it has to do with the extremely high data generation. Other systems manage with far less volume and are therefore faster overall.
@@Langemapp Curious, what are your avg capture times per setup? And at what error? Under 3 min per setup seems fast to me with data and photo capture. It sounds like he could knock a minute off that with a single scan in environments without a lot of motion/noise to be removed. Over 6 setups, now he's down to 11 minutes? Man, I can kill 10 minutes on a job site talking to the super while this is going on and hand them a 3D scene at the end. Now delivering the noah's ark sized data, that's another thing... :)
Great video! Very informative!
Can you provide a link to the modeling? As mentioned at the 20:00 mark...
What is the cost of this software?
I see the scanner does not need levelling?
Yes I will like to why.
Processing on the computer takes 17min? Since the profit in the field is destroyed immediately. I think the data is already registered in the field? With the project a deviation of 0.012ft is not exactly impressive either. There are better systems on the market.
Langemapp Thank you for your question. We would like to clarify a few points. The timer shows that the entire time on the project side to collect the data was less than 17 minutes. The data was fully registered at that point. In the office we just had to import the data, strengthen the registration and export. The worst global registration residual value was .003’ (3 One thousands of a foot or 1/32 inch), where as the .012 ft that you reference is unadjusted raw cloud to cloud error. The global least squares registration result is the appropriate value to reference as being the error that the project is not more than .003 ft.
There are many different types of scanners on the market and some people need higher accuracy, such as small scale metrology scanners for reverse engineering or longer range scanning for open pit mining, in our opinion, the RTC360 provides great value at its price point. We have had many clients do side by side comparisons to other solutions on the market when done head to head, the RTC360 has done exceptionally well.
Feel free to give us a call if you have further questions, we are happy to help!
@@USCADBuilding In the phase where you have activated the time lapse, your system clock is expanded by 17 minutes at the bottom right. I find that a bit much, but it has to do with the extremely high data generation. Other systems manage with far less volume and are therefore faster overall.
@@Langemapp Curious, what are your avg capture times per setup? And at what error? Under 3 min per setup seems fast to me with data and photo capture. It sounds like he could knock a minute off that with a single scan in environments without a lot of motion/noise to be removed. Over 6 setups, now he's down to 11 minutes? Man, I can kill 10 minutes on a job site talking to the super while this is going on and hand them a 3D scene at the end. Now delivering the noah's ark sized data, that's another thing... :)