Javad Mobile Tools (JMT) v5 for Android

[John Rosco]

​

Javad Mobile Tools (v5) for Android can be purchased from JAVAD, Part Number 27-580020-01 - please contact Javad Sales.

The JMT v5 for Android software is available from the JAVAD website – see https://www.javad.com/product/javad-mobile-tools/

Please install JMT v5, and then follow the ‘Android Device ID’ Registration as outlined in the JMT v5 User Manual
which is available here - https://download.javad.com/manuals/JMT/JMT_User_Manual_v5.04.pdf

JMT v5 for Android data collector device requires that 'each Android device' has a valid 'Registration Code' . . .
JMT v5 no longer uses the JMT OAF activation configuration code capability of the JAVAD GNSS receiver . . .

The JMT Registration Request Form is on the JAVAD website.
Please reference your JAVAD 11-digit Order number, that was used to purchase JMT, on the Registration Request form.
Also add in the 'Comment Section' your JAVAD GNSS Receiver model and serial number information, plus any other comments.

Footnote:
JMT and JMT-R v4.x has been depreciated, from the original Google Play-Store.
JMT for IOS has been depreciated and is no longer supported from the App Store.
The most current JAVAD JMT v5 for Android Only, is available directly from JAVAD
– see https://www.javad.com/product/javad-mobile-tools/

 

[John Rosco]

When JMT for Android v5 is installed to an Android device using ‘Scoped storage’, then it is difficult for any other application to access all JMT Android files. Including the Android file manager application.

The solution is to install JMT to use ‘Internal storage’ which allows easy access to all JMT data files.

You may try the following:

Either: Connecting your Android device via USB to your computer
OR: Using the Android Apps | Files utility (from Google Play-Store)

• Create a new folder (off root) Internal storage > javad

The folder should be named javad (all small letters).

• Then reinstall JMT v5 apk from the ‘downloads’ folder...
• Run JMT v5 and the 1st time JMT will ask for a folder to use.
• Select “No previous data in shared storage” option…

• Then choose ‘Internal storage > javad’

JMT v5 should now be setup and installed on the Android unit and should not be using Android ‘scoped or emulated storage’ for the JMT ‘job files’.
The data will be located inside the job (project) folders – IE: Internal storage > javad > jobs > JOB_NAME . . .

 

[John Rosco]

JMT v5 for Android 'Device ID' and 'Registration Code' activation - see attached



Please Note:
JMT v5 for Android data collector device requires that 'each Android device' has a valid 'Registration Code' . . .
JMT v5 no longer uses the JMT OAF activation configuration code capability of the JAVAD GNSS receiver . . .

 

[John Rosco]

Configuring NTRIP corrections via Wi-Fi

The attached document describes how to configure NTRIP corrections via Wi-Fi using JAVAD Mobile Tools (JMT) version 5.1.x

 

[John Rosco]

Regarding Daniel Mekal’s comment on the JDC user forum thread > https://support.javad.com/index.php?threads/javad-data-collector-jdc.6159/#post-55782.
I didn't ask what is JDC.
I asked these questions intentionally.
Because IMU calibration in version 5.1.3 from within JMT is impossible, it doesn't work. Only calibration with an IMU from NetView works.
In JMT version 5.1.3, the IMU doesn't work properly with the Triumph3.
Even staking doesn't work properly in version 5.1.3.
I'm still stuck using JMT version 4.8 despite new releases.

Testing a TRIUMPH-3, with FW 4.6.0, with JMT version 5.1.3, no issues calibrating the IMU and then staking out a point . . .

 

[Andrey Antonov]

Hello John, how can we specify the JMT v.5 ID correctly? The form displays an error, but I do not see any other IDs in the program.

 

[John Rosco]

Hello John, how can we specify the JMT v.5 ID correctly? The form displays an error, but I do not see any other IDs in the program.

JMT v5 for Android needs to have a valid 'Registration Code' based on the JMT 'Device ID' . . .

Please Note:
JMT v5 (from the JAVAD Products | Data Collector website) for Android data collector device requires that 'each Android device' has a valid 'Registration Code' . . .
JMT v5 (from the JAVAD Products | Data Collector website) no longer uses the JMT OAF activation configuration code capability of the original JAVAD GNSS receivers . . .

 

[JAVAD Support]

Using JMT to record and post-process RAW data log-files:

When using JMT to record Raw data to the Javad GNSS receiver internal memory for a point measurement.


You can use the JMT ‘File Manager’ to see the recorded data log-file(s) that have been saved to the Javad GNSS receiver internal memory.


You can then download the .jps log-file (from Javad GNSS receiver internal memory) to your computer and then post process using:-

1. Either: JAVAD DPOS via the JCA website and the Data processing menu
2. Or: Convert to Rinex using the JPS2RIN application and submit the resultant Rinex Observation file to NGS/CORS etc . . .

 

[bjmcclen]

I have been using JMT on android for years and recently saw some concerning issues with my older version on my Samsung Galaxy 6 tablets that I run all my Triumphs on.

I would collect all my data for a day in a single project/job file and then open JMT the next day and all the points were gone.

I downloaded JMT 5 to the tablet for my T3 last week and completed a two day survey today and when I tried to export a report from my points manager the program launched into some kind of startup mode and changed my job to a default.

When I reopened my current job all the points were gone.
I have searched through scoped and shared storage and cant find anything.

This is getting really frustrating.
Luckily I record all my metadata well but this sucks!

Does anyone have any clue what causes this and where my data went?

 

[Nathan Waldren]

Did you download the .jps files from the receiver to the tablet first?

 

[bjmcclen]

Did you download the .jps files from the receiver to the tablet first?

No, I have not typically done this for NRTK data

 

[Nathan Waldren]

They'll still be on the receiver. You can recover them from there through the usual methods.