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

Matt Johnson

Well-Known Member
5PLS
Here is the latest revision of the Quick Start Guide to the TRIUMPH-LS With J-Field 2.0

Feel free to comment about anything you do not understand or mistakes you find.

Update Version 20160523 Attached to This Post

Changes include:
  • Updated the Browse Files screenshots to reflect changes with the open button
  • Base/Rover Setup - File Management
  • Adding Capture Bearing by Compass to CoGo Direct
  • Added CoGo Resection
 

Attachments

  • Quick Start Guide to the Triumph LS - 20160523 Pages.pdf
    8.5 MB · Views: 973
  • Quick Start Guide to the Triumph LS - 20160523 Spreads.pdf
    8.4 MB · Views: 758
Last edited:

Jim Frame

Well-Known Member
The form factor chosen for the manual is very unfortunate. The convenience of having the manual fit in the box is dwarfed by the difficulty imposed on end users who want (or need!) to print a copy of the latest revision in order to keep up with the changes. The page layout -- two manual pages on each PDF page -- makes it hard to produce a legible and user-friendly printed version. Letter-size paper makes the text too small; legal-size paper is too floppy to be practical in the field, and doesn't fit in a standard binder. And binding or punching on the top side makes every other page upside down when the manual is open.

There's got to be a better way.
 

Kelly Bellis

ME PLS 2099
5PLS
Actually, Matt could do another export of pages instead of spreads intended for print (300 dpi) and then each page could be printed to fit a letter-sized piece of paper.
 

Matt Johnson

Well-Known Member
5PLS
On page 12, is that the new or old points screen? I guess that's for Design points on page 12?

See the highlighted note:

upload_2016-5-21_16-9-54.png
 

Matt Johnson

Well-Known Member
5PLS
The form factor chosen for the manual is very unfortunate. The convenience of having the manual fit in the box is dwarfed by the difficulty imposed on end users who want (or need!) to print a copy of the latest revision in order to keep up with the changes. The page layout -- two manual pages on each PDF page -- makes it hard to produce a legible and user-friendly printed version. Letter-size paper makes the text too small; legal-size paper is too floppy to be practical in the field, and doesn't fit in a standard binder. And binding or punching on the top side makes every other page upside down when the manual is open.

There's got to be a better way.

New manuals are available for purchase on the website: http://javad.com/dynamic/Shop/Product/4580
Don't order that one yet as it is still the older version.

I have attached a version exported as individual pages instead of spreads. I like the spread version for viewing on computer monitors.
 

Attachments

  • Quick Start Guide to the Triumph LS - 20160520 Single Pages.pdf
    8.1 MB · Views: 1,781

Robert P Stenerson

Active Member
Hi Matt

It looks great on my Kindle Fire HDX.

Couple items I would have also included, or maybe I missed on this pass:

1. Taking an offset shot using the white box offset button, COGO Direct, use compass to set bearing, etc procedure. This is an important procedure, and GNSS surveyors will want to know how to do this right from the get go. (Hence in the quick guide.)

2. Now that we're using 1sec recording rates with Hybrid RTK , our base GNSS files are now 30x bigger; Shawn mentioned there's a new way to manage the file storage on our base receivers in the Base/Rover screen. I didn't see anything about it here.

All the best, and thanks for the outstanding support from JAVAD GNSS and the Mag 7 team.
Rory
 

Darren Clemons

Well-Known Member
Hi Matt

It looks great on my Kindle Fire HDX.

Couple items I would have also included, or maybe I missed on this pass:

1. Taking an offset shot using the white box offset button, COGO Direct, use compass to set bearing, etc procedure. This is an important procedure, and GNSS surveyors will want to know how to do this right from the get go. (Hence in the quick guide.)

2. Now that we're using 1sec recording rates with Hybrid RTK , our base GNSS files are now 30x bigger; Shawn mentioned there's a new way to manage the file storage on our base receivers in the Base/Rover screen. I didn't see anything about it here.

All the best, and thanks for the outstanding support from JAVAD GNSS and the Mag 7 team.
Rory
You're right Robert, the offset shot - use compass to set bearing is a great feature and we use it quite a lot, but we found a few very important things associated with it for those that haven't used it much.

Matt please correct me if I'm mistaken on any of this.....

1st - The camera issue (which is supposedly being worked on for quite some time now). Usually, in our machine, after about 5 or 6 shots setting compass by bearing the camera will black out and can only be reset with a hard boot of the LS.
2nd - As Matt talks about in red in compass calibration, the compass must be calibrated (sometimes on every job) to get an accurate offset shot. We've tested this quite a bit and found quite a difference from site/site. If you're 5' from a 42" large tree it, of course, wouldn't make much difference, but in other instances it can.
3rd - The "offset" shot is stored as a design point and will NOT be moved during the Dpos adjustment. When doing that process you are asked if you want to "store a new point" at your shot location. If you do store that point it WILL be moved during Dpos, but the offset shot stored from it will not. Up until this latest version there was actually no way to move that point easily in the LS, we were just doing it manually in Autocad. Now those design points can be moved using "shift" or "move" and selecting the Dpos button. It will use the shift bearing/distance and move the selected design points in relation to the rest of the job.

