| |
ZL3AI > APRDIG 24.12.06 07:45l 278 Lines 8139 Bytes #999 (0) @ WW
BID : 9394-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 30 #22, 1/2
Path: DB0FHN<DB0FOR<DB0SIF<DB0EA<DB0NOS<DB0BI<DB0WAL<DB0FBB<DB0IUZ<DB0GOS<
ON0AR<I0TVL<TU5EX<7M3TJZ<ZL2BAU
Sent: 061224/0634Z @:ZL2BAU.#79.NZL.OC #:22617 [Waimate] $:9394-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Today's Topics:
1. Re: 9600 baud TX equalization (Ian ZL1VFO)
2. Packet errors (Bogdan, Rick)
3. RE: Packet errors (Bill Diaz)
4. RE: RE: Packet errors (Bogdan, Rick)
5. RE: Packet errors (Bill Diaz)
6. Re: 9600 baud TX equalization (Ray Wells)
7. RE: RE: Packet errors (Bogdan, Rick)
8. Re: Packet errors (Steve Dimse)
9. Re: RE: Packet errors (Steve Dimse)
10. Re: Packet errors (Jason Winningham)
11. 10.151 lsb (James Smith)
12. RE: Packet errors (Bogdan, Rick)
13. Re: 9600 baud TX equalization (Ian ZL1VFO)
14. ande heard (Kevin Deckert)
----------------------------------------------------------------------
Message: 1
Date: Sat, 23 Dec 2006 11:25:15 +1300
From: Ian ZL1VFO <zl1vfo_at_yahoo.co.uk>
Subject: Re: [aprssig] 9600 baud TX equalization
>Message: 1
>Date: Thu, 21 Dec 2006 10:22:41 -0800
>From: "Scott Miller" <scott_at_opentrac.org>
>I was just reading over the original docs on the G3RUH modem yesterday, and
>I noticed that it makes a big deal of transmit equalization. Several
>different waveforms were provided to compensate for frequency and phase
>response in the transmitter. In reading the manual for the KPC-9612+, I
>only see an option for RX equalization. What's the deal? Are modern radios
>consistent enough in their frequency and phase response to not require
>adjustment on the TX side?
>Scott
>N1VG
Most radios I'm aware of you have to connect deep inside to the modulator
and demodulator circuits, so hopefully at that point the phase & frequency
response shouldn't be too mangled, and should (hopefully) be reasonably
consistant (allowing for levels, of course).
Anyway, where did you find the docs on the G3RUH modem? - I wouldn't mind
having a read of them sometime...
73,
Ian ZL1VFO
------------------------------
Message: 2
Date: Fri, 22 Dec 2006 18:21:55 -0500
From: "Bogdan, Rick" <rbogdan_at_ursinus.edu>
Subject: [aprssig] Packet errors
Hello to the group, and Happy Holidays.
Can anyone tell me what's wrong with this packet?
ka1udx>APRS,TCPXX*,qAX,T2WXCWOP:@222322z1234.56N/01234.56W_045/001g006t042a1wkad
1ux>APRS,TCPXX*,qAX,T2WXCWOP:@222322z1234.56N/01234.56W_045/001g006t042a1w
It shows up at FindU.com as a bad packet.
Thanks in advance,
Rick ka1udx
http://webpages.ursinus.edu/ka1udx
------------------------------
Message: 3
Date: Fri, 22 Dec 2006 17:46:00 -0600
From: "Bill Diaz" <william.diaz_at_comcast.net>
Subject: [aprssig] RE: Packet errors
Rick,
Looks like 2 packets contancated into one. They appear to be identical
packets generated by a1w.
Bill KC9XG
------------------------------
Message: 4
Date: Fri, 22 Dec 2006 18:58:27 -0500
From: "Bogdan, Rick" <rbogdan_at_ursinus.edu>
Subject: RE: [aprssig] RE: Packet errors
Hi Bill,
Now that you mention it and looking at it again, I think you are right. How
how to fix it. It's being generated by Wserver, weather software for my
weather station. I just got it back up and running, just not correctly.
Rick ka1udx
------------------------------
Message: 5
Date: Fri, 22 Dec 2006 18:01:05 -0600
From: "Bill Diaz" <william.diaz_at_comcast.net>
Subject: [aprssig] RE: Packet errors
Rick,
Are you really at 12 degrees, 34.56 minutes North and 12 degrees
34.56 minutes west? I don't think so since qrz.com indicates you are in
licensed in Pennsylvania. The repeating 123456 certainly seems suspicious.
The originating call sign is usually upper case, but yours are lower case.
The FindU error page at
http://www.findu.com/cgi-bin/errorlist.cgi?call=ka1udx
takes issue with your packets also.
Bill
------------------------------
Message: 6
Date: Sat, 23 Dec 2006 11:18:04 +1100
From: Ray Wells <vk2tv_at_exemail.com.au>
Subject: Re: [aprssig] 9600 baud TX equalization
Ian ZL1VFO wrote:
>>I was just reading over the original docs on the G3RUH modem yesterday, and
>>I noticed that it makes a big deal of transmit equalization. Several
>>different waveforms were provided to compensate for frequency and phase
>>response in the transmitter. In reading the manual for the KPC-9612+, I
>>only see an option for RX equalization. What's the deal? Are modern radios
>>consistent enough in their frequency and phase response to not require
>>adjustment on the TX side?
>
>>Scott
>>N1VG
>
>Most radios I'm aware of you have to connect deep inside to the
>modulator and demodulator circuits, so hopefully at that point the
>phase & frequency response shouldn't be too mangled, and should
>(hopefully) be reasonably consistant (allowing for levels, of course).
>
>Anyway, where did you find the docs on the G3RUH modem? - I wouldn't
>mind having a read of them sometime...
>
>73,
>Ian ZL1VFO
Ian,
Take a look here, it may be what you're after.
http://www.jrmiller.demon.co.uk/products/figs/man9k6.pdf
Cheers
Ray vk2tv
------------------------------
Message: 7
Date: Fri, 22 Dec 2006 19:18:29 -0500
From: "Bogdan, Rick" <rbogdan_at_ursinus.edu>
Subject: RE: [aprssig] RE: Packet errors
Ok, changed a few things and this is what comes up:
KA1UDX>APRS,TCPXX*,qAX,T2WXCWOP:@230016z40.2180/-75.4830_045/004g003t043a1w
I think I pasted the original twice, my mistake with the email.
Rick ka1udx
------------------------------
Message: 8
Date: Fri, 22 Dec 2006 19:23:14 -0500
From: Steve Dimse <steve_at_dimse.com>
Subject: Re: [aprssig] Packet errors
On Dec 22, 2006, at 6:21 PM, Bogdan, Rick wrote:
>Can anyone tell me what's wrong with this packet?
>
>ka1udx>APRS,TCPXX*,qAX,T2WXCWOP:_at_222322z1234.56N/
>01234.56W_045/001g006t042a1wka1udx>APRS,TCPXX*,qAX,T2WXCWOP:_at_222322z12
>34.56N/01234.56W_045/001g006t042a1w
>
>It shows up at FindU.com as a bad packet.
Presuming that you simply hit the paste button twice, explaining the double
packet (it does not show double on the findU error page or the raw data
page) it is a weird side effect of using a made up lat/lon. Many trackers
and programs send zeros as a lat/lon when none is entered. I could test for
this with a compound boolean like
(($lat == 0) && ($lon == 0))
instead I just use
($lat+$lon == 0)
Since western hemisphere lats are represented as negative, the sum of the
lat and lon you are sending add up to zero.
I didn't intend for this test to look for people that enter the same made
up number for lat and lon, but it does, and it caught you! You should not
be sending bad positions, it makes maps in all the clients look screwy, and
messes up things like my near page.
Enter your correct latitude and longitude and it will work fine!
Steve K4HG
------------------------------
Message: 9
Date: Fri, 22 Dec 2006 19:23:56 -0500
From: Steve Dimse <steve_at_dimse.com>
Subject: Re: [aprssig] RE: Packet errors
On Dec 22, 2006, at 7:18 PM, Bogdan, Rick wrote:
>KA1UDX>APRS,TCPXX*,qAX,T2WXCWOP:@230016z40.2180/-75.4830_045/004g003t0
>43a1w
This is a wrong format for the lat and lon!
Steve K4HG
------------------------------
Message: 10
Date: Fri, 22 Dec 2006 18:38:05 -0600
From: Jason Winningham <jdw_at_eng.uah.edu>
Subject: Re: [aprssig] Packet errors
On Dec 22, 2006, at 6:23 PM, Steve Dimse wrote:
>instead I just use
>
>($lat+$lon == 0)
>
>Since western hemisphere lats are represented as negative, the sum
>of the lat and lon you are sending add up to zero.
So there's a line (OK, fairly narrow line mostly over water) where packets
get rejected as a result of a faulty test?
I'd guess position ambiguity makes this imaginary line wider for those
using it?
-Jason
kg4wsv
------------------------------
Message: 11
Date: Fri, 22 Dec 2006 19:45:28 -0500
From: James Smith <k9apr_at_tawg.org>
Subject: [aprssig] 10.151 lsb
Someone has a very distorted signal on 30 meter HF freq spanning a least
9khz and guess what? it isn't me, this time. Even though, I did get the
faithful letter saying it was my station causing the distortion from the
FCC field office in D.C. Anyway, I'm in receive mode only now. So whoever
has a station on that frequency you might want to check your equipment. I
couldn't decode the signal, but did see it via a spectrum analyzer. This is
just a FYI, not whining!!!!
73, K9APR
------------------------------
Read previous mail | Read next mail
| |
