Keyboard Shortcuts
Likes
- Direwolf
- Messages
Search
Re: Easy Digi Universal, sanity check
Dave, double check your radio. It's a 6 pin Din.
Jim Bacher, WB8VSU
wb8vsu@...
On Feb 24, 2021, at 3:20 PM, David Jaquay <djaquay@...> wrote: I'm looking to get a Yaesu FT-8900r hooked up for 2m packet, and looking for a sanity check on my thoughts. |
Easy Digi Universal, sanity check
I'm looking to get a Yaesu FT-8900r hooked up for 2m packet, and looking for a sanity check on my thoughts.
My current plan is to get an Easy Digi Universal, which if I read it right, contains the sound card, and will hook up directly to the 9-pin mini-DIN on my radio.? Then Direwolf can be configured to talk via USB to the Easy Digi, can be setup to control PTT, and will send/rcv using the Easy Digi's sound card.? Computer-wise, I would either be using a Win10 laptop or a RasPi 3B+ running Raspbian; I'd like to be able to switch between the two, as I see fit. I do have a question into Clifford at Easy Digi, as his main listing appears to be for the 6-pin DIN, and I might need a different model.? Any feedback on that?? Anybody needed to go that route? Thanks, Dave KC3LZY |
Re: KISS TCP get entire raw APRS message?
Yes. As long as you reverse the process and package up your APRS packet into an AX.25 frame, you can pass that frame to Direwolf via KISS. I haven't tried it, but the write() method on the TCPKISS interface you're using should do what you want, given an encoded AX.25 frame. Martin. KD6YAM On Tue, Feb 23, 2021 at 7:24 AM W Boring (hemna) <waboring@...> wrote:
|
Re: KISS TCP get entire raw APRS message?
Thanks for the help.? I have been able to decode the ax.25 packet and get the aprs header and payload that is now parseable by aprslib. ? wx report ? [../test.py.p:70] {'raw': 'W4PGT-1>APTW14,W4PGT*,K2VIZ-8*,WR4CV-4*,WIDE2*:_02231027c284s002g006t049r000p024P000h69b10099tU2k', 'from': 'W4PGT-1', 'to': 'APTW14', 'path': ['W4PGT*', 'K2VIZ-8*', 'WR4CV-4*', 'WIDE2*'], 'via': '', 'format': 'wx', 'wx_raw_timestamp': '02231027', 'comment': 'tU2k', 'weather': {'wind_direction': 284, 'wind_speed': 0.89408, 'wind_gust': 2.68224, 'temperature': 9.444444444444445, 'rain_1h': 0.0, 'rain_24h': 6.096, 'rain_since_midnight': 0.0, 'humidity': 69, 'pressure': 1009.9}} |
Re: APRS Notification
Hello, No, I dont think that what I mean, basically I live in a very quiet area, what Id be interested in is that each time my iGate get a packet like this: That I get some sort of alert that its got it. Gavin. Sent from iCloud On February 22, 2021 at 8:38 PM, "David Ranch" <direwolf-groupsio@...> wrote:
|
Re: APRS Notification
¿ªÔÆÌåÓýHello Gavin, Are you asking to get an email when you receive an APRS TXT message sent to your callsign?? Direwolf's APRS stack really doesn't support APRS messaging so you will need to look elsewhere.? Two linux programs that do support APRS messaging on Linux are: ?? - Xastir (Xwindows GUI tool) ?? - NixTracker (web interface): ?? - YACC (Java GUI tool: I imagine either tool could be modified to send an email when you receive a message. --David KI6ZHD On 02/22/2021 02:28 AM, gavin.wilby via
groups.io wrote:
Hello, |
Re: KISS TCP get entire raw APRS message?
You are getting the complete message. It is being provided to you as an AX.25 frame, so it's up to you to decode that frame to retrieve its contents, such as the source and destination fields. The problem you're facing is that aprslib expects you to pass in a formatted string, having already decoded the packet, so that it can then decode the string. You'll need to do that translation (AX.25 frame to the string format aprslib expects) yourself. Martin. KD6YAM On Mon, Feb 22, 2021 at 7:29 AM W Boring (hemna) <waboring@...> wrote: Hey guys, |
KISS TCP get entire raw APRS message?
Hey guys,
? I'm trying to figure out how to get the entire raw aprs message from the KISS tcp interface. I am able to connect to the KISS tcp interface and see frames come from direwolf, but what I'm seeing is only a portion of the ARPS message itself. This is what direwolf logs for a particular aprs message
This is what I get from the KISS interface? hexdump.hexdump(frame) 00000000: 00 82 A0 9A 92 60 68 60? 96 94 68 A6 9C A8 60 AE? .....`h`..h...`.
00000010: 68 AA 9C 86 40 E6 AE A4? 68 86 AC 40 E8 AE 92 88? [email protected]..@....
00000020: 8A 64 40 E1 03 F0 54 23? 32 31 33 2C 31 37 39 2C? [email protected]#213,179,
00000030: 30 32 39 2C 30 30 37 2C? 30 36 35 2C 30 35 35 2C? 029,007,065,055,
00000040: 30 30 30 30 30 30 30 30? ? ? ? ? ? ? ? ? ? ? ? ? ?00000000
As you can see I am only getting a portion of the entire APRS message The APRS message: KJ4SNT>APMI04,W4UNC-3,WR4CV-4,WIDE2*:T#213,179,029,007,065,055,00000000 What I'm seeing T#213,179,029,007,065,055,00000000 How can I get the entire message so I can send that through aprslib's () decode Here is my python snippet def p(frame):
? ? print(hexdump.hexdump(frame))
?
k = kiss.TCPKISS("192.168.1.7", 8001)
k.start()
k.read(callback=p) |
Re: Direwolf, hamlib, and pi, oh my
Hi, all.
Thanks for the suggestions. I did recompile direwolf, and that seems to have solved my problem. I have subsequently broken JS8Call and WSTJ-X, perhaps because they depend on the earlier version of hamlib. But that's a problem for a different forum. 73, Rick K3ROG |
Re: Direwolf, hamlib, and pi, oh my
On 2/21/21 12:12 PM, Matt 9V1MH/VK3AMH/YF2AAH wrote:
did you build/install hamlib/direwolf yourself. Direwolf has 2 build options - with and without hamlibIf hamlib is already installed, the direwolf install will include hamlib. If you install direwolf before installing hamlib, you cannot add hamlib support unless you delete direwolf and reinstall with hamlib already present. YMMV Chuck |
Direwolf, hamlib, and pi, oh my
Hi, all.
I'm using direwolf 1.6 to decode APRS packets on my IC-705 using a Raspberry Pi 3+ connected to the rig via USB. Decodes work great.? But In trying to fix a PTT bug, I upgraded to hamlib 4.1 because it supports the IC-705. Now, I get a "Hamlib error: Unknown rig model 3085.? Run "rigctl --list" for a list of model numbers." error when direwolf opens. But running 'rigctl --list | grep 705' gives me '3085 Icom IC-705 20210129.0 Stable RIG_MODEL_IC705'.? So, this 3085 is the right rig number for hamlib 4.1. Somehow, direwolf 1.6 isn't correctly reading the rig identifier from hamlib 4.1. I note that the hamlib 4.1 rig identifiers have changed from hamlib 3.x. The relevant PTT line in direwolf.conf is as follows: PTT RIG 3085 /dev/serial/by-id/usb-Icom_Inc.-IC-705_12004781-if00 I realize that this is a very specific problem, but perhaps someone else has encountered it and determined a solution. Thanks and 73, Rick K3ROG |
Re: Can I use direwolf with a serial TNC?
¿ªÔÆÌåÓýHello Thomas, No, Direwolf does not work with serial TNCs as you cannot disable the redundant modem and KISS encapsulation functions within Direwolf.? That kind of configuration might be added some day but until then, you can use programs like APRX, Xastir, aprsdigi, etc. directly or use Linux's native AX25 stack with other Linux digipeating programs. --David KI6ZHD On 02/16/2021 03:33 AM, Thomas Habets
wrote:
|
Can I use direwolf with a serial TNC?
Hi.
I have a Kenwood TH-D74, which provides a serial TNC. It works very well, and removes the need to think about PTT as compared to using it as a sound card. Is there a way to run direwolf's digipeater functionality against a serial TNC? typedef struct me_s { ?char name[] ? ? ?= { "Thomas Habets" }; ?char email[] ? ? = { "thomas@..." }; ?char kernel[] ? ?= { "Linux" }; ?char *pgpKey[] ? = { "" }; ?char pgp[] = { "9907 8698 8A24 F52F 1C2E ?87F6 39A4 9EEA 460A 0169" }; ?char coolcmd[] ? = { "echo '. ./_&. ./_'>_;. ./_" }; } me_t; |
Re: Kiss Question
This is exactly the use case. I will need to look at this more closely, but based on my initial read, it appears that I could use radio 1 (Direwolf radio port 0) on 8001, and radio 2 (Direwolf radio port 1) on 8002 and transmit/receive with the appropriate radio by selecting the appropriate network port. This would completely address my use case if this is the option. The alternative as someone else suggested was to modify the code to map radio port 1 to network port 8001, but taking a look at the code, it was not entirely obvious where the radio port was mapped in the Kiss networking code. Thanks and 73, -Corky, AF4PM On Sun, Feb 14, 2021, at 5:08 AM, WB2OSZ wrote:
|
Re: Kiss Question
Does this help??? It is a new feature, in the 'dev' development branch, but not the 1.6 release.
??????? Separate KISS TCP ports per radio: ? An increasing number of people are using multiple radios. direwolf is capable of handling many radio channels and provides cross-band repeating, etc. Suppose a single stereo audio interface is used for 2 radios. ? ?????????????????? +------------+??? tcp 8001, all channels Radio A? --------? |??????????? |? -------------------------- Application A ?????????????????? |? direwolf? | Radio B? --------? |??????????? |? -------------------------- Application B ?????????????????? +------------+??? tcp 8001, all channels ? The KISS protocol has a 4 bit field for the TNC port (which I prefer to call channel because port has too many different meanings). direwolf handles this fine.? However, most applications were written assuming that a TNC could only talk to a single radio.? On reception, they ignore the channel in the KISS frame.? For transmit, the channel is always set to 0. ? Many people are using the work-around of two separate instances of direwolf. ? ?????????????????? +------------+??? tcp 8001, KISS ch 0 Radio A? --------? |? direwolf? |? -------------------------- Application A ?????????????????? +------------+ ? ?????????????????? +------------+??? tcp 8002, KISS ch 0 Radio B? --------? |? direwolf ?|? -------------------------- Application B ?????????????????? +------------+ ? ? Or they might be using a single application that knows how to talk to multiple single port TNCs.? But they don't know how to multiplex multiple channels thru a single KISS stream. ? ?????????????????? +------------+??? tcp 8001, KISS ch 0 Radio A? --------? |? direwolf? |? ------------------------ ?????????????????? +------------+????????????????????????? \ ??????????????????????????????????????????????????????????? -- Application ?????????????????? +------------+??? tcp 8002, KISS ch 0?? / Radio B? --------? |? direwolf? |? ------------------------ ?????????????????? +------------+ ? Using two different instances of direwolf means more complex configuration and loss of cross-channel digipeating.? It is possible to use a stereo audio interface but some ALSA magic is required to make it look like two independent virtual mono interfaces. ? In version 1.7 (currently in development), we add the capability of multiple KISS TCP ports, each for a single radio channel.? e.g. ? KISSPORT 8001 1 KISSPORT 8002 2 ? Now can use a single instance of direwolf. ? ? ?????????????????? +------------+??? tcp 8001, KISS ch 0 Radio A? --------? |??????????? |? -------------------------- Application A ????????????? ?????|? direwolf? | Radio B? --------? |??????????? |? -------------------------- Application B ?????????????????? +------------+??? tcp 8002, KISS ch 0 ? When receiving, the KISS channel is set to 0. - only radio channel 1 would be sent over tcp port 8001. - only radio channel 2 would be sent over tcp port 8001. ? When transmitting, the KISS channel is ignored. - frames from tcp port 8001 are transmitted on radio channel 1. - frames from tcp port 8002 are transmitted on radio channel 2. ? Of course, you could also use an application, capable of connecting to multiple single radio TNCs.? Separate TCP ports actually go to the same direwolf instance. ? |
Re: Kiss Question
Typcially the application you are using (which is connecting to Direwolf) will determine the port the connection needs to be made on. I think you need to explain the situation in more detail. Why do you feel port 1 is the proper port? ?? What are you connecting to, with what application you are using to make the connection? Things like the Nexus DR-X (Digital Radio Cross Patch) can separate the chanels of the sound card. But in general, the source of the data is how the reply is determined.? For instance, if you have port 0 on 2m and 440 on port 1, any info that is heard on port 1 would be responded to on port 1. KB8RCO
On Saturday, February 13, 2021, 8:42:48 PM EST, Corky Searls <af4pm@...> wrote:
Is it possible to configure DIREWOLF to connect the KISS TCP/IP TNC? to point to port 1 vs the default of port 0 on a two-port device? It appears that this works with the serial TNC, but not clear if this is possible using the network port. Thanks, -Corky |
Re: Kiss Question
¿ªÔÆÌåÓýHello Corky, Are you asking if Direwolf could send the data payload in the KISS frames for TNC #1 and not TNC #0?? If so, I would assume this would be possible by changing the code and recompiling it. What is your scenario that would need such a thing? --David KI6ZHD On 02/13/2021 03:29 PM, Corky Searls
wrote:
Is it possible to configure DIREWOLF to connect the KISS TCP/IP TNC? to point to port 1 vs the default of port 0 on a two-port device? It appears that this works with the serial TNC, but not clear if this is possible using the network port. |