开云体育

Date

Re: Getting closer but no audio out

 

Please tell us more about the exact type of connection between the computer and radio.
The IC-7100 User Guide? ? , page 18-2 shows 3 possible connections for transmit audio:? DATA2, ACC, or MIC.
The following pages describe some additional considerations.

73,
John WB2OSZ


Re: Getting closer but no audio out

 

开云体育


Hello,

when direwolf receives APRS, it keys the radio. I monitor and nothing goes out on the air (the radio TX silence)


Try running Direwolf in calibration mode from the command line to get a steady stream of tones.? Once that's running, change your Windows mixer "playback" levels.? If that's not working, try explicitly configuring the sound devices using numbers on the ADVICE line.? See the Direwolf UserGuide Section 9.1.2 for Windows for more details but consider the "USB" example as a form of a string match of what Direwolf shows upon startup.? You need to make sure you select the correct audio input and audio output interfaces..

--David
KI6ZHD


Getting closer but no audio out

 

Using IC-9100, usb audio
windows 10
CAT7200 is connected to virtual series port and radio and test does PTT

when direwolf receives APRS, it keys the radio. I monitor and nothing goes out on the air (the radio TX silence)?


i have ?made sure the usb correct audio devices are selected for receive and transmit and direwolf verifies this at startup. My settings are

ADEVICE USB USB

PTT COM RTS


anyone have any idea what may be going on ?


Re: digipeater settings for IC-9100 in Windows

 

Thank you. I’ll try the second approach as I have only a few days before needing this. Appreciate your kindness in pointing me back to older threads on this.?

-Kevin (KK4YEL)?


Re: digipeater settings for IC-9100 in Windows

 

开云体育


So, I am able to have direwolf RX audio from my IC-9100 via the USB cable and act as a I-Gate. The next thing I wanted to do was digipeat.
I read the user guide, but I am confused. it seems Direwolf only supports hamlib on linux.

That's correct.? The pre-built DIrewolf v1.6 or 1.7A (beta) binaries for Windows does NOT have HAMlib support included at this time.? Btw, this has been brought up before and you can see other queries about this in the Groups.IO archives:? /g/direwolf/search?p=recentpostdate%2Fsticky%2C%2C%2C20%2C0%2C0%2C0&q=IC-9100

If you want to compile your own version of Direwolf to natively include Hamlib support, you can read up on that here:

?? Email thread: ? ? ? ? ? ? ? ? ? /g/direwolf/topic/78139539#4905
?? Direwolf Github issue tracker:


If you don't want to compile things, you can use a program like CAT7200 to do bridge or "PTT translation".? With this CAT7200 software running, you configure Direwolf to assert PTT on a virtual serial COM port that this CAT7200 software creates.? When direwolf tries to assert PTT via a simple RTS signal on the virtual serial port, the CAT7200 software will translate that request and create the required CI-V PTT command to the IC-9100 via it's CI-V-only enabled serial port:

??

--David
KI6ZHD


digipeater settings for IC-9100 in Windows

 

So, I am able to have direwolf RX audio from my IC-9100 via the USB cable and act as a I-Gate. The next thing I wanted to do was digipeat.
I read the user guide, but I am confused. it seems Direwolf only supports hamlib on linux.?
I see the comm port COM 7 is the radio, but can't get the PTT to do anything in direwolf. I thought it would be something like
PTT RIG 3068 COM7

is there anyone using an ICOM in windows with Direwolf acting as a digipeater than can help?
thanks
-Kevin (KK4YEL)


Re: strange CMake warnings building direwolf

 

On Sat, Dec 3, 2022 at 02:17 PM, David Ranch wrote:
change to Direwolf's src/dwgpsd.c
Dear David,

thanks for the fast reply and assistance.
Your tip works for compilation with make, but just to inform you:? it is located in line 68 as mentioned by the error messages:

66: // 3.24??? ??? ??? ??? 14??? ??? ??? Not tested yet.
67:
68: #if GPSD_API_MAJOR_VERSION < 5 || GPSD_API_MAJOR_VERSION > 14
69: #error libgps API version might be incompatible.
70: #endif

The needed change was at the end of line 68: number 12 to 14
opensuse thumbleweed installs at this time? libgps 3.24-14

I had no tested the executable with gps until now, but can do it later(days, weeks)

Thanks for now

Michael, dk5hh


Re: strange CMake warnings building direwolf

 

