2.1.0.25 (PreRelease)

[Matt Johnson]

The PreRelease version 2.1.0.25 is available for anyone who like to try and test this version. No one has been able to reproduce the failure of the file system that caused J-Field not to boot yet but we hope this version fixes it. We need more users to try this version to confirm this. To install this version change the version branch to PreRelease in the configuration screen of the software update screen. Be sure to create a Full Backup (Files>Full Backup and Restore) before installing this and backup projects frequently (before switching projects or shutting down) until we confirm this is resolved. If a file system crash occurs a factory recovery will be needed and restore points will be lost so Full Backups and project archives are the only way to protect data.

Since 2.1.0.21

This is attempt to avoid boot failure problem after update:
1. switched off "Write-Ahead Log" option in SQLite DB (the same as in 2.0.5.1011)
2. freezing of DPOS activity during project creation

Since 2.0.5.1011
- Greatly improved database performance
- Implemented Firmware and Options Update of remote Base
- Added a new DPOS network CACS (CAN) from Canada
- Added "Sync DPOS Tasks" feature to "Base/Rover" screen
- Added "Create Base & DPOS from File" feature to "Points" screen
- Added "Create Base & DPOS from Proj" feature to "Points" screen
- Improved NMEA output options
- Added "Design Elevation" stake whitebox
- Added "Attach" button when waiting for Accept/Reject
- Added a whitebox to switch azimut/bearing
- Added option to add design coords to survey point at Stake Accept As
- Added raw GNSS file information to point edit screen
- Added project archive reminder for modified projects at application startup
- Added reminder for periodic Full Backup using warning screen/LED
- Modified alignments math so that north/south, east/west and cut/fill whiteboxes work in Stake Here mode along the alignment and beyond its ends
- Implemented copy/cut/paste for multiselection mode in BrowseFilesScreen
- Implemented deleting files in multiselect mode in BrowseFilesScreen
- Implemented adding offset as attributes of surveyed point at Stake / Accept As
- Improved Collect/Stake white box command selection screen
- Many other bug fixes and improvements

 

[Matt Johnson]

This release contains all changes we did since the last major release 2.0.5.653 in December 2016. It includes all changes related to Linux porting, all new features and fixes we did during this year.


"Sync DPOS Tasks" feature to "Base/Rover" screen

This will be useful for customers with a 2nd LS rover. The procedure is to Start the base with first LS and then later Stop the base and download the data with that same LS. Then connect the 2nd rover to the Base through Base/Rover Setup and Sync DPOS task:

The base file is found and downloaded and then the base point and DPOS session are created in the database on the 2nd LS.

 

[Darren Clemons]

This release contains all changes we did since the last major release 2.0.5.653 in December 2016. It includes all changes related to Linux porting, all new features and fixes we did during this year.


"Sync DPOS Tasks" feature to "Base/Rover" screen

This will be useful for customers with a 2nd LS rover. The procedure is to Start the base with first LS and then later Stop the base and download the data with that same LS. Then connect the 2nd rover to the Base through Base/Rover Setup and Sync DPOS task:

View attachment 7034

View attachment 7035


The base file is found and downloaded and then the base point and DPOS session are created in the database on the 2nd LS.

 

[Nate The Surveyor]

It includes all changes related to Linux porting,

Would you mind elaborating on that phrase?

 

[Matt Johnson]

This means that this build of J-Field contains changes that have been made to make it compatible with the Linux OS that will eventually be released.

 

[Jim Frame]

After updating I'm not able to receive corrections from CRTN. It shows that I'm connected to the mountpoint, but no correction data comes across. Any other CRTN users able to check this?

 

[Matt Johnson]

After updating I'm not able to receive corrections from CRTN. It shows that I'm connected to the mountpoint, but no correction data comes across. Any other CRTN users able to check this?

I would suggest trying to restart the connection by cycling it off and then back on from WiFi > RTN.

 

[Jim Frame]

I rebooted, did a couple rounds of RTN off/on and WiFi off/on, and tried both my office WiFi and my phone WiFi. Same result, connected but no corrections.

 

[Shawn Billings]

Maybe check the mount point

 

[Jim Frame]

I tried a couple different mountpoints, one in NorCal and one down south. Same result.

 

[Jim Frame]

Somehow -- and I'm really scratching my head here -- the IP address got changed in my CRTN profile. It's working now, but I'm really mystified as how that happened. Only 1 digit got changed, and I overlooked it when reviewing the address initially.

 

[Michael Glutting]

Hi Jim,

I just tested MILP_RTCM3 via the NorCal server (ip 132.239.1582.175 port 2103) with no problems. However, the UCD1 stream appears to be lacking a necessary RTCM message(s), similar to what we observed years ago. What mount point are you testing? Have you reached out to the CRTN team (Yehuda et al) yet?

 

[Jim Frame]

I did send email to Yehuda, though I hate bothering him with user support matters. I had a misconfiguration on my end (see above) that I'm at a loss to explain, but once I fixed it I began receiving corrections from UCD1. During testing with both my LS and with BNC on my desktop, I ran into some other problems (e.g., unable at times to obtain a mountpoint table), so I'm thinking that CRTN may have been having some hiccups today.

 

[John Thompson]

Yesterday I updated J-Field to 2.1.0.21, and today it wants to go back to 2.0.5.1011?

 

[Matt Johnson]

Yesterday I updated J-Field to 2.1.0.21, and today it wants to go back to 2.0.5.1011?

The release version was rolled back to the previous version because some people were experiencing problems with J-Field not booting at installing the update.

 

[John Thompson]

So should I go back to the previous version? I haven't had problems, but I haven't rebooted, either.

 

[Matt Johnson]

So should I go back to the previous version? I haven't had problems, but I haven't rebooted, either.

You should at least do a full backup before rebooting if you haven't already.

 

[Shawn Billings]

I noticed today that Reset Tracking is now an option for the user buttons.

 

[Matt Johnson]

The PreRelease version 2.1.0.25 is available for anyone who like to try and test this version. No one has been able to reproduce the failure of the file system that caused J-Field not to boot yet but we hope this version fixes it. We need more users to try this version to confirm this. To install this version change the version branch to PreRelease in the configuration screen of the software update screen. Be sure to create a Full Backup (Files>Full Backup and Restore) before installing this and backup projects frequently (before switching projects or shutting down) until we confirm this is resolved. If a file system crash occurs a factory recovery will be needed and restore points will be lost so Full Backups and project archives are the only way to protect data.

So should I go back to the previous version? I haven't had problems, but I haven't rebooted, either.

You should go to the PreRelease version.

 

[Darren Clemons]

The PreRelease version 2.1.0.25 is available for anyone who like to try and test this version. No one has been able to reproduce the failure of the file system that caused J-Field not to boot yet but we hope this version fixes it. We need more users to try this version to confirm this. To install this version change the version branch to PreRelease in the configuration screen of the software update screen. Be sure to create a Full Backup (Files>Full Backup and Restore) before installing this and backup projects frequently (before switching projects or shutting down) until we confirm this is resolved. If a file system crash occurs a factory recovery will be needed and restore points will be lost so Full Backups and project archives are the only way to protect data.



You should go to the PreRelease version.

I will try it out Monday. I guess it was somehow isolated to certain units, just don’t see how.
I have stayed on 2.0.1.21 all week (after factory reset and re installing backup) and have had no other problems. I know there was discussion of “not waiting long enough” but I didn’t interrupt or stop the initial install at any time.