Quick Start Guide to the TRIUMPH-LS With J-Field 2.0

Darren Clemons

Well-Known Member
I did a test job yesterday collecting many different types of our "usual" points. Some just standard RTK, some with 15 minutes Dpos attached and I did 3 offsets with using the camera (storing both the shot where I was at + the offset shot as Robert suggested) to try shifting design points again.
What I saw this morning when I processed was all the created points off my offset shot were put in "survey" points this time and were processed seamlessly along with the regular "Base processing + Base Shift".
I didn't have to re-select them and go into move and use the Dpos shift anymore! I'm guessing that has just been changed in one of the latest updates (I'm using recommended release 2.0.0.310).
I didn't try any other cogo type points - such as creating a resection - has that been changed as well?
 

Matt Johnson

Well-Known Member
5PLS
I did a test job yesterday collecting many different types of our "usual" points. Some just standard RTK, some with 15 minutes Dpos attached and I did 3 offsets with using the camera (storing both the shot where I was at + the offset shot as Robert suggested) to try shifting design points again.
What I saw this morning when I processed was all the created points off my offset shot were put in "survey" points this time and were processed seamlessly along with the regular "Base processing + Base Shift".
I didn't have to re-select them and go into move and use the Dpos shift anymore! I'm guessing that has just been changed in one of the latest updates (I'm using recommended release 2.0.0.310).
I didn't try any other cogo type points - such as creating a resection - has that been changed as well?

I see that using the white box option is creating offset points as survey points. This is a bug I believe. The plan is still to be able to shift design points in the future with DPOS.
 

Matt Johnson

Well-Known Member
5PLS
Offset points aren't really design points. I don't think this is a bug. It's a feature.

I would argue that they aren't survey points either as we typically define survey points to be directly measured by the receiver. The biggest is that we aren't creating the CoGo resultant points consistently. With the white box option it creates survey points but if we call the CoGo functions directly it always creates design points.
 

Darren Clemons

Well-Known Member
I would argue that they aren't survey points either as we typically define survey points to be directly measured by the receiver. The biggest is that we aren't creating the CoGo resultant points consistently. With the white box option it creates survey points but if we call the CoGo functions directly it always creates design points.
Yes, that's it exactly. It's getting very confusing as to where each type of non surveyed point goes.
That being said, I love the way it did my offset "survey" shots to the building - moved em all when the Dpos shift occurred. I didn't have to go back and do anything.
 

Robert P Stenerson

Active Member
Offset points aren't really design points. I don't think this is a bug. It's a feature.
I agree whole heartedly, and I like how it is now, users using the white button procedure if they want to create offset points as survey points (full credit due to Matthew Sibole for turning me on to it), but users can also go into the Cogo Screen to create design points if they wish.

It would be nice if I could do a three point resection survey point through a white box offset like we have now with Direct.

Just a suggestion, with new Cogo possibilities maybe we should call "Design" points "static points" meaning we don't expect them to move with base processing adjustments, and "surveyed" points "dynamic points" meaning that we want them to move along with the rest of the surveyed points. ???
 
Last edited:

Joe Paulin

Well-Known Member
"Static points" labeling is sure to get confused with points with GNSS static sessions...maybe another term? I do agree we need certain "calculated" points to be treated as "survey points" as you have mentioned above.
 

Robert P Stenerson

Active Member
"Static points" labeling is sure to get confused with points with GNSS static sessions...maybe another term? I do agree we need certain "calculated" points to be treated as "survey points" as you have mentioned above.

Are surveyors still doing "static" GPS surveys with this equipment anymore??? ;) I guess I have gotten used to the JAVAD speak, such as "Stand Alone" for static, but it's been a long while I've since played hop scotch with the old Trimble 4600-s, etc., so that's my bad. I'm an RTK junkie.

Maybe, "Base-Adjusting" and "Non-Base Adjusting' ???
 

Darren Clemons

Well-Known Member
If you find some specific sequence of events or situations (like a project with many points) that always causes it to crash, this might be useful information. There are already internal processes that log some information related to crashes.
Was on a site today and used the offset and set bearing with camera several times and it crashed twice. Probably about 5 or 6 shots worked then - black screen. Re booted immediately the first time and the second time I did try several unsuccessful things to try and get it back on. There's a "reset camera" that I hoped would work but didn't. When I got back to the office I did get the "crash dump sent to developers" message.
Only had about 120 points in the job and nothing else really stood out as to what/why/when it did it.
 

Bruce Dawson

Active Member
Looking through this thread this morning because I also had the black compass screen yesterday. I have been staking to a line, setting fence posts on a USFS boundary. In pretty deep coniferous forest with occasional openings where I can get a decent fix. I had been using offset with the compass view to set my posts and things were going fine then bam! Black screen.

Bruce
 

Bruce Dawson

Active Member
Hope so too. I use the offset feature quite a bit, but not like I did on this job. Probably got half a dozen posts set prior to the issue.
 
Thanks Robert! That was one that I struggled with. Just took it out to my testing grounds at the house and hit a conventional building corner at about 0.05'.

Quick question, does anyone know how to get a quick report on DPOS that just shows ppk/rtk comparisons between the points? In other words just an rtk/ppk comparison record. Thanks in advance.
 

Matt Johnson

Well-Known Member
5PLS
Quick question, does anyone know how to get a quick report on DPOS that just shows ppk/rtk comparisons between the points?

You can export a HTML report that shows this. In the "Point Text" option found when exporting an HTML report, choose the "Hybrid RTK Report" format.

EXPORT-HTML_20180610-13.06.45.png


You can also create screenshots of the Processed Point Info screen for every point using the "Report Screenshots" option found in the menu of the Points screen. Then when you export a pdf report with screenshots, these will be included.

EXPLORER-OBJECTS_20180610-13.14.46.png
 

Darren Clemons

Well-Known Member
You can export a HTML report that shows this. In the "Point Text" option found when exporting an HTML report, choose the "Hybrid RTK Report" format.

View attachment 7557

You can also create screenshots of the Processed Point Info screen for every point using the "Report Screenshots" option found in the menu of the Points screen. Then when you export a pdf report with screenshots, these will be included.

View attachment 7558
Sometimes I wonder if Matt doesn’t have to use earplugs so all the info he stores about the LS doesn’t leak out!! It’s simply amazing how much this machine does, and speaking at least for myself, most of us don’t know half of it!!! We’d sure be in a pickle without your constant help Mr. Johnson.
EC00329F-C744-4AF1-B9F0-B7098B7355C4.jpeg
 

Adam

Well-Known Member
5PLS
Sometimes I wonder if Matt doesn’t have to use earplugs so all the info he stores about the LS doesn’t leak out!! It’s simply amazing how much this machine does, and speaking at least for myself, most of us don’t know half of it!!! We’d sure be in a pickle without your constant help Mr. Johnson.
View attachment 7559
So true! How does he do it?
 
It's like magic :D - I love my LS and T1M combo! These units have performed amazingly for me as a TCP base/rover pair - as I have learned how to use them correctly. The LS has done some really amazing solo work on the network as well.

Here is an issue that I am reminded of when I attempted to export this html file to my thumb drive. Kind of an annoying issue with these html files and my workaround is to send to my google drive but that is slow and costs me data usage. This issue can also happen when I attempt to export a relative accuracy or scale factor report to a thumb drive and sometimes my google drive. I often have to remove an underscore from the end of the file and then it works. Or I get a ghost file that has size, but isn't usable or removable or editable. In this case, the html file of the hybrid rtk report(thumb drive), has 394 kilobytes, attached is a clip for a visual. I normally open the html with ie and you can see this app is not recognized. When I send the same file to my google drive it works fine, upon download. I cannot send the file as I am not able to copy or cut, maybe a known issue? I am currently using mini gorilla drives and these types of things have happened with some several thumb drive types.

Thanks for the assistance.
 

Attachments

  • Ghost File.PNG
    Ghost File.PNG
    26.2 KB · Views: 316
Top