开云体育


Hello Michael,

Most likely your OpenSuse distro has a newer version of gpsd installed than what Direwolf has been tested with.? What version of gpsd do you have installed?? You can consider making a small change to Direwolf's src/dwgpsd.c file to allow the newer gpsd API version to get it to compile.? See line 540 to see how the code checks for both the minimum but also MAXIMUM supported version.? If you then get things to compile and run, it would be appreciated if you would reply back to the list to let us know if this newer version works or not.? If it does, we can update the Direwolf code to officially support this new version of gpsd.

--David
KI6ZHD




On 12/03/2022 02:05 PM, hartje wrote:

Dear list,

on an opensuse thumbleweed I try to compile the newest direwolf
after? git clone and git checkout dev or master I got the same compile? (make ) error:

During make
...
[ 37%]
Building C object src/CMakeFiles/direwolf.dir/dwgpsd.c.o
/home/devel/ax25/DW-17/src/dwgpsd.c:69:2: error: #error lib
gps API version might be incompatible.
??69 | #error libgps API version might be incompatible.
?????| ?^~~~~
make[2]: *** [src/CMakeFiles/direwolf.dir/build.make:1014: src/CMakeFiles/direwo
lf.dir/dwgpsd.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:538: src/CMakeFiles/direwolf.dir/all] Error 2
make: *** [Makefile:156: all] Error 2

"cmake .. " says ok but missing strlcpy and strlcat -- see below:
-- The C compiler identification is GNU 12.2.1
-- The CXX compiler identification is GNU 12.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Git: /bin/git (found version "2.38.1") ?
-- Dire Wolf Version: 1.7.0-3973627
-- Build type set to: Release
CMake system: Linux
-- Target architecture: x86_64
-- Use SSE SIMD instructions
-- Looking for strlcpy
-- Looking for strlcpy - not found
-- Looking for strlcat
-- Looking for strlcat - not found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE ??
-- Checking for module 'libgps'
-- ??Found libgps, version 3.24
-- Found GPSD: /usr/lib64/libgps.so
-- Checking for module 'hamlib'
-- ??Found hamlib, version 4.6~git
-- Found hamlib: /usr/lib64/libhamlib.so ??
-- Found ALSA: /usr/lib64/libasound.so (found version "1.2.8") ?
-- Checking for module 'libudev'
-- ??Found libudev, version 252
-- Found udev: /usr/lib64/libudev.so ??
-- Could NOT find Avahi (missing: AVAHI_COMMON_FOUND AVAHI_CLIENT_FOUND)

how should I adopt or edit the libgps missmatch?

is there any workaround?

Any helpful hint is welcome to get it flying....

Thanks in advance
Michael



Re: strange CMake warnings building direwolf

 

Dear list,

on an opensuse thumbleweed I try to compile the newest direwolf
after? git clone and git checkout dev or master I got the same compile? (make ) error:

During make
...
[ 37%]
Building C object src/CMakeFiles/direwolf.dir/dwgpsd.c.o
/home/devel/ax25/DW-17/src/dwgpsd.c:69:2: error: #error lib
gps API version might be incompatible.
??69 | #error libgps API version might be incompatible.
?????| ?^~~~~
make[2]: *** [src/CMakeFiles/direwolf.dir/build.make:1014: src/CMakeFiles/direwo
lf.dir/dwgpsd.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:538: src/CMakeFiles/direwolf.dir/all] Error 2
make: *** [Makefile:156: all] Error 2

"cmake .. " says ok but missing strlcpy and strlcat -- see below:
-- The C compiler identification is GNU 12.2.1
-- The CXX compiler identification is GNU 12.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Git: /bin/git (found version "2.38.1") ?
-- Dire Wolf Version: 1.7.0-3973627
-- Build type set to: Release
CMake system: Linux
-- Target architecture: x86_64
-- Use SSE SIMD instructions
-- Looking for strlcpy
-- Looking for strlcpy - not found
-- Looking for strlcat
-- Looking for strlcat - not found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE ??
-- Checking for module 'libgps'
-- ??Found libgps, version 3.24
-- Found GPSD: /usr/lib64/libgps.so
-- Checking for module 'hamlib'
-- ??Found hamlib, version 4.6~git
-- Found hamlib: /usr/lib64/libhamlib.so ??
-- Found ALSA: /usr/lib64/libasound.so (found version "1.2.8") ?
-- Checking for module 'libudev'
-- ??Found libudev, version 252
-- Found udev: /usr/lib64/libudev.so ??
-- Could NOT find Avahi (missing: AVAHI_COMMON_FOUND AVAHI_CLIENT_FOUND)

