¿ªÔÆÌåÓý

Direwolf as just a receiver


 

Hi Everybody,

I have started up a new Direwolf iGate, but my intention is that the iGate works a receiver, and no as transmiter.

The issue is that my iGate show all the time this messages:

[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE:;R6-C4FM? *092115z4312.41N/00216.95Wr145.750MHz T797 -060 FM / C4FM R.C zaria

Digipeater WIDE1 (probably EA2TZ-3) audio level = 58(14/8)??? __|||||__
[0.4] ED2ZAD-3>APMI06,EA2TZ-3,WIDE1*:;ED2YAT?? *092115z4317.38N/00302.03Wr438.900MHz T123 -760? FM?? ASRABI
Object, "ED2YAT", Repeater, SQ3PLX http://microsat.com.pl/
N 43 17.3800, W 003 02.0300, 438.900 MHz, -7600k, PL 123.0
? FM?? ASRABI

[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE:;RF85_FM? *092115z4318.53N/00138.15Wr51.850MHz? T000 -060 FM? R.C zaria

Digipeater WIDE1 (probably EA2TZ-3) audio level = 55(14/8)??? __|||____
[0.3] ED2ZAD-3>APMI06,EA2TZ-3,WIDE1*:;RF85_FM? *092115z4318.53N/00138.15Wr51.850MHz? T000 -060 FM? R.C zaria
Object, "RF85_FM", Repeater, SQ3PLX http://microsat.com.pl/
N 43 18.5300, W 001 38.1500
51.850MHz? T000 -060 FM? R.C zaria

[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :PARM.Vin,Rx1h,Dg1h,Eff1h,Temp,O1,O2,O3,O4,I1,I2,I3,I4
[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :UNIT.Volt,Pkt,Pkt,Pcnt,C,On,On,On,On,Hi,Hi,Hi,Hi
[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :EQNS.0,0.075,0,0,10,0,0,10,0,0,1,0,0,0.5,-64
[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :BITS.11111111,Telemetria

but no RX>IG message.
If I go to the aprs page I see that there is no message from my iGate to the network.

This is my conf file.

ADEVICE? plughw:1,0
CHANNEL 0
MYCALL EB2BRA-10
MODEM 1200

AGWPORT 8000
KISSPORT 8001

PBEACON delay=1? every=30 overlay=S symbol="digi" lat=43^16.19N long=002^11.14W power=5 height=2 gain=1 comment="APRS VHF en pruebas" via=WIDE1-1

IGSERVER euro.aprs2.net
IGLOGIN EB2BRA-10 22179
PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=R lat=43^16.19N long=002^11.14W comment="APRS VHF en pruebas"
IGTXLIMIT 6 10

What is wrong ?

Thank you in advance.


 

Notice the digipeat path on the packets you are receiving by RF; the digipeat alias has already been consumed. This indicates you are not receiving the original Object transmissions from ED2ZAD-3, but a digipeated copy. So there was probably an I-gate that was close enough to ED2ZAD-3 to hear the original transmission and get it to the APRS-IS backbone before your station heard the digipeat of the packet. Since the APRS-IS backbone is deliberately designed to suppress duplicates, you will never be the first I-gate to relay those particular stations to the backbone.

However, you did NOT configure your station to be a receive-only I-gate, which is why you are seeing the [ig>tx] messages. So you are I-gating some traffic (which is why you are being given responses to send to that station) but you are not the first I-gater. I don't see a IGTXVIA directive in your configuration, but it might be implied because you did specify IGTXLIMIT.

If you want to actually see traffic I-gated by your station, it has to be traffic that no other I-gate can hear (so no one can beat you to the backbone with the packets). For example, a low-power HT beaconing right next to your I-gate, so no one else could receive it.

Hope this helps.

Andrew, KA2DDO

________________________________________
From: [email protected] <[email protected]> on behalf of John <eb2bra@...>
Sent: Saturday, March 9, 2024 5:27 PM
To: [email protected]
Subject: [direwolf] Direwolf as just a receiver

Hi Everybody,

I have started up a new Direwolf iGate, but my intention is that the iGate works a receiver, and no as transmiter.

The issue is that my iGate show all the time this messages:

[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE:;R6-C4FM *092115z4312.41N/00216.95Wr145.750MHz T797 -060 FM / C4FM R.C zaria

Digipeater WIDE1 (probably EA2TZ-3) audio level = 58(14/8) __|||||__
[0.4] ED2ZAD-3>APMI06,EA2TZ-3,WIDE1*:;ED2YAT *092115z4317.38N/00302.03Wr438.900MHz T123 -760 FM ASRABI
Object, "ED2YAT", Repeater, SQ3PLX
N 43 17.3800, W 003 02.0300, 438.900 MHz, -7600k, PL 123.0
FM ASRABI

[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE:;RF85_FM *092115z4318.53N/00138.15Wr51.850MHz T000 -060 FM R.C zaria

Digipeater WIDE1 (probably EA2TZ-3) audio level = 55(14/8) __|||____
[0.3] ED2ZAD-3>APMI06,EA2TZ-3,WIDE1*:;RF85_FM *092115z4318.53N/00138.15Wr51.850MHz T000 -060 FM R.C zaria
Object, "RF85_FM", Repeater, SQ3PLX
N 43 18.5300, W 001 38.1500
51.850MHz T000 -060 FM R.C zaria

[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :PARM.Vin,Rx1h,Dg1h,Eff1h,Temp,O1,O2,O3,O4,I1,I2,I3,I4
[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :UNIT.Volt,Pkt,Pkt,Pcnt,C,On,On,On,On,Hi,Hi,Hi,Hi
[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :EQNS.0,0.075,0,0,10,0,0,10,0,0,1,0,0,0.5,-64
[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :BITS.11111111,Telemetria

but no RX>IG message.
If I go to the aprs page I see that there is no message from my iGate to the network.

This is my conf file.

ADEVICE plughw:1,0
CHANNEL 0
MYCALL EB2BRA-10
MODEM 1200

AGWPORT 8000
KISSPORT 8001

PBEACON delay=1 every=30 overlay=S symbol="digi" lat=43^16.19N long=002^11.14W power=5 height=2 gain=1 comment="APRS VHF en pruebas" via=WIDE1-1

IGSERVER euro.aprs2.net
IGLOGIN EB2BRA-10 22179
PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=R lat=43^16.19N long=002^11.14W comment="APRS VHF en pruebas"
IGTXLIMIT 6 10

What is wrong ?

Thank you in advance.


 

John,
Building from Andrew's advice and towards verifying that your igate is uploading data you could explore one or both methods below.? Hope this helps & 73, Jon

1)
Have direwolf send igate statistics to the APRS-IS using IBEACON.? This will show the numbers of packets, distinct stations, etc are actually being heard over RF and uploaded to the APRS-IS.

IBEACON sendto=IG delay=30 every=30

Since this data will probably scroll past in the terminal, you can then observe your statistics in the raw packets at findu.com or at the equivalent aprs.fi resource:
http://www.findu.com/cgi-bin/raw.cgi?call=EB2BRA-10&time=1&start=3

The IBEACON command usage and its output values are described in the "Successful-APRS-IGate-Operation.pdf" document at WB2OSZ's github site.

2)
a. Find the APRS-IS server that your instance of Direwolf is connected to by noting the packets at the findu.com or aprs.fi resource above.? The server name comes after qAC, and before the : .? It can also be found in Direwolf's terminal but it will likely scroll by without being noticed.? The servers can automatically change depending on load and internet traffic conditions.

b. Find your server in the left column on this status page:? ???? Click on your server in the left column.

c. The status page for your APRS-IS server will open, search this page for your callsign-ssid.? There will be plenty of details accumulating since your station connected to this server.? Some of the details will be the number of packets that your station has uploaded, how many minutes or seconds ago your station last uploaded a packet (Last in), and an idea of how many packets that you uploaded were duplicates of packets already uploaded by another igate (Packets Rx).


John
 

¿ªÔÆÌåÓý

Hi Jon,

Thanks a lot for all advices. I will read them again carefully and put them into practice and see what happens.

Best regards

On 3/11/24 18:29, Jon Dea (AA4JM) wrote:

John,
Building from Andrew's advice and towards verifying that your igate is uploading data you could explore one or both methods below.? Hope this helps & 73, Jon

1)
Have direwolf send igate statistics to the APRS-IS using IBEACON.? This will show the numbers of packets, distinct stations, etc are actually being heard over RF and uploaded to the APRS-IS.

IBEACON sendto=IG delay=30 every=30

Since this data will probably scroll past in the terminal, you can then observe your statistics in the raw packets at findu.com or at the equivalent aprs.fi resource:


The IBEACON command usage and its output values are described in the "Successful-APRS-IGate-Operation.pdf" document at WB2OSZ's github site.

2)
a. Find the APRS-IS server that your instance of Direwolf is connected to by noting the packets at the findu.com or aprs.fi resource above.? The server name comes after qAC, and before the : .? It can also be found in Direwolf's terminal but it will likely scroll by without being noticed.? The servers can automatically change depending on load and internet traffic conditions.

b. Find your server in the left column on this status page:? ???? Click on your server in the left column.

c. The status page for your APRS-IS server will open, search this page for your callsign-ssid.? There will be plenty of details accumulating since your station connected to this server.? Some of the details will be the number of packets that your station has uploaded, how many minutes or seconds ago your station last uploaded a packet (Last in), and an idea of how many packets that you uploaded were duplicates of packets already uploaded by another igate (Packets Rx).