Date   

Re: FreqSpec Homework...

Greg Depew
 

the ftm 350 does have to be in vfo for it to qsy. it will not qsy  in memory mode. but it will tx the current memory as a qsy freq if you have it set in the beacon stats text, as long as its a tx-able freq in memory or vfo.


To: aprsisce@...
From: fmhillhouse@...
Date: Tue, 8 May 2012 16:27:18 -0400
Subject: RE: [aprsisce] Re: FreqSpec Homework...

 

Thanks for looking at it. I worked with the NW-APRS group initially and finally, James of VE6SRV notoriety, to get them worked out. Unfortunately, others just pointed at the spec and said follow it. For a digipeater noob, it was very frustrating to have very knowledgeable be no help! Thanks again James for your help to knit them together and help with my understanding! IIRC, we had the FREQUENCY OBJECT VS POSITION COMMENT conversation a couple of times. Sadly, we will have it again in the future unless this go around burns it into our bran cells. :) Yup, bran! Use to be more brain. :(
 
Everyone missed the r VS R. That doesn't have any affect on QSY or TUNE but still it doesn't match the spec. I will have to head up the hill now.
 
 
On the FTM-350, we did some testing recently and I remember them working but I have asked the three parties to do it again. I do remember some weirdness though. The radio had to be in a specific mode, such as VFO instead of MEMORY, or it would not QSY. When I hear back, I will certainly forward the results.
 
 
Best regards,
Fred, N7FMH
 


From: aprsisce@... [mailto:aprsisce@...] On Behalf Of Lynn W Deffenbaugh (Mr)
Sent: Tuesday, May 08, 2012 16:11
To: aprsisce@...
Subject: Re: [aprsisce] Re: FreqSpec Homework...

 
Yes, the lower-case r is all that jumps to my eyes.  Do you know if an FTM-350 can QSY/Tune to these objects?  If so, it debunks the fact that they need the frequency in the command and not the name.

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


On 5/8/2012 3:55 PM, Fred Hillhouse wrote:
Hi Lynn,
 
 
Below are four FREQUENCY objects I put out. The only thing I see is a lower case r for the range. Would that be all that is NON-COMPLIANT?
 
Thanks!
 
 
Best regards,
Fred, N7FMH
 
 
:;223.900NH*111111z4259.00N/07135.30WrT103 r20m S.Uncan MT
WinMain:2012-05-08T19:09:12.279 Antenna UNCAN(223.900NH)(Kantronics KPC-3 (83)) Frequency:223.900 T:103 range:20.0mi *NON-COMPLIANT* Comment:T103 r20m S.Uncan MT
 
:;147.330NH*111111z4305.16N/07131.39WrT141 r20m S.Bow
WinMain:2012-05-08T19:11:28.093 Antenna UNCAN(147.330NH)(Kantronics KPC-3 (83)) Frequency:147.330 T:141 range:20.0mi *NON-COMPLIANT* Comment:T141 r20m S.Bow
 
:;147.135NH*111111z4258.99N/07135.29WrT100 r20m S.Uncan MT
WinMain:2012-05-08T19:14:17.366 Antenna UNCAN(147.135NH)(Kantronics KPC-3 (83)) Frequency:147.135 T:100 range:20.0mi *NON-COMPLIANT* Comment:T100 r20m S.Uncan MT
 
:;444.200NH*111111z4258.99N/07135.30WrT186 r20m S.Uncan MT
WinMain:2012-05-08T19:06:28.128 Antenna UNCAN(444.200NH)(Kantronics KPC-3 (83)) Frequency:444.200 T:186 range:20.0mi *NON-COMPLIANT* Comment:T186 r20m S.Uncan MT


From: aprsisce@... [mailto:aprsisce@...] On Behalf Of Lynn W Deffenbaugh (Mr)
Sent: Tuesday, May 08, 2012 10:43
To: aprsisce@...
Subject: Re: [aprsisce] Re: FreqSpec Homework...

 
On 5/8/2012 10:32 AM, apenadragon wrote:

Taking each unique one at a time....

> WinMain:2012-05-08T13:39:03.677 Antenna KA2NDW-1(145.47-/r)(TNC-X de K6DBG (01)) Frequency:145.470 range:30.0mi *NON-COMPLIANT* Comment:R30M Link 449.075-/r

The R30M is non-compliant. The spec says that m and k are lower case.

> WinMain:2012-05-08T13:39:11.067 Antenna W2SO(147.285/R)(UIview 32 bit (25N)) Frequency:147.285 T:141 *NON-COMPLIANT* Comment:T141.3

The T141.3 is non-compliant. The spec says that tones do not include
the decimal places because they've been standardized.

> WinMain:2012-05-08T13:39:12.927 Antenna W2SO(147.255/R)(UIview 32 bit (25N)) Frequency:147.255 T:107 *NON-COMPLIANT* Comment:T107.2 Lancaster Amateur Radio Club

T107.2 is non-compliant as descried above.

> WinMain:2012-05-08T13:45:04.895 Antenna N2ZWO-10(145.110NY)(BEACON) Frequency:145.110 T:167 range:25.0mi *NON-COMPLIANT* Comment:T167 R25M NetM7PM Mtg2ndW

R25M is non-compliant. The spec says that m and k are lower case.

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






Re: {Some tags disabled} Re: FREQ OBJECT Uniqueness

James Ewen
 

On Tue, May 8, 2012 at 1:13 PM, Keith VE7GDH <ve7gdh@rac.ca> wrote:

I'm still trying to find the time to find all the combinations that
work and don't work with a D72, and I'll post it here and on
the APRS SIG when I'm done.
I'm going to make a chart... we can work on filling it out together.
Still stuck at work though!


I just wanted to jump in and say
that my preference is to have the callsign in the object name.
When I call another
ham, I don't say "hey Lynn on 732 this is VE7GDH". I call
them by callsign. I refer to repeaters the same way. It
doesn't happen so much around here, but some places there
is definitely overlapping coverage and only the tone differentiates
them. Callsigns are a lot more unique than frequencies.
So when I come to visit you, and you tell me to VE7RSI, what frequency
should I have on my VFO? Should I be on 2 metres, 70 cm, 6 metres? How
can I possibly divine a frequency from the callsign? The purpose of
using the frequency in the object name is to have the frequency show
up front and center on the display of the radio, and to have the
frequency shown right on the map. No clicking, no poking to find out
what the hidden frequency is.

Like Bob said, these objects are for the traveller who is unfamiliar
with the area, not just as decoration for the local users.

If you tell me to go to VE7RSI, the first thing I'm going to ask is
"What's the frequency?". If however you tell me to go to 147.320, I'll
head on over... I'm not going to ask "What's the callsign" so that I
can meet you on the repeater.

--
James
VE6SRV


Re: FTM-350 FREQ OBJ problem?

Greg Depew
 

Callsign: KB3KBR-1 with qru server, and yes the rest had the receive  freq ex: 145.230-w (obj name) "145.230MHz T186 -060  W3ZIC L/145.19 & 147.12 Net 2030Hr Mon" , quotes mine,  is qsy'ed correctly.


To: aprsisce@...
From: kj4erj@...
Date: Tue, 8 May 2012 16:22:08 -0400
Subject: Re: [aprsisce] FTM-350 FREQ OBJ problem?

 
On 5/8/2012 4:18 PM, Greg Depew wrote:
ok, just made a spec approved obj of 144.630 in the name and 145.230rx T123 and my 350 will NOT  qsy to it. I also set it up in my qru and received the rest of my 2m obj which all qsy'ed just fine.

What callsign transmitted these so we can actually eyeball the raw packets?  And I'm assuming "the rest of my 2m obj" had the frequency at the beginning of the comment for the FTM-350 to work?

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

PS.  Note to all: Please sign your messages or at least include a callsign-SSID when referring to a particular station or object.




To: aprsisce@...
From: bruninga@...
Date: Tue, 8 May 2012 11:05:56 -0400
Subject: [aprsisce] FTM-350 FREQ OBJ problem?

 
Greg said:

> My ftm 350 does not decode the qsy that has no rx freq
> in the comment. Example:443.650PA near Pittsburgh shows
> on my list but will not qsy with just the T131 RM50.
> It ignores the object name and parses from the comment.
> All of my objects that i transmit with aprs32 are compliant
> with the 350 and are all qsy-able but I dont know about the kenwoods.

Is this confirmed? This is a problem.. And why we need to build a BUG
table for all these issues.

I too have noticed that the 350 does not seem to QSY on some objects that
appear to me (in the mobile anyway) to be correctly formatted. I just
checked, and I cannot see any problems with the formatting of the 443.650PA
object.

Can the Yaesu firmware can be upgraded in the field?

Bob, Wb4aPR





Re: FreqSpec Homework...

Fred Hillhouse
 

Thanks for looking at it. I worked with the NW-APRS group initially and finally, James of VE6SRV notoriety, to get them worked out. Unfortunately, others just pointed at the spec and said follow it. For a digipeater noob, it was very frustrating to have very knowledgeable be no help! Thanks again James for your help to knit them together and help with my understanding! IIRC, we had the FREQUENCY OBJECT VS POSITION COMMENT conversation a couple of times. Sadly, we will have it again in the future unless this go around burns it into our bran cells. :) Yup, bran! Use to be more brain. :(
 
Everyone missed the r VS R. That doesn't have any affect on QSY or TUNE but still it doesn't match the spec. I will have to head up the hill now.
 
 
On the FTM-350, we did some testing recently and I remember them working but I have asked the three parties to do it again. I do remember some weirdness though. The radio had to be in a specific mode, such as VFO instead of MEMORY, or it would not QSY. When I hear back, I will certainly forward the results.
 
 
Best regards,
Fred, N7FMH
 


From: aprsisce@... [mailto:aprsisce@...] On Behalf Of Lynn W Deffenbaugh (Mr)
Sent: Tuesday, May 08, 2012 16:11
To: aprsisce@...
Subject: Re: [aprsisce] Re: FreqSpec Homework...

 

Yes, the lower-case r is all that jumps to my eyes.  Do you know if an FTM-350 can QSY/Tune to these objects?  If so, it debunks the fact that they need the frequency in the command and not the name.

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


On 5/8/2012 3:55 PM, Fred Hillhouse wrote:

Hi Lynn,
 
 
Below are four FREQUENCY objects I put out. The only thing I see is a lower case r for the range. Would that be all that is NON-COMPLIANT?
 
Thanks!
 
 
Best regards,
Fred, N7FMH
 
 
:;223.900NH*111111z4259.00N/07135.30WrT103 r20m S.Uncan MT
WinMain:2012-05-08T19:09:12.279 Antenna UNCAN(223.900NH)(Kantronics KPC-3 (83)) Frequency:223.900 T:103 range:20.0mi *NON-COMPLIANT* Comment:T103 r20m S.Uncan MT
 
:;147.330NH*111111z4305.16N/07131.39WrT141 r20m S.Bow
WinMain:2012-05-08T19:11:28.093 Antenna UNCAN(147.330NH)(Kantronics KPC-3 (83)) Frequency:147.330 T:141 range:20.0mi *NON-COMPLIANT* Comment:T141 r20m S.Bow
 
:;147.135NH*111111z4258.99N/07135.29WrT100 r20m S.Uncan MT
WinMain:2012-05-08T19:14:17.366 Antenna UNCAN(147.135NH)(Kantronics KPC-3 (83)) Frequency:147.135 T:100 range:20.0mi *NON-COMPLIANT* Comment:T100 r20m S.Uncan MT
 
:;444.200NH*111111z4258.99N/07135.30WrT186 r20m S.Uncan MT
WinMain:2012-05-08T19:06:28.128 Antenna UNCAN(444.200NH)(Kantronics KPC-3 (83)) Frequency:444.200 T:186 range:20.0mi *NON-COMPLIANT* Comment:T186 r20m S.Uncan MT


From: aprsisce@... [mailto:aprsisce@...] On Behalf Of Lynn W Deffenbaugh (Mr)
Sent: Tuesday, May 08, 2012 10:43
To: aprsisce@...
Subject: Re: [aprsisce] Re: FreqSpec Homework...

 

On 5/8/2012 10:32 AM, apenadragon wrote:

Taking each unique one at a time....

> WinMain:2012-05-08T13:39:03.677 Antenna KA2NDW-1(145.47-/r)(TNC-X de K6DBG (01)) Frequency:145.470 range:30.0mi *NON-COMPLIANT* Comment:R30M Link 449.075-/r

The R30M is non-compliant. The spec says that m and k are lower case.

> WinMain:2012-05-08T13:39:11.067 Antenna W2SO(147.285/R)(UIview 32 bit (25N)) Frequency:147.285 T:141 *NON-COMPLIANT* Comment:T141.3

The T141.3 is non-compliant. The spec says that tones do not include
the decimal places because they've been standardized.

> WinMain:2012-05-08T13:39:12.927 Antenna W2SO(147.255/R)(UIview 32 bit (25N)) Frequency:147.255 T:107 *NON-COMPLIANT* Comment:T107.2 Lancaster Amateur Radio Club

T107.2 is non-compliant as descried above.

> WinMain:2012-05-08T13:45:04.895 Antenna N2ZWO-10(145.110NY)(BEACON) Frequency:145.110 T:167 range:25.0mi *NON-COMPLIANT* Comment:T167 R25M NetM7PM Mtg2ndW

R25M is non-compliant. The spec says that m and k are lower case.

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



QRU/FreqSpecs (Dev: 2012/05/08 16:18)

Lynn Deffenbaugh
 

Flag non-lower-case off in T/C/D/t/c/d constructs as non-compliant (AE5E-5's 146.85TRF) - Note: this may be rolled back once the dust settles.

Put a space after RNGnnnn in QRU* objects to see if D710 likes it better (Adam KC2ANT and QRUW2CXM)

Pick up and parse FFF.FF(f) without the MHz at the front of a comment and flag them as non-compliant. (GB3AG GB3AY GB3CS)

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


Re: FTM-350 FREQ OBJ problem?

Lynn Deffenbaugh
 

On 5/8/2012 4:18 PM, Greg Depew wrote:
ok, just made a spec approved obj of 144.630 in the name and 145.230rx T123 and my 350 will NOT qsy to it. I also set it up in my qru and received the rest of my 2m obj which all qsy'ed just fine.

What callsign transmitted these so we can actually eyeball the raw packets? And I'm assuming "the rest of my 2m obj" had the frequency at the beginning of the comment for the FTM-350 to work?

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

PS. Note to all: Please sign your messages or at least include a callsign-SSID when referring to a particular station or object.




To: aprsisce@...
From: bruninga@...
Date: Tue, 8 May 2012 11:05:56 -0400
Subject: [aprsisce] FTM-350 FREQ OBJ problem?

Greg said:

> My ftm 350 does not decode the qsy that has no rx freq
> in the comment. Example:443.650PA near Pittsburgh shows
> on my list but will not qsy with just the T131 RM50.
> It ignores the object name and parses from the comment.
> All of my objects that i transmit with aprs32 are compliant
> with the 350 and are all qsy-able but I dont know about the kenwoods.

Is this confirmed? This is a problem.. And why we need to build a BUG
table for all these issues.

I too have noticed that the 350 does not seem to QSY on some objects that
appear to me (in the mobile anyway) to be correctly formatted. I just
checked, and I cannot see any problems with the formatting of the 443.650PA
object.

Can the Yaesu firmware can be upgraded in the field?

Bob, Wb4aPR




Re: FTM-350 FREQ OBJ problem?

Greg Depew
 

ok, just made a spec approved obj of 144.630 in the name and 145.230rx T123 and my 350 will NOT  qsy to it. I also set it up in my qru and received the rest of my 2m obj which all qsy'ed just fine.


To: aprsisce@...
From: bruninga@...
Date: Tue, 8 May 2012 11:05:56 -0400
Subject: [aprsisce] FTM-350 FREQ OBJ problem?

 
Greg said:

> My ftm 350 does not decode the qsy that has no rx freq
> in the comment. Example:443.650PA near Pittsburgh shows
> on my list but will not qsy with just the T131 RM50.
> It ignores the object name and parses from the comment.
> All of my objects that i transmit with aprs32 are compliant
> with the 350 and are all qsy-able but I dont know about the kenwoods.

Is this confirmed? This is a problem.. And why we need to build a BUG
table for all these issues.

I too have noticed that the 350 does not seem to QSY on some objects that
appear to me (in the mobile anyway) to be correctly formatted. I just
checked, and I cannot see any problems with the formatting of the 443.650PA
object.

Can the Yaesu firmware can be upgraded in the field?

Bob, Wb4aPR



Re: FREQ OBJECT Uniqueness

James Ewen
 

On Tue, May 8, 2012 at 12:51 PM, Bob Bruninga <bruninga@usna.edu> wrote:
Until changes to the specification are made, the Kenwood
and Yaesu radios are non-compliant..
Interesting comment.  Other than the FTM-350 not QSYing to a FREQ OBJECT
(without a duplicate FREQ in the comment) can you elaborate on what you
think is not compliant in the Kenwood?
The Kenwood TM-D710 does not honour the specification for a frequency object.

Here's an object my peers in Calgary are sending in order to get
"proper" QSY functionality on their Kenwood radios.

;146.85-NH*111111z5106.50N/11405.92Wr146.850MHz T110 -060 R50k RYC

They insist that the radio will NOT QSY without the second frequency
in the comment, and the offset included.

The second frequency according to the current spec should be
interpreted as the RX frequency, and the offset is not a defined part
of the FREQUENCY OBJECT. The Kenwood does not set the radio to
simplex.

I know the Kenwood will QSY without the second frequency as I use it
on all of the FREQUENCY OBJECTs that I send from my digipeaters. I'm
thinking that they have come up with this hybrid to make BOTH the
Yaesu and Kenwood "work".

Once I get the list put together we can start to track what works and
what doesn't.

--
James
VE6SRV


Re: FreqSpec Homework...

Lynn Deffenbaugh
 

Yes, the lower-case r is all that jumps to my eyes.  Do you know if an FTM-350 can QSY/Tune to these objects?  If so, it debunks the fact that they need the frequency in the command and not the name.

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

On 5/8/2012 3:55 PM, Fred Hillhouse wrote:
Hi Lynn,
 
 
Below are four FREQUENCY objects I put out. The only thing I see is a lower case r for the range. Would that be all that is NON-COMPLIANT?
 
Thanks!
 
 
Best regards,
Fred, N7FMH
 
 
:;223.900NH*111111z4259.00N/07135.30WrT103 r20m S.Uncan MT
WinMain:2012-05-08T19:09:12.279 Antenna UNCAN(223.900NH)(Kantronics KPC-3 (83)) Frequency:223.900 T:103 range:20.0mi *NON-COMPLIANT* Comment:T103 r20m S.Uncan MT
 
:;147.330NH*111111z4305.16N/07131.39WrT141 r20m S.Bow
WinMain:2012-05-08T19:11:28.093 Antenna UNCAN(147.330NH)(Kantronics KPC-3 (83)) Frequency:147.330 T:141 range:20.0mi *NON-COMPLIANT* Comment:T141 r20m S.Bow
 
:;147.135NH*111111z4258.99N/07135.29WrT100 r20m S.Uncan MT
WinMain:2012-05-08T19:14:17.366 Antenna UNCAN(147.135NH)(Kantronics KPC-3 (83)) Frequency:147.135 T:100 range:20.0mi *NON-COMPLIANT* Comment:T100 r20m S.Uncan MT
 
:;444.200NH*111111z4258.99N/07135.30WrT186 r20m S.Uncan MT
WinMain:2012-05-08T19:06:28.128 Antenna UNCAN(444.200NH)(Kantronics KPC-3 (83)) Frequency:444.200 T:186 range:20.0mi *NON-COMPLIANT* Comment:T186 r20m S.Uncan MT


From: aprsisce@... [mailto:aprsisce@...] On Behalf Of Lynn W Deffenbaugh (Mr)
Sent: Tuesday, May 08, 2012 10:43
To: aprsisce@...
Subject: Re: [aprsisce] Re: FreqSpec Homework...

 

On 5/8/2012 10:32 AM, apenadragon wrote:

Taking each unique one at a time....

> WinMain:2012-05-08T13:39:03.677 Antenna KA2NDW-1(145.47-/r)(TNC-X de K6DBG (01)) Frequency:145.470 range:30.0mi *NON-COMPLIANT* Comment:R30M Link 449.075-/r

The R30M is non-compliant. The spec says that m and k are lower case.

> WinMain:2012-05-08T13:39:11.067 Antenna W2SO(147.285/R)(UIview 32 bit (25N)) Frequency:147.285 T:141 *NON-COMPLIANT* Comment:T141.3

The T141.3 is non-compliant. The spec says that tones do not include
the decimal places because they've been standardized.

> WinMain:2012-05-08T13:39:12.927 Antenna W2SO(147.255/R)(UIview 32 bit (25N)) Frequency:147.255 T:107 *NON-COMPLIANT* Comment:T107.2 Lancaster Amateur Radio Club

T107.2 is non-compliant as descried above.

> WinMain:2012-05-08T13:45:04.895 Antenna N2ZWO-10(145.110NY)(BEACON) Frequency:145.110 T:167 range:25.0mi *NON-COMPLIANT* Comment:T167 R25M NetM7PM Mtg2ndW

R25M is non-compliant. The spec says that m and k are lower case.

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



Re: FREQ OBJECT Uniqueness

James Ewen
 

On Tue, May 8, 2012 at 12:14 PM, Randy Love <rlove31@gmail.com> wrote:

Ah, but see, if it doesn't have a decimal in it, it isn't a FREQ OBJECT,
it just becomes a regular object with a position and FREQ COMMENT.
I see what you're doing, but that's going to cause even more confusion
most likely as people MAY try creating a FREQUENCY OBJECT in that
format which obviously won't work.

Also, there is no such thing as a FREQ COMMENT. There are FREQUENCY
OBJECTS, and POSITION COMMENTS currently defined. The problem we are
having is that people are using FREQUENCY COMMENTS, a specification
for which there is no definition... it is a hybrid of the two formats.

--
James
VE6SRV


Re: FreqSpec Homework...

Fred Hillhouse
 

Hi Lynn,
 
 
Below are four FREQUENCY objects I put out. The only thing I see is a lower case r for the range. Would that be all that is NON-COMPLIANT?
 
Thanks!
 
 
Best regards,
Fred, N7FMH
 
 
:;223.900NH*111111z4259.00N/07135.30WrT103 r20m S.Uncan MT
WinMain:2012-05-08T19:09:12.279 Antenna UNCAN(223.900NH)(Kantronics KPC-3 (83)) Frequency:223.900 T:103 range:20.0mi *NON-COMPLIANT* Comment:T103 r20m S.Uncan MT
 
:;147.330NH*111111z4305.16N/07131.39WrT141 r20m S.Bow
WinMain:2012-05-08T19:11:28.093 Antenna UNCAN(147.330NH)(Kantronics KPC-3 (83)) Frequency:147.330 T:141 range:20.0mi *NON-COMPLIANT* Comment:T141 r20m S.Bow
 
:;147.135NH*111111z4258.99N/07135.29WrT100 r20m S.Uncan MT
WinMain:2012-05-08T19:14:17.366 Antenna UNCAN(147.135NH)(Kantronics KPC-3 (83)) Frequency:147.135 T:100 range:20.0mi *NON-COMPLIANT* Comment:T100 r20m S.Uncan MT
 
:;444.200NH*111111z4258.99N/07135.30WrT186 r20m S.Uncan MT
WinMain:2012-05-08T19:06:28.128 Antenna UNCAN(444.200NH)(Kantronics KPC-3 (83)) Frequency:444.200 T:186 range:20.0mi *NON-COMPLIANT* Comment:T186 r20m S.Uncan MT


From: aprsisce@... [mailto:aprsisce@...] On Behalf Of Lynn W Deffenbaugh (Mr)
Sent: Tuesday, May 08, 2012 10:43
To: aprsisce@...
Subject: Re: [aprsisce] Re: FreqSpec Homework...

 

On 5/8/2012 10:32 AM, apenadragon wrote:

Taking each unique one at a time....

> WinMain:2012-05-08T13:39:03.677 Antenna KA2NDW-1(145.47-/r)(TNC-X de K6DBG (01)) Frequency:145.470 range:30.0mi *NON-COMPLIANT* Comment:R30M Link 449.075-/r

The R30M is non-compliant. The spec says that m and k are lower case.

> WinMain:2012-05-08T13:39:11.067 Antenna W2SO(147.285/R)(UIview 32 bit (25N)) Frequency:147.285 T:141 *NON-COMPLIANT* Comment:T141.3

The T141.3 is non-compliant. The spec says that tones do not include
the decimal places because they've been standardized.

> WinMain:2012-05-08T13:39:12.927 Antenna W2SO(147.255/R)(UIview 32 bit (25N)) Frequency:147.255 T:107 *NON-COMPLIANT* Comment:T107.2 Lancaster Amateur Radio Club

T107.2 is non-compliant as descried above.

> WinMain:2012-05-08T13:45:04.895 Antenna N2ZWO-10(145.110NY)(BEACON) Frequency:145.110 T:167 range:25.0mi *NON-COMPLIANT* Comment:T167 R25M NetM7PM Mtg2ndW

R25M is non-compliant. The spec says that m and k are lower case.

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


Re: {Some tags disabled} Re: FREQ OBJECT Uniqueness

Robert Bruninga
 

my preference is to have the callsign in the object name.
... I would rather see the callsign for the object name
followed by an "R"...
I think you miss the objective. Sure locals may know the repeaters by
callsign, but the whole point of FREQ objects is for travelers. So they can
see what freq is recommended wherever they are.

If I drove through your area, there is no way I would notice that VE7RSI
flashing on my display is a repeater and it is unsafe to assume that even if
I did recognize it, I would take my hands off the wheel to go through
multiple button pushes to search for it in the station list and then click
on it just to see the frequency.

The purpose of the FREQ object is so that when it is received, it FLASHES
"147.105 R" on the front panel for 10 seconds alerting me that I am in range
of that repeater and that all I have to do is press ONE button to have the
radio go there (including with the correct tone and offset).

That kind of multilevel COGNITION is not possible for Travelers from just a
local callsign.

Bob, Wb4APR


-----Original Message-----
From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf
Of Keith VE7GDH
Sent: Tuesday, May 08, 2012 3:14 PM
To: aprsisce@yahoogroups.com
Subject: Re: {Some tags disabled} Re: [aprsisce] FREQ OBJECT Uniqueness

... I just wanted to jump in and say
that my preference is to have the callsign in the object name. I
know that Bob doesn't like this, but I would rather see the
callsign for the object name followed by an "R"... e.g. VE7RSI-R.
I know Bob and others prefer to see the frequency there, but
my preference would be for the callsign. Bob called them (was
it on this list or the APRS SIG?) useless callsigns. Around here
I would say that at least half the hams refer to repeaters by their
callsign and not just by frequency which might be more expected
from visitors not familiar with the area. When I call another
ham, I don't say "hey Lynn on 732 this is VE7GDH". I call
them by callsign. I refer to repeaters the same way. It
doesn't happen so much around here, but some places there
is definitely overlapping coverage and only the tone differentiates
them. Callsigns are a lot more unique than frequencies.

For a few years, I was sending out an object something like
147.320 (followed by what I can't remember) and when I
had a club-owned D72 to play with (I have it here again) I
got to try the TUNE function and it didn't work. I really don't
remember what I was using for the object name, but if I
searched my email I could find it. I got the format from
the (then recommended) format or at least I thought that I
had, but when I got the D72 to play with, it wouldn't TUNE
to the frequency unless I included MHz. (Yes, James, I have
a reply to you and [the other] Bob still in my drafts folder...
I still have to finish it off and kick it out the door!) Here it
is a couple of months later and the subject has come back
with a vengeance!

James - as I mentioned, I want to finish off that message to
you and (the other) Bob, but so far, I haven't been to send an
offset to the D72. The radio has automatically applied the
offset . I've been busy, but I'll try and do some more testing
later today and I'll post here and on the APRS SIG. I can't
comment on the spec, but I can comment on what works and
what doesn't on a D72A.

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



------------------------------------

Yahoo! Groups Links


Re: {Some tags disabled} Re: FREQ OBJECT Uniqueness

Keith VE7GDH
 

Lynn KJ4ERJ wrote...

Well stated! And if someone wants to put the frequency into the
object name to make it visible on the station list and/or map labels,
so be it, but the REAL information is carefully formatted and fully
contained in the comment.
I'm still trying to find the time to find all the combinations that
work and don't work with a D72, and I'll post it here and on
the APRS SIG when I'm done. I just wanted to jump in and say
that my preference is to have the callsign in the object name. I
know that Bob doesn't like this, but I would rather see the
callsign for the object name followed by an "R"... e.g. VE7RSI-R.
I know Bob and others prefer to see the frequency there, but
my preference would be for the callsign. Bob called them (was
it on this list or the APRS SIG?) useless callsigns. Around here
I would say that at least half the hams refer to repeaters by their
callsign and not just by frequency which might be more expected
from visitors not familiar with the area. When I call another
ham, I don't say "hey Lynn on 732 this is VE7GDH". I call
them by callsign. I refer to repeaters the same way. It
doesn't happen so much around here, but some places there
is definitely overlapping coverage and only the tone differentiates
them. Callsigns are a lot more unique than frequencies.

For a few years, I was sending out an object something like
147.320 (followed by what I can't remember) and when I
had a club-owned D72 to play with (I have it here again) I
got to try the TUNE function and it didn't work. I really don't
remember what I was using for the object name, but if I
searched my email I could find it. I got the format from
the (then recommended) format or at least I thought that I
had, but when I got the D72 to play with, it wouldn't TUNE
to the frequency unless I included MHz. (Yes, James, I have
a reply to you and [the other] Bob still in my drafts folder...
I still have to finish it off and kick it out the door!) Here it
is a couple of months later and the subject has come back
with a vengeance!

James - as I mentioned, I want to finish off that message to
you and (the other) Bob, but so far, I haven't been to send an
offset to the D72. The radio has automatically applied the
offset . I've been busy, but I'll try and do some more testing
later today and I'll post here and on the APRS SIG. I can't
comment on the spec, but I can comment on what works and
what doesn't on a D72A.

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


Re: FREQ OBJECT Uniqueness

Robert Bruninga
 

Until changes to the specification are made, the Kenwood
and Yaesu radios are non-compliant..
Interesting comment. Other than the FTM-350 not QSYing to a FREQ OBJECT
(without a duplicate FREQ in the comment) can you elaborate on what you
think is not compliant in the Kenwood?

Bob, Wb4APR


Re: QRUW2CXM objects (was: FreqSpec Homework...)

Randy Love
 

?? before a call means that the D700/7/710/72 decoded the packet, but doesn't understand the format -or- doesn't know what to do with that particular packet. It is better than not flashing a callsign on the screen at all, but not by much. Since that packet from the object doesn't contain a position or the radio doesn't already have a position for the object, it will just ignored the packet, other than the quick flash of the callsign. 

WF5X


On Tue, May 8, 2012 at 2:32 PM, apenadragon <kc2ant@...> wrote:
 

it's not even doing that.

The D700 displays an object for the QRUW2CXM as it does for any other object.

The D710 does not show the object. I can see the "??QRUW2CXM" flash in the display of the D710 when the packet comes accross, but it doesn't translate to a displayable object.

Adam
KC2ANT



--- In aprsisce@..., "Lynn W Deffenbaugh (Mr)" wrote:
>
> On 5/8/2012 10:32 AM, apenadragon wrote:
> > I will say, that my D710 still doesn't recognize the QRUW2CXM object, but that's different than this topic. Just trying to get it back on your radar.
>
> Please define "recognize"? the QRU* objects only contain a description
> of the available groups. What are you expecting the D710 to do other
> than display this description? Or isn't it even doing that?
>
> Lynn (D) - K4JERJ - Author of APRSISCE for Windows Mobile and Win32
>



Re: QRUW2CXM objects (was: FreqSpec Homework...)

Adam Mahnke
 

it's not even doing that.

The D700 displays an object for the QRUW2CXM as it does for any other object.

The D710 does not show the object. I can see the "??QRUW2CXM" flash in the display of the D710 when the packet comes accross, but it doesn't translate to a displayable object.

Adam
KC2ANT

--- In aprsisce@yahoogroups.com, "Lynn W Deffenbaugh (Mr)" <kj4erj@...> wrote:

On 5/8/2012 10:32 AM, apenadragon wrote:
I will say, that my D710 still doesn't recognize the QRUW2CXM object, but that's different than this topic. Just trying to get it back on your radar.
Please define "recognize"? the QRU* objects only contain a description
of the available groups. What are you expecting the D710 to do other
than display this description? Or isn't it even doing that?

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


Re: FREQ OBJECT Uniqueness

Lynn Deffenbaugh
 

On 5/8/2012 2:14 PM, Randy Love wrote:
I'm all for one specification that contains all aspects of the frequency needed to make / use the voice connectivity inclusive, being defined in the comment for the object - whatever object that may be. Sure would simply making repeater objects on digi's!

Well stated!  And if someone wants to put the frequency into the object name to make it visible on the station list and/or map labels, so be it, but the REAL information is carefully formatted and fully contained in the comment.  I LOVE IT!  And it's even probably (hopefully) fully backward compatible with all the QSY-capable radios out there.

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


Re: FREQ OBJECT Uniqueness

Randy Love
 

On Tue, May 8, 2012 at 2:01 PM, James Ewen <ve6srv@...> wrote:
 

On Tue, May 8, 2012 at 11:49 AM, Randy Love <rlove31@...> wrote:

> If you need 3 digits after the decimal, drop the decimal (i.e.
> 147180MTC).

You can NOT do that, the specification REQUIRES the decimal.
 
Ah, but see, if it doesn't have a decimal in it, it isn't a FREQ OBJECT, it just becomes a regular object with a position and FREQ COMMENT. 

Yes, I understand the current debate and reasoning, but to assume that I was setting up 147180MTC to be a FREQ OBJECT is another reason things can get so confusing.

I'm all for one specification that contains all aspects of the frequency needed to make / use the voice connectivity inclusive, being defined in the comment for the object - whatever object that may be. Sure would simply making repeater objects on digi's!

Randy
WF5X


Re: FREQ OBJECT Uniqueness

Lynn Deffenbaugh
 

ARGH!

On 5/8/2012 1:49 PM, Randy Love wrote:
If you need 3 digits after the decimal, drop the decimal (i.e.
147180MTC).

Drop the decimal and you no longer have a frequency object. The format is very specifically FFF.FFFxy and the dot is required to be recognized. If you do this, it's just like a callsign-named repeater that a human might be able to pick out of a list and the comment better carry the properly formatted FFF.FFFMHz specification or it will almost definitely not be usable by APRS radios and other mechanized parsers.

So, what about a 4th digit? Well, it really isn't necessary *if* you
have the radio set to the proper step size, but then again, that doesn't matter if the Freq Comment of the Object is properly configured.

Yeah, as soon as we nail down for sure what "properly" is, because in the current spec, an object of 146.850PC cannot start the comment with 146.850MHz unless it's a simplex repeater, even though that seems (spreading hear-say here) to be required by Yaesus.

Lynn (D) - KJ4ERJ - Wanting to go spend $2,000 to own one of each radio to test for myself!

Randy
WF5X





Re: FREQ OBJECT Uniqueness

Lynn Deffenbaugh
 

On 5/8/2012 1:49 PM, Randy Love wrote:

18261 - 18280 of 35496