Orion Users Guide-v2.061

8/7/2019 Orion Users Guide-v2.061

1/31

D R A F T

Orion Users Guideversion 2.061April 22, 2004

Foreword

Thank you for choosing Orion. Orion is a DSP equipped broadband receiver/data logger,with unprecedented flexibility to be used as a radio or acoustic telemetry unit. Its inputdaughter board may be changed, depending on the study to be implemented, to receiveVHF radio signals in the 148 to 170 MHz range, IF radio signals in the 30 MHz range, or acoustic signals in the kHz range. Similarly, output options are in development to permitremote download by radio, serial port, or cellular modem.

Taking the VHF radio range as an example, Orion may be configured to monitor any 1MHz band between 148 and 170 MHz. It will do this without scanning frequencies, ahuge advantage in many situations in radio telemetry data collection. Its sensitivity isbetter than any existing broadband receiver.

Downloading is simple and quick simply remove the MMC card and replace with afresh one. Your receiver is off line for a matter of seconds. MMC cards are widelyavailable in commercial outlets, and can be obtained in many sizes. Orion comesequipped with a 32 MB card. Orion will automatically detect the correct size of the cardinserted.

Orion operates on 12V DC power, which may be supplied by a 12V battery or through awall converter plugged into the AC power. Orions power consumption in normaloperation is approximately 0.5A. This will increase somewhat if the radio transmitter download option is selected, for example.

Two fundamental operations are performed using the Orion software supplied on the CD:configuration for optimal operations, and downloading and converting data. Alloperations are performed through a single software application called OrionTool.

This document describes the operation of the Orion and the OrionTool.

Orion Users Guide-v2.061.docc Grant Systems Engineering Inc., 2004


2/31

Draft, April 22, 2004 Page 2 of 31

Table of Contents

1 Hardware..................................................................................................................... 31.1 Internal Components ........................................................................................... 3

1.2 External Components and Connectors................................................................ 31.2.1 Power Connector......................................................................................... 31.2.2 Antenna Input.............................................................................................. 31.2.3 MMC card slot ............................................................................................ 31.2.4 Serial Connectors ........................................................................................ 41.2.5 LED Indicators............................................................................................ 41.2.6 Pause Button ............................................................................................... 5

2 Software ...................................................................................................................... 62.1 OrionTool Installation......................................................................................... 62.2 Running OrionTool............................................................................................. 6

2.2.1 Options........................................................................................................ 7

2.2.2 Serial Communications Commands............................................................ 82.2.2.1 Configure Orion ...................................................................................... 92.2.2.2 Manage Memory................................................................................... 18

2.2.3 MMC/Data Commands............................................................................. 192.2.3.1 Download From MMC ......................................................................... 202.2.3.2 Convert Data ......................................................................................... 202.2.3.3 Erase MMC........................................................................................... 212.2.3.4 Upload Firmware to MMC ................................................................... 21

3 Factory Configuration Settings ............................................................................. 224 Output Data Formats................................................................................................. 22

4.1 Orion Format..................................................................................................... 23

4.1.1 Text Format............................................................................................... 234.1.2 Log Format................................................................................................ 244.2 Mitas Format..................................................................................................... 26

4.2.1 Text Format............................................................................................... 274.2.2 Log Format................................................................................................ 27

4.3 ATS Temp Format ............................................................................................ 294.3.1 Text Format............................................................................................... 294.3.2 Log Format................................................................................................ 29

4.4 Output Fields Used ........................................................................................... 305 Known Limitations ................................................................................................... 31

1

Orion Software Manual v2.061c Grant Systems Engineering Inc., 2004


3/31


4/31


The MMC slot is used for inserting/removing MMC cards. The correct orientation of thecard is shown in the graphic on the front face of the case just above the slot. The graphicshows that there are 2 MMC slots, but only MMC-A is currently in use.

To exchange an MMC card, please read the section about the Pause Button below first.

1.2.4 Serial Connectors

Orion is equipt with 2 serial ports. Currently, only Serial A is in use. Its location isshown in the graphic on the front face of the case.

