Justin Link and JMT

#1
For a better communication between Justin Link and JMT, I will like to use a "server-client" project exchange scenario by mounting a FTP server in JMT (new FTP services icon).

FTP Services icon.png


That could correspond with a project exchange dialog box in Justin Link, something similar to FileZilla Client interface (TriumphVS link / Project list).

Justin Link exchange screen.png


Probably this is already implemented, but I don't know how it works. I could exchange static files, RTK vector data with covariance information (similar to g-file from LS), then graphically view them, but Justin Link shows a Triumph VS icon then a dialog box with "Can't get tvs file" message.

Also, importing a classic *.RW5 / RAW file format from TS and perform coordinate reduction/adjustments, all of these accompanied by a friendly CAD environment with common drawing/modify functions, osnap settings, etc. could make Justin Link a better tool for every surveyor.
 

Yuri Noyanov

Active Member
5PLS
#3
Sorin,
JustinLink has built-in service to exchange projects with J-Field and Javad Mobile Tools (both iOS and Android). So you can exchange data as shown in the video above.
For iOS version JMobile has built-in FTP server, because all data are hidden inside the application. For Android version all data are in /storage/emulated/0/javad . So every FTP server can share these data. There are hundred FTP servers in Google Play Market so you can install any and run in background. And exchange JMobile data.
Do we really need such functionality in Android version? Or you had different idea?
 
#4
Thank you very much for the video and explanations.
I was able to establish the connection between Justin Link and JMT. Just need a sort tool for the projects in the "Project list" dialog box and somehow the same project information that we have in JMT/Job, if possible.
Best regards.
 
#5
Yuri, the idea of such a FTP Services icon was to also create a fast phone to phone project synchronizing and exchange capabilities for all the JMT data shown in the above video, right in the field. I will search Google Play Market, first.

Bluetooth transfer is slow, memory stick with adapter cables are inconvenient, internet not available in some areas, so a in-place wi-fi server/client transfer scenario between phones is the best choice (similar to Wi-Fi Direct technology, if supported on both Android/iOS devices).
 
#6
My thoughts here are about a field-to-finish workflow with a GNSS receiver, JMT, Justin Link and a (little) computer.
According to the above video, importing a survey project from JMT, generates corresponding RTK points probably with all the associated (tabular) vector information surveyed in the field with multiple RTK engines. Every collected RTK point could have graphically representations (similar to static *.jps recordsets). Usually we set some of the RTK shots as reference (control) points.

It will be nice if JMT could perform a classic *.RW5/RAW field data collection (mainly from J-Mate) and Justin Link imports and dynamically calculates the averages and residuals for the horizontal/vertical/distances readings, then displaying a correct value also based on the settings of the survey elements (prism, temperature, pressure, etc). Some adjustment routines could deal between reference (control) points and a classic *.RW5/RAW field book, if possible.

In JMT, user CAD drawing is in developing. I was told to wait. Justin Link must also have a modern ribbon-based interface and implements a easy to use CAD with command line prompter, and subcommands that are intended to provide alternative choices for various drawing CAD elements.

Somehow we must find a way to have a field-to-finish in house surveying solution from Javad with a GNSS receiver, a small computer running a modernized Justin Link version and JMT for field data collection.
 
#7
Just a *.rw5 export demo with my Android phone collecting points, using internal GPS, no base, no correction, no accuracy, single point positioning.

JB,Test Park,DT02-11-2019,TM14:10:00
MO,AD0,UN1,SF1.00000000,EC0,EO0.0,AU1
--CRD: Alphanumeric
--User Defined: ROMANIA/Stereografic 1970-Marea Negra 1975
--Equipment: Internal GNSS
--GPS Scale: 1.00000000
BP,PN0,LA0.00000000000000,LN0.00000000000000,EL0.000000,AG0.0000,PA0.0000,--
--Entered Rover HR: 1.5000, Vertical
LS,HR1.5000
GPS,PNP1,LA44.27059382000000,LN26.02435306000000,EL118.100000,--bord
--GS,PNP1,N 328525.0283,E 583324.0289,EL80.9761,--
--GT,PNP1,SW2040,ST129967000,EW2040,ET129967000
G0,02/11/2019 15:06:07,(Average) - Base ID read at rover: 0
G1,BP0,PNP1,DX-2280722.039,DY2002465.634,DZ4444137.168
--HSDV:2.126, VSDV:2.900, STATUS:SINGLE, SATS:16, PDOP:1.280, HDOP:0.740, VDOP:1.040
GPS,PNP2,LA44.27058338000000,LN26.02434556000000,EL117.300000,--bord
--GS,PNP2,N 328521.7847,E 583322.4126,EL80.1758,--
--GT,PNP2,SW2040,ST129981000,EW2040,ET129981000
G0,02/11/2019 15:06:21,(Average) - Base ID read at rover: 0
G1,BP0,PNP2,DX-2280719.797,DY2002464.884,DZ4444134.308
--HSDV:2.140, VSDV:3.400, STATUS:SINGLE, SATS:15, PDOP:1.170, HDOP:0.680, VDOP:0.920


JMT could also have the option to import/export GNSS RTK vector records in *.rw5 format.
 

Attachments