Ok, with some sleuthing through aprs.fi, I've established: K7RBW - UI-View via TCP, and not very recently K7RBW-1 - APRSIS32 running a non-verified connection to APRS-IS (you need a passcode) K7RBW-7 - APY008 implies the VX-8R K7RBW-9 - AP0T21 implies the T2 K7RBW-14 - APT3A2 must be the AOI?
So, did you get a popup from APRSIS32 about having an unverified connection? You need to e-mail me at [email protected] and I'll give you one. Or just copy the network password from your old UI-View installation if it's still around. That will solve the IGating issue. If you edit your APRSIS32.XML file (http://aprsisce.wikidot.com/editing-xml-configuration) and set <Update.Development> to 1, the About box will offer you a new version. In that version, you can open up the Enables / View Logs / KISS to see whats coming and going via the KISS Interface. Enables / View Logs / Packets will show you all RF and IS packets running through the client. This can help you verify what the T2 is and is not decoding relative to what you see on AGW and/or the VX-8R. Even without upgrading to the latest development release, the scrolling station log in APRSIS32 should show you each packet received via KISS with a * next to it. If you configure your Range to be 0 and leave out any other filter string, you should only see traffic coming in via RF. (Note that you might have to disable and enable APRS-IS to get the previous filter completely cleared). In my experience, there's no comparison to the decoding abilities of AGWPEpro. I've held it up against D7s, TinyTrak4, T2-135s, and OT2m and AGW consistently decodes every packet from those TNCs and throws in several more for good measure. Hardware, it seems, just can't rival the power of a software decoder. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 PS. To download your own free copy of APRSIS32, join the APRSISCE Yahoo Group at: http://groups.yahoo.com/group/APRSISCE/ k7rbw wrote: > I was working with my Tracker2 last night and noticed that it wouldn't > digipeat one of my beacons so I was wondering how I might go about > troubleshooting it. > > Here's what I have: > > 1) Kenwood mobile rig connected to a late model T2 w/ Nuvi 350 (port b) -- > this seems to work fine. > 2) (port a) is running in KISS mode to APRSISCE/32 which also seems to be > working fine (but it's not gating packets to the internet, it seems to just > be receiving them). > 3) FT-857 hooked up to monitor the RF traffic using a Signalink USB audio box > into AGWPE and the AGW terminal > > 4) Beacon 1 - VX-8R. These packets get digipeated by #1 as expected. I see > the beacon's message followed immediately by the digipeated packet with #1's > call inserted. > > 5) Beacon 2 - Byonics AIO beacon. These packets get digipeated intermitently. > Maybe 1/10 of the time but not with any obvious pattern. I see them on the > FT-857's terminal and the VX-8R is picking them up as well. > > So, I'm wondering if the T2 isn't decoding the AIO's packets all the time > (even though the other radios are) and if not, is there some way to tell > and/or adjust that? > > A "silver bullet" would be nice, but absent that, if there was some way see > where things were disappearing, that'd be a big help, too. > > Thanks in advance for any ideas. > > --bob > K7RBW (-1, -7, -9, & -14) >
