How about using the new "pop ups" feature for this.....

Darren Clemons

Well-Known Member
With the new release of J Field last week came the "show/hide pop ups" button which, of course, the first one had the magnificent seven surveyors add on there.

This got me thinking of how valuable a tool this could be for all of us LS users. The updates for the LS of course are automatically available via the Internet and we are notified any time there's one available. But with my Triumph 1M and my HPT435BT radio, I never know if/when there may be a firmware update unless I hook up to Netview or Modem VU and I'll basically never do that unless I have an issue. This pop up ability on the LS would be a great way to have notices of firmware updates to those units sent to us as users. Yes, there are different combos we all use like the Triumph 1, Triumph 2, different radios, etc., but how about we use our login information to "subscribe" to which updates we want to be notified about?
Those updates are few and far between and are not nearly as critical as the updates to the LS, but they are needed from time to time and usually we don't figure out they're needed until somethings not working in the field and we've lost a days work.

Another off the wall use would be to use the pop up to send us notifications of high solar flare activity (yes it's rare but it does happen). Ive had three or four days in the last few years where it was just shut er down and go home they were so bad. There are a few websites that let you track solar flare activity but again, usually I'm already in the field and things are going wrong before I think to check. If I'm thinking correctly these happen a couple days before they affect us, so there'd be some time to notify.

There could potentially be numerous things this "notifications" set up on the LS could be used for, those are just a few I've come up with so far.
 

Matt Johnson

Well-Known Member
5PLS
I believe all the popups are compiled into that build of J-Field so new popups couldn't be added after that version of J-Field is built and installed. We do have the Send/Receive Messages that could be used to send out newly created messages. Also GNSS firmware updates are usually published on the RSS feed which you could subscribe to: http://javad.com/jgnss/javad/web/
 

toivo1037

Active Member
My opinion is that firmware updates should be notified via a e-mail message. A simple list-serv should perform that function, just set it up so an owner can log in, and select which equipment that they own. When something is release a short e-mail notification letting us know it is available, and the reason for the update.

I updated my Hiper twice in 15 years. Lets keep Javad on top with both equipment and customer experience.
 

Darren Clemons

Well-Known Member
My opinion is that firmware updates should be notified via a e-mail message. A simple list-serv should perform that function, just set it up so an owner can log in, and select which equipment that they own. When something is release a short e-mail notification letting us know it is available, and the reason for the update.

I updated my Hiper twice in 15 years. Lets keep Javad on top with both equipment and customer experience.
That would work well also. We owned 6/7 hipers over the last several years and those rarely ever had any updates. We started with the original, then 2 or 3 hiper lights (radio in those things wouldn't go anywhere), then to the hiper GA, which until this Javad equipment was the best system we ever owned. The internal radio in that thing would go anywhere. Have gotten shots over 3 miles away with it.
Anyway, I'm going to subscribe to the RSS feed as Matt suggested but with this LS being able to always transmit "live feed" type of information either with a SIM card or wifi in the office it could be put to other uses besides just advertisement.
Maybe not necessarily firmware update notifications but other critical information. For instance we had issues last fall where there was bad data being transmitted via one of the L2C signals causing the LS to struggle mightily acquiring fixes. We ended up having to turn of "track l2c" until it was fixed. Maybe info like that could be sent out to the masses.
 

Kelly Bellis

ME PLS 2099
5PLS
My opinion is that firmware updates should be notified via a e-mail message. A simple list-serv should perform that function, just set it up so an owner can log in, and select which equipment that they own. When something is release a short e-mail notification letting us know it is available, and the reason for the update.
I totally agree; with one addition, that the notice be given at the time when the update is available. This would be in marked contrast with the RSS feed; e.g., the so-called Hybrid RTK debut which appeared on my LS only just yesterday (20160518). It had been advertised since early April and the RSS-fed notice arrived (absent the Gibb Bros.) 20160411. Don't misunderstand, I like the news feed idea, but the way it has been employed isn't always relevant to the moment.
Subscribe to receive the content of this page as RSS feed

EXPLORER-OBJECTS_20160519-04.49.15.png


In partial regards to what precipitated Darren's topic starter in the first place; i.e., the notice to read the article http://javad.com/jgnss/javad/news/pr20160504.html, I'm hoping that Matt Johnson, while sipping his favorite drink, is writing an expanded version which explains exactly WTF is going on with the buckets and why there needs to be 6 choices for one position when, as far as I'm aware of, multiple occupations of the same base still can't be averaged. Where, in that example, is the ellipsoidal height range of 3.4cm DPOS (4.5cm DPOS-OPUS) accounted for in any of those buckets? That would make a great News Feed if/ when he's finished writing it.
 

Matt Johnson

Well-Known Member
5PLS
I'm hoping that Matt Johnson, while sipping his favorite drink, is writing an expanded version which explains exactly WTF is going on with the buckets and why there needs to be 6 choices for one position when, as far as I'm aware of, multiple occupations of the same base still can't be averaged. Where, in that example, is the ellipsoidal height range of 3.4cm DPOS (4.5cm DPOS-OPUS) accounted for in any of those buckets? That would make a great News Feed if/ when he's finished writing it.
Hi Kelly, I really do hope to have the "Quick Start Guide to The Triumph-LS with J-Field 2.0" published to website today with this information. It is in fact possible to average multiple base station occupations with the tools we have now. I'll see if you can figure out with a sneak preview of one of the page from the updated manual:

upload_2016-5-19_7-46-8.png
 

Kelly Bellis

ME PLS 2099
5PLS
Hi Matt,

I love looking for Waldo, and by the way, nice job on this page of the "Quick Start Guide to The Triumph-LS with J-Field 2.0", but Waldo still hasn't been found. I thought, maybe, it might be the number of stations used, but that's probably referring to the CORS that DPOS has decided to use - I still believe that should be optionally determined by the user. Then maybe, perhaps, the Base Rover Statistics button ? I suppose it must be the add M-Local button, which after watching Shawn's video a few times in the middle of the night gave me nightmares as to how folks who don't read the Survey General's Warning (around minute 18), their projects could develop cancer... Once I finish stumbling through my discovery of all that is new and shiny in JField 2, this will be attempted with girded loin.

@Darren - Please forgive me if I've hi-jacked (unintentionally) this thread... here's the new one:
How to Average Multiple Occupations of the Same Base
 

Darren Clemons

Well-Known Member
Hi Matt,

I love looking for Waldo, and by the way, nice job on this page of the "Quick Start Guide to The Triumph-LS with J-Field 2.0", but Waldo still hasn't been found. I thought, maybe, it might be the number of stations used, but that's probably referring to the CORS that DPOS has decided to use - I still believe that should be optionally determined by the user. Then maybe, perhaps, the Base Rover Statistics button ? I suppose it must be the add M-Local button, which after watching Shawn's video a few times in the middle of the night gave me nightmares as to how folks who don't read the Survey General's Warning (around minute 18), their projects could develop cancer... Once I finish stumbling through my discovery of all that is new and shiny in JField 2, this will be attempted with girded loin.

@Darren - Please forgive me if I've hi-jacked (unintentionally) this thread... here's the new one:
How to Average Multiple Occupations of the Same Base
Naw, not a problem Kelly. Wasn't getting much interest anyway.
I agree although the new version has lots of powerful abilities, it can become, quite quickly, a coordinate transformation nightmare.
Do I have a CORS point, do I have a BP processed point, do I have an RTK point - fact of the matter is - if they're all within 0.02' I don't really care which one it "uses" but it's confusing that it can "choose" different solutions (although I understand the reasoning behind why it does).

Regarding Shawn's mention of not using shift and must use localization with 10,000; 10,000 coordinates we actually take old jobs such as this and only use our line work. Usually there's no need for the "old" coordinate file. We attach a georeferenced image in our native state plane coordinate system and move our line work in CAD before we go back to that old job. Then we just calculate approx new points on our corners and then take those points to the field. With the mapping we have today it's remarkable how close we can get, using fence lines, even fence posts, c/l of the road, etc. to "line up" the old drawing to grid. There will be very, very little rotation to the "new" points since it's aligned to grid via the mapping. Once we get the first point, then do a "move" on all the design points and then we go right to the rest around the entire job.
We're going to have new, much more accurate coordinates with today's GPS than most any 1990's rough as hell EDM traverse anyway so these coordinates are just a "guide" to get us to each point.

Of course, there are many instances where you will need all the coordinates of an old job along with their integrity and that is where localization is a must, but if you're just re marking corners or doing an adjoining boundary, this works much, much easier and smoother for us.
 

David M. Simolo

Active Member
I have tried the intuitive approach to localizations and failed previously. I am not sure how this video got by me but I will use this procedure next time.

Will this work equally well with a 5000/5000 coordinate system for the design points? I realize I won't be able to search for them initially using the LS until a localization is performed.

Also, if a 5000/5000 linework only dwg is brought into a page, is there a way to associate it in the LS with SPC?
 

Shawn Billings

Shawn Billings
5PLS
I have tried the intuitive approach to localizations and failed previously. I am not sure how this video got by me but I will use this procedure next time.

Will this work equally well with a 5000/5000 coordinate system for the design points? I realize I won't be able to search for them initially using the LS until a localization is performed.

Also, if a 5000/5000 linework only dwg is brought into a page, is there a way to associate it in the LS with SPC?
You've got it David. It will absolutely work with 5k,5k systems. Also, once the system has been tied to planet Earth using localization, then the coordinates are all related to planet Earth, including the coordinates that construct the linework for a dwg/dxf. At this point, you can change the coordinate system for the page or project or export to SPCS and export the dwg and it will be transformed from 5k,5k to SPC.
 
Top