开云体育

You would NOT be correct in that assumption.UP means? request an increase the VFO frequency (Up button on the Mic) and Down means a decrease the VFO frequency (Down button on the Mic). The DR-140

thats the trouble? ?it doesnt transmit anything unless it hears it on RF toggling on some debug flags this is W9CVA-13? coming over the network [ig>tx]

I’m making an APRS beaconer with an Alinco DR-140 radio, a tone-key radio-to-soundcard interface (page 6 of http://wa8lmf.net/miscinfo/Tone-Keyed_Soundcard_Interface.PDF ) and a Debian Bullseye

Hello k9wkj, Ok Ok That is way too broad. You should not be transmitting over RF all traffic within a 80km diameter. --David KI6ZHD

David, here is the tail of /var/tmp/dw-start.log Thu Mar 16 12:36:52 PM CDT 2023 Direwolf in GUI mode start up DISPLAY=:0 ----------------------- Direwolf in CLI mode start up No Sockets found in

good day David will address in order 1.? ? ?Ok.. just to confirm, this setup you're using is NOT using an SDR for RX correct? correct it is a Midland LMR rig with a RA interface on a OrangePi

David, Thanks for your reply. The shell script I refer to is one I wrote that simply runs: bash -c 'rtl_fm -f 144.39M - | direwolf -c igate.conf -r 24000 -D 1 -' & And that is the corrected version of

Hello k9wkj, Ok.. just to confirm, this setup you're using is NOT using an SDR for RX correct? When you say "the server", do you mean APRS-IS? What traffic are you expecting to be transmitted from

Hello K9WKJ, Ok.. that's good. If you look in the dw-start.sh script, all additional details go to the LOG file set as /var/tmp/dw-start.log . Do you see any errors in there? --David

unrelated to my other response today our digi works just fine with traffic it receives over RF even handles TT traffic both ways it repeats the traffic on RF and sends it out to the server but it does

having the same trouble with a dongle not behaving in the script it will run for forever with this rtl_fm -f 144.39M -g 30 -p 75 -o 4 - | direwolf -c sdr.conf -n 1 -a 30 -T %H:%M:%S -r 24000 -D 1 -b

Hello Paul, When you say you can run things ok from a command prompt, can you say explicitly what command you're running? What shell script are you running? Is this something you wrote or are you

Sorry I'm late in replying but to underscore Andrew's point, this is what I learned related to position ambiguity and how it is applied in direwolf from this thread in the user guide under section

Thanks for the reply, Gil! That is the writeup I found to be the "nicest." That implementation only launches direwolf, NOT rtl_fm piping output to direwolf. My limited Linux command line experience is

Hello Ian, What I do is the following (assuming you already did your original "git clone"): cd ~/direwolf rm -Rf build git checkout dev git pull mkdir build cd build cmake .. make --David KI6ZHD

Hi Paul, I followed these instructions: https://www.f4fxl.org/start-direwolf-at-boot-the-systemd-way/ I had no problems and everything fired up fine. Accessing Direwolf after that requires using tmux

What's the preferred method of updating Direwolf from the git source? Currently I just blow away my existing source directory with rm -rf ~/direwolf and then just reinstall with git clone

Hi Kevin, I don't see how 'listening in' would make you a bad guy, regardless of mode and frequency. Just pay attention to local/regional band plans before transmitting. In most places it is frowned

It's not that it's "non-APRS" frequencies. It's just the band plan where different types of communications modes are commonly used to avoid interference by incompatible modes. By law and regulation,

Andrew, KA2DDO THANK YOU! You've cleared up something I wasn't understanding. Using APRS protocol system on non-APRS frequencies. I had (wrongfully, apparently) assumed that using that protocol system