how should I adopt or edit the libgps missmatch?

is there any workaround?

Any helpful hint is welcome to get it flying....

Thanks in advance
Michael


Re: Third Party not inspected by filters

 

Hi Craig,

Actually Direwolf is doing gating of messages to RF by the book.

The issue I have here is some fellows gating useless stuff like voice repeater objects with 2 hops or more. I do not want my 1200m HAAT Digipeater to digipeat that crap.


I dug more into it today,? it seems only the type t and budfilter filter were affected. So I reverted some of my work and fixed and I am trying another approach.

To be continued...


Re: Log directory option not working?

 

开云体育

Yeah, thanks for that info. ?Sure. I wouldn’t mind doing the same thing with my igate (posting to html heard stations).


13 Pro Max

On Dec 2, 2022, at 11:24 PM, ksmolkowski@... wrote:

?I believe I have it figured out.? ? The "stock" logging option is only for APRS packets.? ?I wanted to log all "heard" packets so I can display them on a simple web page so users of my gateway can see if they are being received or not.? ? I know I could parse this info from the stdout, but that seems awkward.? ?Instead I added a bit of code and compiled my own version that optionally creates a "heard" log file like so:

rmsgwpi:/var/log/radio# cat 2022-12-03.log
2022-12-03 04:09:21Z, KK7CXF, 110(22/14),? [NONE] , |||||||__
2022-12-03 04:09:30Z, KK7CXF, 82(16/12),? [NONE] , __||_____
2022-12-03 04:09:33Z, KK7CXF, 71(17/15), , _1000____
2022-12-03 04:09:34Z, KK7CXF, 63(18/14), , 5000000__
2022-12-03 04:09:34Z, KK7CXF, 64(18/15), , 3000000__
2022-12-03 04:09:35Z, KK7CXF, 63(18/15), , 2000000__
2022-12-03 04:09:37Z, KK7CXF, 82(15/12), , __000____
2022-12-03 04:09:40Z, KK7CXF, 81(14/9),? [NONE] , __|||____
2022-12-03 04:09:41Z, KK7CXF, 88(17/15),? [NONE] , _||||||__

If anyone thinks this is useful, I can do a pull request and post it.


Re: Log directory option not working?

 

I believe I have it figured out.? ? The "stock" logging option is only for APRS packets.? ?I wanted to log all "heard" packets so I can display them on a simple web page so users of my gateway can see if they are being received or not.? ? I know I could parse this info from the stdout, but that seems awkward.? ?Instead I added a bit of code and compiled my own version that optionally creates a "heard" log file like so:

rmsgwpi:/var/log/radio# cat 2022-12-03.log
2022-12-03 04:09:21Z, KK7CXF, 110(22/14),? [NONE] , |||||||__
2022-12-03 04:09:30Z, KK7CXF, 82(16/12),? [NONE] , __||_____
2022-12-03 04:09:33Z, KK7CXF, 71(17/15), , _1000____
2022-12-03 04:09:34Z, KK7CXF, 63(18/14), , 5000000__
2022-12-03 04:09:34Z, KK7CXF, 64(18/15), , 3000000__
2022-12-03 04:09:35Z, KK7CXF, 63(18/15), , 2000000__
2022-12-03 04:09:37Z, KK7CXF, 82(15/12), , __000____
2022-12-03 04:09:40Z, KK7CXF, 81(14/9),? [NONE] , __|||____
2022-12-03 04:09:41Z, KK7CXF, 88(17/15),? [NONE] , _||||||__

If anyone thinks this is useful, I can do a pull request and post it.


Re: Third Party not inspected by filters

 

开云体育

Fantastic work Geoffrey,? I've been trying to figure this out myself.? Ideally i just allow message
type packets from IS->RF, but you have to essentially allow all third party packets to get all
those embedded messages too.

cool,
-craig
KM6LYW

On 12/2/22 13:33, Geoffrey Merck wrote:

Hi All,

Today I decided to get my hands on it, we have some fellows who thin it is funny to gate repeater objects from IS to RF with 2 or more hops...

I came out with this . Basically, now all filters inspect thrid party payloads....
This solves my issues with the useless objects but brings another issue. Some filters that shall not apply on third party payload are applied on third party payload.

