d-star 101 copyright © 2006 – texas interconnect team presented by texas interconnect team k5tit

Copyright © 2006 – Texas Interconnect Team

D-STAR 101

Presented by

Texas Interconnect TeamK5TIT


D-STAR 101

IntroductionsJim McClellan N5MIJ Pete Loveall AE5PLLisa McClellan K5LRM Gerry Dalton W5MAYBill Moore N5ZPR Al Shjarback K1DOFred Varian WD5ERD

All Users. We can talk about reality!

Session is being recorded. Please hold questions until asked.No additional recording or photography permitted.


D-STAR 101

D-STAR owned by JARL– Not owned by manufacturers– Not Public Domain

Disclaimer– Not going to debate “what should be” or “why didn’t they…”


D-STAR 101

D-STAR Gateway owned by Icom– Not Public Domain or Open Source– May not be copied, shared or redistributed


D-STAR 101

Version 1.2 of D-STAR in USA(?)– Ver 1.0 – Dec ’03, No Gateway, 2 users– Ver 1.1 – Jan ’05, Gateway, More users, systems– Ver 1.2 – May ’06, VHF/UHF repeaters, more new users &

systems


D-STAR 101

Objectives– Convey enough information to allow use of new hardware

Repeater installationGateway, if chosenUser Radios

– Convey sufficient Gateway information to allow you to join and protect D-Star network

– Some information on 3rd party applications developed– Gateway Certification Exam for new trustees

No Sales Effort – Just real results & infoTight Schedule – lots of material


D-STAR 101

Introduction to D-STAR


D-STAR 101Introduction to D-STAR

D-STAR is not necessarily what we expect– Forget everything you think you know about repeaters.– Forget everything you think you know about networking.

Existing knowledge will help, IF you can ignore assumptions!



D-STAR summary– Simultaneous digital voice and data– Better Spectral Efficiency– Better Performance– Applications, Applications, Applications


D-STAR 101



D-Star vs. FM OperationFM

Frequency, Offset, PL

Control codes, if available, for linking

D-STARFrequency, Offset, Mode, Call Signs (up to 4!)

Gateway OperationUser Linking, not site linking

No person-to-person private conversations. Everyone on both ends hears both sides of the conversation.

Probable confusion from D-STAR linking vs. normal experience

Will explore in detail later in class



Site Equipment ProgrammingRP2C

Programmed via Ethernet. You MUST know its address!Default 172.16.0.1

Recommend 172.16.10

Recommend labeling RP2C with 172.16.0.x address

Parameters for Repeaters (suggestion)23 cm on Port ‘A’

70 cm on Port ‘B’

2 m on Port ‘C’



Site Equipment ProgrammingRP2V, RP2000V, RP4000V

Programmed individually via USB. Multiple COM ports, unless over- ridden

Tx Freq

Rx Freq



Site Equipment ProgrammingRP2D

Programmed via USB. Multiple COM ports, unless over-riddenFreq

Offset



Other Site EquipmentPA’s

Duplexers

Filters

Feedline

Antenna

Impact of Window Filters on System Performance



Questions/Discussion


D-STAR 101

Gateway Overview


D-STAR 101Gateway Overview

Gateway FunctionsAuthorization– Nothing crosses gateway if not authorized

– Local usage unaffected

Routing– Allows very cellular-like roaming

• Timing constraints, to be discussed a bit later. Not immediate



D-Star GatewaysIdentical Implementations

Call sign, Internet Address, & MAC address change

Benefits

Specific Network segments & recommendations172.16.0.x (172.16.0.1 -> 172.16.0.10)

10.0.0.x (NO CHANGES* No additions!)



Gateway RequirementsFixed, Routable Internet IP Address

Router must support Class ‘A’ Network on LAN Port

Router must support Port Forwarding

PC, with two NIC’s, Linux, as specified

Unique call required, probably club call (NOT Trustee!)

Gateway PC and RP2C must be co-locatedVPN testing

NY & CA examples



Users all have Fixed IP AddressesIP Address only used on device on other side of ID-1

Radios are transparent bridges

IP address not used for voice or low-speed data

Use of multiple ID’sUse when multiple radios in use at same time

(ie: ID-800 for voice, ID-1 for data)

Routing all done by Call Sign, must differentiate



Gateway Call RoutingAll calls are source-routed

Originating gateway determines complete route to output port/band

No modification/rerouting by target Gateway

Creates potential problems – discuss in later segment



SummaryAll Gateways configured identically

Allows “roaming”

Gateways require Fixed Internet address

Gateway routers have MUST support Class ‘A’ LAN

Gateway PC must be at site with RP2C

Users all have fixed IP address assigned

Radios are transparent bridges

Gateway calls are Source-Routed


D-STAR 101

Gateway and Data File Concepts


D-STAR 101


Gateway driven by 3 data tablesGIP - list of known Gateway systems

RIP - list of IP Block reservations for users

MNG - list of users and most recent Gateway


D-STAR 101



D-STAR 101


Primary Data Tables in MEMORYDisk files are backups of last generation

