开云体育

I am replacing the old PC with the RPi and the KPC3 with the TNC-Pi. This will be running on the local 220Mhz lan to inject connectivity to the current flexnet group in NJ near my home (Staten

David, thank you of your thoughts. Direwolf (APRS/AX.25) and SvxLink (FM phone) share the same ALSA audio input of RIM-Maxtrac (CM119). Both have separate transmit audio and PTT lines connected to the

Hello Veijo, Does your project QSY the radio between two different frequencies? Does it monitor both frequencies in a "scan" like fashion? If so, I imagine it will be hard NOT to miss some bits from a

Hello Charles, What is your goal here? Do you just want to replace the KPC3 with the TNC-Pi? That's possible but you won't use Direwolf here as Direwolf and the TNC-Pi do the same function. Pick one.

Direwolf is a software replacement for the traditional TNC.? Use one or the other but not both. Perhaps a PowerPoint presentation will make this clear. The difference between slides 12 and 13 in the

Any suggestions on using Direwolf with a RPi 3B and a TNC-Pi with a Kenwood TM-231/331 radio? Currently there is a KPC-3 and a desktop 386 PC which is failing. I am using JNOS, but am thinking about

Hei, I found this DW's transmit inhibit very useful. I'm running SvxLink and Direwolf in a RPi 3 which is connected to a Motorola GM340 transceiver with RIM-Maxtrac. Both FM and APRS are two-way

"Don Rolph" <don.rolph@...> writes: The gpsd project's stance is always that people should run the latest release... I would expect the shlib major changes, so you would then need to rebuild

I have been poking to try to understand some instabilities I have observed with Dire Wolf using gpsd under Raspbian BullsEye. I saw: - a flood of packets through the sound card when achieving gps fix

Hey Jeff, Oh.. your update partially changes my previous email which is great though: - The x86 binary is still the original old 32bit only i386 file - The ARM6 and ARM7 binaries are newer but still

Hello Jeff, I assume you're talking about the newest X-net binaries be it the v1.38 or newer v1.39 Beta at http://xnet.swiss-artg.ch/beta/index.htm ? I had tried those a LONG time ago but I always had

I know you want to transmit, which is why I highlighted the transmit line from the user guide in bold. You use the same format. I just did a quick test. I created a 'kiss_packets' directory, and ran:

Thanks again, Martin. Yes sir, I read that in the user guide, and can parse the result and decode *received* message packets just fine.? So now I want to *TRANSMIT* an ACK. What do I put in the file?

I'm curious if Xnet would work with the -p option in Direwolf. I had the linux version 1.39 running for several months (internet only) on a 2009 Asus netbook, then moved it to a 2012 RPi model B using

Updating my last message... there's versions of X-Net for other platforms like DOS and even Atari.? Newer versions include ARM6 and ARM7 processors: https://www.n1uro.com/xnet/files/. ? I'm running

From the Direwolf User Guide: —— All received frames are displayed in the usual monitor format, preceded with the channel number inside of [ ]. [0]

Hi David, Thanks for the reply.? I'm running Linux Mint Xfce 64-bit version, Direwolf 1.6, and X-Net 1.38.? X-Net is a native Linux app for packet node-switching with several drivers available,

Hi Martin - thanks for your reply. That section tells you how to launch the program and various options. It says nothing about the format of the line of text you put in the file. Since Direwolf does

Section 14.6 of the Direwolf User Guide documents kissutil and the format it uses. The APRS content would be defined elsewhere, depending on exactly what kind of APRS data you're trying to construct.

For more flexibility, the FX.25 transmit property can now be set individually by channel, rather than having a global setting for all channels. The -X on the command line now applies only to channel