1.2.5 LED Indicators

There are 3 LED indicators on the front face of the Orion. They are arranged verticallyand have the following meanings in normal operations.

LED State Meaningoff Input DC voltage is in valid range. Or,

input voltage is near 0.0.Low voltageOn (red) Input DC voltage is inadequate for Orion

to function properly.Flashing (~1 second cycle) Orion is sampling data.

Sampling data Frozen Orion is not sampling data. This couldbe because Orion isnt configuredproperly.

Flashing (~1 second cycle) Orion is decoding data. This means thatthe decoding process is going on NOTthat a tag has been detected. Theflashing occurs independently of any tagdetection.Decoding data

Frozen Orion is not decoding data. This couldbe because Orion isnt configuredproperly, or because Orion is paused.

Special LED sequences:

Event LED indicator sequenceOrion Booting

Both LEDs on for ~ 20 seconds

Decoding LED flashes rapidly for ~5 seconds.

Sampling LED flashes rapidly for ~5 seconds. This mayoccur before decoding LED finishes flashing.



5/31


After a delay, both lights will flash, showing normaloperations. This delay may be ~20 seconds/

New Firmware Upload

Both LEDs flash rapidly, not synchronized.

Brief delay, then Sampling LED off.

~1 second delay no LED activity.

Decoding LED flashes again but more slowly.

Decoding LED off.

Normal Operations /Running State

Both Decoding LED and Sampling LED flashing at ~ 1second cycle. These light should be synchronized, but willjump from being in-phase to being totally out of phase.

Paused State

The Sampling LED will continue to flash as the normalrate, but the Decoding LED will be frozen.

1.2.6 Pause Button

The pause button is located next the the MMC slot. The pause button is a state-lessbutton. When you push the button the state will toggle between running and paused.Sometimes you will find you have to push the button a couple of times before the statechanges properly. The state can be determined from the LED indicators.

The Orion states are defined as:

State Meaning

Running Orion is running, and is acquiring/storing tag data if present. Orion can beconfigured.

Paused Orion will NOT acquire tag data even if present. Orion can be configured.

There are 2 uses for Pause Mode:

If you wish to exchange the MMC card, place Orion in pause mode, exchange theMMC card, and place Orion in running mode. This will accomplish 2 criticalthings.

1. It will guarantee that data is not being written to the MMC card at the timeyou are removing it.2.

After the new MMC card is inserted, transitioning from pause mode torunning mode will initialize the MMC card interface. If this is notperformed, NO DATA WILL BE WRITTEN TO THE MMC.

When Orion is running, detected tag records are streamed out the serial port. Thisis generally not an issue, but if the streaming rate is too high, you can lose control



6/31


and NOT be able to configure Orion. Often, this happens if the noise floor is settoo low, and you cant change the noise floor because you cant configure theOrion because the serial port is swamped. In this case, place the Orion in pausemode, wait for the serial output queue to empty, and then you should have no

problems configuring Orion.

2 Software

All control, configuration, and data management software functions are performed by asingle Windows application called OrionTool. This section describes the installationand functioning of OrionTool.

2.1 OrionTool Installation

Installation Steps:

1.

Create a folder for Orion software and data. This following assumes you havecreated C:\Orion.

2.

Create a folder for executables, C:\Orion\bin3.

Create a folder for data, C:\Orion\data

4.

Create a folder for installation, C:\Orion\install5.

Copy the contents of the installation CD to C:\Orion\install

6.

From explorer or My Computer, navigate to C:\Orion\install and run the setupapplication GTK-Runtime-Environment-2.2.4.1.exe.

7.

Add C:\Orion\bin to your path. This can most easily be modified from Start ->Settings -> Control Panel -> System -> Advanced -> Environment Variables.

8.

Also, add the location of the GTK libraries you just installed. If you accepted thedefaults on installation then you must addC:\Program files\Common Files\GTK\2.0\lib

9.

Copy from the installation folder to the bin folder:

OrionTool.exe

dd.exe

10. Create a shortcut to OrionTool.exe and place it on your desktop.

