I was attempting to re organize the garage today and came across a virtually
brand new convertacom unit model number n1244a. For those of you that have never
heard of these units, they are docking station for older Motorola hand handhelds
(I believe this ones for a MX300) when the radio is in the dock it receives
power from the dock and the transmitted signal goes into a 40w amplifier.

Has any one had any experience using the amplifier out of and old Motorola
convertacom for packet? I was thinking that this amplifier might work well with
a T2-301 for a mobile tracker.


Sean, VE6SAR

Teddy,
It looks like you were set up as an Igate using UIView. If you were
setup using KISS mode, the KPC-3 should have most setting turned off.
UIview controls most all of the settings. I think this is where the
problem was. Your station isn't showing up now.
http://aprs.fi/info/KC0WNY-1

If you haven't already done so,  go to UIview "station setup" set
unproto path to "APRS" get rid of the "WIDE-1".

If you have broadband, and want to leave uiview running all the time,
you could serve your area well setup as an RX only Igate. You were setup
already, and gating traffic.

Just be sure to set UIview "RXonly" on the Comms setup screen, and on
the APRS server setup screen uncheck all three "Gate Internet to RF".
settings.  Once you run it for a while, and are comfortable with your
settings, then you might consider allowing local messages to gate
internet to RF.  You have to be careful and understand these setting the
most. If "Gate Internet to RF" is setup wrong you could potentially
bring your area's network to it's knees. RX only is pretty safe.


   I have attached a link that describes how to setup a fillin digi.
however, I recommend you give up the digi idea, and stick to Igate since
it looks like your station was gating traffic.

http://www.cordeoc.ca/EOC-images3/UI-view32-NewParadigm%20Digi%20Setting\
s%20Feb06.pdf

Alan

--- In tracker2@yahoogroups.com, "Teddy Banks" <tbanks204@...> wrote:
>
> I made some changes to my setup based on the link, we will see if it
helped.
> Thanks
> ----- Original Message -----
> From: "Teddy Banks" tbanks204@...
> To: tracker2@yahoogroups.com
> Sent: Saturday, November 21, 2009 7:43 PM
> Subject: Re: [tracker2] T2 and Nuvi 350
>
>
> Keith, I appreciate your patience, and your hand holding, I have
problems
> understanding the concepts of APRS and I may never fully understand
it. .
> ----- Original Message -----
> From: "Keith VE7GDH" ve7gdh@...
> To: tracker2@yahoogroups.com
> Sent: Friday, November 20, 2009 9:20 PM
> Subject: Re: [tracker2] T2 and Nuvi 350
>

Hi,

My OT2 started sending weather reports immediately after each position report.

There is no NMEA mode in the Config utility, only an AUTO mode for NMEA GPSes so
I suppose the OT2 got confused at some point and set itself in weather mode when
it got unexpected bits from the GPS.
Or was that excess sunspot activity and a burst of X-ray hit the wrong bit in
the OT2.

The GPS is a Globalsat BR-355 puck with SiRF chipset.  A script initializes some
settings in binary mode at startup, then reverts it to NMEA.  It's possible the
GPS outputs binary during that initialization phase.

I'll try a reset, but I am worried this may happen again when I am not there to
look after it.

Bernard KI6TSF

Forgot to add the traces.  Those WX messages look weird.

2009-11-22 05:57:35 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C GPS
drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
  2009-11-22 06:17:39 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.5V 14C GPS
drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
  2009-11-22 06:17:39 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_126/850g65428t-87\
3P48059h26b57238T2WX
  2009-11-22 06:27:40 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C GPS
drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
  2009-11-22 06:27:41 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64153g63849t-\
376P31093h67b48059T2WX
  2009-11-22 06:37:42 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C GPS
drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
  2009-11-22 06:37:43 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_428/246g63849t216\
7P62832h39b39321T2WX
  2009-11-22 06:39:12 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C GPS
drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
  2009-11-22 06:49:13 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C GPS
drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
  2009-11-22 06:49:14 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64153g1354t60\
0P39321h15b61165T2WX
  2009-11-22 06:59:15 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C GPS
drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
  2009-11-22 07:09:16 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C GPS
drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
  2009-11-22 07:19:18 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C GPS
drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
  2009-11-22 07:29:19 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C GPS
drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
  2009-11-22 07:29:19 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64169g1354t-1\
919P6508h94b65535T2WX
  2009-11-22 07:39:20 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C GPS
drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
  2009-11-22 07:49:22 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64153g1354t-1\
871P39321h46b56797T2WX
  2009-11-22 07:59:24 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63850g1354t-2\
621P13271h50b28398T2WX
  2009-11-22 08:09:25 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C GPS
drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
  2009-11-22 08:19:26 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C GPS
drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
  2009-11-22 08:19:27 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63897g1354t46\
6P6547h95b30582T2WX
  2009-11-22 08:29:28 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.3V 14C GPS
drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
  2009-11-22 08:29:29 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63897g1354t11\
14P39276h95b13105T2WX
  2009-11-22 08:39:30 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C GPS
drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
  2009-11-22 08:39:31 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63897g1354t21\
86P35184h15b39321T2WX


--- In tracker2@yahoogroups.com, "ki6tsf" <ki6tsf@...> wrote:
>
> Hi,
>
> My OT2 started sending weather reports immediately after each position report.
>
> There is no NMEA mode in the Config utility, only an AUTO mode for NMEA GPSes
so I suppose the OT2 got confused at some point and set itself in weather mode
when it got unexpected bits from the GPS.
> Or was that excess sunspot activity and a burst of X-ray hit the wrong bit in
the OT2.
>
> The GPS is a Globalsat BR-355 puck with SiRF chipset.  A script initializes
some settings in binary mode at startup, then reverts it to NMEA.  It's possible
the GPS outputs binary during that initialization phase.
>
> I'll try a reset, but I am worried this may happen again when I am not there
to look after it.
>
> Bernard KI6TSF
>

----- Original Message -----

From: Alan

To: tracker2@yahoogroups.com

Sent: Sunday, November 22, 2009 2:56 AM

Subject: [tracker2] Re: T2 and Nuvi 350

 

Teddy,
It looks like you were set up as an Igate using UIView. If you were
setup using KISS mode, the KPC-3 should have most setting turned off.
UIview controls most all of the settings. I think this is where the
problem was. Your station isn't showing up now.
http://aprs.fi/info/KC0WNY-1

If you haven't already done so, go to UIview "station setup" set
unproto path to "APRS" get rid of the "WIDE-1".

If you have broadband, and want to leave uiview running all the time,
you could serve your area well setup as an RX only Igate. You were setup
already, and gating traffic.

Just be sure to set UIview "RXonly" on the Comms setup screen, and on
the APRS server setup screen uncheck all three "Gate Internet to RF".
settings. Once you run it for a while, and are comfortable with your
settings, then you might consider allowing local messages to gate
internet to RF. You have to be careful and understand these setting the
most. If "Gate Internet to RF" is setup wrong you could potentially
bring your area's network to it's knees. RX only is pretty safe.

I have attached a link that describes how to setup a fillin digi.
however, I recommend you give up the digi idea, and stick to Igate since
it looks like your station was gating traffic.

http://www.cordeoc.ca/EOC-images3/UI-view32-NewParadigm%20Digi%20Setting\
s%20Feb06.pdf

Alan

--- In tracker2@yahoogroups.com, "Teddy Banks" <tbanks204@...> wrote:
>
> I made some changes to my setup based on the link, we will see if it
helped.
> Thanks
> ----- Original Message -----
> From: "Teddy Banks" tbanks204@...
> To: tracker2@yahoogroups.com
> Sent: Saturday, November 21, 2009 7:43 PM
> Subject: Re: [tracker2] T2 and Nuvi 350
>
>
> Keith, I appreciate your patience, and your hand holding, I have
problems
> understanding the concepts of APRS and I may never fully understand
it. .
> ----- Original Message -----
> From: "Keith VE7GDH" ve7gdh@...
> To: tracker2@yahoogroups.com
> Sent: Friday, November 20, 2009 9:20 PM
> Subject: Re: [tracker2] T2 and Nuvi 350
>