Matt has also talked about, in the quick start guide, how moving design points in relation to the Dpos shift is in the works for a future update (pages 58-59).
 

Matt Johnson

Well-Known Member
5PLS
Hi Matt

It looks great on my Kindle Fire HDX.

Couple items I would have also included, or maybe I missed on this pass:

1. Taking an offset shot using the white box offset button, COGO Direct, use compass to set bearing, etc procedure. This is an important procedure, and GNSS surveyors will want to know how to do this right from the get go. (Hence in the quick guide.)

2. Now that we're using 1sec recording rates with Hybrid RTK , our base GNSS files are now 30x bigger; Shawn mentioned there's a new way to manage the file storage on our base receivers in the Base/Rover screen. I didn't see anything about it here.

All the best, and thanks for the outstanding support from JAVAD GNSS and the Mag 7 team.
Rory

I can add these things.

You're right Robert, the offset shot - use compass to set bearing is a great feature and we use it quite a lot, but we found a few very important things associated with it for those that haven't used it much.

Matt please correct me if I'm mistaken on any of this.....

1st - The camera issue (which is supposedly being worked on for quite some time now). Usually, in our machine, after about 5 or 6 shots setting compass by bearing the camera will black out and can only be reset with a hard boot of the LS.
2nd - As Matt talks about in red in compass calibration, the compass must be calibrated (sometimes on every job) to get an accurate offset shot. We've tested this quite a bit and found quite a difference from site/site. If you're 5' from a 42" large tree it, of course, wouldn't make much difference, but in other instances it can.
3rd - The "offset" shot is stored as a design point and will NOT be moved during the Dpos adjustment. When doing that process you are asked if you want to "store a new point" at your shot location. If you do store that point it WILL be moved during Dpos, but the offset shot stored from it will not. Up until this latest version there was actually no way to move that point easily in the LS, we were just doing it manually in Autocad. Now those design points can be moved using "shift" or "move" and selecting the Dpos button. It will use the shift bearing/distance and move the selected design points in relation to the rest of the job.

Matt has also talked about, in the quick start guide, how moving design points in relation to the Dpos shift is in the works for a future update (pages 58-59).

The camera crash issue is known about and is a problem with the driver in the operation system. Unless someone is able to produce some specific sequence of events to reproduce camera crashes consistently, then these crashes cannot easily be fixed. My understanding is that a rewrite of the camera driver (not easy and time consuming) or upgrading the current Windows Embedded Compact 7 operating system to a better OS (this is not easy either) would be needed. Currently there are highly priority task so resources are not being devoted to this yet. When I just tried setting the bearing by the compass I was able to use it many times without any crashes. Do you really see this problem consistently after only 5 or 6 times of using it?

I have found in the past that the compass need recalibrated frequently. I would always recommend checking the calibration before using features that rely on the compass values.
 

Darren Clemons

Well-Known Member
I can add these things.



The camera crash issue is known about and is a problem with the driver in the operation system. Unless someone is able to produce some specific sequence of events to reproduce camera crashes consistently, then these crashes cannot easily be fixed. My understanding is that a rewrite of the camera driver (not easy and time consuming) or upgrading the current Windows Embedded Compact 7 operating system to a better OS (this is not easy either) would be needed. Currently there are highly priority task so resources are not being devoted to this yet. When I just tried setting the bearing by the compass I was able to use it many times without any crashes. Do you really see this problem consistently after only 5 or 6 times of using it?

I have found in the past that the compass need recalibrated frequently. I would always recommend checking the calibration before using features that rely on the compass values.
Matt, we did have it happen consistently after only 5 or 6 shots back a few months ago. I haven't tried it in a while to be honest as I was aware the camera problem was being fixed, but hadn't so I assumed nothing was different.
I will try it again the next time I get the opportunity and take multiple offset shots using the camera to "set by compass" and see if it's still repeating it's previous patterns....maybe it's something individual to my LS?
Are there any particular things I could set/do to record any of this data except, of course, writing down my sequence of events manually?
 

Nate The Surveyor

Well-Known Member
All this talk about the compass....
Often, I get witness trees. And, while entering the point description, I'd like it if the compass was visable, while entering the point description.
As it is, I have to get out of the mode to type in the desc to get to the compass, to read the bearing, or azimuth, memorize it, and go back to desc. And type it.
If it had a viewable button, in desc. Showing the compass, I'd use it.
N
 

Nate The Surveyor

