|
1 | 1 | %C%#############################################################
|
2 | 2 | %C%# #
|
3 |
| -%C%# Configuration file for Dire Wolf # |
| 3 | +%C%# Sample configuration file for Dire Wolf # |
4 | 4 | %C%# #
|
5 | 5 | %L%# Linux version #
|
6 | 6 | %W%# Windows version #
|
|
14 | 14 | %R% It would be a maintenance burden to keep most of
|
15 | 15 | %R% two different versions in sync.
|
16 | 16 | %R% This common source is now used to generate the
|
17 |
| -%R% two different variations while having only a single |
| 17 | +%R% three different variations while having only a single |
18 | 18 | %R% copy of the common parts.
|
19 | 19 | %R%
|
20 | 20 | %R% The first column contains one of the following:
|
|
38 | 38 | %M%# /usr/local/share/doc/direwolf/ or /usr/share/doc/direwolf/
|
39 | 39 | %M%# Concise "man" pages are also available for Mac OSX.
|
40 | 40 | %C%#
|
| 41 | +%C%# Recommended Reading for everyone: |
| 42 | +%C%# "Understanding APRS Packets" in https://github.com/wb2osz/aprsspec |
| 43 | +%C%# |
| 44 | +%C%# |
41 | 45 | %C%# Questions??? Join the discussion forum: https://groups.io/g/direwolf
|
42 | 46 | %C%#
|
43 | 47 | %C%#
|
|
90 | 94 | %C%#############################################################
|
91 | 95 | %C%# #
|
92 | 96 | %C%# FIRST AUDIO DEVICE PROPERTIES #
|
93 |
| -%C%# (Channel 0 + 1 if in stereo) # |
| 97 | +%C%# (Channel 0 or 0 + 1 if in stereo) # |
94 | 98 | %C%# #
|
95 | 99 | %C%#############################################################
|
96 | 100 | %C%
|
|
121 | 125 | %W%# * 4: Speakers (Realtek High Definiti (channels 0 & 1)
|
122 | 126 | %W%# 5: Realtek Digital Output (Realtek
|
123 | 127 | %W%#
|
124 |
| -%W%# Example: To use the microphone and speaker connections on the |
125 |
| -%W%# system board, either of these forms can be used: |
| 128 | +%W%# It is recommended that you use a unique substring of the device description. |
| 129 | +%W%# For example, use "High" or "Realtek High Def" for the built in sound system. |
| 130 | +%W%# Use "USB", or a longer string to distinguish amount multiple devices for a USB audio. |
| 131 | +%W%# You can also use numbers but you are asking for trouble. Device numbers can change. |
126 | 132 | %W%
|
127 |
| -%W%#ADEVICE High |
128 |
| -%W%#ADEVICE 3 4 |
| 133 | +%W%#ADEVICE USB |
129 | 134 | %W%
|
130 | 135 | %W%
|
131 | 136 | %W%# Example: To use the USB Audio, use a command like this with
|
|
158 | 163 | %L%
|
159 | 164 | %L%# ADEVICE plughw:1,0
|
160 | 165 | %L%
|
161 |
| -%L%# You can also use "-" or "stdin" to pipe stdout from |
162 |
| -%L%# some other application such as a software defined radio. |
163 |
| -%L%# "stdin" is not an audio device. Don't use this unless you |
164 |
| -%L%# understand what this means. Read the User Guide. |
165 |
| -%L%# You can also specify "UDP:" and an optional port for input. |
166 |
| -%L%# Something different must be specified for output. |
167 |
| -%L% |
168 |
| -%L%# ADEVICE stdin plughw:1,0 |
169 |
| -%L%# ADEVICE UDP:7355 default |
170 |
| -%L% |
171 | 166 | %R% ---------- Mac ----------
|
172 | 167 | %R%
|
173 | 168 | %M%# Macintosh Operating System uses portaudio driver for audio
|
|
182 | 177 | %M%
|
183 | 178 | %M%# ADEVICE "USB Audio Codec:6" "USB Audio Codec:5"
|
184 | 179 | %M%#
|
185 |
| -%M%# |
186 |
| -%M%# You can also use "-" or "stdin" to pipe stdout from |
187 |
| -%M%# some other application such as a software defined radio. |
188 |
| -%M%# "stdin" is not an audio device. Don't use this unless you |
189 |
| -%M%# understand what this means. Read the User Guide. |
190 |
| -%M%# You can also specify "UDP:" and an optional port for input. |
191 |
| -%M%# Something different must be specified for output. |
192 | 180 | %M%
|
193 |
| -%M%# ADEVICE UDP:7355 default |
194 |
| -%M%# |
195 |
| -%C% |
196 |
| -%C%# |
197 |
| -%C%# Number of audio channels for this souncard: 1 (mono) or 2 (stereo). |
198 |
| -%C%# 1 is the default so there is no need to specify it. |
199 |
| -%C%# |
200 |
| -%C% |
201 |
| -%C%#ACHANNELS 2 |
202 |
| -%C% |
203 |
| -%C% |
204 |
| -%C%############################################################# |
205 |
| -%C%# # |
206 |
| -%C%# SECOND AUDIO DEVICE PROPERTIES # |
207 |
| -%C%# (Channel 2 + 3 if in stereo) # |
208 |
| -%C%# # |
209 |
| -%C%############################################################# |
210 |
| -%C% |
211 |
| -%C%#ADEVICE1 ... |
212 |
| -%C% |
213 |
| -%C% |
214 |
| -%C%############################################################# |
215 |
| -%C%# # |
216 |
| -%C%# THIRD AUDIO DEVICE PROPERTIES # |
217 |
| -%C%# (Channel 4 + 5 if in stereo) # |
218 |
| -%C%# # |
219 |
| -%C%############################################################# |
220 |
| -%C% |
221 |
| -%C%#ADEVICE2 ... |
222 |
| -%C% |
| 181 | +%C%# Many more details and examples can be found in: |
| 182 | +%C%# https://github.com/wb2osz/direwolf-doc/blob/main/Radio-Interface-Guide.pdf |
223 | 183 | %C%
|
224 | 184 | %C%#############################################################
|
225 | 185 | %C%# #
|
|
230 | 190 | %C%CHANNEL 0
|
231 | 191 | %C%
|
232 | 192 | %C%#
|
233 |
| -%C%# The following MYCALL, MODEM, PTT, etc. configuration items |
234 |
| -%C%# apply to the most recent CHANNEL. |
235 |
| -%C%# |
236 |
| -%C% |
237 |
| -%C%# |
238 | 193 | %C%# Station identifier for this channel.
|
239 | 194 | %C%# Multiple channels can have the same or different names.
|
240 | 195 | %C%#
|
|
259 | 214 | %C%# In most cases you can just specify the speed. Examples:
|
260 | 215 | %C%#
|
261 | 216 | %C%
|
262 |
| -%C%MODEM 1200 |
| 217 | +%C%#MODEM 300 |
263 | 218 | %C%#MODEM 9600
|
264 | 219 | %C%
|
265 | 220 | %C%#
|
266 | 221 | %C%# Many options are available for great flexibility.
|
267 | 222 | %C%# See User Guide for details.
|
268 | 223 | %C%#
|
269 | 224 | %C%
|
270 |
| -%C%# |
271 |
| -%C%# Uncomment line below to enable the DTMF decoder for this channel. |
272 |
| -%C%# |
273 |
| -%C% |
274 |
| -%C%#DTMF |
275 |
| -%C% |
276 | 225 | %C%# Push to Talk (PTT) can be confusing because there are so many different cases.
|
277 | 226 | %C%# https://github.com/wb2osz/direwolf-doc/blob/main/Radio-Interface-Guide.pdf
|
278 | 227 | %C%# goes into detail about the various options.
|
|
291 | 240 | %W%
|
292 | 241 | %W%#PTT CM108
|
293 | 242 | %W%%C%#
|
294 |
| -%C%# The transmitter Push to Talk (PTT) control can be wired to a serial port |
295 |
| -%C%# with a suitable interface circuit. DON'T connect it directly! |
296 |
| -%C%# |
297 |
| -%C%# For the PTT command, specify the device and either RTS or DTR. |
298 |
| -%C%# RTS or DTR may be preceded by "-" to invert the signal. |
299 |
| -%C%# Both can be used for interfaces that want them driven with opposite polarity. |
300 |
| -%C%# |
301 |
| -%L%# COM1 can be used instead of /dev/ttyS0, COM2 for /dev/ttyS1, and so on. |
302 |
| -%L%# |
303 |
| -%C% |
304 |
| -%C%#PTT COM1 RTS |
305 |
| -%C%#PTT COM1 RTS -DTR |
306 |
| -%L%#PTT /dev/ttyUSB0 RTS |
307 |
| -%L%#PTT /dev/ttyUSB0 RTS -DTR |
308 |
| -%C% |
309 |
| -%L%# |
310 |
| -%L%# On Linux, you can also use general purpose I/O pins if |
311 |
| -%L%# your system is configured for user access to them. |
312 |
| -%L%# This would apply mostly to microprocessor boards, not a regular PC. |
313 |
| -%L%# See separate Raspberry Pi document for more details. |
314 |
| -%L%# The number may be preceded by "-" to invert the signal. |
315 |
| -%L%# |
316 |
| -%L% |
317 |
| -%L%#PTT GPIO 25 |
318 |
| -%L% |
319 |
| -%C%# The Data Carrier Detect (DCD) signal can be sent to most of the same places |
320 |
| -%C%# as the PTT signal. This could be used to light up an LED like a normal TNC. |
321 |
| -%C% |
322 |
| -%C%#DCD COM1 -DTR |
323 |
| -%L%#DCD GPIO 24 |
324 |
| -%C% |
325 |
| -%C% |
326 |
| -%C%############################################################# |
327 |
| -%C%# # |
328 |
| -%C%# CHANNEL 1 PROPERTIES # |
329 |
| -%C%# # |
330 |
| -%C%############################################################# |
331 | 243 | %C%
|
332 |
| -%C%#CHANNEL 1 |
333 |
| -%C% |
334 |
| -%C%# |
335 |
| -%C%# Specify MYCALL, MODEM, PTT, etc. configuration items for |
336 |
| -%C%# CHANNEL 1. Repeat for any other channels. |
337 |
| -%C% |
338 |
| -%C% |
339 |
| -%C%############################################################# |
340 |
| -%C%# # |
341 |
| -%C%# TEXT TO SPEECH COMMAND FILE # |
342 |
| -%C%# # |
343 |
| -%C%############################################################# |
344 |
| -%C% |
345 |
| -%W%#SPEECH dwespeak.bat |
346 |
| -%L%#SPEECH dwespeak.sh |
| 244 | +%C%# There are other possibilities such as serial port RTS, Raspberry Pi GPIO pins, |
| 245 | +%C%# and hamlib for CAT control. For more details see: |
| 246 | +%C%# https://github.com/wb2osz/direwolf-doc/blob/main/Radio-Interface-Guide.pdf |
347 | 247 | %C%
|
348 | 248 | %C%
|
349 | 249 | %C%#############################################################
|
|
361 | 261 | %W%# - KISS TNC via serial port
|
362 | 262 | %L%# - KISS TNC via pseudo terminal (-p command line option)
|
363 | 263 | %C%#
|
364 |
| -%C% |
365 |
| -%C%AGWPORT 8000 |
366 |
| -%C%KISSPORT 8001 |
367 |
| -%C% |
368 |
| -%W%# |
369 |
| -%W%# Some applications are designed to operate with only a physical |
370 |
| -%W%# TNC attached to a serial port. For these, we provide a virtual serial |
371 |
| -%W%# port that appears to be connected to a TNC. |
372 |
| -%W%# |
373 |
| -%W%# Take a look at the User Guide for instructions to set up |
374 |
| -%W%# two virtual serial ports named COM3 and COM4 connected by |
375 |
| -%W%# a null modem. |
376 |
| -%W%# |
377 |
| -%W%# Using the configuration described, Dire Wolf will connect to |
378 |
| -%W%# COM3 and the client application will use COM4. |
379 |
| -%W%# |
380 |
| -%W%# Uncomment following line to use this feature. |
381 |
| -%W% |
382 |
| -%W%#NULLMODEM COM3 |
383 |
| -%W% |
384 |
| -%W% |
385 |
| -%C%# |
386 |
| -%C%# It is sometimes possible to recover frames with a bad FCS. |
387 |
| -%C%# This is not a global setting. |
388 |
| -%C%# It applies only the the most recent CHANNEL specified. |
389 |
| -%C%# |
390 |
| -%C%# 0 - Don't try to repair. (default) |
391 |
| -%C%# 1 - Attempt to fix single bit error. |
392 |
| -%C%# |
393 |
| -%C% |
394 |
| -%C%#FIX_BITS 0 |
395 |
| -%C% |
396 | 264 | %C%#
|
397 | 265 | %C%#############################################################
|
398 | 266 | %C%# #
|
|
410 | 278 | %C%# Each has a series of keywords and values for options.
|
411 | 279 | %C%# See User Guide for details.
|
412 | 280 | %C%#
|
413 |
| -%C%# Example: |
414 |
| -%C%# |
415 |
| -%C%# This results in a broadcast once every 10 minutes. |
416 |
| -%C%# Every half hour, it can travel via one digipeater hop. |
417 |
| -%C%# The others are kept local. |
| 281 | +%C%# Example: PLEASE change the latitude and longitude. |
418 | 282 | %C%#
|
419 | 283 | %C%
|
420 |
| -%C%#PBEACON delay=1 every=30 overlay=S symbol="digi" lat=42^37.14N long=071^20.83W power=50 height=20 gain=4 comment="Chelmsford MA" via=WIDE1-1 |
421 |
| -%C%#PBEACON delay=11 every=30 overlay=S symbol="digi" lat=42^37.14N long=071^20.83W power=50 height=20 gain=4 comment="Chelmsford MA" |
422 |
| -%C%#PBEACON delay=21 every=30 overlay=S symbol="digi" lat=42^37.14N long=071^20.83W power=50 height=20 gain=4 comment="Chelmsford MA" |
| 284 | +%C%#PBEACON overlay=S symbol="digi" lat=42^37.14N long=071^20.83W power=50 height=20 gain=4 comment="Chelmsford MA" |
423 | 285 | %C%
|
424 | 286 | %C%#
|
425 | 287 | %C%# Did you know that APRS comments and messages can contain UTF-8 characters, not only plain ASCII?
|
|
428 | 290 | %C%#PBEACON delay=11 every=30 overlay=S symbol="digi" lat=42^37.14N long=071^20.83W comment=" Did you know that APRS comments and messages can contain UTF-8 characters? \xce\xa1\xce\xb1\xce\xb4\xce\xb9\xce\xbf\xce\xb5\xcf\x81\xce\xb1\xcf\x83\xce\xb9\xcf\x84\xce\xb5\xcf\x87\xce\xbd\xce\xb9\xcf\x83\xce\xbc\xcf\x8c\xcf\x82"
|
429 | 291 | %C%#PBEACON delay=21 every=30 overlay=S symbol="digi" lat=42^37.14N long=071^20.83W comment=" Did you know that APRS comments and messages can contain UTF-8 characters? \xe3\x82\xa2\xe3\x83\x9e\xe3\x83\x81\xe3\x83\xa5\xe3\x82\xa2\xe7\x84\xa1\xe7\xb7\x9a"
|
430 | 292 | %C%#
|
431 |
| -%C%# With UTM coordinates instead of latitude and longitude. |
432 |
| -%C% |
433 |
| -%C%#PBEACON delay=1 every=10 overlay=S symbol="digi" zone=19T easting=307477 northing=4720178 |
434 |
| -%C% |
435 |
| -%C% |
436 |
| -%C%# |
437 |
| -%C%# When the destination field is set to "SPEECH" the information part is |
438 |
| -%C%# converted to speech rather than transmitted as a data frame. |
439 |
| -%C%# |
440 |
| -%C% |
441 |
| -%C%#CBEACON dest="SPEECH" info="Club meeting tonight at 7 pm." |
442 |
| -%C% |
443 |
| -%C%# Similar for Morse code. If SSID is specified, it is multiplied |
444 |
| -%C%# by 2 to get speed in words per minute (WPM). |
445 |
| -%C% |
446 |
| -%C%#CBEACON dest="MORSE-6" info="de MYCALL" |
447 |
| -%C% |
448 |
| -%C% |
449 |
| -%C%# |
450 |
| -%C%# Modify for your particular situation before removing |
451 |
| -%C%# the # comment character from the beginning of appropriate lines above. |
452 |
| -%C%# |
453 |
| -%C% |
454 | 293 | %C%
|
455 | 294 | %C%#############################################################
|
456 | 295 | %C%# #
|
|
497 | 336 | %C%# That's all you need for a receive only IGate which relays
|
498 | 337 | %C%# messages from the local radio channel to the global servers.
|
499 | 338 | %C%
|
500 |
| -%C%# Some might want to send an IGate client position directly to a server |
501 |
| -%C%# without sending it over the air and relying on someone else to |
502 |
| -%C%# forward it to an IGate server. This is done by using sendto=IG rather |
503 |
| -%C%# than a radio channel number. Overlay R for receive only, T for two way. |
504 |
| -%C%# There is no need to send it as often as you would over the radio. |
505 |
| -%C% |
506 |
| -%C%#PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=R lat=42^37.14N long=071^20.83W |
507 |
| -%C%#PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=T lat=42^37.14N long=071^20.83W |
508 |
| -%C% |
509 |
| -%C% |
510 |
| -%C%# To relay messages from the Internet to radio, you need to add |
| 339 | +%C%# To relay APRS "messages" from the Internet to radio, you need to add |
511 | 340 | %C%# one more option with the transmit channel number and a VIA path.
|
512 | 341 | %C%
|
513 | 342 | %C%#IGTXVIA 0 WIDE1-1,WIDE2-1
|
514 | 343 | %C%
|
515 |
| -%C% |
516 |
| -%C%# Finally, we don't want to flood the radio channel. |
517 |
| -%C%# The IGate function will limit the number of packets transmitted |
518 |
| -%C%# during 1 minute and 5 minute intervals. If a limit would |
519 |
| -%C%# be exceeded, the packet is dropped and message is displayed in red. |
520 |
| -%C%# This might be low for APRS Thursday when there is abnormally high activity. |
521 |
| -%C% |
522 |
| -%C%IGTXLIMIT 6 10 |
| 344 | +%C%# For more information see Successful-IGate-Operation.pdf. |
523 | 345 | %C%
|
524 | 346 | %C%
|
525 | 347 | %C%#############################################################
|
|
0 commit comments