----- Original Message -----

From: Teddy Banks

To: tracker2@yahoogroups.com

Sent: Sunday, November 22, 2009 2:19 PM

Subject: Re: [tracker2] Re: T2 and Nuvi 350

 

ok, here is the deal, I run UI-View but not very often and I have the digi option turned off at the present time, I am approx 40 to 50 miles I would guess, from another Aprs base station, I use teraterm pro to monitor incoming traffic from the KPC3+ and a Alinco DR-135 and am using a ground plane antenna at about 30 ft, running med power and it appears to be tranmitting, I can hear it on another radio, I can see references to my station KC0WNY-1 on it, and up until a few days ago, I could see my station on the internet tracking  apps Aprs.fi, Findu.com, etc , but when I check now, no new info. at the present time I have the Digi option turned off. I can't figure out what changed at my location. Perhaps I should get my other Alinco with the T2, and connect it to my base antenna. Thanks

----- Original Message -----

From: Alan

To: tracker2@yahoogroups.com

Sent: Sunday, November 22, 2009 2:56 AM

Subject: [tracker2] Re: T2 and Nuvi 350

 

Teddy,
It looks like you were set up as an Igate using UIView. If you were
setup using KISS mode, the KPC-3 should have most setting turned off.
UIview controls most all of the settings. I think this is where the
problem was. Your station isn't showing up now.
http://aprs.fi/info/KC0WNY-1

If you haven't already done so, go to UIview "station setup" set
unproto path to "APRS" get rid of the "WIDE-1".

If you have broadband, and want to leave uiview running all the time,
you could serve your area well setup as an RX only Igate. You were setup
already, and gating traffic.

Just be sure to set UIview "RXonly" on the Comms setup screen, and on
the APRS server setup screen uncheck all three "Gate Internet to RF".
settings. Once you run it for a while, and are comfortable with your
settings, then you might consider allowing local messages to gate
internet to RF. You have to be careful and understand these setting the
most. If "Gate Internet to RF" is setup wrong you could potentially
bring your area's network to it's knees. RX only is pretty safe.

I have attached a link that describes how to setup a fillin digi.
however, I recommend you give up the digi idea, and stick to Igate since
it looks like your station was gating traffic.

http://www.cordeoc.ca/EOC-images3/UI-view32-NewParadigm%20Digi%20Setting\
s%20Feb06.pdf

Alan

--- In tracker2@yahoogroups.com, "Teddy Banks" <tbanks204@...> wrote:
>
> I made some changes to my setup based on the link, we will see if it
helped.
> Thanks
> ----- Original Message -----
> From: "Teddy Banks" tbanks204@...
> To: tracker2@yahoogroups.com
> Sent: Saturday, November 21, 2009 7:43 PM
> Subject: Re: [tracker2] T2 and Nuvi 350
>
>
> Keith, I appreciate your patience, and your hand holding, I have
problems
> understanding the concepts of APRS and I may never fully understand
it. .
> ----- Original Message -----
> From: "Keith VE7GDH" ve7gdh@...
> To: tracker2@yahoogroups.com
> Sent: Friday, November 20, 2009 9:20 PM
> Subject: Re: [tracker2] T2 and Nuvi 350
>

---

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.425 / Virus Database: 270.14.76/2519 - Release Date: 11/22/09 07:38:00

No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.5.425 / Virus Database: 270.14.76/2519 - Release Date: 11/22/09
07:38:00

In case anyone is looking for a refurb 350.

http://www.ecost.com/Detail.aspx?edp=52715227&navid=155441519

Yup,
What Rudy said is true.

From the limited stats I can see from your station, it has only reported
via your UIview to APRS-IS through your connection to APRS-IS, when you
had it Igateing traffic.
Your RF isn't being decoded.
So  listen to your TX with a receiver. Use the CAL command to put it in
TX.  Listen, is it too soft, too loud? Adjust TX deviation using the CAL
command (+ -). If XMITLVL is set at default 100, that's your problem.
The last Alinco I looked at needed an XMITLVL of around 265 to achieve a
dev of 3.0Khz. The default of 100 was sub-audible (.8Khz).

If that doesn't bring you joy, then look at your TX delay. 30 is the
stupid 1993 default setting of 300ms. Set it to around 15 (150ms)

Here is the manual, you might want to study it,
http://www.kantronics.com/documents/kpc-3plus_manual_RevD.pdf

Since you don't want to run an Igate (usually the best help to an area).
Set it up as a Fillin digi. That will forward real traffic, not old
stale crap from your nearby Digi "appliance user" he is running several
of his Digi's and a WX station running "WIDE".  (What's wrong with
Kansas?)

Please look at your States Coordinator for help with local settings,
here is a link that might bring you valuable  local info.
http://skynet.entz.net/webpages/shorty/kcaprs/ (It is a few years old
but probably good info)

The page has is a list of  "Elmers" in Kansas that are willing to help
you out.

The folling will show you how to setup a KPC-3+ as a stand alone Fillin
digi,  http://www.aprs.org/newN/WIDE1-1settings.txt

Good luck, hope this helps.

Alan:-)


Old stuff below:
--- In tracker2@yahoogroups.com, "Rudy Benner" <benner@...> wrote:
>
>
> What do you have under STATION SETUP - UNPROTO ADDRESS ?
>
> Something like APRS,WIDE1-1 is expected. The APRS is required, its
your DESTINATION, everything after that is the path.
>
>   ----- Original Message -----
>   From: Teddy Banks
>   To: tracker2@yahoogroups.com
>   Sent: Sunday, November 22, 2009 2:19 PM
>   Subject: Re: [tracker2] Re: T2 and Nuvi 350
>
>
>
>
>   ok, here is the deal, I run UI-View but not very often and I have
the digi option turned off at the present time, I am approx 40 to 50
miles I would guess, from another Aprs base station, I use teraterm pro
to monitor incoming traffic from the KPC3+ and a Alinco DR-135 and am
using a ground plane antenna at about 30 ft, running med power and it
appears to be tranmitting, I can hear it on another radio, I can see
references to my station KC0WNY-1 on it, and up until a few days ago, I
could see my station on the internet tracking  apps Aprs.fi, Findu.com,
etc , but when I check now, no new info. at the present time I have the
Digi option turned off. I can't figure out what changed at my location.
Perhaps I should get my other Alinco with the T2, and connect it to my
base antenna. Thanks
>     ----- Original Message -----
>     From: Alan
>     To: tracker2@yahoogroups.com
>     Sent: Sunday, November 22, 2009 2:56 AM
>     Subject: [tracker2] Re: T2 and Nuvi 350
>
>
>
>     Teddy,
>     It looks like you were set up as an Igate using UIView. If you
were
>     setup using KISS mode, the KPC-3 should have most setting turned
off.
>     UIview controls most all of the settings. I think this is where
the
>     problem was. Your station isn't showing up now.
>     http://aprs.fi/info/KC0WNY-1
>
>     If you haven't already done so, go to UIview "station setup" set
>     unproto path to "APRS" get rid of the "WIDE-1".
>
>     If you have broadband, and want to leave uiview running all the
time,
>     you could serve your area well setup as an RX only Igate. You were
setup
>     already, and gating traffic.
>
>     Just be sure to set UIview "RXonly" on the Comms setup screen, and
on
>     the APRS server setup screen uncheck all three "Gate Internet to
RF".
>     settings. Once you run it for a while, and are comfortable with
your
>     settings, then you might consider allowing local messages to gate
>     internet to RF. You have to be careful and understand these
setting the
>     most. If "Gate Internet to RF" is setup wrong you could
potentially
>     bring your area's network to it's knees. RX only is pretty safe.
>
>     I have attached a link that describes how to setup a fillin digi.
>     however, I recommend you give up the digi idea, and stick to Igate
since
>     it looks like your station was gating traffic.
>
>
http://www.cordeoc.ca/EOC-images3/UI-view32-NewParadigm%20Digi%20Setting\
\
>     s%20Feb06.pdf
>
>     Alan
>
>     --- In tracker2@yahoogroups.com, "Teddy Banks" tbanks204@ wrote:
>     >
>     > I made some changes to my setup based on the link, we will see
if it
>     helped.
>     > Thanks
>     > ----- Original Message -----
>     > From: "Teddy Banks" tbanks204@
>     > To: tracker2@yahoogroups.com
>     > Sent: Saturday, November 21, 2009 7:43 PM
>     > Subject: Re: [tracker2] T2 and Nuvi 350
>     >
>     >
>     > Keith, I appreciate your patience, and your hand holding, I have
>     problems
>     > understanding the concepts of APRS and I may never fully
understand
>     it. .
>     > ----- Original Message -----
>     > From: "Keith VE7GDH" ve7gdh@
>     > To: tracker2@yahoogroups.com
>     > Sent: Friday, November 20, 2009 9:20 PM
>     > Subject: Re: [tracker2] T2 and Nuvi 350
>     >
>
>
>
>
>
>
>
>
------------------------------------------------------------------------\
------
>
>
>
>   No virus found in this incoming message.
>   Checked by AVG - www.avg.com
>   Version: 8.5.425 / Virus Database: 270.14.76/2519 - Release Date:
11/22/09 07:38:00
>
>
> No virus found in this outgoing message.
> Checked by AVG - www.avg.com
> Version: 8.5.425 / Virus Database: 270.14.76/2519 - Release Date:
11/22/09 07:38:00
>

