Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Direwolf
- Messages
Search
|
Grey Terminal Background
When using Direwolf for Raspberry PI version 1.3-2, apparently the most recent in the repositories for Stretch.
Is there a way to changes the colors Direwolf uses? I have the termianl set for a white background with black text. Direwolf deems to change that to a grey background. Some of the text is pink, making it unreadable. Direwolf appears to be making the changes because when text from Direwold is printed the background of the text is grey with the text being different colors depending on what is being printed. This seems to only effect the Raspberry Pi. Any help appreciated. |
|
Re: ISS: can't see myself being digipeated
Hello David,
Thanks for the reply/answer and sorry for coming back so late. I did test some things over the past few days, so I got somewhat of a solution. You are right I am not using the build-in TNC but Direwolf exclusively and ARISS is the digipeater. So all good there. As for the sound levels: I knew these have influence, but not that it would cause bleed-over and repeated packets, I thought more of distortion. The suggestion I usually see is 3/4 of the total volume and I kept it somewhat above that (80-85%). But the reason is that the discriminator of the TS-2000 needs a high voltage for 9600 baud operation. I do daily runs of Falconsat-3, which is transmitting APRS and a BBS in 9600 baud and below 60% volume my outgoing audio signal is not strong enough for the discriminator to handle. So with the ALSA volume down to 50% I have digipeats and no bleed-over when working 1200 baud APRS via the ISS. With the ALSA volume at 50% I don't have digipeats via Falconsat-3 at 9600 baud, so the volume needs to be increased to 80%. To be complete: I do switch between 1200/9600 on the TS-2000 (menu option 50F), otherwise it still won't work :-) I think I'm going to write some wrapper bash scripts for Direwolf so that when Direwolf starts up the ALSA volume will be set at 50% or 80% respectively according to the speed I'm using. The other solution would be so install an audio amp in-line which can be switched on when using 9600 baud. BTW, thank you also for this webpage on your site: . That really is a labor of love and it solved my wandering ALSA hardware address problem. So much to learn from that page, so thanks for sharing your knowledge. |
|
Re: No IGate Transmit
I looked over your config file and I see the issue. By default, Direwolf only sends messages to individuals heard in the last 30 minutes. To change this, insert a line after your IGFILTER statement. It should read FILTER IG 0 followed by your filter string. Consult section 9.6 of the user guide regarding packet filtering. If you wish to send individual messages, add |i/30 to the end of the filter string you construct. Best of luck, Patrick (N3TSZ)
On Friday, August 6, 2021, 03:33:52 PM EDT, PAUL UNWIN <paul@...> wrote:
[Edited Message Follows] Hi Patrick,Thankyou for the fast response, i've attached the conf file it's from my PI setup. As far as i can see the igate is being pointed at my TX Channel 0 and Channel 0 does transmit both my beacon and morse i.d. So it seems both my CM108 PTT and audio works ok its just not the data fed from the IGate server.... Anyway i await your feedback.... Regards Paul (G4HDS) |
|
Re: No IGate Transmit
Hi Patrick,
Thankyou for the fast response, i've attached the conf file it's from my PI setup. As far as i can see the igate is being pointed at my TX Channel 0 and Channel 0 does transmit both my beacon and morse i.d. So it seems both my CM108 PTT and audio works ok its just not the data fed from the IGate server.... Anyway i await your feedback.... Regards Paul (G4HDS) |
|
Re: No IGate Transmit
Hello Paul, The line with [Ig>tx] should be followed by a line beginning with [channel number] in magenta colored text. If you do not see that, your IG to TX is not configured or the data is being filtered. Please post a copy of your .conf file so that we may have a look at it.? Best regards, Patrick (N3TSZ)
On Friday, August 6, 2021, 02:38:07 PM EDT, PAUL UNWIN <paul@...> wrote:
Hi All, ? ? ? ? ? I'm hoping that someone could kindly shine a light on a daft problem I have... I'm sure the problem is a config error but I simply can't see it myself at the? present time. I've been running Direwolf Version 1.3f on a windows setup for sometime with no problems. However I decided to upgrade to V1.6 and run it on a Raspberry PI.? After compiling and setting up everything appeared to work...? The digipeater, and cw ident work like a charm... But the IGate will simply will not retransmit any data on my local rf port ! It doesn't key up the tx or produce any audio tones either. It does however key up and transmit my beacon info without a problem... I've checked and double checked my filter settings and I can watch the screen show the? info from the IGate server apparently being sent, Ig>tx appears followed by the data to be transmitted.... just nothing else happens.? I then setup the windows precompiled version 1.6 with exactly the same result. I'm convinced that by going from V1.3 directly to V1.6 I've missed out some newly added filter or configuration setting.... So any suggestions please ?? In the mean time I'll be reading up on the user instructions for the latest versions Regards Paul G4HDS |
|
No IGate Transmit
Hi All,
? ? ? ? ? I'm hoping that someone could kindly shine a light on a daft problem I have... I'm sure the problem is a config error but I simply can't see it myself at the? present time. I've been running Direwolf Version 1.3f on a windows setup for sometime with no problems. However I decided to upgrade to V1.6 and run it on a Raspberry PI.? After compiling and setting up everything appeared to work...? The digipeater, and cw ident work like a charm... But the IGate will simply will not retransmit any data on my local rf port ! It doesn't key up the tx or produce any audio tones either. It does however key up and transmit my beacon info without a problem... I've checked and double checked my filter settings and I can watch the screen show the? info from the IGate server apparently being sent, Ig>tx appears followed by the data to be transmitted.... just nothing else happens.? I then setup the windows precompiled version 1.6 with exactly the same result. I'm convinced that by going from V1.3 directly to V1.6 I've missed out some newly added filter or configuration setting.... So any suggestions please ?? In the mean time I'll be reading up on the user instructions for the latest versions Regards Paul G4HDS |
|
Re: ISS: can't see myself being digipeated
¿ªÔÆÌåÓýHello Hans, First, I assume you're NOT using the built-in AX.25 TNC in your TS2000 and instead, you're only using Direwolf.? Correct?? You cannot use both at the same time.? Next, what are you using as your digipeater as configured in the UISS application?? It should be "ARISS": ?? I imagine you've seen this site but you can see live details about APRS an non-APRS AX.25 packets on . As for your issue with seeing your packets twice, this has been previously discussed on this list.? The issue comes down to two areas: ?? - Your output levels on your Direwolf sound device are way too high.? Lower you your output to more reasonable levels. ?? - Your cabling from your Direwolf soundcard to the radio is somehow having a bleed-over issue.? Consider tuning your audio levels to set the required output level ONLY on the specific channel (left or right) on your sound device.? For the non-used channel, set it's level to 0. --David KI6ZHD On 08/05/2021 04:33 AM, Hans Fong
wrote:
My setup: 5 element 2m X-pol yagi --> TS-2000 --> Behringer USB audio interface --> Direwolf --> UISS |
|
ISS: can't see myself being digipeated
My setup: 5 element 2m X-pol yagi --> TS-2000 --> Behringer USB audio interface --> Direwolf --> UISS
I made some QSOs with this setup through the ISS APRS repeater, so my setup is working - sort of. Problem is I can't see my own packets coming down from the ISS. It almost seems the digipeat is happening before the TS-2000 switches back from transmit to receive. I do see my own packet twice, with about a one second delay, but this is happening even if the ISS is not around, so clearly a Direwolf thing. I've been looking for things in the UISS and Direwolf setup to tweak, but can't find anything about timing. Could it be a TS-2000 issue? Any thoughts or input welcome. 73 from Taiwan -- Hans (BX2ABT) |
|
Re: dw-start.sh will not run from crontab
Matt Domsch N5MLD
Rather than use crontab to try to keep a process running (which it isn't really designed to do, but as proven here can be coerced into it), you may wish to use the systemd service that the?Debian-provided package (apt install direwolf) provides and is also in the direwolf source tree. The service file takes care to start direwolf in a way that's as secure as possible.? If for some reason that isn't feasible, you may look into using supervisor, itself a daemon service that launches (and restarts as necessary) other applications (in this case, direwolf).? Similarly, monit "monitors" applications started as daemons, and invokes their initscript or systemd service file to restart the as necessary, and sends emails to you when it found something had failed and when it recovers. Thanks, Matt N5MLD On Fri, Jul 23, 2021 at 3:09 AM Mikel EA2CW <ea2cw@...> wrote:
|
|
Re: Direwolf and PiGate for Winlink
¿ªÔÆÌåÓýDavid, Mike I know Gary, PiGate RMS v2 and linbpq well.? I also have this working with PiGate and PiGate RMS which uses linbpq rather than Paclink-Unix. I am just working on it for our club. I also have several other ways of using Direwolf on a Raspberry Pi working especially for remote applications. It performs better than the TNC-Pi in marginal RF situations. With multimode rigs with built in soundcards like 991A or for normal rigs, the CM108 ptt control and modified usb soundcard dongles, it is very cost effective to add improved packet capability.? I have an Alinco 135mkIII in use at a RMS which I set up using a RPi. It uses a TNC-Pi, not the 135 internal tasco tnc option (now unavailable) or Direwolf. I am considering changing ?the TNC to Direwolf when covid site access restrictions abate. However luckily there isn¡¯t a FM txr at the site! It changes the situation to our one. Haven¡¯t heard of Alinco RIM lite interface before, about to look it up. Happy to help Mike as well. Jim VA7OPD? On Jul 29, 2021, at 8:49 AM, David Ranch <direwolf-groupsio@...> wrote:
|
|
Re: Direwolf and PiGate for Winlink
¿ªÔÆÌåÓýHello Mike, I spent some time with Gary VE7POP and we were able to successfully get PiGate to work with using Direwolf on a Raspberry Pi.? The technical details was passed on to Mark Griffith (creator of PiGate) and he said he would review and consider if he'd add the support but at the time, he preferred the TNC-Pi only approach just to minimize support difficulties. If you would like to try updating your system to use Direwolf (not too difficult), please email Gary and myself offline. --David KI6ZHD On 07/28/2021 05:56 PM, Mike Sullivan
wrote:
|
|
Re: Local filter to suppress bulletin packets?
¿ªÔÆÌåÓýThe originating stations are from all over the world.? the problem is the tier2 aprsis servers sending me these "message type" bulletin packets to targets outside of my range filter.? The addressee is "BLN#". This is a list of bulletin traffic, This applies to DALLAS and T2QUEBEC.? Normally they don't send messages to BLN, but, when they do, maybe once a year, it's a flood. In any event, we are responsible for filtering at a local level with direwolf.? This local filter prevents any messages addressed to BLN* from hitting RF. IGFILTER? t/m/GTOWN/160? b/KM6LYW-9/KM6LYW-3 FILTER IG 0? t/m & ! g/BLN*? "send me all message type packets within 160km of my location, and all packets from KM6LYW-9 and -3" "transmit only message type packets to RF, but not if they're addressed to BLN*" I think that defends against DALLAS and T2QUEBEC bulletin floods. thanks, -craig KM6LYW On 7/29/21 7:07 AM, A P via groups.io
wrote:
|
|
Re: Local filter to suppress bulletin packets?
A P
Have you considered blacklisting the originating station of those bulletins? After all, the APRS-IS servers are not the source of all that spam, so you might see that from all APRS-IS servers. Or is this the same as telephone spam, that hundreds of different originating callsign-SSID values are used for originating the messages? Hmmm.... if it's a bug in some software product, perhaps you could filter on the tocall of that product (assuming the sender isn't using some common software's tocall instead of their own). It's hard to tell the issue with the traffic, since your samples look edited. Andrew, KA2DDO author of YAAC
On Wednesday, July 28, 2021, 11:42:29 AM EDT, Craig, KM6LYW <craig@...> wrote:
My HT radio message list fills with BLN* messages from all over the
world, it hits the packet limiter on direwolf, suppressing legit
traffic. I wrote the owners of DALLAS and T2QUEBEC, no answer.? now blacklisted.?? The emphasis of my digi is message-type packets, so I can't just ban all messages.? So far the local "group" filter is banning messages to callsigns BLN*. fingers crossed, -craig On 7/28/21 8:29 AM, Arnold Harding -
KQ6DI wrote:
T2QUEBEC is a
Java version server, and I have had problems with getting
excessive stuff from Java APRS servers when I use filters.?
Maybe your issue is related to what I've seen.
Arnold, KQ6DI
|
|
Re: Direwolf and PiGate for Winlink
Yes, "LinuxRMS" combined with direwolf/ax.25 on a Raspberry Pi becomes a Winlink RMS gateway on VHF/UHF.
toggle quoted message
Show quoted text
Be advised, LinuxRMS is non-trivial to install, but doable, Winlink demo of DigiPi at 14:00: On 7/28/21 9:35 PM, Mike Sullivan wrote:
|
|
Re: Direwolf and PiGate for Winlink
¿ªÔÆÌåÓýKm4ack build a pi is perfect for winlink express station. His is called PAT winlinkMine is running perfect A few hickups with downloading forms at this stage. But you can send and receive It supports Ardop and Pactor as well as P2P and Telnet Greetings from the Namib Pieter Jacobs V51pj On 29 Jul 2021, at 6:35 AM, Mike Sullivan <Kn4imu@...> wrote:
|
|
Re: Direwolf and PiGate for Winlink
¿ªÔÆÌåÓýCompact?? low power?? Raspberry Pi? ? Winlink? ??I can shamelessly self promote a DigiPi? that does all this and more, many instances in the field now. ?? Always looking for feedback and developers too. KM4ACK has a great build-a-pi also (need to confirm it runs LinuxRMS for Winlink services) best, -craig KM6LYW On 7/28/21 5:56 PM, Mike Sullivan
wrote:
|
|
Direwolf and PiGate for Winlink
We are redoing our club's Winlink 2m gateway at the tower. Original set up was a Windows PC and a KPC3, but we are wanting to switch to something much more compact. I have come across the PiGate software which is designed to be used with a TNC hat, but I was wondering if anyone has tried using Direwolf with PiGate. We have an Alinco DR-135 radio and a RIM-Lite Alinco interface to use, so that's why I'm asking. We're trying to avoid using cables between radio and TNC because we are having issues with APRS and our WX3in1 not decoding well because of a 100kW FM transmitter 450' above us. Or, failing that, if anyone has any other Pi-based suggestions (I know, kind of off topic) I would appreciate it. Mike (P.S. sorry for the repost, I goofed up the subject line) |
Danny K5CG
Patrick Connor
to navigate to use esc to dismiss