The position is correct.

What I want to do is eliminate the position packet to recover the wasted
bandwidth.  The station position is already being broadcast in the WX
packet. Maybe it isn't possible. As I said before I am new to APRS and I
haven't figured out what I can and can't do yet.

I don't know why you can't see the screen shot. It looks fine on
Firefox. Are you viewing via email?

Tom - W4SNA

--- In tracker2@yahoogroups.com, "k7ybz" <k7ybz@...> wrote:
>
>
> The position reported is 36 degrees 22.65 minutes North and 80 degress
21.86 minutes West.
>
> Look at the reported position from this link.
> http://aprs.fi/?call=W4SNA-2
>
> Is that the correct location?
>
> BTW. At least for me, the screen shot is not available.
>
> Larry
> K7YBZ
>

Andrew KC2EUS wrote...

> what settings do I put in the Tracker2 to get it to digipeat my beacon
> from the VX8. I set the digipeat on call, but on a quick test, and it
> did not seem to work. What am I missing... is there anything different
> I need to add to the WIDE1-1, WIDE2-1 on the VX8 ??

With DIGI ON in the T2, it should digipeat via the call in the T2. To
use it that way, you could use a path like GM1YMI,WIDE2-1 assuming that
GM1YMI was the MYCALL in the T2. If the T2 could be heard by a WIDEn-N
digi, it would act on the remaining WIDE2-1. However, if the T2 didn't
hear the beacon from the VX-8, your beacon would end there. Digi paths
are used in order... with the exception of the T2 which if it had
PREEMPT <n> turned on could act on an alias with un-used aliases
ahead of the "pre-empted" alias.

To get it to respond to WIDEn-N you could...

ALIAS 1 WIDE
HOPLIMIT 2
USEALIAS 1
DIGIID 1 ON

or if you wanted it to respond to WIDE1-1 only...

ALIAS 1 WIDE1
HOPLIMIT 1
USEALIAS 1
DIGIID 1 ON

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

Would that not allow the T2 to digipeat everything ?

Andrew

--- In tracker2@yahoogroups.com, "Keith VE7GDH" <ve7gdh@...> wrote:
>
> Andrew KC2EUS wrote...
>
> > what settings do I put in the Tracker2 to get it to digipeat my beacon
> > from the VX8. I set the digipeat on call, but on a quick test, and it
> > did not seem to work. What am I missing... is there anything different
> > I need to add to the WIDE1-1, WIDE2-1 on the VX8 ??
>
> With DIGI ON in the T2, it should digipeat via the call in the T2. To
> use it that way, you could use a path like GM1YMI,WIDE2-1 assuming that
> GM1YMI was the MYCALL in the T2. If the T2 could be heard by a WIDEn-N
> digi, it would act on the remaining WIDE2-1. However, if the T2 didn't
> hear the beacon from the VX-8, your beacon would end there. Digi paths
> are used in order... with the exception of the T2 which if it had
> PREEMPT <n> turned on could act on an alias with un-used aliases
> ahead of the "pre-empted" alias.
>
> To get it to respond to WIDEn-N you could...
>
> ALIAS 1 WIDE
> HOPLIMIT 2
> USEALIAS 1
> DIGIID 1 ON
>
> or if you wanted it to respond to WIDE1-1 only...
>
> ALIAS 1 WIDE1
> HOPLIMIT 1
> USEALIAS 1
> DIGIID 1 ON
>
> 73 es cul - Keith VE7GDH
> --
> "I may be lost, but I know exactly where I am!"
>

Thanks Keith for the reply ... This begs another question. If I enable as WIDE
2-1 or WIDE 1-1 then it'll digi everything it hears, as long as they fit the
WIDE n-N criteria.
Or is there a way to only digi my packets .. is this where the checkbox "digi on
my call" comes into play ?

Andrew
K1YMI

--- In tracker2@yahoogroups.com, "Keith VE7GDH" <ve7gdh@...> wrote:
>
> Andrew KC2EUS wrote...
>
> > what settings do I put in the Tracker2 to get it to digipeat my beacon
> > from the VX8. I set the digipeat on call, but on a quick test, and it
> > did not seem to work. What am I missing... is there anything different
> > I need to add to the WIDE1-1, WIDE2-1 on the VX8 ??
>
> With DIGI ON in the T2, it should digipeat via the call in the T2. To
> use it that way, you could use a path like GM1YMI,WIDE2-1 assuming that
> GM1YMI was the MYCALL in the T2. If the T2 could be heard by a WIDEn-N
> digi, it would act on the remaining WIDE2-1. However, if the T2 didn't
> hear the beacon from the VX-8, your beacon would end there. Digi paths
> are used in order... with the exception of the T2 which if it had
> PREEMPT <n> turned on could act on an alias with un-used aliases
> ahead of the "pre-empted" alias.
>
> To get it to respond to WIDEn-N you could...
>
> ALIAS 1 WIDE
> HOPLIMIT 2
> USEALIAS 1
> DIGIID 1 ON
>
> or if you wanted it to respond to WIDE1-1 only...
>
> ALIAS 1 WIDE1
> HOPLIMIT 1
> USEALIAS 1
> DIGIID 1 ON
>
> 73 es cul - Keith VE7GDH
> --
> "I may be lost, but I know exactly where I am!"
>

On Mon, Nov 2, 2009 at 5:55 PM, w4sna <w4sna@...> wrote:

> What I want to do is eliminate the position packet to recover the wasted
> bandwidth.  The station position is already being broadcast in the WX
> packet.

What about the wasted bandwidth from the status packet?

>!3622.65N/08021.86W_PHG5750/Wide1-1, WX Sauratown Mtn, NC

That's an awful lot of wasted bandwidth, far more than what you're
concerned with...

!3622.65N/08021.86W_

The status packet gives nothing new to the observer in the first 20
characters. The PHG would be useful if it were on a position packet,
not status. WIDE1-1 is new info, WX is known from your icon. Sauratown
Mtn, NC can be deduced from your location.