11. Launch OrionTool and configure as necessary.

2.2 Running OrionTool

When you launch OrionTool, you will see the following interface:



7/31


There are 3 areas of interest in running OrionTool.

Options to setup a number of required parameters for the tool itself.

Serial Communications Commands tools you can use when connected via aserial connection to an Orion unit. These include tools for configuring Orion andfor managing internal memory.

MMC/Data Commands tools you can use when downloading data from an MMCcard, or for further processing.

These features will be discussed in separate sections below.

2.2.1 Options

The Options are accessible from the Options menu. The Options Page looks like this:



8/31


The parameters, and their meanings, are given below.

Parameter Meaning Remarks

Com Port Com Port used tocommunicate with Orion

Drop-down list is populatedwith valid ports only.

Mmc Drive Drive letter of MMC drive. Can be determined usingMy Computer, or explorer, with your MMCreader/writer plugged in.

Data Folder Default location for Oriondata.

Can be modified by clickingon the button. During datadownload/conversion, anyother folder can benavigated to this is onlythe starting point.

Compressed File Extension File extension applied tocompressed data file

Compressed file is inbinary.

Text File Extension File extension applied totext data file

Text file contains extracteddata, in text.

Log File Extension File extension applied to logfile.

Log file is a summary file.

Output Format Different users requiredifferent data outputformats. This drop-down isused to select a data format.The data format does noteffect the compressed filebut DOES effect the textfile and the log file.

Current Options:

Orion givesessential informationonly.

Mitas output textfile is compatible withMitasView viewer software. Also, tagfrequency is not givenbecause it has beenconverted to channels.

ATS Temp. Outputappropriate for ATSTemperature tags.Includes approximatetemperature as well asactual interval in ms.

2.2.2 Serial Communications Commands



9/31


The serial communications commands are ONLY useful if OrionTool is running, andthere is a NULL modem serial cable between the PC and Orion, and if Orion is running(in running or in paused mode).

There are 2 Serial Communications Commands:

Configure Orion used to configure Orion, and/or for setting the receiver time.

Manage Memory used to see how much data is on the MMC card currently inthe Orion, and/or to clear the memory.

2.2.2.1 Configure Orion

The Orion Configuration dialog contains 2 menus, File and Receiver. The File menuis used for reading/writing the global parameters. The Receiver menu is used to Send or Retrieve configuration information to/from the Orion currently connected.

The configuration information is laid out in pages, which are selected using the tab on topof each page. As the pages are similar in function, this document will discuss only thefirst page, ID, in detail, simply defining the parameters on the other pages.

The ID page contains a label (Identification Parameters) which describes the generalpurpose of the parameters on the page. The ID page also contains a table of parameters.Each parameter (row) has four elements:

The name of the parameter

A check box to indicate if the parameter is global. If you click on the check box,the global symbol will appear or disappear. A Global parameter is one thatapplies to a group of Orions, such as site ID, as opposed to one that is specific toone unit (such as antenna number) For more on Global parameters, please refer to Section 2.4.

The current value of this parameter. If you are connected to an Orion unit andhave pressed Retrieve Config, this will be the last value of the parameter set onthat Orion unit. These values cannot be overwritten by the user, and can bechanged only through reconfiguration.

The new value of this parameter. This is the value that would be set on an Orionunit if you pressed Send Config.

In this section, the pages will be shown, along with descriptions of the variousparameters.

Config ID Identification Parameters



10/31


Parameter Meaning RemarksAntenna Number An integer representing the antenna number.Site ID An integer representing the site number.

Config Channels



11/31


The Channel configuration contains multiple pages because Orion can be configured tohandle and scan through 5 bands if required.

There is 1 common setting for all bands:

Parameter Meaning RemarksScan Time (s) The amount of time to spend on each band, if multiple bands

are enabled.Can be set inincrements of 0.1 s.

And for each band, these settings apply:

Parameter Meaning RemarksEnabled If a band is enabled, it will be

included in the list of bands toscan. If not, it will be ignored.

Cur shows the current setting,New shows the new setting if the configuration were to beuploaded.

