We are using Leica VIVA series equipment (TS12, TS15, GS14 coupled with CS15 data collectors). Hardware works mostly good; quite typically software is OK. Glitches fair amount, most of the time it is workable, mostly due to the fact that we are using Survey, Stakeout, Stakeout+ and Sets of Angles programs - quite basic things.
Yesterday I was told that maximum amount of points in any given viva job should be no more than 400. I was told that by tech support person at my local Leica dealer. Is that true? I have worked with Leica equipment for last 10 years and with VIVA since it came out but I have never heard of such limitation.
It's just seems a bit ridiculous - what about 1000 pt topo job, you can collect easily within a day. #WTF
Yes, seems ridiculous.
# Why the face?
Update: Just received more info, its for the lite version there is 400 pt limit. Never mind me 🙂
Sounds like a joke.
More importantly to me, whoever heard of a fair amount of glitches being acceptable?
Evgeny,
I have not heard of a limit to the number of points in either the Lite or Full version of Viva SmartWorx. I will add that if your import a file that has 7000 plus stakeout points the system will slow down if you viewing the map screen. There are settings that will limit how many points the map view will try to display to help. I have seen users that have imported a 7000 plus ASCII file on-board the CS15. It make take 5 to 10 minutes to crunch and there are so downs in the map screens. I have dealt with topo jobs that may have 2000 to 3000 points from say a small hydro survey. I cannot remember hearing any complaints about the performance.
The one thing that will slow down the CS15 is when you are storing allot of individual jobs to the internal memory. After a point where allot of jobs have been deleted and there are 200 to 300 jobs stored on the internal memory you will see a slow down overall on the system. The internal memory is say only 60% full but is very fragmented. Same situation as never defragging your PC hard drive. The only way to get the system backup is to format the internal memory and then start storing new jobs. The data base opens and closes very quickly when storing data in order to protect the data and if the memory is fragmented the system slows down when working and trying to maintain the speed at which the database opens and closes. I have seen users that keep every job they have done for a year and a half on the CS15. After awhile the system slows down when trying to find open spaces to store parts of the files involved.
Post some of the glitches you were mentioning. Maybe there is a solution or even a work around.
