开云体育

I promise I didn't touch nothing! One day had a guy call me a tell me my station what spitting out bad call signs. The info seems to be ok with the station just the call sign is bad. Anyone else had/seen this issue before? It looks like when I restart IUView software and it will work fine for a few days then start gating bad calls. I'm not running a digipeater. Help Please!?

Brian,
KJ4TDM

Brian KJ4TDM wrote...

One day had a guy call me a tell me my station was spitting
out bad call signs. The info seems to be OK with the station
just the call sign is bad. Anyone else had/seen this issue
before? It looks like when I restart UI-View software and it
will work fine for a few days then start gating bad calls.
I'm not running a digipeater.

1) What guy called?

2) What "bad call signs" does he say your station is
"spitting out"?

3) Does he mean "gating to RF" or perhaps digipeating?

4) What call sign/SSID is your UI-View station using?

KJ4TDM is a WX station using UI-View. It also appears
to be an iGate. KJ4TDM-8 is your Jeep. KJ4TDM-1 is a
balloon with an Internet connection. KJ4TDM-5 was a
D74 but appears to be using APRSdroid. KJ4TDM-2 is a
TT4 digipeater in a warm location. KJ4TDM-7 is a D74.

The logical answer to question #3 is that you are
running an iGate or a digi, but you said that you
were not running a digi. KJ4TDM-2 says that it is
a digi, but it is a TT4 and not using UI-View. Looking
at some nearby stations, some were digi'd by KJ4TDM-2.
I don't believe the TT4 has a "passall" setting, but I
suppose if it was swamped with RF, strange things could
happen, but not to just the call signs.

Tell us about KJ4TDM-1. Exactly what is it doing? Is
KJ4TDM in fact an iGate? If so, what is it gating to RF?

--
73 Keith VE7GDH
"I may be lost, but I know exactly where I am!"

I like when people ask questions I can answer!
1. A fellow ham friend the lives about 5 miles from me, N4XWC.
2. Example of one from today: PK4EJ-1 should be AK4EJ-1. (Look these 2 up.)
3.I have my APRS server setup to gate "RF to Internet" only, all 3 boxes. No boxes checked under "Internet to RF"
4. KJ4TDM

You are correct in your description of all 6 of my SSID's. I am not running a digipeater on the KJ4TDM station. KJ4TDM-1 is a weather balloon that I track every Saturday. You can find out more about it here: . It is not tied to the KJ4TDM system at all, I run it on separate system.
KJ4TDM has been an iGate for a little while until this started happening. I turned that feature off a few weeks ago. I just now getting to set down with it and study the issue. I think I answered your last question with number 3.

Thanks,
Brian KJ4TDM

On 11/13/2016 2:30 PM, kj4tdm@... [ui-view] wrote:

I promise I didn't touch nothing! One day had a guy call me a tell me my station what spitting out bad call signs. The info seems to be ok with the station just the call sign is bad. Anyone else had/seen this issue before? It looks like when I restart IUView software and it will work fine for a few days then start gating bad calls. I'm not running a digipeater. Help Please!?

Brian,
KJ4TDM







------------------------------------
Posted by: kj4tdm@...
------------------------------------

I had a similar problem with one of my own mobile calls. Turned out to be my KPC3 needed to be rebooted every few days.
Mike KA6IYS

Mike KA6IYS wrote...

I had a similar problem with one of my own mobile calls.
Turned out to be my KPC3 needed to be rebooted every few days

Are you sure you aren't referring to the KPC3+ introducing
delays after running for a few days? This would not be the
same issue as receiving garbled packets like when PASSALL
is turned on.

--
73 Keith VE7GDH
"I may be lost, but I know exactly where I am!"

I have tried another TNC, not fix. I was hoping that's all it was. I am using a KPC3 btw.

I have tried another TNC, not fix. I was hoping that's all it was. I am using a KPC3 btw.

Is PASSALL on? If so, it could let bad packets through.

Do you have a long serial cable? My HF used to corrupt packets when I
had the TNC and computer in different rooms.

Bill

PASSALL, is that a command in the TNC? I will check that tomorrow. thanks
Brian, kj4tdm
On Sun, Nov 13, 2016 at 9:17 PM, Bill Vodall wa7nwp@... [ui-view]<ui-view@...> wrote: ?

I have tried another TNC, not fix. I was hoping that's all it was. I am using a KPC3 btw.

Is PASSALL on? If so, it could let bad packets through.

Do you have a long serial cable? My HF used to corrupt packets when I
had the TNC and computer in different rooms.