Base Freq (MHz) Sets the base Freq for the band.The base freq can be set inmultiples of 100 kHz.

The valid values for the basefrequency is determined by theinput board installed.



12/31


13/31


recorded as part of the data set.PQ Max Max Pulse Queue desired for

constraining the automatic noisefloor

PQ Max Min Pulse Queue desired for constraining the automatic noisefloor.

Larger numbers will lower thenoise floor (make the receiver

more sensitive), but allow moreinterference from noise.

Config Tags

The tag configuration page contains multiple pages. One page, Types is used to selectwhich tag type is to be used, and then there is a separate setup page for each tag type.

Parameter Meaning RemarksUse ATS TemperatureTags

Enable detection of ATSTemperature tags.

Use Beeper Tags Enable detection of Beeper tags.



14/31


15/31


Temp Offset 10*interval(ms)/divisor] / 10

These values are tag specific. Toget approx temp values, typical

values can be used.Power Match Maximum power fluctuationallowed between pulses in asingle contact

Power unit is dB.

Tags Beeper

Parameter Meaning RemarksPulse Min (ms) Minimum acceptable length of

pulsesPulse Max (ms) Maximum acceptable length of

pulsesInterval Min (ms) Minimum Acceptable interval.Interval Max (ms) Maximum Acceptable interval.Doppler (ms) If more than 2 pulses are required, Useful for acoustic.



16/31


this setting specifies a timeacceptance window.

Required Number of Pulses

Required number of pulses tocreate a contact record.

Power Match Maximum power fluctuationallowed between pulses in asingle contact

Power unit is dB.

Tags Lotek

Parameter Meaning RemarksLotek Codeset Codset to use.Power Match Maximum power fluctuation

allowed between pulses in a singlecontact

A contact that exhibits substantivevariation in power levels betweenpulses may be rejected as beingnoise. Power unit is dB.



17/31


18/31


Config Hardware

Parameter Meaning RemarksInput Board Type of input board installedOutput Board Type of output board installedCalibration Offset Offset applied to dBm calibration Linearly applied to convert dB to

dBm.Dead Time (scans) Allows the receiver to become

deaf for a certain number of scans after a pulse is detected.

Useful for controlling reverb inacoustic applications.

Gain A First-stage gain setting Factory set

Gain B Second-stage gain setting Factory set

2.2.2.2 Manage Memory

The Orion Memory Management windows looks like this:



19/31


The window shows the current memory status of the MMC card inserted in the Orion.

The Rx Memory menu has 2 menu items.

Status Used to update the display to reflect changes since the last update.

Erase Used to initialize the MMC card in the Orion. If selected, the user will beprompted before proceeding with the following dialog box:

2.2.3 MMC/Data Commands

The MMC/Data commands are useful for interacting with the data, particularly whenconnected to a USB MMC reader/writer. These commands may be executed whether or not an Orion is connected to the serial port.

The MMC/Data Commands are:

Download From MMC for downloading and converting compressed data intotext and log files.

Convert Data to reconvert data This will re-extract the compressed data intothe text and log files.



20/31


Erase MMC This will clear the MMC device. When placed into an Orion andun-paused, the MMC card will be auto-sized and an appropriate header will bewritten. This function will erase data cards and/or firmware cards.

Upload Firmware to MMC. This will deposit new firmware onto an MMC card insuch a way that Orion will detect and self-install the new firmware.

2.2.3.1 Download From MMC

When you select Download from MMC, a dialog box will appear letting you navigateto the folder, and select the file prefix, that you want. The dialog box looks like this:

2.2.3.2 Convert Data

When you select Convert Data, a dialog box will appear letting you navigate to thefolder and select the compressed filename that you want. The dialog box is the same asfor the Download From MMC tool.



21/31


22/31


Now, when you click OK, the firmware file will be uploaded to the MMC.

3 Factory Configuration Settings

Many of the configuration settings are known only by the user. This includes arbitrarysettings (such as antenna number) and project specific settings (such as what frequenciesthe tags are on).

