开云体育

Hi, It is good that you realize that the audio volume settings (especially the transmit audio volume) are important for successful packet operation. However you are mistaken when you assume that

I have a digipeater and igate at home, using a Retevis RT-95 (same radio as the Anytone AT-778UV) with its mic jack and external speaker jack connected to a Digirig Mobile which is connected to a

Hmm, already running 1.7 release on my tx-igate.

A 1.7 development version is in use.? I'll test on 1.7 Release to see if there's any change.

The location of objects created by a station is presumably erroneously used to update the location in the heard table for the station, as seen when using the debug option -d m This causes an incorrect

Hello Cassie, Awesome. Good work. Sure.. that will work though I would now recommend you learn a bit about how APRS works, how the different "WIDE" constructs work (WIDE1-1, vs WIDE2-1), etc

Alright everyone. The initial setup is done I think. Both rig setups are able to receive packets off 144.39 and are able to do a transmit test with -x a. Hooray! Huge thank you for the support from

Hi Cass You will strike different opinions on what sound system to use, basic ALSA, pulseaudio and pipewire seem to be the main contenders. If the PC's are dedicated to just running direwolf or rather

David- I can honestly say I have no idea where the binary came from. But, I agree that I should be able to recompile it which I will start doing this week. I have a feeling a lot of things will be

I haven't chipped in as I don't have anything to contribute, having only used Direwolf along with a Digirig Mobile sound card to make a run-of-the-mill APRS digipeater and igate, but I before this

Excellent Cassie! Might be good to check that your distro isn't running pulseaudio. The "could not open plughw" kind of screams that. Try ps ax| grep pulse And if it comes back with the any pulseaudio

Hello Cres, Great to hear you're making progress! The error is just like it reads.. your version of Direwolf wasn't build with hamlib support. Where did you get this binary? Recompiling isn't too hard

The partial reset worked! I can't even begin to express how awesome it is to see something other than an error come out of this thing. Now onto the next event of direwolf. So, In trying to keep up

I should ask, does dmesg display the USB ports and Burr Brown sound card when the rig is hot plugged? if so that kind of (now) suggests there is a rig setting awry. It might also be worth confirming

Sorry, I did also check rigctl -l | grep 9100 and it is still the 3068 -Cass

Hello again, So following: "rigctld -m 3068 -v -r /dev/ttyUSB0 -s 19200 -c 0x7c in one shell window, and rigctl -m 2" and then trying a f command, yields the same sad communication timed out message.

Sorry I pasted my own USB device names Substitute /dev/ttyUSB0 for /dev/icom9100a Bob

Hi Cassie A swag of notes/ideas. Yes I agree something has gone wrong. Note there is a difference between rigctld and rigctl. For testing you would start; rigctld -m 3068 -v -r /dev/icom9100a -s 19200

Hi Rob/David Actually for the 9100 it always presents them in the right sequence. ie the first is always the C-IV port. Other USB devices may of course get in the way of numbering if they are

Of course Rob is right here.. though there is a simpler way if the cabling on the host never changes: /dev/serial/by-id . For example, I can see the various serial ports on my host: ls -la