After reviewing the documentation here is what I've come up with for a cable to
connect my radio (Yaesu FT-7800) Data Jack to the OT2m "Radio" connector.  Any
feedback would be greatly appreciated especially if you already have a OT2m
working with a FT-7800 or FT-8800.

OT2m pin 1 Audio out to FT-7800 pin 1 Packet Data Input
OT2m pin 2 no connection
OT2m pin 3 PTT out to FT-7800 pin 3 PTT (Gnd to xmit)
OT2m pin 4 no connection
OT2m pin 5 Audio in to FT-7800 pin 5 1200 bps Packet Data Output
OT2m pin 6 Ground to FT-7800 pin 2 Signal Ground
OT2m pin 7 no connection
OT2m pin 8 no connection

Thanks in advance,
Tim
KB4PZO

Tim,

Wiring looks good. Just make sure you do not have the HT jumper set inside the
OT2.

Larry
K7YBZ

--- In tracker2@yahoogroups.com, "kb4pzo" <kb4pzo@...> wrote:
>
> After reviewing the documentation here is what I've come up with for a cable
to connect my radio (Yaesu FT-7800) Data Jack to the OT2m "Radio" connector. 
Any feedback would be greatly appreciated especially if you already have a OT2m
working with a FT-7800 or FT-8800.
>
> OT2m pin 1 Audio out to FT-7800 pin 1 Packet Data Input
> OT2m pin 2 no connection
> OT2m pin 3 PTT out to FT-7800 pin 3 PTT (Gnd to xmit)
> OT2m pin 4 no connection
> OT2m pin 5 Audio in to FT-7800 pin 5 1200 bps Packet Data Output
> OT2m pin 6 Ground to FT-7800 pin 2 Signal Ground
> OT2m pin 7 no connection
> OT2m pin 8 no connection
>
> Thanks in advance,
> Tim
> KB4PZO
>

Jeff KT2K wrote...

> In case anyone is looking for a refurb 350.
> www.ecost.com/Detail.aspx?edp=52715227&navid=155441519

Thanks for the tip, but I just tried and got as far as the checkout to
be told they won't ship outside of the US. Too bad... $85 was a pretty
good price! I have 3 so far. One more wouldn't have hurt!

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

----- Original Message -----

From: Alan

To: tracker2@yahoogroups.com

Sent: Sunday, November 22, 2009 2:40 PM

Subject: [tracker2] Re: T2 and Nuvi 350

 

Yup,
What Rudy said is true.

From the limited stats I can see from your station, it has only reported
via your UIview to APRS-IS through your connection to APRS-IS, when you
had it Igateing traffic.
Your RF isn't being decoded.
So listen to your TX with a receiver. Use the CAL command to put it in
TX. Listen, is it too soft, too loud? Adjust TX deviation using the CAL
command (+ -). If XMITLVL is set at default 100, that's your problem.
The last Alinco I looked at needed an XMITLVL of around 265 to achieve a
dev of 3.0Khz. The default of 100 was sub-audible (.8Khz).

If that doesn't bring you joy, then look at your TX delay. 30 is the
stupid 1993 default setting of 300ms. Set it to around 15 (150ms)

Here is the manual, you might want to study it,
http://www.kantronics.com/documents/kpc-3plus_manual_RevD.pdf

Since you don't want to run an Igate (usually the best help to an area).
Set it up as a Fillin digi. That will forward real traffic, not old
stale crap from your nearby Digi "appliance user" he is running several
of his Digi's and a WX station running "WIDE". (What's wrong with
Kansas?)

Please look at your States Coordinator for help with local settings,
here is a link that might bring you valuable local info.
http://skynet.entz.net/webpages/shorty/kcaprs/ (It is a few years old
but probably good info)

The page has is a list of "Elmers" in Kansas that are willing to help
you out.

The folling will show you how to setup a KPC-3+ as a stand alone Fillin
digi, http://www.aprs.org/newN/WIDE1-1settings.txt

Good luck, hope this helps.

Alan:-)

Old stuff below:
--- In tracker2@yahoogroups.com, "Rudy Benner" <benner@...> wrote:
>
>
> What do you have under STATION SETUP - UNPROTO ADDRESS ?
>
> Something like APRS,WIDE1-1 is expected. The APRS is required, its
your DESTINATION, everything after that is the path.
>
> ----- Original Message -----
> From: Teddy Banks
> To: tracker2@yahoogroups.com
> Sent: Sunday, November 22, 2009 2:19 PM
> Subject: Re: [tracker2] Re: T2 and Nuvi 350
>
>
>
>
> ok, here is the deal, I run UI-View but not very often and I have
the digi option turned off at the present time, I am approx 40 to 50
miles I would guess, from another Aprs base station, I use teraterm pro
to monitor incoming traffic from the KPC3+ and a Alinco DR-135 and am
using a ground plane antenna at about 30 ft, running med power and it
appears to be tranmitting, I can hear it on another radio, I can see
references to my station KC0WNY-1 on it, and up until a few days ago, I
could see my station on the internet tracking apps Aprs.fi, Findu.com,
etc , but when I check now, no new info. at the present time I have the
Digi option turned off. I can't figure out what changed at my location.
Perhaps I should get my other Alinco with the T2, and connect it to my
base antenna. Thanks
> ----- Original Message -----
> From: Alan
> To: tracker2@yahoogroups.com
> Sent: Sunday, November 22, 2009 2:56 AM
> Subject: [tracker2] Re: T2 and Nuvi 350
>
>
>
> Teddy,
> It looks like you were set up as an Igate using UIView. If you
were
> setup using KISS mode, the KPC-3 should have most setting turned
off.
> UIview controls most all of the settings. I think this is where
the
> problem was. Your station isn't showing up now.
> http://aprs.fi/info/KC0WNY-1
>
> If you haven't already done so, go to UIview "station setup" set
> unproto path to "APRS" get rid of the "WIDE-1".
>
> If you have broadband, and want to leave uiview running all the
time,
> you could serve your area well setup as an RX only Igate. You were
setup
> already, and gating traffic.
>
> Just be sure to set UIview "RXonly" on the Comms setup screen, and
on
> the APRS server setup screen uncheck all three "Gate Internet to
RF".
> settings. Once you run it for a while, and are comfortable with
your
> settings, then you might consider allowing local messages to gate
> internet to RF. You have to be careful and understand these
setting the
> most. If "Gate Internet to RF" is setup wrong you could
potentially
> bring your area's network to it's knees. RX only is pretty safe.
>
> I have attached a link that describes how to setup a fillin digi.
> however, I recommend you give up the digi idea, and stick to Igate
since
> it looks like your station was gating traffic.
>
>
http://www.cordeoc.ca/EOC-images3/UI-view32-NewParadigm%20Digi%20Setting\
\
> s%20Feb06.pdf
>
> Alan
>
> --- In tracker2@yahoogroups.com, "Teddy Banks" tbanks204@ wrote:
> >
> > I made some changes to my setup based on the link, we will see
if it
> helped.
> > Thanks
> > ----- Original Message -----
> > From: "Teddy Banks" tbanks204@
> > To: tracker2@yahoogroups.com
> > Sent: Saturday, November 21, 2009 7:43 PM
> > Subject: Re: [tracker2] T2 and Nuvi 350
> >
> >
> > Keith, I appreciate your patience, and your hand holding, I have
> problems
> > understanding the concepts of APRS and I may never fully
understand
> it. .
> > ----- Original Message -----
> > From: "Keith VE7GDH" ve7gdh@
> > To: tracker2@yahoogroups.com
> > Sent: Friday, November 20, 2009 9:20 PM
> > Subject: Re: [tracker2] T2 and Nuvi 350
> >
>
>
>
>
>
>
>
>
----------------------------------------------------------\
------
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.425 / Virus Database: 270.14.76/2519 - Release Date:
11/22/09 07:38:00
>
>
> No virus found in this outgoing message.
> Checked by AVG - www.avg.com
> Version: 8.5.425 / Virus Database: 270.14.76/2519 - Release Date:
11/22/09 07:38:00
>