However, there are some recommended settings that should apply for all orions and theseare listed here.

Input BoardParameterAcoustic 30 MHz 150 MHz

Noise store noise no no noNoise - AutoNoise yes yes yesNoise - PQ Max 3 5 5Noise - PQ Min 1 3 3Tags Pulse PowerMatch 50 4 4Hardware - calibration 0 -130 -130Hardware - deadtime 5 0 0Hardware Gain A 4095 4095 4095Hardware Gain B 0 200 200

4 Output Data FormatsOrion records data to the MMC card in a compressed format. When data is downloadedit is automatically converted to human readable formats. The conversion format isdetermined by the Output Format specified in the OrionTool Options.

Please note that the conversion process produces 2 output files:



23/31


A Text file, which contain a record (line) for each tag contact. The fieldsincluded varies with the output format specified.

A Log file, which contains summary information about all the data in the file.The summary produced varies with the output format specified.

As of this version, there are 3 output formats:

Orion this gives essential tag information only.

Mitas this is a file format compatible with the Mitas receiver. It contains extrafields that are sometimes useful for diagnostic purposes. Also, files in this formatcan be viewed with the MitasView data visualization software.

ATS Temp this file format outputs fields that are meaningful only for ATSTemperature tags.

Special formats may be created for customers on request.

This section shows example data and explains the output formats. Please read the sectionon the Orion Format first, regardless of which format you wish to use, as generalinformation is given there.

4.1 Orion Format

The Text format and Log format files that follow were created from the same compressedfile. The Text Format section only shows the first 9 records the Log Formatsection shows the results for the entire data file. The data was created using Lotek codedtags.

4.1.1 Text Format

A sample or the text output format is shown below.

The file consists of a header, followed by the data presented one line per tag record.

A complete list of the fields used, their meaning, and their units can be found later in thissection.

Date Time Site Ant Freq Code Power NFL2004-04-15 09:48:11 4 3 150.280 25 -78 -1002004-04-15 09:48:16 4 3 150.280 25 -78 -1002004-04-15 09:48:21 4 3 150.280 25 -78 -1002004-04-15 09:48:26 4 3 150.280 25 -78 -1002004-04-15 11:51:32 4 3 150.380 46 -107 -1102004-04-15 11:51:41 4 3 150.400 247 -110 -1102004-04-15 11:51:50 4 3 150.420 2 -110 -110



24/31


25/31


-88 4-89 3-90 * 7-91 * 7-92 4

-93 *** 14-94 *** 14-95 ** 10-96 *** 16-97 ***** 24-98 ****** 25-99 ********* 40

-100 ******** 35-101 ******** 33-102 ******** 33-103 ** 9-104 **** 19-105 ************ 52-106 ************ 49-107 ***************** 70-108 ************************* 104-109 ************************************************** 202-110 ********************************************** 187

#Noise By Freq:+---------+---------+---------+---------+--------- 4

150.400 ************************************************** 4

#Noise By Power:+---------+---------+---------+---------+--------- 3

-96 ************************************************** 3-97 **************** 1

Hourly Performance Indicators

Performance Indicators By Hour:

Year-Mo-Dy-Hr AveNoiseFloor AveNumScans AvePulseQueue2004-04-15-09 -100.0 191.0 N/ANo Data for 1 hour2004-04-15-11 -110.0 197.5 7.12004-04-15-12 -109.6 198.6 5.52004-04-15-13 -107.2 199.6 6.52004-04-15-14 -105.7 199.4 6.42004-04-15-15 -102.3 203.4 3.02004-04-15-16 -102.0 205.4 3.4



26/31


4.2 Mitas Format

The Text format and Log format files that follow were created from the same compressedfile. This is also the same compressed file used in the Orion Format case above.

The Mitas Format is similar to the Orion Format with the following differences:

An extended file header has been added.

Frequencies have been converted to channels.

Additional diagnostic information is provided.

The frequency to channel assignment is as follows:

Freq (Mhz) Channel

