Somehow lost ability to transmit to internet / Rx-only iGate
|
Jon W7SEA
I'm using UZ7HO sound modem (in conjunction with a USB sound card) and everything was working fine.... I see packets on the UZ7HO monitor and the same packets on the APRSISCE scroller (set to RF only). I shut down for the night, clicking YES after being prompted on enabling my same KISS port upon restart (127.0.0.1; port 8100). Fire UZ7HO up again it I get a warning message "KISS Port Is Busy." I see packet activity again on UZ7HO's monitor but now nothing on APRSISCE scroller. I go to my port's log (named KISS Rx Only--example below) and see it first referring to 127.0.0.1; port 8100 then another port with a 5xxxx number that seems to change. I went through steps on Wiki about what to do if your APRSISCE isn't transmitting and it didn't fix it. Any advice? thanks
WinMain:2023-01-25T14:31:10.177 Starting Port(KISS Rx Only)
Port(KISS Rx Only):2023-01-25T14:31:10.178 TcpReader Running on @127.0.0.1 or 127.0.0.1:8100 (1 OpenCmds, 1 CloseCmds)
Port(KISS Rx Only):2023-01-25T14:31:10.179 Connected 127.0.0.1:8100
Port(KISS Rx Only):2023-01-25T14:31:10.179 Connected via 127.0.0.1:58863 |
|
|
|
Steve
Last time I looked, RX only means no transmit, I never worked out why anyone would like to be an RX only Igate, 73 Steve, kf6wax On Wed, Jan 25, 2023 at 3:02 PM Jon W7SEA <jonw7sea@...> wrote: I'm using UZ7HO sound modem (in conjunction with a USB sound card) and everything was working fine.... I see packets on the UZ7HO monitor and the same packets on the APRSISCE scroller (set to RF only). I shut down for the night, clicking YES after being prompted on enabling my same KISS port upon restart (127.0.0.1; port 8100). Fire UZ7HO up again it I get a warning message "KISS Port Is Busy." I see packet activity again on UZ7HO's monitor but now nothing on APRSISCE scroller. I go to my port's log (named KISS Rx Only--example below) and see it first referring to 127.0.0.1; port 8100 then another port with a 5xxxx number that seems to change. I went through steps on Wiki about what to do if your APRSISCE isn't transmitting and it didn't fix it. Any advice? thanks |
|
|
|
Ben Miller
I agree, but that seems to be the fad these days. APRS_IS will send messages through them that don't go anywhere. Not a problem in areas with multiple I gates, but it would be if that is the only one around. On Wed, Jan 25, 2023 at 9:28 AM Steve <kf6wax@...> wrote:
|
|
|
|
Lynn Deffenbaugh
Well, in my case my APRS antenna is located close to my amplified over-the-air TV antenna. When the IGate transmits, it desenses either the amplifier or the TV at the other end of the wire. All I know for sure is that when APRS transmits, the TV goes blank with a lost signal for about 10 seconds. So to keep the peace, my IGate is receive-only. As we say, you have to know the local RF environment before you
start transmitting with either an IGate or especially with a
digipeater. Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 1/25/2023 10:28 AM, Steve wrote:
|
|
|
|
Lynn Deffenbaugh
Note to all: It is very helpful to include your actual callsign-SSID for stations that you are talking about. It saves us trying to guess which station to look at. The second 5xxxx port is the ephemeral port that the network stack assigned to the APRSIS32 end of the connection. That is normal. What does your enabled Transmit trace log say when you select the Transmit menu optino? And what does the also-enabled Port(KISS Rx Only) trace log say at the same time? Actually, it appears that you've corrected the problem with W7SEA-10, at least the IGATE messages no longer say "R/O!". Check https://aprs.fi/?c=raw&call=W7SEA*&limit=50&view=normal But at the same time, W7SEA-10 isn't responding to query
messages, so it's either down right now or has some other
non-default configuration settings. Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 1/25/2023 10:02 AM, Jon W7SEA wrote:
I'm using UZ7HO sound modem (in conjunction with a USB sound card) and everything was working fine.... I see packets on the UZ7HO monitor and the same packets on the APRSISCE scroller (set to RF only). I shut down for the night, clicking YES after being prompted on enabling my same KISS port upon restart (127.0.0.1; port 8100). Fire UZ7HO up again it I get a warning message "KISS Port Is Busy." I see packet activity again on UZ7HO's monitor but now nothing on APRSISCE scroller. I go to my port's log (named KISS Rx Only--example below) and see it first referring to 127.0.0.1; port 8100 then another port with a 5xxxx number that seems to change. I went through steps on Wiki about what to do if your APRSISCE isn't transmitting and it didn't fix it. Any advice? thanks |
|
|
|
Jon W7SEA
Transmit trace log
2023-01-25T16:29:06.009 Logging Enabled
2023-01-25T16:31:28.884 Transmit(IS+RF) W7SEA-10>APWW11,WIDE1-1,WIDE2-1:@163128h4828. NR12011.17W&APRS-IS for Win32
2023-01-25T16:31:28.884 Transmit(INT) W7SEA-10>APWW11,WIDE1-1,WIDE2-1:@163128h4828. NR12011.17W&APRS-IS for Win32
2023-01-25T16:31:48.063 Transmit(INT) W7SEA-10>APWW11,WIDE1-1,WIDE2-1:T#550,100,048,002,128,000,10000000 Port - KISS Rx Only WinMain:2023-01-25T14:31:10.177 Starting Port(KISS Rx Only)
Port(KISS Rx Only):2023-01-25T14:31:10.178 TcpReader Running on @127.0.0.1 or 127.0.0.1:8100 (1 OpenCmds, 1 CloseCmds)
Port(KISS Rx Only):2023-01-25T14:31:10.179 Connected 127.0.0.1:8100
Port(KISS Rx Only):2023-01-25T14:31:10.179 Connected via 127.0.0.1:58863
WinMain:2023-01-25T16:28:39.994 Logging Enabled
Will include SSID in future. Just trying to send via APRS-IS to internet at this point. Replied to your message, Lynn. |
|
|
|
Lynn Deffenbaugh
First, if you named your port "KISS Rx Only", why are you expecting it to transmit? I looked at the source code, and the following conditions will result in R/O being placed on the IGATE status packet which indicates that the station is in Receive-Only mode. 1) If the APRS-IS port does not have "IS to RF" checked, you are
R/O If none of the above forces you to R/O, then all configured ports are checked to find one which is: a) Enabled If no ports pass the previous check, the station is R/O. There is an "IGateEnabled" trace log that you can enable to see
diagnostics about these checks. I don't know how often the check
is run, but it is at least at startup, so you can enable the
"IGateEnabled" trace log and restart saving the enable status and
you should see something in it after that. On 1/25/2023 11:35 AM, Jon W7SEA wrote:
Transmit trace log |
|
|
|
Lynn Deffenbaugh
Oh, I missed one additional check at the end of everything
else. If you have Enables / Ports / Receive-Only checked, then
you are definitely going to be R/O. This feature is for license
jurisdictions that require an operator to be present when
transmitting. When they walk away, a single menu click will put
them into R/O mode and a single menu click later will restore
their transmit capability without mucking around in other
configurations and possibly changing something unintentionally. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 1/25/2023 11:57 AM, Lynn Deffenbaugh
wrote:
|
|
|
|
Jon W7SEA
Thanks for the specific directions, Lynn. I checked all the things you mentioned, and everything seemed in order.
A few notes. My use of "transmit" is wrong; for the time being, all I'm trying to do is convert RF to IS, not IS to RF. The APRS-IS port was never changed; it has all of selections (e.g., IS to RF) checked as I found it. It was that way when RF was appearing on the scroller yesterday, and packets that SSID-10 "directly heard" were being sent via IS and showing on APRS.fi. The log for iGate-Enabled says the KISS Rx-Only port is bidirectional.... unclear what that means. WinMain:2023-01-25T14:31:10.284 KISS Rx Only[Simply(KISS)] IGating Receive-Only at 1200 baud
WinMain:2023-01-25T14:31:10.284 ***** IGate Enabled Bi-Directional *****
WinMain:2023-01-25T17:24:07.533 Logging Enabled I've attached the settings for KISS Rx Only; IP 127.0.0.1; port 8100  |
|
|
|
Lynn Deffenbaugh
Issue was resolved via APRS messaging. The problem was that
UZ7HO logged a "KISS port is busy" error that was finally cleared
up with a reboot. After that, APRSIS32 started seeing
RF-received packets from the KISS over TCP/IP port to UZ7HO. Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 1/25/2023 12:35 PM, Jon W7SEA wrote:
Thanks for the specific directions, Lynn. I checked all the things you mentioned, and everything seemed in order. |
|
|
|
Jon W7SEA
Many thanks, Lynn
|
|
|
