Installing Tri-Global Software

Transcription

1

2 Installing Tri-Global Software To Begin, let us first talk about the different pieces of software available to you and the purpose for each. The individual software pieces are listed below, with a brief description of the purpose for each. 1) Microsoft Active Sync / Windows Mobile Device Center These two pieces of software are necessary to communicate between a Windows Mobile device and a Windows Desktop computer. They are both free software from Microsoft, but are necessary for the communication. Active Sync is used on Windows XP or earlier computers, while Mobile Device Center is used on Windows Vista, Windows 7 or Windows 8 computers. Tri-Global desktop software WILL NOT communicate with our mobile software unless one of these two items is present and running. 2) Tri-Global Mobile Utility Suite This is a generic term used to describe our Mobile Suite of software that will run on your Windows Mobile Device There are a number of different licenses inside this suite, the most common are MobileStaker and UtiliMapper, but all are grouped under the term Mobile Utility Suite. There are two version of MUS. MUS for 2010 and later and MUS for 2009 and Earlier. What really differentiates the two, is the presence of a Trimble Pathfinder Toolkit license. All Trimble GPS receivers built after 2010 must have a license of Pathfinder Toolkit in order to write Trimble SSF files for post-processing. If you are uncertain whether you have this license or not, consult your Tri-Global representative prior to any installation. 3) Tri-Global Device Manager - This is a free desktop software, created by Tri-Global to manage the mobile device (hence the name). From this software, we can load new versions, download the latest mobile version from our website, register the mobile software and load files such as ESRI shp, csv, or templates to the Mobile device. It also has some basic export functionality to export our Native SQL format straight out to Partner XML, QuickPhoto KMZ, and Silvics ForestCollector text. 4) Tri-Global Transfer Tool Beginning with Device Manager 5.6, The ability to transfer jobs no longer resides in Device Manager. This functionality now resides in TGT Transfer Tool. The sole purpose of this tool, is to take Mobile Utility Suite Jobs (including Trimble GPS files and photos), and compress them into one zip file called a TGZ. This TGZ file can then be sent to another computer to be used by Device Manager or DataView. 5) Tri-Global DataView This is a free desktop software, created by Tri-Global to allow the importation of our Mobile software into a desktop project. From here the user can merge multiple mobile jobs into projects, post-process data (see Pathfinder Office), view data over Google Maps API, and Export to other data formats. 6) Trimble Pathfinder Office Software This is a software created by Trimble Navigation to Post-Process Trimble GPS Files (SSF Files). This is not a free software and is not created by Tri-Global Technologies. In order to post-process jobs inside DataView software or using ChronoCorrect, a valid license of Pathfinder Office, must reside on the same computer as DataView. 7) Tri-Global ChronoCorrect This is another free software, developed by Tri-Global that will automate the operations of Pathfinder Office for Partner Software and Milsoft Field Engineering Users. It will look at a specific input directory, and run once a day to postprocess Trimble SSF files and then export them to a Partner specific text file. While this software is free to any Partner or Milsoft user, the support of this software must be contracted separately with Tri-Global. 2

3 TGT Device Manager 5.70 User Guide Foreword About Device Manager 5.70 CHAPTER I: Getting Started Download Device Manager Installing Device Manger Loading Mobile Utility Suite to a Mobile Device Licensing Mobile Utility Suite (Page 11) CHAPTER II: Sending Data to Mobile Utility Suite Importing Shapefiles (Page 14) Importing CSV Files (Page 18) Importing Partner Units (Page 21) Importing an XML Job into MUS ( Page 25) CHAPTER IV: Exporting Data Connecting to the Database (Page 27) Connecting to a TGZ file (Page 28) Exporting QuickPhotos (Page 30) Exporting Partner XML (Page 31) 3

4 Foreword About Device Manager 5.70 Device Manager 5.70 has been designed with some of the functionality that was in previous versions removed. Some of those pieces have been moved to the new TGT Transfer Tool and DataView2. The goal in moving those functions, was to leave only the basic functions that are used the most inside of Device Manager. The remaining pieces can be broken into essentially, 3 Parts: 1) Installing and Licensing Mobile Utility Suite from Device Manager, 2) Sending data to Mobile Utility Suite from Device Manager, and 3) Exporting Data from Device Manager. A key difference between this version and previous versions, is the Not Connected Dialogue you see in the image below. It is important to realize, that this warning only signifies, that you are not connected to the Mobile Utility Suite database, and has nothing to do with the ActiveSync or Windows Mobile Device Manager connection. Users only need to be Connected to the database to EXPORT data. All other functions should be performed when you are Not Connected! 4

