GitHub/sdrtrunk
1
0
Fork 0
mirror of https://github.com/DSheirer/sdrtrunk.git synced 2026-11-09 15:17:24 -05:00
Code Issues Packages Projects Releases 2 Wiki Activity

Migrating wiki contents from Google Code

Browse Source
This commit is contained in:
Google Code Exporter
2015-08-24 20:49:54 -04:00
commit 096f5678b1
47 changed files with 1228 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
.project Normal file
View File

@@ -0,0 +1,11 @@
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>sdrtrunk wiki</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
</buildSpec>
<natures>
</natures>
</projectDescription>

52
APCO25.md Normal file
View File

@@ -0,0 +1,52 @@
# APCO-25 Decoder #
The APCO-25 decoder will decoder P-25 phase I signals that are using either
C4FM modulation or LSM Simulcast (CQPSK) modulation. It will process trunked,
conventional and packet data messages.
## Audio Vocoder ##
APCO-25 Phase-1 audio calls use the multi-band excitation model vocoder to
compress the digitized audio. SDRTrunk supports the JMBE library for decoding
audio, but DOES NOT include the jmbe library in the normal application download.
You must download and compile the library and place the jmbe-x.x.x.jar file in
the same directory from where you launch the sdrtrunk application. On startup,
sdrtrunk will attempt to discover the library and can then decode imbe audio.
[JMBE library](https://github.com/DSheirer/jmbe)
[How To Setup JMBE](JMBE.md)
## Traffic Channel Following ##
The decoder currently does not automatically follow trunked traffic channels.
This feature is planned for a future release
![http://sdrtrunk.googlecode.com/svn/wiki/images/P25_Decoding.png](http://sdrtrunk.googlecode.com/svn/wiki/images/P25_Decoding.png)
## Talkgroups and Addresses ##
All talkgroups and radio addresses are listed in hexadecimal (base-16) notation
and use the digits 0 - 9 and the letters A - F. Talkgroups are four characters
in length and radio addresses are six characters in length.
Packet data IP Version 4 addresses will normally show in the from column of the
events window and the Logical Link ID (radio address) will show in the from
column with the radio's IP Version 4 address listed in the details column. If
the data contains UDP over IP protocol, the UDP source and destination ports
will be appended to the IP address.
## Aliases ##
You can create an Alias List and attach it to your P25 decoder in the channel
configuration window.
When aliasing talkgroups and radio addresses, ensure you include the full 4 or 6
character talkgroup or address with leading zeros.
## Modulation ##
Choose either C4FM or LSM Simulcast (CQPSK) modulation in the channel configuration
decoder tab. When you select the P25 Decoder from the drop-down list, the
modulation selector list will appear.
![http://sdrtrunk.googlecode.com/svn/wiki/images/P25_Decoding_2.png](http://sdrtrunk.googlecode.com/svn/wiki/images/P25_Decoding_2.png)

13
ActivitySummary.md Normal file
View File

@@ -0,0 +1,13 @@
# Activity Summary #
The activity summary window displays a summary of information about network, frequency, call and user activity received. The format of the activity summary is different for each decoder.
If you are using [auxiliary decoders](AuxiliaryDecoder.md), then the activity summary for each of those auxiliary decoders is included at the end of the primary decoder activity summary.
## Accessing Activity Summary ##
The activity summary window can be accessed from any of the channel context menus
* **[Configuration](Configuration.md)** - right-click on a currently decoding channel in the configuration tree
* **[Decoding Channels](DecodingChannels.md)** - right-click on a channel
* **[Spectral Display](SpectralDisplay.md)** - right click on a currently decoding channel overlay

80
Alias.md Normal file
View File

@@ -0,0 +1,80 @@
# Alias #
An alias is a user readable name that can be associated with one or more identifiers produced by the decoders.
![http://sdrtrunk.googlecode.com/svn/wiki/images/Alias.png](http://sdrtrunk.googlecode.com/svn/wiki/images/Alias.png)
## Creating an Alias ##
Right-click on the Alias Group folder and select **New Alias**.
## Deleting an Alias ##
Right-click on the Alias and select **Delete**
## Configuring an Alias ##
* **Name** - display name for the alias
* **Map Color** - for decoders that produce (GPS) locations where the entity can be plotted on the map, designates the color of the label and history trail used for that entity
* **Map Icon** - picture to display with the alias
* **[Icon Manager](IconManager.md)** - tool for managing and importing new pictures to use with Aliases.
* **Save** - saves any changes to the alias
* **Reset** - resets the alias with the last saved values
## Alias Identifiers ##
Each message and event produced by the decoders contains user and system identifiers that can be aliased. Each alias can be associated with one or more alias identifiers.
### Alias Identifier Wildcards ###
Each of the alias identifiers (except LTR-Net unique ID and Status) allow you to specify a single character wildcard (asterisk) or a full java regular expression to use when matching identifiers.
Examples:
```
0-**-123 LTR talkgroup 123 on any LCN
ABCD12** Any electronic serial numbers beginning with ABCD12
(?!FA-40|FA-41|FA-42).* Any lojack site ID except for FA-40, FA-41, or FA-42 (use '|' to separate each site identifier)
```
### Create an Alias Identifier ###
Right-click on the Alias folder and select the type of alias identifer you want to associate with the Alias.
### Delete an Alias Identifier ###
Right-click on the Alias identifier and select **Delete**.
## Alias Identifier Types ##
* **ESN** - electronic serial number.
![http://sdrtrunk.googlecode.com/svn/wiki/images/AliasESNID.png](http://sdrtrunk.googlecode.com/svn/wiki/images/AliasESNID.png)
* **Fleetsync** - fleetsync identifier.
![http://sdrtrunk.googlecode.com/svn/wiki/images/AliasFleetsyncID.png](http://sdrtrunk.googlecode.com/svn/wiki/images/AliasFleetsyncID.png)
* **MDC-1200** - MDC-1200 identifier.
![http://sdrtrunk.googlecode.com/svn/wiki/images/AliasMDC1200ID.png](http://sdrtrunk.googlecode.com/svn/wiki/images/AliasMDC1200ID.png)
* **MIN** - passport radio Mobile ID Number (MIN).
![http://sdrtrunk.googlecode.com/svn/wiki/images/AliasMIDID.png](http://sdrtrunk.googlecode.com/svn/wiki/images/AliasMIDID.png)
* **MPT-1327** - MPT-1327 user or group identifier.
![http://sdrtrunk.googlecode.com/svn/wiki/images/AliasMPT1327ID.png](http://sdrtrunk.googlecode.com/svn/wiki/images/AliasMPT1327ID.png)
* **Site** - site number.
![http://sdrtrunk.googlecode.com/svn/wiki/images/AliasSiteID.png](http://sdrtrunk.googlecode.com/svn/wiki/images/AliasSiteID.png)
* **Talkgroup** - used with LTR and Passport talkgroups. **TGID** identifies the formatted talkgroup. **Audio** identifies how the audio from a call for this talkgroup should be handled : _Normal, Muted, or Inverted_.
![http://sdrtrunk.googlecode.com/svn/wiki/images/AliasTalkgroupID.png](http://sdrtrunk.googlecode.com/svn/wiki/images/AliasTalkgroupID.png)
* **Unique ID** - LTR-Net mobile radio unique ID (UID).
![http://sdrtrunk.googlecode.com/svn/wiki/images/AliasUniqueID.png](http://sdrtrunk.googlecode.com/svn/wiki/images/AliasUniqueID.png)

48
AliasAction.md Normal file
View File

@@ -0,0 +1,48 @@
# Alias Action #
You can assign one or more alias actions to an alias that will be executed when the alias becomes active in a decoded message. Each message type can produce one or more aliases against any of the identifiers in the message that can be associated with an alias.
## Interval ##
Interval defines when and how often the action will occur.
**Once** - the action will only occur once when the alias is first active for the duration that sdrtrunk is running.
**Once, Reset After Delay** - the action will occur when the alias is first active, but will suppress any further actions for a specified number of seconds. Once the delay period has elapsed, this action will again alert in the future if the alias is active.
**Until Dismissed** - the action will occur when the alias is first noted active and will continue to occur every specified number of seconds. A dialog window with an OK button will pop up and the action will repeat until the user clicks the OK button. The action will reset 15 seconds after the OK button is pressed and will alert again in the future if the alias is active.
## Period ##
Specifies the time period in seconds for the two interval options that require a time period setting.
# Available Alias Actions #
![http://sdrtrunk.googlecode.com/svn/wiki/images/AliasActions.png](http://sdrtrunk.googlecode.com/svn/wiki/images/AliasActions.png)
## Audio Clip ##
Plays the audio clip specified by the file name. The audio clip action provides a file selection button and a test button to allow you to play the selected audio file to ensure that the file is a supported audio type.
## Beep ##
Beeps the computer
## Script ##
The script action allows you to select a script, batch file, or program to execute when the action occurs. Select the program from the File button and use the Test button to test the script to ensure that the script operates correctly.
![http://sdrtrunk.googlecode.com/svn/wiki/images/ScriptAction.png](http://sdrtrunk.googlecode.com/svn/wiki/images/ScriptAction.png)
# Errors #
If any errors are encountered playing an audio clip or executing a script, a popup window will appear providing details on the error.
# How To Assign An Alias Action #
* Right-click on an alias
* Select the Add Action menu and choose from the list of available actions
* Ensure the newly added alias action is highlighted in the tree
* Configure the interval and period settings
* Optionally select a file and test the action against the file
* Click the Save button at the bottom of the configuration window

13
AliasGroup.md Normal file
View File

@@ -0,0 +1,13 @@
# Alias Group #
Contains a list of [Aliases](Alias.md) used by the decoder to assign an alias name to one or more identifiers produced by the decoder. Use alias groups to arrange each set of user aliases into groups on a system.
![http://sdrtrunk.googlecode.com/svn/wiki/images/AliasGroup.png](http://sdrtrunk.googlecode.com/svn/wiki/images/AliasGroup.png)
## Creating an Alias Group ##
Right-click on the Alias List folder and select **New Group**.
## Deleting an Alias Group ##
Right-click on the Alias Group and select **Delete**

13
AliasList.md Normal file
View File

@@ -0,0 +1,13 @@
# Alias List #
Contains a list of [Alias Groups](AliasGroup.md) and [Aliases](Alias.md) used by the decoder to assign an alias name to one or more identifiers produced by the decoder.
![http://sdrtrunk.googlecode.com/svn/wiki/images/AliasList.png](http://sdrtrunk.googlecode.com/svn/wiki/images/AliasList.png)
## Creating an Alias List ##
Right-click on the Alias Lists folder and select **New Alias List**.
## Deleting an Alias List ##
Right-click on the Alias List and select **Delete**

19
ApplicationLog.md Normal file
View File

@@ -0,0 +1,19 @@
# Application Log #
The application log contains logging information about the application. Note: see [EventLog](EventLog.md) for details about logging of decoded channel messages.
# Location #
**Windows 7**:
c:\Users\(your username)\sdrtrunk\log\
---
**Linux**:
In your user directory:
~\sdrtrunk\log

9
ApplicationOverview.md Normal file
View File

@@ -0,0 +1,9 @@
### Application Overview ###
![http://sdrtrunk.googlecode.com/svn/wiki/images/Overview.png](http://sdrtrunk.googlecode.com/svn/wiki/images/Overview.png)
* **[Spectral Display](SpectralDisplay.md)**
* **[Waterfall Display](WaterfallDisplay.md)**
* **[Decoding Channels](DecodingChannels.md)**
* **[Configuration](Configuration.md)
***[Editor](Editor.md)*****[Calls](CallEvents.md)*****[Messages](Messages.md)*****[Map](Map.md)

5
B100.md Normal file
View File

@@ -0,0 +1,5 @@
# Ettus Research B100 with WBX Daughter Card #
Coming soon.
https://www.ettus.com/product/details/UB100D-BDL

28
Building.md Normal file
View File

@@ -0,0 +1,28 @@
# Downloading and Compiling sdrtrunk #
This page describes several methods for checking out the source code from the SVN server and building the sdrtrunk application on your local computer.
## Eclipse IDE ##
If you use the [Eclipse IDE for Java](http://www.eclipse.org/downloads/), you can download and import the sdrtrunk project directly into Eclipse.
1. Install an eclipse svn plugin ( Help > Install New Software, choose the Luna site, Collaboration > Subversive SVN )
1. Project Explorer > Import > SVN > Project from SVN
1. Create a new repository location: https://sdrtrunk.googlecode.com/svn
> or http://sdrtrunk.googlecode.com/svn/trunk/
1. Open the ant view ( Window > Show View > Ant )
1. Drag the ant build script from the Package Explorer (sdrtrunk/build/build.xml) into the ant view panel
1. Click the play button to execute the default build target
1. Compiled software package is placed in the sdrtrunk/product/xxx.zip folder
## Manually ##
1. Install the Java JDK version 1.7 or higher and create a JAVA\_HOME environment variable pointing to the JDK installation folder
1. Install an SVN client on your computer: [Tortoise SVN](http://tortoisesvn.net/downloads.html) on windows or kdesvn on Linux
1. Checkout the source code from https://sdrtrunk.googlecode.com/svn
> or http://sdrtrunk.googlecode.com/svn/trunk/
1. Install the latest version of [Ant](http://ant.apache.org/) and follow the installation instructions in the [manual](http://ant.apache.org/manual/index.html)
1. Change to the sdrtrunk build directory ( sdrtrunk/build )
1. Execute the ant command.
Ant will look for a file named build.xml in the current folder and will run the the default build target. The compiled and zipped output program file will be located in the sdrtrunk/product/xxx.zip folder.

36
CallEvents.md Normal file
View File

@@ -0,0 +1,36 @@
# Call Events #
The call events window displays a history of the radio calls decoded for a channel. Select a channel in the [decoding channels](DecodingChannels.md) window to display the call event history for that channel.
Note: call events continue to be displayed for the last selected channel, allowing you to select and then deselect a channel in order to turn off the audio for that channel and continue to see all call events.
![http://sdrtrunk.googlecode.com/svn/wiki/images/CallEvents.png](http://sdrtrunk.googlecode.com/svn/wiki/images/CallEvents.png)
## Call Event Table Details ##
* **Time** - time that the event occurred
* **Event** - call event description
* **From** - identifier of the radio that initiated the call
* **From Alias** - alias label of the from entity
* **To** - identifier of the radio or talkgroup receiving the call
* **To Alias** - alias label of the to entity
* **Channel** - channel number for the event
* **Frequency** - frequency of the channel number
* **Details** - minimal additional details for the call event
## Call Events ##
* **Acknowledge** - acknowledgement from a radio
* **ANI** - automatic number identification for a radio
* **Call Detect** - a call detected on another channel
* **Call End** - call end event
* **Call Start** - call start
* **Call - No Tuner** - call start event when no tuner is available
* **Call Timeout** - call end event was not received and call expire timer forced a timeout on the call event
* **Emergency** - emergency notification from a radio
* **ESN** - radio registering on the network with an ESN, or responding to an ESN interrogation
* **GPS** - gps update from a radio
* **Unique ID** - LTR-Net unique identifier for a radio
* **Page** - the system is paging a radio
* **Register** - radio registering on the network
* **SDM** - short data message
* **Status** - status message

67
Channel.md Normal file
View File

@@ -0,0 +1,67 @@
# Channel #
A channel defines all of the configuration details needed for to setup a radio channel for decoding. When a [Channel](Channel.md) is actively decoding, the system icon is colored Green. If there is no source available, the channel icon turns red.
![http://sdrtrunk.googlecode.com/svn/wiki/images/Channel.png](http://sdrtrunk.googlecode.com/svn/wiki/images/Channel.png)
## Creating a New Channel ##
Right-click on a [Site](Site.md) folder and select 'New Channel'.
## Deleting a Channel ##
Right-click on the [Channel](Channel.md) and select 'Delete'
## Starting/Stopping Channel Decoding ##
Use the Enabled check box in the channel configuration to turn decoding on or off. Once you save the configuration, the channel will automatically start decoding, if enabled.
**Quick Start** - right-click on the channel in the configuration window, or right-click on the channel in the spectral display and selected 'Enable' or 'Disable' to turn the decoder on or off with one click.
## Channel Configuration ##
* **Enabled** - turns the channel on/off for decoding.
* **Name** - name for the channel
* **Aliases** - assigns an AliasList to the channel so that any identifiers produced by the decoder can have an [Alias](Alias.md) value.
* **Source Tab** - designates the source for raw sampled data to feed the decoder
* **Decoder Tab** - designates the primary decoder to use for this channel
* **Aux Tab** - identifies additional auxiliary decoders to use in addition to the primary decoder
* **Event Log Tab** - logging options for decoded events
* **Record Tab** - recording options
### Source Tab ###
The source tab allows you to specify the source for raw sampled data to feed the primary and auxiliary decoders.
* **No Source** - this is the default source when a new channel is created. You cannot decode a channel with this source.
* **Mixer/Sound Card** - allows you to use an external radio scanner with the audio output or discriminator tapped audio from the scanner patched to a sound card input on the computer. Select the Mixer (Sound Card) and Channel for the sound card where you have the scanner audio patched.
* **Tuner** - allows you to specify a radio frequency as the source for raw samples. You must have a [Tuner](Tuner.md) attached to your computer and it must appear in the list of [Tuners](Tuners.md) in the SDRTrunk [Configuration](Configuration.md) window. If no tuners are attached, or if none of the attached tuners can tune the requested frequency, the channel will indicated 'No Tuner' when you enable it.
### Decoder Tab ###
The decoder tab provides a list of available primary decoders to select for the channel. Only one primary decoder can be selected per channel. If you want to run multiple primary decoders, create additional channels, each with a different primary decoder.
* **[LTR-Standard](LTR.md)** - FM demodulator and Logic Trunked Radio (LTR) trunked radio signaling decoder
* **[LTR-Net](LTRNet.md)** - FM demodulator and LTR-Net trunked radio signaling decoder
* **[MPT-1327](MPT1327.md)** - FM demodulator and MPT-1327 trunked radio signaling decoder. Provides automatic traffic channel following.
* **[NBFM](NBFM.md)** - narrow-band FM demodulator.
* **[Passport](Passport.md)** - FM demodulator and Passport trunked radio signaling decoder.
## Aux Tab ##
The aux tab allows you to select from multiple auxiliary decoders to use in addition to the selected primary decoder. Auxiliary decoders are used to decode pass-band audio signals like gps and digital radio identification bursts that are used on some trunked and conventional radio systems.
* **[Fleetsync II](Fleetsync2Decoder.md)** - decodes ANI, Acknowledge, Status, Paging and GPS bursts
* **[MDC-1200](MDC1200Decoder.md) - decodes MDC-1200 ANI bursts.**
### Event Log Tab ###
The event log tab allows you to select from multiple textual logging options.
* **Binary Messages** - logs raw binary messages created by the decoder. Each message contains a timestamp, protocol, and a string of binary ones and zeros.
* **Decoded Messages** - logs decoded textual messages created by the decoder.
* **Call Events** - logs all of the call events that can be seen in the [Calls](CallEvents.md) window.
### Record Tab ###
The record tab provides options for recording of the demodulated/decoded audio and/or the raw I/Q samples from a tuner or complex mixer source.
* **Audio** - records all demodulated audio, uninterrupted and without squelch control in a wave file.
* **Baseband I/Q** - records all raw baseband sample data in a two-channel, 16-bits per sample wave file.

35
ChannelMap.md Normal file
View File

@@ -0,0 +1,35 @@
# Introduction #
Channel Maps are used by some decoders to specify the channel number to frequency mapping used by a system. Most decoders do not require a channel map. Channel Maps allow the trunking controller to tell a mobile radio to go to a channel number for a radio call, without having to specify the frequency. An accurate channel map is essential for decoders that support traffic channel following, so that SDRTrunk can tune to the correct traffic channel frequency to decode the traffic channel call.
![http://sdrtrunk.googlecode.com/svn/wiki/images/ChannelMap.png](http://sdrtrunk.googlecode.com/svn/wiki/images/ChannelMap.png)
## Create a Channel Map ##
Right-click on the Channel Maps folder and selected **New Channel Map**
## Delete a Channel Map ##
Right-click on the Channel Map and select **Delete**
## Channel Ranges ##
A channel map contains one or more channel ranges. A range defines a range of channel numbers, the base frequency, and the channel size. A simple math formula produces the channel frequency by multiplying the channel number by the channel size, and adding that value to the base frequency. A channel map can contain multiple channel ranges to support systems where the channel frequencies are not allocated in a contiguous manner.
### Add a Channel Range ###
Click 'New Range'.
### Delete a Channel Range ###
Highlight the range and click 'Delete'
## Configuring a Channel Map ##
* **Name** - Update the name for your channel map. Once you have finished updating the channel map, you can then select this name in the channel's decoder configuration tab.
* **Range** - update the default channel range in the table with beginning and ending channel numbers, base frequency, and channel size. Use the **New Range** button to add additional channel ranges to the channel map. Use the **Delete** button to delete any channel ranges that aren't needed.
* **Save** - saves the current configuration.
* **Reset** - resets the channel map to the last saved state

8
Configuration.md Normal file
View File

@@ -0,0 +1,8 @@
# Configuration #
The configuration window uses a tree list to provide access to all of the configurable features and settings in the SDRTrunk application.
* [Tuners](Tuner.md)
* [Playlist](Playlist.md)
![http://sdrtrunk.googlecode.com/svn/wiki/images/Configuration.png](http://sdrtrunk.googlecode.com/svn/wiki/images/Configuration.png)

15
DecodingChannels.md Normal file
View File

@@ -0,0 +1,15 @@
# Decoding Channels #
The decoding channels window displays a list containing the [channel state](ChannelState.md) for each of the channels that are currently enabled for decoding.
## Listening to Decoded Audio ##
Each channel's audio output can be toggled by selecting that channel. The currently selected channel is highlighted. When available, each decoder uses trunking signalling messages to determine when to squelch or unsquelch the currently selected channel.
## Context Menus ##
Right-click on any of the listed channels to see a list of context-sensitive menus applicable to each channel.
* **Disable** - turns off decoding for this channel
* **[Activity Summary](ActivitySummary.md)** - displays a current activity summary for the channel
* **Delete** - disables and deletes the channel. _Note: this action completely removes the channel from the [playlist](Playlist.md)_

42
E4000.md Normal file
View File

@@ -0,0 +1,42 @@
# Elonics E4000 #
http://www.nooelec.com/store/sdr/sdr-receivers.html
![http://sdrtrunk.googlecode.com/svn/wiki/images/E4000.png](http://sdrtrunk.googlecode.com/svn/wiki/images/E4000.png)
## Tuner Configurations ##
SDRTrunk allows you to define multiple named tuner configurations per tuner type. A **Default** configuration is automatically created the first time you use each specific tuner type and will be recreated again if you accidentally delete or rename the **Default** configuration.
SDRTrunk uses the serial number from the E4000 that can be set using the rtl\_eeprom utility, so automatically associate a named tuner configuration with the E4000 dongle, regardless of which USB port is used.
All changes to a named configuration are automatically saved.
## Configuration ##
* **Frequency** - sets the tuned frequency
* **Configuration Tab** - controls for changing tuner configuration
* **Info Tab** - displays information about the tuner
### Configuration Tab ###
* **Config** - selects a named configuration to use. Automatically applies the corresponding settings to the tuner
* **Name** - tuner configuration name.
* **Correction PPM** - correction value to align the currently tuned frequency with the frequency display values. Increasing the value causes the frequency display to move to the left and vice-versa.
* **Sample Rate** - sets the sample rate to use for the tuner.
* **Master Gain** - sets the overall gain for the tuner and automatically controls the individual gain controls. Use the **Manual** setting to enable and independently change the LNA, Mixer and Enhance gain controls
* **LNA Gain** - sets the LNA gain. Place the Master Gain into **Manual** mode to enable this control.
* **Mixer Gain** - sets the Mixer gain. Place the Master Gain into **Manual** mode to enable this control.
* **Enhance Gain** - sets the Enhance gain. Place the Master Gain into **Manual** mode to enable this control.
* **New** - creates a new named tuner configuration
* **Delete** - deletes the currently listed tuner configuration
### Info Tab ###
The info tab displays information about the tuner:
* **USB ID** - USB vendor and product identifiers.
* **Vendor** - vendor name from EEPROM
* **Product** - product label from EEPROM
* **Serial** - serial label from EEPROM
* **IR Enabled** - IR enabled setting from EEPROM
* **Remote Wake** - remote wake setting from EEPROM

5
Editor.md Normal file
View File

@@ -0,0 +1,5 @@
# Editor #
[Configuration](Configuration.md) details for each node in the [configuration](Configuration.md) tree is displayed in the editor window when you select the node in the configuration tree window.
Use the editor window to update configuration details and then choose **Save** to save the updates or **Reset** to restore the settings to the last saved version.

21
EventLogger.md Normal file
View File

@@ -0,0 +1,21 @@
# Event Log #
The event log contains logging information about decoded messages from one of the decoder channels. Each channel will generate a log file that starts with a time stamp and ends with the channel name and a .log suffix.
Note: see [ApplicationLog](ApplicationLog.md) for details about logging of application information.
# Location #
**Windows 7**:
c:\Users\(your username)\SDRtrunk\event\_logs\
---
**Linux**:
In your user directory:
~\SDRtrunk\event\_logs

5
FC0013.md Normal file
View File

@@ -0,0 +1,5 @@
# RTL-2832 with Fitipower FC0013 Tuner #
Coming soon.
http://www.nooelec.com/store/sdr/sdr-receivers.

29
Fleetsync2.md Normal file
View File

@@ -0,0 +1,29 @@
# Fleetsync II Decoder #
Fleetsync is a digital radio identifier, status, GPS, and data protocol that is normally used in addition to other trunked radio protocols and/or on conventional radio channels. The decoder decodes Automatic Number Identification (ANI), Acknowledgements, Status and GPS messages. If you discover additional message types, please share them with the author for inclusion in the decoder.
## Using Fleetsync Decoder ##
Select the Fleetsync decoder in the **Aux** tab of the channel configuration window. If you are decoding a conventional channel, then use the [NBFM](NBFM.md) decoder as the primary decoder. The Fleetsync auxiliary decoder can be used in addition to any of the primary analog trunked radio decoders.
## GPS ##
GPS data bursts normally occur on a conventional radio channel, separate from normal voice communications. Each mobile radio has a unique timestamp that tells it when to broadcast, so that users don't broadcast on top of each other. In addition to the defined time to transmit, radios are told how often to broadcast. Broadcast updates of 1, 3, 5 and 6 minute intervals have been observed.
Smaller fleets may broadcast more often. Larger fleets will broadcast less often, because each radio must have an opportunity to broadcast at least once within the repeat interval.
## Status ##
Mobile radios are programmed with a pre-defined list of canned status messages. The decoder will display the status number received. If you can determine the meaning of each status number, you can alias the status number with a status alias identifier so that the meaning is displayed, instead of the status number.
## Acknowledge ##
Some radio networks will acknowledge status messages. When this happens, the mobile radio will broadcast a status message, and the network will immediately respond with an acknowledgement.
## Aliases ##
Add the following aliases to each alias list you are using for Fleetsync:
* 099-0999 Broadcast Call
* `*``*``*`-0999 Fleet Call
* 099-`*``*``*``*` Supervisor Call

42
FuncubeDonglePro.md Normal file
View File

@@ -0,0 +1,42 @@
# Funcube Dongle Pro Tuner #
![http://sdrtrunk.googlecode.com/svn/wiki/images/FuncubeDonglePro.png](http://sdrtrunk.googlecode.com/svn/wiki/images/FuncubeDonglePro.png)
## Tuner Configurations ##
SDRTrunk allows you to define multiple named tuner configurations per tuner type. A **Default** configuration is automatically created the first time you use each specific tuner type and will be recreated again if you accidentally delete or rename the **Default** configuration.
Each time you plug your USB tuner into a new USB port, it will automatically use the **Default** tuner configuration. If you select a different named configuration, SDRTrunk will remember to use that named configuration each time you use the USB tuner in that specific USB port. If you create a named configuration for your tuner and subsequently move the tuner to a different USB port, simply select that named configuration from the drop-down list and it will store that port to named configuration setting.
All changes to a named configuration are automatically saved.
## Configuration ##
* **Frequency** - sets the tuned frequency
* **Configuration Tab** - controls for changing tuner configuration
* **Info Tab** - displays information about the tuner
### Configuration Tab ###
* **Configuration Selection List** - selects a named configuration to use. Automatically applies the corresponding settings to the tuner
* **Name** - tuner configuration name.
* **Correction Tab - Frequency PPM** - correction value to align the currently tuned frequency with the frequency display values. Increasing the value causes the frequency display to move to the left and vice-versa.
* **Correction Tab - DC Inphase** - corrects for DC offset in the Inphase component
* **Correction Tab - DC Quadrature** - corrects for DC offset in the Quadrature component
* **Correction Tab - Gain** - corrects for Gain
* **Correction Tab - Phase** - corrects for Phase
* **Gain Tab - LNA** - LNA gain setting
* **Gain Tab - LNA Enahance** - LNA enhance gain setting
* **Gain Tab - Mixer** - Mixer gain setting
* **New** - creates a new named tuner configuration
* **Delete** - deletes the currently listed tuner configuration
### Info Tab ###
The info tab displays information about the tuner:
* **USB Address** - current USB bus and device port, and USB vendor and product identifiers.
* **Cellular Band** - indicates if the cellular band is blocked or unblocked for this tuner
* **Firmware** - firmware revision
Note: firmware on the http://www.funcubedongle.com/?page_id=313 website is identified by a major revision and letter. Convert the listed firmware minor revision number to a letter to identify the correct firmware revision on the funcube website. For example, firmware **18.10** is listed as **18j** on the funcube website.

34
FuncubeDongleProPlus.md Normal file
View File

@@ -0,0 +1,34 @@
# Funcube Dongle Pro Plus Tuner #
![http://sdrtrunk.googlecode.com/svn/wiki/images/FuncubeDongleProPlus.png](http://sdrtrunk.googlecode.com/svn/wiki/images/FuncubeDongleProPlus.png)
## Tuner Configurations ##
SDRTrunk allows you to define multiple named tuner configurations per tuner type. A **Default** configuration is automatically created the first time you use each specific tuner type and will be recreated again if you accidentally delete or rename the **Default** configuration.
Each time you plug your USB tuner into a new USB port, it will automatically use the **Default** tuner configuration. If you select a different named configuration, SDRTrunk will remember to use that named configuration each time you use the USB tuner in that specific USB port. If you create a named configuration for your tuner and subsequently move the tuner to a different USB port, simply select that named configuration from the drop-down list and it will store that port to named configuration setting.
All changes to a named configuration are automatically saved.
## Configuration ##
* **Frequency** - sets the tuned frequency
* **Configuration Tab** - controls for changing tuner configuration
* **Info Tab** - displays information about the tuner
### Configuration Tab ###
* **Config** - list of named configurations. Automatically applies the corresponding settings to the tuner
* **Name** - tuner configuration name.
* **Correction PPM** - correction value to align the currently tuned frequency with the frequency display values. Increasing the value causes the frequency display to move to the left and vice-versa.
* **LNA Gain** - LNA gain setting
* **Mixer Gain** - Mixer gain setting
* **New** - creates a new named tuner configuration
* **Delete** - deletes the currently listed tuner configuration
### Info Tab ###
The info tab displays information about the tuner:
* **USB Address** - current USB bus and device port, and USB vendor and product identifiers.
* **Cellular Band** - indicates if the cellular band is blocked or unblocked for this tuner
* **Firmware** - firmware revision

37
GettingStarted.md Normal file
View File

@@ -0,0 +1,37 @@
## Getting started with SDRTRunk ##
### Setup ###
* **[Linux](SetupLinux.md)**
* **[Windows](SetupWindows.md)**
![http://sdrtrunk.googlecode.com/svn/wiki/images/Overview.png](http://sdrtrunk.googlecode.com/svn/wiki/images/Overview.png)
[Application Overview](ApplicationOverview.md)
### Quick Start - SDR Dongle ###
1. Select a tuner to display in the spectral display
2. Tune to a frequency near the channel that you want to decode. Do not tune
the channel into the center of the display. Adjust the frequency so that the
channel is either to the left or to the right of the center of the display.
3. Right-click on the frequency in the spectral display, choose **Add Decoder**
select the type of decoder that you want to use.
4. If a tuner is available, the channel will immediately start decoding with
default settings. Select the channel in the **Decoding Channels** window to see
call events and decoded messages.
### Quick Start - Sound Card / Scanner Audio ###
1. Create a new [channel](Channel.md)
2. In the channel editor select the correct **Mixer** and **Channel** in the source tab, corresponding to where you have patched your scanner audio into the computer.
3. Select **Enabled**
4. Hit **Save**.
5. Select the channel in the [decoding channels](DecodingChannels.md) window to hear the pass-through audio.

87
HackRF.md Normal file
View File

@@ -0,0 +1,87 @@
# HackRF #
![http://sdrtrunk.googlecode.com/svn/wiki/images/HackRF.png](http://sdrtrunk.googlecode.com/svn/wiki/images/HackRF.png)
## Tuner Configurations ##
SDRTrunk allows you to define multiple named tuner configurations per tuner
type. A **Default** configuration is automatically created the first time you
use each specific tuner type and will be recreated again if you accidentally
delete or rename the **Default** configuration.
Each time you plug your USB tuner into a new USB port, it will automatically
use the **Default** tuner configuration. If you select a different named
configuration, SDRTrunk will remember to use that named configuration each time
you use the USB tuner in that specific USB port. If you create a named
configuration for your tuner and subsequently move the tuner to a different
USB port, simply select that named configuration from the drop-down list and it
will store that port to named configuration setting.
All changes to a named configuration are automatically saved.
## Configuration ##
* **Frequency** - sets the tuned frequency
* **Config Tab** - controls for changing tuner configuration
* **Info Tab** - displays information about the tuner
### Configuration Tab ###
* **Configuration Selection List** - selects a named configuration to use. Automatically applies the corresponding settings to the tuner
* **Name** - tuner configuration name.
* **Correction PPM** - correction value to align the currently tuned frequency with the frequency display values. Increasing the value causes the frequency display to move to the left and vice-versa.
* **Sample Rate** - sampling rate of the tuner - corresponds to the visible/tunable bandwidth
* **Gain - Amp** - turns the amplifier on/off
* **Gain - LNA** - gain settings for the Low Noise Amplifier
* **Gain - VGA** - gain settings for the Variable Gain Amplifier
* **New** - creates a new named tuner configuration
* **Delete** - deletes the currently listed tuner configuration
### Info Tab ###
The info tab displays information about the tuner:
* **Serial** - serial number of the HackRF board.
* **Part** - part number
* **Firmware** - firmware revision
## Using the HackRF ##
One of the most important settings on the HackRF are the gain settings. The
gain settings affect each portion of the radio spectrum differently, so you
need to adjust the gain each time you move to a different part of the frequency
spectrum.
Strong nearby signals easily overload the HackRF. If the spectral display
rises significantly, or if you notice the spectral display jumping up and down,
this is an indication that you have overloaded the tuner. Another symptom of
overload is spectral mirroring, where the left and right side look identical.
Broadcast FM radio stations overload the tuner and you may or may not be able
to set the gain low enough to visualize the entire FM band.
Note: on startup if you have previously used a high sample rate, you may notice
lagging/stalling in the application. Change the sample rate to a lower sample
rate until the application stabilizes, and then select the desired sample rate.
### Setting Gain ###
* Set the frequency, or enable a channel and the tuner will automatically
> adjust the frequency.
* Turn the amplifier off and set LNA and VGA gain to 0.
* Slowly adjust the LNA gain higher until you see the spectral display rise
> significantly high or start to jump. Back off the gain setting until the
> display settles down.
* Repeat this step for the VGA gain setting.
* Experiment with the Amp button to turn the amplifier on or off.
If you have a strong nearby signal that is close in frequency to the channel
that you want to decode, attempt to tune the strong signal up or down, so that
it is no longer in the viewable passband of the tuner.
## Updating Firmware ##
The firmware label shown on the Info tab is the GIT revision label that was
tagged against the software release. SDRTrunk does not currently support
flashing the HackRF with new firmware. Use the HackRF tools to update the
tuner.

38
JMBE.md Normal file
View File

@@ -0,0 +1,38 @@
# JMBE Library #
The Java Multi-Band Excitation (JMBE) library provides decoder support for converting IMBE encoded audio frames to normal audio so that you can listen to the audio calls over your computer speakers.
Website: [JMBE](https://github.com/DSheirer/jmbe)
## Patent Warning ##
The JMBE library contains source code that may be patent protected. Users
should check local laws before downloading, compiling, using, or DISTRIBUTING
compiled versions of the JMBE library.
## Copyright Notice ##
Copyrights for the terms MBE and IMBE are the property of their respective
owners.
## Adding JMBE to SDRTrunk for decoding MBE audio ##
# Download the **jmbe\_builder.zip** (windows) or the **jmbe\_builder.tar.gz** (linux) file to your computer and uncompress the file. These files are available in the [Download](https://drive.google.com/folderview?id=0B7BHsssXUq8eOHBTNndCczZTd0k&usp=sharing) folder
# Run the **make\_jmbe\_library\_windows.bat** (windows) or the **make\_jmbe\_library\_linux.sh** (linux) file. This will download the source code and create the **jmbe-x.x.x.jar** file. The file that gets created will have version numbers in place of the x's in the filename.
# Copy the **jmbe-x.x.x.jar** file to the same folder where you run the sdrtrunk scripts to start the sdrtrunk program.
# Start SDRTrunk normally and the program will automatically discover and use the jmbe library.
## Troubleshooting ##
If you download, compile and copy the JMBE library jar file to the same directory as the SDRTrunk application, you should not have any issues.
SDRTrunk will generate a log entry to let you know if it discovered the jmbe library correctly for each P25 channel that you have decoding:
> 09:38:54.166 INFO d.p.audio.P25AudioOutput - JMBE audio conversion library successfully loaded - P25 audio will be available
Or, when the library cannot be found, each channel will log:
> 09:38:54.166 INFO d.p.audio.P25AudioOutput - JMBE audio conversion library NOT FOUND

11
LTR.md Normal file
View File

@@ -0,0 +1,11 @@
# LTR Standard Decoder #
## Squelch Control ##
The LTR decoder provides signalling-based squelch control. If you have a decoding channel selected, then audio will play automatically during a call, and will be squelched at the end of the call, or upon call timeout.
## Aliases ##
If you are in the United States, and your LTR network occasionally broadcasts its FCC station callsign, then add the following alias to each alias list you are using for LTR:
* `*`-`*``*`-255 FCC CWID

62
LTRNet.md Normal file
View File

@@ -0,0 +1,62 @@
# LTR-Net Decoder #
The LTR-Net decoder will decode both Inbound Status Word (ISW) and Outbound Status Word (OSW) messaging. ISW messages are transmitted by the mobile radio on the uplink, or input frequency of the repeater. The network broadcasts OSW messages on the downlink or output frequency of the repeater.
Many of the LTR-Net system information messages are two-part messages. In the decoded messages table, you will see references to part 1 of 2 or for ESNs, you may only see one half of the ESN (1234xxxx).
## Squelch Control ##
The LTR-Net decoder provides signalling-based squelch control. If you have a decoding channel selected, then audio will play automatically during a call, and will be squelched at the end of the call, or upon call timeout.
## Channels ##
Each LTR-Net site supports 1-20 Logical Channel Numbers (LCN). Each site will have a continuously transmitting Home Status Channel (HSC).
Each LCN transmits the same site configuration message set. The HSC transmits these messages repeatedly, and the individual traffic channels transmit these messages one at a time, every few seconds.
The HSC will support traffic calls if the primary traffic channels become saturated. In addition, the HSC will reflect all traffic call activity from all traffic channels on the site. An effective strategy for determining site usage is to monitor the HSC and then look at the call event table to see call activity for the entire site.
## Activity Summary ##
The [Activity Summary](ActivitySummary.md) information window displays all decoded information about the current site (site id, channels, frequencies, talkgroups, etc.).
## Talkgroups ##
LTR-Net supports roaming of users across all sites in the system. Each talkgroup is defined to be unique at a specific site, or unique across the network.
If you discover that a talkgroup is unique across the network, you can wildcard the talkgroup alias, so that that alias is used on every site in the systme for the talkgroup. Wildcard the area and channel fields for a global talkgroup ( `*`-`*``*`**-123 )**
## Special Talkgroups ##
Talkgroups 240 - 247 are reserved for special network functions like PSTN telephone calls to/from a radio, or network phone patches.
## Unique ID ##
Each radio is assigned a unique ID by the system. This supports radio identification to the network, and supports individual radio messaging by the network. Unique IDs are 16--bit values ranging 1 - 65536.
## ESN ##
Each LTR-Net radio has a globally unique Electronic Serial Number that is set at the vendor factory.
## Decoding ESNs and Unique IDs ##
The mobile radio's Electronic Serial Number (ESN) is broadcast by the radio on the uplink frequency upon registration. In response, the network broadcasts a radio Unique ID assignment on the downlink frequency to the mobile radio. The radio then uses that unique ID for all subsequent communications.
You can discover these ESN and Unique ID assignments by decoding both the uplink and downlink frequencies for a specific channel at the same time. Watch the uplink call event table for ESN messages. Find the corresponding radio register message from the downlink frequency that matches the timestamp.
If the mobile radio later makes a call, you can discover the Unique ID and the talkgroup that the radio belongs to and the identity of the user.
## LTR-Net Aliasing ##
Setup an alias with all three pieces of information ( ESN, Unique ID,
and Talkgroup ) and you will then know when that radio is registering on the network, and which radio in the talkgroup is broadcasting.
### Aliases to use with LTR-Net ###
* `*`-`*``*`-240 Special Talkgroup
* `*`-`*``*`-241 Special Talkgroup
* `*`-`*``*`-242 Special Talkgroup
* `*`-`*``*`-243 Special Talkgroup
* `*`-`*``*`-244 Special Talkgroup
* `*`-`*``*`-245 Special Talkgroup
* `*`-`*``*`-246 Special Talkgroup
* `*`-`*``*`-247 Special Talkgroup
* `*`-`*``*`-253 Radio Register
* `*`-`*``*`-254 FCC CWID

3
MDC1200.md Normal file
View File

@@ -0,0 +1,3 @@
# MDC-1200 Decoder #
The MDC-1200 decoder is a work in progress. The decoder doesn't provide any error detection or error correction, so some of the decoded messages may not be accurate.

21
MPT1327.md Normal file
View File

@@ -0,0 +1,21 @@
# MPT-1327 #
The MPT-1327 decoder provides decoding of both control and traffic channel signaling.
## Squelch Control ##
The control channel is not squelch controlled and will produce audio of the control signal when selected. Each individual traffic channel is unsquelched for the duration of the call, until call end, or call timeout.
## Usage ##
Run the decoder against the control channel. If a tuner is available, traffic channels will be created and started decoding automatically. Upon call tear down, or call timeout, traffic channels will automatically be destroyed.
NOTE: the decoder requires a [channel map](ChannelMap.md) in order to automatically allocate and trunk track traffic channels.
Monitor the messages window to verify that the decoder is working. Ensure the tuner is accurately aligned with the center of the control signal for optimal decoding.
## Talkgroups ##
Create an alias group containing the following MPT-1327 system idents:
> `*``*``*`-8185 = System Register
> `*``*``*`-8190 = System Controller

10
Map.md Normal file
View File

@@ -0,0 +1,10 @@
# Map #
The map displays any decoded messages that contain location data, like GPS positions.
The map component uses aliases to determine the display label, icon and color to use when plotting decoded messages. Update messages from the same entity are chained together.
The map uses map tiles from the open street map server. If you do not have an internet connection, no map data will be displayed, however decoded messages will be plotted.
## Default Location and Zoom ##
Drag the map to recenter the view and use the mouse wheel to zoom in or out. Right-click on the map to store the location and zoom level as the map default.

3
Messages.md Normal file
View File

@@ -0,0 +1,3 @@
# Messages #
The messages component displays messages as they are decoded by the channel decoder. All messages from the primary decoder and any messages from auxiliary decoders are displayed.

7
NBFM.md Normal file
View File

@@ -0,0 +1,7 @@
# NBFM Decoder #
The NBFM decoder is a simple FM demodulator. You can use any of the auxiliary decoders ([Fleetsync](Fleetsync2.md) or [MDC1200](MDC1200.md) ) in conjunction with the NBFM decoder.
## Squelch Control ##
The NBFM doesn't provide any squelch control.

25
Passport.md Normal file
View File

@@ -0,0 +1,25 @@
# Passport #
The passport decoder will decode the Outbound Status Word (OSW) messages and signalling that are transmitted by the network to the mobile radio.
## Talkgroups ##
User mobile radios are normally assigned the talkgroup identifiers starting from 1, upward. Group talkgroups are normally assigned from the highest talkgroup numbers working their way downward. You can create an alias for each talkgroup.
## Mobile ID Number (MIN) ##
Each passport mobile radio on the network is assigned a MIN. You can create an alias for each MIN.
## Squelch Control ##
The Passport decoder provides signalling-based squelch control. If you have a decoding channel selected, then audio will play automatically during a call, and will be squelched at the end of the call, or upon call timeout.
## Aliases ##
If you are in the United States, and your Passport network occasionally broadcasts its FCC station callsign, then add the following alias to each alias list you are using for Passport:
* 65535 FCC CWID
## Passport Decode Example ##
![http://sdrtrunk.googlecode.com/svn/wiki/images/passport_decoding.png](http://sdrtrunk.googlecode.com/svn/wiki/images/passport_decoding.png)

11
Playlist.md Normal file
View File

@@ -0,0 +1,11 @@
# Playlist #
The playlist contains a folder for each of the following:
* [Alias Lists](AliasList.md)
* [Channel Maps](ChannelMap.md)
* [Systems](System.md)
Note: the Systems, Channel Maps and Alias Lists folders cannot be deleted or changed.
![http://sdrtrunk.googlecode.com/svn/wiki/images/Configuration.png](http://sdrtrunk.googlecode.com/svn/wiki/images/Configuration.png)

49
ProjectHome.md Normal file
View File

@@ -0,0 +1,49 @@
## SDRTrunk ##
SDRTrunk is a java based application for decoding and trunk tracking multiple analog and digital radio channels across multiple USB dongle tuners and/or sound card inputs from scanner radios.
* **[Getting Started](GettingStarted.md)**
* **[User's Manual](UserManual.md)
***[Download](https://drive.google.com/folderview?id=0B7BHsssXUq8eOHBTNndCczZTd0k&usp=sharing)
This application uses some of the fantastic components available from [JIDE Software](http://www.jidesoft.com).
![http://sdrtrunk.googlecode.com/svn/wiki/images/SDRTrunk_application.png](http://sdrtrunk.googlecode.com/svn/wiki/images/SDRTrunk_application.png)
### Operating Systems ###
* **Linux**
* **Windows**
* Any operating system supported by Java and libusb, however other systems have not yet been tested
### Requirements ###
* **[Java 7](http://www.java.com/en/download/index.jsp)** or newer
### Supported [Tuners](Tuner.md) ###
* Airspy - coming soon
* Funcube Dongle Pro
* Funcube Dongle Pro Plus
* HackRF
* RTL-2832 with E4000 Tuner
* RTL-2832 with R820T Tuner
* Sound card(s) connected to scanner audio output
### Decoders ###
* [APCO-25](APCO25.md) Phase 1 - C4FM and CQPSK/LSM - coming soon
* [Fleetsync II](Fleetsync2.md)
* [LJ-1200](LJ1200.md)
* [LTR](LTR.md)
* [LTR-Net](LTRNet.md)
* [MDC-1200](MDC1200.md)
* [MPT-1327](MPT1327.md)
* [Passport](Passport.md)
* [Tait CCDI 1200 ANI/GPS](Tait.md)
Note: nomitive use of protocol names are for identification. Registered trademarks are the property of their respective owners.
### Source Code ###
The source code is available on this website
* [Downloading and Compiling](Building.md) sdrtrunk

9
R820T.md Normal file
View File

@@ -0,0 +1,9 @@
# RTL-2832 with Rafael Micro R820T Tuner #
http://www.nooelec.com/store/sdr/sdr-receivers.html
R820T tuner support is now included as of 20140614, revision [R134](https://code.google.com/p/sdrtrunk/source/detail?r=134).
Windows Users: R820T support requires installation of Zadig driver:
http://zadig.akeo.ie

5
ScreenCapture.md Normal file
View File

@@ -0,0 +1,5 @@
# Screen Capture #
Click on the menu item entitled **Screen Capture** to automatically create a screen capture of the currently displayed screen layout.
Screen captures are stored in the **Screen Captures** sub folder in the sdrTrunk folder in your user directory.

19
SetupLinux.md Normal file
View File

@@ -0,0 +1,19 @@
1. Install Java JRE version 7 or newer from http://www.oracle.com/java
2. Verify java installation:
```
terminal: java -version
java version "1.7.0_55"
Java(TM) SE Runtime Environment (build 1.7.0_55)
Java HotSpot (TM) 64-bit Server VM
```
3. Install udev rules file for any tuners you'll be using into the /etc/udev/rules.d/ directory. The **funcube-dongle.rules** and **rtl-sdr.rules** files are included.
4. Run the SDRTrunk start script:
```
terminal: ./run_SDRTrunk
```

17
SetupWindows.md Normal file
View File

@@ -0,0 +1,17 @@
1. Install Java JRE version 7 or newer from http://www.oracle.com/java
2. Verify java installation:
```
c:\ java -version
java version "1.7.0_55"
Java(TM) SE Runtime Environment (build 1.7.0_55)
Java HotSpot (TM) 64-bit Server VM
```
3. Run the SDRTrunk start script:
```
C:\SDRTRunk\run_SDRTrunk.bat
```

23
Site.md Normal file
View File

@@ -0,0 +1,23 @@
# Site #
A site is the next level below a [System](System.md) for managing a set of [channels](Channel.md). Use a different site for each trunked radio tower location, or to organize a collection of related channels.
When a [Channel](Channel.md) within the [Site](Site.md) is actively decoding, the system icon is colored Green.
![http://sdrtrunk.googlecode.com/svn/wiki/images/Site.png](http://sdrtrunk.googlecode.com/svn/wiki/images/Site.png)
# Creating a New Site #
2. Right-click on a [System](System.md) folder and select 'New Site'.
3. Select the new [Site](Site.md) and update the name in the editor. Click 'Save'.
# Deleting a Site #
2. Right-click on the [Site](Site.md) and select 'Delete'
# Changing a Site Name #
2. Select the site from the list.
3. Update the name in the editor and click 'Save'

7
SoundCard.md Normal file
View File

@@ -0,0 +1,7 @@
# Sound Card / Mixer Sources #
You can input the headset audio, and/or discriminator audio output from your scanner to use as a source for each of the decoders. Normal headset audio works great with MPT-1327, Fleetsync and MDC-1200. Discriminator audio is required for LTR, LTR-Net and Passport since the signalling would be filtered out by the normal headset audio filters.
Use the **NBFM** decoder first when you are trying to setup a scanner to sound card setup. Configure a channel using the NBFM decoder and select the sound card and left or right channel as the input. Enable the channel and once running, select the channel in the [decoding channels](DecodingChannels.md) window to hear the audio output. Adjust the scanner audio volume to mid-level, but not so high as to induce clipping on the signal.
Once you have good sound running through the system, change the decoder from NBFM to the one you want to use and save the configuration.

43
SpectralDisplay.md Normal file
View File

@@ -0,0 +1,43 @@
# Introduction #
The spectral display component shows the frequency activity of the currently selected tuner.
## Cursor ##
A cursor with frequency readout is automatically shown as you move the mouse about the spectral display window.
## Context Menus ##
Right-click anywhere in the spectral display to show a list of context-specific menu options.
### Channel Menu ###
Channels defined in the [Playlist](Playlist.md) are also displayed in the spectral display window. Each channel exposes a context menu allowing you to start/stop the channel decoder, or view the [ActivitySummary](ActivitySummary.md) for currently decoding channels
### Frequency Menu ###
The current frequency displayed by the cursor displays as a menu that allows you to assign a decoder and automatically start decoding that channel. A channel configuration is automatically created and enabled.
### Color Menu ###
The color menu allows you to change any of the global color settings used by all spectral displays.
* **Background** - background color for the spectral display
* **Channel** - channel overlay color for channels that are defined in the configuration, but are currently not processing (decoding) or selected
* **Channel Processing** - channel overlay color for any channels that are currently processing (decoding)
* **Channel Selected** - channel overlay color for the channel that is currently selected in the [Decoding Channels](DecodingChannels.md) window.
* **Cursor** - color used for the cursor and frequency readout
* **Gradient Bottom** - bottom color for the gradient used to display the frequency spectrum
* **Gradient Top** - top color for the gradient used to display the frequency spectrum
* **Lines** - color used for lines and frequency labels
### Display Menu ###
The display menu allows you to change settings associated with Fast Fourier Transform (FFT) results that are displayed in the spectral display. Changes made with the display menu are temporary and only apply to the spectral display where they are changed.
* **FFT Width** - bin size used in FFT calculations, 512 - 32,768. Using a higher setting provides increased resolution in the display, but also significantly increases CPU usage.
* **Frame Rate** - determines the number of times per second that the FFT is calculated and the spectral display is updated.
* **Window Type** - specifies the windowing method to use prior to calculating the FFT.
## Changing Displayed [Tuner](Tuner.md) ##
Right-click on the desired tuner in the [Configuration](Configuration.md) window and select **Show in Main Spectrum**, or choose **New Spectrum Window** to create a new, separate Spectral Display and Waterfall.

29
System.md Normal file
View File

@@ -0,0 +1,29 @@
# System #
A system is a top-level folder for managing a set of [sites](Site.md) and [channels](Channel.md). Use a different system for each trunked radio network, or to organize a collection of related sites and channels.
When a channel within the system is actively decoding, the system icon is colored Green.
![http://sdrtrunk.googlecode.com/svn/wiki/images/System.png](http://sdrtrunk.googlecode.com/svn/wiki/images/System.png)
# Creating a New System #
1. Expand the [Playlist](Playlist.md) folder and the [Systems](Systems.md) folder
2. Right-click on the [Systems](Systems.md) folder and select 'New System'.
3. Select the new [System](System.md) folder and update the system name in the editor. Click 'Save'.
# Deleting a System #
1. Expand the [Playlist](Playlist.md) folder and the [Systems](Systems.md) folder
2. Right-click on the [System](System.md) and select 'Delete'
# Changing a System Name #
1. Expand the [Playlist](Playlist.md) folder and the [Systems](Systems.md) folder
2. Select the system from the list.
3. Update the system name in the editor and click 'Save'

31
Tuner.md Normal file
View File

@@ -0,0 +1,31 @@
# Tuner #
The Tuners folder contains a listing of all recognized tuners that are automatically discovered upon startup of the SDRTrunk application. Each tuner displays the tuner type, name, serial number (if known), and the currently tuned frequency and [bandwidth/sample] rate.
![http://sdrtrunk.googlecode.com/svn/wiki/images/Tuners.png](http://sdrtrunk.googlecode.com/svn/wiki/images/Tuners.png)
## Supported Tuners ##
The following tuners are currently supported or will soon be supported by the SDRTrunk application. Additional tuner support may be added in the future.
* **[Funcube Dongle Pro](FuncubeDonglePro.md) (1.0)**
* **[Funcube Dongle Pro Plus](FuncubeDongleProPlus.md) (2.0)**
* **[RTL-2832 with Elonics E4000](E4000.md)**
* **[Ettus B100/WBX Daughter Card](B100.md)** - (planned). SDRTrunk will recognize the B100 but it will not allow you to use or configure the B100
* **[HackRF](HackRF.md)**
* **[RTL-2832 with Rafael Micro R820T](R820T.md)**
* **[RTL-2832 with Fitipower FC0013](FC0013.md)** - (planned)
## Tuner Management ##
SDRTrunk manages all tuners as a pooled set of resources. As you enable channels for decoding, SDRTrunk polls each tuner to see if it can support the requested channel, and then assigns the channel to the tuner. If no tuners can support the channel, then the [Channel State](ChannelState.md) will reflect **NO TUNER**.
Each tuner can source one or more channel frequencies, as long as the set of channel frequencies fit within the current center tuned frequency and bandwidth (sample rate) of the tuner. As additional channels are sourced by the tuner, the tuner controller will automatically tune the center frequency to provide a best-fit of all of the requested channels, while ensuring that no channels overlap the DC-spike normally present in the center of the spectrum for these types of tuners.
## Visualizing the Tuner Spectrum ##
On startup, SDRTrunk automatically displays the first discovered tuner in the [Spectral Display](SpectralDisplay.md). All tuners can be displayed in the main spectral display or in additional spectral display windows.
* **Application Spectral Display** - right-click on any of the tuners and select **Show in Main Spectrum** to show the spectral display for that tuner in the main application display.
* **Additional Spectral Display** - right click on any of the tuners and select **New Spectrum Window** to open a new window and display the spectrum for that tuner. You can open as many spectral display windows as you want, including multiple windows on the same tuner.

42
UserManual.md Normal file
View File

@@ -0,0 +1,42 @@
# SDRTrunk User's Manual #
1. [Application Overview](ApplicationOverview.md)
1. [Call Events](CallEvents.md)
1. [Decoding Channels List](DecodingChannels.md)
1. [Editor](Editor.md)
1. [Map](Map.md)
1. [Messages](Messages.md)
1. [Spectral Display](SpectralDisplay.md)
1. [Waterfall Display](WaterfallDisplay.md)
1. Aliases
1. [Alias List](AliasList.md)
1. [Alias Group](AliasGroup.md)
1. [Alias](Alias.md)
1. [Alias Actions](AliasAction.md)
1. Auxiliary Decoders
1. [Fleetsync II](Fleetsync2.md)
1. [MDC1200](MDC1200.md)
1. [Configuration](Configuration.md)
1. [Alias Lists](AliasList.md)
1. [Channel Maps](ChannelMap.md)
1. [Playlist](Playlist.md)
1. Decoders
1. [LTR](LTR.md)
1. [LTRNet](LTRNet.md)
1. [MPT1327](MPT1327.md)
1. [NBFM](NBFM.md)
1. [Passport](Passport.md)
1. Logging
1. [Application Log](ApplicationLog.md)
1. [Event Log](EventLogger.md)
1. [Recorder](Recorder.md)
1. Sources
1. [Sound Card](SoundCard.md)
1. [Tuners](Tuner.md)
1. [Ettus Research B100](B100.md)
1. [Funcube Dongle Pro](FuncubeDonglePro.md)
1. [Funcube Dongle Pro Plus](FuncubeDongleProPlus.md)
1. [RTL-2832 with E4000 Tuner](E4000.md)
1. [RTL-2832 with FC0013 Tuner](FC0013.md)
1. [RTL-2832 with R820T Tuner](R820T.md)
1. [ScreenCapture](ScreenCapture.md) Screen Captures

9
WaterfallDisplay.md Normal file
View File

@@ -0,0 +1,9 @@
# Waterfall Display #
The waterfall display shows a history of the frequency content of the currently displayed [tuner](Tuner.md).
## Context Menus ##
Right-click anywhere in the waterfall display to view a list of context-sensitive menu options. See the [Spectral Display](SpectralDisplay.md) page to see descriptions of the Color, Display and Frequency context menus.
* **Pause** - pauses the waterfall and displays **Paused** in the upper left corner. When you un-pause the display, the waterfall will show all frequency history that happened while paused.