diff --git a/.project b/.project deleted file mode 100644 index 7a8b5d4..0000000 --- a/.project +++ /dev/null @@ -1,11 +0,0 @@ - - - sdrtrunk.wiki - - - - - - - - diff --git a/Creating-Radio-Reference-Library.md b/other/Creating-Radio-Reference-Library.md similarity index 100% rename from Creating-Radio-Reference-Library.md rename to other/Creating-Radio-Reference-Library.md diff --git a/JMBE.md b/other/JMBE.md similarity index 100% rename from JMBE.md rename to other/JMBE.md diff --git a/Java-Flight-Recorder.md b/other/Java-Flight-Recorder.md similarity index 100% rename from Java-Flight-Recorder.md rename to other/Java-Flight-Recorder.md diff --git a/v0.2/AM.md b/v0.2/AM.md deleted file mode 100644 index 67788bd..0000000 --- a/v0.2/AM.md +++ /dev/null @@ -1,8 +0,0 @@ -# AM Decoder # - -The AM decoder is a simple AM demodulator for monitoring air band and other -amplitude modulated signals. - -## Squelch Control ## - -The AM decoder doesn't provide any audio squelch control. \ No newline at end of file diff --git a/v0.2/APCO25.md b/v0.2/APCO25.md deleted file mode 100644 index b720c94..0000000 --- a/v0.2/APCO25.md +++ /dev/null @@ -1,113 +0,0 @@ -# APCO-25 Decoder # - -The P25 decoder processes all voice, trunking, and data messages and provides -traffic/voice/data call following when a tuner is available that can monitor -both the control channel and any traffic channels within the available bandwidth -of the tuner, or across multiple tuners. - -## P-25 Phase I## -Decodes FDMA Common Air Interface (CAI) C4FM modulation and Linear Simulcast -Modulation (LSM). - -## P-25 Phase II## -Phase II TDMA decoding is not currently supported. - -## P-25 Hybrid (Phase I/II)## -P25 hybrid systems use both Phase 1 control channels and Phase I and Phase II -traffic channels, providing transition support for users with a combination of -Phase I and Phase II radios. - -TDMA configuration messages that are broadcast on Phase I control channels are -decoded. Currently these include the TDMA timing synchronization and TDMA -channel identifier messages. - -## Audio Vocoders ## - -### IMBE ### -APCO-25 Phase I 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) - -### VSELP ### -SDRTrunk recognizes VSELP audio CODEC messages and will display them in the -messages tab during decoding. However, it will not decode the audio. - -## Traffic Channel Following ## -The P25 decoder provides full traffic channel following when monitoring a P25 -control channel. You can optionally select to not follow data calls in the -decoder configuration when setting up the channel for decoding. - -## 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. - -Add these trunking system unit ID values to your alias list: - -**FFFFFD** = (Trunking) System Controller. -**FFFFFE** = Registration Controller -**FFFFFF** = All Call - -## 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. - -## Monitoring a P25 Trunked System ## - -Setup a channel to decode the trunked system's control channel only. The decoder -will automatically detect when additional traffic channels are allocated for -calls and will create temporary decoding channels in the application to process -each of these calls. - -You do NOT need to create decoding channel configurations for each of the -traffic channel frequencies used by the system because the control channel will -tell the sdrtrunk application every thing that it needs to know in order to -setup a temporary decoding channel. - -### Traffic Channel Pool ### - -When configuring the P25 control channel decode configuration, use the Traffic -Channel Pool setting to set the maximum number of temporary traffic channels -that can be running at the same time. The sdrtrunk application will create -channel configurations up to this maximum number and reuse the channel -configurations for subsequent calls. - -The default value of 4 traffic channels in the pool is suitable for a modern -powerful processor. You may have to reduce this pool size if you are using a -lower powered CPU. Monitor the computer's CPU and memory consumption and adjust -this value as needed. Note: you'll have to stop and restart the decoding after -you change the traffic channel pool size value and save it. - -## P25 Decoding Example ## - -The following screenshot shows the application configured to decode one P25 -control channel. It also shows 3 traffic channels being decoded where the -call event was decoded on the control channel and sdrtrunk automatically -created the 3 decoder channels to follow the calls. - -![](images/P25Decoder.png) - diff --git a/v0.2/ActivitySummary.md b/v0.2/ActivitySummary.md deleted file mode 100644 index 57d1129..0000000 --- a/v0.2/ActivitySummary.md +++ /dev/null @@ -1,17 +0,0 @@ -# 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), 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) - right-click on a currently decoding channel in the configuration tree - * [Decoding Channels](DecodingChannels) - right-click on a channel - * [Spectral Display](SpectralDisplay) - right click on a currently decoding channel overlay \ No newline at end of file diff --git a/v0.2/Airspy.md b/v0.2/Airspy.md deleted file mode 100644 index 665b4c1..0000000 --- a/v0.2/Airspy.md +++ /dev/null @@ -1,76 +0,0 @@ -# Airspy # - -## 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. - - * **New** - creates a new named tuner configuration - * **Delete** - deletes the currently listed tuner configuration - - * **Sample Rate** - select from 10.00 or 2.50 MHz sample rates. Note: the - additional decimation option is not currently supported in sdrtrunk. - * **Gain Mode** - select from LINEARITY, SENSITIVITY, or CUSTOM. Linearity - and sensitivity modes provide a single gain adjustment value that automatically - configures the IF, Mixer and LNA gains for each master gain setting. The - Custom mode disables the single gain adjustment slider and provides access to - each of the IF, Mixer and LNA gain sliders so that you can manually adjust - each gain value to meet your specific needs. - -### Info Tab ### -The info tab displays information about the tuner: - - * **Serial** - serial number of the Airspy tuner. - * **Firmware** - version number of the firmware loaded in the airspy - * **Part** - airspy part number - * **Board ID** - airspy board identifier - -## Using the Airspy ## - -![](images/airspy.png) - -## 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 support -flashing the Airspy with new firmware. Use the Airspy tools to update the -tuner. - -## Using Airspy With Linux ## - -If you've never setup your airspy for linux, you'll need to add permissions to allow users to access the airspy: - -Copy the file **\config\52-airspy.rules** from the sdrtrunk application folder to your **\etc\udev\rules.d** folder. - - sudo cp 52-airspy.rules \etc\udev\rules.d - -Set file permissions. - - sudo chmod u=rw,g=r,o=r 52-airspy.rules - -Refresh the udev rules - - sudo udevadm control --reload-rules diff --git a/v0.2/Alias.md b/v0.2/Alias.md deleted file mode 100644 index 3bbaaba..0000000 --- a/v0.2/Alias.md +++ /dev/null @@ -1,98 +0,0 @@ -# Alias # - -An alias is a user defined label that can be associated with one or more -identifiers produced by the decoders. Each alias can include: - - * **Alias Identifier** - (see below) one or more identifiers that you want to be associated with the alias - * [Alias Action](AliasAction) - an action that you want to happen each time the alias is active - * [Non-Recordable](NonRecordable) - indicates that the alias should not be recorded when - AUDIO recording is specified for the decoding channel - * [Call Priority](CallPriority) - specifies audio playback priority for this alias or allows - you to designate an alias as 'DO NOT MONITOR' - -![](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)** - 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. One or more of these decoded identifiers can -be assigned to an alias. - -### 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 in the ADD ID menu, 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. - -![](images/AliasESNID.png) - - * **Fleetsync** - fleetsync identifier. - -![](images/AliasFleetsyncID.png) - - * **LoJack** - lojack tower or transponder and related functions. - - * **MDC-1200** - MDC-1200 identifier. - -![](images/AliasMDC1200ID.png) - - * **MIN** - passport radio Mobile ID Number (MIN). - -![](images/AliasMIDID.png) - - * **MPT-1327** - MPT-1327 user or group identifier. - -![](images/AliasMPT1327ID.png) - - * **Site** - site number. - -![](images/AliasSiteID.png) - - * **Status** - status numeric value produced by decoders like P25 or FLEETSYNC - - * **Talkgroup** - used with P25, LTR and Passport talkgroups. **TGID** -identifies the formatted talkgroup. - -![](images/AliasTalkgroupID.png) - - * **Unique ID** - LTR-Net mobile radio unique ID (UID). - -![](images/AliasUniqueID.png) \ No newline at end of file diff --git a/v0.2/AliasAction.md b/v0.2/AliasAction.md deleted file mode 100644 index cc82d4e..0000000 --- a/v0.2/AliasAction.md +++ /dev/null @@ -1,48 +0,0 @@ -# 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 # - -![](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. - -![](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 \ No newline at end of file diff --git a/v0.2/AliasGroup.md b/v0.2/AliasGroup.md deleted file mode 100644 index f1d2e2e..0000000 --- a/v0.2/AliasGroup.md +++ /dev/null @@ -1,13 +0,0 @@ -# Alias Group # - -Contains a list of [Aliases](Alias) 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. - -![](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** \ No newline at end of file diff --git a/v0.2/AliasList.md b/v0.2/AliasList.md deleted file mode 100644 index 5911468..0000000 --- a/v0.2/AliasList.md +++ /dev/null @@ -1,13 +0,0 @@ -# Alias List # - -Contains a list of [Alias Groups](AliasGroup) and [Aliases](Alias) used by the decoder to assign an alias name to one or more identifiers produced by the decoder. - -![](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** \ No newline at end of file diff --git a/v0.2/ApplicationLog.md b/v0.2/ApplicationLog.md deleted file mode 100644 index 63f60d1..0000000 --- a/v0.2/ApplicationLog.md +++ /dev/null @@ -1,19 +0,0 @@ -# Application Log # - -The application log contains logging information about the application. Note: see [EventLog](EventLog) for details about logging of decoded channel messages. - -# Location # - -**Windows 7**: - -c:\Users\(your username)\sdrtrunk\log\ - - ---- - - -**Linux**: - -In your user directory: - -~\sdrtrunk\log \ No newline at end of file diff --git a/v0.2/ApplicationOverview.md b/v0.2/ApplicationOverview.md deleted file mode 100644 index a1a7be2..0000000 --- a/v0.2/ApplicationOverview.md +++ /dev/null @@ -1,15 +0,0 @@ -### Application Overview ### - - * [Audio Panel](AudioPanel) - * [Channel Spectrum](ChannelSpectrum) - * [Configuration](Configuration) - * [Decoding Channels](DecodingChannels) - * [Editor](Editor) - * [Events](CallEvents) - * [Map](Map) - * [Messages](Messages) - * [Spectral Display](SpectralDisplay) - * [Waterfall Display](WaterfallDisplay) - -![](images/Overview.png) - \ No newline at end of file diff --git a/v0.2/AudioPanel.md b/v0.2/AudioPanel.md deleted file mode 100644 index 0f22682..0000000 --- a/v0.2/AudioPanel.md +++ /dev/null @@ -1,64 +0,0 @@ -# Audio Panel # - -The audio panel controls the audio that is played from the decoding channels to -either your computer speakers or headphones. Audio from each decoding channel -is automatically routed to the Audio Manager and the audio manager automatically -routes the highest priority audio to the speakers. - -Each audio playback channel is automatically started and stopped depending on -audio availability. Playback channels use an internal buffer to store a -small number of audio frames before automatically starting playback. Therefore, -you may experience a slight delay between seeing a call start in the decoder -window and audio playback starting. Likewise, you may hear audio playing for a -short period after the decoding channel display indicates that the call has -ended. - -Audio priority can be specified for each alias that you create. If you want -certain talkgroups or identifiers to have a higher priority for listening, you -can create the alias, assign the talkgroup(s) or identifier(s) and specify a -priority. - -If a call is in playback over the speakers and a higher priority call comes in, -the higher priority call will be routed and the existing call audio will be -stopped. - -You can override all call priorities defined in the system when you select an -individual decoding channel. Any audio produced from a selected channel is -routed with the highest priority for playback. - -## Audio Playback Device ## - -The default audio playback device with mono audio is selected by default. You -can change the audio playback device and choose the number of playback channels -by right-clicking on the audio panel and use the AUDIO OUTPUT menu to select a -different audio device. - -## Mono Audio Playback ## -You can select mono audio playback to have any playback audio routed to both -speakers. - -![](images/mono_audio_panel.png) - -## Stereo Audio Playback ## -You can select stereo audio playback so that you have independent LEFT and RIGHT -audio playback over a stereo audio output. Each audio channel will be managed -by the Audio Manager and all audio produced by all decoding channels will be -routed to these two channels on a priority basis. - -![](images/stereo_audio_panel.png) - -## Mute Button ## -The green speaker icon on the audio panel is the master mute control. Click the -icon to mute the audio and the icon will turn red. Click again, and the audio -will unmute and the icon will turn green again. - -![](images/audio_muted.png) - -## Channel Menu ## -Right-click on either the MONO channel, or the LEFT or RIGHT channel to access -the context menu for the channel. You can independently mute or change the -audio volume of each channel via this context menu. - -## Channel Mute ## -Each channel will show a RED M in the panel when the audio is muted either via -the master mute button, or by the channel mute context menu. \ No newline at end of file diff --git a/v0.2/B100.md b/v0.2/B100.md deleted file mode 100644 index 1fb77ca..0000000 --- a/v0.2/B100.md +++ /dev/null @@ -1,5 +0,0 @@ -# Ettus Research B100 with WBX Daughter Card # - -Coming soon. - -https://www.ettus.com/product/details/UB100D-BDL \ No newline at end of file diff --git a/v0.2/Building.md b/v0.2/Building.md deleted file mode 100644 index 2068b5d..0000000 --- a/v0.2/Building.md +++ /dev/null @@ -1,27 +0,0 @@ -# Downloading and Compiling sdrtrunk # - -The sdrtrunk source code is hosted on github.com and the repository can be -downloaded as a compressed archive or cloned using GIT. - -[sdrtrunk repository on github](https://github.com/DSheirer/sdrtrunk) - -## Eclipse IDE ## - -If you use the [Eclipse IDE for Java](http://www.eclipse.org/downloads/), you -can clone the github source code repository and import the sdrtrunk project -directly into Eclipse using either the EGit or JGit plugins. - -## 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 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. Click the 'Download Zip' button to download the source code from - https://github.com/DSheirer/sdrtrunk and unzip the code - 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 -default build target. The compiled and zipped output program file will be -located in the sdrtrunk/product/xxx.zip folder. \ No newline at end of file diff --git a/v0.2/CallEvents.md b/v0.2/CallEvents.md deleted file mode 100644 index 4a23ad2..0000000 --- a/v0.2/CallEvents.md +++ /dev/null @@ -1,50 +0,0 @@ -# Call Events # - -The **Events** window displays a history of the radio calls and network messages -that have been decoded for each channel. Select each channel individually in -the [decoding channels](DecodingChannels) window to display the call event -history for that channel. - -![](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 Event Types ## - * **Acknowledge** - acknowledgement from a radio - * **ANI** - automatic number identification for a radio - * **Announcement** - announcement transmitted on a control channel - * **Call** - call event - * **Call Alert** - a mobile radio is alerted about a pending call - * **Call Detect** - a call detected on another channel - * **Call-Do Not Monitor** - a call where either the TO or FROM identifier's - alias has a call priority with the 'Do Not Monitor' box checked - * **Command** - the network is commanding a mobile radio to do something - * **Data Call** - a data call event - * **Deregister** - a mobile radio is deregistering from the network - * **Emergency** - emergency notification from a radio - * **Encrypted Call** - a call using encryption - * **ESN** - radio registering on the network with an ESN, or responding to an ESN interrogation - * **Function** - a function transmitted by the network to the mobile radio - * **GPS** - gps location broadcast from a mobile radio - * **Group Call** - a group call event - * **Page** - the system is paging a radio - * **Query** - the network is querying the status of a mobile radio - * **Register** - radio registering on the network - * **Response** - the network is responding to a mobile radio - * **SDM** - short data message - * **Station ID** - network callsign (FCC ID) - * **Status** - status message - * **Telephone Interconnect** - a landline call to or from a mobile radio - * **Unit To Unit Call** - mobile radio to mobile radio call - * **Unique ID** - LTR-Net unique identifier for a radio registration - \ No newline at end of file diff --git a/v0.2/CallPriority.md b/v0.2/CallPriority.md deleted file mode 100644 index 0a28604..0000000 --- a/v0.2/CallPriority.md +++ /dev/null @@ -1,18 +0,0 @@ -# Call Priority # - -Any alias can be assigned a call monitoring priority. Priority values range -from 1 to 100, with 1 being the highest priority and 100 being the lowest. - -Audio playback will use any call priority that you have specified and will -automatically override lower priority calls with higher priority calls when they -occur. - -You can designate an alias as 'DO NOT MONITOR' and any audio calls where that -alias is a participant will not be routed for audio playback. - -Note: if you select a decoding channel, any audio from that channel will have -the highest priority and will override any settings that you have defined. -Selected audio has an effective priority of 0 so it will be higher priority than -your priority 1 alias calls. - -![](images/call_priority.png) diff --git a/v0.2/Channel.md b/v0.2/Channel.md deleted file mode 100644 index ca01fde..0000000 --- a/v0.2/Channel.md +++ /dev/null @@ -1,67 +0,0 @@ -# Channel # - -A channel defines all of the configuration details needed for to setup a radio channel for decoding. When a [Channel](Channel) is actively decoding, the system icon is colored Green. If there is no source available, the channel icon turns red. - -![](images/Channel.png) - -## Creating a New Channel ## - -Right-click on a [Site](Site) folder and select 'New Channel'. - -## Deleting a Channel ## - -Right-click on the [Channel](Channel) 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) 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) attached to your computer and it must appear in the list of [Tuners](Tuners) in the SDRTrunk [Configuration](Configuration) 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](Decoder) 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) - FM demodulator and Logic Trunked Radio (LTR) trunked radio signaling decoder - * [LTR-Net](LTRNet) - FM demodulator and LTR-Net trunked radio signaling decoder - * [MPT-1327](MPT1327) - FM demodulator and MPT-1327 trunked radio signaling decoder. Provides automatic traffic channel following. - * [NBFM](NBFM) - narrow-band FM demodulator. - * [Passport](Passport) - 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) - decodes ANI, Acknowledge, Status, Paging and GPS bursts - * [MDC-1200](MDC1200Decoder) - 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) 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. \ No newline at end of file diff --git a/v0.2/ChannelMap.md b/v0.2/ChannelMap.md deleted file mode 100644 index 04ae549..0000000 --- a/v0.2/ChannelMap.md +++ /dev/null @@ -1,35 +0,0 @@ -# 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. - -![](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 \ No newline at end of file diff --git a/v0.2/ChannelSpectrum.md b/v0.2/ChannelSpectrum.md deleted file mode 100644 index 5892cb0..0000000 --- a/v0.2/ChannelSpectrum.md +++ /dev/null @@ -1,27 +0,0 @@ -# Channel Spectrum # - -The channel spectrum window allows you to view the dynamic frequency content of -the demodulated audio produced from the currently selected decoding channel. -The demodulated audio is processed with a Discrete Fourier Transform (DFT) -similar to the Spectral Display. This display allows you to hover over each of -the peaks in the audio frequency and a frequency readout is displayed next the -cursor. - -You can use the frequency readout to measure spectral content like CTCSS tones -that may be present in the demodulated audio output. - -Spectral display processing only occurs when you have a channel selected and -when the spectral display tab is displayed. If you have the spectral display -tab displayed and no channels are selected, the display will be empty. - -Note: certain decoders like the P25-LSM decoder do not produce demodulated audio -and will not display audio content in the channel spectrum window. The audio -output from digital voice CODECs is not displayed in this channel spectrum -window. - -## Context Menus ## -You can change the color, FFT size, and frame rate of the channel spectrum -window by right-clicking anywhere in the display and choosing from the menu -options. - -![](images/channel_spectrum.png) \ No newline at end of file diff --git a/v0.2/Configuration.md b/v0.2/Configuration.md deleted file mode 100644 index 6ddc224..0000000 --- a/v0.2/Configuration.md +++ /dev/null @@ -1,10 +0,0 @@ -# Configuration # - -The configuration window uses a tree list to provide access to each of the -configurable features and settings in the SDRTrunk application. - - * [Tuners](Tuner) - controls each of the tuners available to the application - * [Playlist](Playlist) - allows you to create and edit decoding channels, - channel maps, and alias lists - -![](images/Configuration.png) \ No newline at end of file diff --git a/v0.2/Decoder.md b/v0.2/Decoder.md deleted file mode 100644 index ea6a388..0000000 --- a/v0.2/Decoder.md +++ /dev/null @@ -1,44 +0,0 @@ -# Decoders # - -Each decoding [channel](Channel) requires one primary decoder and can optionally -have zero or more auxiliary decoders running at the same time. If you want to -run multiple primary decoders on the same frequency, create separate channels -for each primary decoder. - -## Primary Decoders ### - - * [AM](AM) - AM demodulator - * [LTR-Standard](LTR) - FM demodulator and Logic Trunked Radio (LTR) trunked radio signaling decoder - * [LTR-Net](LTRNet) - FM demodulator and LTR-Net trunked radio signaling decoder - * [MPT-1327](MPT1327) - FM demodulator and MPT-1327 trunked radio signaling decoder and automatic trunked channel following. - * [NBFM](NBFM) - narrow-band FM demodulator. - * [Passport](Passport) - FM demodulator and Passport trunked radio signaling decoder. - * [P-25 Phase 1 C4FM](APCO25) - FM demodulator with P25 message decoder and automatic trunked channel following. - * [P-25 Phase 1 LSM](APCO25) - Quadrature demodulator with P25 message decoder and automatic trunked channel following. - -## Auxiliary Decoders ## -Auxiliary decoders are designed to process demodulated audio or in-band -signaling that is normally layered on top of another digital protocol or FM -modulated analog repeater channel. These layered protocols provide services -like Automatic Number Identification (ANI), status messaging, GPS location, -emergency notification, etc. Auxiliary protocols may be transmitted when the -mobile radio user keys the microphone, or in the case of GPS, they can key the -radio and transmit the GPS location without any user actions. - -How do auxiliary decoders work? Demodulated audio from a primary decoder's FM -demodulator is simultaneously routed to each of the auxiliary decoders -and the decode results are added to the Events and Messages lists, as well as -displayed in the [decoding channel](DecodingChannels) windows. - -Auxiliary decoders are normally used with analog decoders like NBFM, LTR, -LTR-Net, and Passport. - - * [Fleetsync II](Fleetsync2) - decodes ANI, Acknowledge, Status, Paging and GPS bursts - * [LJ1200](LoJack) - decodes LoJack data bursts on 173.075 MHz in US. - * [MDC-1200](MDC1200) - decodes MDC-1200 ANI bursts. - * [Tait 1200](Tait1200) - decodes Tait CCDI protocol GPS location bursts. - -**Note**: there are a wide variety of these auxiliary service protocols that can be -easily added to SDRTrunk. If you encounter a new audio-band protocol, collect -a number of good quality sample recordings and contact the author via the -google support group for possible inclusion in the sdrtrunk application. \ No newline at end of file diff --git a/v0.2/DecodingChannels.md b/v0.2/DecodingChannels.md deleted file mode 100644 index 041e09b..0000000 --- a/v0.2/DecodingChannels.md +++ /dev/null @@ -1,116 +0,0 @@ -# Decoding Channels # - -The decoding channels window displays a list of each of the channels that you -have enabled for decode. - -## Standard vs. Traffic Channels ## - -There are two types of decoding channels processed by the system. STANDARD -channels are defined in the playlist and enabled/disabled by you. TRAFFIC -channels are dynamically created by the Traffic Channel Manager when you are -decoding a control channel and the decoder detects that the monitored network -has allocated a traffic channel. The traffic channel is created, enabled and -disabled at the end of the call. If you are decoding a trunked control channel -and you have configured the decoder to allow traffic channels, you will see these -traffic channels appear in the decoding channels list and then disappear upon -call teardown. - -## Decoding Channel Window ## - -Each decoding channel that you have enabled will have a display panel that shows -the channel information and the current state of the channel. - -![](images/channel_state.png) - -* **Decoder** - primary and auxiliary decoders and related display fields that are specific to each decoder -* **Frequency** - frequency for the channel or audio input source name -* **Logging & Recording** - indicates logging (LOG) and recording (AUDIO/BASEBAND) options are enabled for this channel -* **Name** - name of the channel -* **Site** - channel's site name -* **State** - indicates the current channel state -* **System** - channel's system name - -## Channel States ## -Channel state tracks activity for the primary decoder and any auxiliary decoders -that have been added to the channel. Each state has a color associated with it -to provide visual feedback when the state changes. You can change the color -for each of these states using the right-click context menu. - -### IDLE State ### -Idle is the normal/resting state for a channel when it is not decoding any channel -activity, or when it is only decoding routine, periodic messages from the channel. - -![](images/idle_state.png) - -### CALL State ### -Call indicates the decoder is processing a call sequence. - -![](images/call_state.png) - -### CONTROL State ### -Control indicates that the decoder is processing a trunked radio system control channel. - -![](images/control_state.png) - -### DATA State ### -Data indicates that the decoder is processing a data call between the network -and the mobile radio. Normally, there will be no audio during this state. - -![](images/data_state.png) - -### FADE or TEARDOWN State ### -The FADE and TEARDOWN states occur after any CALL, DATA, or ENCRYPTED states to -provide a short period of time where you can still view the event details after -the event is over. For short audio calls, this provides you a moment to look -at the decoder and see which Identifiers were involved in the event. - -Standard channels use the FADE state and Traffic channels use the TEARDOWN state. -Traffic channels are immediately disabled, so you will likely not see the -TEARDOWN state. Standard channels will immediately transition back to an IDLE -state after the brief FADE pause. - -![](images/fade_state.png) - -### Automatic Audio Squelch ### -Channel state also controls audio playback. When you are using a trunking or -digital decoder, audio will only playback when the channel is in a CALL state. -If you are using a non-trunking decoder like the AM or the NBFM narrow band FM -demodulator, no automatic audio squelch is provided. - -## Selected Channel ## - -A decoding channel can be selected or deselected by left-clicking on the channel -display. A selected channel will have a color (yellow) highlight around the -perimiter of the channel display. Selecting a channel causes several changes -in the application display: - - * **Audio Playback Priority** is set to override all other audio priorities that - you have defined with aliases. This causes any audio output from the - selected channel to automatically be played to the speakers. - * **Channel Spectrum** will display demodulated audio from the channel only - when the channel spectrum tab is visible. When the channel spectrum tab is - hidden by selecting another tab, the spectrum display and processing is halted - even though the channel may still be selected - * **Events** tab in the configuration window will display any decode events - for the decoder channel. - * **Messages** tab in the configuration window will display any decoded - messages from the decoder channel. - - -## Channel Display Context Menus ## - -Right-click on any of the decoding channel displays to see a list of -context-sensitive menus applicable to each channel. - -### CHANNEL Menu ### - * **Disable** - disables decoding for this channel - * [Activity Summary](ActivitySummary) - displays a current activity summary for the channel - * **Delete** - disables and permanently deletes the channel from the [playlist](Playlist) - -### COLOR Menu ### - * **Background** - changes the background color of the channel display. Note: - the channel state color may obscure this background color. - * **Channel State** - changes the color gradient used for each channel state - * **Labels** - changes the text colors for the primary DECODER and the auxiliary - AUX DECODER display labels and the DETAILS for the channel like System, Site and Name. - * **Selected** - changes the channel selection border color diff --git a/v0.2/E4000.md b/v0.2/E4000.md deleted file mode 100644 index 11227cd..0000000 --- a/v0.2/E4000.md +++ /dev/null @@ -1,42 +0,0 @@ -# Elonics E4000 # - -http://www.nooelec.com/store/sdr/sdr-receivers.html - -![](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 \ No newline at end of file diff --git a/v0.2/Editor.md b/v0.2/Editor.md deleted file mode 100644 index a7769b6..0000000 --- a/v0.2/Editor.md +++ /dev/null @@ -1,5 +0,0 @@ -# Editor # - -[Configuration](Configuration) details for each node in the [configuration](Configuration) 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. \ No newline at end of file diff --git a/v0.2/EventLogger.md b/v0.2/EventLogger.md deleted file mode 100644 index 9d0c858..0000000 --- a/v0.2/EventLogger.md +++ /dev/null @@ -1,21 +0,0 @@ -# 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) 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 \ No newline at end of file diff --git a/v0.2/FC0013.md b/v0.2/FC0013.md deleted file mode 100644 index 46b608c..0000000 --- a/v0.2/FC0013.md +++ /dev/null @@ -1,5 +0,0 @@ -# RTL-2832 with Fitipower FC0013 Tuner # - -Coming soon. - -http://www.nooelec.com/store/sdr/sdr-receivers. \ No newline at end of file diff --git a/v0.2/Fleetsync2.md b/v0.2/Fleetsync2.md deleted file mode 100644 index b8081bb..0000000 --- a/v0.2/Fleetsync2.md +++ /dev/null @@ -1,35 +0,0 @@ -# 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. - -## 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 - -## Decoder Setup - Conventional or Repeater Network ## - -Setup a decoding channel with a NBFM decoder and select MDC1200 in the aux -decoder configuration tab. - -## Decoder Setup - Analog Trunked Network ## - -Setup a decoding channel with one of the analog trunked radio decoders (LTR, -LTRNet, Passport, etc) and select MDC1200 in the aux decoder configuration tab. \ No newline at end of file diff --git a/v0.2/FuncubeDonglePro.md b/v0.2/FuncubeDonglePro.md deleted file mode 100644 index 5204f4c..0000000 --- a/v0.2/FuncubeDonglePro.md +++ /dev/null @@ -1,42 +0,0 @@ -# Funcube Dongle Pro Tuner # - -![](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. \ No newline at end of file diff --git a/v0.2/FuncubeDongleProPlus.md b/v0.2/FuncubeDongleProPlus.md deleted file mode 100644 index 8f195a4..0000000 --- a/v0.2/FuncubeDongleProPlus.md +++ /dev/null @@ -1,34 +0,0 @@ -# Funcube Dongle Pro Plus Tuner # - -![](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 \ No newline at end of file diff --git a/v0.2/GettingStarted.md b/v0.2/GettingStarted.md deleted file mode 100644 index 66b483a..0000000 --- a/v0.2/GettingStarted.md +++ /dev/null @@ -1,83 +0,0 @@ -## Getting started with SDRTrunk ## - -SDRtrunk is an integrated application for demodulating radio signals and -decoding trunked radio network and some related radio signal formats. The -application does NOT require a discriminator tapped scanner and it does NOT -require the use of audio piping applications like Virtual Audio Cable. All -connections between the tuner or sound card and the decoders is provided by the -sdrtrunk application. - -SDRTrunk uses channel configurations to setup a demodulation and decoder -processing sequence. In order to successfully decode radio signals, each -channel configuration requires: - -* **Source** - specifies where to get the radio samples from (tuner or sound card) -* **Decoder** - which demodulator or decoder to use in processing the source samples - -Each channel configuration allows you to optionally configure: - -* **Aux Decoder** - additional in-band audio protocols -* **Logging** - log decoded messages or events -* **Recording** - record audio calls or digitized baseband samples - -The SDRTrunk application is programmed in Java and can run on any computer where -the there is Java available for the operating system and the computer hardware -(processor/memory) is sufficient for the processing workload. - -### Setup ### - - * [Linux](SetupLinux) - * [Windows](SetupWindows) - -### Application Overview ### - -The [application overview](ApplicationOverview) article describes the various -components in the sdrtrunk application - -### Configuration ### - -The configuration window/tab at the center of the application is the central -control for configuring tuners and creating/managing channel configurations, -aliases and channel maps. - -Channels are organized by [System](System) and [Site](Site). The system and -site labels can be anything that you want to name them and allow you to setup -your configurations to mirror actual radio network configurations. - -### Setup a Channel for Decoding ### - -In the Configuration tab at the center of the application window: - -1. Click on the 'Tuners' tree branch and verify that the application recognized one or more [tuners](Tuner). -1. Right-click on 'Systems' tree branch and create a system - type a system name and click 'Save' in the editor. -1. Right-click on the system tree branch that you created and add a Site - type a site name and click 'Save' in the editor. -1. Right-click on the site tree branch that you created and add a Channel. -1. Type in the channel name. -1. In the Source tab, select Tuner from the Source drop-down menu and type in the frequency that you want to monitor -1. In the Decoder tab, select a decoder. The default options can be changed, but should be sufficient for a quick start. -1. Click 'enabled' so that channel decoding starts when you hit save. -1. Click the save button. - -If everything is configured correctly and the application can use the tuner to -tune to the frequency that you entered, you should see a [channel](DecodingChannel) -display appear in the lower-left corner of the application that will show the -status of the decoding process. - -Click on this [channel](DecodingChannel) to select it. Then, click on the -[Messages](Messages) tab or the [Events](CallEvents) tab to see the decoding -results. - -### Alternate Quick Start - SDR Dongle ### - -1. In the Configuration tab, select a tuner to display in the spectral display -by right-clicking on the tuner tree branch and select 'Show in Main Spectrum'. -1. Left-click the tuner and in the [editor](Editor) window, 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. -1. Right-click on the frequency in the [spectral display](SpectralDisplay) and -choose **Add Decoder** and select the type of decoder that you want to use. -1. If a tuner is available, the channel will immediately start decoding with -default settings and a [channel](DecodingChannels) will appear in the lower-left -window of the application. Left-click the channel display to select the channel -and then click on the Messages or Events tab to see the decoding results. diff --git a/v0.2/HackRF.md b/v0.2/HackRF.md deleted file mode 100644 index 31d1faa..0000000 --- a/v0.2/HackRF.md +++ /dev/null @@ -1,87 +0,0 @@ -# HackRF # - -![](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. \ No newline at end of file diff --git a/v0.2/LTR.md b/v0.2/LTR.md deleted file mode 100644 index 2b9ea56..0000000 --- a/v0.2/LTR.md +++ /dev/null @@ -1,14 +0,0 @@ -# LTR Standard Decoder # - -## Squelch Control ## - -The LTR decoder provides signaling-based squelch control. - -## 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 to identify these as FCC Callsign Broadcasts: - - * `*`-`*``*`-255 FCC CWID - -![](images/ltr_decoding.png) - \ No newline at end of file diff --git a/v0.2/LTRNet.md b/v0.2/LTRNet.md deleted file mode 100644 index 3d8e550..0000000 --- a/v0.2/LTRNet.md +++ /dev/null @@ -1,65 +0,0 @@ -# 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 signaling-based audio squelch control. - -## 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) 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 - -![](images/ltrnet_decoding.png) - \ No newline at end of file diff --git a/v0.2/LoJack.md b/v0.2/LoJack.md deleted file mode 100644 index 94285fe..0000000 --- a/v0.2/LoJack.md +++ /dev/null @@ -1,23 +0,0 @@ -# LJ1200 Decoder # - -LoJack is a vehicle and equipment tracking and recovery service that is available -in a number of cities in the US. The network broadcasts a series of data -messages on 173.075 MHz to transponders installed in each tracked vehicle or -piece of equipment. This decoder processes these network broadcast messages. - -## LoJack Alias ID ## - -The LoJack alias identifier allows you to specify a function code and tower ID -or transponder ID to associate with an alias. - -## ESN Alias ID ## - -The ESN ID alias can be used to match a vehicle transponder address. - -## Decoder Setup ## - -Setup a decoding channel with a NBFM decoder and specify a tuner frequency of -173.075 in the source configuration tab. Select LJ1200 in the aux decoder -configuration tab. - - diff --git a/v0.2/MDC1200.md b/v0.2/MDC1200.md deleted file mode 100644 index 43dfe83..0000000 --- a/v0.2/MDC1200.md +++ /dev/null @@ -1,22 +0,0 @@ -# MDC-1200 Decoder # - -The MDC-1200 decoder processes Automatic Number Identification (ANI) data -bursts that are used in some analog radio networks to identify individual radios -each time they broadcast on the repeater or trunked radio channel. - -Note: this decoder doesn't currently provide error detection and correction and -therefore it may produce invalid decoded messages. If you have access to a -radio with MDC1200 capability and can provide quality audio recordings of the -various data bursts, please contact the author via the Google support group. - -## Decoder Setup - Conventional or Repeater Network ## - -Setup a decoding channel with a NBFM decoder and select MDC1200 in the aux -decoder configuration tab. - -## Decoder Setup - Analog Trunked Network ## - -Setup a decoding channel with one of the analog trunked radio decoders (LTR, -LTRNet, Passport, etc) and select MDC1200 in the aux decoder configuration tab. - - diff --git a/v0.2/MPT1327.md b/v0.2/MPT1327.md deleted file mode 100644 index f239072..0000000 --- a/v0.2/MPT1327.md +++ /dev/null @@ -1,59 +0,0 @@ -# MPT-1327 # - -The MPT-1327 decoder provides decoding of both control and traffic channel -signaling and trunked traffic channel following. - -## Trunked Channel Following ## - -Configure the MPT-1327 decoder to process the system control channel and specify -a channel map. The application will automatically detect call events and -dynamically create a traffic channel to monitor these calls and end the traffic -channel whenever the channel timeout occurs, or the end of call is detected. - -Each system that you monitor may have different call timeouts. You can change -this timeout from the default 45 seconds to meet your needs. However, if you -specify a long timeout and the end of call is not detected, you'll have a long -period of static at the end of your calls and recordings. - -Specify the maximum number of traffic channels that the decoder can allocate -simultaneously in order to keep total processing to a level that your computer -can handle. You may have to experiment with this value in order to keep the -application from allocating more channels than your computer can process. Start -with 1 traffic channel and monitor your computer's CPU and memory to see how it -responds. Keep increasing the traffic channel count and restart the channel -until you find the maximum number of traffic channels that your computer can -process and then consider reducing that count by one or two. - -## Channel Map ## -You must specify a channel map name in the decoder configuration in order for -trunked channel following to work. Otherwise, the application does not know -about the channel number to frequency mapping. You can run the decoder without -a chanel map against control and traffic channels, however no trunked channel -following will occur. - -If you don't know what the [channel map](ChannelMap) is, you can try to find the license -for the system that specifies the frequencies for the system. Configure an -sdrtrunk channel to monitor each frequency and after successfully decoding a -call, look at the messages tab. The end of call signaling messages tell the mobile -radio what channel it is currently on, and what the channel number is for the -control channel that the mobile radio must return to. You can use these -channel numbers to determine the channel map. If you need help, use the -radioreference.com forums, or post a help request in the sdrtrunk support group. -There is also a wiki page on radioreference.com that details how to calculate -the channel map from known frequency to channel number pairings. - -## Squelch Control ## - -When moniting a control channel the audio is muted. When monitoring a traffic -channel, audio squelch is controlled by the call start and call end signaling that -is decoded on the traffic channel. - -## Talkgroups ## - -The following talkgroups are used in all MPT-1327 systems. Create an alias -group containing the following MPT-1327 system idents: - - * `*``*``*`-8185 = System Register - * `*``*``*`-8190 = System Controller - -![](images/mpt1327_decoding.png) diff --git a/v0.2/Map.md b/v0.2/Map.md deleted file mode 100644 index 50ad714..0000000 --- a/v0.2/Map.md +++ /dev/null @@ -1,17 +0,0 @@ -# Map # - -The map displays any decoded messages that contain location data like GPS positions. - -The map component uses [aliases](Alias) 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 re-center 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. - -![](images/map.png) diff --git a/v0.2/Messages.md b/v0.2/Messages.md deleted file mode 100644 index 675b478..0000000 --- a/v0.2/Messages.md +++ /dev/null @@ -1,5 +0,0 @@ -# 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. - -![](images/messages.png) diff --git a/v0.2/NBFM.md b/v0.2/NBFM.md deleted file mode 100644 index f0e77a3..0000000 --- a/v0.2/NBFM.md +++ /dev/null @@ -1,7 +0,0 @@ -# NBFM Decoder # - -The NBFM decoder is a simple FM demodulator. You can use any of the [auxiliary decoders](Decoder) in conjunction with the NBFM decoder. - -## Squelch Control ## - -The NBFM doesn't provide any squelch control. \ No newline at end of file diff --git a/v0.2/NonRecordable.md b/v0.2/NonRecordable.md deleted file mode 100644 index 64b4621..0000000 --- a/v0.2/NonRecordable.md +++ /dev/null @@ -1,15 +0,0 @@ -# Non-Recordable # - -Any alias can be designated as non-recordable. - -Audio recording can be enabled for all calls that occur on the decoding channel. -By using the non-recordable alias setting, you can designate certain aliases -to not be recorded. - -When you are initially monitoring a new system, this feature allows you to record -every call. Then, as you identify each user or group on the system, you can -create an alias for the group and designate the group as non-recordable. -Eventually, you record fewer groups until you identify all of the users on the -system. - -![](images/non_recordable.png) diff --git a/v0.2/Passport.md b/v0.2/Passport.md deleted file mode 100644 index 734497a..0000000 --- a/v0.2/Passport.md +++ /dev/null @@ -1,41 +0,0 @@ -# Passport # - -The passport decoder will decode the Outbound Status Word (OSW) messages and -signaling that are transmitted by the network to the mobile radio. Passport -systems do not have dedicated control channels, therefore this decoder does not -support trunked channel following. - -## 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 signaling-based squelch control. - -## Aliases ## - -If you are in the United States, and your Passport network may occasionally -broadcast its FCC station callsign. Add the following alias and talkgroup -identifier to your alias list to automatically identify these station ID -call events: - - * 65535 FCC CWID - -## Passport Decode Example ## - -The below screenshot shows a passport channel being decoded where the system -also uses the Fleetsync auxiliary protocol overlay. SDRTrunk decodes both the -passport signaling and the fleetsync data bursts and displays the decoded -information. In this instance, the mobile radio is transmitting an automatic - Fleetsync GPS location report without the user's input. - -![](images/passport_decoding.png) \ No newline at end of file diff --git a/v0.2/Playlist.md b/v0.2/Playlist.md deleted file mode 100644 index 4fd3911..0000000 --- a/v0.2/Playlist.md +++ /dev/null @@ -1,11 +0,0 @@ -# Playlist # - -The playlist contains a folder for each of the following: - - * [Alias Lists](AliasList) - alias lists that can be attached to each decoding channel - * [Channel Maps](ChannelMap) - required for certain decoders like MPT-1327 - * [Systems](System) - all configured decoding channels, arranged by System and Site - -Note: the Systems, Channel Maps and Alias Lists folders cannot be deleted or changed. - -![](images/Configuration.png) \ No newline at end of file diff --git a/v0.2/R820T.md b/v0.2/R820T.md deleted file mode 100644 index b5265f1..0000000 --- a/v0.2/R820T.md +++ /dev/null @@ -1,7 +0,0 @@ -# RTL-2832 with Rafael Micro R820T Tuner # - -http://www.nooelec.com/store/sdr/sdr-receivers.html - -Windows Users: R820T support requires installation of Zadig driver: - -http://zadig.akeo.ie \ No newline at end of file diff --git a/v0.2/ScreenCapture.md b/v0.2/ScreenCapture.md deleted file mode 100644 index 6240f04..0000000 --- a/v0.2/ScreenCapture.md +++ /dev/null @@ -1,5 +0,0 @@ -# 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. \ No newline at end of file diff --git a/v0.2/SetupLinux.md b/v0.2/SetupLinux.md deleted file mode 100644 index 4d09762..0000000 --- a/v0.2/SetupLinux.md +++ /dev/null @@ -1,22 +0,0 @@ -1. Install Java JRE version 7 or newer from http://www.oracle.com/java. Note: if you are using airspy or hackrf, your computer should have 8GB or more of memory and you should use the 64-bit (x64) version of the java JRE. - -2. Verify java installation: - -``` -console: 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. Download the sdrtrunk application and decompress the file. - -4. Install udev rules file for any tuners you'll be using into the /etc/udev/rules.d/ directory. The **funcube-dongle.rules**, **52-airspy.rules**, **53-hackrf.rules**, and **rtl-sdr.rules** files are included in the /config directory - -5. Run the SDRTrunk start script: - -``` -console: cd (unzip folder)/sdrtrunk -console: ./run_sdrtrunk_linux.sh -``` \ No newline at end of file diff --git a/v0.2/SetupWindows.md b/v0.2/SetupWindows.md deleted file mode 100644 index df3fa23..0000000 --- a/v0.2/SetupWindows.md +++ /dev/null @@ -1,19 +0,0 @@ -1. Install Java JRE version 7 or newer from http://www.oracle.com/java. Note: if you are using the airspy or hackrf tuners, your computer should have 8GB of memory or more and use the 64-bit (x64) version of the java JRE. - -2. In a command prompt, verify your 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. Download the sdrtrunk application and unzip the file. - -4. Run the SDRTrunk start script: - -``` -(unzip folder)\sdrtrunk\run_sdrtrunk_windows.bat -``` \ No newline at end of file diff --git a/v0.2/Site.md b/v0.2/Site.md deleted file mode 100644 index bc8c4ad..0000000 --- a/v0.2/Site.md +++ /dev/null @@ -1,23 +0,0 @@ -# Site # - -A site is the next level below a [System](System) for managing a set of [channels](Channel). Use a different site for each trunked radio tower location, or to organize a collection of related channels. - -When a [Channel](Channel) within the [Site](Site) is actively decoding, the system icon is colored Green. - -![](images/Site.png) - -# Creating a New Site # - -2. Right-click on a [System](System) folder and select 'New Site'. - -3. Select the new [Site](Site) and update the name in the editor. Click 'Save'. - -# Deleting a Site # - -2. Right-click on the [Site](Site) and select 'Delete' - -# Changing a Site Name # - -2. Select the site from the list. - -3. Update the name in the editor and click 'Save' \ No newline at end of file diff --git a/v0.2/SoundCard.md b/v0.2/SoundCard.md deleted file mode 100644 index 78e7d98..0000000 --- a/v0.2/SoundCard.md +++ /dev/null @@ -1,7 +0,0 @@ -# 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) 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. \ No newline at end of file diff --git a/v0.2/SpectralDisplay.md b/v0.2/SpectralDisplay.md deleted file mode 100644 index 96b579f..0000000 --- a/v0.2/SpectralDisplay.md +++ /dev/null @@ -1,59 +0,0 @@ -# Introduction # - -The spectral display component shows the frequency activity of the currently selected tuner and all configured decoder channels. - -## Cursor ## -A cursor with frequency readout is automatically shown as you move the mouse about the spectral display window. When zoomed -in, the zoom level is also displayed below the frequency value. - -![](images/spectral_display.png) - -## Zoom ## -The spectral and waterfall displays can be zoomed together using the mouse scroll wheel, or using the right-click context menu. - -When zoomed in, a small zoom window appears at the bottom of the waterfall display indicating the area of the spectral and waterfall displays that is visible and the zoom level. You can left click drag the display with the mouse when zoomed in to drag the display left or right. The zoom control - -![](images/zoom_window.png) - -## 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) 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) 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) 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 Discrete Fourier Transform (DFT) results that are displayed in the spectral display. -* **Averaging** - sets the averaging window size. Averaging occurs over multiple sets of DFT results. -* **Channel** - controls display of channel overlays. Choose to display ALL, NONE, or only the channels currently ENABLED and decoding. -* **FFT Width** - bin size used in DFT 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 DFT is calculated and the spectral display is updated. -* **Window Type** - specifies the windowing method to use prior to calculating the DFT. Windowing minimizes signals from bleeding over into neighboring DFT bins. -* **Smoothing** - sets the smoothing filter type. Smoothing is applied across DFT bins within the same DFT result set. - -### Zoom Menu ### - -Changes the zoom size where 1x is no zoom and 64x is the display zoomed in 64 times. - -## Changing Displayed [Tuner](Tuner) ## - -Right-click on the desired tuner in the [Configuration](Configuration) window and select **Show in Main Spectrum**, or choose **New Spectrum Window** to create a new, separate Spectral Display and Waterfall. \ No newline at end of file diff --git a/v0.2/System.md b/v0.2/System.md deleted file mode 100644 index 8491d01..0000000 --- a/v0.2/System.md +++ /dev/null @@ -1,29 +0,0 @@ -# System # - -A system is a top-level folder for managing a set of [sites](Site) and [channels](Channel). 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. - -![](images/System.png) - -# Creating a New System # - -1. Expand the [Playlist](Playlist) folder and the [Systems](Systems) folder - -2. Right-click on the [Systems](Systems) folder and select 'New System'. - -3. Select the new [System](System) folder and update the system name in the editor. Click 'Save'. - -# Deleting a System # - -1. Expand the [Playlist](Playlist) folder and the [Systems](Systems) folder - -2. Right-click on the [System](System) and select 'Delete' - -# Changing a System Name # - -1. Expand the [Playlist](Playlist) folder and the [Systems](Systems) folder - -2. Select the system from the list. - -3. Update the system name in the editor and click 'Save' \ No newline at end of file diff --git a/v0.2/Tait1200.md b/v0.2/Tait1200.md deleted file mode 100644 index af85a2f..0000000 --- a/v0.2/Tait1200.md +++ /dev/null @@ -1,19 +0,0 @@ -# Tait 1200 Decoder # - -The Tait 1200 decoder processes audio band GPS location bursts. - -Note: the decoder only decodes GPS data bursts. If you have access to a Tait -radio with GPS and can provide additional quality audio recordings of data -bursts from the radio, please contact the author in the Google support group. - -## Decoder Setup - Conventional or Repeater Network ## - -Setup a decoding channel with a NBFM decoder and select Tait 1200 in the aux -decoder configuration tab. - -## Decoder Setup - Analog Trunked Network ## - -Setup a decoding channel with one of the analog trunked radio decoders (LTR, -LTRNet, Passport, etc) and select Tait 1200 in the aux decoder configuration tab. - - diff --git a/v0.2/Tuner.md b/v0.2/Tuner.md deleted file mode 100644 index fc773a2..0000000 --- a/v0.2/Tuner.md +++ /dev/null @@ -1,30 +0,0 @@ -# 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. - -![](images/Tuners.png) - -## Supported Tuners ## - -The following tuners are currently supported by the SDRTrunk application. Additional tuner support will be added in the future. - - * [Airspy](Airspy) - * [Ettus B100/WBX Daughter Card](B100)** - (planned). SDRTrunk will recognize the B100 but it will not allow you to use or configure the B100 - * [Funcube Dongle Pro](FuncubeDonglePro) (1.0) - * [Funcube Dongle Pro Plus](FuncubeDongleProPlus) (2.0) - * [HackRF](HackRF) - * [RTL-2832 with Elonics E4000](E4000) - * [RTL-2832 with Rafael Micro R820T or R820T2](R820T) - -## 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 will not start and will be disabled. - -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 adjust the center frequency to provide a best-fit of all of the requested channels, while ensuring that no channels overlap any DC-spike that may be present in the center of the spectrum for some types of tuners. - -## Visualizing the Tuner Spectrum ## -On startup, SDRTrunk automatically displays the first discovered tuner in the [Spectral Display](SpectralDisplay). 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. \ No newline at end of file diff --git a/v0.2/UserManual.md b/v0.2/UserManual.md deleted file mode 100644 index 8b5df82..0000000 --- a/v0.2/UserManual.md +++ /dev/null @@ -1,54 +0,0 @@ -# SDRTrunk Version 0.2.x User's Manual # - -#[Getting Started](GettingStarted)# - -#[Application Overview](ApplicationOverview)# - -#Aliases# - -* [Alias List](AliasList) -* [Alias Group](AliasGroup) -* [Alias](Alias) -* [Alias Actions](AliasAction) - -#Auxiliary Decoders# - -* [Fleetsync II](Fleetsync2) -* [MDC1200](MDC1200) - -#[Configuration](Configuration)# - -* [Alias Lists](AliasList) -* [Channel Maps](ChannelMap) -* [Playlist](Playlist) - -#Decoders# - -* [LTR](LTR) -* [LTRNet](LTRNet) -* [MPT1327](MPT1327) -* [NBFM](NBFM) -* [Passport](Passport) - -#Logging# - -* [Application Log](ApplicationLog) -* [Event Log](EventLogger) - -#[Recorder](Recorder)# - -#Source and [Tuners](Tuner)# - -* [Sound Card](SoundCard) -* [Airspy](Airspy) -* [Ettus Research B100](B100) -* [Funcube Dongle Pro](FuncubeDonglePro) -* [Funcube Dongle Pro Plus](FuncubeDongleProPlus) -* [RTL-2832 with E4000 Tuner](E4000) -* [RTL-2832 with FC0013 Tuner](FC0013) -* [RTL-2832 with R820T Tuner](R820T) - -#[Screen Captures](ScreenCapture)# - -#[Streaming](Streaming)# - diff --git a/v0.2/WaterfallDisplay.md b/v0.2/WaterfallDisplay.md deleted file mode 100644 index e597dcd..0000000 --- a/v0.2/WaterfallDisplay.md +++ /dev/null @@ -1,15 +0,0 @@ -# Waterfall Display # - -The waterfall display shows a history of the frequency content of the currently displayed [tuner](Tuner). - -![](images/waterfall.png) - -## Context Menus ## - -Right-click anywhere in the waterfall display to view a list of context-sensitive menu options. See the [Spectral Display](SpectralDisplay) 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. - -Note: if you see a signal in the waterfall, you can pause the waterfall and use the zoom control to zoom in on the transmission to inspect the bandwidth and frequency, or other features of the signal. You can optionally expand the viewable height of the waterfall window to view waterfall signals that appear to have scrolled off the screen. There is a limited history available. - -![](images/waterfall_paused.png) diff --git a/v0.2/images/Alias.png b/v0.2/images/Alias.png deleted file mode 100644 index 92fb148..0000000 Binary files a/v0.2/images/Alias.png and /dev/null differ diff --git a/v0.2/images/AliasActions.png b/v0.2/images/AliasActions.png deleted file mode 100644 index ffe3b3f..0000000 Binary files a/v0.2/images/AliasActions.png and /dev/null differ diff --git a/v0.2/images/AliasESNID.png b/v0.2/images/AliasESNID.png deleted file mode 100644 index eb33a5f..0000000 Binary files a/v0.2/images/AliasESNID.png and /dev/null differ diff --git a/v0.2/images/AliasFleetsyncID.png b/v0.2/images/AliasFleetsyncID.png deleted file mode 100644 index eaa913f..0000000 Binary files a/v0.2/images/AliasFleetsyncID.png and /dev/null differ diff --git a/v0.2/images/AliasGroup.png b/v0.2/images/AliasGroup.png deleted file mode 100644 index dc96a9b..0000000 Binary files a/v0.2/images/AliasGroup.png and /dev/null differ diff --git a/v0.2/images/AliasList.png b/v0.2/images/AliasList.png deleted file mode 100644 index dc3d451..0000000 Binary files a/v0.2/images/AliasList.png and /dev/null differ diff --git a/v0.2/images/AliasMDC1200ID.png b/v0.2/images/AliasMDC1200ID.png deleted file mode 100644 index 9bb96d2..0000000 Binary files a/v0.2/images/AliasMDC1200ID.png and /dev/null differ diff --git a/v0.2/images/AliasMIDID.png b/v0.2/images/AliasMIDID.png deleted file mode 100644 index 4e7a9bb..0000000 Binary files a/v0.2/images/AliasMIDID.png and /dev/null differ diff --git a/v0.2/images/AliasMPT1327ID.png b/v0.2/images/AliasMPT1327ID.png deleted file mode 100644 index 151e04e..0000000 Binary files a/v0.2/images/AliasMPT1327ID.png and /dev/null differ diff --git a/v0.2/images/AliasSiteID.png b/v0.2/images/AliasSiteID.png deleted file mode 100644 index 883cfde..0000000 Binary files a/v0.2/images/AliasSiteID.png and /dev/null differ diff --git a/v0.2/images/AliasStatusID.png b/v0.2/images/AliasStatusID.png deleted file mode 100644 index a23bcf1..0000000 Binary files a/v0.2/images/AliasStatusID.png and /dev/null differ diff --git a/v0.2/images/AliasTalkgroupID.png b/v0.2/images/AliasTalkgroupID.png deleted file mode 100644 index 4d60615..0000000 Binary files a/v0.2/images/AliasTalkgroupID.png and /dev/null differ diff --git a/v0.2/images/AliasUniqueID.png b/v0.2/images/AliasUniqueID.png deleted file mode 100644 index 3665e80..0000000 Binary files a/v0.2/images/AliasUniqueID.png and /dev/null differ diff --git a/v0.2/images/Aliases.png b/v0.2/images/Aliases.png deleted file mode 100644 index facf13a..0000000 Binary files a/v0.2/images/Aliases.png and /dev/null differ diff --git a/v0.2/images/CallEvents.png b/v0.2/images/CallEvents.png deleted file mode 100644 index bf22c0c..0000000 Binary files a/v0.2/images/CallEvents.png and /dev/null differ diff --git a/v0.2/images/Channel.png b/v0.2/images/Channel.png deleted file mode 100644 index cadb2ef..0000000 Binary files a/v0.2/images/Channel.png and /dev/null differ diff --git a/v0.2/images/ChannelMap.png b/v0.2/images/ChannelMap.png deleted file mode 100644 index 1d29596..0000000 Binary files a/v0.2/images/ChannelMap.png and /dev/null differ diff --git a/v0.2/images/ChannelsAuxDecoderEditor.png b/v0.2/images/ChannelsAuxDecoderEditor.png deleted file mode 100644 index f75fcc0..0000000 Binary files a/v0.2/images/ChannelsAuxDecoderEditor.png and /dev/null differ diff --git a/v0.2/images/ChannelsDecoderEditor.png b/v0.2/images/ChannelsDecoderEditor.png deleted file mode 100644 index 1407262..0000000 Binary files a/v0.2/images/ChannelsDecoderEditor.png and /dev/null differ diff --git a/v0.2/images/ChannelsLoggingEditor.png b/v0.2/images/ChannelsLoggingEditor.png deleted file mode 100644 index 6a08758..0000000 Binary files a/v0.2/images/ChannelsLoggingEditor.png and /dev/null differ diff --git a/v0.2/images/ChannelsNameEditor.png b/v0.2/images/ChannelsNameEditor.png deleted file mode 100644 index 4b9858f..0000000 Binary files a/v0.2/images/ChannelsNameEditor.png and /dev/null differ diff --git a/v0.2/images/ChannelsRecordingEditor.png b/v0.2/images/ChannelsRecordingEditor.png deleted file mode 100644 index 0761107..0000000 Binary files a/v0.2/images/ChannelsRecordingEditor.png and /dev/null differ diff --git a/v0.2/images/ChannelsSourceEditor.png b/v0.2/images/ChannelsSourceEditor.png deleted file mode 100644 index 57888ce..0000000 Binary files a/v0.2/images/ChannelsSourceEditor.png and /dev/null differ diff --git a/v0.2/images/Configuration.png b/v0.2/images/Configuration.png deleted file mode 100644 index e6ab022..0000000 Binary files a/v0.2/images/Configuration.png and /dev/null differ diff --git a/v0.2/images/E4000.png b/v0.2/images/E4000.png deleted file mode 100644 index ba6d5dd..0000000 Binary files a/v0.2/images/E4000.png and /dev/null differ diff --git a/v0.2/images/E4000_V0.3.0.png b/v0.2/images/E4000_V0.3.0.png deleted file mode 100644 index e528191..0000000 Binary files a/v0.2/images/E4000_V0.3.0.png and /dev/null differ diff --git a/v0.2/images/FuncubeDonglePro.png b/v0.2/images/FuncubeDonglePro.png deleted file mode 100644 index ecd8aed..0000000 Binary files a/v0.2/images/FuncubeDonglePro.png and /dev/null differ diff --git a/v0.2/images/FuncubeDongleProPlus.png b/v0.2/images/FuncubeDongleProPlus.png deleted file mode 100644 index 4361a5c..0000000 Binary files a/v0.2/images/FuncubeDongleProPlus.png and /dev/null differ diff --git a/v0.2/images/HackRF.png b/v0.2/images/HackRF.png deleted file mode 100644 index 09de78c..0000000 Binary files a/v0.2/images/HackRF.png and /dev/null differ diff --git a/v0.2/images/MultipleAliasEditor.png b/v0.2/images/MultipleAliasEditor.png deleted file mode 100644 index 9849665..0000000 Binary files a/v0.2/images/MultipleAliasEditor.png and /dev/null differ diff --git a/v0.2/images/Overview.png b/v0.2/images/Overview.png deleted file mode 100644 index e9017c7..0000000 Binary files a/v0.2/images/Overview.png and /dev/null differ diff --git a/v0.2/images/P25Decoder.png b/v0.2/images/P25Decoder.png deleted file mode 100644 index b5fff2a..0000000 Binary files a/v0.2/images/P25Decoder.png and /dev/null differ diff --git a/v0.2/images/SDRTrunk_application.png b/v0.2/images/SDRTrunk_application.png deleted file mode 100644 index 06f67b0..0000000 Binary files a/v0.2/images/SDRTrunk_application.png and /dev/null differ diff --git a/v0.2/images/ScriptAction.png b/v0.2/images/ScriptAction.png deleted file mode 100644 index cf9ade5..0000000 Binary files a/v0.2/images/ScriptAction.png and /dev/null differ diff --git a/v0.2/images/Site.png b/v0.2/images/Site.png deleted file mode 100644 index 65d7dfe..0000000 Binary files a/v0.2/images/Site.png and /dev/null differ diff --git a/v0.2/images/Streaming.png b/v0.2/images/Streaming.png deleted file mode 100644 index 916ae13..0000000 Binary files a/v0.2/images/Streaming.png and /dev/null differ diff --git a/v0.2/images/StreamingStatusPanel.png b/v0.2/images/StreamingStatusPanel.png deleted file mode 100644 index 7eab990..0000000 Binary files a/v0.2/images/StreamingStatusPanel.png and /dev/null differ diff --git a/v0.2/images/System.png b/v0.2/images/System.png deleted file mode 100644 index 9549bd5..0000000 Binary files a/v0.2/images/System.png and /dev/null differ diff --git a/v0.2/images/Tuners.png b/v0.2/images/Tuners.png deleted file mode 100644 index baeecf9..0000000 Binary files a/v0.2/images/Tuners.png and /dev/null differ diff --git a/v0.2/images/airspy.png b/v0.2/images/airspy.png deleted file mode 100644 index 29359f3..0000000 Binary files a/v0.2/images/airspy.png and /dev/null differ diff --git a/v0.2/images/audio_muted.png b/v0.2/images/audio_muted.png deleted file mode 100644 index 56fd5f7..0000000 Binary files a/v0.2/images/audio_muted.png and /dev/null differ diff --git a/v0.2/images/call_priority.png b/v0.2/images/call_priority.png deleted file mode 100644 index b597323..0000000 Binary files a/v0.2/images/call_priority.png and /dev/null differ diff --git a/v0.2/images/call_state.png b/v0.2/images/call_state.png deleted file mode 100644 index 85b3668..0000000 Binary files a/v0.2/images/call_state.png and /dev/null differ diff --git a/v0.2/images/channel_spectrum.png b/v0.2/images/channel_spectrum.png deleted file mode 100644 index af7c10c..0000000 Binary files a/v0.2/images/channel_spectrum.png and /dev/null differ diff --git a/v0.2/images/channel_state.png b/v0.2/images/channel_state.png deleted file mode 100644 index 2b98655..0000000 Binary files a/v0.2/images/channel_state.png and /dev/null differ diff --git a/v0.2/images/control_state.png b/v0.2/images/control_state.png deleted file mode 100644 index 3f99bc3..0000000 Binary files a/v0.2/images/control_state.png and /dev/null differ diff --git a/v0.2/images/data_state.png b/v0.2/images/data_state.png deleted file mode 100644 index d0ef0ff..0000000 Binary files a/v0.2/images/data_state.png and /dev/null differ diff --git a/v0.2/images/fade_state.png b/v0.2/images/fade_state.png deleted file mode 100644 index 911f0e8..0000000 Binary files a/v0.2/images/fade_state.png and /dev/null differ diff --git a/v0.2/images/idle_state.png b/v0.2/images/idle_state.png deleted file mode 100644 index 6833eb9..0000000 Binary files a/v0.2/images/idle_state.png and /dev/null differ diff --git a/v0.2/images/ltr_decoding.png b/v0.2/images/ltr_decoding.png deleted file mode 100644 index d0b3449..0000000 Binary files a/v0.2/images/ltr_decoding.png and /dev/null differ diff --git a/v0.2/images/ltrnet_decoding.png b/v0.2/images/ltrnet_decoding.png deleted file mode 100644 index 363014b..0000000 Binary files a/v0.2/images/ltrnet_decoding.png and /dev/null differ diff --git a/v0.2/images/map.png b/v0.2/images/map.png deleted file mode 100644 index 61f396f..0000000 Binary files a/v0.2/images/map.png and /dev/null differ diff --git a/v0.2/images/messages.png b/v0.2/images/messages.png deleted file mode 100644 index bc5dfb7..0000000 Binary files a/v0.2/images/messages.png and /dev/null differ diff --git a/v0.2/images/mono_audio_panel.png b/v0.2/images/mono_audio_panel.png deleted file mode 100644 index 1de6a68..0000000 Binary files a/v0.2/images/mono_audio_panel.png and /dev/null differ diff --git a/v0.2/images/mpt1327_decoding.png b/v0.2/images/mpt1327_decoding.png deleted file mode 100644 index f718808..0000000 Binary files a/v0.2/images/mpt1327_decoding.png and /dev/null differ diff --git a/v0.2/images/non_recordable.png b/v0.2/images/non_recordable.png deleted file mode 100644 index 8d45b7a..0000000 Binary files a/v0.2/images/non_recordable.png and /dev/null differ diff --git a/v0.2/images/passport_decoding.png b/v0.2/images/passport_decoding.png deleted file mode 100644 index 1bec04f..0000000 Binary files a/v0.2/images/passport_decoding.png and /dev/null differ diff --git a/v0.2/images/spectral_display.png b/v0.2/images/spectral_display.png deleted file mode 100644 index b1b3289..0000000 Binary files a/v0.2/images/spectral_display.png and /dev/null differ diff --git a/v0.2/images/stereo_audio_panel.png b/v0.2/images/stereo_audio_panel.png deleted file mode 100644 index 040c3e4..0000000 Binary files a/v0.2/images/stereo_audio_panel.png and /dev/null differ diff --git a/v0.2/images/waterfall.png b/v0.2/images/waterfall.png deleted file mode 100644 index a02d133..0000000 Binary files a/v0.2/images/waterfall.png and /dev/null differ diff --git a/v0.2/images/waterfall_paused.png b/v0.2/images/waterfall_paused.png deleted file mode 100644 index ffe9657..0000000 Binary files a/v0.2/images/waterfall_paused.png and /dev/null differ diff --git a/v0.2/images/zoom_window.png b/v0.2/images/zoom_window.png deleted file mode 100644 index 530e155..0000000 Binary files a/v0.2/images/zoom_window.png and /dev/null differ diff --git a/v0.3/AM_V0.3.0.md b/v0.3/AM_V0.3.0.md deleted file mode 100644 index 39194b1..0000000 --- a/v0.3/AM_V0.3.0.md +++ /dev/null @@ -1,8 +0,0 @@ -# AM Decoder # - -The Amplitude Modulation (AM) decoder is a simple AM demodulator for monitoring air band and other -amplitude modulated signals. - -## Squelch Control ## - -The AM decoder doesn't provide any audio squelch control. \ No newline at end of file diff --git a/v0.3/APCO25_V0.3.0.md b/v0.3/APCO25_V0.3.0.md deleted file mode 100644 index 473d864..0000000 --- a/v0.3/APCO25_V0.3.0.md +++ /dev/null @@ -1,119 +0,0 @@ -# APCO-25 Decoder # - -The P25 decoder processes all voice, trunking, and data messages and provides -traffic/voice/data call following when a tuner is available that can monitor -both the control channel and any traffic channels within the available bandwidth -of the tuner, or across multiple tuners. - -## P-25 Phase I -Decodes FDMA Common Air Interface (CAI) C4FM modulation and Linear Simulcast -Modulation (LSM). - -## P-25 Phase II -Phase II TDMA (2 timeslot) traffic channel decoding. - -## P-25 Phase I/II -P25 Phase II systems use both a Phase 1 control channel and Phase I and Phase II -traffic channels, providing transition support for users with a combination of -Phase I and Phase II radios. - -## Audio Vocoders - -### IMBE ### -APCO-25 Phase I audio calls use the IMBE vocoder for digital audio. - -### AMBE ### -APCO-25 Phase II audio calls use the AMBE vocoder for digital audio. - -SDRTrunk supports the JMBE library for decoding both IMBE and AMBE digital -audio, but DOES NOT include the jmbe library in the normal application download. -You must download and compile the library and use the **View >> Preferences** menu -to specify the location of the compiled JMBE library (jmbe-x.x.x.jar). - -[JMBE library](https://github.com/DSheirer/jmbe) - -[How To Setup JMBE](JMBE) - -### VSELP ### -SDRTrunk recognizes VSELP audio CODEC messages and will display them in the -messages tab during decoding. However, it will not decode the audio. - -## Traffic Channel Following ## -The P25 decoder provides full traffic channel following when monitoring a P25 -control channel. You can optionally select to not follow data calls in the -decoder configuration when setting up the channel for decoding. - -## Talkgroups and Addresses ## - -All talkgroups and radio addresses are presented in decimal or hexadecimal -(base-16) notation (see Preferences). - -### **Talkgroups**: 1 - 65,535 -### **Individual Radio Identifiers**: 65,636 - 16,777,211 - -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, you can use either a single talkgroup decimal value, or you can enter a range of talkgroup decimal values. - -Optionally, add these trunking system unit ID values to your alias list: - -16,777,212 = (Trunking) System Controller. -16,777,213 = Registration Controller -16,777,215 = All Call - -## Modulation ## - -Choose either C4FM or LSM Simulcast (CQPSK) modulation for Phase 1 channels in the channel configuration -decoder tab. When you select the P25 Decoder from the drop-down list, the -modulation selector list will appear. - -## Monitoring a P25 Trunked System ## - -Setup a channel to decode the trunked system's control channel only. The decoder -will automatically detect when additional traffic channels are allocated for -calls and will create temporary decoding channels in the application to process -each of these calls. - -You do NOT need to create decoding channel configurations for each of the -traffic channel frequencies used by the system because the control channel will -tell the sdrtrunk application every thing that it needs to know in order to -setup a temporary decoding channel. - -**Note**: Phase 2 capable trunked systems will use a Phase 1 control channel -with Phase 2 traffic channels. You only have to setup one channel configuation -for the Phase 1 control channel. The Phase 2 traffic channels will be -automatically created by sdrtrunk as each call occurs. - -### Traffic Channel Pool Size ### - -When configuring the P25 control channel decode configuration, use the Traffic -Channel Pool setting to set the maximum number of temporary traffic channels -that can be running at the same time. The sdrtrunk application will create -channel configurations up to this maximum number and reuse the channel -configurations for subsequent calls. - -The default value of 4 traffic channels in the pool is suitable for a modern -powerful processor. You can increase this value to match the number of traffic -channel frequencies for the system your are monitoring, provided your computer -is capable of running that many channels at the same time. You may have to reduce -this pool size if you are using a lower powered CPU. Monitor the computer's CPU -and memory consumption and adjust this value as needed. Note: you'll have to -stop and restart the decoding after you change the traffic channel pool size -value and save it. - -## P25 Decoding Example ## - -The following screenshot shows the application configured to decode one P25 -control channel. It also shows 3 traffic channels being decoded where the -call event was decoded on the control channel and sdrtrunk automatically -created the 3 decoder channels to follow the calls. - diff --git a/v0.3/Airspy_V0.3.0.md b/v0.3/Airspy_V0.3.0.md deleted file mode 100644 index 13c2c81..0000000 --- a/v0.3/Airspy_V0.3.0.md +++ /dev/null @@ -1,48 +0,0 @@ -# Airspy # - -### Configuration ### - - * **Name** - tuner configuration name. - * **Sample Rate** - select from 10.00 or 2.50 MHz sample rates. Note: the - additional decimation option is not currently supported in sdrtrunk. - * **Gain Mode** - select from LINEARITY, SENSITIVITY, or CUSTOM. Linearity - and sensitivity modes provide a single gain adjustment value that automatically - configures the IF, Mixer and LNA gains for each master gain setting. The - Custom mode disables the single gain adjustment slider and provides access to - each of the IF, Mixer and LNA gain sliders so that you can manually adjust - each gain value to meet your specific needs. - -### Info Tab ### -The info tab displays information about the tuner: - - * **Serial** - serial number of the Airspy tuner. - * **Firmware** - version number of the firmware loaded in the airspy - * **Part** - airspy part number - * **Board ID** - airspy board identifier - -## Using the Airspy ## - -![Figure 1: Airspy Tuner Configuration](v0.3/images/Airspy_V0.3.0.png) - -## 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 support -flashing the Airspy with new firmware. Use the Airspy tools to update the -tuner. - -## Using Airspy With Linux ## - -If you've never setup your airspy for linux, you'll need to add permissions to allow users to access the airspy: - -Download the file [52-airspy.rules](https://github.com/DSheirer/sdrtrunk/blob/master/src/main/resources/52-airspy.rules) and copy to your **\etc\udev\rules.d** folder. - - sudo cp 52-airspy.rules \etc\udev\rules.d - -Set file permissions. - - sudo chmod u=rw,g=r,o=r 52-airspy.rules - -Refresh the udev rules - - sudo udevadm control --reload-rules diff --git a/v0.3/Aliases_V0.3.0.md b/v0.3/Aliases_V0.3.0.md deleted file mode 100644 index 034656b..0000000 --- a/v0.3/Aliases_V0.3.0.md +++ /dev/null @@ -1,589 +0,0 @@ -Table of Contents ---- -* [Creating, Deleting and Copying Aliases](#creating,-deleting-and-copying-aliases) -* [Single Alias Editor - Alias Tab](#single-alias-editor---alias-tab) -* [Single Alias Editor - Audio/Identifier Tab](#single-alias-editor---audio/identifier-tab) - * [Audio and Identifier Items](#audio-and-identifier-items) -* [Single Alias Editor - Action Tab](#single-alias-editor---action-tab) -* [Multiple Alias Editor](#multiple-alias-editor) -* [Examples](#examples) - * [Example: Create Aliases for an Alias List](#example-create-aliases-for-an-alias-list) - * [Example: Attach an Alias List to a Decoding Channel](#example-attach-an-alias-list-to-a-decoding-channel) - * [Example: P25 Aliases](#example-p25-aliases) - * [Example: Audio Priority](#example-audio-priority) - * [Example: Audio Streaming](#example-audio-streaming) - * [Example: Alias with Wildcard P25 Talkgroup](#example-alias-with-wildcard-p25-talkgroup) - * [Example: Audio Recording](#example-audio-recording) - * [Example: LTR Aliases](#example-ltr-aliases) - -Aliases ---- -Aliases are a powerful feature in sdrtrunk that enable you to assign meaning to -many of the logical identifiers found in radio communication systems. An -alias can represent one or more radios, radio groups, people, vehicles, -network nodes, etc. An alias can have multiple associated identifiers that -allow you to link together each of the pieces of information that can be used -to identify something or someone. - -Aliases provide the ability to trigger actions whenever any of the identifiers -that are associated with the alias are active on the radio network. For -instance, you can assign an alias to beep, or popup a message dialog whenever -the alias is active. By assigning a script alias action, the possibilities -are unlimited for triggered actions. - -Aliases also allow you to define audio monitoring priority, recording, and -network audio streaming of audio associated with the alias when active. - -![Figure 1: Alias Table and Single Alias Editor](v0.3/images/Aliases_V0.3.0.png) - -**Figure 1:** Alias Table and Single Alias Editor - -Figure 1 presents the Alias tab showing the alias table and the single alias -editor. In this view, you can select an individual alias row in the table -and the alias editor allows you to change any of the details about the alias -and to add or delete alias identifiers and alias actions. - -Each column in the table provides a drop-down field in the column header -allowing multiple search and row filtering options. - -Each of the single alias editor options are described later in this document. - -![Figure 2: Alias Table and Multiple Alias Editor](v0.3/images/MultipleAliasEditor_V0.3.0.png) - -**Figure 2:** Alias Table and Multiple Alias Editor - -Figure 2 shows the multiple alias editor. By selecting multiple rows of -aliases, you can modify individual settings across a set of aliases with a -single action. - -Click on a check box for a setting that you want to change, type in a value -or select from the list, and click **Save** to change that setting for all -selected aliases. - -Each of the multiple alias editor options are described later in this document - -Creating, Deleting and Copying Aliases ---- -Use the three buttons at the bottom of the alias table to create new aliases, -copy one or more existing aliases, or delete one or more aliases. - -#### New Button -Click the new button to create a new alias. The new alias appears at the bottom -of the alias table. Select the new alias and use the single alias editor pane at -the right to edit the alias settings and save the changes with the **Save** button -at the bottom of the alias editor. - -#### Copy Button -Select one or more aliases that you have already created and click the Copy button -to create duplicate copies of the selected aliases. You can then edit each of the -alias copies individually. This is a convenient feature when you are creating -many aliases that are mostly the same and you only have to change a few settings. - -#### Delete Button -Select one or more aliases and click the Delete button to remove the selected -aliases from the list. - -Single Alias Editor - Alias Tab ---- - -The following are settings that can be modified for each alias. The single -alias editor is shown in Figure 1. - -#### Name -The alias name is the textual value that will be displayed everywhere that the -alias is used. - -#### List -An alias list is a named group of aliases that you attach to one or more -channel configurations. Type in a new alias list name select an existing -alias list name from the list. - -Attach an alias list to a channel configuration and all aliases with the -alias list name will be used by any decoder(s) specified in the channel -configuration. - -#### Group -An alias group is a second grouping option that allows you to better organize -your alias lists and to quickly filter your larger alias lists into manageable -sizes convenient for editing. The alias group value is not used by any of the -decoders and is only provided as a means for you to organize your aliases. - -#### Color -Select a color by clicking on the color bar and choose a color from the -dialog. This color will be used when displaying the alias name or when -plotting the GPS locations and path of travel for an alias on the integrated -map display. NOTE: use caution when choosing a light color or white, because -the text will not be visible against most of the white background displays. - -#### Icon -Choose an icon from the dropdown list or click on the **Icon Manager** button -to import your own custom icon to attach to your alias. The icon will be -displayed next to your alias name and will be used on the integrated map -display when plotting GPS locations. - -#### Save Button -After editing any of the settings in the aliast, click the **Save** button -to save the settings. - -#### Reset Button -Click the reset button if you have made changes to the alias settings and -wish to revert all settings back to the previous saved state. - -Single Alias Editor - Audio/Identifier Tab ---- -This tab allows you to assign one or more identifiers to an alias and to -assign audio settings for priority, recording and streaming. Once you have -attached audio or identifier items to an alias, you can select each item -individually in the list and an editor will appear allowing you to change -the setting(s) for the item. - -#### New Button -Click the new button to choose a new audio or identifier item to attach to -the alias. The items that you can add or attach to an alias are detailed -immediately following the Delete button description. - -#### Clone Button -Select an existing item in the list and click the Clone button to create a -duplicate copy of the item. You can then change the settings for the cloned -copy of the audio or identifier. - -#### Delete Button -Select an existing item in the list that you want to remove from the alias -and click the Delete button. - -Audio and Identifier Items ---- -The following alias identifiers and audio items can be attached to any alias. -Multiple identifiers and identifier types can be attached to each alias. Most -alias identifiers also support wildcard (*) characters. Click the **Help ...** -link in any of the identifier editor windows to view tips and comments on -how to format identifier values for each of the identifier types. - -##### ESN -Electronic Serial Number (ESN) identifiers used in specific decoders like -LTR-Net. - -##### Fleetsync -Kenwood fleetsync radio or group identifier. This identifier only applies to -the Fleetsync decoder. - -##### LoJack -Lojack function and ID. This identifier only applies to the LoJack decoder. - -##### LTRNet UID -LTR-Net Unique ID. This identifier only applies to the LTR-Net decoder. - -##### MDC-1200 -MDC-1200 radio identifier. This identifier only applies to the MDC-1200 -decoder. - -##### MPT-1327 -MPT-1327 radio or group identifier. This identifier only applies to the -MPT-1327 decoder. - -##### Passport MIN -Passport Mobile ID Number (MIN). This identifier only applies to the Passport -decoder. - -##### Site -Radio network site identifier. This identifier is used in the LTR-Net, -MPT-1327 and P25 decoders to allow you to alias each network site with a -meaningful site descriptor label. - -##### Status -Status code identifier. This identifier is used by the Fleetsync and -MPT-1327 decoders. - -##### Talkgroup -Talkgroup or radio identifier. This identifer is used by the P25, LTR -Standard, and Tait 1200 decoders. - -##### Audio Broadcast Channel (Streaming) -This audio setting designates an audio broadcast (streaming) channel. Any -audio calls associated with the alias will be streamed across the specified -streaming channel. See the [Streaming](Streaming_V0.3.0) page for details on -configuring audio streaming channels. - -##### Audio Non-Recordable -This audio setting designates the alias as non-recordable. If you wish to -change the alias and make it recordable again, simply delete the non-recordable -item from the list. - -##### Audio Priority -Assigns an audio listening priority of 1 (highest) to 100 (lowest), or -designates the alias as **Do Not Monitor** when you slide the setting all the -way to the right. - - -Single Alias Editor - Action Tab ---- -You can attach one ore more alias actions to each alias. Alias actions are -performed when any of the identifiers attached to the alias are active on any -radio channels. Each alias action provides timing and periodicity settings that -allow you to customize how and how often the action will be performed. Each -action also provides a **Test** button that allows you to test the action. - -#### New Button -Click the new button and select from the list of available alias actions. - -#### Clone Button -Select one or more alias actions and click the clone button to create an exact -copy of each selected alias action. You can then modify each of the action -copies. - -#### Delete Button -Select one ore more alias actions and click the delete button to remove the -alias action from the alias. - -#### Beep Alias Action -Generates a beep on your computer when the alias is active on one of the channels. - -#### Play Clip Alias Action -Plays a sound clip over your computer speakers when the alias is active. - -#### Run Script Alias Action -Executes a computer script when the alias is active. Create a script that is -compatible with your computer operating system and store it on the hard drive -and then select the script in the script editor window. - -Multiple Alias Editor ---- -The multiple alias editor allows you to modify one or more settings across a -selected set of aliases. Simply use your mouse in combination with the -**Alt** key to select a range of aliases. Use your mouse in combination with -the **Control** key to select multiple individual aliases. - -**NOTE:** The multiple alias editor will only modify those settings that you -have selected by clicking the check box to the left of each setting. You can -modify multiple settings at a time by checking the box next to each setting -that you want to modify. - -#### Save and Reset Buttons -Click the **Save** button to apply any settings that you have changed. Click -the **Reset** button to reset any changes that you have made to the editor -panel, without applying those changes to the selected aliases. - -#### List, Group, Color and Icon -These settings are the same as detailed above for the single alias editor. - -#### Record -Recording is turned on for each individual channel configuration. When -recording is turned on, all calls are recorded. You can designate specific -aliases or groups of aliases to not be recorded by adding the **Non-Recordable** -alias identifier to each alias. - -Choose the **Non-Recordable** option to add the non-recordable alias identifier -to each of the selected aliases. Choos the **Recordable** option to remove -the non-recordable alias identifier from each of the aliases. You can view -the recordable status of each alias the single aliase editor, Audio Identifier -tab. - -#### Priority -Each alias can have an audio monitoring priority. Assign a value of 1 to 100 -where 1 is the highest priority and 100 is the lowest priority. Slide the -audio priority all the way to the right to select a **Do Not Monitor** -priority. Audio from any alias with Do Not Monitor will not be played over -the local speakers. If you do not assign an audio priority to an alias, it -will default to a priority of 100 (lowest). - -#### Streaming -Each alias can be streamed over one or more internet audio streaming -channels. Internet streaming channels can be configured in the **Streaming** -tab. - -Examples ---- - -![Figure 3: New Alias](v0.3/images/AliasCreateNew_V0.3.0.png) - -**Figure 3:** Create New Alias - -Example: Create Aliases for an Alias List ---- -1. Click the Aliases tab in the middle of the application window -1. Click the **New** button to create a new alias. The alias will be added to the list as shown -in **Figure 3** and it will be loaded into the alias editor on the right-hand side of the application window. -1. Add the following attributes to your alias: - * **Name:** ABC Truck 1 - * **List:** ABC Trucking - * **Group:** Local Delivery - * **Color:** Blue - * **Icon:** Van -1. Click the **Save** button -1. The completed alias is shown in **Figure 4** - -Next, we'll clone the first alias to quickly create a second alias. - -1. Select the **ABC Truck 1** alias in the alias table. -1. Click the **Copy** button. The copy is created and auto-selected in the editor. -1. Type a new name for the copy: **ABC Truck 2** -1. Click the **Save** button. - -Next, we'll clone the first alias to quickly create a third alias. - -1. Select the **ABC Truck 1** alias in the alias table. -1. Click the **Copy** button. The copy is created and auto-selected in the editor. -1. Type a new name for the copy: **ABC Trucking-Local** -1. Click the **Save** button. - -Repeat the above steps and add three more aliases with the following details. Use the first set of -steps to create a new **ABC Truck 10** alias, and then use the second set of steps to clone -the alias two more times and then rename the copies to **ABC Truck 11** and **ABC Trucking-Buses**. - -1. Alias: - * **Name:** ABC Truck 10 - * **List:** ABC Trucking - * **Group:** Bus Fleet - * **Color:** Green - * **Icon:** Transport Bus -1. Alias: - * **Name:** ABC Truck 11 - * **List:** ABC Trucking - * **Group:** Bus Fleet - * **Color:** Green - * **Icon:** Transport Bus -1. Alias: - * **Name:** ABC Trucking-Buses - * **List:** ABC Trucking - * **Group:** Bus Fleet - * **Color:** Green - * **Icon:** Transport Bus -1. Your completed aliases should resemble the aliases shown in **Figure 4**. - -![Figure 4: New Aliases - ABC Trucking](v0.3/images/AliasExampleABCTrucking_V0.3.0.png) - -**Figure 4:** New Aliases - ABC Trucking Alias List - -Example: Attach an Alias List to a Decoding Channel ---- -We're going to attach the aliases created in the [first example](#example-create-aliases-for-an-alias-list) -to our P25 decoding channel configuration so that the aliases will be used during decoding. - -Aliases are attached to a channel configuration using the Alias List value that is assigned to -each alias. - -Please refer to the [channels](Channels_V0.3.0) wiki page for help in -creating a channel configuration and enabling the channel for decoding. This example assumes -that you have already created a P25 channel configuration. - -1. Click on the **Channels** tab in the application window. -1. Click on the **Name/Alias** tab in the channel editor window at the bottom. -1. Select **ABC Trucking** in the Alias List dropdown box. -1. Click the **Save** button. -1. Click the **Enable** button to start the channel decoding using the **ABC Trucking** alias list. -2. The completed channel configuration is shown in **Figure 4a** below. - -**Note:** once you have attached an alias list to a channel configuration, you do not have to -repeat this step. Any changes that you make to the existing aliases in your alias list will -be reflected in the decoding channel, so long as each of the aliases continue to be identified -with the same alias list name. You can also add new aliases to the alias list and they will -be reflected in the results produced by the decoding channel. - -![Figure 4a: Attach Alias List to Channel Configuration](v0.3/images/AliasExampleChannelAliasList_V0.3.0.png) - -**Figure 4a:** Attach Alias List to Channel Configuration - -Example: P25 Aliases ---- -In this example, we're going to attach P25 radio identifiers and talkgroups to the ABC Trucking aliases -created in the [first example](#example-create-aliases-for-an-alias-list). - -Individual P25 radios can call other P25 radios, or they can call a talkgroup and the call is placed -to all radios that belong to that talkgroup. P25 radio identifiers are up to six hexadecimal characters -long and P25 talkgroups are up to four hexadecimal characters long. In order for sdrtrunk to correctly -match radio identifiers and talkgroups, add leading zeros to talkgroups or radio identifiers to make -the value either four (talkgroup) or six (radio identifer) hexadecimal characters long. - -In the first part of this example we're going to attach individual P25 radio identifiers to the four -ABC Truck aliases we created earlier. - -1. Select the alias for **ABC Truck 1** in the alias table. -1. Click the **Audio/Identifier** tab in the alias editor. -1. Click the **New button** at the bottom of the alias editor and select **Talkgroup**. -1. Type A1234B in the talkgroup field. -1. Click the **Save** button. -1. The completed P25 alias identifier is shown in **Figure 5** below. - -Repeat these steps and add the following P25 radio identifiers to the remaining ABC Trucking aliases: -* ABC Truck 2: **A1234C** -* ABC Truck 10: **A12400** -* ABC Truck 11: **A12401** - -![Figure 5: Adding a P25 Radio Identifier to ABC Truck 1 Alias](v0.3/images/AliasExampleRadioIdentifier_V0.3.0.png) - -**Figure 5:** Adding a P25 Radio Identifier to ABC Truck 1 Alias - -Now that we have the P25 radio identifiers attached to the four ABC Truck aliases, let's setup two -P25 talkgroup aliases. - -1. Select the alias for **ABC Trucking-Local** in the alias table. -1. Click the **Audio/Identifier** tab in the alias editor. -1. Click the **New** button at the bottom of the alias editor and select **Talkgroup**. -1. Type **0012** in the talkgroup field. -1. Click the **Save** button. -1. The completed P25 alias identifier is shown in **Figure 6** below. - -Repeat these steps to add a talkgroup to the **ABC Trucking-Buses** alias. -* ABC Trucking-Buses: **0013** - -![Figure 6: Adding a P25 Talkgroup to ABC Trucking-Local Alias](v0.3/images/AliasExampleTalkgroup_V0.3.0.png) - -**Figure 6:** Adding a P25 Talkgroup to ABC Trucking-Local Alias - -Example: Audio Priority ---- -In this example, we're going to assign an audio priority to the ABC Trucking talkgroup aliases -that were created in the [first example](#example-create-aliases-for-an-alias-list). Since we -want to listen to the ABC Trucking local deliveries and we do not want to listen to the ABC Trucking -bus fleet, we'll assign an audio priority of **10** to the local delivery talkgroup and we'll assign -an audio priority of **Do Not Monitor** to the bus talkgroup. - -1. Select the alias for **ABC Trucking-Local** in the alias table. -1. Click the **Audio/Identifier** tab in the alias editor. -1. Click the **New** button and select **Audio Priority**. -1. Adjust the slider to change the value to **Priority: 10** -1. Click the **Save** button. - -Next, we set an audio priority for the **ABC Trucking-Buses** alias so that we do not have to -listen to the radio calls for the bus fleet. - -1. Select the alias for **ABC Trucking-Buses** in the alias table. -1. Click the **Audio/Identifier** tab in the alias editor. -1. Click the **New** button and select **Audio Priority**. -1. Move the slider all the way to the right until it reads **Priority: Do Not Monitor** -1. Click the **Save** button. -1. The completed P25 audio priority is shown in **Figure 7** below. - -![Figure 7: Setting Audio Priority to Do Not Monitor](v0.3/images/AliasExampleAudioPriority_V0.3.0.png) - -**Figure 7:** Setting Audio Priority to **Do Not Monitor** - -Example: Audio Streaming ---- -In this example, we're going to setup to stream all calls for the ABC Trucking bus fleet -using the aliases created in the [first example](#example-create-aliases-for-an-alias-list). - -In the [audio priority](#example-audio-priority) example, we setup the ABC Trucking bus fleet -to Do Not Monitor so that we did not have to listen to bus radio calls on our local computer. -However, other listeners have requested to hear the bus fleet streaming over the internet. This -example assumes that we've already setup a local Icecast audio streaming server and configured -an audio stream with a name of **ABC Trucking Audio Stream**. Next, we'll setup the ABC -Trucking buses talkgroup to stream to the server. - -**Note:** see the [Streaming](Streaming_V0.3.0) page for details on setting up streaming. - -1. Select the alias for **ABC Trucking-Buses** in the alias table. -1. Click the **Audio/Identifier** tab in the alias editor. -1. Click the **New** button and select **Audio Broadcast Channel**. -1. Click the dropdown list and select **ABC Trucking Audio Stream** from the list. - * Note: even though the stream is listed in the drop-down box, you must click the down arrow and - select the ABC Trucking Audio Stream entry for it to be recognized. -1. Click the **Save** button. -1. The completed audio streaming setup is shown in **Figure 8** below. - -![Figure 8: Setup ABC Trucking for Internet Audio Streaming](v0.3/images/AliasExampleAudioStreaming_V0.3.0.png) - -**Figure 8:** Setup ABC Trucking for Internet Audio Streaming - -Example: Alias with Wildcard P25 Talkgroup ---- -We often listen to radio systems that can contain hundreds of user talkgroups and thousands of -individual radios. When we don't want to create aliases for each and every one of these -users and talkgroups, we can create wildcard aliases as a catch-all alias for large groups -of these users and talkgroups. The wildcard alias is useful for matching large groups of users -and applying actions like **Non-Recordable** or **Do Not Monitor** alias identifiers. - -1. In the **Aliases** tab, click the **New** button to create a new Alias. -1. Setup the alias with the following values: - * **Name:** All Other Talkgroups - * **List:** ABC Trucking - * **Group:** Blacklisted Talkgroups - * **Color:** Red - * **Icon:** No Icon (default) -1. Click the **Save** button. -1. The completed alias is shown in **Figure 9**. - -![Figure 9: Wildcard Alias](v0.3/images/AliasExampleWildcardAlias_V0.3.0.png) - -**Figure 9:** Wildcard Alias - -Next, we assign a wildcard talkgroup identifier to the alias. The asterisk (*) is used to -wildcard individual identifier characters. Since P25 talkgroups are four hexadecimal -characters long, our wildcard pattern must also be four characters long. We use -an asterisk to match each hexadecimal digit, so the final pattern will be four asterisks. - -**Note:** the four asterisk pattern will only match identifiers that are four characters long, -like P25 talkgroups. Since P25 radio identifiers are six hexadecimal characters, they will -not match this four asterisk pattern. If we want to match groups of P25 radio identifiers, -we would use some combination of hexadecimal characters and asterisks to form a six -character value. - -1. Select the **All Other Talkgroups** alias in the alias table. -1. Click the **Audio/Identifier** tab in the alias editor. -1. Click the **New** button at the bottom of the alias editor and select **Talkgroup**. -1. Type **** (4 wildcard asterisks) in the talkgroup field. -1. Click the **Save** button. -1. The completed P25 wildcard talkgroup alias identifier is shown in **Figure 10** below. - -![Figure 10: Wildcard Talkgroup](v0.3/images/AliasExampleWildcardTalkgroup_V0.3.0.png) - -**Figure 10:** Wildcard Talkgroup - -Example: Audio Recording ---- -In this example, we're going to turn on audio recording so that we can record only -the audio from the ABC Trucking bus and local fleets. Since we do not want to record -any other talkgroups that may be active on the radio system, we have to create a -wildcard alias that will match all other talkgroups. - -Follow the [wildcard alias](#example-alias-with-wildcard-p25-talkgroup) example above -to create a P25 Alias with a wildcard talkgroup alias identifier. - -Next, we'll designate our wildcard alias as **Non-Recordable**. - -1. Select the **All Other Talkgroups** alias in the alias table. -1. Click the **Audio/Identifier** tab in the alias editor. -1. Click the **New** button at the bottom of the alias editor and select **Audio Non-Recordable**. -1. Click the **Save** button. -1. The completed recording blacklisted wildcard talkgroup is show in **Figure 11** below. - -![Figure 11: Wildcard Audio Non-Recordable](v0.3/images/AliasExampleAudioNonRecordable_V0.3.0.png) - -**Figure 11:** Wildcard Audio Non-Recordable - -Finally, we change our channel configuration to turn on Audio Recording. - -Example: LTR Aliases ---- - -In this example we're going to attach an LTR talkgroup to the ABC Trucking aliases -that we created in the [first example](#example-create-aliases-for-an-alias-list). - -Aliases can have multiple Alias Identifiers. In this example, ABC Trucking has -created a new LTR radio repeater for a small group of their bus fleet, in addition -to the P25 network that is used by the rest of the ABC Trucking bus fleet. - -Since we have already created an alias for our ABC Trucking bus fleet, we're simply -going to attach an LTR talkgroup identifier to that alias and then use the ABC Trucking -alias list in our new LTR channel configuration. - -1. Click the **Aliases** tab of the application window. -1. Select the **ABC Trucking-Buses** alias in the alias table. -1. In the alias editor window, click the **Audio/Identifier** tab. -1. Click the **New** button and select **Talkgroup**. -1. Type the value **0-01-001** for the LTR talkgroup in the box -1. Click the Save button. -1. The completed LTR talkgroup alias identifier is shown in **Figure 12** below. -1. Follow the steps in the [attach alias list example](#example-attach-an-alias-list-to-a-decoding-channel) -to attach the ABC Trucking alias list to our LTR decoding channel configuration - -**Note:** In the [audio streaming example](#example-audio-streaming) we designated -the **ABC Trucking-Buses** alias for audio streaming for the P25 Talkgroup 0013. -Now that we have attached an LTR talkgroup to this alias and we're using the -**ABC Trucking** alias list in the LTR channel configuration, all P25 calls and -all LTR calls from both channels will now be streamed over the -**ABC Trucking Audio Stream**. - -![Figure 12: LTR Talkgroup](v0.3/images/AliasExampleLTRTalkgroup_V0.3.0.png) - -**Figure 12:** LTR Talkgroup diff --git a/v0.3/ApplicationOverview_V0.3.0.md b/v0.3/ApplicationOverview_V0.3.0.md deleted file mode 100644 index 555e400..0000000 --- a/v0.3/ApplicationOverview_V0.3.0.md +++ /dev/null @@ -1,13 +0,0 @@ -### Application Overview ### - - * [Audio Panel](AudioPanel_V0.3.0) - * [Now Playing](NowPlaying_V0.3.0) - * [Aliases](Aliases_V0.3.0) - * [Channels](Channels_V0.3.0) - * [Map](Map_V0.3.0) - * [Streaming](Streaming_V0.3.0) - * [Tuners](Tuners_V0.3.0) - * [Spectral Display](SpectralDisplay_V0.3.0) - * [Waterfall Display](WaterfallDisplay_V0.3.0) - -![Figure 1: Application Overview](v0.3/images/ApplicationOverviewAnnotated_V0.3.0.png) diff --git a/v0.3/AudioPanel_V0.3.0.md b/v0.3/AudioPanel_V0.3.0.md deleted file mode 100644 index 1c1240e..0000000 --- a/v0.3/AudioPanel_V0.3.0.md +++ /dev/null @@ -1,74 +0,0 @@ -**Version:** 0.3.0 - -Audio Panel ---- - -The audio panel controls the audio that is played from the decoding channels to -either your computer speakers or headphones. Audio from each decoding channel -is automatically routed to the Audio Manager and the audio manager automatically -routes the highest priority audio to the speakers. - -Each audio playback channel is automatically started and stopped depending on -audio availability. Playback channels use an internal buffer to store a -small number of audio frames before automatically starting playback. Therefore, -you may experience a slight delay between seeing a call start in the decoder -window and audio playback starting. Likewise, you may hear audio playing for a -short period after the decoding channel display indicates that the call has -ended. - -Audio priority can be specified for each alias that you create. If you want -certain talkgroups or identifiers to have a higher priority for listening, you -can create the [alias](Aliases_V0.3.0), assign the talkgroup(s) or identifier(s) -and specify a priority. - -If a call is in playback over the speakers and a higher priority call comes in, -the higher priority call will be routed and the existing call audio will be -stopped. - -You can override all call priorities defined in the system when you select an -individual decoding channel. Any audio produced from a selected channel is -routed with the highest priority for playback. - -Audio Playback Device ---- - -The default audio playback device with mono audio is selected by default. You -can change the audio playback device and choose the number of playback channels -by right-clicking on the audio panel and use the AUDIO OUTPUT menu to select a -different audio device. - -### Mono Audio Playback -You can select mono audio playback to have any playback audio routed to both -speakers. The mono audio playback is shown in Figure 1. - -![Audio Panel with Mono Playback](v0.3/images/AudioPanelMono_V0.3.0.png) - -**Figure 1:** Audio Playback Panel with Mono Audio - -## Stereo Audio Playback ## -You can select stereo audio playback so that you have independent LEFT and RIGHT -audio playback over a stereo audio output. Each audio channel will be managed -by the Audio Manager and all audio produced by all decoding channels will be -routed to these two channels on a priority basis, as shown in Figure 2. - -![Audio Panel with Stereo Playback](v0.3/images/AudioPanelStereo_V0.3.0.png) - -**Figure 2:** Audio Playback Panel with Stereo Audio - -## Master Mute Button ## -The green speaker icon visible in Figure 2 on the audio panel is the master mute -control. Click the icon to mute the audio and the icon will turn red as shown -in Figure 3. Click again, and the audio will unmute and the icon will turn green again. - -## Channel Menu ## -Right-click on either the MONO channel, or the LEFT or RIGHT channel to access -the context menu for the channel. You can independently mute or change the -audio volume of each channel via this context menu. - -## Channel Mute ## -Each channel will show a RED M in the panel when the audio is muted either via -the master mute button, or by the channel mute context menu, as shown in Figure 3. - -![Audio Panel with Muted Audio](v0.3/images/AudioPanelMuted_V0.3.0.png) - -**Figure 3:** Audio Playback Panel with Muted Audio diff --git a/v0.3/ChannelMap_V0.3.0.md b/v0.3/ChannelMap_V0.3.0.md deleted file mode 100644 index 18695fc..0000000 --- a/v0.3/ChannelMap_V0.3.0.md +++ /dev/null @@ -1,35 +0,0 @@ -# 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. - -![Figure 1: Channel Map Manager](v0.3/images/ChannelMapManager_V0.3.0.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 \ No newline at end of file diff --git a/v0.3/ChannelSpectrum_V0.3.0.md b/v0.3/ChannelSpectrum_V0.3.0.md deleted file mode 100644 index 5892cb0..0000000 --- a/v0.3/ChannelSpectrum_V0.3.0.md +++ /dev/null @@ -1,27 +0,0 @@ -# Channel Spectrum # - -The channel spectrum window allows you to view the dynamic frequency content of -the demodulated audio produced from the currently selected decoding channel. -The demodulated audio is processed with a Discrete Fourier Transform (DFT) -similar to the Spectral Display. This display allows you to hover over each of -the peaks in the audio frequency and a frequency readout is displayed next the -cursor. - -You can use the frequency readout to measure spectral content like CTCSS tones -that may be present in the demodulated audio output. - -Spectral display processing only occurs when you have a channel selected and -when the spectral display tab is displayed. If you have the spectral display -tab displayed and no channels are selected, the display will be empty. - -Note: certain decoders like the P25-LSM decoder do not produce demodulated audio -and will not display audio content in the channel spectrum window. The audio -output from digital voice CODECs is not displayed in this channel spectrum -window. - -## Context Menus ## -You can change the color, FFT size, and frame rate of the channel spectrum -window by right-clicking anywhere in the display and choosing from the menu -options. - -![](images/channel_spectrum.png) \ No newline at end of file diff --git a/v0.3/Channels_V0.3.0.md b/v0.3/Channels_V0.3.0.md deleted file mode 100644 index 5f1fafd..0000000 --- a/v0.3/Channels_V0.3.0.md +++ /dev/null @@ -1,215 +0,0 @@ -**Version:** 0.3.0 and newer - -Channels ---- -Channels are configurations that you create for each radio frequency channel that -you want to monitor. The channel configuration contains the basic information -needed to tune to a radio channel frequency, attach one or more protocol-specific -decoders, specify an alias list, and setup logging and recording options. - -**TIP:** Create channel configurations for all radio channels that you might want to -monitor. Click the **Enable** button in the channel configuration editor to start -a channel decoding. If you shut down the application and restart it later, any -channels that were enabled will automatically start again. - -![Figure 1: Channels Table - Name/Alias Editor](v0.3/images/ChannelsNameEditor_V0.3.0.png) -**Figure 1:** Channels Table - Name/Alias Editor - -All channel configuration editing and management is accessible in the **Channels** -tab of the application. - -Viewing, Sorting, and Filtering Channel definitions ---- - -#### Sorting -Click the column name in the channels table to apply alphabetical sorting. An -arrow appears to the right of the column name to indicate if the list is sorted -ascending or descending. By clicking the column name you can toggle the ascending -or descending order. - -#### Filtering -Each of the columns in the channels table contain a column heading with a drop-down -cell. In the drop-down menu, you can select from a list of column values to filter -the list of visible channel configurations. The top row of the filter drop-down also -supports text and wildcard values for filtering. - -You can apply filtering to multiple columns. - -Click the top empty row in the drop-down list to remove any filtering that you -have applied. - -**TIP:** Use the **Enabled** column filter to quickly view channels are currently -decoding. - -#### Viewing -Click on an individual channel configuration row to show the channel configuration -settings in the editor below the table. - -Creating, Deleting and Copying Channels ---- -Use the three buttons at the bottom of the channels table to create new channels, -copy one or more existing channels, or delete one or more channels. - -#### New Button -Click the new button to create a new channel. The new channel configuration appears -at the bottom of the channel table. Select the new channel and use the editor -window at the bottom of the screen to configure the channel settings. - -#### Copy Button -Select one or more channels that you have already created and click the Copy button -to create duplicate copies of the selected channels. You can then edit each of the -channel copies individually. This is a convenient feature when you are creating -many channels that are mostly the same and you only have to change a few settings. - -#### Delete Button -Select one or more channels and click the Delete button to remove the selected -channels from the list. - -Channels Table - Editing a Channel Configuration ---- -Select one of the channel configurations in the channels table to edit the -configuration settings. The following sections explain each of the section tabs -of the channel configuration editor. - -#### Enable Button -Once you have created a channel configuration, click the **Enable** button to -start the channel decoding. The button color will change to green to indicate -that the channel is currently enabled. Click the button again to disable decoding -for that channel. - - -#### Save Button - -#### Reset Button - -Channels Table - Name/Alias Editor ---- - -The following are settings that can be modified in the **Name/Alias** section tab -of the channel editor. The **Name/Alias** editor is shown in Figure 1. - -#### Name -The channel name is a textual value that you specify. This value does not -affect decoding. - -#### Alias List -Choose an alias list name from the drop-down list, or type a new alias list name. -The values in the list are pulled from any [Aliases](Aliases_V0.3.0) that you may -have already created. - -If you type a new alias list name for your channel configuration, be sure to use -that alias list name for any aliases that you create in the [Aliases](Aliases_V0.3.0) -table. When you start your channel decoding, any aliases with the matching alias -list name will be assembled into an alias list for use with the channel. If you -add new aliases while your channel is currently decoding, they will be automatically -added to the alias list used by your decoding channel if the alias list name -matches the alias list name specified for the channel. - -#### System -System is an optional textual value that you can use to manage your set of channel -configurations. By using the System column filter in the channels table, you can quickly filter -down to a related set of channel configurations in the channels table. - -**Note:** a planned future enhancement will use the System label to deduplicate -call audio for systems that simulcast a radio call across multiple sites. - -#### Site -Site is an optional textual value that you can use to manage your set of channel -configurations. By using the Site column filter in the channels table, you can -quickly filter down to a related set of channel configurations in the channels -table. - - -![Figure 2: Channels Table - Source Editor](v0.3/images/ChannelsSourceEditor_V0.3.0.png) -**Figure 2:** Channels Table - Source Editor - -Channels Table - Source Editor ---- - -The source editor is where you specify the tuner frequency or sound card to -use as an input to the decoder. The **Source Editor** is shown in Figure 2. - -#### Tuner -Specify a frequency for your channel. When your channel is enabled, the -application will automatically select one of the tuners present on your -computer and automatically tune to the channel frequency specified. - -#### Sound Card -This optional channel source enables you to feed demodulated audio from an -external scanner or radio to feed a small subset of decoders. Decoders that -work with sound card audio: **MPT-1327**, **Fleetsync**, **MDC-1200**, -**Tait 1200** and **LoJack**. - -![Figure 3: Channels Table - Decoder Editor](v0.3/images/ChannelsDecoderEditor_V0.3.0.png) -**Figure 3:** Channels Table - Decoder Editor - -Channels Table - Decoder Editor ---- -The decoder editor is where you select the _primary_ decoder to use for your -channel configuration. The **Decoder Editor** is shown in Figure 3. The application -allows you to specify exactly one primary decoder and one or more auxiliary -decoders. See below for details on auxiliary decoders. - -Refer to the [Decoders](Decoders) page for details and configuration for each -primary decoder type. - -![Figure 4: Channels Table - Aux Decoders Editor](v0.3/images/ChannelsAuxDecoderEditor_V0.3.0.png) - -**Figure 4:** Channels Table - Aux Decoders Editor - -Channels Table - Aux Decoders Editor ---- -The **Aux Decoders Editor** is show in Figure 4. Use this editor to select one or -more auxiliary decoders to run in addition to the primary decoder that you have -selected. Auxiliary decoders work against demodulated audio to decode in-band -signalling that may be included in certain radio systems. These in-band -signalling types are normally used for radio identification or data/GPS -transmissions in older analog radio systems. - -Refer to the [Decoders](Decoders) page for details and configuration for each -auxiliary decoder type. - -![Figure 5: Channels Table - Logging Editor](v0.3/images/ChannelsLoggingEditor_V0.3.0.png) -**Figure 5:** Channels Table - Logging Editor - -Channels Table - Logging Editor ---- - -The **Logging Editor**, shown in Figure 5, is where you select logging options for -your decoding channel. - -#### Binary Messages -This option creates a log file containing a binary (text 0 or 1) representation -of each decoded message. - -#### Decoded Messages -This option creates a log file containing decoded messages in readable text format. - -#### Call Events -This option creates a log file containing the call events and times. - -![Figure 6: Channels Table - Recording Editor](v0.3/images/ChannelsRecordingEditor_V0.3.0.png) -**Figure 6:** Channels Table - Recording Editor - -Channels Table - Recording Editor ---- - -The **Recording Editor**, shown in Figure 6, is where you select recording options for -your decoding channel. - -#### Audio -Records all audio and audio calls. - -**Note:** you can assign a **Non-Recordable** audio setting to individual aliases -to control which audio is recorded for a channel. Use wildcards with the -Talkgroup Alias Identifier to set groups of talkgroups as recordable or non-recordable - -#### Baseband I/Q -Records the baseband channel samples. This recording is not demodulated and -will sound like noise if you attempt to playback this recording. This format -is used to record the channel for decoding or analysis. - -#### Traffic Channel Baseband I/Q -Similar to the Baseband I/Q setting above, this will generate a recording for -each traffic channel that is allocated when you are decoding a control channel -on a system like MPT-1327 or P25. diff --git a/v0.3/Decoders_V0.3.0.md b/v0.3/Decoders_V0.3.0.md deleted file mode 100644 index b0f2c0b..0000000 --- a/v0.3/Decoders_V0.3.0.md +++ /dev/null @@ -1,47 +0,0 @@ -Decoders ---- - -Each decoding [channel](Channels_V0.3.0) requires one primary decoder and can optionally -have one or more auxiliary decoders running at the same time. If you want to -run multiple primary decoders on the same frequency, create separate channel configurations -for each primary decoder. - -Primary Decoders ---- - * [AM](AM_V0.3.0) - AM demodulator - * [LTR-Standard](LTR_V0.3.0) - FM demodulator and Logic Trunked Radio (LTR) trunked radio signaling decoder - * [LTR-Net](LTRNet_V0.3.0) - FM demodulator and LTR-Net trunked radio signaling decoder - * [MPT-1327](MPT1327_V0.3.0) - FM demodulator and MPT-1327 trunked radio signaling decoder and automatic trunked channel following. - * [NBFM](NBFM_V0.3.0) - narrow-band FM demodulator. - * [Passport](Passport_V0.3.0) - FM demodulator and Passport trunked radio signaling decoder. - * [P-25 Phase 1 C4FM](APCO25_V0.3.0) - FM demodulator with P25 message decoder and automatic trunked channel following. - * [P-25 Phase 1 LSM](APCO25_V0.3.0) - Quadrature demodulator with P25 message decoder and automatic trunked channel following. - * [P-25 Phase 2](APCO25_V0.3.0) - Phase 2 traffic channels - -Auxiliary Decoders ---- -Auxiliary decoders are designed to process demodulated audio or in-band -signaling that is normally layered on top of another digital protocol or FM -modulated analog repeater channel. These layered protocols provide services -like Automatic Number Identification (ANI), status messaging, GPS location, -emergency notification, etc. Auxiliary protocols may be transmitted when the -mobile radio user keys the microphone, or in the case of GPS, they can key the -radio and transmit the GPS location without any user actions. - -How do auxiliary decoders work? Demodulated audio from a primary decoder's FM -demodulator is simultaneously routed to each of the auxiliary decoders -and the decode results are added to the Events and Messages lists, as well as -displayed in the [Now Playing](NowPlaying_V0.3.0) window. - -Auxiliary decoders are normally used with analog decoders like NBFM, LTR, -LTR-Net, and Passport. - - * [Fleetsync II](Fleetsync2_V0.3.0) - decodes ANI, Acknowledge, Status, Paging and GPS bursts - * [LJ1200](LoJack_V0.3.0) - decodes LoJack data bursts on 173.075 MHz in US. - * [MDC-1200](MDC1200_V0.3.0) - decodes MDC-1200 ANI bursts. - * [Tait 1200](Tait1200_V0.3.0) - decodes Tait CCDI protocol GPS location bursts. - -**Note:** there are a wide variety of these auxiliary service protocols that can be -easily added to SDRTrunk. If you encounter a new audio-band protocol, collect -a number of good quality sample recordings and contact the author via the -google support group for possible inclusion in the sdrtrunk application. diff --git a/v0.3/E4000_V0.3.0.md b/v0.3/E4000_V0.3.0.md deleted file mode 100644 index bf94a47..0000000 --- a/v0.3/E4000_V0.3.0.md +++ /dev/null @@ -1,33 +0,0 @@ -# Elonics E4000 # - -http://www.nooelec.com/store/sdr/sdr-receivers.html - -![Figure 1: E4000 Tuner Configuration](v0.3/images/E4000_V0.3.0.png) - -## E4000 Tuner Configuration ## - -SDRTrunk uses the serial number label from the E4000 to associate the most recently used tuner configuration. This serial number can be set/changed using the rtl\_eeprom utility, - -All changes to a named configuration are automatically saved. - -### Configuration ### - - * **Name** - tuner configuration name. - * **Tuner Info** - see next section - * **Sample Rate** - sets the sample rate to use for the tuner. - * **PPM** - correction value (parts per million) 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. - * **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 - * **Mixer Gain** - sets the Mixer gain. Place the Master Gain into **Manual** mode to enable this control. - * **LNA Gain** - sets the LNA 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. - -### Tuner Info ### -The tuner info button 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 - \ No newline at end of file diff --git a/v0.3/Fleetsync2_V0.3.0.md b/v0.3/Fleetsync2_V0.3.0.md deleted file mode 100644 index aa33094..0000000 --- a/v0.3/Fleetsync2_V0.3.0.md +++ /dev/null @@ -1,50 +0,0 @@ -# Fleetsync II Decoder # - -Fleetsync is a digital radio identifier, status, GPS, and data protocol that is -normally used in combination with other trunked radio protocols and/or 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. - -## 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 - -## Decoder Setup - Conventional or Repeater Network ## - -Setup a decoding channel with a NBFM decoder and select FLEETSYNC 2 in the aux -decoder configuration tab. - -## Decoder Setup - Analog Trunked Network ## - -Setup a decoding channel with one of the analog trunked radio decoders (LTR, -LTRNet, Passport, etc) and select FLEETSYNC 2 in the aux decoder configuration tab. \ No newline at end of file diff --git a/v0.3/FuncubeDongleProPlus_V0.3.0.md b/v0.3/FuncubeDongleProPlus_V0.3.0.md deleted file mode 100644 index 3bee34e..0000000 --- a/v0.3/FuncubeDongleProPlus_V0.3.0.md +++ /dev/null @@ -1,26 +0,0 @@ -Funcube Dongle Pro Plus Tuner Configuration ---- - -![Figure 1: Funcube Dongle Pro Plus Tuner Configuration](v0.3/images/FuncubeDongleProPlus_V0.3.0.png) - -**Figure 1:** Funcube Dongle Pro Plus Tuner Configuration - - -The following settings shown in Figure 1 are available for configuring the tuner: - -#### Name -Name for the tuner configuration. - -#### Tuner Info Button -Provides a summary of details about the currently selected tuner, including: USB ID, USB address, -USB speed, cellular band block, and Firmware version - -#### 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 Checkbox -Turns on or off the LNA gain - -#### Mixer Gain Checkbox -Turns on or off the Mixer gain diff --git a/v0.3/FuncubeDonglePro_V0.3.0.md b/v0.3/FuncubeDonglePro_V0.3.0.md deleted file mode 100644 index 9e4eee3..0000000 --- a/v0.3/FuncubeDonglePro_V0.3.0.md +++ /dev/null @@ -1,48 +0,0 @@ -**Version:** 0.3.0 - -Funcube Dongle Pro Tuner Configuration ---- - -![Figure 1: Funcube Dongle Pro Tuner Configuration](v0.3/images/FuncubeDonglePro_V0.3.0.png) - -**Figure 1:** Funcube Dongle Pro Tuner Configuration - - -The following settings shown in Figure 1 are available for configuring the tuner: - -#### Name -Name for the tuner configuration. - -#### Tuner Info Button -Provides a summary of details about the currently selected tuner, including: USB ID, USB address, -USB speed, cellular band block, and Firmware version - -#### 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 -LNA gain setting - -#### Enhance -LNA enhance gain setting - -#### Mixer -Mixer gain setting - -#### DC Inphase -Corrects for DC offset in the Inphase component - -#### DC Quadrature -Corrects for DC offset in the Quadrature component - -#### Gain -Corrects for Gain error - -#### Phase -Corrects for Phase error - -**Note:** firmware on the [Funcube Dongle Website](http://www.funcubedongle.com/?page_id=313) -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. \ No newline at end of file diff --git a/v0.3/GettingStarted_V0.3.0.md b/v0.3/GettingStarted_V0.3.0.md deleted file mode 100644 index 2a9e02b..0000000 --- a/v0.3/GettingStarted_V0.3.0.md +++ /dev/null @@ -1,41 +0,0 @@ -## Getting started with SDRTrunk ## - -SDRtrunk is an integrated application for demodulating radio signals and -decoding trunked radio network protocols and some related radio signal formats. The -application does NOT require a discriminator tapped scanner and it does NOT -require the use of audio piping applications like Virtual Audio Cable. All -connections between the tuner or sound card and the decoders is provided by the -sdrtrunk application. - -SDRTrunk uses channel definitions to configure and setup each demodulation and decoder -processing sequence. In order to successfully decode radio signals, each channel configuration requires: - -* **Source** - specifies where to get the radio samples from (tuner or sound card) -* **Decoder** - which demodulator or decoder to use in processing the source samples - -Each channel definition allows you to optionally configure: - -* **Aux Decoder** - additional in-band audio digital signal protocol decoding -* **Logging** - log decoded messages or events -* **Recording** - record audio calls or digitized baseband samples - -The SDRTrunk application is programmed in Java and can run on any computer where Java is supported -for the operating system and where the computer hardware (processor/memory) is sufficient for the -processing workload. - -### Setup ### - - * [Linux](SetupLinux_V0.3.0) - * [Windows](SetupWindows_V0.3.0) - -### Application Overview ### - -The [application overview](ApplicationOverview_V0.3.0) article describes the various -components in the sdrtrunk application - -### Configuration ### - -The Channels tab at the center of the application is the central control for configuring and -managing channel definitions. Please refer to the [Channels](Channels_V0.3.0) wiki page for -instructions on creating channel definitions and starting channels decoding. - diff --git a/v0.3/HackRF_V0.3.0.md b/v0.3/HackRF_V0.3.0.md deleted file mode 100644 index e69df79..0000000 --- a/v0.3/HackRF_V0.3.0.md +++ /dev/null @@ -1,33 +0,0 @@ -HackRF Tuner Configuration ---- - -![Figure 1: HackRF Tuner Configuration](v0.3/images/HackRF_V0.3.0.png) - -**Figure 1:** HackRF Tuner Configuration - -The following settings shown in Figure 1 are available for configuring the tuner: - -#### Name -Name for the tuner configuration. - -#### Tuner Info Button -Provides a summary of details about the currently selected tuner, including Board ID, Serial Number, -Part Number and Firmware revision. - -#### Sample Rate -Allows you to change the sample rate. - -#### PPM -Adjusts the frequency correction Parts Per Million (PPM) value for the tuner. If you notice in -the spectral display that the frequency labels are slightly misaligned to observed signals, you -can adjust this value to align the frequency to the observed signals with known operating -frequencies. - -#### Amplifier Button -Turns on or off the amplifier - -#### LNA Gain -Sets the LNA gain - -#### VGA Gain -Sets the VGA gain. \ No newline at end of file diff --git a/v0.3/LTRNet_V0.3.0.md b/v0.3/LTRNet_V0.3.0.md deleted file mode 100644 index 7f19aac..0000000 --- a/v0.3/LTRNet_V0.3.0.md +++ /dev/null @@ -1,60 +0,0 @@ -# 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 signaling-based audio squelch control. - -## 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. - -## 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 - \ No newline at end of file diff --git a/v0.3/LTR_V0.3.0.md b/v0.3/LTR_V0.3.0.md deleted file mode 100644 index 548a71b..0000000 --- a/v0.3/LTR_V0.3.0.md +++ /dev/null @@ -1,12 +0,0 @@ -# LTR Standard Decoder # - -## Squelch Control ## - -The Logic Trunked Radio (LTR) decoder provides signaling-based squelch control. - -## 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 to identify these as FCC Callsign Broadcasts: - - * `*`-`*``*`-255 FCC CWID - \ No newline at end of file diff --git a/v0.3/LoJack_V0.3.0.md b/v0.3/LoJack_V0.3.0.md deleted file mode 100644 index 94285fe..0000000 --- a/v0.3/LoJack_V0.3.0.md +++ /dev/null @@ -1,23 +0,0 @@ -# LJ1200 Decoder # - -LoJack is a vehicle and equipment tracking and recovery service that is available -in a number of cities in the US. The network broadcasts a series of data -messages on 173.075 MHz to transponders installed in each tracked vehicle or -piece of equipment. This decoder processes these network broadcast messages. - -## LoJack Alias ID ## - -The LoJack alias identifier allows you to specify a function code and tower ID -or transponder ID to associate with an alias. - -## ESN Alias ID ## - -The ESN ID alias can be used to match a vehicle transponder address. - -## Decoder Setup ## - -Setup a decoding channel with a NBFM decoder and specify a tuner frequency of -173.075 in the source configuration tab. Select LJ1200 in the aux decoder -configuration tab. - - diff --git a/v0.3/MDC1200_V0.3.0.md b/v0.3/MDC1200_V0.3.0.md deleted file mode 100644 index 43dfe83..0000000 --- a/v0.3/MDC1200_V0.3.0.md +++ /dev/null @@ -1,22 +0,0 @@ -# MDC-1200 Decoder # - -The MDC-1200 decoder processes Automatic Number Identification (ANI) data -bursts that are used in some analog radio networks to identify individual radios -each time they broadcast on the repeater or trunked radio channel. - -Note: this decoder doesn't currently provide error detection and correction and -therefore it may produce invalid decoded messages. If you have access to a -radio with MDC1200 capability and can provide quality audio recordings of the -various data bursts, please contact the author via the Google support group. - -## Decoder Setup - Conventional or Repeater Network ## - -Setup a decoding channel with a NBFM decoder and select MDC1200 in the aux -decoder configuration tab. - -## Decoder Setup - Analog Trunked Network ## - -Setup a decoding channel with one of the analog trunked radio decoders (LTR, -LTRNet, Passport, etc) and select MDC1200 in the aux decoder configuration tab. - - diff --git a/v0.3/MPT1327_V0.3.0.md b/v0.3/MPT1327_V0.3.0.md deleted file mode 100644 index 38e7d4d..0000000 --- a/v0.3/MPT1327_V0.3.0.md +++ /dev/null @@ -1,57 +0,0 @@ -# MPT-1327 # - -The MPT-1327 decoder provides decoding of both control and traffic channel -signaling and trunked traffic channel following. - -## Trunked Channel Following ## - -Configure the MPT-1327 decoder to process the system control channel and specify -a channel map. The application will automatically detect call events and -dynamically create a traffic channel to monitor these calls and end the traffic -channel whenever the channel timeout occurs, or the end of call is detected. - -Each system that you monitor may have different call timeouts. You can change -this timeout from the default 45 seconds to meet your needs. However, if you -specify a long timeout and the end of call is not detected, you'll have a long -period of static at the end of your calls and recordings. - -Specify the maximum number of traffic channels that the decoder can allocate -simultaneously in order to keep total processing to a level that your computer -can handle. You may have to experiment with this value in order to keep the -application from allocating more channels than your computer can process. Start -with 1 traffic channel and monitor your computer's CPU and memory to see how it -responds. Keep increasing the traffic channel count and restart the channel -until you find the maximum number of traffic channels that your computer can -process and then consider reducing that count by one or two. - -## Channel Map ## -You must specify a channel map name in the decoder configuration in order for -trunked channel following to work. Otherwise, the application does not know -about the channel number to frequency mapping. You can run the decoder without -a chanel map against control and traffic channels, however no trunked channel -following will occur. - -If you don't know what the [channel map](ChannelMap_V0.3.0) is, you can try to find the license -for the system that specifies the frequencies for the system. Configure an -sdrtrunk channel to monitor each frequency and after successfully decoding a -call, look at the messages tab. The end of call signaling messages tell the mobile -radio what channel it is currently on, and what the channel number is for the -control channel that the mobile radio must return to. You can use these -channel numbers to determine the channel map. If you need help, use the -radioreference.com forums, or post a help request in the sdrtrunk support group. -There is also a wiki page on radioreference.com that details how to calculate -the channel map from known frequency to channel number pairings. - -## Squelch Control ## - -When monitoring a control channel the audio is muted. When monitoring a traffic -channel, audio squelch is controlled by the call start and call end signaling that -is decoded on the traffic channel. - -## Talkgroups ## - -The following talkgroups are used in all MPT-1327 systems. Create an alias -group containing the following MPT-1327 system idents: - - * `*``*``*`-8185 = System Register - * `*``*``*`-8190 = System Controller diff --git a/v0.3/Map_V0.3.0.md b/v0.3/Map_V0.3.0.md deleted file mode 100644 index e88ea10..0000000 --- a/v0.3/Map_V0.3.0.md +++ /dev/null @@ -1,22 +0,0 @@ -**Version:** 0.3.0 - -Map ---- - -The map displays any decoded messages that contain location data like GPS positions. - -The map component uses [aliases](Aliases_V0.3.0) 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 re-center 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. - -![Map Display](v0.3/images/Map_V0.3.0.png) - -**Figure 1:** Map Display diff --git a/v0.3/NBFM_V0.3.0.md b/v0.3/NBFM_V0.3.0.md deleted file mode 100644 index f9d2279..0000000 --- a/v0.3/NBFM_V0.3.0.md +++ /dev/null @@ -1,7 +0,0 @@ -# NBFM Decoder # - -The NBFM decoder is a simple FM demodulator. You can use any of the [auxiliary decoders](Decoders_V0.3.0) in conjunction with the NBFM decoder. - -## Squelch Control ## - -The NBFM doesn't provide any squelch control. \ No newline at end of file diff --git a/v0.3/NowPlaying_V0.3.0.md b/v0.3/NowPlaying_V0.3.0.md deleted file mode 100644 index d584cab..0000000 --- a/v0.3/NowPlaying_V0.3.0.md +++ /dev/null @@ -1,149 +0,0 @@ -**Version:** 0.3.0 and newer - -Now Playing ---- -The **Now Playing** tab provides a convenient summary screen to monitor when you -are decoding channels and monitoring audio. It displays a summary of channels and -provides access to decoding details, messages and call events for each channel. - -![Figure 1: Application Overview with Now Playing Displayed](v0.3/images/ApplicationOverview_V0.3.0.png) -**Figure 1:** Application Overview with Now Playing tab - -Decoding Channel Table ---- -The table at the top of the Now Playing screen provides a summary of all channels that you have -enabled for decoding. The table contains the following columns: - -#### State -Indicates the current state of the channel's primary and secondary decoders: -* **CALL** - a radio call is in progress -* **CONTROL** - a trunked radio control channel is being decoded -* **DATA** - a radio data call is in progress -* **ENCRYPTED** - an encrypted radio call is in progress -* **FADE** - temporary state when a call has ended before changing to IDLE state -* **IDLE** - the decoder is running -* **OVERFLOW** - temporary error when the computer is unable to keep up with the incoming -data rate. When this occurs frequently, consider reducing the number of decoding channels -that you have enabled -* **RESET** - temporary state when the decoders are being reset -* **TEARDOWN** - temporary state when a traffic channel call has ended and the channel is -being removed - -#### Decoder -Primary decoder specified in the channel configuration. Any auxiliary decoders that you have enabled -for the channel will not be displayed here. - -#### Channel -Diplays the logical Channel identifier for trunked radio systems. - -#### Frequency -Tuned frequency for the channel - -#### Primary From -Primary decoder radio or talkgroup identifier for the (FROM) part of a radio call. - -#### Primary To -Primary decoder radio or talkgroup identifier for the (TO) part of a radio call. - -#### Secondary From -Secondary (auxiliary) decoder radio or talkgroup identifier for the (FROM) part of a radio call. - -#### Secondary To -Secondary (auxiliary) decoder radio or talkgroup identifier for the (TO) part of a radio call. - -#### Channel Name -Channel name from the channel configuration. Note: traffic channels that are automatically created -when decoding a trunked radio control channel will display _TRAFFIC_. - -#### Message -Any decoded status, GPS, or text message from the Primary and Auxiliary decoders. - -Channel Information ---- -The lower half of the **Now Playing** screen shows additional information when you select/click on a -row in the channels table above. - -![Figure 2: Now Playing with Channel Details View](v0.3/images/NowPlayingDetailsView_V0.3.0.png) -**Figure 2:** Now Playing with Channel Details View - -Details View ---- -The details view provides summary information from each of the primary and auxiliary decoders -for the channel. Primary decoder summary information is displayed first and a section is added -to the bottom of the report for each additional auxiliary decoder that is configured for the -channel. - -The channel configuration System, Site and Channel name are displayed across the top of the -detail view. - -**Note:** the format of the detail summary report is different for each decoder. - -#### Refresh Button -The summary report is generated when you first select a channel and click on the details view. -You can regenerate the report with the latest summary information from the decoders when you -click on the **Refresh** button. - -![Figure 3: Now Playing with Channel Events View](v0.3/images/NowPlayingEventsView_V0.3.0.png) -**Figure 3:** Now Playing with Channel Events View - -Events View ---- -The events view details any events decoded from either the primary decoder or from any of the -auxiliary decoders that may be included in the channel configuration. - -#### Time -Timestamp or time range of the event - -#### Event -Event description. - -#### From -Identifier of the radio or entity for the FROM part of the event. - -#### (From) Alias -Optional alias corresponding to the **From** identifier. - -#### To -Identifier of the radio or entity for the TO part of the event - -#### (To) Alias -Optional alias corresponding to the **To** identifier - -#### Channel -Logical channel identifier for the event - -#### Frequency -Channel frequency for the event - -#### Details -Message, GPS location, status, or additional details about the event. - -![Figure 4: Now Playing with Channel Messages View](v0.3/images/NowPlayingMessagesView_V0.3.0.png) -**Figure 4:** Now Playing with Channel Messages View - -Messages View ---- -The channel messages table displays messages being decoded by the primary decoder for the -channel. - -#### Time -Time for the message - -#### Protocol -Radio protocol being decoded - -#### Error Check -Indicates if sections of the message were decoded without errors (*) or if sections of the -message were corrected (C) - -#### Message -Textual representation of the decoded message. - -#### Binary -Textual representation of the binary (0 or 1) decoded message. - -**Note:** -Viewing the real-time messages decoding adds to the computer's processing workload. When you -are viewing the messages, each message is being fully parsed. When you are not viewing the -message display, the computer is only parsing the minimum information that it needs from -each message. \ No newline at end of file diff --git a/v0.3/Passport_V0.3.0.md b/v0.3/Passport_V0.3.0.md deleted file mode 100644 index 407fb2a..0000000 --- a/v0.3/Passport_V0.3.0.md +++ /dev/null @@ -1,39 +0,0 @@ -# Passport # - -The passport decoder will decode the Outbound Status Word (OSW) messages and -signaling that are transmitted by the network to the mobile radio. Passport -systems do not have dedicated control channels, therefore this decoder does not -support trunked channel following. - -## 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 signaling-based squelch control. - -## Aliases ## - -If you are in the United States, and your Passport network may occasionally -broadcast its FCC station callsign. Add the following alias and talkgroup -identifier to your alias list to automatically identify these station ID -call events: - - * 65535 FCC CWID - -## Passport Decode Example ## - -The below screenshot shows a passport channel being decoded where the system -also uses the Fleetsync auxiliary protocol overlay. SDRTrunk decodes both the -passport signaling and the fleetsync data bursts and displays the decoded -information. In this instance, the mobile radio is transmitting an automatic - Fleetsync GPS location report without the user's input. diff --git a/v0.3/Preferences_V0.3.0.md b/v0.3/Preferences_V0.3.0.md deleted file mode 100644 index 4af9603..0000000 --- a/v0.3/Preferences_V0.3.0.md +++ /dev/null @@ -1,76 +0,0 @@ -Preferences ---- -The preferences dialog allows you to change settings that affect the way -that sdrtrunk operates and displays decoded data. - -![Figure 1: Preferences Dialog](v0.3/images/Preferences_V0.4.0.png) - -**Figure 1:** Preferences Dialog - -Each section of the preferences dialog is detailed below. - -Decoder ---- -#### JMBE Audio Library -Use the **Change...** button to specify the location for the optional JMBE audio -library that can be used for decoding digital audio like P25 Phase 1 and 2. - -Display ---- -Settings to change the way that decoded values are displayed in the application. - -#### Channel Events -Choose the timestamp format that is used in the Events tab. - -#### Talkgroups -Customize the display format for talkgroup values produced by each of the decoders. - -**Decimal** - Base 10 decimal format (0 - 9) -**Hexadecimal** - Base 16 format (0 - 9 and A - F) -**Formatted** - default format for the decoder (either Decimal or Hexadecimal) -**Fixed Width** - when checked, adds leading zeros to make all of the displayed values have the same width - -File Storage ---- -Customize the file system directories and locations used by sdrtrunk. - -By default, a base folder **SDRTrunk** is created in your user directory and all -other folders are created below that folder. You can use the **Change ...## button -to customize any of the locations. - -**Application Root** - base directory for all sdrtrunk generated data and logging folders -**Application Logs** - log files that are created each time the application runs -**Event Logs** - event logs produced by each decoder channel when you enable event logging. -**Playlists** - playlist configuration file(s) -**Recordings** - all audio, baseband and MBE recordings are stored here -**Screen Captures** - screen capture pictures created by the user -**Streaming** - temporary streaming audio file queue. - -Source ---- -Settings for application data sources like tuners and wideband recordings. - -#### Channel - Multiple Frequency -The multiple frequency tuner source feature allows you to specify multiple frequencies -to monitor for a system that uses rotating control channels. The **Rotation Delay** value -indicates the number of seconds that sdrtrunk should remain on a channel that has -stopped decoding before moving to the next frequency in the list. The application will -continue to try each frequency in the list until it discovers an active signal -to decode. - -#### Tuner Channelizer -This setting allows you to choose which channelizer sdrtrunk should use. The channelizer -is used to breakup a wide signal that you normally see from a tuner into a number -of smaller channels that are used by each of the decoders. - -**Channelizer Type** - choose between **Polyphase** and **Heterodyne** - -**Polyphase** is the default type and provides the best channelization with minimal to -no bleed over from adjacent channels. - -**Heterodyne** is less processor intensive and may be appropriate for lower powered -processors. However, this channelizer does not provide the best filtering and -some bleed over from adjacent channels can impact the performance of decoders. This -bleed over is only an issue if you have strong signals on adjacent channels next -to the channel that you are decoding. - diff --git a/v0.3/R820T_V0.3.0.md b/v0.3/R820T_V0.3.0.md deleted file mode 100644 index 7f0bf58..0000000 --- a/v0.3/R820T_V0.3.0.md +++ /dev/null @@ -1,39 +0,0 @@ -**Version:** 0.3.0 - -RTL-2832 R820T and R820T2 Tuner Configuration ---- - -![Figure 1: R820T Tuner Configuration](v0.3/images/R820T_V0.3.0.png) - -**Figure 1:** R820T Tuner Configuration - -The following settings shown in Figure 1 are available for configuring the tuner: - -#### Name -Name for the tuner configuration. - -#### Tuner Info Button -Provides a summary of details about the currently selected tuner, including USB ID, Vendor, Product, -Serial number, IR status, and Remote Wake status. - -#### Sample Rate -Allows you to change the sample rate. - -#### PPM -Adjusts the frequency correction Parts Per Million (PPM) value for the tuner. If you notice in -the spectral display that the frequency labels are slightly misaligned to observed signals, you -can adjust this value to align the frequency to the observed signals with known operating -frequencies. - -#### 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. \ No newline at end of file diff --git a/v0.3/SetupLinux_V0.3.0.md b/v0.3/SetupLinux_V0.3.0.md deleted file mode 100644 index b15c35b..0000000 --- a/v0.3/SetupLinux_V0.3.0.md +++ /dev/null @@ -1,37 +0,0 @@ -## Setup Linux - sdrtrunk Version: 0.4.x - -1. Download the latest release for the Linux operating system from https://github.com/DSheirer/sdrtrunk/releases -1. Use a zip utility such as 7-zip to unzip the release -1. Run the script: **/bin/sdr-trunk** - -## Setup Linux - sdrtrunk Version: 0.3.x - -1. Install Java JRE version 8 or newer from http://www.oracle.com/java. Note: if you are using airspy or hackrf, your computer should have 8GB or more of memory and you should use the 64-bit (x64) version of the java JRE. - -2. Verify java installation: - -``` -console: java -version - -java version "1.8.0_91" -Java(TM) SE Runtime Environment (build 1.8.0_91-b14) -Java HotSpot (TM) 64-bit Server VM -``` - -3. Download the sdrtrunk application. - -4. Install udev rules file for any tuners you'll be using into the /etc/udev/rules.d/ directory. - -The following udev files are available here: https://github.com/DSheirer/sdrtrunk/tree/master/src/main/resources - -**funcube-dongle.rules** -**52-airspy.rules** -**53-hackrf.rules** -**rtl-sdr.rules** - -5. Run the SDRTrunk application: - -``` -console: cd (download folder) -console: java -jar sdrtrunk-release-jar-filename -``` \ No newline at end of file diff --git a/v0.3/SetupWindows_V0.3.0.md b/v0.3/SetupWindows_V0.3.0.md deleted file mode 100644 index 48b0bea..0000000 --- a/v0.3/SetupWindows_V0.3.0.md +++ /dev/null @@ -1,28 +0,0 @@ -## Setup Windows - sdrtrunk Version: 0.4.x - -1. Download the latest release for the Windows operating system from https://github.com/DSheirer/sdrtrunk/releases -1. Use a zip utility such as 7-zip to unzip the release -1. Run the script: **/bin/sdr-trunk** - -## Setup Windows - sdrtrunk Version: 0.3.x - -1. Install Java JRE version 8 or newer from http://www.oracle.com/java. Note: if you are using the airspy or hackrf tuners, your computer should have 8GB of memory or more and use the 64-bit (x64) version of the java JRE. - -2. In a command prompt, verify your java installation: - -``` -c:\ java -version - -java version "1.8.0_91" -Java(TM) SE Runtime Environment (build 1.8.0_91-b14) -Java HotSpot (TM) 64-bit Server VM -``` - -3. Download the sdrtrunk application. - -4. Run the SDRTrunk application: - -``` -console: cd (download folder) -console: java -jar sdrtrunk-release-jar-filename -``` \ No newline at end of file diff --git a/v0.3/SoundCard_V0.3.0.md b/v0.3/SoundCard_V0.3.0.md deleted file mode 100644 index 9ff8b33..0000000 --- a/v0.3/SoundCard_V0.3.0.md +++ /dev/null @@ -1,12 +0,0 @@ -# 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, view the channel in the -[channel spectrum](ChannelSpectrum_V0.3.0) window to verify the audio routing is correct. -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. \ No newline at end of file diff --git a/v0.3/SpectralDisplay_V0.3.0.md b/v0.3/SpectralDisplay_V0.3.0.md deleted file mode 100644 index 339c116..0000000 --- a/v0.3/SpectralDisplay_V0.3.0.md +++ /dev/null @@ -1,68 +0,0 @@ -Spectral Display ---- - -The spectral display component shows the frequency activity of the currently selected tuner and overlays -a visual representation of channel configuration contained in the playlist and listed in the -[Channels](Channels_V0.3.0) tab. - -### Cursor -A cursor with frequency readout is automatically shown as you move the mouse about the spectral display window. -When zoomed in, the zoom level is also displayed below the frequency value. - -### Zoom -The spectral and waterfall displays can be zoomed together using the mouse scroll wheel, or using the -right-click context menu. - -When zoomed in, a small zoom window appears at the bottom of the waterfall display indicating the area -of the spectral and waterfall displays that is visible and the zoom level. You can left-click drag the -display with the mouse when zoomed in to drag the display left or right. - -### Context Menus - -Right-click anywhere in the spectral display to show a list of context-specific menu options. - -#### Channel Menu - -[Channels](Channels_V0.3.0) defined in the playlist are also displayed in the spectral display window. -Each channel exposes a context menu allowing you to start/stop the channel decoder. - -#### 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 - [Now Playing](NowPlaying_V0.3.0) tab. - * **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 Discrete Fourier Transform (DFT) results -that are displayed in the spectral display. -* **Averaging** - sets the averaging window size. Averaging occurs over multiple sets of DFT results. -* **Channel** - controls display of channel overlays. Choose to display ALL, NONE, or only the channels -currently ENABLED and decoding. -* **FFT Width** - bin size used in DFT 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 DFT is calculated and the spectral -display is updated. -* **Window Type** - specifies the windowing method to use prior to calculating the DFT. Windowing -minimizes signals from bleeding over into neighboring DFT bins. -* **Smoothing** - sets the smoothing filter type. Smoothing is applied across DFT bins within the -same DFT result set. - -#### Zoom Menu - -Changes the zoom size where 1x is no zoom and 64x is the display zoomed in 64 times. - -### Changing Displayed [Tuner](Tuners_V0.3.0) - -In the [Tuners](Tuners_V0.3.0) tab, click on the **Main** link for any of the tuners to -show that tuner's output in the main/primary spectral display. Click on the **New** link -to create a new spectral display window for the tuner. \ No newline at end of file diff --git a/v0.3/Streaming_V0.3.0.md b/v0.3/Streaming_V0.3.0.md deleted file mode 100644 index df82948..0000000 --- a/v0.3/Streaming_V0.3.0.md +++ /dev/null @@ -1,202 +0,0 @@ -**Version:** 0.3.0 - -Streaming Overview ---- -The SDRTrunk application supports streaming of multiple audio calls to multiple -remote audio streaming servers. Audio calls are temporarily recorded to disk in -MP3 audio format. The temporary recording is then queued for broadcast with one -or more audio streams. Streaming uses aliases to identify which stream(s) will -broadcast the audio recording. Each temporary recording contains metadata about -the call that is also forwarded to the streaming server. - -This concept allows you to create simple single channel audio streams or very -complex audio streams that are combined from multiple radio systems or radio -users. For example, you could monitor a group on a P25 system and a related -separate group on an LTR system and combine all calls from both systems into a -single broadcast channel. - -Temporary audio recordings that are queued for streaming in the order received. -When the streaming queue is empty, MP3 silence frames are streamed to maintain a -consistent connection to the remote server. When silence is streaming, the -metadata is updated to read '_Scanning..._'. - -![Figure 1: Streaming Tab](v0.3/images/Streaming_V0.3.0.png) -**Figure 1:** Streaming Tab - -Figure 1 shows the streaming configuration tab where you can add, copy and delete -streaming configurations. The following describes the streaming tabel columns: - -#### Streaming -Show an icon identifying the streaming server type. - -#### Name -The name assigned to the streaming channel. This is also the name that can be -selected when choosing a broadcast channel to add to an alias. - -#### Status -Shows the status of the connection. -* **Configuration Error** - the broadcast channel configuration contais an error -* **Connected** - connected to the remote streaming server and streaming audio -* **Connecting** - attempting to connect to the remote streaming server -* **Disabled** - the **Enable** button in the stream configuration is not checked -and this broadcast channel has been disabled for streaming. -* **Disconnected** - the stream is disconnected. This normally occurs when the -connection is interrupted and the application will normally attempt to reconnect. -* **Error** - there is an error with the stream configuration or remote server. -* **Invalid User Name/Password** - user name or password is incorrect -* **Invalid Mount/Stream ID** - the mount point or stream ID is not recognized by -the remote server -* **Max Sources Exceeded** - the remote server rejected the connection because -there are too many audio sources currently connected -* **Mount Point In Use** - your mount point is already in use. This can happen -if you disconnect from the server and reconnect too quickly. Waiting a few seconds -and restarting the connection will normally clear this error. -* **No Server** - the remote streaming server is not available. -* **Temporary Broadcast Error** - general temporary error -* **Unsupported Audio Format** - the remote server does not support MP3 audio - -#### Queued -The number of MP3 audio recordings that are waiting to be streamed - -#### Streamed -The number of MP3 audio recordings that have been streamed this session. - -#### Aged Off -The number of MP3 audio recordings that were removed from the streaming queue -because the start time of the recording exceeded the maximum wait time or Age -Limit. When this value grows large relative to the streamed count on a daily -basis, consider removing some of the aliases that you have assigned to be -streamed over this broadcast channel because the volume of call audio is -exceeding the application's ability to stream the audio in a timely manner. -It is normal for some calls to be aged off during periods of increased audio -volume. - -## Supported Servers - -The following servers are supported: -* [Broadcastify](http://www.broadcastify.com/) -* Icecast Version 2.3.x (TCP connection) -* [Icecast Version 2.4.1+](http://icecast.org/) (HTTP 1.1 connection) -* Shoutcast 1.x -* [Shoutcast 2.x/Ultravox 2.1](http://wiki.shoutcast.com/wiki/SHOUTcast_Broadcaster) - -## Audio Format -* MP3 lossless audio compression -* Constant Bit Rate (CBR) -* 8000 Hz Sample Rate -* 16-bit samples - -## Setup an Audio Stream -1. Click the **Streaming** tab -2. Click the **New** button and select the streaming server type -3. Create a unique name for the channel (each stream requires a unique name) -4. Fill in the server-specific stream details. See **Streaming Configurations** -below -5. Click **Save** -6. Attach this stream to one or more Aliases. - -## [Aliases](Aliases_V0.3.0) and Broadcast Channels - -Aliases are used for designating specific radio users and/or groups for streaming. -You can attach one or more Broadcast Channel identifiers to each alias. When a -call occurs, it is temporarily recorded to disk in MP3 format. Once the recording -is complete, it is queued for broadcast with each broadcast channel that is listed -for each and every alias involved in the call. - -For example, if you have a call from radio ID 123456 to talkgroup ABCD and the -radio ID has Channel A and Channel B attached, and the talkgroup has Channel B and -Channel C attached, then the call would be streamed to all three channels. - -### Attaching a Broadcast Channel to an Individual Alias -1. Create an [Alias List](Aliases_V0.3.0) and attach it to your decoding [Channel Configuration](Channels_V0.3.0) -1. In the **Aliases** tab, select the alias you want to stream -1. In the Alias editor screen, switch to the **Audio/Identifier** tab -1. Click **New** and select **Audio Broadcast Channel** -1. In the drop-down list, select the Broadcast Channel that you have previously configured -1. Click **Save** -1. Repeat these steps to add additional broadcast channels for the alias. - -### Attaching a Broadcast Channel to Multiple Aliases -1. Create an [Alias List](Aliases_V0.3.0) and attach it to your decoding [Channel Configuration](Channels_V0.3.0) -1. In the **Aliases** tab, select the the set of aliases that you want to modify -1. In the multiple alias editor, place a check in the **Stream** entry -1. Select the broadcast channel from the drop-down list -1. Click **Save** - -![Figure 2: Now Playing with Streaming Status Panel](v0.3/images/StreamingStatusPanel_V0.3.0.png) -**Figure 2:** Now Playing with Streaming Status Panel Showing - -## Streaming Status Panel - -Select the **View** menu at the top of the application window and click on the -**Show Streaming Status** menu item to turn on the streaming status panel at the -bottom of the application window as shown in Figure 2. This allows you to view -the **Now Playing**' window, channel details windows, and monitor your streaming -status at the same time. **Note:** this status panel is read-only. You can only -make changes to stream configurations in the **Streaming** tab. - -## Streaming Configurations - -### All Server Configurations -* **Delay** - this delays streaming of queued audio calls by the specified -minutes (0-60 minutes). Calls will remain in the queue and will not be streamed -until the call start time plus the delay minutes has elapsed. -* **Age Limit** - time limit for retaining audio recordings in the broadcast -queue (1-60 minutes). If a call remains in the queue too long, it is -automatically deleted once the call start time plus delay plus age limit has -elapsed. This feature ensures that your streaming queue doesn't grow to the -point that streaming will never catch up. It also ensures that what you're -streaming is relatively recent audio. Note: if you see that a large number of -your calls are being aged off (deleted prior to broadcast), consider -changing/reducing the number of aliases that you have designated for that -stream, or increase the age limit value to allow for temporary increases in -activity. -* **Enabled** - enables or disables a stream. Use this check box to turn -streaming on or off. -* **Save** - saves any changes you have made to the configuration. If a stream -is running when you make changes, the stream will be disconnected and then -recreated with the new settings. -* **Reset** - resets the editor window to the saved configuration values after -you have made changes to the editor. - -### Broadcastify -* **Lookup ...** - click this button to lookup your stream provider details on -Broadcastify and auto-configure your stream. Enter your user name and password -in the dialog window. Click **Get Feeds** and then select one of the -streams/feeds that appear in the list. Click **Ok**. -* **Name** - name of your feed -* **Server** - Broadcastify server URL for your feed -* **Port** - Broadcastify server port for your feed -* **Mount** - mount point for your feed -* **Password** - password for your feed -* **Feed ID** - your feed identifier - -### Icecast v2.3 and v2.4+ -* **Name** - unique name for your feed -* **Server** - server URL for your feed -* **Port** - server port for your feed -* **Mount** - mount point for your feed -* **User Name** - (v2.4+ only) user name for your feed -* **Password** - password for your feed -* **Description** - description of the feed contents -* **Genre** - genre of the feed contents -* **Public** - designates the feed as Public (checked) or Private (not checked) - -### Shoutcast v1.x -* **Name** - unique name for your feed -* **Server** - server URL for your feed -* **Port** - server port for your feed -* **Password** - password for your feed -* **Genre** - genre of the feed contents -* **Description** - description of the feed contents -* **Public** - designates the feed as Public (checked) or Private (not checked) - -### Shoutcast v2.x -* **Name** - unique name for your feed -* **Server** - server URL for your feed -* **Port** - server port for your feed -* **Stream ID** - numeric ID for your feed -* **User ID** - user name/ID for your feed -* **Password** - password for your feed -* **Genre** - genre of the feed contents -* **Public** - designates the feed as Public (checked) or Private (not checked) \ No newline at end of file diff --git a/v0.3/Tait1200_V0.3.0.md b/v0.3/Tait1200_V0.3.0.md deleted file mode 100644 index af85a2f..0000000 --- a/v0.3/Tait1200_V0.3.0.md +++ /dev/null @@ -1,19 +0,0 @@ -# Tait 1200 Decoder # - -The Tait 1200 decoder processes audio band GPS location bursts. - -Note: the decoder only decodes GPS data bursts. If you have access to a Tait -radio with GPS and can provide additional quality audio recordings of data -bursts from the radio, please contact the author in the Google support group. - -## Decoder Setup - Conventional or Repeater Network ## - -Setup a decoding channel with a NBFM decoder and select Tait 1200 in the aux -decoder configuration tab. - -## Decoder Setup - Analog Trunked Network ## - -Setup a decoding channel with one of the analog trunked radio decoders (LTR, -LTRNet, Passport, etc) and select Tait 1200 in the aux decoder configuration tab. - - diff --git a/v0.3/Tuners_V0.3.0.md b/v0.3/Tuners_V0.3.0.md deleted file mode 100644 index dd32d3f..0000000 --- a/v0.3/Tuners_V0.3.0.md +++ /dev/null @@ -1,124 +0,0 @@ -Tuners ---- -The tuners tab lists all tuners currently recognized and available for use by the sdrtrunk -application. You can create one or more tuner configurations for each tuner and identify -one of those configurations as the default configuration for the tuner. The application -attempts to reconfigure your tuner to the same settings used the last time that you ran the -software. - -![Figure 1: Tuners](v0.3/images/Tuners_V0.3.0.png) - -**Figure 1:** Tuners View - -The tuners view contains three sections with all available tuners listed in the top section, tuner -configurations listed in the lower-left panel and a tuner configuration editor panel in the -lower-right panel. - -Select a tuner row in the top table to view available tuner configurations in the lower-left. - -Select a tuner configuration in the lower-left table to view the tuner configuration editor panel -in the lower right. - -Supported Tuners ---- -The following tuners are currently supported by the SDRTrunk application. Additional tuner support will -be added in the future. - - * [Airspy](Airspy_V0.3.0) - * [Funcube Dongle Pro](FuncubeDonglePro_V0.3.0) (1.0) - * [Funcube Dongle Pro Plus](FuncubeDongleProPlus_V0.3.0) (2.0) - * [HackRF](HackRF_V0.3.0) - * [RTL-2832 with Elonics E4000](E4000_V0.3.0) - * [RTL-2832 with Rafael Micro R820T or R820T2](R820T_V0.3.0) - -Tuner Management ---- -The application automatically 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 frequency, and -then assigns the channel to the tuner. If no tuners can support the channel, then the channel will -not start and you will receive a popup message indicating that no tuners are available. - -Each tuner can source one or more channel frequencies so 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 adjust the center frequency -to provide a best-fit of all sourced channels, while ensuring that no channels overlap any -DC-spike that may be present in the center of the spectrum for some types of tuners. - -Tuners Table ---- -All available tuners are detailed in the table at the top of the tuners view. The following columns -are included in the table: - -#### Tuner -Description of the tuner model - -#### ID -Identifier or serial number of the tuner - -#### Sample Rate -Current sample rate setting for the tuner - -#### Frequency -Current center tuned frequency of the tuner. **Note:** the sdrtrunk application automatically adjusts -the tuner's center tuned frequency according to the channels that are being sourced from the tuner. You -can adjust this frequency and each of the decoding channels will adjust their offset to compensate. -However, it's recommended to let the application manage this setting for you. - -#### Channels -Number of decoding channels currently being sourced by the tuner. - -#### Spectral -Provides a quick-link for showing the tuner in the primary spectral display. Click the **Main** -link in the row to show that tuner in the primary spectral display. - -#### Display -Provides a quick-link to launch a new spectral display window for the tuner. Click the **New** -link in the row to create a new spectral display window for the tuner. - -**Note:** you can launch multiple windows for each tuner or combination of tuners. However, each -window adds to the overall processing workload for the computer and using too many spectral -display windows may impair application performance. - -Tuner Configuration Table ---- -The tuner configuration table lists all tuner configurations for the currently selected tuner. This -section includes a descriptive name for the tuner and a **Frequency** control for adjusting the -center tuned frequency for the currently selected tuner. The following columns are included in -the tuner configuration table: - -#### Tuner Type -Indicates the type of tuner for the configuration. - -#### Name -Name of the tuner configuration - -#### Assigned -Only one of the tuner configurations listed will contain an asterisk (*) indicating that the -configuration is the currently assigned configuration for the selected tuner. - -The following buttons allow you to manage your tuner configurations for the currently selected -tuner: - -#### New Button -Click to create a new tuner configuration for the selected tuner. - -#### Delete Button -Click to delete the currently selected tuner configuration. If you attempt to delete a -tuner configuration that is assigned to the currently selected tuner, a popup error -message will appear indicating that you have to assign another tuner configuration to -the tuner before you can delete the currently selected tuner configuration. - -#### Assign Button -Assigns the currently selected tuner configuration as the default configuration for the -currently selected tuner. The default configuration is used to configure the tuner -each time you start the application. - -Tuner Configuration Editor ---- -Selecting a tuner configuration in the tuner configuration table will load the -corresponding editor for the tuner configuration and allow you to change settings -for the tuner. See each specific tuner type listed above in the **Supported Tuners** -section for a listing of available settings. - -**Note:** any changes made to the default tuner configuration will be automatically -applied to the currently selected tuner. diff --git a/v0.3/UserManual_V0.3.0.md b/v0.3/UserManual_V0.3.0.md deleted file mode 100644 index 5e28ca4..0000000 --- a/v0.3/UserManual_V0.3.0.md +++ /dev/null @@ -1,62 +0,0 @@ -SDRTrunk User Manual ---- - -Application Overview ---- -SDRTrunk is a software application for monitoring, decoding and internet streaming of -analog and digital radio communications systems. It is designed to operate with -multiple external and dongle-type USB tuners. The application allows you to process -multiple radio channels simultaneously, limited only by your computer's processing -power and the tunable bandwidth of each of the tuners attached to your computer. It -also supports automatically creating and tuning to traffic channels in trunked -radio systems when decoding the system control channel. - -![Figure 1: Application Overview](v0.3/images/ApplicationOverview_V0.3.0.png) - -**Figure 1:** Application Overview showing a single Airspy tuner decoding multiple -trunked radio control channels and automatically generating traffic channels for -each system. - -Spectral Display ---- -* [Spectral Display](SpectralDisplay_V0.3.0) - -Audio Playback ---- -* [Audio Panel](AudioPanel_V0.3.0) - -Configuration Tabs and Views ---- -* [Now Playing](NowPlaying_V0.3.0) -* [Aliases](Aliases_V0.3.0) -* [Channels](Channels_V0.3.0) -* [Map](Map_V0.3.0) -* [Streaming](Streaming_V0.3.0) -* [Tuners](Tuners_V0.3.0) - -Decoders ---- -* [Decoders](Decoders_V0.3.0) - -Menu Items ---- -#### File > Logs and Recordings -Opens a file explorer to your user directory to view the logs and recordings folders. - -#### File > Icon Manager -Opens the Icon Manager dialog where you can import additional icons to use for your aliases. - -#### File > Exit -Closes the application - -#### View > Show Streaming Status -Toggles visibility of the streaming status panel - -#### View > [Preferences](Preferences_V0.3.0) -Opens the preferences dialog - -#### Screen Capture -Creates a screen shot picture and stores the image in your Screen Captures folder. Use the -Logs and Recordings menu item to open a file explorer and browse to the Screen Captures folder. - - diff --git a/v0.3/WaterfallDisplay_V0.3.0.md b/v0.3/WaterfallDisplay_V0.3.0.md deleted file mode 100644 index bc4b5c4..0000000 --- a/v0.3/WaterfallDisplay_V0.3.0.md +++ /dev/null @@ -1,24 +0,0 @@ -# Waterfall Display # - -The waterfall display shows a history of the frequency content of the currently -displayed [tuner](Tuners_V0.3.0). - -![Figure 1: Waterfall](v0.3/images/Waterfall_V0.3.0.png) - -## Context Menus ## - -Right-click anywhere in the waterfall display to view a list of context-sensitive menu -options. See the [Spectral Display](SpectralDisplay_V0.3.0) 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. - -Note: if you see a signal in the waterfall, you can pause the waterfall and use the -zoom control to zoom in on the transmission to inspect the bandwidth and frequency, or -other features of the signal. You can optionally expand the viewable height of the -waterfall window to view waterfall signals that appear to have scrolled off the -screen. There is a limited history available. - -![Figure 2: Waterfall Paused](v0.3/images/WaterfallPaused_V0.3.0.png) diff --git a/v0.3/images/Airspy_V0.3.0.png b/v0.3/images/Airspy_V0.3.0.png deleted file mode 100644 index 91d05ca..0000000 Binary files a/v0.3/images/Airspy_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/AliasCreateNew_V0.3.0.png b/v0.3/images/AliasCreateNew_V0.3.0.png deleted file mode 100644 index 20cf9b5..0000000 Binary files a/v0.3/images/AliasCreateNew_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/AliasExampleABCTrucking_V0.3.0.png b/v0.3/images/AliasExampleABCTrucking_V0.3.0.png deleted file mode 100644 index 82d06fd..0000000 Binary files a/v0.3/images/AliasExampleABCTrucking_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/AliasExampleAudioNonRecordable_V0.3.0.png b/v0.3/images/AliasExampleAudioNonRecordable_V0.3.0.png deleted file mode 100644 index 059d3c5..0000000 Binary files a/v0.3/images/AliasExampleAudioNonRecordable_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/AliasExampleAudioNonRecording_V0.3.0.png b/v0.3/images/AliasExampleAudioNonRecording_V0.3.0.png deleted file mode 100644 index f1450a8..0000000 Binary files a/v0.3/images/AliasExampleAudioNonRecording_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/AliasExampleAudioPriority_V0.3.0.png b/v0.3/images/AliasExampleAudioPriority_V0.3.0.png deleted file mode 100644 index cc576b0..0000000 Binary files a/v0.3/images/AliasExampleAudioPriority_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/AliasExampleAudioStreaming_V0.3.0.png b/v0.3/images/AliasExampleAudioStreaming_V0.3.0.png deleted file mode 100644 index 9ded060..0000000 Binary files a/v0.3/images/AliasExampleAudioStreaming_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/AliasExampleChannelAliasList_V0.3.0.png b/v0.3/images/AliasExampleChannelAliasList_V0.3.0.png deleted file mode 100644 index 1b4761b..0000000 Binary files a/v0.3/images/AliasExampleChannelAliasList_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/AliasExampleLTRTalkgroup_V0.3.0.png b/v0.3/images/AliasExampleLTRTalkgroup_V0.3.0.png deleted file mode 100644 index 6655a93..0000000 Binary files a/v0.3/images/AliasExampleLTRTalkgroup_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/AliasExampleRadioIdentifier_V0.3.0.png b/v0.3/images/AliasExampleRadioIdentifier_V0.3.0.png deleted file mode 100644 index ece55a8..0000000 Binary files a/v0.3/images/AliasExampleRadioIdentifier_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/AliasExampleTalkgroup_V0.3.0.png b/v0.3/images/AliasExampleTalkgroup_V0.3.0.png deleted file mode 100644 index b9b3ead..0000000 Binary files a/v0.3/images/AliasExampleTalkgroup_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/AliasExampleWildcardAlias_V0.3.0.png b/v0.3/images/AliasExampleWildcardAlias_V0.3.0.png deleted file mode 100644 index 75732f9..0000000 Binary files a/v0.3/images/AliasExampleWildcardAlias_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/AliasExampleWildcardTalkgroup_V0.3.0.png b/v0.3/images/AliasExampleWildcardTalkgroup_V0.3.0.png deleted file mode 100644 index 67cc188..0000000 Binary files a/v0.3/images/AliasExampleWildcardTalkgroup_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/Aliases_V0.3.0.png b/v0.3/images/Aliases_V0.3.0.png deleted file mode 100644 index f779b26..0000000 Binary files a/v0.3/images/Aliases_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/ApplicationOverviewAnnotated_V0.3.0.png b/v0.3/images/ApplicationOverviewAnnotated_V0.3.0.png deleted file mode 100644 index 8157508..0000000 Binary files a/v0.3/images/ApplicationOverviewAnnotated_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/ApplicationOverview_V0.3.0.png b/v0.3/images/ApplicationOverview_V0.3.0.png deleted file mode 100644 index c9ace25..0000000 Binary files a/v0.3/images/ApplicationOverview_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/AudioPanelMono_V0.3.0.png b/v0.3/images/AudioPanelMono_V0.3.0.png deleted file mode 100644 index 32357e0..0000000 Binary files a/v0.3/images/AudioPanelMono_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/AudioPanelMuted_V0.3.0.png b/v0.3/images/AudioPanelMuted_V0.3.0.png deleted file mode 100644 index 30ee001..0000000 Binary files a/v0.3/images/AudioPanelMuted_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/AudioPanelStereo_V0.3.0.png b/v0.3/images/AudioPanelStereo_V0.3.0.png deleted file mode 100644 index 572a5da..0000000 Binary files a/v0.3/images/AudioPanelStereo_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/ChannelMapManager_V0.3.0.png b/v0.3/images/ChannelMapManager_V0.3.0.png deleted file mode 100644 index dd875dd..0000000 Binary files a/v0.3/images/ChannelMapManager_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/ChannelsAuxDecoderEditor_V0.3.0.png b/v0.3/images/ChannelsAuxDecoderEditor_V0.3.0.png deleted file mode 100644 index f75fcc0..0000000 Binary files a/v0.3/images/ChannelsAuxDecoderEditor_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/ChannelsDecoderEditor_V0.3.0.png b/v0.3/images/ChannelsDecoderEditor_V0.3.0.png deleted file mode 100644 index 1407262..0000000 Binary files a/v0.3/images/ChannelsDecoderEditor_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/ChannelsLoggingEditor_V0.3.0.png b/v0.3/images/ChannelsLoggingEditor_V0.3.0.png deleted file mode 100644 index 6a08758..0000000 Binary files a/v0.3/images/ChannelsLoggingEditor_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/ChannelsNameEditor_V0.3.0.png b/v0.3/images/ChannelsNameEditor_V0.3.0.png deleted file mode 100644 index 4b9858f..0000000 Binary files a/v0.3/images/ChannelsNameEditor_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/ChannelsRecordingEditor.png b/v0.3/images/ChannelsRecordingEditor.png deleted file mode 100644 index 0761107..0000000 Binary files a/v0.3/images/ChannelsRecordingEditor.png and /dev/null differ diff --git a/v0.3/images/ChannelsSourceEditor_V0.3.0.png b/v0.3/images/ChannelsSourceEditor_V0.3.0.png deleted file mode 100644 index 57888ce..0000000 Binary files a/v0.3/images/ChannelsSourceEditor_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/E4000_V0.3.0.png b/v0.3/images/E4000_V0.3.0.png deleted file mode 100644 index 82fdede..0000000 Binary files a/v0.3/images/E4000_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/FuncubeDongleProPlus_V0.3.0.png b/v0.3/images/FuncubeDongleProPlus_V0.3.0.png deleted file mode 100644 index 9ae168b..0000000 Binary files a/v0.3/images/FuncubeDongleProPlus_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/FuncubeDonglePro_V0.3.0.png b/v0.3/images/FuncubeDonglePro_V0.3.0.png deleted file mode 100644 index f38ae48..0000000 Binary files a/v0.3/images/FuncubeDonglePro_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/GettingStartedChannelsView_V0.3.0.png b/v0.3/images/GettingStartedChannelsView_V0.3.0.png deleted file mode 100644 index bd5e485..0000000 Binary files a/v0.3/images/GettingStartedChannelsView_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/HackRF_V0.3.0.png b/v0.3/images/HackRF_V0.3.0.png deleted file mode 100644 index b906724..0000000 Binary files a/v0.3/images/HackRF_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/Map_V0.3.0.png b/v0.3/images/Map_V0.3.0.png deleted file mode 100644 index f560ae5..0000000 Binary files a/v0.3/images/Map_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/MultipleAliasEditor_V0.3.0.png b/v0.3/images/MultipleAliasEditor_V0.3.0.png deleted file mode 100644 index f78e5af..0000000 Binary files a/v0.3/images/MultipleAliasEditor_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/NowPlayingDetailsView_V0.3.0.png b/v0.3/images/NowPlayingDetailsView_V0.3.0.png deleted file mode 100644 index f119400..0000000 Binary files a/v0.3/images/NowPlayingDetailsView_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/NowPlayingEventsView_V0.3.0.png b/v0.3/images/NowPlayingEventsView_V0.3.0.png deleted file mode 100644 index 8cf1f80..0000000 Binary files a/v0.3/images/NowPlayingEventsView_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/NowPlayingMessagesView_V0.3.0.png b/v0.3/images/NowPlayingMessagesView_V0.3.0.png deleted file mode 100644 index 65673bb..0000000 Binary files a/v0.3/images/NowPlayingMessagesView_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/Preferences_V0.4.0.png b/v0.3/images/Preferences_V0.4.0.png deleted file mode 100644 index b002f69..0000000 Binary files a/v0.3/images/Preferences_V0.4.0.png and /dev/null differ diff --git a/v0.3/images/R820T_V0.3.0.png b/v0.3/images/R820T_V0.3.0.png deleted file mode 100644 index d7ecc6d..0000000 Binary files a/v0.3/images/R820T_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/StreamingStatusPanel_V0.3.0.png b/v0.3/images/StreamingStatusPanel_V0.3.0.png deleted file mode 100644 index 7eab990..0000000 Binary files a/v0.3/images/StreamingStatusPanel_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/Streaming_V0.3.0.png b/v0.3/images/Streaming_V0.3.0.png deleted file mode 100644 index ff42dce..0000000 Binary files a/v0.3/images/Streaming_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/Tuners_V0.3.0.png b/v0.3/images/Tuners_V0.3.0.png deleted file mode 100644 index 76021c2..0000000 Binary files a/v0.3/images/Tuners_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/WaterfallPaused_V0.3.0.png b/v0.3/images/WaterfallPaused_V0.3.0.png deleted file mode 100644 index ffe9657..0000000 Binary files a/v0.3/images/WaterfallPaused_V0.3.0.png and /dev/null differ diff --git a/v0.3/images/Waterfall_V0.3.0.png b/v0.3/images/Waterfall_V0.3.0.png deleted file mode 100644 index a02d133..0000000 Binary files a/v0.3/images/Waterfall_V0.3.0.png and /dev/null differ