Larry,

Thanks much, always good to have another set of eyes look things over.  Also
noted regarding NOT setting the HT jumper.

Tim

--- In tracker2@yahoogroups.com, "k7ybz" <k7ybz@...> wrote:
>
> Tim,
>
> Wiring looks good. Just make sure you do not have the HT jumper set inside the
OT2.
>
> Larry
> K7YBZ
>
> --- In tracker2@yahoogroups.com, "kb4pzo" <kb4pzo@> wrote:
> >
> > After reviewing the documentation here is what I've come up with for a cable
to connect my radio (Yaesu FT-7800) Data Jack to the OT2m "Radio" connector. 
Any feedback would be greatly appreciated especially if you already have a OT2m
working with a FT-7800 or FT-8800.
> >
> > OT2m pin 1 Audio out to FT-7800 pin 1 Packet Data Input
> > OT2m pin 2 no connection
> > OT2m pin 3 PTT out to FT-7800 pin 3 PTT (Gnd to xmit)
> > OT2m pin 4 no connection
> > OT2m pin 5 Audio in to FT-7800 pin 5 1200 bps Packet Data Output
> > OT2m pin 6 Ground to FT-7800 pin 2 Signal Ground
> > OT2m pin 7 no connection
> > OT2m pin 8 no connection
> >
> > Thanks in advance,
> > Tim
> > KB4PZO
> >
>

Teddy,
That's great!
Glad it did the trick,

Alan :-)


--- In tracker2@yahoogroups.com, "Teddy Banks" <tbanks204@...> wrote:
>
> Thank You Alan, I took a look at the XMITLVL, it was as you stated 100,
> changed it to 300, changed TX DELAY TO 15, I think it worked, I can see my
> station now, I am also reading some to the links you and others have posted,
> hopefully I can get better educated on this APRS stuff.
>   ----- Original Message -----

Yikes.  If possible, could you do a DUMP command and send me the
results?  Without powering the unit down, of course.  I want to see if
it was a random bit flip or if some buffer overflowed and trashed stuff.

I don't know how it'd keep going like that, though.  It's supposed to
clear the weather flag after transmission and only re-set it if it gets
valid weather data.

I'll also need to know the firmware build number.  I've got to remember
to start saving the linker map files for old versions to do this sort of
debugging.

Scott

ki6tsf wrote:
>
>
>
> Forgot to add the traces. Those WX messages look weird.
>
> 2009-11-22 05:57:35 PST:
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> 2009-11-22 06:17:39 PST:
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.5V 14C
> GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> 2009-11-22 06:17:39 PST:
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_126/850g65428t-87\
3P48059h26b57238T2WX
> 2009-11-22 06:27:40 PST:
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> 2009-11-22 06:27:41 PST:
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64153g63849t-\
376P31093h67b48059T2WX
> 2009-11-22 06:37:42 PST:
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> 2009-11-22 06:37:43 PST:
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_428/246g63849t216\
7P62832h39b39321T2WX
> 2009-11-22 06:39:12 PST:
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> 2009-11-22 06:49:13 PST:
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> 2009-11-22 06:49:14 PST:
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64153g1354t60\
0P39321h15b61165T2WX
> 2009-11-22 06:59:15 PST:
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> 2009-11-22 07:09:16 PST:
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> 2009-11-22 07:19:18 PST:
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> 2009-11-22 07:29:19 PST:
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> 2009-11-22 07:29:19 PST:
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64169g1354t-1\
919P6508h94b65535T2WX
> 2009-11-22 07:39:20 PST:
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> 2009-11-22 07:49:22 PST:
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64153g1354t-1\
871P39321h46b56797T2WX
> 2009-11-22 07:59:24 PST:
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63850g1354t-2\
621P13271h50b28398T2WX
> 2009-11-22 08:09:25 PST:
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> 2009-11-22 08:19:26 PST:
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> 2009-11-22 08:19:27 PST:
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63897g1354t46\
6P6547h95b30582T2WX
> 2009-11-22 08:29:28 PST:
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.3V 14C
> GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> 2009-11-22 08:29:29 PST:
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63897g1354t11\
14P39276h95b13105T2WX
> 2009-11-22 08:39:30 PST:
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> 2009-11-22 08:39:31 PST:
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63897g1354t21\
86P35184h15b39321T2WX
>
> --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
> "ki6tsf" <ki6tsf@...> wrote:
>  >
>  > Hi,
>  >
>  > My OT2 started sending weather reports immediately after each
> position report.
>  >
>  > There is no NMEA mode in the Config utility, only an AUTO mode for
> NMEA GPSes so I suppose the OT2 got confused at some point and set
> itself in weather mode when it got unexpected bits from the GPS.
>  > Or was that excess sunspot activity and a burst of X-ray hit the
> wrong bit in the OT2.
>  >
>  > The GPS is a Globalsat BR-355 puck with SiRF chipset. A script
> initializes some settings in binary mode at startup, then reverts it to
> NMEA. It's possible the GPS outputs binary during that initialization phase.
>  >
>  > I'll try a reset, but I am worried this may happen again when I am
> not there to look after it.
>  >
>  > Bernard KI6TSF
>  >
>
>

Ron K7CDL wrote...

> also this is for everyone, don't forget about setting up the right
> SSID as it goes by this site http://zlhams.wikidot.com/aprs-ssidguide

That's OK, and some people will adhere to the guide, but that's all it
is - just a guide. Identifying a station type by SSID was once a
standard, but is no longer.

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

----- Original Message -----

From: Keith VE7GDH

To: tracker2@yahoogroups.com

Sent: Sunday, November 22, 2009 10:34 PM

Subject: Re: [tracker2] Re: T2 and Nuvi 350

 

Ron K7CDL wrote...

> also this is for everyone, don't forget about setting up the right
> SSID as it goes by this site http://zlhams.wikidot.com/aprs-ssidguide

That's OK, and some people will adhere to the guide, but that's all it
is - just a guide. Identifying a station type by SSID was once a
standard, but is no longer.

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