No way to directly edit memory tablesMNG has limited “delete”

Indirect editing only“write”/edit/”read”

synchronization issues


D-STAR 101


Boot sequence of new gatewaySynchronizes with TRUST_SERVER

Pulls GIP, RIP, & MNG tables

Contacts EVERY Gateway in GIP table for sync

Database is replicated, not distributed

Network is full-mesh, not hierarchical


D-STAR 101


Periodic Gateway SyncDaily

Whenever contacts are made inter-zoneTiming?

Problems resulting from Gateway sync timingUsers unable to hear directed calls

(source routing!)

Propagation of errors throughout networkHard to remove


D-STAR 101


How to force clean start

Shut down gateway processes – dsgwd & dsipsvd

Completely clear /var/dsipsvd directory

Reboot GatewayTables in memory not cleared if processes restarted


D-STAR 101


Potentially many independent D-STAR networks

All based on definition of TRUST_SERVER

System cannot participate in multiple networks

would cross-sync and merge networks


D-STAR 101


Summary

Three primary tables – GIP, RIP, & MNG tables

Primary tables are in memory

Disk files are backup

Gateway pull initial tables from TRUST_SERVER

Cannot directly edit tables

Process for cleaning & restarting


D-STAR 101




D-STAR 101

Break


D-STAR 101

Gateway Installation & Verification


D-STAR 101


Process OverviewBuild System

Test & Validate with Icom Test System

Completely clear the system

Change to production TRUST_SERVER

Reboot

Test & Validate

Importance of Validation on Test System vs. Production


D-STAR 101


Building the GatewayRS-RP2C Setting Manual – READ FIRST!

Linux Installation Fedora Core 4. FC 5 Not yet verified.

Watch configuration of ‘named’. Manual not clear

Test & validate ‘named’ as described in manual

Generally, don’t run GUI – set runlevel as instructed


D-STAR 101


Router InformationNeed MAC address of LAN port on router

Many have labels. Some are correct.

‘arp’ command will always give correct data.


D-STAR 101



D-STAR 101


Gateway InstallationRun the ‘tar’ command from the ‘/’ directory!

Follow instructions to copy .conf files

Configure /etc/dsgwd.conf & /etc/dsipsvd.confSet TRUST_SERVER to TEST SYSTEM!

Configure /etc/syslog.conf for log files – VERY helpful!

Create /var/dsipsvd


D-STAR 101


Startup of GATEWAY

MANUAL IS WRONGSignificant typo on p.6!


D-STAR 101



D-STAR 101


Correct StartupBoth processes running (dsgwd * dsipsvd)

ps –aef | grep dstar

Complete set of files in /var/dsipsvd (GIP, RIP, MNG)

No errors in /var/log/dsipsvd.log

If errors, review log files. Most likely errors:

Incorrect router MAC address

Incorrectly configured ‘named’


D-STAR 101


Test ProcessCoordinate with Icom Tech Support for use of Test System

Verify system running correctly

Execute ONE (1!) ‘reserve’ command

Add ONE (1!) user (yourself)

Execute ‘push mng’ command

Coordinate test QSO with Icom Tech Support

When correctly validated, they’ll give you information on production TRUST_SERVER (USRoot)


D-STAR 101


Moving to ProductionClear system

Change TRUST_SERVER

Reboot

Execute ONE (1!) ‘reserve’ command

Add ONE (1!) user (Yourself)

Execute ‘push mng’

Coordinate test QSO

Add additional users as requiredExecute addional ‘reserve’ commands as required


D-STAR 101


Command QueuesAll interaction with Gateway is via command queues

/var/dsipsvd-cmdin & /var/dsipsvd-cmdout

Most commands should generate ‘200 Command OK’

Otherwise, look in log files for error details/var/log/dsgwd.log

/var/log/dsipsvd.log

Limited help available via ‘help’ command


D-STAR 101



D-STAR 101


SummaryTake your time in installation, follow instructions

Pay attention to typo on p.6 of manual

Test with Icom Tech Support to validate

Join Production network

Be prudent in use of ‘reserve’ command

Watch log files for error descriptions


D-STAR 101




D-STAR 101

Gateway Operations


D-STAR 101Gateway Operations

Four call signs used

MYCALL – Call sign of the originating station

URCALL – Call sign of the desired target station, or CQCQCQ

RPT1 – Call sign (& port) of the originating repeater

RPT2 – Call sign & designator of the gatewayCan also be used for designated local cross-band use



RegistrationNo registration required for local use

No call sign required for local use !!!!

No private conversations both ends hear all

User linking, not site linkingNot all users on site can participate

Opportunity for confusion!!!



Multiple ways to traverse GatewayUser-Specific call

“Follow-me Roaming”

Sync Timing IssuesSource Routing & gateway sync timing create inability to hear a

user- specific call – illustrate in a moment.

Zone callExample - URCALL = ‘/K5TIT’

Specific routing of zone call – defaults to Port ‘A’

Port-specific zone callExample – URCALL = ‘/K5TIT C’



