PreRelease 4.0

John Thompson

Well-Known Member
The issue is which functions rate top-level access. I'm lobbying in favor of leaving Data Exchange as a one-push function due to its frequency of use.
I agree with this reasoning. I was trying to think of which home screen button could be sacrificed to make room for Localization (which is not necessary if it has a hardware button). I never use the Data Exchange button - I always get to it from Files or Points. But Data Exchange is a basic function that merits a spot on the Home screen. I suppose if room needs to be made on the Home Screen (and I'm not sure it does), there are other buttons that could be moved inside the System button or a third Home Screen could be added.
 

nusouthsc

Active Member
I vote for Data Exchange on home screen. We use it every single day. We transfer all data to/from the LS through google drive so Data Exchange is a top tier button.

As a side idea suggestion regarding codes:

What if the traditional grid view was used but the top row of buttons toggled between customizable categories. Essentially like customizable pages of codes.
 

Matt Johnson

Well-Known Member
5PLS
If Localization is available as a hard button I see no need for it on the Home screen. I'm with Jim.

A home screen and hardware button for localization are both dead ends. You can create the localization but not change the page or project coordinate system to that localization after it is created. You can create a localization from the screens where you change the project or page coordinate systems so why not just do it there?
 

avoidthelloyd

Active Member
I vote for Data Exchange on home screen. We use it every single day. We transfer all data to/from the LS through google drive so Data Exchange is a top tier button.

As a side idea suggestion regarding codes:

What if the traditional grid view was used but the top row of buttons toggled between customizable categories. Essentially like customizable pages of codes.
Us too! Daily. Multiple times a day in fact. We use it out in the field on the job multiple times.
 

John Thompson

Well-Known Member
You can create a localization from the screens where you change the project or page coordinate systems so why not just do it there?
I do create the localization there when I'm importing a deed description or prior survey, usually in the form of linework in a dxf file. I'm referring to the need to access the localization multiple times in the field to add each point as it is collected and link it to a corner of the linework on that page.
Like this.
 

John Thompson

Well-Known Member
What if the traditional grid view was used but the top row of buttons toggled between customizable categories. Essentially like customizable pages of codes.
Unless I misunderstand what you are suggesting, that is exactly how I use the Category to show button. My codes are categorized and it's one more click than what you describe, but it works well for me.

The new "list view" for codes shows all of the attributes at a glance which looks to me like it's more useful when initially setting up codes than using them in the field, which got me to thinking... Would it be possible to copy the attributes from one code to another? Or possibly copy a code with all its attributes and rename it? That would help me standardize some of my codes without having to make the same change in multiple places.

Also, the ability to switch between grid view and list view of codes has given me some hope that some of the other lists in J-Field could (maybe optionally) be converted to buttons and thus be more compatible with my fat fingers and old eyes. I'm thinking of lists that are accessed in the field like Antenna Profiles, Action Profiles, and Code Attributes.
 

giulio

Member
I am about 29 km from a station, I get the message "far from stdl" with the previous firmware you had to increase the FROM STDL value to 50 or more, with the latest firmware this option I can no longer find it. Has it been removed or is it still there?
 

Michael Stazhkov

Developer
JAVAD GNSS
I am about 29 km from a station, I get the message "far from stdl" with the previous firmware you had to increase the FROM STDL value to 50 or more, with the latest firmware this option I can no longer find it. Has it been removed or is it still there?
We hide the parameter in the user mode. By default the parameter has "0" value (unlimited distance). It could be that in your profile it has a different value. You can set an engine parameters to the default values by pushing the "To Default" button on the bottom row of the screen.
Screenshot from 2022-04-06 13-21-04.png
 

A.lacey

Member
Is there a way to set the store points in d to d offset to automatically move up to the next point? it did it before the 4.0 update.
 

Andrey Zhiganov

Active Member
JAVAD GNSS
Is there a way to set the store points in d to d offset to automatically move up to the next point? it did it before the 4.0 update.
Could you explain your workflow in more details - collecting points, collecting with offsets, CoGo or something else?
 

Andrey Zhiganov

Active Member
JAVAD GNSS
COGO-TASK-SCREEN-DIRECT_20220407-07.19.18.png


I found a bug: after collecting a point in Offset mode, the name of the resulting point does not increase. Do you mean this case?
 

nusouthsc

Active Member
Can anyone elaborate on the settings for the predefined profiles?

View attachment 12874
Charles,
It is my understanding that the purple profiles are "Stock" profiles. They cannot be "used" or edited, only copied and then used. It seems the idea is that you have a backup in case you change something by accident and want to start over with these. So, I copied both of them and give them our company name NuSouth Canopy, NuSouth Open. Hope this helps.
 
Top