So we have been having major problems with our Leica Viva Software. Our sales rep/company can't seem to answer anything...and I'm still waiting on Leica. We are using an MS50 with a CS15. We are usually standing right next to the instrument when these issues happen.
Issue 1)
When we try to use points from a control file then write out the data to RW5 file we run into problems. It puts a "?" for the backsight point, then assigns a 0.0000 azimuth to the setup and then takes all of the angles right from that 0.0000 azimuth. Luckily I have my guys take regular check shots so we can catch it and rotate it all in. But this basically means we can't use control files.
Issue 2)
When we try to use the traverse program to run a traverse we have some big issues. What will happen is that we hit OK to start the measurements and it will start to turn the angles. Somewhere (randomly) while turning the angles, the instrument will stop on one of the targets...make the sound like it's taking a measurement and get stuck there. The DC is still responsive but the instrument just sits there trying to take a measurement. We have to back out the traverse program, abandon the setup, and turn the instrument off, re-set up, and then we try again. Sometimes we have to do this 2-3 times before it will complete a set of angles. Sometimes we don't have to turn the instrument off and it will work if we go back into the traverse program but sometimes we have to turn it all off. Other times it turns angles just fine. But I would say we go through this at least once on every traverse we run.
Issue 3)
Sometimes when running traverse we will tell it to take two sets of angles. The instrument will take the backsight then turn the the foresight, take a single shot and then say it is done with the sets. It then asks us if we want to foresight point, move, survey, or done. *it does store this foresight point even though it did not take the angle sets!* We hit foresight point, go into the point list from there, erase the bad point that was supposed to be turned to (but only took a single shot to), then try to foresight the point again. We then get an error saying "Invalid ID". We then back all the way out of the traverse program using the back key and then go back into the traverse and we are able to turn the angle to the point correctly.
Any ideas?
Thanks
Tom
We are all Leica all the time in my shop, with two TS15's. The on-board traverse routines and TPS processing in LGO are just the worst I've seen in my 15 years. I'm not the check-signer here, so my one-word solution has gone unheeded: Carlson.
> So we have been having major problems with our Leica Viva Software. Our sales rep/company can't seem to answer anything...and I'm still waiting on Leica. We are using an MS50 with a CS15. We are usually standing right next to the instrument when these issues happen.
>
> Issue 1)
> When we try to use points from a control file then write out the data to RW5 file we run into problems. It puts a "?" for the backsight point, then assigns a 0.0000 azimuth to the setup and then takes all of the angles right from that 0.0000 azimuth. Luckily I have my guys take regular check shots so we can catch it and rotate it all in. But this basically means we can't use control files.
>
>
> Any ideas?
>
> Thanks
> Tom
I can comment on Issue 1
I have been using a leica ts15i for just under a year now. First day out of the box we decided to go to a job about an hour away... not the best idea but I don't exactly call the shots around here. but anyway what was apparent (not so right away) was by default I guess the software is set up to start your setup with a bs azm and then all turned angles are based on azm. no angle right. So your first setup is bs-ing a user defined azm and all turned angles are azm format. Next setup will be not setting 0 on bs it will want to set a calculated azm and turn azm's not angle right.
Kinda cool but I still prefer setting zero and turning ang. right. You can change that stuff in the setup.
Also as far as control files go I don't mess with them just load all your control pts (I use text file) right into the working job . When im done export as rw5, convert to fbk in cad on cpu and all your loaded control pts are right on top ( if its the first thing you do) in nez format. just window and erase... easy enough
Not sure if that was part of the issue hope this helps and good luck.
> ...so my one-word solution has gone unheeded: Carlson.
LMAO, if you only knew. I'm a big Carlson fan, but let's not encourage a glitchy software being replaced by another software plauged with its own issues.
Shoot me an email with your contact information. I'll get you a solution. No need in waiting on the dealer. You're running a $60k gun, should have been taken care of already.
Fattiretom,
I have been thinking about your issues. I am not sure about issue No 3 but this is what may be the causes….
1. I need to test this with the same setup but it basically sounds like the export of the RW5 does not work when using a control job to extract the traverse control… obviously. You would need to import an ASCII file or hand enter the coordinates for the control points into you working job that is recording all of the data. If you import the points from an ASCII file or hand enter them the system will tag these with the Control class automatically. When you export the RW5 the format will be correct.
2. This should be caused because your have your Coding and Linework setting to utilize a codelist. This would be set in your Working Style that you are running or you can look at the setting from Main Menu -> Work settings.. -> Coding & linework -> if the top box “Use a list box to view codes” is selected the system is set to require a code for the point located. So the instrument is waiting for an input for a code for the point before it continues measurements. If this is not the case and the instrument is simply locking up I have never seen this before and would need to see if I can repeat the issue using the same setting you are using.
3. This may be just the way you are starting your sets versus what angle measurement order you have set in the Traverse application settings. When you first start a Traverse you give the traverse a name and then the next page is the configuration page. The first field is the Measurement sequence. There are 5 different options but I will explain this using the B’F’…F”B” sequence. So this is set to measure Backsight Face 1 -> Foresight Face 1…. Then Foresight Face 2 -> BS Face 2. When you turn set(s) you start with a BS check … so the instrument already has a measurement to the backsight… the next thing you do is to turn to the foresight… you do not leave the instrument pointing at the backsight. You turn to the foresight give the program a Point ID , target height, and then enter how many sets you want to turn. The instrument will then measure the first foresight reading and then begins to trn the sets of angles indicated. It sounds like in your description that you are double measuring to the first backsight.
You also want to choose “When using automatic target aiming, automatically measure the targets” in the configuration menu. For now please do not choose “Allow multiple foresight points” in the configuration menu. This will set up the application just to measure to the traverse points and nothing else. The option works but it would be good to just start the application in its simplest operation mode.
Be sure that you have the proper settings in your TPS settings for Measure Mode and Target so that the system is set up to use the correct prism type and automatic aiming when measuring the backsight and foresight. You can use different prisms and settings for the back sight and foresight targets. Just make sure your settings are correct.
Please let me know if these points solved or did not solve the issues you are having. The Traverse application works very good but there may be some issues with the settings.
Just got a CS15 controller last week. Can you tell me exactly how to change the settings from azi to ang right?
> So we have been having major problems with our Leica Viva Software. Our sales rep/company can't seem to answer anything...and I'm still waiting on Leica. We are using an MS50 with a CS15. We are usually standing right next to the instrument when these issues happen.
>
Hmm...... your sales rep eh.....