5 CHAPTER I: Getting Started Below we will look at installing Tri-Global Device Manager to the desktop and downloading and installing Mobile Utility Suite to the Mobile Device. To download Tri-Global Desktop software, you can visit our download page located at Once there, click on Downloads as shown below. You will need to create an account to log in to the download page. Follow the online instructions. The account will take 5-10 minutes to activate during normal business hours. If after that 10 minutes you account is still not active, contact your Tri-Global rep. 5

6 I chose to download the compressed installer, to my Desktop. Next, Extract the installer from the zip file you just downloaded. DO NOT ATTEMPT TO INSTALL FROM THE ZIP FILE! 6

7 You will then browse the folder that has just been created by extracting. Inside you will see a series of files like below. double click on Setup.exe. You must have Administrative Privileges to install this! Additionally, it is recommended that you have a connection to the internet. If you do not have the Microsoft.Net Framework 3.5 or SQL CE 3.5 Drivers on your computer, they will automatically be downloaded from Microsoft. 7

8 Loading Mobile Utility Suite to a Mobile Device Device Manager will allow you to download and install Mobile Utility Suite software updates. To do this click on Install to Device / Check for Updates. The software will now query Tri-Global website for mobile updates. You will see the following prompts, click yes or no to the appropriate answers: IMPORTANT INFORMATION The difference between MUS (2009 and Earlier) and MUS (2010 and Later) is very simple. Starting with the Geo6000 and newer Trimble equipment, Trimble adopted a new license system to connect to the Trimble receivers. That license is called Pathfinder Field Toolkit. If you have a valid field Toolkit license, you will use MUS 2010 and Later. If you do not, you will use the 2009 and Earlier version of Mobile Utility Suite. 8

9 You may now connect to your Mobile Device. Please see your mobile device getting started guide if you are uncertain how to do this. Next, Click Install to Device / Install MUS (option as described above). For this guide, we will be installing MUS 2010 and Later. Once you click install, Device Manager will send the installer to the device This can take several minutes, before the message box please check your device to continue installation appears. You will receive the following series of message boxes on the mobile device. Click OK on each one to continue: Once you see that MUS is installed and click OK, you are done installing. Now it is time to license the software. If you are using Mobile Utility Suite for 2010 and Later, you must follow the instructions on the next page. If you are not, please skip the Trimble Activator section, and proceed straight to the section on Licensing Tri-Global Mobile Utility Suite! 9

10 Trimble Activator You will next activate your PF Toolkit license. Do this by going to Install to Device / Run Trimble Activator. For the next steps, you must be connected to the Mobile Device and have Internet Connection: Select the connected Windows Mobile Device, hit Next, Paste your Installation Code, and hit Next again. Select I wish to activate over the Intenet and Next. Finally, if your Device serial number does not pop up, enter it and hit Next. You should see a completed message. Hit Finished. 10

11 Licensing Mobile Utility Suite Tri-Global has implemented a brand new Online licensing system. When you license your software, you will be issued a Customer ID number and a Software order Number. You will need to know both of these to proceed. If you are uncertain about yours, please contact your Tri-Global representative. You must have your device connected to your computer, and Internet access to proceed with the next step! Select Install to Device / Authorize Registration. The next screen you will see, is the Validation Screen. There is a new option to Validate Using Tri-Global ID, press this button. You are then taken to a screen where you will enter your Customer ID Number. After entering this, press OK! 11

12 Licensing Continued Next you will see a screen much like the one below. There are two types of licenses Inactive and Active. Inactive licenses are unused licenses that are available for you to assign to a mobile device. Active Licenses are those that have already been activated on a device. If you are relicensing software to an Active device, the Device ID and Serial Number MUST match! If they do not, you will need to contact Tri-Global about transferring your license, and fees may apply. To Activate a license, select the Order ID you wish to apply and then click Activate. You will be prompted to enter your Device type and Serial Number. Be cautious with your serial number, as this will link your future device, as mentioned above. If you do not see your Device type, simply select any in the list. This is for querying purposes only. Finally, press Confirm! 12

13 Licensing Continued If it is successful, you will receive the message box below, and your software will open on the mobile device! Congratulations, you are ready to start using your software. A final caution! If you are upgrading software, and not performing a clean install; you may see the following error upon first loading the software: This is the error described in the release notes. The settings for the old version, are not compatible with the new. Simply delete the Settings.XML file from the device under MyDocuments\MobileUtilityData\Scripts. Launch the software again after deleting this, and everything should run fine. 13