The site that you are at looks like a might fine spot for a full blown
digipeater rather than a fill-in. You probably hear more than the
other full digipeaters in the area. One issue with running a fill-in
digipeater is that you end up acting only as an RF collector site.
Anyone in your local area sending messages probably won't get a
message back because there's no local digi to bounce through.

You're also hammering the local RF network pretty hard. You're sending
WX packets every 5 minutes over a 2 hop path. That's probably lighting
up most of North Carolina, half of Virginia, and probably even hitting
South Carolina too. If you really need to know the weather ever 5
minutes on the mountaintop, and you don't have internet access up
there, it might be a good idea to run on a separate frequency. Because
your station is sitting on a mountaintop, a WIDE2-2 path is equivalent
to a regular user using a path of WIDE3-3. Regular users have to use
one hop to get to the mountaintop, but your station is already there.

> I don't know why you can't see the screen shot. It looks fine on
> Firefox. Are you viewing via email?

Pretty hard to read your email as a movie... this reflector is not
going to pass images. If you want to share an image, save it in the
images section of the yahoogroup, or on another site of your choice.

Unfortunately I don't have a weather station, so I haven't played with
sending weather and packets...

James
VE6SRV

> I'm not sure if anyone has sat down and measured what Power Output was
> created by each "SETLEVEL" setting on the T2-301, but since I have a
> need to limit ERP to 25 Watts, I decided to sit down and do just that.

The command is "SETPOWER", but other than that it looks good.
Consistent with what I get, at least in general shape.  I'd like to run
several curves at different voltages when I get a chance.  If I can
figure out how to pull the power reading from the HP 8920A I can
probably automate most of it - I don't have a programmable power supply.

Scott

It's not possible at the moment, but I have it on my list.  It also
needs to be able to transmit with a different SSID for the position and
weather station packets, to avoid confusing some clients.

Scott

w4sna wrote:
>
>
> The position is correct.
>
> What I want to do is eliminate the position packet to recover the wasted
> bandwidth. The station position is already being broadcast in the WX
> packet. Maybe it isn't possible. As I said before I am new to APRS and I
> haven't figured out what I can and can't do yet.
>
> I don't know why you can't see the screen shot. It looks fine on
> Firefox. Are you viewing via email?
>
> Tom - W4SNA
>
> --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
> "k7ybz" <k7ybz@...> wrote:
>  >
>  >
>  > The position reported is 36 degrees 22.65 minutes North and 80 degress
> 21.86 minutes West.
>  >
>  > Look at the reported position from this link.
>  > http://aprs.fi/?call=W4SNA-2 <http://aprs.fi/?call=W4SNA-2>
>  >
>  > Is that the correct location?
>  >
>  > BTW. At least for me, the screen shot is not available.
>  >
>  > Larry
>  > K7YBZ
>  >
>
>

--- In tracker2@yahoogroups.com, James Ewen <ve6srv@...> wrote:
If you really need to know the weather ever 5
> minutes on the mountaintop, and you don't have internet access up
> there, it might be a good idea to run on a separate frequency.


You have some good points.

Obtaining near real time wind speed reports from the repeater site is the
primary reason this station was installed. APRS was chosen because there is no
Internet access available at the site. The fill-in digi was set up because there
are some RF shadows in the local area not covered well by the full digis.

Since the WX data is of little interest to persons outside the local area your
suggestion to change frequencies is probably the best solution to eliminate the
impact of the station on the network. I can collect the data and publish it on
the web for locals that don't have APRS capabilities.

I have shut down the station until Neal gets back in town. We can decide what to
do then.

Tom - W4SNA

Hi Fujira, Patrick,

How did you resolve the PHG issue on aprs.fi?  Has Scott been made aware of this
protocol bug?  I'm just running into it myself.

Thanks
Henry
KB7NIE

--- In tracker2@yahoogroups.com, "FUJIURA Toyonori" <toyokun@...> wrote:
>
> Patrick,
>
> 2008/9/28 Patrick <winston@...>:
> > One thing that could be breaking the parsing of it is that there's no
> > space between the temp (22C) and the PHG...  does adding a space before
> > the PHG resolve the issue?
>
> On aprs.fi, I have resolved the issue.
> But I haven't resolved it on openaprs.net.
> Anyway, thank you for your advise.
> # Testing with not T2 but UIView because nobody receive my QRP packet...
> --
> FUJIURA Toyonori mailto:toyokun@...
>

Andrew K1YMI / KC2EUS / GM1YMI wrote...

> This begs another question. If I enable as WIDE 2-1 or WIDE 1-1
> then it'll digi everything it hears, as long as they fit the WIDE n-N
> criteria.

If you enable it for WIDEn-N up to two hops, it would respond to anyone
using a path of WIDE2-2 or WIDE2-1 or WIDE1-1. If it was set up as a
fill-in digi only, it would only respond to WIDE1-1.

> Or is there a way to only digi my packets .. is this where the
> checkbox "digi on my call" comes into play ?

The "digi on my call" (the call in the T2) is one option. Another would
be to pick a non-standard alias for ALIAS 1 <alias> like...

ALIAS 1 MEONLY

and set a path of MEONLY in the VX-8R, or MEONLY,WIDE2-1 if you
hope another digi to pick you up after it goes through the T2. Of
course, if someone sees you being digi'd by MEONLY, there would be
nothing to stop them from using the path too.

Yet another option... use a path of WIDE2-2,TEMP and enable TEMP as one
of the aliases in the T2 and turn PREEMPT ON for that alias. You would
get at least one hop from the T2 if it hears you. If it doesn't, there's
a chance you will be digi'd by any WIDEn-N digi that hears you.

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

Andrew KC2EUS wrote...

> Would that not allow the T2 to digipeat everything ?

The two lots of settings I suggested would allow it to digipeat either
WIDEn-N up to 2 hops or WIDE1-1 only, as well as digipeating on its own
callsign. If you don't want anyone else to digi through it, set USEALIAS
<n> OFF for all of them and leave DIGI ON and it will only digi on its
own callsign. However, you said you tried that and it didn't work. What
is the callsign in the T2, and what path did you have entered in the
VX-8R?

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