No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.5.425 / Virus Database: 270.14.76/2519 - Release Date: 11/22/09
07:38:00

Teddy KC0WNY wrote...

> What does a semicolon  in front of a line of text do. Thanks

Are you thinking of the APRS data type identifier? A semicolon
is used for a message. There's a copy of the APRS spec at...

www.ui-view.org/files/APRS101.pdf 3.1 MB or in ZIP form
www.ui-view.org/files/APRS101.zip 780 KB

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

Hi,

I sent it a CMD DUMP over the air but it did not reply.
CMD VERSION returned Tracker2 Build 54740.

How should I do the DUMP?  Connect the PC serial to the
OT2 GPS port?  Port A is in Garmin mode, port B is Auto (for NMEA).
I guess the PC should be connected to B @4800 bauds, right?

BTW I now get more weird WX packets, with longitude being garbled:

2009-11-23 00:27:39 PST:
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.80N/ασ_163/65535g63929t-3041P14\
776h95b31069T2WX [Invalid uncompressed location]

Could this be RF leaking into the OT2 (or GPS)?  I put small ferrites bought
from you on the end near the GPS, and on the RF coax near the transmitter.

Thanks,

Bernard

--- In tracker2@yahoogroups.com, Scott Miller <scott@...> wrote:
>
> Yikes.  If possible, could you do a DUMP command and send me the
> results?  Without powering the unit down, of course.  I want to see if
> it was a random bit flip or if some buffer overflowed and trashed stuff.
>
> I don't know how it'd keep going like that, though.  It's supposed to
> clear the weather flag after transmission and only re-set it if it gets
> valid weather data.
>
> I'll also need to know the firmware build number.  I've got to remember
> to start saving the linker map files for old versions to do this sort of
> debugging.
>
> Scott
>
> ki6tsf wrote:
> >
> >
> >
> > Forgot to add the traces. Those WX messages look weird.
> >
> > 2009-11-22 05:57:35 PST:
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> > 2009-11-22 06:17:39 PST:
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.5V 14C
> > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> > 2009-11-22 06:17:39 PST:
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_126/850g65428t-87\
3P48059h26b57238T2WX
> > 2009-11-22 06:27:40 PST:
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> > 2009-11-22 06:27:41 PST:
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64153g63849t-\
376P31093h67b48059T2WX
> > 2009-11-22 06:37:42 PST:
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> > 2009-11-22 06:37:43 PST:
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_428/246g63849t216\
7P62832h39b39321T2WX
> > 2009-11-22 06:39:12 PST:
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> > 2009-11-22 06:49:13 PST:
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> > 2009-11-22 06:49:14 PST:
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64153g1354t60\
0P39321h15b61165T2WX
> > 2009-11-22 06:59:15 PST:
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> > 2009-11-22 07:09:16 PST:
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> > 2009-11-22 07:19:18 PST:
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> > 2009-11-22 07:29:19 PST:
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> > 2009-11-22 07:29:19 PST:
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64169g1354t-1\
919P6508h94b65535T2WX
> > 2009-11-22 07:39:20 PST:
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> > 2009-11-22 07:49:22 PST:
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64153g1354t-1\
871P39321h46b56797T2WX
> > 2009-11-22 07:59:24 PST:
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63850g1354t-2\
621P13271h50b28398T2WX
> > 2009-11-22 08:09:25 PST:
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> > 2009-11-22 08:19:26 PST:
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> > 2009-11-22 08:19:27 PST:
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63897g1354t46\
6P6547h95b30582T2WX
> > 2009-11-22 08:29:28 PST:
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.3V 14C
> > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> > 2009-11-22 08:29:29 PST:
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63897g1354t11\
14P39276h95b13105T2WX
> > 2009-11-22 08:39:30 PST:
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> > 2009-11-22 08:39:31 PST:
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63897g1354t21\
86P35184h15b39321T2WX
> >
> > --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
> > "ki6tsf" <ki6tsf@> wrote:
> >  >
> >  > Hi,
> >  >
> >  > My OT2 started sending weather reports immediately after each
> > position report.
> >  >
> >  > There is no NMEA mode in the Config utility, only an AUTO mode for
> > NMEA GPSes so I suppose the OT2 got confused at some point and set
> > itself in weather mode when it got unexpected bits from the GPS.
> >  > Or was that excess sunspot activity and a burst of X-ray hit the
> > wrong bit in the OT2.
> >  >
> >  > The GPS is a Globalsat BR-355 puck with SiRF chipset. A script
> > initializes some settings in binary mode at startup, then reverts it to
> > NMEA. It's possible the GPS outputs binary during that initialization phase.
> >  >
> >  > I'll try a reset, but I am worried this may happen again when I am
> > not there to look after it.
> >  >
> >  > Bernard KI6TSF
> >  >
> >
> >
>

You have to be connected to port A to run the DUMP command.  Sounds like
you might have to reset it after all.  But it's useful to know what your
setup is.  Is there data on port B when you're seeing this problem?
Maybe it's a conflict between the NMEA and Garmin inputs.

Scott

ki6tsf wrote:
>
>
> Hi,
>
> I sent it a CMD DUMP over the air but it did not reply.
> CMD VERSION returned Tracker2 Build 54740.
>
> How should I do the DUMP? Connect the PC serial to the
> OT2 GPS port? Port A is in Garmin mode, port B is Auto (for NMEA).
> I guess the PC should be connected to B @4800 bauds, right?
>
> BTW I now get more weird WX packets, with longitude being garbled:
>
> 2009-11-23 00:27:39 PST:
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.80N/ασ_163/65535g63929t-3041P14\
776h95b31069T2WX
> [Invalid uncompressed location]
>
> Could this be RF leaking into the OT2 (or GPS)? I put small ferrites
> bought from you on the end near the GPS, and on the RF coax near the
> transmitter.
>
> Thanks,
>
> Bernard
>
> --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
> Scott Miller <scott@...> wrote:
>  >
>  > Yikes. If possible, could you do a DUMP command and send me the
>  > results? Without powering the unit down, of course. I want to see if
>  > it was a random bit flip or if some buffer overflowed and trashed stuff.
>  >
>  > I don't know how it'd keep going like that, though. It's supposed to
>  > clear the weather flag after transmission and only re-set it if it gets
>  > valid weather data.
>  >
>  > I'll also need to know the firmware build number. I've got to remember
>  > to start saving the linker map files for old versions to do this sort of
>  > debugging.
>  >
>  > Scott
>  >
>  > ki6tsf wrote:
>  > >
>  > >
>  > >
>  > > Forgot to add the traces. Those WX messages look weird.
>  > >
>  > > 2009-11-22 05:57:35 PST:
>  > >
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
>  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
>  > > 2009-11-22 06:17:39 PST:
>  > >
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.5V 14C
>  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
>  > > 2009-11-22 06:17:39 PST:
>  > >
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_126/850g65428t-87\
3P48059h26b57238T2WX
>  > > 2009-11-22 06:27:40 PST:
>  > >
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
>  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
>  > > 2009-11-22 06:27:41 PST:
>  > >
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64153g63849t-\
376P31093h67b48059T2WX
>  > > 2009-11-22 06:37:42 PST:
>  > >
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
>  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
>  > > 2009-11-22 06:37:43 PST:
>  > >
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_428/246g63849t216\
7P62832h39b39321T2WX
>  > > 2009-11-22 06:39:12 PST:
>  > >
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
>  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
>  > > 2009-11-22 06:49:13 PST:
>  > >
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
>  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
>  > > 2009-11-22 06:49:14 PST:
>  > >
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64153g1354t60\
0P39321h15b61165T2WX
>  > > 2009-11-22 06:59:15 PST:
>  > >
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
>  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
>  > > 2009-11-22 07:09:16 PST:
>  > >
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
>  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
>  > > 2009-11-22 07:19:18 PST:
>  > >
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
>  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
>  > > 2009-11-22 07:29:19 PST:
>  > >
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
>  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
>  > > 2009-11-22 07:29:19 PST:
>  > >
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64169g1354t-1\
919P6508h94b65535T2WX
>  > > 2009-11-22 07:39:20 PST:
>  > >
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
>  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
>  > > 2009-11-22 07:49:22 PST:
>  > >
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64153g1354t-1\
871P39321h46b56797T2WX
>  > > 2009-11-22 07:59:24 PST:
>  > >
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63850g1354t-2\
621P13271h50b28398T2WX
>  > > 2009-11-22 08:09:25 PST:
>  > >
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
>  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
>  > > 2009-11-22 08:19:26 PST:
>  > >
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
>  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
>  > > 2009-11-22 08:19:27 PST:
>  > >
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63897g1354t46\
6P6547h95b30582T2WX
>  > > 2009-11-22 08:29:28 PST:
>  > >
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.3V 14C
>  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
>  > > 2009-11-22 08:29:29 PST:
>  > >
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63897g1354t11\
14P39276h95b13105T2WX
>  > > 2009-11-22 08:39:30 PST:
>  > >
> KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
>  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
>  > > 2009-11-22 08:39:31 PST:
>  > >
>
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63897g1354t21\
86P35184h15b39321T2WX
>  > >
>  > > --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>
> <mailto:tracker2%40yahoogroups.com>,
>  > > "ki6tsf" <ki6tsf@> wrote:
>  > > >
>  > > > Hi,
>  > > >
>  > > > My OT2 started sending weather reports immediately after each
>  > > position report.
>  > > >
>  > > > There is no NMEA mode in the Config utility, only an AUTO mode for
>  > > NMEA GPSes so I suppose the OT2 got confused at some point and set
>  > > itself in weather mode when it got unexpected bits from the GPS.
>  > > > Or was that excess sunspot activity and a burst of X-ray hit the
>  > > wrong bit in the OT2.
>  > > >
>  > > > The GPS is a Globalsat BR-355 puck with SiRF chipset. A script
>  > > initializes some settings in binary mode at startup, then reverts
> it to
>  > > NMEA. It's possible the GPS outputs binary during that
> initialization phase.
>  > > >
>  > > > I'll try a reset, but I am worried this may happen again when I am
>  > > not there to look after it.
>  > > >
>  > > > Bernard KI6TSF
>  > > >
>  > >
>  > >
>  >
>
>