These filters are the filters working on the path: d/ v/ and u/

Still have to fiure a way out to get around it.


73
Geoffrey F4FXL - KC3FRA

?



Re: Third Party not inspected by filters

 

Hi All,

Today I decided to get my hands on it, we have some fellows who thin it is funny to gate repeater objects from IS to RF with 2 or more hops...

I came out with this . Basically, now all filters inspect thrid party payloads....
This solves my issues with the useless objects but brings another issue. Some filters that shall not apply on third party payload are applied on third party payload.

These filters are the filters working on the path: d/ v/ and u/

Still have to fiure a way out to get around it.


73
Geoffrey F4FXL - KC3FRA

?


Re: "Sent" packets in KISS terminal

 

Hi Rob and David,

Thank you for the discussions and the advice. Adding IChannel 15 seems to work. I am still monitoring my logs and kissutil to see if has unwanted results. But so far, attached clients are now able to read packets received via igate.

Should you wish to check out the application I am developing and maintaining, I would be happy to share -- .

Cheers,

angelo


Re: "Sent" packets in KISS terminal

 

As I reread David's question, I am a little confused.
? ?>??If this user has a RF channel configured via direwolf.conf "CHANNEL 0", to forward any IGATE heard trafficthat way, would configure "IChannel 0" here?
If you configure ICHANNEL 0, I would assume that would cause an error. The other option would be the data from the soundcard would be 'muted' and the data from APRS-IS would be sent as TCP/IP KISS on 'stream 0'
Again, the concept of ICHANNEL was listeing to APRS-IS and sending the packets out to attached clients over KISS over TCP/IP

I will use my balloon tracking configuration file to explain.
? ? ADEVICE0? - null? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? # RTL_FM feed audio in through standard input, 'listen only'
? ? ACHANNEL 1
? ? CHANNEL 0
? ? MYCALL KB8RCO-2
? ? MODEM 1200
#? MODEM 9600

# ? CHANNEL 1? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? # Not used as Device 0 only has 1 channel

ADEVICE1 plughw:1,0? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? # USB sound card connected to a 2 meter radio
? ? ACHANNELS 1
? ? CHANNEL 2
? ? MYCALL KB8RCO-3
? ? MODEM 1200
#? MODEM 9600
AGWPORT 8000
KISSPORT 8001
IChannel 15
IGSERVER noam.aprs2.net:14580
IGLOGIN KB8RCO-5 {passcode}
IGFILTER m/80 f/KE8VUC-11/100? ? ? ? ? ? ? ? # Using friend filter of balloon callsign.?
IGTXVIA? 0
PBEACON sendto=IG every=30:00 symbol="House" overlay=R lat=42^17.53N long=083^42.80W

In the picture that was previously posted, you see "CH ##:" which indicates which KISS stream identifier the data came in on.
? ? ? CH? 0 -> RTL dongle => Direwolf => 'my antenna pointing client' (picture is that output)
? ? ? CH? 1 -> no data because ADEVICE0 only has 1 channel
? ? ? CH? 2 -> Sound card => Direwolf => 'my antenna pointing client' (picture is that output)
? ? ? CH? 3 -> no data because ADEVICE1 only has 1 channel
? ? ? CH 15 -> APRS-IS => Direwolf => my 'antenna pointing client' (picture is that output)
? ? ? ? ? ? ? ? ? ? ? NOTE: nothing into CH 15 is going.? That is actually handled by the IGATE function of Direwolf.
? ? ? ? ? ? ? ? ? ? ? Any attached client would send on channel 0 (not capable), or Channel 2.
Now add a second APRS 'client2' that attaches to Direwolf:
? ? ? CH? 0 -> RTL dongle => Direwolf => client2
? ? ? CH? 1 -> no data because ADEVICE0 only has 1 channel
? ? ? CH? 2 -> Sound card => Direwolf => client2
? ? ? CH? 3 -> no data because ADEVICE1 only has 1 channel
? ? ? CH 15 -> APRS-IS => Direwolf => client2
? ? ? ? ? ? ? ? ? ? ? NOTE: nothing?into?CH 15 is going.? That is actually handled by the IGATE function of Direwolf.
? ? ? ? ? ? ? ? ? ? ? Any attached client would send on channel 0 (not capable), or Channel 2.
When client2 transmits, Direwolf receives the requests and acts on it accordingly.?
I am pretty sure that if client 2 sends (say a position) the packet to Direwolf, that will be sent out according to the Direwolf configuration (any TX available port).
? ?In the example above, that would be CH0 (to null device), CH3 (plughw), and APRS-IS (since it is configured).?
? ?Since CH 15 is redundant with APRS-IS, there is no need to send it over CH 15.? It would be a duplicate.
Same with 'my antenna pointing client' sending packets.
-----
Rob KB8RCO