Thank you Scott,

Larry
K7YBZ

--- In tracker2@yahoogroups.com, Scott Miller <scott@...> wrote:
>
> It's not possible at the moment, but I have it on my list.  It also
> needs to be able to transmit with a different SSID for the position and
> weather station packets, to avoid confusing some clients.
>
> Scott
>

--- In tracker2@yahoogroups.com, Scott Miller <scott@...> wrote:
>
> > I'm not sure if anyone has sat down and measured what Power Output was
> > created by each "SETLEVEL" setting on the T2-301, but since I have a
> > need to limit ERP to 25 Watts, I decided to sit down and do just that.
>
> The command is "SETPOWER", but other than that it looks good.
> Consistent with what I get, at least in general shape.  I'd like to run
> several curves at different voltages when I get a chance.  If I can
> figure out how to pull the power reading from the HP 8920A I can
> probably automate most of it - I don't have a programmable power supply.

Doh! Lord only knows how I made that mistake. And throughout the entire article.
I've fixed the article, and I'll redo the graph this evening

I'll also try and get a PDF and the raw data uploaded as per Larry's suggestion


Iain

Sorry for the double post last time. I did not think the first had gone through.
Ok I've got it now. If I set it to a fill-in with WIDE 1-1 I think I should be
good.
I was worried I was going to cause an issue with "spamming" the network. This
was where the concern was coming from.
Also if I leave it at WIDE 1-1 I don't have to mess around changing the default
settings in the VX8 everytime I use this setup.

Thanks for the info, i think I was trying to make it more complex than it was !

Andrew

--- In tracker2@yahoogroups.com, "Keith VE7GDH" <ve7gdh@...> wrote:
>
> Andrew K1YMI / KC2EUS / GM1YMI wrote...
>
> > This begs another question. If I enable as WIDE 2-1 or WIDE 1-1
> > then it'll digi everything it hears, as long as they fit the WIDE n-N
> > criteria.
>
> If you enable it for WIDEn-N up to two hops, it would respond to anyone
> using a path of WIDE2-2 or WIDE2-1 or WIDE1-1. If it was set up as a
> fill-in digi only, it would only respond to WIDE1-1.
>
> > Or is there a way to only digi my packets .. is this where the
> > checkbox "digi on my call" comes into play ?
>
> The "digi on my call" (the call in the T2) is one option. Another would
> be to pick a non-standard alias for ALIAS 1 <alias> like...
>
> ALIAS 1 MEONLY
>
> and set a path of MEONLY in the VX-8R, or MEONLY,WIDE2-1 if you
> hope another digi to pick you up after it goes through the T2. Of
> course, if someone sees you being digi'd by MEONLY, there would be
> nothing to stop them from using the path too.
>
> Yet another option... use a path of WIDE2-2,TEMP and enable TEMP as one
> of the aliases in the T2 and turn PREEMPT ON for that alias. You would
> get at least one hop from the T2 if it hears you. If it doesn't, there's
> a chance you will be digi'd by any WIDEn-N digi that hears you.
>
> 73 es cul - Keith VE7GDH
> --
> "I may be lost, but I know exactly where I am!"
>

Hello Scott,
I'm going to place my T2-301 in another box with a Tx/Rx LED, a 'Beacon
now' push button and profile select switch on the front.

1. Is D4 as marked on the T2 board a connection point for a Tx/Rx LED?
2. Is there a connection point for a profile switch or do I have to
connect a wire direct to the processor chip, pin 34?

TIA.
Mike, VK2IN.

Keith VE7GDH wrote:
> Andrew KC2EUS wrote...
>
>
>> Would that not allow the T2 to digipeat everything ?
>>
>
> The two lots of settings I suggested would allow it to digipeat either
> WIDEn-N up to 2 hops or WIDE1-1 only, as well as digipeating on its own
> callsign. If you don't want anyone else to digi through it, set USEALIAS
> <n> OFF for all of them and leave DIGI ON and it will only digi on its
> own callsign. However, you said you tried that and it didn't work. What
> is the callsign in the T2, and what path did you have entered in the
> VX-8R?
>
>
And have you confirmed that the T2 can/is actually DECODING the VX-8R?
If it doesn't decode (verify by hooking up a PC and running TEXT mode),
then it won't digipeat anything.

Lynn (D) - KJ4ERJ

kc2eus wrote:
> Sorry for the double post last time. I did not think the first had gone
through.
> Ok I've got it now. If I set it to a fill-in with WIDE 1-1 I think I should be
good.
> I was worried I was going to cause an issue with "spamming" the network. This
was where the concern was coming from.
> Also if I leave it at WIDE 1-1 I don't have to mess around changing the
default settings in the VX8 everytime I use this setup.
>
>
Buit if you leave the T2 set up as a WIDE1, you will definitely be
"spamming" the network as you drive it around town. It will be a WIDE1-1
digi full time repeating every WIDE1-1 packet that it hears.  Not
recommended configuration.

Lynn (D) - KJ4ERJ - Watching this closely as I'd like to use my T2-135
as a local digi for my MT-300 on a bicycle!