Bill




[Non-text portions of this message have been removed]

Brian KJ4TDM wrote...

PASSALL, is that a command in the TNC? I will check
that tomorrow.

Having PASSALL on would give you all kinds of corrupted
received beacons. It wouldn't affect anything that you
transmitted though.

I'll respond to your earlier message after supper, but
did N4XWC mean that he was seeing "bad call signs" on RF
or that he was looking online at stations gated by you?

--
73 Keith VE7GDH
"I may be lost, but I know exactly where I am!"

CABLE: Not only long, but NOT shielded!



We shielded our cable from stray RF and it solved this problem. The longer it is, the more STUFF it brings in!



Kevin

KD7DFV



From: ui-view@... [mailto:ui-view@...]
Sent: Sunday, November 13, 2016 8:30 PM
To: ui-view@...
Subject: Re: [UI-View] Bad call signs being iGated





PASSALL, is that a command in the TNC? I will check that tomorrow. thanks
Brian, kj4tdm
On Sun, Nov 13, 2016 at 9:17 PM, Bill Vodall wa7nwp@... [ui-view]<ui-view@...> wrote:

I have tried another TNC, not fix. I was hoping that's all it was. I am using a KPC3 btw.

Is PASSALL on? If so, it could let bad packets through.

Do you have a long serial cable? My HF used to corrupt packets when I
had the TNC and computer in different rooms.

Bill

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]

Brian KJ4TDM wrote...

1. A fellow ham friend the lives about 5 miles from me, N4XWC.

Did he happen to say if he saw you gating "bad call signs"
out to RF or if he thought you were gating them towards
the APRS-IS?

2. Example of one from today: PK4EJ-1 should be AK4EJ-1.
(Look these 2 up.)

2016-11-13 13:45:36 PST:
PK4EJ-1>S3TU1W,WB4GNA-7,WIDE1,K4TQR-1,WIDE2*,qAR,KJ4TDM:
'qLUl <0x1c>#/"6Q}/TinyTrak4 Alpha!w!!!

You gated it, but there isn't any way of telling it if
the digis WB4GNA-7 or K4TQR-1 introduced the error or
your KJ4TDM iGate.

3.I have my APRS server setup to gate "RF to Internet"
only, all 3 boxes. No boxes checked under "Internet to RF"

Actually, "RF to Internet" only is not a good thing. If
your iGate isn't bi-directional, messages destined to
mobile stations around you will fail. This doesn't mean
that you have to gate everything to the Internet that
you get from the APRS-IS. Go into FILE - EDIT IGATE.INI
and decide what path to use to RF. It could be a one-hop
WIDE2-1 or possibly more, but usually not more than two
hops. The chance of success goes down with more hops,
and it also starts to QRM stations a few hops away from
you too. Decide how many hops away a station can be and
still be considered local. I have mine set to zero... in
other words, I don't consider a station local unless I
can hear it direct. I think zero is the right setting for
my location. Location, terrain/geography and the number
of digis and iGates around would help determine if you
should consider stations further away to be local. Do
enable "show Internet entry point callsign". Do not gate
LAN to Internet unless you have another APRS client
connected over the LAN to your iGate, and only if you
need to gate traffic from that other APRS client. Do
NOT enable "gate all RF to Internet". You only want to
gate UI frames. Hopefully there isn't any connected
packet going around you, but not checking that box would
prevent you from gating it. You only want to gate APRS
traffic.

Then on the APRS server setup. You mentioned having
having OPEN THE GATEWAY, GATE OBJECTS and INSERT STATION
CALL SIGN enabled. That's good. On to the bad. You
said that you didn't have anything enabled under
GATE INTERNET TO RF. You do want to gate local messages.
It would be considered normal to transmit IGATE status.
It will tell anyone looking at your iGate how much
traffic you are gating. Nice to know, but not mandatory.

If you gate a message to a "local station" it will
be followed by a position report from the sender. That
way the recipient of the message has a chance to see
where the sender was located.

Garbled call signs (or payloads) is another matter. If
it isn't a TNC set with PASSALL enabled, the explanation
of RF getting into a serial cable is a reasonable one.
Hopefully you can track down whether the problem is with
a nearby digi ore in your own station.

Is AK4-1 a valid callsign or alias? It hasn't been
heard since Oct 19. You could watch your screen for
a while and if you see any bogus call signs, double
click on them to open up the station information so
you can see the path by which it was heard. If you
heard it direct, your station might be responsible.
If any digis were involved, they could be possible
culprits too. If the problem "goes away" then that is
that. If it is happening often, it would be nice to
track it down.