Re: "Sent" packets in KISS terminal

 

Verified the ICHANNEL will distribute the APRS-IS packets to all KISS clients on assigned port.
I only had 2 going, but both received the data.

Robert Giuliano
KB8RCO



On Wednesday, November 30, 2022 at 03:15:00 PM EST, David Ranch <direwolf-groupsio@...> wrote:



Thanks for that Rob.? I vaguely remember this one but it's not documented anywhere other so I kept my mouth shut. :-)? I now see it in the DEV branch's source code but there is no real description of what this is in the Git commit log either.? If this user has a RF channel configured via direwolf.conf "CHANNEL 0", to forward any IGATE heard trafficthat way, would configure "IChannel 0" here?? Do you know if specifying MULTIPLE destination channels is possible here?

--David
KI6ZHD


On 11/30/2022 12:05 PM, Rob Giuliano via groups.io wrote:

Some time ago I requested the APRS-IS traffic be available over TCP-KISS port.
That was implemented in V1.7C, and you can assign the port in the configuration file:
#############################################################
#? ? ? ? ? ? ? ?VIRTUAL TNC SERVER PROPERTIES? ? ? ? ? ? ? ?#
#############################################################
AGWPORT 8000
KISSPORT 8001
IChannel 15

In this configuration, any packets received from APRS-IS (met any filtering requirements, etc.) would be sent to any attached KISS client on port 15.
Since Direwolf was acting as my internet server,?I used this with a filters to receive any packets from a specific callsign to my 'special use' client application.
NOTE:? Traffic was (assumed still 'is') unidirectional - internet to client ONLY.

Is that what you are asking about?
-----
Rob KB8RCO


Re: Log directory option not working?

 

开云体育

Yah, I'm with you on that, using ramdiscs in remote locations now.? I use logrotate as you
suggested, I didn't know direwolf has that kind of feature.? Let us know what you come up
with.



On 12/1/22 09:59, ksmolkowski@... wrote:

I could do what you suggest, but the think I like about the -l option is that its supposed to create a daily log file so it will clean up after itself.? ? This setup will run in a very remote location and my goal is to make it as automated as possible.

There are lots of options I know,? with tee and logrotate, but if the application supports it, then why re-invent the wheel?


Re: Log directory option not working?

 

I could do what you suggest, but the think I like about the -l option is that its supposed to create a daily log file so it will clean up after itself.? ? This setup will run in a very remote location and my goal is to make it as automated as possible.

There are lots of options I know,? with tee and logrotate, but if the application supports it, then why re-invent the wheel?


Re: Log directory option not working?

 

开云体育

I can't explain the -l/-L options.. you could redirect all output to a file with

direwolf > /var/log/radio/direwolf/direwolf.log 2>&1


I happened to use "tee" in my implementations,

direwolf -d t -p -q d -t 0 -c /run/direwolf.tnc.conf | tee /var/log/radio/direwolf/direwolf.log



did you try -L /path/to/logfile.log? ?? (upper case L)


-craig
KM6LYW

On 12/1/22 09:23, ksmolkowski@... wrote:

I am running direwolf with the -l option, but it's not writing the log files to where I specify, its still writing to stdout.? ?I don't have log file settings in the conf file and I tried putting a "/" at the end and not doing so with the same result.

radio@rmsgwpi:/var/log/radio/direwolf $ ps -ef | grep dire
radio? ? 31276 31275? 7 Nov23 pts/4? ? 13:50:21 direwolf -c /usr/local/radio/direwolf/direwolf.conf -l /var/log/radio/direwolf/ -d n -d v
?
I validated that the "radio" user can write to that location
radio@rmsgwpi:/var/log/radio/direwolf $ touch /var/log/radio/direwolf/xx
radio@rmsgwpi:/var/log/radio/direwolf $ ls -l /var/log/radio/direwolf/
total 0
-rw-r--r-- 1 radio radio 0 Dec? 1 09:18 xx


?