Locata LOCLITEG4 LocataLite G4 User Manual LocataLite User s Manual
Locata Corporation Pty Ltd LocataLite G4 LocataLite User s Manual
UserManual.wiki
>
Locata
>
LOCLITEG4 User Manual
User Manual
Navigation menu
Upload a User Manual
Namespaces
Wiki Guide
HTML
PDF
Info
Views
User Manual
Discussion / Help
Navigation
![Chapter 4 LocataLite Operation LocataLite User's Manual Locata-LocataLite-UserManual v8r0 27-May-2014 52 The serial ports may be used to determine the Ethernet configuration (e.g. IP address) of the LocataLite. This process is described in section Error! Reference source not found. on page Error! Bookmark not defined.. 4.11. Web Interface The LocataLite operates a HTTP server which provides a set of simple web pages which display information derived from the LBMP messages defined in reference [4]. To access the web interface use a web browser and set the address to, http://<locatalite_ip_address> Once on this page click on a link to one of the LBMP messages to display data from a given message. The web server will generate a static page and populate it with current data from the selected message. Refreshing the page will trigger a or re-requesting of data that will then be updated on the page. Supported web browsers include: Internet Explorer 9+ Firefox 16+ Chrome 24+](https://usermanual.wiki/Locata/LOCLITEG4/User-Guide-2283666-Page-52.png)
![Chapter 5 Troubleshooting LocataLite User's Manual Locata-LocataLite-UserManual v8r0 27-May-2014 56 External Time Missing. The LocataLite cannot detect a serial connection between itself and the PPS timing source. External Time Bad. Serial communication is operating between the uTevo and the LocataLite, the uTevo has GPS lock, but the LocataLite can't see the PPS. Most likely the cable connecting the GPS PPS to the LocataLite is incorrectly installed or faulty. If the LocataLite LED behavior is difficult to distinguish it is possible to get the same information from the serial stream of $GPLOC,ASC messages that output from COM1 on the LocataLite [115200 baud, 8 data bits, 1 parity bit, no flow control, null modem cable]. The second last field of the ASC message before the checksum indicates the GPS sync error state with the following possible values (matching the error states above): State 0: no error State 1: missing serial comms State 2: bad PPS status State 3: missing PPS Connect a computer to the GPS receiver serial feed [115200 baud, 8 data bits, 1 parity bit, no flow control, null modem cable] and check the SSR report status (which is output automatically at 1Hz). The Appendix “Message Definitions” contains a definition of the SSR message. In particular look at the last 6 fields of the SSR (underlined below). These are the holdover (1), time/frequency tolerances (4) and error conditions (1). When the uTevo has a good solution and an accurate PPS output they should read 0,1,1,1,1,0* as shown. If they read differently then the uTevo is not fully locked to GPS and the LocataLite will not trust the PPS. This would constitute the "State 2" error cited above. $PSGNR,SSR,20100721,093159,1,15.0,0,1,0,1,1,1,1,0*CS If the uTevo is reporting that it does not have GPS lock (as described in point 3 above) it is possible to send queries to determine which signals are being tracked, which have downloaded ephemeris data, and whether a position/time solution is being computed. The following set of commands would be useful. The uTevo communication protocol (Reference 7) describes the commands and their responses. $GPGPQ,GSV $GPGPQ,GGA $GPGPQ,GSA $GPGPQ,UNC](https://usermanual.wiki/Locata/LOCLITEG4/User-Guide-2283666-Page-56.png)
![Appendix Message Definitions LocataLite User's Manual Locata-LocataLite-UserManual v8r0 27-May-2014 A-5 A.2.2 Locata ENV Message This message reports the internal temperature and supply voltage for the LocataLite. ENV Format $GPSLOC,ENV,<week>,<tow_s>,<t1>,<t2>,<t3>,<t4>,<t5>,<tmax>,<Vss>*CS\r\n ENV Fields Table 19, ENV message fields Field Symbol Description (units) Range / Options / Comments 1 Week Week number [week] GPS week number 2 tow_s Time of week [s] Seconds into the week 3 t1 CPU temperature [ºC] Resolution to nearest °C 4 t2 CPU PCB temperature [ºC] Resolution to nearest °C 5 t3 FPGA temperature [ºC] Resolution to nearest °C 6 t4 FPGA PCB temperature [ºC] Resolution to nearest °C 7 t5 TCXO PCB temperature [ºC] Resolution to nearest °C 8 tmax Max of t1 through t5 [ºC] Resolution to nearest °C 9 Vss Supply voltage [V] Resolution to mV](https://usermanual.wiki/Locata/LOCLITEG4/User-Guide-2283666-Page-67.png)
![Appendix Configuration File LocataLite User's Manual Locata-LocataLite-UserManual v8r0 27-May-2014 A-13 APPENDIX B CONFIGURATION FILE What follows is the contents of a standard LocataLite configuration file including documentation of all user configuration options. ############################################################################# # Configuration File: loclite_release_config.txt [2014-05-14 at 02:44:40] ############################################################################# ############################################################################# # LocataLite Device Type # # There is only one Master in a given network. The remaining LocataLites # are Slaves. In general you should designate the LocataLite that is best # placed to provide a timing reference for the network as the Master # LocataLite. That is, the Master should be that LocataLite having the # shortest paths, including using the fewest TimeLoc hops where necessary # to all other LocataLites. This arrangement would provide the cleanest # TimeLoc performance operationally. However, other reasons may prompt a # different selection for Master, such as accessibility or elevation. # # Options: MASTER, MASTER_WITH_GPS_SYNC, SLAVE # Device_Type = MASTER; ############################################################################# # LocataLite Device ID # # This is a numeric assignment to each LocataLite which determines the # pseudorandom spreading code and TDMA timeslot used by each device. # # Device ID selection: # # - Each LocataLite device must be configured with a unqiue ID different from # all other LocataLites in the same network. # # - Maximising usage of device IDs from within each decade series ensures # overlap is avoided in small networks and kept to a minimum in larger # networks. # # 10 or fewer devices - operators should choose device IDs within within # the same decade. For example within the range 1-10 # or 11-20. This approach maximises network # performance by ensuring that all active TDMA # transmissions do not overlap. # - Examples: # 7 devices: 1,2,3,4,5,6,7 # 10 devices: 1,2,3,4,5,6,7,8,9,10 # # More than 10 devices - operators should initially choose device IDs within # the same decade (as above) and then repeat this # process by only adding additional IDs from within # another decade until this is full, etc.](https://usermanual.wiki/Locata/LOCLITEG4/User-Guide-2283666-Page-75.png)
![Appendix Configuration File LocataLite User's Manual Locata-LocataLite-UserManual v8r0 27-May-2014 A-14 # - Examples: # 16 devices: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16 # 22 devices: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16, # 17,18,19,20,21,22 # # - It is convention to assign a loclite_device_id of 1 to the Master # LocataLite, although it is not necessary to do so. # # Notes: # # - Note that the TDMA transmission sequences have been carefully defined such # that the impact of transmission overlap possible in larger networks is # minimised. Key statistical properties of transmission sequence # combinations were optimised during this process to ensure performance is # consistent and reliable in these scenarios regardless of the specific # device ID combinations in play. # Loclite_Device_ID = 1; ############################################################################# # Reference device for TimeLoc # # Relevant to SLAVE LocataLites only (not Master LocataLites) # # Defines the reference device ID used to acquire TimeLoc and synchronise with # the network. Slave LocataLites will search for the LocataLite cited in this # field when searching for a TimeLoc signal at boot. # # Typically a Slave LocataLite will have a direct line-of-sight path to the # Master LocataLite and so operators should you should set this field to match # the loclite_device_id of that Master LocataLite. When this direct line-of- # sight path does not exist operators will need to set this field to match the # loclite_device_id of another Slave LocataLite in the network which is # TimeLoc'd directly from the Master LocataLite, or alternatively to another # Slave LocataLite with the shortest path (fewest and shortest hops) to the # Master LocataLite from itself. # Reference_Device_ID = 2; ############################################################################# # Rx and Tx Antenna of this LocataLite # # Note that this parameters are ignored when self-survey is enabled. # # LocataLiteRx is the Receiver Antenna. # LocataLiteTx1 uses the antenna connected to port Tx1 on the LocataLite. # LocataLiteTx2 uses the antenna connected to port Tx2 on the LocataLite. # # LocataLiteRx/LocataLiteTx1/LocataLiteTx2: # # Field Description Range # ===== =========== ===== # Coords Rx Antenna coordinates [X,Y,Z] ECEF XYZ co-ordinates [m] # Attitude Yaw, Pitch, Roll, Validity [0 - 359,-90-90,-90-90,YES/NO] # RxAntennaType Possible types are: [ 0-5 ]](https://usermanual.wiki/Locata/LOCLITEG4/User-Guide-2283666-Page-76.png)
![Appendix Configuration File LocataLite User's Manual Locata-LocataLite-UserManual v8r0 27-May-2014 A-15 # # 0 - None # 1 - AeroAntenna Patch (AT2400) # # Name of this site: [INSERT NAME HERE] # LocataLiteRx: Coords[ -4431684.7961, 2636076.3421, -3742707.4700 ] Attitude[ 360, -90, -90, NO ] RxAntennaType[ 1 ]; LocataLiteTx1: Coords[ -4431684.7961, 2636076.3421, -3742707.4700 ] Attitude[ 360, -90, -90, NO ] TxAntennaType[ 1 ]; LocataLiteTx2: Coords[ -4431683.5388, 2636075.3371, -3742706.1663 ] Attitude[ 360, -90, -90, NO ] TxAntennaType[ 1 ]; ############################################################################# # LocataLite Self Survey ############################################################################# # The following parameters apply to the LocataLite GPS self-survey feature. # # When this feature is enabled the LocataLiteRx/LocataLiteTx ECEF XYZ # co-ordinate parameters are ignored. ############################################################################# # Enable/disable self-survey # # Options: ON, OFF (default) # SelfSurvey_enabled = OFF; ############################################################################# # Select the level of GPS dependency. This series of parameters changes the # LocataLite behaviour when valid TPV data is unavailable during each stage # of operation. # # Valid options are: YES (default) / NO # # Any combination may be selected to achieve the desired operation. # # SelfSurvey_GPS_rqd_to_load_nv_posn: # # Defines whether GPS position data is required to validate a previous survey # position loaded from non-volatile memory at boot. # # YES - non-volatile position must be validated before it can be used # NO - non-volatile position will be used even if we can't validate it, # position will ultimately be verified if GPS becomes available # # SelfSurvey_GPS_rqd_during_full_survey: # # Defines whether the LocataLite reports bad health if GPS data is not # available at any point during the full survey. # # YES - LocataLite will assert bad health during the full survey if GPS is # not present or has bad quality # NO - LocataLite can assert good health during the full survey even if](https://usermanual.wiki/Locata/LOCLITEG4/User-Guide-2283666-Page-77.png)
![Appendix Configuration File LocataLite User's Manual Locata-LocataLite-UserManual v8r0 27-May-2014 A-16 # GPS is not present or has bad quality # # SelfSurvey_GPS_rqd_during_monitoring: # # Defines whether the LocataLite reports bad health if GPS data is not # available at any point during on-going position monitoring. # # YES - LocataLite will assert bad health during on-going monitoring if GPS # is not present or has bad quality # NO - LocataLite can assert good health during on-going monitoring even # if GPS is not present or has bad quality # # SelfSurvey_movement_asserts_bad_health: # # Set whether detecting movement is cause for setting the LocataLite health # as bad in the NAV data. # # YES - LocataLite will assert bad health if movement is detected # NO - LocataLite can assert good health even if movement is detected # SelfSurvey_GPS_rqd_to_load_nv_posn = YES; SelfSurvey_GPS_rqd_during_full_survey = YES; SelfSurvey_GPS_rqd_during_monitoring = YES; SelfSurvey_movement_asserts_bad_health = YES; ############################################################################# # Set the vertical offsets between the GPS antenna and the LocataLite # antennas in metres. # # The GPS antenna should be above all LocataLite antennas and the offsets # given as positive numbers. e.g. 0.015 # # Defaults: # Tx1 = 0.200 # Tx2 = 2.200 # Rx = 0.350 # # Units: [metres] # SelfSurvey_Tx1_offset = 0.200; SelfSurvey_Tx2_offset = 2.200; SelfSurvey_Rx_offset = 0.350;](https://usermanual.wiki/Locata/LOCLITEG4/User-Guide-2283666-Page-78.png)
![Appendix Configuration File LocataLite User's Manual Locata-LocataLite-UserManual v8r0 27-May-2014 A-18 # <rate> : MEAS_RATE : output message at the measurement rate # NAV_RATE : output message at the nav solution rate # ON_UPDATE : output message whenever the underlying data changes # <period_in_seconds> : a period in seconds (treated as a float) # # A maximum of 16 LBMP_schedule_message entries are allowed. Only one rate # per message ID is accepted. If multiple requests for the same message ID # are provided only the final request will apply. # # It is up to the user to schedule any desired messages, no LBMP messages # are scheduled to output by default. # # These elements only apply when IO_PORT_LBMP is selected for at least one # COM port. # LBMP_schedule_message = 1001, 1.0; LBMP_schedule_message = 2001, 5; LBMP_schedule_message = 6101, ON_UPDATE; LBMP_schedule_message = 7001, ON_UPDATE; LBMP_schedule_message = 8001, ON_UPDATE; LBMP_schedule_message = 9001, ON_UPDATE; LBMP_schedule_message = 9002, ON_UPDATE; LBMP_schedule_message = 9003, ON_UPDATE; LBMP_schedule_message = A001, 60; ############################################################################# # Specify the initial time and date in the following format: # # Date = YYYY/MM/DD # Time = HH:MM:SS # GPS/UTC offset = [offset in seconds] # - where UTC_time = GPS_time - offset) # Date = 2014/05/14; Time = 02:44:40; GPS_UTC_Offset = 16; ############################################################################# # Operating_Region # # Set the region in which this LocataLite is operating for the purposes of # spectrum management. This parameter will be used with the Frequency_Plan # parameter to limit the maximum output power of the signals that are # broadcast from the LocataLite. # # # | Location | # -----|-----------------------------| # 1 | US (FCC compliant, default) | # -----|-----------------------------| # Operating_Region = 1;](https://usermanual.wiki/Locata/LOCLITEG4/User-Guide-2283666-Page-80.png)
![Appendix Configuration File LocataLite User's Manual Locata-LocataLite-UserManual v8r0 27-May-2014 A-19 ############################################################################# # Frequency_Plan # # Set the carrier frequencies to be used by the system. Default is plan '2'. # This single parameter defines the frequencies for all four signals from the # LocataLite. It is critical that this parameter be configured consistently # by all LocataLites and Rovers across a LocataNet. # # # | Carrier 1 | Carrier 2 | # -----|--------------------------|----------------------------| # 1 | S02 | 2411.211 MHz | S62 | 2472.591 MHz | # 2 | S02 | 2411.211 MHz | S52 | 2462.361 MHz | # -----|--------------------------|----------------------------| # Frequency_Plan = 1; ############################################################################# # LT_Board_Revision # # Specify which revision of transmitter hardware is present in this LocataLite. # This information is used to determine the correct settings to achieve the # requested output power. In future the LocataLite will be able to detect # the hardware revisions itself and this parameter will be removed # # There are currently two supported boards: # # 1 - the original tx board # 2 - the new tx board produced in 2012 # # (Note that updated transmitter boards may be retrofitted to first generation # systems) # LT_Board_Revision = 2; ############################################################################# # LT_Tx_Power_dBm[] # # Set the transmit power for each of the four signals from this LocataLite. # The powers are set in units of dBm with a special value 'max' which will # use the maximum allowed power for the given operating region and frequency # plan. # # Range : -49 to +20 dBm # Step size : 1 dB # Special cases : max # # Restrictions: # # (a) The max Tx power depends on the region in which the LocataLite is # operating according to the 'Operating_Region' parameter and the # frequency plan that has been selected. If a value higher than # the maximum allowed power for that region and frequency is # selected the LocataLite will limit the power to the maximum # allowed value for that region and frequency. # # (b) Note that it is important to avoid setting too great a difference](https://usermanual.wiki/Locata/LOCLITEG4/User-Guide-2283666-Page-81.png)
![Appendix Configuration File LocataLite User's Manual Locata-LocataLite-UserManual v8r0 27-May-2014 A-20 # between the transmit powers for two different transmit signals. # Doing so can introduce a persistent near/far effect where the stronger # signal causes interference on the weaker signal. The maximum transmit # power difference allowed between any two signals is therefore # restricted to 10dB. # # Channel map: # # 0 --> A # 1 --> B # 2 --> C # 3 --> D # LT_Tx_Power_dBm[0] = max; LT_Tx_Power_dBm[1] = max; LT_Tx_Power_dBm[2] = max; LT_Tx_Power_dBm[3] = max; ############################################################################# # Network Longest Edge (m) # # This value defines the longest range between any two LocataLites in the # Locata network. # # Note: this parameter is only used by a MASTER or MASTER_WITH_GPS_SYNC # LocataLite. SLAVE LocataLites will ignore the configuration file # value as it is transmit to them by their TimeLoc reference LocataLite. # Network_Longest_Edge = 2500.0; ############################################################################# # Type of GPS Receiver to which Master will synchronise # Note: Set to None if GPS synchronisation is not required # # Options: uTevo, TSC4400, JPS, None # # Note: this parameter will be ignored for all LocataLite types other than # MASTER_WITH_GPS_SYNC # GPS_Receiver_Type = uTevo; ############################################################################# # Met Station polling configuration. # 0 - Do Nothing # 1 - Poll the Met Station for data # 2 - Configure the Met Station to output data we understand at boot (default) # met_station_polling = 1;](https://usermanual.wiki/Locata/LOCLITEG4/User-Guide-2283666-Page-82.png)
