1 / 9

D-STAR Operating Protocols and Best Practices

D-STAR Operating Protocols and Best Practices. John Davis - WB4QDX GA ARES District Emergency Coordinator – Georgia Public Broadcasting ARES Emergency Coordinator – Gwinnett County, Georgia WB4QDX@arrl.net. Don’t Forget Simplex.

seth
Download Presentation

D-STAR Operating Protocols and Best Practices

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. D-STAROperating Protocols and Best Practices John Davis - WB4QDX GA ARES District Emergency Coordinator – Georgia Public Broadcasting ARES Emergency Coordinator – Gwinnett County, Georgia WB4QDX@arrl.net

  2. Don’t Forget Simplex • Simplex mode for direct communication, point-to-point low speed data • Basic Simplex settings • Frequency/Offset (none) • Mode = DV • MYCALL (MY) = your own callsign (WB4QDX) • URCALL (UR) = CQCQCQ • RPT1 = Blank • RPT2 = Blank • Consider repeater output simplex in memory adjacent to repeater • Designate DV simplex frequencies for local use plus store National Simplex Frequency of 145.670

  3. Remember the Basics • Basic local repeater settings: • Frequency/Offset (some odd splits in SERA states) • Mode = DV • MYCALL (MY) = your own callsign (WB4QDX) • URCALL (UR) = CQCQCQ • RPT1 = Local repeater and module (ex. K4WAK C, note module always in 8th space) • RPT2 = Always use repeater and gateway “G” (ex. K4WAK G to route to Gateway (even if not linking) • Store in memory for easy recall • Store UNLINK ( U) in UR in adjacent memory for quick unlinking

  4. What Happens When Linking? • Link command is transmitted with contents of UR field (ex. REF002AL) • Local repeater responds with voice announcement • “Remote System Linked” is link is established • “Remote System Busy” if already linked to something else • Listen for at least one minute to ensure remote repeater is idle (any voice activity will not be heard until next user transmits on remote repeater)

  5. Linking Etiquette • LISTENFIRST • If idle, check to see if repeater is currently linked by sending “I” command in UR (ex. K4WAK I) • If linked, voice announcement will reply “Remote System Linked” • If unlinked, voice announcement will reply “No Link Established” • Announce your intentions • Send linking command • If you linked it, unlink repeater when finished

  6. Reflector Practices • Know a reflector’s typical use, any net schedules • REF001C is the “worldwide meeting place” • REF014 for West Coast repeaters • REF015C for D-RATS/D-STAR data • REF030 for Georgia repeaters • Remember to listen and wait before transmitting to ensure it’s clear

  7. Callsign Routing Practices • Remember you are barging in! • You can’t hear if distant repeater is active • Remote station must program reverse route or press one touch “RX-CS” key to quickly program reverse path • Consider using Callsign Routing to initiate call, then link repeaters so users on both ends are included • When QSO is over, move radio channel select off one, then back to clear temporary callsign routing

  8. Net Etiquette LISTEN carefully to net instructions Leave space between transmissions so others can join in or break Use “Quick Key” to raise your hand (TX for one second to send callsign) Don’t “kerchunk” during net (NCS sees callsigns and thinks it’s a breaking station) Turn off auto TX or beaconing during net

  9. Questions?

More Related