--
73 Keith VE7GDH

Ok, got a lot of questions and info in the past few emails. I try to answer them the best I can.
1. RF in the cable - possible, I'll move the cable around and do something with it....
2. I checks PASSALL, it is off.
3. I'm not transmitting any HF.
4. When n4xwc called me about it we looked at it together. All the bad call signs were gated from me. They all did not take the same path to me. The only thing common with them was i gated them to the internet.
5. I went back and marked ALL the boxes under GATE RF TO INTERNET & GATE INTERNET TO RF.
6. I have never changed anything in IGATE.ini. So what i have done there is
PORT(S) 1
PATH(S) WIDE2-1
everything else is set to default under the rest of the tabs.
7. AK4-1 is not a valid call.

As I set here and type this email I'm letting in RF mode only, not connected to the internet. I'm receiving 19 station all call signs look good. I'm going to connect to the internet to start the iGate in a minute and see what happens.

Brian, KJ4TDM

Brian KJ4TDM wrote...

I have tried another TNC, not fix. I was hoping that's
all it was. I am using a KPC3 btw.

If you watch the terminal window, do you see any errors
in the call signs there? You could set OPTIONS - FILTER
to EXCLUDE INTERNET traffic so you were viewing packets
from RF only.

--
73 Keith VE7GDH
"I may be lost, but I know exactly where I am!"

I got everything running right now. I'm waiting for it to start messing up, hopefully it wont. When/if it does I will do what you have suggested.
Brian

Well since the last time we spoke about this issue i have had no more problems. I didn't really do anything but moved the PTT cable that goes from the radio to the TNC, whatever works! If it starts happening again I'll pay more attention to what its receiving vs what its gating. Thanks again for the suggestions.
?
Brian
KJ4TDM

From: "Keith VE7GDH ve7gdh@... [ui-view]" <ui-view@...>
To: ui-view@...
Sent: Tuesday, November 15, 2016 8:25 AM
Subject: Re: [UI-View] Bad call signs being iGated

? Brian KJ4TDM wrote...

I have tried another TNC, not fix. I was hoping that's

> all it was. I am using a KPC3 btw.

If you watch the terminal window, do you see any errors
in the call signs there? You could set OPTIONS - FILTER
to EXCLUDE INTERNET traffic so you were viewing packets
from RF only.

--
73 Keith VE7GDH
"I may be lost, but I know exactly where I am!"