150.28 26150.30 0150.32 1150.34 2150.36 3150.38 4150.40 5150.42 6150.44 7150.46 8150.48 9150.50 10150.52 11150.54 12150.56 13150.58 14150.60 15150.62 16150.64 17150.66 18150.68 19

150.70 20150.72 21150.74 22150.76 23



27/31


4.2.1 Text Format

This format contains too many fields to conveniently fit the page the line breaks areadded here but are not present in the original data file.

DataFormat 4SiteID 4SiteName OrionFirstAntenna 1LastAntenna 3SDBFactor 8Date Time Tag Ch Code St An Pow #H T0 T1 T2 #L #HHQ PQ #C IC NFL Cal2004-04-15 09:48:11 CODED 26 25 4 3 -78 4 263 297 981 31 310 0 191 681327 -100 -1282004-04-15 09:48:16 CODED 26 25 4 3 -78 4 273 292 971 34 340 0 191 731309 -100 -128

2004-04-15 09:48:21 CODED 26 25 4 3 -78 4 268 292 972 34 340 0 191 781300 -100 -1282004-04-15 09:48:26 CODED 26 25 4 3 -78 4 268 287 981 34 340 0 191 831287 -100 -1282004-04-15 11:51:32 CODED 4 46 4 3 -107 4 322 273 355 22 226 3 0 175095 -110 -1282004-04-15 11:51:41 CODED 5 247 4 3 -110 4 750 226 385 18 186 8 0 270078 -110 -1282004-04-15 11:51:50 CODED 6 2 4 3 -110 4 207 225 456 9 98 6 0 353360 -110 -1282004-04-15 11:52:03 CODED 7 134 4 3 -110 4 503 264 273 10 106 6 0 489492 -110 -1282004-04-15 11:52:17 CODED 3 162 4 3 -109 4 557 529 1272 10 106 10 0 628494 -110 -128

4.2.2 Log Format

SiteID : 4Antenna : 3

First Data Record : 2004-04-15 09:48:11Last Data Record : 2004-04-15 16:04:00Processed : 2004-04-22 10:00:28

Total Number of Contacts: 975

Total Number of Noise : 4

#Contacts By Channel:+---------+---------+---------+---------+--------- 193

1 *********************************** 1362 ****************** 733 ************************************** 1494 ********************************** 1345 ************************************************** 193



28/31


6 ******************* 777 ************* 528 ***************** 69

26 *********************** 92

#Contacts By Power:+---------+---------+---------+---------+--------- 202

-77 1-78 4-79 1-80 1-83 1-85 1-87 * 5-88 4-89 3-90 * 7-91 * 7-92 4-93 *** 14-94 *** 14-95 ** 10-96 *** 16-97 ***** 24-98 ****** 25-99 ********* 40

-100 ******** 35-101 ******** 33-102 ******** 33-103 ** 9-104 **** 19

-105 ************ 52-106 ************ 49-107 ***************** 70-108 ************************* 104-109 ************************************************** 202-110 ********************************************** 187

#Noise By Channel:+---------+---------+---------+---------+--------- 4

5 ************************************************** 4

#Noise By Power:+---------+---------+---------+---------+--------- 3

-96 ************************************************** 3-97 **************** 1


Year-Mo-Dy-Hr AveNoiseFloor AveNumScans AvePulseQueue2004-04-15-09 -100.0 191.0 N/A



29/31


No Data for 1 hour2004-04-15-11 -110.0 197.5 7.12004-04-15-12 -109.6 198.6 5.52004-04-15-13 -107.2 199.6 6.52004-04-15-14 -105.7 199.4 6.4

2004-04-15-15 -102.3 203.4 3.02004-04-15-16 -102.0 205.4 3.4

4.3 ATS Temp Format

The Text format and Log format files that follow were created from the same compressedfile.

The ATS Temp format is similar to the Orion Format, with the exception that the code

value is replaced by 2 fields: the approximate temperature (~Temp), and the exact timeinterval in ms. The approximate temperate is only approximate in the sense that insteadof applying the actual slope/offset values for the tag being reported, nominal values areused. These nominal values are the ones that were given in the Orion Configuration.

