Release 4.0

Eugene Aksyonov

Well-Known Member
This is a major release that mostly related to User Interface and User eXperience. We do consider it as a step to simplify surveyor work. Also there are lot of new features and bug fixes were done. Please comment your experience in this thread to help us make the software better.
To make migration experience more smooth and easy we have prepared the guidance (https://docs.javad.com/en/Manuals/Receivers/Triumph-LS/J-Field_v4_Migration) where you can find the key points that differ version 4.0.

J-Field 4.0.0.1216
Since 3.0.11.835:
New Features
  • JCORS support
  • Custom WMTS background map support
  • OpenStreetMap background map support
  • UI profiles

Updated Features
  • User Interface. Added Map, Collect & Stake buttons to the front screen for quick access. Removed Prepare Screen. Updated button Icons on the home screens. Added a direct Corrections setup button to status bar for protocol type and a Unit working mode (Stand-Alone, Base, Rover). Removed Corrections Setup Wizard. Added project name to the bottom status bar. Added electronic bubble and Tilt Compensation mode indicator to the compass control on the Action screen.
  • External Base Setup. Renamed a button title “Base/Setup” to “Remote Base”. Completely rewritten UI. Now the Base can be configured for broadcast corrections simultaneously over the UHF, TCP Output server and JCORS NTRIP service. Added Pairing and Unpairing Modems over Bluetooth. Added option to manage Base systems and signals. Added indicator of satellite systems that Base broadcasts. Added 2, 2.5 and 3 seconds options to base broadcast corrections.
  • NTRIP / TCP Corrections Services Support. Completely rewritten clients for NTRIP and RCV connections. Improved management and stability of the connection. Provided more detailed information about the mount points from the source table of NTRIP Caster. Added support NTRIP v2 protocol.
  • PDF Report. Added localization report with residuals and statistics. Added more information about coordinate systems.
  • Built-in Help Pages. Updated content of pages for the old screens.

Bugs Fixed
  • Background Map download doesn’t work over Cellular Interface
  • Base ID is not displayed for CMR corrections
  • Battery icon is not displayed correctly on Collect screen
  • Can’t set GPRS connection
  • Changing transformation clears the background map
  • Circle is not appearing on the map
  • Clear Keyboard Dictionary does not become grey after clicking at it
  • CoGo functions UI
  • CoGo pick position from map screen when Survey is stopped but not accepted
  • Collecting Device status over RAMS
  • Crashes on Surveying a trajectory
  • Crashes when NTRIP Client is in use
  • Crashes if click at “Configuration file has been corrupted. Press OK for restoring.”
  • Crashes by clicking Help button on two screens
  • Crashes on calling Points screen popup menu and then a hardware “Action” button
  • Crashes on Map Screen
  • CS can’t be changed in Edit Screen
  • CSs are hidden while adding a new localization
  • DPOS coordinates before August 26 does not match the coordinates calculated now
  • Frozen on loading attached project
  • GSM firmware updates fail
  • Hang on Reboot
  • Importing & Exporting DWG files
  • Incorrect binding of the background Yandex Satellite Map
  • JField disconnects from RAMS on firmware update
  • Long Click on Point Name doesn’t open pop-up window
  • Low Power Off has a control with empty name
  • Pairing & Unpairing over USB
  • Pairing & Unpairing over Base/Setup
  • RTPK related issues
  • Screenshot duplication on starting LS as a base
  • Stacking Alignments issues
  • Stop Base does not always stop
  • Touch Screen calibration doesn’t work
  • User profile management issues. Copy
  • Wrong status of Verizon connection if wrong APN

Known Issues
  • Remote Base Configuration. No option to select a non-JAVAD radio protocol to transmit corrections. No ability to know external public IP of the base’s interface to configure TRIUMPH-LS automatically. Manual adjustment in connections settings required. Bluetooth Unpair and Radio Firmware doesn’t work with TRIUMPH-1M. Unpairing over Bluetooth doesn’t work with HPT404BT.
  • Map (Draw). Snap to arc midpoint works incorrectly. Problem with snapping to circle.
  • Bluetooth. Bluetooth headset doesn’t work.
  • UHF. UHF Spectrum Analysis doesn’t work.
 

giulio

Member
I don't know which button I touched during a survey test, but the 10 white boxes have disappeared and I can no longer make them appear in collect (they are still present in stake) I have searched the guides but have not found the solution
 

Jim Frame

Well-Known Member
I've been holding off on this update since it represents such a major change, but I'd like to stay current. It seems that most of the questions/concerns about this update so far have pertained to the LS+. Does anyone who's updated a plain old LS have any advice to offer before I dive in?
 

Steve Hankins

Active Member
5PLS
I've been holding off on this update since it represents such a major change, but I'd like to stay current. It seems that most of the questions/concerns about this update so far have pertained to the LS+. Does anyone who's updated a plain old LS have any advice to offer before I dive in?
Jim, I run the LS standard with a T2, and ArDot RTN, and have been on the new release for over a month. Other than learning to navigate the new interface, (read the white paper), I have had solid results on my setup.
 

Nate The Surveyor

Well-Known Member
One of the changes with 4.0, is that you make radio changes while hooked to the base via Bluetooth. This allows you to also make power level changes, without shutting down your base. This also allows you to use multiple sources of corrections, such as Rtn, and your own local base. Without returning to base. I have a t3, and 35 watt radio. I have moved up to v4.0. It's faster navigating. The stake setup, and collect setup screens are gone. But the items needed on those pages are accessible from stake and collect.
Overall, it's a large step foreword. It will allow more progress, as it a more intuitive structure.
That's my opinion.
Nate
 

Sean Joyce

Well-Known Member
Jim, I run the LS standard with a T2, and ArDot RTN, and have been on the new release for over a month. Other than learning to navigate the new interface, (read the white paper), I have had solid results on my setup.
Same here, look for localization in the coordinate system menu now.
 

Jim Frame

Well-Known Member
First day in the field with v4.0 and I learned that my TCP connection no longer works. John Evers made a heroic effort to get it going again -- much of it while driving down the highway in North Carolina(?) -- but it appears that either v4.0 or the T2 firmware upgrade (as suggested by the migration guide) did it in. :(
 

Jim Frame

Well-Known Member
John suggested that I try JCORS, so back in the office I went about setting it up. I think I have it going in the LS, but now my T2 WiFi LED won't go green, so it can't connect to the JetPack. I've tried clearing NVRAM and rebooting, to no avail. Suggestions?
 

Jim Frame

Well-Known Member
I finally got it figured out (I think!). In all the monkeying around that John and I did trying to troubleshoot the problem, at some point my T2 got reconfigured to connect to my phone's hotspot instead of the Jetpack. Once I got that squared away (which fixed the no-WiFi light situation on the T2), I was still getting a connection error for the TCP setup,. I noticed that in the list of connections there was one that John set up as a test that had the T2 IP address. Even though that connection wasn't selected, it had a green arrow next to it, and I wondered if somehow it was monopolizing the connection to the T2. So I deleted it, and then both the TCP and JCORS connections started working. Whew!
 

Jim Frame

Well-Known Member
Today was my first opportunity to actually use v4.0 in the field after working through the glitches. When I first tried to get a TCP connection through my jetpack I got the dreaded "socket failed" message. Looking at the connections screen I saw that the mystery profile named with the IP address of my T2 had reappeared (I had deleted it a couple of days ago) and had a green arrow to the left of it. I deleted it again, restarted the base, and everything worked fine. I was even able to switch between TCP and UHF on the fly without having to send any GREIS commands directly.

Why does this connection keep getting recreated, and how can I prevent it from happening so I don't have to delete it and restart every time I set up?
 

Wes Hand

Active Member
Jim I think it does it if you use a jetpack at the base…my T1M with Verizon jetpack does the same thing. It doesn’t cause problems for me starting my base though.
 

Wes Hand

Active Member
Logically I think it should say firmware updated but I did the same with a T1M and got confused with the terminology. Not positive but I recall a green check nearby that message and it did complete the update.
 
Top