#yiv2262757929 #yiv2262757929 -- #yiv2262757929ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv2262757929 #yiv2262757929ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv2262757929 #yiv2262757929ygrp-mkp #yiv2262757929hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv2262757929 #yiv2262757929ygrp-mkp #yiv2262757929ads {margin-bottom:10px;}#yiv2262757929 #yiv2262757929ygrp-mkp .yiv2262757929ad {padding:0 0;}#yiv2262757929 #yiv2262757929ygrp-mkp .yiv2262757929ad p {margin:0;}#yiv2262757929 #yiv2262757929ygrp-mkp .yiv2262757929ad a {color:#0000ff;text-decoration:none;}#yiv2262757929 #yiv2262757929ygrp-sponsor #yiv2262757929ygrp-lc {font-family:Arial;}#yiv2262757929 #yiv2262757929ygrp-sponsor #yiv2262757929ygrp-lc #yiv2262757929hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv2262757929 #yiv2262757929ygrp-sponsor #yiv2262757929ygrp-lc .yiv2262757929ad {margin-bottom:10px;padding:0 0;}#yiv2262757929 #yiv2262757929actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv2262757929 #yiv2262757929activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv2262757929 #yiv2262757929activity span {font-weight:700;}#yiv2262757929 #yiv2262757929activity span:first-child {text-transform:uppercase;}#yiv2262757929 #yiv2262757929activity span a {color:#5085b6;text-decoration:none;}#yiv2262757929 #yiv2262757929activity span span {color:#ff7900;}#yiv2262757929 #yiv2262757929activity span .yiv2262757929underline {text-decoration:underline;}#yiv2262757929 .yiv2262757929attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv2262757929 .yiv2262757929attach div a {text-decoration:none;}#yiv2262757929 .yiv2262757929attach img {border:none;padding-right:5px;}#yiv2262757929 .yiv2262757929attach label {display:block;margin-bottom:5px;}#yiv2262757929 .yiv2262757929attach label a {text-decoration:none;}#yiv2262757929 blockquote {margin:0 0 0 4px;}#yiv2262757929 .yiv2262757929bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv2262757929 .yiv2262757929bold a {text-decoration:none;}#yiv2262757929 dd.yiv2262757929last p a {font-family:Verdana;font-weight:700;}#yiv2262757929 dd.yiv2262757929last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv2262757929 dd.yiv2262757929last p span.yiv2262757929yshortcuts {margin-right:0;}#yiv2262757929 div.yiv2262757929attach-table div div a {text-decoration:none;}#yiv2262757929 div.yiv2262757929attach-table {width:400px;}#yiv2262757929 div.yiv2262757929file-title a, #yiv2262757929 div.yiv2262757929file-title a:active, #yiv2262757929 div.yiv2262757929file-title a:hover, #yiv2262757929 div.yiv2262757929file-title a:visited {text-decoration:none;}#yiv2262757929 div.yiv2262757929photo-title a, #yiv2262757929 div.yiv2262757929photo-title a:active, #yiv2262757929 div.yiv2262757929photo-title a:hover, #yiv2262757929 div.yiv2262757929photo-title a:visited {text-decoration:none;}#yiv2262757929 div#yiv2262757929ygrp-mlmsg #yiv2262757929ygrp-msg p a span.yiv2262757929yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv2262757929 .yiv2262757929green {color:#628c2a;}#yiv2262757929 .yiv2262757929MsoNormal {margin:0 0 0 0;}#yiv2262757929 o {font-size:0;}#yiv2262757929 #yiv2262757929photos div {float:left;width:72px;}#yiv2262757929 #yiv2262757929photos div div {border:1px solid #666666;height:62px;overflow:hidden;width:62px;}#yiv2262757929 #yiv2262757929photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv2262757929 #yiv2262757929reco-category {font-size:77%;}#yiv2262757929 #yiv2262757929reco-desc {font-size:77%;}#yiv2262757929 .yiv2262757929replbq {margin:4px;}#yiv2262757929 #yiv2262757929ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv2262757929 #yiv2262757929ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv2262757929 #yiv2262757929ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv2262757929 #yiv2262757929ygrp-mlmsg select, #yiv2262757929 input, #yiv2262757929 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv2262757929 #yiv2262757929ygrp-mlmsg pre, #yiv2262757929 code {font:115% monospace;}#yiv2262757929 #yiv2262757929ygrp-mlmsg * {line-height:1.22em;}#yiv2262757929 #yiv2262757929ygrp-mlmsg #yiv2262757929logo {padding-bottom:10px;}#yiv2262757929 #yiv2262757929ygrp-msg p a {font-family:Verdana;}#yiv2262757929 #yiv2262757929ygrp-msg p#yiv2262757929attach-count span {color:#1E66AE;font-weight:700;}#yiv2262757929 #yiv2262757929ygrp-reco #yiv2262757929reco-head {color:#ff7900;font-weight:700;}#yiv2262757929 #yiv2262757929ygrp-reco {margin-bottom:20px;padding:0px;}#yiv2262757929 #yiv2262757929ygrp-sponsor #yiv2262757929ov li a {font-size:130%;text-decoration:none;}#yiv2262757929 #yiv2262757929ygrp-sponsor #yiv2262757929ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv2262757929 #yiv2262757929ygrp-sponsor #yiv2262757929ov ul {margin:0;padding:0 0 0 8px;}#yiv2262757929 #yiv2262757929ygrp-text {font-family:Georgia;}#yiv2262757929 #yiv2262757929ygrp-text p {margin:0 0 1em 0;}#yiv2262757929 #yiv2262757929ygrp-text tt {font-size:120%;}#yiv2262757929 #yiv2262757929ygrp-vital ul li:last-child {border-right:none !important;}#yiv2262757929

Brian KJ4TDM wrote…

I didn't really do anything but moved the PTT cable that goes from the radio to the TNC…

Just a guess, but perhaps RF was being picked up by the cable between the radio and the TNC and corrupting the data stream somewhere after error detection is done.

--
73 Keith VE7GDH
"I may be lost, but I know exactly where I am!"

Here is an issue I had with bad packets with bad call signs and wx data
Chuck
Chuck,







Just FYI, I reported the issue to the manufacturer, and they released a firmware fix. My iGate is up again, and so far (after two hours), I don't see any corrupt packets.







I'll be monitoring on findu.com, but if you notice anything weird or bad, please let me know.







My apologies once again for all the previous bad packets.







(last 24 hours)







73,



/ John 858-449-3326