Source Routing vs. Sync TimingCreates inability to receive User-specific call

Discuss example



User ConcernsUser “error codes”

‘UR *’

‘RPT ?’

‘Did I make the repeater?’Courtesy tone discussion

Problems with full-duplex operation

‘Kerchunking a D-STAR systemNo squelch tail

Call known bad user, (ie: WN5ABC), should return ‘UR *’



Interfacing Digital and Analog SystemsTechnically possible – of course!

LimitationsAnalog users can’t vary call signs like URCALL & RPT2

Analog users can’t participate in all conversations

Creates impression of “D-STAR doesn’t work”

Analog users can’t see any included dataD-STAR repeaters pass all D-STAR encoded voice and data.

Also allows use of applications, discussed later

Good use of analog/digital interfaceEmergency situation, no gateway, local-only

MUST limit confusion


D-STAR 101

Public Relations & promotion of D-Star with new & existing users. (LISA)


D-STAR 101

Adding New Users


D-STAR 101

Call sign length and why

Call sign modifier, who needs them, and how to handle them.

DNS alias

Command line

Checking the results

Local Registrar


D-STAR 101Call signs

Call signs must have a total length of eight characters.

The 8th column contains the Port ID or Modifier for a user.


D-STAR 101

Call sign modifier

Who needs them

How to handle them


D-STAR 101

Call sign modifiers

This is the extra letter placed in the 8th column of a user’s call sign.


D-STAR 101

Who needs them

Users that need more than a single ID.

Any user that will have two or more radios in use at the same time.

Any user that needs more than one IP address.


D-STAR 101

How to handle them

The recommended convention is a letter added to the 8th column.

Example

N5ZPR**B


D-STAR 101

DNS Alias

This applies the local DNS entry for D-Star.

Call sign in lower case

A “-” between a modifier and the call sign

Example

n5zpr

n5zpr-b


D-STAR 101

Add Command

Call Sign (Upper Case)

Area Repeater (Upper Case)

Zone Repeater (Upper Case)

Zone Public IP Address

Assigned IP Address

DNS Alias


D-STAR 101

Entering Command

This is done from the Linux command prompt


D-STAR 101

Check the Results

Check output queue

Check the MNG table


D-STAR 101

Local Registrar

Each system should have a local Registrar. Someone to keep track of who was assigned what IP address. That person should also be the one who adds users.


D-STAR 101

User Configurations


D-STAR 101Applications



D-STAR 101

DStarMonitor

Activity Monitor


D-STAR 101

• Java Application– Runs on Gateway server– Requires Java 1.5.0 or above– Uses jPCAP (port monitor)– Uses JDBC (mySQL driver for dstarusers.org)

• Activity monitor on Gateway <-> Controller IP link

DStarMonitor


D-STAR 101Station ID

• All station presence is reported to the Gateway from the Controller, even RF-only

• RF-only does not identify type of activity

• RF<->Gateway activity identifies type of activity (DV or DD)

• Only IDs reported from the controller recorded


D-STAR 101Gateway Activity

• DV activity totaled per transmission for one record

• DD activity reported for each IP packet

• Packets not recorded, just stations, times, time spans, and packet sizes

• Use these records for Gateway usage accounting


D-STAR 101DStarMonitor

Internet

Router

Data Repeater Voice Repeater

Gateway Server

Controller

Repeater Site

JDBC to SQL

DStarMonitor

jPCAP


D-STAR 101dstarusers.org


D-STAR 101dstarusers.org

• Controlled access to MySQL

• Must open firewall port for your gateway

• Register your system on-line at:

• http://www.d-starusers.org/gwreg1.php

• Sysop will send you return email with further details


D-STAR 101

D-PRS

Icom GPS/APRS Gateway


D-STAR 101D-PRS

• Icom implements GPS reporting on DV

• GPS is carried on standard DV data channel

• APRS Interfaces Developed– javAPRSSrvr – IGate (gateway to APRS-IS)– DStarTNC2 – APRS client interface– DGate – TNC-X D-STAR->APRS RF Interface


D-STAR 101

javAPRSSrvr/DStarTNC2

• Java/J# based

• Bidirectional

• DV error detection

• Loop protection

• Icom GPS supported

• APRS TNC2 format supported


D-STAR 101

D-PRSAPRS-IS

DStar Radio

3 WireRS232

javAPRSIGatejavAPRSIGate

DSTARIntefaceTNCInterfaceTo/From

Serial Port

Server

TCP/IPto

APRS-IS

IPAPRS-IS


D-STAR 101

D-PRSAPRS Client

DStar Radio

APRS/SerialClient

3 WireRS232

APRS ClientAPRS Client

Serial ClientSerial Client

DStarTNC2

TCP/IP

TCP/IP

To/FromSerial Port


D-STAR 101

D-PRSD-STAR Repeaters

d-star 101 copyright © 2006 – texas interconnect team presented by texas interconnect team k5tit

Documents

dstar slide

dstar frequency

texas interconnect team

class slide

redistributed slide

immediate slide

port c slide

system performance slide