Sorry for the confusion, but on page 23 is an image of the config program Tuning
and Diagnostics window that includes a slider whose label reads: Transmit Audio
Level.

But on page 16 there is an image of the main config window that includes a
slider whose label reads:  TX Audio Level.

Which one are we referring to (assuming we're referring to one of those)?


--- In tracker2@yahoogroups.com, Tom Hayward <tom@...> wrote:
>
> On Wed, Aug 29, 2012 at 9:54 AM, kc2yu <jrskoler@...> wrote:
> > --- In tracker2@yahoogroups.com, Tom Hayward <tom@> wrote:
> > > > 2) Will I need to "tune" the unit's Transmit Audio Level?
> > >
> > > Yes... the proper way is with a service monitor, but you can fake it
> > > by listening to the signal (with an HT, etc) while turning down the
> > > gain. When the volume starts to decrease, turn it down a bit more and
> > > leave it there.
> >
> > No service monitor, but plenty of other rigs to listen in.
> >
> > Just to be clear, the gain you refer to is the audio level, right?
> >
> > I hope my ears are trained enough to hear this properly (;-)
>
> I'm referring to the transmit audio gain. This is adjusted with a
> slider in otwincfg.exe. You can tell otwincfg.exe to transmit with
> both tones while adjusting the slider (page 21 of the Tracker2 manual). Please
> don't do this on 144.39 ;-)
>
> If the slider is at the top of the range and audio is still low, you
> may need to set the HI jumper (page 7 of the Tracker2 manual).
>
> Tom KD7LXL
>

Thanks for everyones' input.
For those familiar with the area, I am near Tatla Lake BC half way between
Williams Lake and Bella Coola.
For the time being, I did indeed change the input frequency, which is fine for
locals who know ( VE7SML-1) but not so good for visiting hams, although the
output is on 144.39. However one would have to read the message, reprogram the
radio etc which is a bit of a hassle.
I will have to re-read everything and try and digest it a bit.
As an aside, is there an advantage to forcing the same path to the igate with
something like
PATH wide1-1, Fishpot,Smokey,WilliamsLake ( where the igate is) ?
where those would be the digis that are hopped to each time to get to the igate.
Thanks
Mike