> Thanks for the info, i think I was trying to make it more complex than it was
!
>
> Andrew
>
> --- In tracker2@yahoogroups.com, "Keith VE7GDH" <ve7gdh@...> wrote:
>
>> Andrew K1YMI / KC2EUS / GM1YMI wrote...
>>
>>
>>> This begs another question. If I enable as WIDE 2-1 or WIDE 1-1
>>> then it'll digi everything it hears, as long as they fit the WIDE n-N
>>> criteria.
>>>
>> If you enable it for WIDEn-N up to two hops, it would respond to anyone
>> using a path of WIDE2-2 or WIDE2-1 or WIDE1-1. If it was set up as a
>> fill-in digi only, it would only respond to WIDE1-1.
>>
>>
>>> Or is there a way to only digi my packets .. is this where the
>>> checkbox "digi on my call" comes into play ?
>>>
>> The "digi on my call" (the call in the T2) is one option. Another would
>> be to pick a non-standard alias for ALIAS 1 <alias> like...
>>
>> ALIAS 1 MEONLY
>>
>> and set a path of MEONLY in the VX-8R, or MEONLY,WIDE2-1 if you
>> hope another digi to pick you up after it goes through the T2. Of
>> course, if someone sees you being digi'd by MEONLY, there would be
>> nothing to stop them from using the path too.
>>
>> Yet another option... use a path of WIDE2-2,TEMP and enable TEMP as one
>> of the aliases in the T2 and turn PREEMPT ON for that alias. You would
>> get at least one hop from the T2 if it hears you. If it doesn't, there's
>> a chance you will be digi'd by any WIDEn-N digi that hears you.
>>
>> 73 es cul - Keith VE7GDH
>> --
>> "I may be lost, but I know exactly where I am!"
>>
>>

Andrew KC2EUS wrote...

> Ok I've got it now. If I set it to a fill-in with WIDE 1-1 I think I
> should be good. I was worried I was going to cause an issue with
> "spamming" the network. This was where the concern was coming from.
> Also if I leave it at WIDE 1-1 I don't have to mess around changing
> the default settings in the VX8 every time I use this setup. Thanks
> for the info, I think I was trying to make it more complex than it
> was !

Note... there isn't a space between "WIDE" and "1-1".

It's definitely good to think it through. Yes, setting it up as a
fill-in digi would have the advantage of not having to keep changing
the path in the VX-8R. If you have ALIAS 1 WIDE1 just remember to
turn it off with USEALIAS 1 OFF when it isn't needed.

That could be done from a Nuvi if you have one, or from a terminal
program or with otwincfg.exe, or even by sending a message from the
VX-8R when you get back to your vehicle... message to KC2EUS-9 (if
that's the call in the T2) cmd USEALIAS 1 OFF as long as your callsign
is in the AUTHLIST. Does the VX-8R allow you to save canned messages
for re-use? If so, you could have one to turn it on and one to turn it
off. Hmmm I wonder if a script could toggle the digi function based
on a switch connected to the accessory connector? Scott?

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

Yeah, this is my quandary .. It's not a problem to turn the digi on and off. I
can do that either via the Nuvi or canned messages in the VX8.
I just want to make sure my packets make it out of the area I'll be in.
I wonder for situations like this it's better to use TEMP or something like that
in the PATH. I don't have an issue with others using it.. I just don't want to
flood the network with extra traffic.
I guess I'm looking for the recommended configuration :)

Andrew

--- In tracker2@yahoogroups.com, "Lynn W. Deffenbaugh (Mr)"
> Buit if you leave the T2 set up as a WIDE1, you will definitely be
> "spamming" the network as you drive it around town. It will be a WIDE1-1
> digi full time repeating every WIDE1-1 packet that it hears.  Not
> recommended configuration.
>

So, wouldn't the solution to avoid spamming the network be:

1) turn off the Digi feature while driving and then turn it on when parked.

2) use a low-gain or directional antenna so that that the range of signals your
digi picks up is local. This will minimize what it hears to the area surrounding
your car. Pick an antenna gain that matches your local transmitter and the
surrounding area.

Another option would be to crank up the squelch so that only strong, local
signals are recieved.

3) use a high-power transmitter to kick the digipeated packets out to another
digipeater or iGate. Adjust the TX power so that the signal goes as far as it
needs to, but no more than it has to.

4) monitor the packets received to see if yours is among those digipeted by the
wide2 digi. If you use a WIDE1-1,WIDE2-1 path in your beacon (VX-8R) and a WIDE1
digi in your car, your digi should still hear the packets that have been
repeated by the WIDE2 digi, but it shouldn't repeat them. Or, you could have
someone watching the APRS-IS to see if your packets are showing up in the net.

5) if you want to be extra conscientious, you could test the area where you park
to see if there's already a WIDE1 digi that's covering where you are. e.g. see
if the packets sent by the VX-8R are being digipeated by another digipeater. If
so, leave your Digipeater off and use the existing one. If not, turn yours on
and then it can be the one to fill in wherever you are.

--bob
K7RBW


--- In tracker2@yahoogroups.com, "kc2eus" <kc2eus@...> wrote:
>
> Yeah, this is my quandary .. It's not a problem to turn the digi on and off. I
can do that either via the Nuvi or canned messages in the VX8.
> I just want to make sure my packets make it out of the area I'll be in.
> I wonder for situations like this it's better to use TEMP or something like
that in the PATH. I don't have an issue with others using it.. I just don't want
to flood the network with extra traffic.
> I guess I'm looking for the recommended configuration :)
>
> Andrew
>
> --- In tracker2@yahoogroups.com, "Lynn W. Deffenbaugh (Mr)"
> > Buit if you leave the T2 set up as a WIDE1, you will definitely be
> > "spamming" the network as you drive it around town. It will be a WIDE1-1
> > digi full time repeating every WIDE1-1 packet that it hears.  Not
> > recommended configuration.
> >
>

Yes, D4 is a bicolor, common-cathode LED.  It looks like I did include a
pull-up resistor for the CFG input on pin 34, but neglected to route it
to a convenient pad.  You can connect to pin 34, or to the resistor
(R29) immediately adjacent to it.

Scott

Mike wrote:
> Hello Scott,
> I'm going to place my T2-301 in another box with a Tx/Rx LED, a 'Beacon
> now' push button and profile select switch on the front.
>
> 1. Is D4 as marked on the T2 board a connection point for a Tx/Rx LED?
> 2. Is there a connection point for a profile switch or do I have to
> connect a wire direct to the processor chip, pin 34?
>
> TIA.
> Mike, VK2IN.
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

Lynn,

If you want to have your OT2 act as a personal digi, just set up an
alias that is unique, and turn on preemptive digipeating on that
alias.

