开云体育

I have a remote Mountain top that has a part 15 link providing internet and have setup a 25W mobile on 144.39 with a CM108 interface running Direwolf on a pi on site (W7SID-10)... I seem to have it running but, am pretty blurry as to the proper setup and would appreciate some direction to a cookbook to better understand what I need to do to get it optimized. Add YAAC etc. ?? Thanks! KL7UT, Ray

Hello. I’ve recently started to learn about and experiment with Direwolf. I have a Pi Zero 2w running a server/headless installation, an AIOC cable, USB GPS puck, and a Quansheng UV-K5 HT to make up the rig. It’s in an ammo box, with a larger phone backup battery. As long as I’m using an external/remote antenna, I don’t seem to have RF issues. Just using the HT with a rubber duck causes the AIOC to be wiped out, and the sound card is disabled. Occasionally, it will take off and beacon when it’s booted, but usually I have to restart Direwolf manually over SSH. As long as I have a terminal connected, it operates fine. If I disconnect the SSH session and just let it run, it gets quiet and seems to quit. I can log back in and start over, and repeat the process. It’s usually connected to my phone’s Wi-Fi hotspot when I’m traveling with it. This morning on a 30 mile trip, it stalled before I left town. This evening, it ran beautifully, as I kept a SSH client connected. My TBEACON string is basic minimum/maximum speed smart beaconing. It’s like it’s not continuing to run after I’ve logged off from the SSH session. I’ve found logs in /var/log/direwolf/, but that’s just bland logs of APRS traffic, rather than software failures, etc. When I log into SSH, I get a message that Direwolf is running, and I have to send a Ctl-C break to get a prompt and start over. I’d like to be able to boot the Pi, and just let it do its thing in the trunk, but for some reason it stops running. Any help appreciated. Thanks and 73, Adam, W8FLH Greenville, Ohio

I just noticed that the default dw-start.sh includes "screen", so the previous may or may not apply. There are also some distros that kill user processes on logout. It's part of systemd/logind Hope this helps... ======== Hi Adam Generally when you run a SSH remote terminal session the process will be stopped after disconnection. It's called "hup" and disabling is "nohup". There are a few ways around it, but these is about the simplest; Using disown and backgrounding ctrl-z within the terminal window bg (moves process to background) disown -h (keeps running on terminal close) Also possible to precede the process command with nohup". eg; nohup dwstart & This also saves the running session to a file, the default being nohup.out in the home directory Use "screen" ssh into your remote box and type screen, then start direwolf normally. Ctrl+A, then Ctrl+D. This will detach your screen session. You can now log out of the remote box. If you want to reconnect, ssh in again and type screen -r Lots of help in manpages etc over this Cheers Bob VK2YQA On 5/8/24 12:57, Adam Liette wrote: > Hello. I’ve recently started to learn about and experiment with > Direwolf. I have a Pi Zero 2w running a server/headless installation, > an AIOC cable, USB GPS puck, and a Quansheng UV-K5 HT to make up the > rig. It’s in an ammo box, with a larger phone backup battery. As long > as I’m using an external/remote antenna, I don’t seem to have RF > issues. Just using the HT with a rubber duck causes the AIOC to be > wiped out, and the sound card is disabled. > > Occasionally, it will take off and beacon when it’s booted, but > usually I have to restart Direwolf manually over SSH. As long as I > have a terminal connected, it operates fine. If I disconnect the SSH > session and just let it run, it gets quiet and seems to quit. I can > log back in and start over, and repeat the process. It’s usually > connected to my phone’s Wi-Fi hotspot when I’m traveling with it. > This morning on a 30 mile trip, it stalled before I left town. This > evening, it ran beautifully, as I kept a SSH client connected. My > TBEACON string is basic minimum/maximum speed smart beaconing. > > It’s like it’s not continuing to run after I’ve logged off from the > SSH session. I’ve found logs in /var/log/direwolf/, but that’s just > bland logs of APRS traffic, rather than software failures, etc. When > I log into SSH, I get a message that Direwolf is running, and I have > to send a Ctl-C break to get a prompt and start over. I’d like to be > able to boot the Pi, and just let it do its thing in the trunk, but > for some reason it stops running. >

The question are... Is necesary every run in the lastest verions the lines of warning that the ham know perfectly? Line 192: Warning - IGFILTER is a rarely needed expert level feature. If you don't have a special situation and a good understanding of how this works, you probably should not be messing with it. The default behavior is appropriate for most situations. Please read "Successful-APRS-IGate-Operation.pdf". Config file: FILTER IG ... on line 198. Warning! Don't mess with IS>RF filtering unless you are an expert and have an unusual situation. Warning! The default is fine for nearly all situations. Warning! Be sure to read carefully and understand "Successful-APRS-Gateway-Operation.pdf" . Warning! If you insist, be sure to add " | i/180 " so you don't break messaging. Config file: FILTER ... IG ... on line 200. Warning! Don't mess with RF>IS filtering unless you are an expert and have an unusual situation. Warning! Expected behavior is for everything to go from RF to IS. Warning! The default is fine for nearly all situations. Warning! Be sure to read carefully and understand "Successful-APRS-Gateway-Operation.pdf" . Available audio input devices for receive (*=selected): etc etc etc... tiempo perdido. innecesary lines of code and shock when see the red lines. excesive maniac programation. The solution, compile whitout this messages... but the creator need a mental reflexion.

