Carlson 3.0 - GPS Localization BUG

I wish I had stayed with version 2x. The problems have outweighed the advantages.
The two point offset still doesn't work right after 3 fixes (3.0 to 3.03).
When I installed the version 3 upgrade from 2, it said I couldn't go back, but if something don't change pretty soon, I'm going to see what it would take to go back.
Thanks for the heads up. I use hiper lites, also.
Did you report it to carlson support?

Yes 3 weeks ago and no word , so I though I would put it up hear to light a fire under someone. and to see if its anyone else is seeing this .. We just started with version 3 a couple weeks ago because we bought new Topcon DS the old version would not run it.

Also the Back Sight Prism offset setting will not stick , it keeps setting to 0 offset .09'+/- different .

Found the same bug with Altus APS-3 this week

Found the same bug with the Altus APS-3 this week. Started with an autonomous position on the base, it recorded two positions for it - BP records, one was the exact L1 phase center offset below the other. They are looking into it. I would not have seen it unless I had a static observation between two points that didn't check with the RTK position between base and rover. Always check. Always.

I was able to change the BP record to the correct elevation and process the rw5 file with "Process GPS" (which isn't really processing GPS, but ok). But it only fixed half the error. There was another line, a GPS record that also stored the base in the rw5 file, so I had to change it also, otherwise, since I had "average points with the same name on", it was averaging the bogus elevation and the right elevation together.

Like you said, nasty little bug. One of those that's close enough to right to get overlooked.

Yes,

Our localization bug just changes the points or file at random.
Also, in the RW5 file it lists the localization file, then says no points used in localization file.

Seems to be 3.0 only

Definetley buggy

Found the same bug with Altus APS-3 this week

I had the same type of antenna height issue with a Javad Triumph 1 when using RTCM 3.0 for the RTK message type.

Here is a direct quote from Carlson Tech Support on a fix:

"In SurvCE 3.02 you can go into Equip / GPS Base and GPS Rover and tap the “RTK” tab and change the “Message Type:” to “CMR+” to address the 0.30 ft elevation issue."

I am seeing quite a few bugs with SurvCE in relation to the Javad Triumph 1 system.

Is anyone getting any bad elevations when you enter local coordinates?

Found the same bug with Altus APS-3 this week

Just got the same message regarding switch to CMR+ from RTCM 3.0

If you set up on a known with local coords you will get the error, most likely ..

Found the same bug with Altus APS-3 this week

Dam they new about this and did not send out an emergency fix. I thinking of some words that I can't say..

> This one is nasty and needs to be fixed quick . I been on two jobs chasing my tail trying to figure this out .
> Check and check and check . I already do not trust GPS that much and now this.

I too have had some issues with a localization. (Different, this was applying a localization after the fact and reprocessing the localization...it didn't move any points.) I took the time, made a report, included all the raw data files and emailed it to them. Nothing back.

This is strange for Carlson, I usually have good service from them. (Also using SurvCE3.0)

Found the same bug with Altus APS-3 this week

Idea , They have everyone's email that registers the software , there should be alerts on the software if it's something that's going to be bad .

So if I go enter assumed coordinates like 10000,10000,1000 call it point 1 then in my setup tell it to setup on point 1 that the elevations I am shooting are off my by .3'

Not sure .. Do some checking .. Have not done it that way. If you localize to points already surveyed you will see it .. You might not see it if your doing a one point type localization .

Found the same bug with Altus APS-3 this week

I agree.

My son called me this week to check 0.3 error in gps elevations for him
I use carlson rtk he was using topcon base rover setup.
Maybe its not just a carlson problem

Found the same bug with Altus APS-3 this week

I have told Carlson about the .35 height problem months ago. This hasn't just happened to the Javad Triumph.

I reported this bug to Carlson over a year ago. I think that it was with SurvCE 2.6 if I remember correctly. It seems that it only happens when you are using the RTCM 3 radio protocol. I sent them raw files proving the issue. They contacted me after 3.0 came out and told me that it had been fixed. I just upgraded to 3.03 this week and haven't had a chance to check it. This is a big deal. It caused us to have a 0.70 (Topcon GR-5's) bust in our base point elevations on every job that we worked on. They need to deal with this stat. [msg=197440]Here[/msg] is a previous thread from last March. I spent many hours trying to ascertain what was going on and documenting it for them. Come on Carlson!

I would not want to have this situation happen to anyone. The software developer should have contacted all licensees as soon as they were made aware and found that indeed the bug existed. There should be alert bulletins for those situations.

Can you imagine having to tell the road builder that his blast rock lift (run of quarry rock size 2 ft and up) has to be re-adjusted and re-compacted on his 2 miles stretch by 1 ft? That person would be fuming.

This is a big big bug and it should have exterminated as soon as the notice came in.

Sure re-inforces a very basic rule of surveying: check, check, check.

Found the same bug with Altus APS-3 this week

"I am seeing quite a few bugs with SurvCE in relation to the Javad Triumph 1 system."

Care to share the other Triumph-1 bugs & what release of 3 you are using?

Thanks

Sam