In the HT, set your path to WIDE1-1,WIDE2-1,LYNN,WIDE2-1.

In the regular network, you'll get picked up by regular and fill-in
digis on the first hop. On the next hop, you'll get handled only by
WIDE digis. The next hop is your unique alias, which will cause an end
to the packet being handled.

When you are in the neighborhood of your personal digi, the OT2 will
preempt up to the LYNN alias, and then the next hop will be the final
WIDE2-1 in the list.

If you are in range of both your personal digi, and any other digi,
there should be no issues, as the main digipeater network will
anti-dupe no matter where it is handling the packet in the outgoing
paths.

James
VE6SRV



On 11/3/09, Lynn W. Deffenbaugh (Mr) <ldeffenb@...> wrote:
> kc2eus wrote:
>> Sorry for the double post last time. I did not think the first had gone
>> through.
>> Ok I've got it now. If I set it to a fill-in with WIDE 1-1 I think I
>> should be good.
>> I was worried I was going to cause an issue with "spamming" the network.
>> This was where the concern was coming from.
>> Also if I leave it at WIDE 1-1 I don't have to mess around changing the
>> default settings in the VX8 everytime I use this setup.
>>
>>
> Buit if you leave the T2 set up as a WIDE1, you will definitely be
> "spamming" the network as you drive it around town. It will be a WIDE1-1
> digi full time repeating every WIDE1-1 packet that it hears.  Not
> recommended configuration.
>
> Lynn (D) - KJ4ERJ - Watching this closely as I'd like to use my T2-135
> as a local digi for my MT-300 on a bicycle!
>
>
>> Thanks for the info, i think I was trying to make it more complex than it
>> was !
>>
>> Andrew
>>
>> --- In tracker2@yahoogroups.com, "Keith VE7GDH" <ve7gdh@...> wrote:
>>
>>> Andrew K1YMI / KC2EUS / GM1YMI wrote...
>>>
>>>
>>>> This begs another question. If I enable as WIDE 2-1 or WIDE 1-1
>>>> then it'll digi everything it hears, as long as they fit the WIDE n-N
>>>> criteria.
>>>>
>>> If you enable it for WIDEn-N up to two hops, it would respond to anyone
>>> using a path of WIDE2-2 or WIDE2-1 or WIDE1-1. If it was set up as a
>>> fill-in digi only, it would only respond to WIDE1-1.
>>>
>>>
>>>> Or is there a way to only digi my packets .. is this where the
>>>> checkbox "digi on my call" comes into play ?
>>>>
>>> The "digi on my call" (the call in the T2) is one option. Another would
>>> be to pick a non-standard alias for ALIAS 1 <alias> like...
>>>
>>> ALIAS 1 MEONLY
>>>
>>> and set a path of MEONLY in the VX-8R, or MEONLY,WIDE2-1 if you
>>> hope another digi to pick you up after it goes through the T2. Of
>>> course, if someone sees you being digi'd by MEONLY, there would be
>>> nothing to stop them from using the path too.
>>>
>>> Yet another option... use a path of WIDE2-2,TEMP and enable TEMP as one
>>> of the aliases in the T2 and turn PREEMPT ON for that alias. You would
>>> get at least one hop from the T2 if it hears you. If it doesn't, there's
>>> a chance you will be digi'd by any WIDEn-N digi that hears you.
>>>
>>> 73 es cul - Keith VE7GDH
>>> --
>>> "I may be lost, but I know exactly where I am!"
>>>
>>>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

James,

Wonderfully concise and complete!  Thank you so much for the
clarification.  I would have messed up the path by not putting the
WIDE2-1 after the LYNN which is after the path that I'd really like
handled by the normal network.

It would seem that this solution would also work for KC2EUS and his
VX8R, right?

Lynn (D) - KJ4ERJ - Wanting to resurrect my MT-300 on a pocket J-Pole
for bicycling

James Ewen wrote:
> Lynn,
>
> If you want to have your OT2 act as a personal digi, just set up an
> alias that is unique, and turn on preemptive digipeating on that
> alias.
>
> In the HT, set your path to WIDE1-1,WIDE2-1,LYNN,WIDE2-1.
>
> In the regular network, you'll get picked up by regular and fill-in
> digis on the first hop. On the next hop, you'll get handled only by
> WIDE digis. The next hop is your unique alias, which will cause an end
> to the packet being handled.
>
> When you are in the neighborhood of your personal digi, the OT2 will
> preempt up to the LYNN alias, and then the next hop will be the final
> WIDE2-1 in the list.
>
> If you are in range of both your personal digi, and any other digi,
> there should be no issues, as the main digipeater network will
> anti-dupe no matter where it is handling the packet in the outgoing
> paths.
>
> James
> VE6SRV
>
>
>
> On 11/3/09, Lynn W. Deffenbaugh (Mr) <ldeffenb@...> wrote:
>
>> kc2eus wrote:
>>
>>> Sorry for the double post last time. I did not think the first had gone
>>> through.
>>> Ok I've got it now. If I set it to a fill-in with WIDE 1-1 I think I
>>> should be good.
>>> I was worried I was going to cause an issue with "spamming" the network.
>>> This was where the concern was coming from.
>>> Also if I leave it at WIDE 1-1 I don't have to mess around changing the
>>> default settings in the VX8 everytime I use this setup.
>>>
>>>
>>>
>> Buit if you leave the T2 set up as a WIDE1, you will definitely be
>> "spamming" the network as you drive it around town. It will be a WIDE1-1
>> digi full time repeating every WIDE1-1 packet that it hears.  Not
>> recommended configuration.
>>
>> Lynn (D) - KJ4ERJ - Watching this closely as I'd like to use my T2-135
>> as a local digi for my MT-300 on a bicycle!
>>
>>
>>
>>> Thanks for the info, i think I was trying to make it more complex than it
>>> was !
>>>
>>> Andrew
>>>
>>> --- In tracker2@yahoogroups.com, "Keith VE7GDH" <ve7gdh@...> wrote:
>>>
>>>
>>>> Andrew K1YMI / KC2EUS / GM1YMI wrote...
>>>>
>>>>
>>>>
>>>>> This begs another question. If I enable as WIDE 2-1 or WIDE 1-1
>>>>> then it'll digi everything it hears, as long as they fit the WIDE n-N
>>>>> criteria.
>>>>>
>>>>>
>>>> If you enable it for WIDEn-N up to two hops, it would respond to anyone
>>>> using a path of WIDE2-2 or WIDE2-1 or WIDE1-1. If it was set up as a
>>>> fill-in digi only, it would only respond to WIDE1-1.
>>>>
>>>>
>>>>
>>>>> Or is there a way to only digi my packets .. is this where the
>>>>> checkbox "digi on my call" comes into play ?
>>>>>
>>>>>
>>>> The "digi on my call" (the call in the T2) is one option. Another would
>>>> be to pick a non-standard alias for ALIAS 1 <alias> like...
>>>>
>>>> ALIAS 1 MEONLY
>>>>
>>>> and set a path of MEONLY in the VX-8R, or MEONLY,WIDE2-1 if you
>>>> hope another digi to pick you up after it goes through the T2. Of
>>>> course, if someone sees you being digi'd by MEONLY, there would be
>>>> nothing to stop them from using the path too.
>>>>
>>>> Yet another option... use a path of WIDE2-2,TEMP and enable TEMP as one
>>>> of the aliases in the T2 and turn PREEMPT ON for that alias. You would
>>>> get at least one hop from the T2 if it hears you. If it doesn't, there's
>>>> a chance you will be digi'd by any WIDEn-N digi that hears you.
>>>>
>>>> 73 es cul - Keith VE7GDH
>>>> --
>>>> "I may be lost, but I know exactly where I am!"
>>>>
>>>>
>>>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>>
>>
>>
>>
>>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
>