Good evening, I would like to use FlexRadio 6400 with nDAX software (https://github.com/kc2g-flex-tools/nDAX) and DIREWOLF. nDAX creates 2 pulseaudio devices, sink(RX) and source(TX), and they works pretty well. How to use these pulseaudio devices in direwolf? here the result of `pacmd list-sinks` ``` index: 3 name: <flex.sliceA.tx> driver: <module-pipe-sink.c> flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: IDLE suspend cause: (none) priority: 0 volume: mono: 65536 / 100% / 0.00 dB balance 0.00 base volume: 65536 / 100% / 0.00 dB volume steps: 65537 muted: no current latency: 59.39 ms max request: 4 KiB max rewind: 0 KiB monitor source: 6 sample spec: s16be 1ch 24000Hz channel map: mono Mono used by: 0 linked by: 0 configured latency: 85.33 ms; range is 0.50 .. 85.33 ms module: 25 properties: device.string = "/tmp/nDAX-flex.sliceA.tx.pipe" device.description = "Flex slice A TX" device.icon_name = "radio" nDAX.pid = "19101" ``` here the result of `pacmd list-sources` ``` index: 5 name: <flex.sliceA.rx> driver: <module-pipe-source.c> flags: DECIBEL_VOLUME LATENCY state: IDLE suspend cause: (none) priority: 0 volume: mono: 65536 / 100% / 0.00 dB balance 0.00 base volume: 65536 / 100% / 0.00 dB volume steps: 65537 muted: no current latency: 1365.33 ms max rewind: 0 KiB sample spec: s16be 1ch 24000Hz channel map: mono Mono used by: 0 linked by: 0 fixed latency: 85.33 ms module: 24 properties: device.string = "/tmp/nDAX-flex.sliceA.rx.pipe" device.description = "Flex slice A RX" device.buffering.buffer_size = "4800" device.icon_name = "radio" nDAX.pid = "19101" ```

So i was looking at cat control for my usdx radio and i found this really set up. https://yd0nxx.wordpress.com/2022/08/16/cat-cable-for-usdx/ Would something like this work for an HT ? OF course you if you have a baofeng type, you would use the 2.5 / 3.5 head and then connect the bare wires to a FTDI / USB-TTL connector. can this also be used for our use cases? if not, why not? many thanks

Good afternoon. I finally took some time to cross an item off my ham list: build an iGate/Digipeater. I am using a Yaesu FT2900 for the radio I have a raspberry pi 3+ running bookworm (32-bit) I have a digirig mobile w/cables for interconnection I got the pi configured and direwolf installed. I followed the tutorial from Darren, N4VFR and am mostly working! I have an iGate connected, K0ACP-10 I have the Digipeater function working with the radio, K0ACP-10, that shows up on both my Kenwood TH-D74 and Kenwood D710. However, the digpeater seems deaf, no received packets. Any ideas? 73 es God Bless, Art / K0ACP

I'm running Linpac but never get anything when I use the ":mheard" command ...any idea how to fix this?

I want to study some stuff about aprs-si connections and temporarily build direwolf so I can set breakpoints and look at some variables. I'm using debian (not on a Raspberry pi). How do you build it for this? When I'm done looking at some things in vscode I'll re-install it in release mode. When I re-install it should I just let the new 'make install' overwrite the debug version? thanks, Bob

I have a config file line that reads "PTT RIG 1020 /dev/ttyUSB0 RTS 4800" but when direwolf encounters this line it responds "An optional number is required here for CAT serial port speed" I'm certain it's reading the correct config file. Can anyone suggest a reason it might complain about my specified serial port speed? 73, Jim KX0U

Hi All, I am currently writing some tutorials for our club members and BTW refreeshing my Direwolf knowledge. While doing so I wanted to write about the MODEM option in teh config file. To my surprise, the E option is no longer mentionned in the manual for 1200bps, only A and D. Yet the latest dev branch does not complain about my MODEM 1200 E+ configuration. I wanted to learn more about it and looked deeper into the source code and found out that it is actually legit to configure something like MODEM 1200 ADE+ When starting Direwolf it give feedback on which decoder is what I am testing it on our club moutain top digipeater, and it s decoding very well. Or this one! Now the questions Are their any difference between A and E or has E just been renamed to A? What does actually D do? How is it different from A and E ? Given I have enough CPU power to run all three of them, is there an actual benefit from it? I have the feeling that some stations are better decoded, but could not prove it yet. 73 Geoffrey F4FXL / KC3FRA -- Geoffrey F4FXL / KC3FRA My Direwolf stuff : https://www.f4fxl.org/tag/direwolf/

So, before I bothered to find out what the repercussions of doing a update/upgrade, I went ahead and did it. Now I see that the OS upgrade to Bookworm has thrashed the operation of the IO on the RPi. The general consensus for repair appears to be an upgrade to 1.8 Direwolf, and a re-compile. As there seems to be no tutorial, and I am not a programmer, I am effectively no longer providing the only area two way APRS internet gateway access. At this point I am not willing to continue this fight, so I am QRT, at least until a tutorial appears, and then I will have to see if I want to spend a lot of time going through all the pain and suffering of a rebuild. Thanks to everyone who answered my questions. 73 to all. ve7bul, QRT.

I have been trying to set up Dyer Wolf on a raspberry pie for two weeks now and I have watched every YouTube video googled everything and I just don’t understand it and it’s a very frustrating. I’m not sure where to start. I don’t do code on computers, so I’m very confused on how to configure this and make it run on a raspberry pie. Please, please, please help me. I want to Set it up for aprs with digipeter and igate. I believe I have all the right cables. I just need to get this raspberrypie working. This is my first raspberrypie Like I said, very new beginner.

Hi all, I am currently on a road trip through southwest US. Family and friends us APRS to look where I am. Lately they told me : your track has some weird jumps and cros crosses. I analyzed my data and came out to the conclusion that all of these issues are caused by sur based igates running outdated direwolf. The symptoms are outdated packets are sent to APRS-IS sometimes hours after they were originally transmitted. I had the case were some of my packets were resent to APRS-IS 3 hours after their original transmission. -- Geoffrey F4FXL / KC3FRA My Direwolf stuff : https://www.f4fxl.org/tag/direwolf/

Good afternoon, I encountered an issue using UDP device on direwolf Scenario Audio sender: Windows 10 host with ffmpeg Receiver: Ubuntu Desktop 22.04 with direwolf last release build from github today On Windows host (audio sender) ffmpeg -f dshow -i audio="Line 1 (Virtual Audio Cable)" -c 1 -acodec pcm_s16le -b:a 48000 -f mpegts udp://192.168.56.1:12000 I tried playing a test.wav generated with gen_packet and tested with atest. On Ubuntu If I try to listen the stream with VLC I can hear it loud and clear, but with direwolf with this command direwolf -n 1 -a 10 -r 44100 udp:12000 Output: Dire Wolf version 1.7 Includes optional support for: hamlib cm108-ptt Reading config file direwolf.conf Audio input device for receive: udp:12000 (channel 0) Audio out device for transmit: null (channel 0) Channel 0: Demodulator + option can't be combined with multiple frequencies. Channel 0: 300 baud, AFSK 1600 & 1800 Hz, A+, 44100 sample rate / 4. Note: PTT not configured for channel 0. (Ignore this if using VOX.) Ready to accept AGW client application 0 on port 8000 ... Ready to accept KISS TCP client application 0 on port 8001 ... ADEVICE0: Sample rate approx. 10.0 k, 0 errors, receive audio level CH0 195 ADEVICE0: Sample rate approx. 9.8 k, 0 errors, receive audio level CH0 194 ADEVICE0: Sample rate approx. 10.0 k, 0 errors, receive audio level CH0 195 ADEVICE0: Sample rate approx. 10.0 k, 0 errors, receive audio level CH0 194 ADEVICE0: Sample rate approx. 10.0 k, 0 errors, receive audio level CH0 194 But...no decoding! direwolf.conf ADEVICE0 udp:12000 null ARATE 44100 MYCALL TEST MODEM 300 1600:1800 7@30 /4

I don't know whether it's common in groups.io to introduce yourself before posting for help, but it is in most online support forums so here goes: I'm Jay, DW7GDL, an ex-pat living in Cebu, Philippines. I got my first ever ham radio license last August and have recently become interested in APRS as an additional means of communication. As we have no digipeaters or igates in this part of the country I took a spare radio, a Retevis RT95, a Raspberry Pi 3B+ and a Digirig Mobile with appropriate cables, installed direwolf on the Pi, configured it as a systemd service, and configured it as an igate with pbeacons to announce its presence both on RF and to APRS-IS, obeacons to announce my club's 2m and 70cm repeaters to any visiting hams who use APRS, and a cbeacon to send my callsign in CW every 10 minutes to meet legal station ID requirements. I didn't bother with enabling digipeat as there are no other digipeaters to send packets to or receive them from. There are only a few pockets of APRS activity in the country, mainly in the Manila area, in Central Luzon and in Negros Occidental province east of me, with a wee bit in parts of Mindanao Island also (the big island in the south of the country.) Having experienced supertyphoon Rai, known locally as Odette, in December 2021 and having no means of communications (or running water or electricity) for weeks afterward I've become somewhat of a prepper and am interested in promoting APRS as an additional means of emergency communications when the cell phone system is down due to lack of power. Most Filipinos prefer to send SMS text messages vs. making phone calls , plus there are additional used for APRS: WX beacons, obeacons advising visiting hams new to the area of local repeaters, locations of i.e. hospitals, ATMs, places to eat, hotels, etc, beacons announcing club meetings or special events so they could drop in and meet some local hams, and so on to give them a "situational awareness" of things, events and places in the local area via their radios. I figured if I set up at least an igate that also sent some of these beacons I might be able to get APRS going in this part of the country too. 73, mabuhay!