14 CHAPTER II: Sending Data to Mobile Utility Suite Importing Shapefiles Shapefiles are composed of at least (3) files, SHP, SHX and DBF. The DBF files can become pretty large, it is highly recommended to reduce The size of the DBF by limiting the fields that are in the shapefile, to the data that a field user actually needs to see i.e. Users of a road layer, typically only care about seeing the Road name. Additionally a PRJ file can be present. This PRJ file defines the Projection and Coordinate System of the Shapefile. It is not necessary for our software, but is useful in defining what the Mobile Coordinate System should be in for background display. (see Example Below) All shapefiles must be in the same coordinate system. All shapefiles should be placed in the same directory, and the directory should contain no additional files! WARNING, Do not use a Network Drive folder! PROJCS["NAD_1983_StatePlane_Texas_Central_FIPS_4203_Feet",GEOGCS["GCS_North_American_198 3",DATUM["D_North_American_1983",SPHEROID["GRS_1980", , ]],PRIMEM[" Greenwich",0.0],UNIT["Degree", ]],PROJECTION["Lambert_Conformal_Conic"],PA RAMETER["False_Easting", ],PARAMETER["False_Northing", ],PARAMETE R["Central_Meridian", ],PARAMETER["Standard_Parallel_1", ],PARAMETER["Standar d_parallel_2", ],parameter["latitude_of_origin", ],unit["fo ot_us", ]] Example 1: Contents of a Typical PRJ file opened in NotePad, Defines the Coordinate system as Texas State Plane, Central NAD83, US Foot Units Start in ArcGIS. It is useful to use the Properties of a layer to limit the number of attribute fields that will be sent out to the shapefile upon export to your project Folder (See Example 2) 14

15 Example Above: Shows the size of a Primary Conductor DBF (156 Mbytes) before reducing the fields, vs. the size of the DBF after (under 10Mbytes). This makes a dramatic difference in operations on the Mobile Device. Geo6000 Windows Mobile Devices The Geo6000 loads background data far greater than previous versions. However, it is very important to realize that the Geo6000 still only has 256Mbytes of Memory. To load MUS and the Operating system alone takes up about 120 Mbytes of memory. Therefore, there are 135 Mbytes free to run your operations and load background data. It becomes very difficult to load an entire GIS worth of data onto the handheld device. For this reason, we need to reduce DBF size, sometimes crop shapefiles into smaller sections and utilize some thresholding techniques so that the device does not attempt to load an entire shapefile! Simply click on Send to GPS / Background Shapefiles / Transfer to Device 15

16 Upon successful import of the shapefiles, you will notice that (2) additional files are added to your shapefile directory. APL File this is a default thresholding file, and tells the shapefile not to be drawn past an absolute scale of 1: Therefore, large shapefiles will not crash the system if draw to extents is selected. (more about thresholding in section 7) IDX File this is an index file to allow shapefiles to be queried and drawn more efficiently. Open MUS and make sure that the Mobile Map is set to the same coordinate system as your shapefiles. Managing Thresholds and Layer Symbology. Notice that the same Coodinate System is chosen, as the PRJ file. This is done through, Menu /Options / Setup / Coordinate System. Pay special attention to the Coordinate Units (US Feet) not Feet or Meters! The default symbology may not work for some users, so you can edit this by going to Menu / Options / Manager Layers. Once there you can click on any layer (except Locations), Select a layer, and click Symbology. 16

17 I have chosen to make my County Layer show up at large Scale, as this is a small layer (in file size), and not show Up at scales below 1000 feet. I have also changed the color scheme. After Making your changes, Exit MUS and restart. This will allow your changes to take effect and will look something like the examples below. Notice, that they detailed layers and labels do not show up until I reach a certain scale. 17

18 Importing CSV Data The importing CSV data options is ideal for importing features that you might wish to use for ReNavigation. For this example we will begin inside Microsoft Excel. Notice that you will create 4 key fields. The spelling and capitalization is very important for this to work properly. Those fields are, LocName, Latitude, Longitude and Note. See Below: Save the Excel file off as a CSV file from Excel, the name itself is irrelevant: 18

19 Next you will go to the Sent to GPS / Import CSV Data in Device Manager. You will be instructed to browse to the file you just created. Warning: Make sure you are connected to the Mobile Device at this point! Once you have browsed for the file, you will need to make sure that you have set your Mobile Map Coordinate System, to match the coordinate system set in the device! This is the same as setting it up for the Shapefile import. Click the blue link to set it up! Click Import CSV once you have set your Coordinate System. Ensure that both your CSV file on the desktop and MUS on the Mobile Device are both closed! 19

20 After selecting Import, you will be taken to a wizard of options that will allow you to set up a Job to pull your csv file into. You can choose from an existing job, or create a brand new job by clicking the Add New Job button, as we have. If you choose to Add a new job, you will need to give it a name and optionally a Note, just as you would on the mobile device. Once you have selected / created a job, you will need to either select an existing line or create one to import to, just like the job. As a final step, you will select OK on the Choose Line screen and it will import to the database, and then transfer to the device. You should see the message below when everything is finished. 20