Sorry for the off-topic post, but this is the most likely place I could
think to find something on short notice.  And to keep it more on-topic,
I'll be happy to send free trackers to anyone who can help out with this.

My parents (KK6AD and KB6VAA) made it as far as Morgantown, West
Virginia on their way to Iowa for Thanksgiving, pulling a 29' fifth
wheel, when they blew the engine on their truck (which incidentally
served them for 18 solid months of RVing with hardly a hiccup).
Replacement is going to take several days.  My uncle in Iowa may very
well not be around next holiday season, so this is an important trip for
them.

My sister and I are hoping to find someone in the area who's got a 5th
wheel tow rig they can rent out for several days, that they can deliver
to Morgantown.  Today, if possible.  A 1-ton truck with 5th wheel hitch
is not something you usually find at Hertz, though.  I'll be the one
paying - an early Christmas present for my parents if we can find something.

If you've got something available or know someone who does, let me know.

Thanks,

Scott
N1VG

Hope this isn't a too tall order, but I would love to be able to set a
digi so it could trap the whole path of an incoming packet if it
contained more hops than needed. A limit that could be set with a new
command, similar to hoplimit, but more like a pathlimit.

An abuser recently came in running this path:
   2009-11-13 11:01:44 PST:
KD6M**-1>3X5TSS,N6ZX-3,WIDE1*,WIDE2-2,WIDE3-3,WIDE10-10,qAR,KE6ZBX-10:`1\
_=l"<0x1c>=/`"7M}On 145535 & 28385 ......_

I would like to be able to set a "cap" on his whole path. I live in a
busy area, run only fillin digi's, that can be heard directly by igates.
A command that would set a cap that would use up his entire path except
for the limit that is set. Like the example below, cap is set to allow 1
more hop.

2009-11-13 11:01:44 PST:
KD6M**-1>3X5TSS,N6ZX-3,WIDE1,WIDE2,WIDE3,WIDE10-1*,qAR,KE6ZBX-10:`1_=l"<\
0x1c>=/`"7M}On 145535 & 28385 ......_


Alan

---

From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of Alan
Sent: Tuesday, November 24, 2009 14:25
To: tracker2@yahoogroups.com
Subject: [tracker2] Digi command wish

 

Hope this isn't a too tall order, but I would love to be able to set a
digi so it could trap the whole path of an incoming packet if it
contained more hops than needed. A limit that could be set with a new
command, similar to hoplimit, but more like a pathlimit.

An abuser recently came in running this path:
2009-11-13 11:01:44 PST:
KD6M**-1>3X5TSS,N6ZX-3,WIDE1*,WIDE2-2,WIDE3-3,WIDE10-10,qAR,KE6ZBX-10:`1\
_=l"<0x1c>=/`"7M}On 145535 & 28385 ......_

I would like to be able to set a "cap" on his whole path. I live in a
busy area, run only fillin digi's, that can be heard directly by igates.
A command that would set a cap that would use up his entire path except
for the limit that is set. Like the example below, cap is set to allow 1
more hop.

2009-11-13 11:01:44 PST:
KD6M**-1>3X5TSS,N6ZX-3,WIDE1,WIDE2,WIDE3,WIDE10-1*,qAR,KE6ZBX-10:`1_=l"<\
0x1c>=/`"7M}On 145535 & 28385 ......_

Alan

I run fillin's, KPC-3's, TT4's and OT2's,  all will deal with the
WIDE1-7.

The KPC's and TT4's ignore since I set alias to WIDE1-1.
The OT2 is set WIDE1 with Hoplimit 0, it will trap the WIDE1-7 to
WIDE1*, but if the "appliance user" has additional paths he's is still
able to abuse the network.

I would hope the new command could be able to parse the complete path,
and trap to sanity including WIDE1-7.


--- In tracker2@yahoogroups.com, "Fred Hillhouse" <fmhillhouse@...>
wrote:
>
> If one is using the new paradigm with a KPC3, anything above 3 is
trapped on
> a WIDEN digi. I would assume those running T2s would trap in a similar
> fashion. My guess is that the WIDE3 would possibly make it through but
not
> the WIDE10.
>
> Of course a WIDE1-7 would be worse because of no trapping of this type
of
> hop request. James has pointed this out before.
>
>
>
>
>   _____
>
> From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On
Behalf
> Of Alan
> Sent: Tuesday, November 24, 2009 14:25
> To: tracker2@yahoogroups.com
> Subject: [tracker2] Digi command wish
>
>
>
>
>
> Hope this isn't a too tall order, but I would love to be able to set a
> digi so it could trap the whole path of an incoming packet if it
> contained more hops than needed. A limit that could be set with a new
> command, similar to hoplimit, but more like a pathlimit.
>
> An abuser recently came in running this path:
> 2009-11-13 11:01:44 PST:
>
KD6M**-1>3X5TSS,N6ZX-3,WIDE1*,WIDE2-2,WIDE3-3,WIDE10-10,qAR,KE6ZBX-10:`1\
\
> _=l"<0x1c>=/`"7M}On 145535 & 28385 ......_
>
> I would like to be able to set a "cap" on his whole path. I live in a
> busy area, run only fillin digi's, that can be heard directly by
igates.
> A command that would set a cap that would use up his entire path
except
> for the limit that is set. Like the example below, cap is set to allow
1
> more hop.
>
> 2009-11-13 11:01:44 PST:
>
KD6M**-1>3X5TSS,N6ZX-3,WIDE1,WIDE2,WIDE3,WIDE10-1qAR,KE6ZBX-10:`1_=l"<\
> 0x1c>=/`"7M}On 145535 & 28385 ......_
>
> Alan
>