Well-Known Member
Or...even better, if it had the compass, viewable in point description and a button, that put the curent bearing, into the note... Wow! Thatd be even better!
 

Matt Johnson

Well-Known Member
5PLS
Or...even better, if it had the compass, viewable in point description and a button, that put the curent bearing, into the note... Wow! Thatd be even better!

I can see if Aleksey can add a Compass button to keyboard. Tapping it would open the "Set Angle By Compass" screen and insert the bearing or azimuth (depending upon the user's set units) formatted like "Bearing: N30ºE" or "Azimuth: 30º":

KEYBOARD_Proposed.png
 

Nate The Surveyor

Well-Known Member
Absolutely! And, since it's a note, for Azimuth, Just use Az. (I'm still thinking about the laser pointer on the front. Maybe in a few years, with the Gen2 LS!) I have tried to rig one up, on the face of the LS, cobbled from other parts. This would then serve to point at the tree, aiming the LS effectively, and quickly.

Here is an example, taken from "SalemAR"

set gutter spk in fd rk pl under pine knot s1/4 18 W/T 351° 12.75' 11" Banded wo 98° 13.78 5" Sg Y blz

Set Gutter Spike, in Found Rock Pile, under Pine Knot, South one-forth corner, of Section 18. Witness Trees: 351°Az 12.75' 11" Banded White Oak 98° Az. 13.78' 5" Sweet Gum, with Y blaze.

This is actually the SAME point that shows in the RAIN PIC, posted elsewhere!


Abbreviations are used alot, because of habit, due to other data collectors run out of space fast. And, that continues, because Carlson only supports 20 characters.

Thanks Matt. That's the idea!!
 

Matt Johnson

Well-Known Member
5PLS
Are there any particular things I could set/do to record any of this data except, of course, writing down my sequence of events manually?

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.
 

Darren Clemons

Well-Known Member
Matt, we did have it happen consistently after only 5 or 6 shots back a few months ago. I haven't tried it in a while to be honest as I was aware the camera problem was being fixed, but hadn't so I assumed nothing was different.
I will try it again the next time I get the opportunity and take multiple offset shots using the camera to "set by compass" and see if it's still repeating it's previous patterns....maybe it's something individual to my LS?
Are there any particular things I could set/do to record any of this data except, of course, writing down my sequence of events manually?
My apologies on noting the frequency of the camera "blacking out". I just returned from a site where I started using "set by compass" at least 12-15 times in a row with no problems.
Like I'd said, I hadn't used it in quite some time thinking it would still lock up every 5 or 6 shots......seemed all good today!
Will let you know if/when it happens again.
 

Matt Johnson

Well-Known Member
5PLS
Hi Matt

It looks great on my Kindle Fire HDX.

Couple items I would have also included, or maybe I missed on this pass:

1. Taking an offset shot using the white box offset button, COGO Direct, use compass to set bearing, etc procedure. This is an important procedure, and GNSS surveyors will want to know how to do this right from the get go. (Hence in the quick guide.)

2. Now that we're using 1sec recording rates with Hybrid RTK , our base GNSS files are now 30x bigger; Shawn mentioned there's a new way to manage the file storage on our base receivers in the Base/Rover screen. I didn't see anything about it here.

All the best, and thanks for the outstanding support from JAVAD GNSS and the Mag 7 team.
Rory

The updated versions are attached to the opening post.
 

Robert P Stenerson

Active Member
Hi Matt, good first edit, I'd circle back and clean up the typos. Also, I think you should step by step the offset on the fly procedure since there is a very specific way to do this, and it's not by going through the Cogo Screen. Nate if you're reading this you're going to like it.

Step one, put a Offsets white button on your Collect Action screens in all your Action group Setups.

*Step two, when you're about shoot that witness big cypress tree, press the white button for offsets, which takes you to the Cogo Screen
(don't go there directly from the Home Screen or a U button you gotta use the white box in the collect action screen.)

Step three, Select Direct (the only usable option.) Tap the P field in the upper right that has coordinates in it, and this should return you to the collect action screen, survey where you are standing, and when you accept it, it will ask you if you want to create a new point, CLICK YES, I'll repeat that, Click YES. *Before I take step two I usually change the point name with a high point name for filtering later on, but it's important to create this surveyed point because J-Field seems to use it as a quasi base point for the offset point you're creating, thus it can get adjusted along with it. That's just my theory, and I could be very wrong, but I had problems when I chose No.

Step four, tap the bearing/azimuth field, then tap set by compass, and voila! Your front camera comes up with a target crosshair which you point at your tree, then press the big green check button to lock it in, tap apply at the bottom of the screen.

Step five pull out your disto, hand tape, or whatever and enter your offset distance in the next field below.

Step six the bottom P field will allow you to edit the point name, description, for the tree, or whatever that want in the right place of your drawing.

When all's good tap create, and it will come back with a success message.
 
Last edited:
Top