4.3.1 Text Format

Date Time Site Ant Freq ~Temp Interval(ms) Power NFL2004-04-20 15:14:07 1 14 150.535 -1 0 -73 -1002004-04-20 15:14:08 1 14 150.535 23.3 843.5 -73 -1002004-04-20 15:14:10 1 14 150.535 23.3 843.5 -73 -1002004-04-20 15:14:12 1 14 150.535 23.3 843.0 -73 -1002004-04-20 15:14:13 1 14 150.535 23.3 843.6 -73 -1002004-04-20 15:14:15 1 14 150.535 23.3 842.5 -73 -1002004-04-20 15:14:17 1 14 150.535 23.3 842.5 -73 -1002004-04-20 15:14:19 1 14 150.535 23.3 843.0 -73 -1002004-04-20 15:14:20 1 14 150.535 23.3 842.5 -73 -1002004-04-20 15:14:22 1 14 150.535 23.3 843.0 -73 -1002004-04-20 15:14:24 1 14 150.535 23.3 842.4 -73 -1002004-04-20 15:14:25 1 14 150.535 23.3 842.5 -73 -1002004-04-20 15:14:27 1 14 150.535 23.3 843.1 -73 -1002004-04-20 15:14:29 1 14 150.535 23.3 843.0 -73 -100

4.3.2 Log Format

SiteID : 1Antenna : 14

First Data Record : 2004-04-20 15:14:07Last Data Record : 2004-04-20 15:23:25Processed : 2004-04-22 09:13:08



30/31


Total Number of Contacts: 332Total Number of Noise : 1

#Contacts By Freq:

+---------+---------+---------+---------+--------- 332150.535 ************************************************** 332

#Contacts By Power:+---------+---------+---------+---------+--------- 332

-73 ************************************************** 332

#Contacts By ~Temp:+---------+---------+---------+---------+--------- 308

23.3 ************************************************** 30823.4 *** 24

#Noise By Freq:+---------+---------+---------+---------+--------- 1

150.535 ************************************************** 1

#Noise By Power:+---------+---------+---------+---------+--------- 1

-73 ************************************************** 1


Year-Mo-Dy-Hr AveNoiseFloor AveNumScans AvePulseQueue2004-04-20-15 -100.0 181.7 1.0

4.4 Output Fields Used

The following table specifies the meaning of the various output fields in alphabeticalorder.

Label Meaning Unit

#C Scan Rate kscans / 100 seconds#H number of hits per record#L/#H number of samples per contactAn antenna number Ant antenna number Cal calibration offset used dBCh channelCode code



31/31


Date date yyyy-mm-ddFreq frequency MHzHQ hit queue lengthIC relative time on dsp. Counter counts

from 0 to 100 seconds.0.1 ms

Interval (ms) interval between pulses msNFL noise floor used dBmPow average power for contact dBmPower average power for contact dBmPQ pulse queue lengthSite site IDSt site IDT0 first time interval within contact 0.1 msT1 second time interval within contact 0.1 ms

T2 third time interval within contact 0.1 msTag tag type text~Temp approximate temperature for ATS temp

tag. Temperature is approximatebecause only typical calibration valueshave been applied.

degrees C

Time time HH:MM:SS, 24-hour format.

5 Known Limitations

OrionTool will only run properly under Win2000 or better.

Orion has been observed to operate poorly when powered by a wall charger thatwas getting AC power from an inverter.

The size of the MMC cards is determined automatically by Orion. This capabilityhas only been tested with 32, 64, and 128 MB cards.

As of version 2.061, the global feature in the Orion Configuration is notoperating properly and may lead to application crashes. The global feature shouldnot be used at present.

For reading data from MMC cards, an MMC reader is adequate. However, for uploading new firmware to an MMC card, or for erasing an MMC card, an MMCreader/writer is required.

For Serial communications, a NULL modem serial cable is required.

Tag type selection is mutually exclusive. Although the user interface implied thatyou can select multiple tag types, you cannot.

Orion Users Guide-v2.061

Documents

Transcript of Orion Users Guide-v2.061