Hmm.  Can you check the connection on the BNC?  A few units have had a
flaky solder joint there.

On the bench they're tested at something like -60 dBm with a signal
source that's just a bunch of copies of the same packet with increasing
levels of noise.  Of course, that doesn't do much to test the RF
sensitivity of the radio, just the demodulator.  I should probably set
the test set to -105 dBm or so, where I know it should get solid copy if
it's working right.

I just copied the test setup I used for the T2-135's, but there testing
the radio wasn't an issue.  I've been trusting the radio manufacturer's
QA, but it wouldn't cost me anything to crank the signal level way lower
to weed out any weak ones.

Scott

g7iii wrote:
>
>
> Hi All,
>
> Is there a pot or two inside the T2-301 where I can adjust the receive
> audio level being fed into the T2 board ?
>
> I'm in a situation where:
>
> a) I don't hear many packets on the T2-301
> b) If I turn PASSALL on, they all come flooding past in various states
> of corruption
> c) Plugging the D-710 into the same antenna results in many packets
> being decoded from far stations (~25 miles plus) as well as near
> stations (~5 miles)
> d) I did try an external pre-amp (although admittedly, not mast-head
> mounted), which did not improve the system at all)
> e) A Very distant digi can hear me (although it is very high), but I
> can't hear it (and w/o hearing many packets of course, I suspect the
> CSMA gets stuffed up and I end up stomping,o r getting stomped on
>
> So I'm kinda wondering I have an RX Sensitivity issue, a S/N issue, or
> if it's a situation where a bit more audio needs to be injected to the
> T2, and if somehow I can twiddle the two at all ?
>
> 73s
>
> Iain
>
>

If it's not getting a GPS signal, then whatever's in the position buffer
is going to stay.  How it got corrupted in the first place, I'm not
sure.  I've seen a similar (or similar-appearing) problem in
circumstances I know I can replicate, so I'll focus on sorting that out
and hopefully it'll fix this one too.

Scott

Keith VE7GDH wrote:
>
>
> This was posted over on the NWAPRS list...
>
> http://find-you.com/cgi-bin/errors.cgi
> <http://find-you.com/cgi-bin/errors.cgi>
>
> KF7DEI-4>APOT21,KK7DO-1*,WIDE2-1,qAR,WA7MXZ-3
> :!4111.N9N/11156.55WO!W!NO FIX 13.7V 17C
>
> http://aprs.fi/?c=raw&call=KF7DEI-4&limit=1000
> <http://aprs.fi/?c=raw&call=KF7DEI-4&limit=1000>
>
> The GPS appears to have lost lock, but the latitude is missing a
> couple of decimal positions. Looking at the raw data, it doesn't
> appear to be a one-time occurrence. Scott - any ideas?
>
> 73 es cul - Keith VE7GDH
> --
> "I may be lost, but I know exactly where I am!"
>
>

>>  > ADC0 and ADC1 are reported in the standard telemetry string.

I think this is NOT correct.
The standard telemtry string of an OT2M looks like this:
T# internalTemp,Voltage,ADC0,COUNT,HDOP, 0,0,0,0,0,0,JUMPER,PROFILE

Unfortunately it only reports one ADC line and  COUNTER from the M08
connector.
There should be a file in the files/picture section describing details.
For weather stations and telemetry applications it would be much better to
have more and selectable analogue ADC-I/O lines available.
However, you could use an OT1+ or OT1SMT...

vy 73 de Mike
oe3mzc

----- Original Message -----
From: "Scott Miller" <scott@...>
To: <tracker2@yahoogroups.com>
Sent: Monday, November 09, 2009 6:40 AM
Subject: Re: [tracker2] Re: A/D inputs


> Not all of them are general purpose I/O lines.  Anything that starts
> with 'PT' is, though.  You *can* control them through the scripting
> language, but it requires using the POKE command and looking up the
> addresses in the MC908AP64 data sheet.  Also, the LCD code will be
> trying to control 6 of those lines.
>
> Scott
>
> ki6tsf wrote:
>>
>>
>>
>> Hi,
>>
>> Is there a way to read(/write) to those from the OT2 scripting language?
>>
>> Thanks and 73,
>>
>> Bernard KI6TSF
>>
>> --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
>> Scott Miller <scott@...> wrote:
>>  >
>>  > I missed this before... here's the pinout for the 16 pads at the
>> front,
>>  > starting at the 'M' in MON08:
>>  >
>>  > 1 - PTB7/T2CH1 (digital I/O or timer channel)
>>  > 2 - GND
>>  > 3 - PTB5/T1CH1
>>  > 4 - Reset
>>  > 5 - No connection
>>  > 6 - IRQ (counter/transmit-now input)
>>  > 7 - No connection
>>  > 8 - PTA3/ADC3 (digital I/O or ADC input)
>>  > 9 - No connection
>>  > 10 - PTA0/ADC0
>>  > 11 - No connection
>>  > 12 - PTA2/ADC2
>>  > 13 - Clock oscillator (32.768 kHz)
>>  > 14 - PTA1/ADC1
>>  > 15 - +5V
>>  > 16 - PTB0 (digital I/O)
>>  >
>>  > ADC0 and ADC1 are reported in the standard telemetry string.
>>  >
>>  > Scott
>>  >
>>  > Sean Smith wrote:
>>  > >
>>  > >
>>  > > Hi Scott,
>>  > >
>>  > > I've finally got time to work with the two Tracker2s I ordered a
>>  > > while back, I'm wondering where I hook up my exteral ADC's I'm
>>  > > assuming it's some where on the twin rows of 16 pads at the front of
>>  > > the unit. Couldn't find any thing in the manual or the schematics
>>  > > that are online.
>>  > >
>>  > > Configuring the units was a dream very straight forward, almost like
>>  > > they were designed to be user friendly....
>>  > >
>>  > > Sean
>>  > >
>>  > > --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>
>> <mailto:tracker2%40yahoogroups.com>,
>>  > > Scott Miller <scott@> wrote:
>>  > > >
>>  > > > ADCs are 0-5 volts. The internal sensor can be calibrated with a
>>  > > simple
>>  > > > offset. For an external sensor, it's going to return a raw ADC
>>  > > reading.
>>  > > > The sequence of the telemetry values should be in the OT2m manual.
>>  > > >
>>  > > > Scott
>>  > > >
>>  > > > Sean Smith wrote:
>>  > > > >
>>  > > > >
>>  > > > > What voltage range will the A/D inputs handle?
>>  > > > >
>>  > > > > The internal voltage / Temp readings what postions are they
>>  > > located
>>  > > > > in in a telemetry packet? I've got a couple perl scripts I'm
>>  > > playing
>>  > > > > with to display the telemetry on a web page.
>>  > > > >
>>  > > > > Also can the the inputs be calibrated? ie using a LM335 temp
>>  > > sensor.
>>  > > > >
>>  > > > > Sean
>>  > > > >
>>  > > > > --- In tracker2@yahoogroups.com
>> <mailto:tracker2%40yahoogroups.com> <mailto:tracker2%40yahoogroups.com>
>>  > > <mailto:tracker2%
>>  > > 40yahoogroups.com>,
>>  > > > > Joel Maslak <jmaslak@> wrote:
>>  > > > > >
>>  > > > > > On Apr 7, 2008, at 7:38 AM, Sean Smith wrote:
>>  > > > > > > I'm looking at using a tracker 2 for our club's next
>> repeater
>>  > > > > site.
>>  > > > > > > It's a very remote site (2 hours north of Peace River Ab) so
>>  > > I
>>  > > > > want
>>  > > > > > > it to have telemetry from it.
>>  > > > > > >
>>  > > > > > > What I'm looking for is the following:
>>  > > > > > > Analog
>>  > > > > > > -Supply voltage
>>  > > > > > > -temp inside shack
>>  > > > > > > -temp outside shack
>>  > > > > > >
>>  > > > > > > Digital
>>  > > > > > > -1 input to indicate wether commerial power is connected or
>>  > > not. I
>>  > > > > > > usually use a wall wort to give me this signal.
>>  > > > > > >
>>  > > > > >
>>  > > > > > I'm working on all of these with an OT1+, but should be the
>>  > > same
>>  > > > > as
>>  > > > > > the T2. It can do this. (I'm doing this in an RV, but need
>>  > > > > exactly
>>  > > > > > the same telemetry).
>>  > > > > >
>>  > > > > > As for the commercial power, I believe there is enough A/D
>>  > > inputs
>>  > > > > to
>>  > > > > > actually use a non-regulated wall-wart (maybe with some
>>  > > > > overvoltage
>>  > > > > > protection) and send the actual line voltage out, rather than
>>  > > just
>>  > > > > > "on/off". I'm thinking of finding a step-down transformer
>>  > > > > somewhere
>>  > > > > > in the 3-4 volt range for that, without any regulator built
>>  > > into it.
>>  > > > > >
>>  > > > >
>>  > > > >
>>  > > >
>>  > >
>>  > >
>>  >
>>
>>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Hi,