It will work for anyone wanting to have a helper digi for themselves.
Just choose an alias that is not normally used by the network.



On 11/3/09, Lynn W. Deffenbaugh (Mr) <ldeffenb@...> wrote:
> James,
>
> Wonderfully concise and complete!  Thank you so much for the
> clarification.  I would have messed up the path by not putting the
> WIDE2-1 after the LYNN which is after the path that I'd really like
> handled by the normal network.
>
> It would seem that this solution would also work for KC2EUS and his
> VX8R, right?
>
> Lynn (D) - KJ4ERJ - Wanting to resurrect my MT-300 on a pocket J-Pole
> for bicycling
>
> James Ewen wrote:
>> Lynn,
>>
>> If you want to have your OT2 act as a personal digi, just set up an
>> alias that is unique, and turn on preemptive digipeating on that
>> alias.
>>
>> In the HT, set your path to WIDE1-1,WIDE2-1,LYNN,WIDE2-1.
>>
>> In the regular network, you'll get picked up by regular and fill-in
>> digis on the first hop. On the next hop, you'll get handled only by
>> WIDE digis. The next hop is your unique alias, which will cause an end
>> to the packet being handled.
>>
>> When you are in the neighborhood of your personal digi, the OT2 will
>> preempt up to the LYNN alias, and then the next hop will be the final
>> WIDE2-1 in the list.
>>
>> If you are in range of both your personal digi, and any other digi,
>> there should be no issues, as the main digipeater network will
>> anti-dupe no matter where it is handling the packet in the outgoing
>> paths.
>>
>> James
>> VE6SRV
>>
>>
>>
>> On 11/3/09, Lynn W. Deffenbaugh (Mr) <ldeffenb@...> wrote:
>>
>>> kc2eus wrote:
>>>
>>>> Sorry for the double post last time. I did not think the first had gone
>>>> through.
>>>> Ok I've got it now. If I set it to a fill-in with WIDE 1-1 I think I
>>>> should be good.
>>>> I was worried I was going to cause an issue with "spamming" the network.
>>>> This was where the concern was coming from.
>>>> Also if I leave it at WIDE 1-1 I don't have to mess around changing the
>>>> default settings in the VX8 everytime I use this setup.
>>>>
>>>>
>>>>
>>> Buit if you leave the T2 set up as a WIDE1, you will definitely be
>>> "spamming" the network as you drive it around town. It will be a WIDE1-1
>>> digi full time repeating every WIDE1-1 packet that it hears.  Not
>>> recommended configuration.
>>>
>>> Lynn (D) - KJ4ERJ - Watching this closely as I'd like to use my T2-135
>>> as a local digi for my MT-300 on a bicycle!
>>>
>>>
>>>
>>>> Thanks for the info, i think I was trying to make it more complex than
>>>> it
>>>> was !
>>>>
>>>> Andrew
>>>>
>>>> --- In tracker2@yahoogroups.com, "Keith VE7GDH" <ve7gdh@...> wrote:
>>>>
>>>>
>>>>> Andrew K1YMI / KC2EUS / GM1YMI wrote...
>>>>>
>>>>>
>>>>>
>>>>>> This begs another question. If I enable as WIDE 2-1 or WIDE 1-1
>>>>>> then it'll digi everything it hears, as long as they fit the WIDE n-N
>>>>>> criteria.
>>>>>>
>>>>>>
>>>>> If you enable it for WIDEn-N up to two hops, it would respond to anyone
>>>>> using a path of WIDE2-2 or WIDE2-1 or WIDE1-1. If it was set up as a
>>>>> fill-in digi only, it would only respond to WIDE1-1.
>>>>>
>>>>>
>>>>>
>>>>>> Or is there a way to only digi my packets .. is this where the
>>>>>> checkbox "digi on my call" comes into play ?
>>>>>>
>>>>>>
>>>>> The "digi on my call" (the call in the T2) is one option. Another would
>>>>> be to pick a non-standard alias for ALIAS 1 <alias> like...
>>>>>
>>>>> ALIAS 1 MEONLY
>>>>>
>>>>> and set a path of MEONLY in the VX-8R, or MEONLY,WIDE2-1 if you
>>>>> hope another digi to pick you up after it goes through the T2. Of
>>>>> course, if someone sees you being digi'd by MEONLY, there would be
>>>>> nothing to stop them from using the path too.
>>>>>
>>>>> Yet another option... use a path of WIDE2-2,TEMP and enable TEMP as one
>>>>> of the aliases in the T2 and turn PREEMPT ON for that alias. You would
>>>>> get at least one hop from the T2 if it hears you. If it doesn't,
>>>>> there's
>>>>> a chance you will be digi'd by any WIDEn-N digi that hears you.
>>>>>
>>>>> 73 es cul - Keith VE7GDH
>>>>> --
>>>>> "I may be lost, but I know exactly where I am!"
>>>>>
>>>>>
>>>>>
>>>
>>> ------------------------------------
>>>
>>> Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>>
>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>>
>>
>>
>>
>>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

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