21 Sending Standard Units and Spans to MobileStaker To Begin, start by making sure you have exited out of MobileStaker software on the handheld device! - If you do not, you will not see the units and spans listed in the units dropdown. The units and spans are cached when MobileStaker Opens. Second, make sure that your device is connected to either Microsoft ActiveSync or Mobile Device Center, as shown in the screen shot. Once connected to the device, open Tri-Global Device Manager. 1) Select Send to GPS / Partner / Import Unit Types as shown below 21

22 2) The directory box should be populated (as shown below) If not, browse to your Milsoft Field Engineering Install directory and then find the subfolder v3x\shared\config\customer\pocketpc directory and click OK 3) Click Import Unit Types 4) The next option deals with applying configurations. Essentially, this is asking, would you like to have Unit Header fields on your units and spans? Note: If you are uncertain about this question, we recommend you click NO! for details on what happens when you hit yes, skip to item 6. 5) Finally, you will be prompted with a question to transfer to the device. Select Yes as long as you are connected to the device. Note: This step can take 4-5 minutes depending on the number of spans and units inside Milsoft Field Engineering, so be patient. 22

23 6) If you choose to add Unit Header Fields to MobileStaker you will select YES on the configuration option. A dialogue box similar to the one below will then pop up. 7) On the left side you will see the appropriate Filter Tree that is read from Milsoft Field Engineering for your units. On the left are the header fields that will be added to that tree. Units / OVERHEAD / MISC. in the example above. Phase and Size will be added to that tree. 8) If you don t wish that header field to be added to that particular tree, then you will Unselect that field. You can optionally, Uselect all now! 9) Select the OK button on the bottom of the form when you are satisfied with the results. You will then get the do you wish to copy data dialogue below like mentioned before. 23

24 10) Copy Complete will show when the transfer is complete! Below are example screenshots of how the Header fields will show inside MobileStaker. ( See adding units in the User Guide for further details ) 24

25 Importing an XML Job into MUS The importing XML dialogue is new to version It s purpose is to allow Jobs already created and NOT still on the handheld, to be reimported to the handheld. WARNING, this dialogue will not work, if an existing job already resides on the handheld. To begin, simply select the option to import by going to Send to GPS / Partner / XML Data Browse to the directory where the XML files are stored. The process can take a few minutes to parse through the XML files, so be patient There are a few considerations for this process. 25

26 Importing an XML Job into MUS continued 1. TGF files must be present in a subfolder called: TGFs. If you are an SBS client, the folder should be packaged with the export. For any other user unfamiliar with where to find these XML configuration files, consult your Tri-Global representative. 2. Existing SSF files will not be transferred back to the device. If you wish to be able to postprocess any data imported, the location must be recollected or a new location added. 3. Existing Photos will not be transferred back to the device. You can collect new photos to attach to points, or manually copy photos back to the device. 4. Proper Mobile Map Coordinate System must be set up. This feature should be done prior to import. 26

27 CHAPTER III: Exporting Data Connecting to the Database The first thing you should notice about the new Device Manager Export opitions, are that they are greatly simplified! There are only (3) options for export. Those options are Quickphotos, ForestCollector, and Partner XML. All three begin in the same fashion. You must now Connect to the database as shown below. From there, you will be able to Choose the Job you wish to export and then proceed to the export options listed in this chapter.with the device connected via USB, Click the Connect button. This may take a few seconds, as the database is transferred via USB over to your computer. The result should look like the screenshot below. 27

28 Connecting to a TGZ Like previous versions of Device Manager, we wished to give the operator the capability of exporting from a TGZ or (Tri-Global Zip) file that was created from our Transfer Utility. It is still very easy to do this, but is now a hidden option so that the main user interfaces would remain simple and uncluttered. If you choose to do this option, you will need to access, Edit / Export from TGZ as shown below. Once you select this, you will be allowed to browse for your TGZ file you wish to export from. After finding the TGZ, you may select OK. You will now see that under Not Connected you have a TGZ path. Select Connect as you did when connected directly to the device and proceed to your export option. 28

29 Exporting QuickPhoto Once you are connected to your device, you will simply select the job you wish to export as shown in the example below. Then select your Format and hit Export Data After successful Export you can click on View Exported Files to see your KMZ. 29

30 Exporting QuickPhoto Your file, entitled QuickPhotos.KMZ can then be renamed, ed, moved or any number of other possibilities. When ready to view, you can open it directly in Google Earth. It will contain the photos that you captured and will give the user a location that the photo was created as seen below: 30

31 Exporting Partner XML This section simply deals with exporting to a Partner XML from Device Manager. For more complete information on importing MobileStaker data into FieldEngineering, please reference the Milsoft Field Engineering Appendix to the Mobile Utility Suite 5.2 User Guide. Begin, by connecting to your database or TGZ as described in the previous sections. Select your Job or Jobs you wish to export, then select Partner XML and Export. By Default, all Partner XML is always sent to c:\triglobaldata\partner. If for some reason you wish to change this, it must be done from Edit / Edit Export Directory as shown below. 31