On Wed, Aug 29, 2012 at 1:07 PM, kc2yu <jrskoler@...> wrote:
>
> Sorry for the confusion, but on page 23 is an image of the config program
> Tuning and Diagnostics window that includes a slider whose label reads:
> Transmit Audio Level.
>
> But on page 16 there is an image of the main config window that includes a
> slider whose label reads: TX Audio Level.
>
> Which one are we referring to (assuming we're referring to one of those)?

They are pages 14 and 21 here:
https://www.argentdata.com/support/tracker2_manual.pdf

and those are both the same parameter, just two different places to
change it. Sliding one will change the other.

Tom KD7LXL

On Wed, Aug 29, 2012 at 12:59 PM, James Ewen <ve6srv@...> wrote:
>
> Also look at using alternate paths where your second path is blank.
> This will also reduce the load you put on the network. One position
> report would go out via WIDE2-1, and the next just direct.
>
> This keeps the digi showing up on the map of those local every 10
> minutes, and those further away will hear from it every 20 minutes.

I forget... is there a way to do this without writing to flash? How do
you do it?

I assume using a script to change the PATH variable would write to flash.

Tom KD7LXL

I see the problem -- you're looking at the ot2 and I'm looking at the ot3
manual, here:

http://www.argentdata.com/support/tracker3_manual.pdf

both sliders do the same thing -- got it.

Thanks again!

--- In tracker2@yahoogroups.com, Tom Hayward <tom@...> wrote:
>
> On Wed, Aug 29, 2012 at 1:07 PM, kc2yu <jrskoler@...> wrote:
> >
> > Sorry for the confusion, but on page 23 is an image of the config program
> > Tuning and Diagnostics window that includes a slider whose label reads:
> > Transmit Audio Level.
> >
> > But on page 16 there is an image of the main config window that includes a
> > slider whose label reads: TX Audio Level.
> >
> > Which one are we referring to (assuming we're referring to one of those)?
>
> They are pages 14 and 21 here:
> https://www.argentdata.com/support/tracker2_manual.pdf
>
> and those are both the same parameter, just two different places to
> change it. Sliding one will change the other.
>
> Tom KD7LXL
>

Pete KC0GPB wrote...

> I'm running mobile a T2-135 connected to a Nuvi 350. A couple
> of times over the last couple of months I've had an issue with what
> seems to me the DR-135 sending 'dirty' packets...

Could it be an RF issue? How much power is the radio running? Any
chance the SWR has gone high and there's lots of RF floating around
inside the radio where the T2-135 is located? You could try the radio
on low power for a while and see if the problem only occurs when the
power is cranked up.

However, you said that you had "fixed" it on previous occasions
by re-loading the settings into the T2-135. Was the radio on the
usual antenna at the time, or perhaps on one with a good match,
or even a dummy load while it was on the bench? Again, just
wondering if it's an RF issue or if it's something else. I usually
run a DR-136T on medium power with a T2-135 inside it, but it
is sometimes used on high power.

Would it be worth popping the lid on the radio and making sure
the T2-135 is properly seated in the connector in the radio?

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

I'm not sure what daughterboard you're using (maybe one of Sparkfun's
BlueSmirfs?), but you will need to do RS-232 to TTL conversion for the Tracker
to talk to the RN-42 unless you tap in to the TTL lines on the Tracker 3 PCB.
Should work fine once you do that though.

- Cai /W6CAI

--- In tracker2@yahoogroups.com, "kb1wxd_andrew" <mechcondrid@...> wrote:
>
> ok if your reasonably sure on the voltage then i'm good
> the bt module (RN-42) is actually on a near same footprint daughter board that
converts everything from a range of 3v to 6v in terms of both power and signal
(so it's good up to 5.5v peak) not to mention its pretty damn cheap ($40) and
sold and made in the US

On Wed, Aug 29, 2012 at 3:31 PM, kc2yu <jrskoler@...> wrote:
>
> I see the problem -- you're looking at the ot2 and I'm looking at the ot3
> manual, here:
>
> http://www.argentdata.com/support/tracker3_manual.pdf
>
> both sliders do the same thing -- got it.
>
> Thanks again!

Ah, excellent, I didn't know this existed. I thought the Tracker3 docs
were wiki-only for now. Anyway, the features we're talking about are
identical on the Tracker2 and Tracker3.

Tom KD7LXL

On Wed, Aug 29, 2012 at 2:37 PM, mooksmd2005 <mikesmi@...> wrote:

> For the time being, I did indeed change the input frequency, which is fine for
locals
> who know ( VE7SML-1) but not so good for visiting hams, although the output
> is on 144.39. However one would have to read the message, reprogram the radio
> etc which is a bit of a hassle.

And it still leaves you as an outbound digipeater only. You have
effectively cut yourself off from ALL outside communications. Anyone
outside of the local digipeater coverage area can NOT get packets back
to you.

You've got the digipeater input nice and quiet, but at what cost?

> I will have to re-read everything and try and digest it a bit.

There's a bit to digest and understand, for sure.

> As an aside, is there an advantage to forcing the same path to the
> igate with something like PATH wide1-1, Fishpot,Smokey,WilliamsLake
> ( where the igate is) ?

Well, if you're going to do that, why not use PUNTZI,FISHPT,SMOKEY?

You're going t have to get into PUNTZI to get to FISHPT, right? You
only have the one digipeater local to you. If you have a home station
supporting WIDE1-1, can it be heard by FISHPT? If not, and you want to
use the fill-in as a helper, then WIDE1-1,FISHPT won't work because
PUNTZI is not in the list. When you specify digipeaters by name, each
digipeater HAS to act upon the packet at the designated place in the
line. Using generic paths allows ANY digipeater to act upon the hop
request.

When you specify an exact path, each digipeater has to be able to hear
the previous one in the list. If there's a packet collision or such,
the packet dies right there. If the path is generic, the packet has
the option of being heard and handled by any digipeater in range.

An exact path keeps the packet from spreading far and wide, and is
frugal in network resource usage, but relies on everything working
perfectly.

You do not have to name the i-gate station. i-gates do not digipeat
(unless it is a combined i-gate/digipeater). All you need to do is get
your packet digipeated by a digipeater that can be heard by the
i-gate.

Again, remember that this concept that you have developed is good for
getting a track showing up at aprs.fi, but it is useless for
bi-directional communications.

It's up to you what you build, as you are the ultimate user of the
system... I'm just pointing out the limitations in case you haven't
noticed them yet.

--
James
VE6SRV

On Wed, Aug 29, 2012 at 1:13 PM, kc2yu <jrskoler@...> wrote:

>> As for your outgoing path, it is best to set that to 1 hop less than
>> the local recommended max hops.
>
> Understood.  I actually just read this in an APRS theory paper and was
> impressed by it's obviousness -- that is, I was surprised that I didn't
> intuitively understand this all on my own.

Don't feel silly... there are people out there using WIDE4-4 because
they would like the 4 closest digipeaters to act on their packet, or
worse. When you plot out the local digipeater mesh, and put a pin in
at a digipeater that can hear you direct, and then another colour pin
at ALL the digipeaters that can hear that digi, you can get an idea of
just how much area your packet can affect. Do that for each digipeater
that can hear you direct. If you start from a digipeater, you're
already at that first pin, so two hops is effectively 3 for the
regular users.

>> Also look at using alternate paths where your second path is blank.
>> This will also reduce the load you put on the network. One position
>> report would go out via WIDE2-1, and the next just direct.
>>
>> This keeps the digi showing up on the map of those local every 10
>> minutes, and those further away will hear from it every 20 minutes.
>
> That's very cool. I didn't know it could do that.  I saw the 2-profile
> capability and didn't focus on it, assuming I had no use for it.

It's not making use of profile switching... select alternate paths on
your primary profile. All that it will do is use the path from the
primary profile, and then use the path from the secondary profile on
each alternate beacon. There's nothing to do with the other profile
other than the program looks to see what path you have there.

Again, just optimizing the operation of the digipeater.

As a primary infrastructure element, it behooves the digipeater
operator to understand the impacts of the operation of that station,
and to do all he/she can to ensure that the digipeater creates as
little impact on the RF network as possible, while still fulfilling
the key role that it plays.

--
James
VE6SRV

On Wed, Aug 29, 2012 at 3:04 PM, Tom Hayward <tom@...> wrote:

>> Also look at using alternate paths where your second path is blank.
>> This will also reduce the load you put on the network. One position
>> report would go out via WIDE2-1, and the next just direct.
>>
>> This keeps the digi showing up on the map of those local every 10
>> minutes, and those further away will hear from it every 20 minutes.
>
> I forget... is there a way to do this without writing to flash? How do
> you do it?

Yup, look for the check box right next to the path labelled alternate paths.

> I assume using a script to change the PATH variable would write to flash.

Yup, a less than desirable course of action. This option allows for 2
paths to be used. Scott has an outstanding request for the ability to
specify the path for an outbound packet without having to write to
flash... That would open up a world of possibilities. I would like
more than 2 paths available, but 2 is better than 1.

--
James
VE6SRV

Dear all,

on the USB port of T3-135 board, is there 5V available? or is it data only (D+,
D-, and ground).

73 de Paulus - N5SNN / YD0NXX

APRS up and running with the Tracker 3 and Nuvi 350. Installed Windows INF file,
otwincfg.exe utility, read the Tracker 3 manual, all is well in APRS land.
Thanks, Ron

--- In tracker2@yahoogroups.com, Tony VE6MVP <tony@...> wrote:
>
> At 09:44 PM 2012-08-26, roadtoscituate wrote:
>
> Whoops.  My apologies.  I'm running the Tracker2 in my T2-301 so
> there might be significant differences.   A USB port will simplify
> things in the OT3.   And I see a note that states the GTRANS
> translation cable isn't needed either which I think I have for the
> OT2 if I recall correctly.
>
> Tony
>
> >Well, after reading the Tracker 3 Manual :) Port Mode selection and
> >Profiles etc., won't happen until I connect the OT3M to a PC and use
> >a config utility such as otwincfg.exe. I'll give it a try and get
> >back to you. The rear panel of the OT3m includes a standard USB 'B'
> >connector just for that purpose I think. Ron
> >
> >--- In <mailto:tracker2%40yahoogroups.com>tracker2@yahoogroups.com,
> >Tony VE6MVP <tony@> wrote:
> > >
> > > At 04:11 PM 2012-08-26, Lynn W. Deffenbaugh (Mr) wrote:
> > >
> > > >Is the OT3m port to which the FMI cable is connected set to GARMIN
> > > >mode? AFAIK, the "Dispatch" menu shows up the first time the Nuvi
> > > >detects an FMI host like the OT3m. I'm not sure just the attached cable
> > > >will do it. I think it actually has to hear FMI protocol over that cable.
> > >
> > > It's also my understanding that you have to have the appropriate
> > > Tracker port set to Garmin mode and the Tracker powered on. Then
> > > power on the Nuvi 360 GPS so it detects the Garmin signal on power
> > > up. But once you've set it to Dispatch mode it will stay in Dispatch
> > > mode no matter which is powered on first. Until you clear all the
> > > data in the Garmin somehow.
> > >
> > > Given a choice I'd suggest using the Y serial cable as available from
> > > Argent and setting port B to Garmin. Then you can still attach a PC
> > > to port A if desired. It's also easier to program the tracker as
> > > I've recently discovered when I set port A to Garmin mode. <smile>
> > >
> > > Tony
> > >
> >
> >
>

--- In tracker2@yahoogroups.com, James Ewen <ve6srv@...> wrote:

> Don't feel silly... there are people out there using WIDE4-4 because
> they would like the 4 closest digipeaters to act on their packet, or
> worse.

Great idea, thanks!

What I'll do is make my digi beacon every 10 seconds with a WIDE7-7 path because
I really, really, really want everyone in North America to know I'm here -- and
it's so much easier than having a QSO (;-).

(Please everyone stay calm, I'm just kidding.)


>When you plot out the local digipeater mesh, and put a pin in
> at a digipeater that can hear you direct, and then another colour pin
> at ALL the digipeaters that can hear that digi, you can get an idea of
> just how much area your packet can affect. Do that for each digipeater
> that can hear you direct. If you start from a digipeater, you're
> already at that first pin, so two hops is effectively 3 for the
> regular users.

That's yet another interesting way to look at it.  I think what this describes
is the number of stations hearing my digi starts growing geometrically one hop
sooner than a mobile's station, resulting in each hop have a greater affect.

That is (for example, a WIDE3-3), a mobile might be heard by 1 digi (DIGI-A),
and that digi by 2 other digis (DIGI-B and DIGI-C), which each are heard by 2
digis (DIGI-D, DIGI-E, DIGI-F, DIGI-G).  This results in the mobile station
being heard by (and digipeated by) 7 digis.

Whereas, the same 3 hops starting from a digi results in being heard by 2 digis
initially (DIGI-A, DIGI-B), then 4 more digis (DIGI-C, DIGI-D, DIGI-E, DIGI-F),
then 8 more digis (DIGI-G, H, I, J, K, L, M, N).  That's 14 digis.

Is this correct?


> [Alternating paths is] not making use of profile switching... select alternate
paths on
> your primary profile. All that it will do is use the path from the
> primary profile, and then use the path from the secondary profile on
> each alternate beacon. There's nothing to do with the other profile
> other than the program looks to see what path you have there.

I see -- it doesn't switch profiles, it just switches which profile's path is
used.  So the 2 profile paths can be WIDE2-2 and blank, or WIDE2-2 and WIDE4-4,
for example.


> As a primary infrastructure element, it behooves the digipeater
> operator to understand the impacts of the operation of that station,
> and to do all he/she can to ensure that the digipeater creates as
> little impact on the RF network as possible, while still fulfilling
> the key role that it plays.

I do hope I will be helping the infrastructure, not hurting it.

Thanks very much for the help and education!

Joseph, kc2yu

On Thu, Aug 30, 2012 at 4:15 AM, kc2yu <jrskoler@...> wrote:

> That's yet another interesting way to look at it.  I think what this
> describes is the number of stations hearing my digi starts growing
> geometrically one hop sooner than a mobile's station, resulting in
> each hop have a greater affect.
>
> That is (for example, a WIDE3-3), a mobile might be heard by 1 digi
> (DIGI-A), and that digi by 2 other digis (DIGI-B and DIGI-C), which each
> are heard by 2 digis (DIGI-D, DIGI-E, DIGI-F, DIGI-G).  This results in
> the mobile station being heard by (and digipeated by) 7 digis.
>
> Whereas, the same 3 hops starting from a digi results in being heard
> by 2 digis initially (DIGI-A, DIGI-B), then 4 more digis (DIGI-C, DIGI-D,
DIGI-E,
> DIGI-F), then 8 more digis (DIGI-G, H, I, J, K, L, M, N).  That's 14 digis.
>
> Is this correct?

You got it except if you want to think of it as the same digis as your
first example, move all the letters up one since the packet originated
from DIGIA...

And of course you're using a very sparse APRS network in your example.
In some areas you might hit more than 1 digi on the first hop, and the
second hop will be far more than just 2 digis, and then that third hop
will be far far more than eight.

I was looking at Dallas last week, and counted 23 digipeaters within
50 miles of downtown. Being on the pessimistic side, let's just say
that you get heard by only 8 of the closest digipeaters within the
city limits on the first hop, and then only the rest of the 23
digipeaters on the second hop. How many more digipeaters do we add for
the third hop?

Now of course in the real world all of those digipeaters aren't going
to fire off in Dallas. There are far too many of them in too confined
an area. They are probably causing so much interference with each
other that the locals are fighting to be heard over the din.


> I see -- it doesn't switch profiles, it just switches which profile's path
> is used.  So the 2 profile paths can be WIDE2-2 and blank, or
> WIDE2-2 and WIDE4-4, for example.

That's correct, and if everyone around is using a 2 hop hop limit,
WIDE4-4 shouldn't go anywhere.

> I do hope I will be helping the infrastructure, not hurting it.

That's a great attitude, and you're on your way towards that goal. If
everyone that wanted to put up a digipeater did the research and
learnt about what a digipeater does and how it affects the local
network before deciding whether they *should* put one up, that would
be great. A poorly implemented digipeater can harm the network more
than help.

> Thanks very much for the help and education!

It's worth my time and effort to educate now rather than try to fight
with you later to fix it. Hopefully you'll continue to read and learn,
experiment and observe, and help others as well. There are hundreds of
digipeaters improperly configured or sited out there that need to be
fixed because people don't bother to educate themselves before
installing them.

--
James
VE6SRV

The remote weather station Digi Shut down yesterday. The way it looks in the Raw
data it looks like the software messed up. Looks like the newest software or my
scripts failed. Do not have much time before it is winter at the high site so
the next trip I will likely set it back to the old software or replace the T2
with something that works better.

Scott KB7DZR

--- In tracker2@yahoogroups.com, Tim Cunningham <n8deu@...> wrote:
>
> There is nothing wrong with the U2100's. They have worked flawlessly with
other
> packet controllers for years until the T2-135's were attached.
>
> I have had a little time off from my travels and recently came up with a last
> effort plan for the EMA group in an adjacent county to get their T2-135's
> working with a Peet Brothers U2100 and avoid invalid data. If this effort is
> successful we will post our findings... Keep your fingers crossed as we should
> know something in the next few weeks when the proposed solution goes back to
the
> digipeater site. A lot of effort went into attempting to get these T2-135's
> working better on 8 separate stations purchased under a Government Grant.
>
>
> Tim - N8DEU
>
>  
>
>
>
> ________________________________
> From: offtracks1 <worldroamer@...>
> To: tracker2@yahoogroups.com
> Sent: Thu, August 23, 2012 11:49:45 AM
> Subject: [tracker2] Re: T2-301 WX help
>
>  
> Just installed the latest beta firmware were you can set the weather beacon on
> its own at a remote site also (ALAKES). It looks like the crazy data or
missing
> data is still taking place. When on site the data coming from the U2100 is
fine.
>
> Scott KB7DZR
>
> --- In tracker2@yahoogroups.com, "N5UDK" <tpurvis@> wrote:
> >
> > No I haven't tried the latest beta firmware. I've been watching to see if
> >you've posted a fix. I will give it one last shot.
> >
> > No thanks for the ADS-WS1 option. The problem is not with the Peet wx
station,
> >the problem is with the T2-135. We have over $6000 invested in the Peet wx
> >stations. It would be much easer and less expensive to trash the T2-135's and
> >install the Byonics WXTrak.
> >
> > I'll let you know if your latest beta firmware works.
> >
> > Tim, N5UDK
> >
> >
> > --- In tracker2@yahoogroups.com, Scott Miller <scott@> wrote:
> > >
> > > Have you tried the most recent beta firmware? I've continually made
> > > tweaks to code that could affect this.
> > >
> > > When I finish the next round of firmware updates, the ADS-WS1 base unit
> > > might also be an option for you. It's got Peet Bros input capability
> > > now and I'm putting a lot of work into data integrity.
> > >
> > > Scott
> > >
> > > On 8/20/2012 1:56 PM, N5UDK wrote:
> > > > Scott,
> > > >
> > > > Have you found a solution for the missing data problem on the Peet.
> > > > U2100 and the Argent Data T2-135? I have six of these in operation that
> > > > are still giving problems. I spoke to a previous Argent Data customer
> > > > that was having the same problem. He is now a very satisfied Byonics
> > > > customer after using the WXTrak and I'm almost ready to join him. Any
> > > > help would be appreciated.
> > > >
> > > > --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
> > > > "Tim Cunningham" <n8deu@> wrote:
> > > > >
> > > > > Scott,
> > > > >
> > > > > The problem may be the interface between the Peet Brothers Weather
> > > > Station
> > > > > and the T2-135. A UIDIGI equipped MFJ TNC connected to the same
weather
> > > > > station worked flawlessly for a number of years.
> > > > >
> > > > > We recorded data from a weather station for a 24 hour period, noting
> > > > there
> > > > > was corrupted weather data and inconsistent beacon rates.
> > > > >
> > > > > We took the recorded data and the same T2-135 equipped radio and feed
> > > > the
> > > > > same recorded data via a desktop computer RS-232 interface. We
> > > > increased the
> > > > > beacon rate to 5 seconds and recorded the packets from the
> > > > transmitter from
> > > > > another station. It was consistent and the data had no
> > > > corruption.This was
> > > > > true with the original code and the code you modified for us.
> > > > >
> > > > > It may have more to do with the signal levels generated by the desktop
> > > > > RS-232 versus the levels generated by the Peet Brothers Weather
Station.
> > > > > They are clearly different.
> > > > >
> > > > > The Peet Brothers Weather Station is powered by a Wall Wart at each of
8
> > > > > installations so there is possibility of a ground loop or noise. I
spoke
> > > > > with the guys this week and they are going to eliminate the Wall Wart
> > > > so the
> > > > > return power signals are referenced to the same supply powering the
> > > > radio.
> > > > > The next step, if the previous fails to be satisfactory, will be to
> > > > modify
> > > > > the levels from the Peet WX Station to observe the impact. At that
> > > > point I
> > > > > will contact Jason who is closer since I have trouble keeping my feet
> > > > below
> > > > > 36K feet these days.
> > > > >
> > > > >
> > > > > Tim - N8DEU
> > > > >
> > > > >
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Scott Miller" <scott@>
> > > > > To: <tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>>
> > > > > Sent: Thursday, April 19, 2012 10:02 PM
> > > > > Subject: Re: [tracker2] Re: T2-301 WX help
> > > > >
> > > > >
> > > > > > Is autobaud turned off? That might cause intermittent problems.
> > > > > >
> > > > > > Also, is it possible to increase the baud rate on the station? Could
> be
> > > > > > the tracker is marking the current weather data as invalid while
it's
> > > > > > busy parsing the new data. A faster transfer would reduce the time
> > > > > > window when that could happen. It's not a 100% fix, but would let us
> > > > > > know that's probably the problem.
> > > > > >
> > > > > > Scott
> > > > > >
> > > > > > On 4/19/2012 1:35 PM, N5UDK wrote:
> > > > > >> Does anyone have any updates on this issue? We have about five of
> > > > these
> > > > > >> in the field and ALL are having issues. Most of the time they will
> > > > TX at
> > > > > >> the proper interval but sometime the weather data is missing. I'm
> > > > > >> thinking when this happens, it is only sending out a beacon.
> > > > > >>
> > > > > >> Thanks,
> > > > > >> Tim Purvis, N5UDK
> > > > > >>
> > > > > >> --- In tracker2@yahoogroups.com
> > > > <mailto:tracker2%40yahoogroups.com> <mailto:tracker2%40yahoogroups.com>,
> > > > > >> "Tim Cunningham" <tim_cunningham@> wrote:
> > > > > >> >
> > > > > >> > In our case with the T2-135 the data from the Peet U2100 was
> > > > > >> perfectly fine.
> > > > > >> > It was the data coming out of the T2-135 that was the issue, but
I
> > > > > >> will
> > > > > >> > clarify the U2100 was in the Data Logger mode initially. It took
> > > > > >> about a day
> > > > > >> > for it to start the issues at a couple of sites. When we
> > > > switched to
> > > > > >> the
> > > > > >> > Complete Record mode most of the problems went away or were
> > > > > >> drastically
> > > > > >> > reduced in output errors from the T2-135.
> > > > > >> >
> > > > > >> > 73's,
> > > > > >> > Tim - N8DEU
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> > ----- Original Message -----
> > > > > >> > From: "virtual_chico" <virtual_chico@>
> > > > > >> > To: <tracker2@yahoogroups.com
> > > > <mailto:tracker2%40yahoogroups.com> <mailto:tracker2%40yahoogroups.com>>
> > > > > >> > Sent: Thursday, April 15, 2010 12:54 PM
> > > > > >> > Subject: Re: [tracker2] Re: T2-301 WX help
> > > > > >> >
> > > > > >> >
> > > > > >> > Hi,
> > > > > >> >
> > > > > >> > we asked Peet if they could help us to figure out the problem
> > > > with the
> > > > > >> > erroneus data.
> > > > > >> >
> > > > > >> > First answer from Peet was like: We do not know anything about
> wrong
> > > > > >> > data that might be delivered by our stations...
> > > > > >> >
> > > > > >> >
> > > > > >> > As we reasked and pointed out, that other users also have
> > > > problems we
> > > > > >> > got this today:
> > > > > >> >
> > > > > >> >
> > > > > >>
> > > >
----------------------------------cut-------------------------------------
> > > > > >> > Von: Peet Bros. <peetbros@>
> > > > > >> > Gesendet: Mittwoch, 14. April 2010 16:54
> > > > > >> > An: dh1gd@
> > > > > >> > Betreff: RE: Ultimeter 2100 delivering wrong values
> > > > > >> >
> > > > > >> > Hi Daniel,
> > > > > >> >
> > > > > >> > Based upon the information you've provided, it appears that
> > > > people are
> > > > > >> > having difficulty with configuration of radios and interfaces,
and
> > > > > >> also
> > > > > >> > possibly with the serial cables they are using.
> > > > > >> >
> > > > > >> > It is a common mistake, when a person fabricates a modular cable
> > > > with
> > > > > >> > RJ-11 or RJ-12 plugs, that they will use RJ plugs designed for
> SOLID
> > > > > >> > wire with their STRANDED wire cable. There are two designs of
> > > > modular
> > > > > >> > RJ plugs: for solid wire cable (such as old telephone cable),
> > > > and for
> > > > > >> > stranded wire cable
> > > > > >> >
> > > > > >>
> > > >
----------------------------------cut-------------------------------------
> > > > > >> >
> > > > > >> >
> > > > > >> > We ONLY have original Peet cables attached to our Peet Ultimeter
> > > > 2100
> > > > > >> > and we used a bought stranded cable, cut it in the middle to
> > > > solder on
> > > > > >> > the 3,5mm stereo plug...
> > > > > >> >
> > > > > >> > We will try our luck with ferrites now... as the problem seems
> > > > to be
> > > > > >> our
> > > > > >> > unabilty to configure our devices... hi
> > > > > >> >
> > > > > >> > We hope that we get the station running correctly.
> > > > > >> >
> > > > > >> > I'm also running a Davis Vantage Pro wireless station in my QRL
and
> > > > > >> what
> > > > > >> > should I say - no problems. Our reason to choose the Peet
> > > > station was
> > > > > >> > that it fits nicely together with our Argent Data T2-135...
> > > > > >> > We still hope this was the right decision.
> > > > > >> >
> > > > > >> > Maybe some OM of you would like to mail your problems to Peet so
> > > > that
> > > > > >> > they get a little feedback on their products...
> > > > > >> >
> > > > > >> >
> > > > > >> > 73s de Mark , DL1GMC, and Daniel, DH1GD.
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> > Am Sonntag, den 11.04.2010, 10:21 +0000 schrieb vk2boz:
> > > > > >> > >
> > > > > >> > > Hi Tim
> > > > > >> > >
> > > > > >> > > Thanks for your input as it has been helpful. I have it settup
> > > > very
> > > > > >> > > close to yours and it is working better but not quite as it
> > > > should.
> > > > > >> > >
> > > > > >> > > Still Tx when it wants to but a lot more constant, set time
> > > > slot at
> > > > > >> > > 16min but it Tx at 30min roughly. I'll look at making an other
> > > > > >> cable,
> > > > > >> > > (using a cable from an other unit it also had troubles).
> > > > > >> > >
> > > > > >> > > What changes did you do to the code?
> > > > > >> > >
> > > > > >> > > Thanks
> > > > > >> > > Cris VK2BOZ
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > > > ------------------------------------
> > > > > >
> > > > > > Yahoo! Groups Links
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
>

Worked like a charm,

Thanks
Sean

--- In tracker2@yahoogroups.com, "Lynn W. Deffenbaugh (Mr)" <ldeffenb@...>
wrote:
>
> I saved the Data mode on into a memory channel and have that channel as
> well as Lock selected.
>
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
>
> On 8/27/2012 12:29 PM, Sean wrote:
> > Ok I'm sure I'm missing some thing simple, how do I get my DR-135 to stay in
Data mode even if it's powered off and back on? The radio isn't that old ( < 3
years) so I would hope it's not a internal battery issue.
> >
> > Thanks
> >
> > Sean
> >
>

The BlueSmirf can take 5V levels (and so can the Tracker 3 at the DE-9 serial
port), so you won't risk frying the ICs on either end of that connection, but
they won't talk to each other on their own.

The BlueSmirf uses TTL serial where (in this case) a +5V signal is a logic "1",
but the Tracker 3, at the DE-9 port, uses RS-232 where 0V is a logic "1". You
can see that these two devices won't be able to communicate directly. The
Sparkfun product page for the BlueSmirf
(https://www.sparkfun.com/products/10269) even addresses this and has a link to
their own RS-232 to TTL converter product.

You *might* be able to get around having to use a converter circuit by finding a
spot on the PCB of the Tracker 3 board where you can solder in a wire to access
the serial lines at the TTL level, but I don't yet own a Tracker 3, so I'm not
sure about that.

If you don't mind buying directly from China and having no product support, you
could get an integrated RS-232 to Bluetooth adapter like this:
www.dealextreme.com/p/db9-rs232-wireless-bluetooth-serial-module-104301

Anyway, the BlueSmirf modules are great (I've used them in a few projects
myself), and they'll work fine to add Bluetooth to a Tracker 3, you'll just need
to account for the different serial protocols with an additional circuit or
perhaps some clever soldering. Good luck!

- Cai /W6CAI

--- In tracker2@yahoogroups.com, "Andrew Wawrzynowicz" <mechcondrid@...> wrote:
>
> Ya its a sparkfun bluesmirf silver i thought it could take up to 5v signal
> levels
>

Having some difficulty with my brand new OT3m.

I've got it hooked up to an FT-8800 and to the computer via UBS.

Got otwincfg running and was able to configure the ot3m (and write settings).

I can make use otwincfg to transmit (test the PTT button in the program).

Downloaded aprsis32 and did a very brief config (mycall, location, etc.).

But, while I hear lots of traffic on 144.39, nothing shows up on the aprsis32
map or packet log.

It appears aprsis32 isn't communicating with the ot3m.

I found a web page that says I need to put the following command in aprsis32.xml
-- http://www.kj4iwx.com/?p=52

but that isn't working.

Any ideas?

Thank you,

Joseph, kc2yu

Update:

I believe aprsis32 and the ot3m are now talking.

Here's a snippet from the trace-port log:

Port(test):2012-08-31T15:00:27.705 KISS:Missing Leading C0[165]:<0D
0A>WB2ZEX>APW285,N2MH-15*,WA2MJM-15*:_08311456c290s006g002t094r493p493P000h00b10\
138wHKT<0D 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for
Wb`@145833hIS for W
Port(test):2012-08-31T15:00:33.529 KISS:Missing Leading C0[152]:<0D
0A>W2LV>APN391,WIDE2-1:!!0013002002DB0623266602FF024C----00F3026100000000<0D 0A
0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for
W
Port(test):2012-08-31T15:00:36.529 KISS:Missing Leading C0[155]:<0D
0A>W2LV>APN391,WA2MJM-15*:!!0013002002DB0623266602FF024C----00F3026100000000<0D
0A 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS
for W
Port(test):2012-08-31T15:00:38.146 KISS:Missing Leading C0[154]:<0D
0A>N1LMA-9>APNX01,SALECT*,KB1AEV-15*,WIDE2:!4120.95NS07157.74W#PHG5130/CRSnet<0D
0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W

So, packets are getting from the radio to aprsis32, but I'm not seeing them on
my map or list of names.  Sounds like this is an aprsis32 question, so sorry for
msg traffic here.  I'll move it over.



--- In tracker2@yahoogroups.com, "kc2yu" <jrskoler@...> wrote:
>
>
> Having some difficulty with my brand new OT3m.
>
> I've got it hooked up to an FT-8800 and to the computer via UBS.
>
> Got otwincfg running and was able to configure the ot3m (and write settings).
>
> I can make use otwincfg to transmit (test the PTT button in the program).
>
> Downloaded aprsis32 and did a very brief config (mycall, location, etc.).
>
> But, while I hear lots of traffic on 144.39, nothing shows up on the aprsis32
map or packet log.
>
> It appears aprsis32 isn't communicating with the ot3m.
>
> I found a web page that says I need to put the following command in
aprsis32.xml -- http://www.kj4iwx.com/?p=52
>
> but that isn't working.
>
> Any ideas?
>
> Thank you,
>
> Joseph, kc2yu
>

Based on the "Missing Leading C0", your tracker port isn't in KISS
mode.  You'll want to use the appropriate AMODE/BMODE/USBKISS to put it
there and make sure your port in APRSISCE/32 is a Simply(KISS) or edit
the XML file and set the <Open/CloseCmd>s to no-ops as described at
http://aprsisce.wikidot.com/tt4-via-kiss (yes, I know that's for the
TT4, but it describes how to set up the No-Operation <Open/CloseCmd>s).

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 8/31/2012 11:03 AM, kc2yu wrote:
> Update:
>
> I believe aprsis32 and the ot3m are now talking.
>
> Here's a snippet from the trace-port log:
>
> Port(test):2012-08-31T15:00:27.705 KISS:Missing Leading C0[165]:<0D
0A>WB2ZEX>APW285,N2MH-15*,WA2MJM-15*:_08311456c290s006g002t094r493p493P000h00b10\
138wHKT<0D 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for
Wb`@145833hIS for W
> Port(test):2012-08-31T15:00:33.529 KISS:Missing Leading C0[152]:<0D
0A>W2LV>APN391,WIDE2-1:!!0013002002DB0623266602FF024C----00F3026100000000<0D 0A
0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for
W
> Port(test):2012-08-31T15:00:36.529 KISS:Missing Leading C0[155]:<0D
0A>W2LV>APN391,WA2MJM-15*:!!0013002002DB0623266602FF024C----00F3026100000000<0D
0A 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS
for W
> Port(test):2012-08-31T15:00:38.146 KISS:Missing Leading C0[154]:<0D
0A>N1LMA-9>APNX01,SALECT*,KB1AEV-15*,WIDE2:!4120.95NS07157.74W#PHG5130/CRSnet<0D
0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
>
> So, packets are getting from the radio to aprsis32, but I'm not seeing them on
my map or list of names.  Sounds like this is an aprsis32 question, so sorry for
msg traffic here.  I'll move it over.
>
>
>
> --- In tracker2@yahoogroups.com, "kc2yu" <jrskoler@...> wrote:
>>
>> Having some difficulty with my brand new OT3m.
>>
>> I've got it hooked up to an FT-8800 and to the computer via UBS.
>>
>> Got otwincfg running and was able to configure the ot3m (and write settings).
>>
>> I can make use otwincfg to transmit (test the PTT button in the program).
>>
>> Downloaded aprsis32 and did a very brief config (mycall, location, etc.).
>>
>> But, while I hear lots of traffic on 144.39, nothing shows up on the aprsis32
map or packet log.
>>
>> It appears aprsis32 isn't communicating with the ot3m.
>>
>> I found a web page that says I need to put the following command in
aprsis32.xml -- http://www.kj4iwx.com/?p=52
>>
>> but that isn't working.
>>
>> Any ideas?
>>
>> Thank you,
>>
>> Joseph, kc2yu
>>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

---

From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of kc2yu
Sent: Friday, August 31, 2012 11:03
To: tracker2@yahoogroups.com
Subject: [tracker2] Re: New OT3m

 

Update:

I believe aprsis32 and the ot3m are now talking.

Here's a snippet from the trace-port log:

Port(test):2012-08-31T15:00:27.705 KISS:Missing Leading C0[165]:<0D 0A>WB2ZEX>APW285,N2MH-15*,WA2MJM-15*:_08311456c290s006g002t094r493p493P000h00b10138wHKT<0D 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
Port(test):2012-08-31T15:00:33.529 KISS:Missing Leading C0[152]:<0D 0A>W2LV>APN391,WIDE2-1:!!0013002002DB0623266602FF024C----00F3026100000000<0D 0A 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
Port(test):2012-08-31T15:00:36.529 KISS:Missing Leading C0[155]:<0D 0A>W2LV>APN391,WA2MJM-15*:!!0013002002DB0623266602FF024C----00F3026100000000<0D 0A 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
Port(test):2012-08-31T15:00:38.146 KISS:Missing Leading C0[154]:<0D 0A>N1LMA-9>APNX01,SALECT*,KB1AEV-15*,WIDE2:!4120.95NS07157.74W#PHG5130/CRSnet<0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W

So, packets are getting from the radio to aprsis32, but I'm not seeing them on my map or list of names. Sounds like this is an aprsis32 question, so sorry for msg traffic here. I'll move it over.

--- In tracker2@yahoogroups.com, "kc2yu" <jrskoler@...> wrote:
>
>
> Having some difficulty with my brand new OT3m.
>
> I've got it hooked up to an FT-8800 and to the computer via UBS.
>
> Got otwincfg running and was able to configure the ot3m (and write settings).
>
> I can make use otwincfg to transmit (test the PTT button in the program).
>
> Downloaded aprsis32 and did a very brief config (mycall, location, etc.).
>
> But, while I hear lots of traffic on 144.39, nothing shows up on the aprsis32 map or packet log.
>
> It appears aprsis32 isn't communicating with the ot3m.
>
> I found a web page that says I need to put the following command in aprsis32.xml -- http://www.kj4iwx.com/?p=52
>
> but that isn't working.
>
> Any ideas?
>
> Thank you,
>
> Joseph, kc2yu
>

That did it, thought I'm not sure what exactly it did.

The ot was in AUTO mode for the serial ports.  I switched them to KISS.

Then restarted aprsis32 and it worked.

Shut down aprsis32 and restarted it and it didn't.

Checked otwincfg and the serial ports were back to AUTO -- despite having
written the config the first time.

Edited aprsis32.xml and replace the opencmd & closecmd lines with:

<OpenCmd>~!!0</OpenCmd>
<CloseCmd>~!!0</CloseCmd>

Seems like that did it (not 100% certain).

Thanks very much!

And, it sure looks like the OT continues to digi on its own while still in KISS
mode connected to aprsis32 -- very cool.

What I'd like to do now is find a way to see who is hearing my signals direct. 
I very well may need to turn down the power, or adjust in some other way.





--- In tracker2@yahoogroups.com, "Lynn W. Deffenbaugh (Mr)" <ldeffenb@...>
wrote:
>
> Based on the "Missing Leading C0", your tracker port isn't in KISS
> mode.  You'll want to use the appropriate AMODE/BMODE/USBKISS to put it
> there and make sure your port in APRSISCE/32 is a Simply(KISS) or edit
> the XML file and set the <Open/CloseCmd>s to no-ops as described at
> http://aprsisce.wikidot.com/tt4-via-kiss (yes, I know that's for the
> TT4, but it describes how to set up the No-Operation <Open/CloseCmd>s).
>
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
>
> On 8/31/2012 11:03 AM, kc2yu wrote:
> > Update:
> >
> > I believe aprsis32 and the ot3m are now talking.
> >
> > Here's a snippet from the trace-port log:
> >
> > Port(test):2012-08-31T15:00:27.705 KISS:Missing Leading C0[165]:<0D
0A>WB2ZEX>APW285,N2MH-15*,WA2MJM-15*:_08311456c290s006g002t094r493p493P000h00b10\
138wHKT<0D 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for
Wb`@145833hIS for W
> > Port(test):2012-08-31T15:00:33.529 KISS:Missing Leading C0[152]:<0D
0A>W2LV>APN391,WIDE2-1:!!0013002002DB0623266602FF024C----00F3026100000000<0D 0A
0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for
W
> > Port(test):2012-08-31T15:00:36.529 KISS:Missing Leading C0[155]:<0D
0A>W2LV>APN391,WA2MJM-15*:!!0013002002DB0623266602FF024C----00F3026100000000<0D
0A 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS
for W
> > Port(test):2012-08-31T15:00:38.146 KISS:Missing Leading C0[154]:<0D
0A>N1LMA-9>APNX01,SALECT*,KB1AEV-15*,WIDE2:!4120.95NS07157.74W#PHG5130/CRSnet<0D
0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
> >
> > So, packets are getting from the radio to aprsis32, but I'm not seeing them
on my map or list of names.  Sounds like this is an aprsis32 question, so sorry
for msg traffic here.  I'll move it over.
> >
> >
> >
> > --- In tracker2@yahoogroups.com, "kc2yu" <jrskoler@> wrote:
> >>
> >> Having some difficulty with my brand new OT3m.
> >>
> >> I've got it hooked up to an FT-8800 and to the computer via UBS.
> >>
> >> Got otwincfg running and was able to configure the ot3m (and write
settings).
> >>
> >> I can make use otwincfg to transmit (test the PTT button in the program).
> >>
> >> Downloaded aprsis32 and did a very brief config (mycall, location, etc.).
> >>
> >> But, while I hear lots of traffic on 144.39, nothing shows up on the
aprsis32 map or packet log.
> >>
> >> It appears aprsis32 isn't communicating with the ot3m.
> >>
> >> I found a web page that says I need to put the following command in
aprsis32.xml -- http://www.kj4iwx.com/?p=52
> >>
> >> but that isn't working.
> >>
> >> Any ideas?
> >>
> >> Thank you,
> >>
> >> Joseph, kc2yu
> >>
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>

At 12:33 PM 8/31/2012, kc2yu wrote:

>And, it sure looks like the OT continues to digi on its own while
>still in KISS mode connected to aprsis32 -- very cool.

Yes, that is a feature of the Tracker2 and Tracker3 lines that comes
up in conversation here from time to time. It's a useful feature, but
you have to be careful with it as you don't want both the TNC and the
client program doing the same thing whether it be beaconing or
digipeating. For instance, if your client program is handling the
beaconing, make sure the TNC isn't beaconing, too.

If you take a look at the Tracker2 set up instructions for UI-View
(http://wiki.argentdata.com/index.php?title=UI-View_Setup), you will
see that UI-View's "Into KISS" strings are commanding the Tracker2 to
_not_ beacon before it actually tells the Tracker2 to go into KISS mode.

Bob...

It seems like a very nice feature.

With features come power and complications.

I don't believe the APRSISCE/32 instance is digipeating, but I should check the
beaconing.  I have the ot3m digi as kc2yu-2, while the ASRSISCE/32 as kc2yu-3 --
just assuming it'd be easier to distinguish what is generating what and there
cause a problem doing so.

Thanks for the explanation!

--- In tracker2@yahoogroups.com, Bob Burns W9RXR <w9rxr_@...> wrote:
>
> At 12:33 PM 8/31/2012, kc2yu wrote:
>
> >And, it sure looks like the OT continues to digi on its own while
> >still in KISS mode connected to aprsis32 -- very cool.
>
> Yes, that is a feature of the Tracker2 and Tracker3 lines that comes
> up in conversation here from time to time. It's a useful feature, but
> you have to be careful with it as you don't want both the TNC and the
> client program doing the same thing whether it be beaconing or
> digipeating. For instance, if your client program is handling the
> beaconing, make sure the TNC isn't beaconing, too.
>
> If you take a look at the Tracker2 set up instructions for UI-View
> (http://wiki.argentdata.com/index.php?title=UI-View_Setup), you will
> see that UI-View's "Into KISS" strings are commanding the Tracker2 to
> _not_ beacon before it actually tells the Tracker2 to go into KISS mode.
>
> Bob...
>

On Fri, Aug 31, 2012 at 10:33 AM, kc2yu <jrskoler@...> wrote:

> What I'd like to do now is find a way to see who is hearing my signals direct.

Look at your map, and use Screen|Paths to enable showing the paths
between stations. You'll be able to see who you can hear direct. You
can contact the operators of those stations and ask them if they can
see you. Digipeaters will digipeat your packets so you can see if they
hear you when they send your packets back at you. i-gates pushing your
data to the internet can be observed via the internet, but you might
not see all of the i-gates that can hear you due to the duplicate
filtering issues.

--
James
VE6SRV

Anyone know when Scott will be back?

I have an OT3m question that only he can answer.


--

Thanks! & 73, KD4E.com
David Colburn nevils-station.com
I don't google I SEARCH! duckduckgo.com
Network: groups.yahoo.com/group/qrv
Restored to design-spec at Heaven's gate 1Cor15:22

http://www.burningman.com/ FOR DETAILS

Eric
AF6EP

On Fri, Aug 31, 2012 at 5:29 PM, qrv@... <qrv@...> wrote:

 

Anyone know when Scott will be back?

I have an OT3m question that only he can answer.

--

Thanks! & 73, KD4E.com
David Colburn nevils-station.com
I don't google I SEARCH! duckduckgo.com
Network: groups.yahoo.com/group/qrv
Restored to design-spec at Heaven's gate 1Cor15:22