From: Scott Miller

To: tracker2@yahoogroups.com

Sent: Monday, September 14, 2009 2:33 AM

Subject: Re: [tracker2] Tracker2/Display & poor decoding

 

Yes, and yes.

Scott

Mike Zwingl oe3mzc wrote:
>
>
> Scott,
> I guess you are talking abt C13 and C17 ?
>
> When you replace them, do you see improved decoding?
>
> sorry for the hassel.
> vy 73 de Mike
> oe3mzc
>
>
>
> ----- Original Message -----
> *From:* Scott Miller <mailto:scott@opentrac.org>
> *To:* tracker2@yahoogroups.com <mailto:tracker2@yahoogroups.com>
> *Sent:* Sunday, September 13, 2009 4:42 AM
> *Subject:* Re: [tracker2] Tracker2/Display & poor decoding
>
>
>
> Hi Mike,
>
> I'm kind of fed up with the 2211 myself. I've been doing a lot more
> testing on the OT2ms before they ship these days, and a significant
> portion of them need to have the 0.027 uF capacitors replaced before
> they ship. I'm not sure the batch sent to the contract manufacturer is
> really meeting specs.
>
> I haven't run into any that didn't get up to par with the capacitor
> replacement and a thorough cleaning of flux residue. Still, it's a lot
> of hassle. I've got a few boards on the way to test a new MX614-based
> layout. When those come in (sometime late in the week) I'll start doing
> some side by side comparisons. Assuming I can get my crashed workbench
> PC up and running again. I already bought a replacement, but I can't
> run the software I need under Vista, and I can't get the machine to
> load
> XP Pro.
>
> Scott
>
> Mike Zwingl oe3mzc wrote:
> >
> >
> > Hi,
> > we have exactly the same problem and we are no newbies to packet
> radio
> > modems.
> > The XR2211 decoder should perform much better, than it sometimes
> does in
> > OT2m.
> > This modem chip is also used in some other tncs...
> > but I did not change it for an TCM3105 or similar in the OT2m -so
> far no
> > time to test this...
> > However we observe many OT2m units, that show POOR DECODE on
> 1200baud on
> > different radios and locations.
> > Some only decode less than one third of all heard packets..we do not
> > know why...
> > However, we have also seen some OT2m units that do significantly
> better
> > than that, running same firmware.
> > We are also aware of the wrong capacitor in the audio filter
> circuit of
> > some OT2m serial No. batches, but even if we soldered the correct C
> > it is still showing very odd effects with poor decode and digipeater
> > performance.
> > We would be glad to have some solution offered, since OT2m is
> starting
> > to get widely used in our national APRS network as an intelligent
> > digipeater
> > or replacing old tncs, that could not do the NEWn-n paradigm.
> >
> > hw?
> > vy 73 de Mike
> > oe3mzc
> >
> >
> >
> > ----- Original Message -----
> > *From:* Mark Cheavens <mailto:mcheavens@usa.net
> <mailto:mcheavens%40usa.net>>
> > *To:* tracker2@yahoogroups.com
> <mailto:tracker2%40yahoogroups.com> <mailto:tracker2@yahoogroups.com
> <mailto:tracker2%40yahoogroups.com>>
> > *Sent:* Thursday, September 10, 2009 3:31 PM
> > *Subject:* Re: [tracker2] Tracker2/Display & decoding
> >
> >
> >
> > With the modem chip used it is rare that a "weak" or "noisy" signal
> > will get decoded. Is the audio "packet" 9600, 1200, or speaker audio?
> >
> > With 1200 baud packet you need to have de-emphasized (sp?) audio to
> > the modem (TNC). Speaker audio DOES have de-emphasis, as should a
> > "1200" baud port of the radio.
> >
> > (FYI- 9600 had NO pre- or de- emphasis)
> >
> > Just because you can HEAR a packet, does not mean the TNC can decode
> > it. The signal to noise radio need to have a LOT of signal, and VERY
> > little noise.
> >
> > Mark
> > KC5EVE
> >
> >
> > At 01:02 AM 9/10/2009, you wrote:
> >
> >>
> >>
> >> Hi there,
> >>
> >> I've Tracker2 connected to a Nuvi350 and was wondering why
> >> sometime it
> >> took a while before I could see some of the callsigns get into the
> >> Favorite (after I did a delete all). So, I added an LCD display
> to my
> >> Tracker2 yesterday and found out that most of the time, Tracker2
> >> couldn't decode the packets (i.e. not displayed on the LCD)
> >> especially
> >> the weak ones. Now I'm wondering what else I need to do ..
> Anyway, my
> >> setup is .. Kenwood TMV71A/Data/BandB <-> Tracker2 with LCD <->
> Nuvi.
> >> I brewed my own cable between the TMV71A and the Tracker2.. sending
> >> packet out does not seem to be a problem. Is there anything in the
> >> configuration that I need to do?
> >>
> >> TIA,
> >> Mohd/9W2TPT
> >
> >
>
>

> It will work for anyone wanting to have a helper digi for themselves.
> Just choose an alias that is not normally used by the network.

This might also be an opportunity to use the TEMP alias ..   That's
essentially what it's for.

Bill - WA7NWP

If everyone uses TEMP, then you no longer limit the digipeating to
your own packets only. I was going to suggest TEMP first, but the
request was to limit who would be digipeated.

One needs to be prepared to explain the abnormal path to those who
don't know about preemptive digipeating, and will try to tell you that
you are using a goofy path.



On 11/3/09, Bill V WA7NWP <wa7nwp@...> wrote:
>> It will work for anyone wanting to have a helper digi for themselves.
>> Just choose an alias that is not normally used by the network.
>
> This might also be an opportunity to use the TEMP alias ..   That's
> essentially what it's for.
>
> Bill - WA7NWP
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

The biggest problem for me with VP2 troubleshooting is that I don't have
one here to test with.  This might be the same problem as the Peet Bros
thing, so I'm going to work on that first.  It seems to be timing
dependent, and it's hard to duplicate on the bench.

Scott

pruittn2 wrote:
>
>
> A friend and I have set up a remote APRS weather station using the
> tracker2 w/ 09022009 firmware and a Davis VP2 wx station.  We are seeing
> occasional packets with incorrect temp, humidity and/or rain data.  The
> tracker is setup to transmit a weather packet every 5 mins.  We have
> seen about 30 incorrect packets today.  There is no indication of data
> errors in the VP2 console.  The incorrect temp value has always been
> 3277.  Anyone seen this before? Scott, what other information is needed
> to help troubleshoot this issue.  Below are some example packets from
> Findu.com
>
>
W4SNA-2>APOT21,KI4WXS-9*,WIDE2-1,qAR,WA4SAS-11:>!3622.65N/08021.86W_PHG5750/W1,
> WX Sauratown Mtn, NC
> W4SNA-2>APOT21,WIDE2-2,qAR,WD4LSS:!3622.65N/08021.86W_ 14.0V 84F
>
W4SNA-2>APOT21,WX4GSO*,qAR,WW4FL-1:!3622.65N/08021.86W_042/003g...t053p000h58b10\
203T2WX
> W4SNA-2>APOT21,WIDE2-2,qAR,W4DEX:!3622.65N/08021.86W_ 14.0V 85F
>
W4SNA-2>APOT21,WIDE2-2,qAR,W4DEX:!3622.65N/08021.86W_092/003g...t053p000h13b1020\
4T2WX
> W4SNA-2>APOT21,KI4WXS-5*,WIDE2-1,qAR,WA4SAS-11:!3622.65N/08021.86W_
> 14.0V 85F
>
W4SNA-2>APOT21,KI4WXS-5*,WIDE2-1,qAR,WA4SAS-11:!3622.65N/08021.86W_092/003g...t0\
53p000h13b10204T2WX
> W4SNA-2>APOT21,WIDE2-2,qAR,WW4FL-1:!3622.65N/08021.86W_ 14.0V 85F
>
W4SNA-2>APOT21,WIDE2-2,qAR,WD4LSS:!3622.65N/08021.86W_065/003g...t053p32556h00b1\
0204T2WX
> W4SNA-2>APOT21,WIDE2-2,qAR,WW4FL-1:!3622.65N/08021.86W_ 14.0V 84F
>
W4SNA-2>APOT21,WIDE2-2,qAR,W4DEX:!3622.65N/08021.86W_018/003g...t053p000h59b1020\
4T2WX
> W4SNA-2>APOT21,KI4WXS-9*,WIDE2-1,qAR,WA4SAS-11:!3622.65N/08021.86W_
> 14.0V 84F
>
W4SNA-2>APOT21,KI4WXS-9*,WIDE2-1,qAR,WA4SAS-11:!3622.65N/08021.86W_018/003g...t0\
53p000h59b10204T2WX
> W4SNA-2>APOT21,WIDE2-2,qAR,WD4LSS:!3622.65N/08021.86W_ 14.0V 84F
>
W4SNA-2>APOT21,WIDE2-2,qAR,WD4LSS:!3622.65N/08021.86W_027/003g...t053p000h59b102\
03T2WX
> W4SNA-2>APOT21,WIDE2-2,qAR,WW4FL-1:!3622.65N/08021.86W_ 14.0V 84F
>
W4SNA-2>APOT21,WIDE2-2,qAR,WW4FL-1:!3622.65N/08021.86W_044/003g...t053p000h57b10\
203T2WX
> W4SNA-2>APOT21,KI4WXS-5*,WIDE2-1,qAR,WA4SAS-11:!3622.65N/08021.86W_
> 14.0V 85F
> W4SNA-2>APOT21,KI4WXS-5,K4FI-3,WIDE2*,qAS,N2ZZ-5:!3622.65N/08021.86W_
> 14.0V 85F
> W4SNA-2>APOT21,WIDE2-2,qAR,W4DEX:!3622.65N/08021.86W_ 14.0V 85F
>
W4SNA-2>APOT21,WIDE2-2,qAR,WD4LSS:!3622.65N/08021.86W_031/003g...t3277p000h55b10\
203T2WX
> W4SNA-2>APOT21,KI4WXS-9*,WIDE2-1,qAR,WA4SAS-11:!3622.65N/08021.86W_
> 14.0V 85F
> W4SNA-2>APOT21,WIDE2-2,qAR,W4DEX:>!3622.65N/08021.86W_PHG5750/W1, WX
> Sauratown Mtn, NC
>
W4SNA-2>APOT21,WIDE2-2,qAR,WD4LSS:!3622.65N/08021.86W_116/003g...t053p000h58b102\
03T2WX
> W4SNA-2>APOT21,WIDE2-2,qAR,WW4FL-1:!3622.65N/08021.86W_ 14.0V 85F
>
> Neal - WD4LSS
>
>

Hi all

anyone have connected an old TR-2500 portable over an OT1 ?

i have found the speaker,the mic audio but i cannot figure out how too
connect the ptt??

maybe a drawn diagramm would be great for me

thanks again

gervais ve2ckn