--- In tracker2@yahoogroups.com, Scott Miller <scott@...> wrote:
>
> You have to be connected to port A to run the DUMP command.  Sounds like
> you might have to reset it after all.  But it's useful to know what your

By reset, do you mean power-off/power-on, or CMD RESET over-the-air?

> setup is.  Is there data on port B when you're seeing this problem?

Yes, the Globalsat GPS is on port B and outputs NMEA.  Once the WX problem
occurs, it looks like the GPS doesn't output NMEA anymore but SiRF binary....  I
have no idea why.  It didn't do that before.
It did it again after some time last night.

I think the last resort is a factory reset on the GPS and a re-install of the
OT2 firmware.  Hopefully that will help.

> Maybe it's a conflict between the NMEA and Garmin inputs.

The Garmin was disconnect from port A when this occured..

Bernard KI6TSF

>
> Scott
>
> ki6tsf wrote:
> >
> >
> > Hi,
> >
> > I sent it a CMD DUMP over the air but it did not reply.
> > CMD VERSION returned Tracker2 Build 54740.
> >
> > How should I do the DUMP? Connect the PC serial to the
> > OT2 GPS port? Port A is in Garmin mode, port B is Auto (for NMEA).
> > I guess the PC should be connected to B @4800 bauds, right?
> >
> > BTW I now get more weird WX packets, with longitude being garbled:
> >
> > 2009-11-23 00:27:39 PST:
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.80N/ασ_163/65535g63929t-3041P14\
776h95b31069T2WX
> > [Invalid uncompressed location]
> >
> > Could this be RF leaking into the OT2 (or GPS)? I put small ferrites
> > bought from you on the end near the GPS, and on the RF coax near the
> > transmitter.
> >
> > Thanks,
> >
> > Bernard
> >
> > --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
> > Scott Miller <scott@> wrote:
> >  >
> >  > Yikes. If possible, could you do a DUMP command and send me the
> >  > results? Without powering the unit down, of course. I want to see if
> >  > it was a random bit flip or if some buffer overflowed and trashed stuff.
> >  >
> >  > I don't know how it'd keep going like that, though. It's supposed to
> >  > clear the weather flag after transmission and only re-set it if it gets
> >  > valid weather data.
> >  >
> >  > I'll also need to know the firmware build number. I've got to remember
> >  > to start saving the linker map files for old versions to do this sort of
> >  > debugging.
> >  >
> >  > Scott
> >  >
> >  > ki6tsf wrote:
> >  > >
> >  > >
> >  > >
> >  > > Forgot to add the traces. Those WX messages look weird.
> >  > >
> >  > > 2009-11-22 05:57:35 PST:
> >  > >
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> >  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> >  > > 2009-11-22 06:17:39 PST:
> >  > >
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.5V 14C
> >  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> >  > > 2009-11-22 06:17:39 PST:
> >  > >
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_126/850g65428t-87\
3P48059h26b57238T2WX
> >  > > 2009-11-22 06:27:40 PST:
> >  > >
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> >  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> >  > > 2009-11-22 06:27:41 PST:
> >  > >
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64153g63849t-\
376P31093h67b48059T2WX
> >  > > 2009-11-22 06:37:42 PST:
> >  > >
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> >  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> >  > > 2009-11-22 06:37:43 PST:
> >  > >
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_428/246g63849t216\
7P62832h39b39321T2WX
> >  > > 2009-11-22 06:39:12 PST:
> >  > >
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> >  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> >  > > 2009-11-22 06:49:13 PST:
> >  > >
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> >  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> >  > > 2009-11-22 06:49:14 PST:
> >  > >
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64153g1354t60\
0P39321h15b61165T2WX
> >  > > 2009-11-22 06:59:15 PST:
> >  > >
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> >  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> >  > > 2009-11-22 07:09:16 PST:
> >  > >
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> >  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> >  > > 2009-11-22 07:19:18 PST:
> >  > >
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> >  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> >  > > 2009-11-22 07:29:19 PST:
> >  > >
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> >  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> >  > > 2009-11-22 07:29:19 PST:
> >  > >
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64169g1354t-1\
919P6508h94b65535T2WX
> >  > > 2009-11-22 07:39:20 PST:
> >  > >
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> >  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> >  > > 2009-11-22 07:49:22 PST:
> >  > >
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/64153g1354t-1\
871P39321h46b56797T2WX
> >  > > 2009-11-22 07:59:24 PST:
> >  > >
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63850g1354t-2\
621P13271h50b28398T2WX
> >  > > 2009-11-22 08:09:25 PST:
> >  > >
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> >  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> >  > > 2009-11-22 08:19:26 PST:
> >  > >
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> >  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> >  > > 2009-11-22 08:19:27 PST:
> >  > >
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63897g1354t46\
6P6547h95b30582T2WX
> >  > > 2009-11-22 08:29:28 PST:
> >  > >
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.3V 14C
> >  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> >  > > 2009-11-22 08:29:29 PST:
> >  > >
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63897g1354t11\
14P39276h95b13105T2WX
> >  > > 2009-11-22 08:39:30 PST:
> >  > >
> > KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W>12.4V 14C
> >  > > GPS drift test: elevation mask>20, DOP<8, WAAS=on, SN=on
> >  > > 2009-11-22 08:39:31 PST:
> >  > >
> >
KI6TSF-9>APOT21,WIDE1-1,WIDE2-1,qAR,W6YX-5:!3723.79N/12205.97W_511/63897g1354t21\
86P35184h15b39321T2WX
> >  > >
> >  > > --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>
> > <mailto:tracker2%40yahoogroups.com>,
> >  > > "ki6tsf" <ki6tsf@> wrote:
> >  > > >
> >  > > > Hi,
> >  > > >
> >  > > > My OT2 started sending weather reports immediately after each
> >  > > position report.
> >  > > >
> >  > > > There is no NMEA mode in the Config utility, only an AUTO mode for
> >  > > NMEA GPSes so I suppose the OT2 got confused at some point and set
> >  > > itself in weather mode when it got unexpected bits from the GPS.
> >  > > > Or was that excess sunspot activity and a burst of X-ray hit the
> >  > > wrong bit in the OT2.
> >  > > >
> >  > > > The GPS is a Globalsat BR-355 puck with SiRF chipset. A script
> >  > > initializes some settings in binary mode at startup, then reverts
> > it to
> >  > > NMEA. It's possible the GPS outputs binary during that
> > initialization phase.
> >  > > >
> >  > > > I'll try a reset, but I am worried this may happen again when I am
> >  > > not there to look after it.
> >  > > >
> >  > > > Bernard KI6TSF
> >  > > >
> >  > >
> >  > >
> >  >
> >
> >
>