开云体育

Start a terminal in your script with direwolf and its arguments as an argument to the terminal? (Can't test at the moment, but look at https://forums.raspberrypi.com/viewtopic.php?t=66206)

Thanks guys, Switched to the systemd method and it works fine.? Autostarts on boot, and restarts either instance when killing one.? Is there a method to keep the Direwolf terminal windows open on

Thanks!

That was a left over debug message from IL2P development. It is harmless. Ignore it. It has been removed.

Just compiled QTTerm and after some configuration it worked. Fabulous! Thanks all! V.

When it happened, I was using V1.7b, just because I was doing nothing critical. In my case, I was connected to Direwolf from APRSIS32 using AGW, and my app: only receives KISS packets from Direwolf,

I wouldn't recommend to try running random binaries on your system. Too often, things just won't work and testing on u20.04, I too see this error: -- strace -f ./QtTermTCP execve("./QtTermTCP",

Hello Don, I think you mean the "Master" branch which in Git parlance means "bleeding edge" aka.. unstable. Yes, you're right about the current Master branch having the Bonjour/Avahi support but

Can you help me run QtTermTCP ( https://www.cantab.net/users/john.wiseman/Documents/QtTermTCP.html ) ? I downloaded the file QtTermTCP ( http://www.cantab.net/users/john.wiseman/Downloads/QtTermTCP )

Unfortunately our deployments require functionality of the 1.7 release. My understanding is that there is a main branch of 1.7 which I was using. I need the Bonjour DNS announcement functionality of

Unless you're trying to use IL2P, I would just ignore those warnings. Please also note that the current production release of Direwolf is v1.6. Direwolf's development branch is currently labeled as

I see these errors in the direwolf screen entries. I am running BullsEye with Dire Wolf 1.7. wrote: -- 73, AB1PH Don Rolph

IL2P is brand new to Direwolf and still is very much Alpha. Are you trying to use it with another Direwolf or NINO TNC or are you just seeing these errors when you start Direwolf? --David KI6ZHD

This might get you pointed in the right direction ... https://ham.stackexchange.com/questions/11785/using-direwolf-with-multiple-radios It has the advantage of the predictability of systemd for

The original request was looking for AGW compatible programs. Neither Linpac or axcall offer that today. --David KI6ZHD (Maintainer of Linpac)

I saw this as well, but was connecting through a simple KISS TCP/IP port that I wrote code for. -> I kind of thought it was something in my code, so wasn't speaking up. I was running Nexus version of

I agree with using systemd vs. cron. My only question is your cron file.? You are using separate lines for each script? Since this appears to be a cron issue, you might post the actual cron lines in

Hmm, I am seeing a message “IL2P header has reverse polarity” after I build on Raspian BullsEye. I did not see this message on Buster. Does anyone know what this message in the Dire Wolf screen

That should have been "more than one ADEVICE" and "systemd" not "systems" One typo and one autocorrect. [email protected]> wrote:

Why are you running two instances? Direwolf can handle more than on ADEVICE at a time. Second, systems would be better than cron for managing startup and restarts. wrote: