| |
CX2SA > SATDIG 20.11.17 19:57l 801 Lines 28062 Bytes #999 (0) @ WW
BID : AMSATBB12303
Read: GUEST
Subj: AMSAT-BB-digest V12 303
Path: IW8PGT<IR2UBX<SR1BSZ<SV1CMG<ON0AR<OZ5BBS<CX2SA
Sent: 171120/1747Z @:CX2SA.SAL.URY.SOAM #:27167 [Salto] FBB7.00e $:AMSATBB12303
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. Re: AO 91 identification (Nico Janssen)
2. AO-91 (Alex Weimer)
3. New Satellite ADIF Logging Tool (Jeremy Turner)
4. Re: AO 91 identification (Ray Hoad)
5. Re: Foxtelem and Kenwood TM-V71 signal to noise ratio
(Nitin Muttin)
6. Re: AO-91 - Safe Mode Annoucement (Jerry Buxton)
7. Re: Foxtelem and Kenwood TM-V71 signal to noise ratio
(Kevin Schuchmann)
8. Re: AO-91 TLEs/KEPS with FoxTelem (George Henry)
9. Re: Foxtelem and Kenwood TM-V71 signal to noise ratio
(Nitin Muttin)
10. Re: AO-91 - Safe Mode Annoucement (John Zaruba Jr)
11. Thanks to KE4AL (Carlos Cardon)
12. Re: New Satellite ADIF Logging Tool (Jeremy Turner)
----------------------------------------------------------------------
Message: 1
Date: Sun, 19 Nov 2017 22:44:35 +0100
From: Nico Janssen <hamsat@xxxxxx.xx>
To: AMSAT <amsat-bb@xxxxx.xxx>, Ray Hoad <ray.hoad@xxxxxxxx.xxx>
Subject: Re: [amsat-bb] AO 91 identification
Message-ID: <88474997-9d67-46a2-43af-6efb1f2949c1@xxxxxx.xx>
Content-Type: text/plain; charset=utf-8; format=flowed
All,
The missing two TLE sets have now been published by 18SPCS.
The reason it took so long is probably that it was hard to detect
all three 1U Cubesats with a distance between them of only a few
kilometers. Since they are now less than 2 seconds apart, it is not
yet possible to determine which one is AO 91.
So AO 91 is either object 43016, 43017 or 43018. For the time being
you can use any of the TLE sets for these three objects.
73,
Nico PA0DLO
On 19-11-17 15:26, Nico Janssen wrote:
> All,
>
> Currently only three TLE sets have been published for the five
> Cubesats that were launched with JPSS 1. Now 18SPCS claims
> that JPSS 1 (soon to be called NOAA 20) is object 43013, that
> MiRaTa is object 43014 and that Buccaneer RRM is object 43015.
>
> Detailed doppler measurements show that AO 91 almost certainly
> is object 43016 (2017-073D). But since two TLE sets are still
> missing, we shall have to wait to be absolutely sure.
>
> 73,
> Nico PA0DLO
>
>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership.
> Opinions expressed
> are solely those of the author, and do not reflect the official views
> of AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite
> program!
> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
>
------------------------------
Message: 2
Date: Sun, 19 Nov 2017 22:05:15 +0000 (UTC)
From: Alex Weimer <kc7mg@xxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] AO-91
Message-ID: <984163920.1088045.1511129115688@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
AO-91? full quieting when heard in grid DM42 Arizona at? 1922 Z.. Very loud
through complete pass.? JACK? KC7MG
------------------------------
Message: 3
Date: Sun, 19 Nov 2017 16:21:49 -0800
From: Jeremy Turner <jeremy@xxxxxxxxxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] New Satellite ADIF Logging Tool
Message-ID:
<CAO4qtUfxMbD4GQzzk4hc1K=NKcbTTen6G9Gpa7PDc0q5pDXSKg@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"
Hello all,
One of the challenges that I've had since starting to work satellites is my
logging workflow. I don't always get back to my logging app to log QSOs
immediately, I have found it challenging to get all the right settings to
get LOTW to match, and some logging apps don't even allow me to type all
the right settings in. I hated having to fill in 10 fields per QSO, that
always seemed to reset to the wrong values with every QSO!
I wrote myself a little Python console app to improve my workflow, and I
want to share Python Satellite ADIF or pysatadif with you.
For instance, if there is an SO-50 pass where I make several QSOs, I would
type:
pysatadif --satname SO-50 --timeon 1450 --qsodate 20171119 --qso KO6RM,DN70
--qso N0CALL,EL99
I can add as many QSOs per pass as I need. I can leave off the date if the
QSO was on the current UTC day.
The software pulls my station defaults including rig, power, and my grid
square from a defaults file (automatically generated for you on first run),
and pulls frequency, band, and mode from a directory of satellite info.
These can be overridden for you rovers and special event ops out there.
The resulting ADIF output can be imported into your favorite logging app,
TQSL or whatever else you'd like.
If this sounds interesting, you can install pysatadif on Windows, Mac or
Linux using Python 2.7 or 3.6 by running 'pip install pysatadif'.
For more information, check out:
https://github.com/jeremymturner/pysatadif
https://pypi.python.org/pypi/pysatadif
If you have questions, feel free to contact me off-list.
73,
Jeremy / KO6RM
jeremy@xxxxxxxxxxxxx.xxx
------------------------------
Message: 4
Date: Sun, 19 Nov 2017 21:28:00 -0600
From: "Ray Hoad" <ray.hoad@xxxxxxxx.xxx>
To: "'Nico Janssen'" <hamsat@xxxxxx.xx>, "'AMSAT'"
<amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] AO 91 identification
Message-ID: <000a01d361af$917a5180$b46ef480$@xxxxxxxx.xxx>
Content-Type: text/plain; charset="utf-8"
As noted the objects are still too close to call who is who.
For the time being, I will continue to use NORAD CAT ID 43015 until it
becomes obvious that 43016, 43017, or 43018 is the preferred TLE set. I do
not want to change CAT IDs any more than necessary.
The AO-91 team is still very happy with object 43015 TLE, but as is normal
in these tight groupings, a change is also very probable.
Thanks Nico!
Ray Hoad
WA5QGD
Orbital Elements Manager
-----Original Message-----
From: Nico Janssen [mailto:hamsat@xxxxxx.xxx
Sent: Sunday, November 19, 2017 15:45
To: AMSAT <amsat-bb@xxxxx.xxx>; Ray Hoad <ray.hoad@xxxxxxxx.xxx>
Subject: Re: [amsat-bb] AO 91 identification
All,
The missing two TLE sets have now been published by 18SPCS.
The reason it took so long is probably that it was hard to detect
all three 1U Cubesats with a distance between them of only a few
kilometers. Since they are now less than 2 seconds apart, it is not
yet possible to determine which one is AO 91.
So AO 91 is either object 43016, 43017 or 43018. For the time being
you can use any of the TLE sets for these three objects.
73,
Nico PA0DLO
On 19-11-17 15:26, Nico Janssen wrote:
> All,
>
> Currently only three TLE sets have been published for the five
> Cubesats that were launched with JPSS 1. Now 18SPCS claims
> that JPSS 1 (soon to be called NOAA 20) is object 43013, that
> MiRaTa is object 43014 and that Buccaneer RRM is object 43015.
>
> Detailed doppler measurements show that AO 91 almost certainly
> is object 43016 (2017-073D). But since two TLE sets are still
> missing, we shall have to wait to be absolutely sure.
>
> 73,
> Nico PA0DLO
>
>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership.
> Opinions expressed
> are solely those of the author, and do not reflect the official views
> of AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite
> program!
> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
>
------------------------------
Message: 5
Date: Mon, 20 Nov 2017 05:21:30 +0000 (UTC)
From: Nitin Muttin <vu3tyg@xxxxx.xx.xx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Foxtelem and Kenwood TM-V71 signal to noise
ratio
Message-ID: <530818124.1707760.1511155290024@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
What I understand from the Decoder manual is that 9600 is for special
experiments and under normal conditions the data under voice (DUV) is 200
bps hence i dont think 9600 setting needs to be enabled / wired at the
radio.?73
Nitin [VU3TYG]
From: John Brier <johnbrier@xxxxx.xxx>
To: Scott <scott23192@xxxxx.xxx>
Cc: AMSAT BB <amsat-bb@xxxxx.xxx>
Sent: Monday, 20 November 2017 1:18 AM
Subject: Re: [amsat-bb] Foxtelem and Kenwood TM-V71 signal to noise ratio
Thanks for trying Scott.
I do have the 9600 setting enabled. I think you can also set which side of
the radio is used for data, and I believe I set it right, but I'm going to
double check.
Thanks for the USB sound card link. I actually have a 10 yr old laptop with
mic/line in that I might try. If I have to use a laptop during the pass I
almost feel like I might as well just go SDR. In general I don't like to
have things anchored to the ground and me, which is why I carry all my gear
on my body.
73, John Brier KG4AKV
On Nov 19, 2017 2:31 PM, "Scott" <scott23192@xxxxx.xxx> wrote:
Hi John.
No decodes here from your audio recording, either.? And the reception was
crystal clear.
Did set the data speed menu option to 9600?? I don't know if the 1200
setting would work with AO-91's DUV data or not; I use an SDR, so my RX
audio is already "in" the computer and connected to FoxTelem via VB Audio
cable.
Also, I have been using the following USB audio adapter for data audio
in/out with success in case you need a device for your computer that can
accomodate "line" level audio input:
https://www.amazon.com/Griffin-Technology-iMic-
original-Adapter/dp/B003Y5D776
73!
-Scott,? K4KDR
===============================
On Sun, Nov 19, 2017 at 2:16 PM, John Brier <johnbrier@xxxxx.xxx> wrote:
> Oh interesting. I didn't consider that. I will see if I can hook the
> radio into my laptop directly, or try another recorder, though my
> other recorder does 44.1 KHz only, not 48 KHz like the manual says is
> ideal.
>
> Thanks Paul.
>
> 73, John Brier KG4AKV
>
> On Sun, Nov 19, 2017 at 2:11 PM, Paul Stoetzer <n8hm@xxxx.xxx> wrote:
> > Seems likely that some sort of audio filtering is going on in your
> recorder.
> >
> > 73,
> >
> > Paul, N8HM
> >
> > On Sun, Nov 19, 2017 at 2:07 PM, John Brier <johnbrier@xxxxx.xxx> wrote:
> >> I made a cable to tap the 9600 data pin off my Kenwood and I'm trying
> >> to decode telemetry from AO-91.
> >>
> >> I am having trouble getting a continuously clean reception, so I don't
> >> expect frames, which I'm not getting, but parts of the reception are
> >> fine and yet FoxTelem still shows a low S/R of 1.2, 1.5 at best. I am
> >> wondering if there is still some filtering going on. I notice the
> >> peaks of the "bits" are not flat like they are supposed to be
> >> according to the manual:
> >>
> >> https://imgur.com/pfX7cSK
> >>
> >> I am recording the audio off the radio into a Zoom H1 at 48,000 KHz
> 16bit wav.
> >>
> >> Maybe I should try hooking the radio directly up to a computer into
> FoxTelem.
> >>
> >> Here is my recording:
> >>
> >> https://www.dropbox.com/s/ineqhoprz50ljl3/2017-11-19_-_
> 1743_UTC_-_AO-91_-_FM05_-_KG4AKV_just_transmissions.wav?dl=0
> >>
> >> Ideas?
> >>
> >> 73, John Brier KG4AKV
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
to all interested persons worldwide without requiring membership. Opinions
expressed
are solely those of the author, and do not reflect the official views of
AMSAT-NA.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
to all interested persons worldwide without requiring membership. Opinions
expressed
are solely those of the author, and do not reflect the official views of
AMSAT-NA.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 6
Date: Sun, 19 Nov 2017 23:59:18 -0600
From: Jerry Buxton <n0jy@xxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] AO-91 - Safe Mode Annoucement
Message-ID: <e837d0a0-ad23-bd5a-8ec5-ee1ad0063409@xxxxx.xxx>
Content-Type: text/plain; charset=utf-8
That is a nice recording, Paul.
I would like to state for the record that the ID is not actually a
"child", Veronica Monteiro was just starting in college when we made the
Fox-1x recordings.? Because of the need to sharply filter the recordings
with a 350 Hz high pass to eliminate any audio in the DUV telemetry
frequency range, it does have the effect of making her sound younger.?
That coupled with whatever your particular SDR or transceiver filtering
adds creates the rather common misconception that the recordings were of
a young child.
Veronica Monteiro is the daughter of the late Tony Monteiro AA2TX, who
as AMSAT Vice-President of Engineering brought the Fox-1 1U CubeSat
concept and project to the Board of Directors and "sold" the Fox-1
Program that has now produced 5 (OK 4 1/2 until Fox-1E is complete)
Fox-1 CubeSats.? The concept included a Morse Code ID for the beacon of
the FM repeaters, as stated in the System Requirements:
3.9.6 If the downlink transmitter has been un-keyed for a period of 5
minutes, the satellite shall send " HI THIS IS AMSAT FOX " in Morse code
via a keyed audio tone on the downlink transmitter.
When designing the software for the ID back in 2014 after I was
appointed VPE, the Fox-1 Team thought it would be a nice idea to use a
voice ID instead of Morse Code given the abilities of the IHU and
available memory.? In kicking around ideas about who would record the ID
it came to us that it would be a nice tribute to Tony if Veronica were
the voice ID.? Fox-1 software engineer Burns Fisher, who lives near
Tony's family, contacted them.? Veronica graciously agreed, and Burns
set out with his recorder to capture Veronica to become the voice of the
Fox-1 FM satellites.
>From their many clips I was able to assemble the various Safe Mode and
Transponder Mode IDs for each satellite/name, so I guess I'm to blame
for the processing I did that makes her sound like a child...
I listened to Veronica's IDs I'll bet hundreds if not a thousand times
in testing the Fox-1 engineering model and Fox-1A through D, and I still
get a kick and a smile from it every time I hear her - especially from
orbit!
Jerry Buxton, N?JY
On 11/19/2017 12:57, Paul Andrews wrote:
> Satellite Fans,
>
> I pointed my 2 x XP28 moonbounce antenna at AO-91 today. The AO-91
> pass was nearly directly overhead in FN20. The FM signal quality was
> so high - you can hear the room acoustics in the recording of the
> child's voice. Very cool.
>
> Here is a YouTube link - https://youtu.be/gepcNt2sW2g
>
> 73 - Paul - W2HRO
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
expressed
> are solely those of the author, and do not reflect the official views of
AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
>
>
------------------------------
Message: 7
Date: Sun, 19 Nov 2017 22:17:23 -0800
From: Kevin Schuchmann <wa7fwf@xxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Foxtelem and Kenwood TM-V71 signal to noise
ratio
Message-ID: <52a32b02-a289-6aba-8a85-54aa773af1bd@xxxxx.xxx>
Content-Type: text/plain; charset=utf-8; format=flowed
I will mention that for a Icom IC-9100 you need it in Data 9600 mode,?
the reason being that 9600 gives you the full bandwidth, in non-data
mode the radio filters out the sub-audible tones.
73 Kevin WA7FWF
On 11/19/2017 9:21 PM, Nitin Muttin via AMSAT-BB wrote:
> What I understand from the Decoder manual is that 9600 is for special
experiments and under normal conditions the data under voice (DUV) is 200
bps hence i dont think 9600 setting needs to be enabled / wired at the
radio.?73
> Nitin [VU3TYG]
> From: John Brier <johnbrier@xxxxx.xxx>
>
------------------------------
Message: 8
Date: Mon, 20 Nov 2017 00:33:17 -0600
From: "George Henry" <ka3hsw@xxx.xxx>
To: "'Chris Thompson'" <g0kla@xxxx.xxx>, <AMSAT-BB@xxxxx.xxx>
Subject: Re: [amsat-bb] AO-91 TLEs/KEPS with FoxTelem
Message-ID: <CEBA762956B14B6DA1302B255D2FD8B2@xxxxxxxxxxx>
Content-Type: text/plain; charset="UTF-8"
I did that, but FoxTelem complains that it can't find the TLE for AO-91.
Nasabare.txt is in the download folder, and FoxTelem has extracted the keps
for AO-85, but not AO-91. I even tried copying and pasting the AO-91 data
from nasabare.txt to FOX2.tle, but the program still complains that they are
missing or corrupt...
Any suggestions?
George, KA3HSW
-----Original Message-----
From: AMSAT-BB [mailto:amsat-bb-bounces@xxxxx.xxxx On Behalf Of Chris Thompson
Sent: Saturday, November 18, 2017 7:20 PM
To: AMSAT-BB@xxxxx.xxx
Subject: [amsat-bb] AO-91 TLEs/KEPS with FoxTelem
?If you are using FoxTelem and want it to automatically grab the latest
keps, or be in sync with the name you are using in SatPC32, then you need
to change the name of the spacecraft from RadFxSat to AO-91. You can do
that from the spacecraft menu on the setup page. Put AO-91 in the name box
instead of RadFxSat. If you use a different source of TLEs now or in the
future, you can change that field to match.
And no, I'm not able to get the OSCAR number in advance so that I can build
it into the release :) It will be in future releases though.
73
Chris?
--
Chris E. Thompson
chrisethompson@xxxxx.xxx
g0kla@xxxx.xxx
------------------------------
Message: 9
Date: Mon, 20 Nov 2017 10:49:50 +0000 (UTC)
From: Nitin Muttin <vu3tyg@xxxxx.xx.xx>
To: Kevin Schuchmann <wa7fwf@xxxxx.xxx>, "amsat-bb@xxxxx.xxxx
<amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Foxtelem and Kenwood TM-V71 signal to noise
ratio
Message-ID: <1891446339.2103371.1511174990560@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
Noted Kevin, so my putting the radio in 9600 data mode the audio is now
available from the discriminator directly. For some reason I am unable to
decode the telemetry from AO85 and AO91 using a ICOM 821H and Signalink USB.
Will try soon with an SDR as well.?73
Nitin [VU3TYG]
From: Kevin Schuchmann <wa7fwf@xxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Sent: Monday, 20 November 2017 11:50 AM
Subject: Re: [amsat-bb] Foxtelem and Kenwood TM-V71 signal to noise ratio
I will mention that for a Icom IC-9100 you need it in Data 9600 mode,?
the reason being that 9600 gives you the full bandwidth, in non-data
mode the radio filters out the sub-audible tones.
73 Kevin WA7FWF
On 11/19/2017 9:21 PM, Nitin Muttin via AMSAT-BB wrote:
> What I understand from the Decoder manual is that 9600 is for special
experiments and under normal conditions the data under voice (DUV) is 200
bps hence i dont think 9600 setting needs to be enabled / wired at the
radio.?73
> Nitin [VU3TYG]
>? ? ? ? From: John Brier <johnbrier@xxxxx.xxx>
>
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
to all interested persons worldwide without requiring membership. Opinions
expressed
are solely those of the author, and do not reflect the official views of
AMSAT-NA.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 10
Date: Mon, 20 Nov 2017 06:59:02 -0500
From: John Zaruba Jr <aa2bn@xxxxxxx.xxx>
To: Jerry Buxton <n0jy@xxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] AO-91 - Safe Mode Annoucement
Message-ID: <7EBC0BA8-909A-4A28-92E7-7EAB958EC70F@xxxxxxx.xxx>
Content-Type: text/plain; charset=utf-8
What a wonderful tribute to Tony AA2TX!
73,
John K2ZA
AMSAT #22683
Sent from my iPhone
> On Nov 20, 2017, at 00:59, Jerry Buxton <n0jy@xxxxx.xxx> wrote:
>
> That is a nice recording, Paul.
>
> I would like to state for the record that the ID is not actually a
> "child", Veronica Monteiro was just starting in college when we made the
> Fox-1x recordings. Because of the need to sharply filter the recordings
> with a 350 Hz high pass to eliminate any audio in the DUV telemetry
> frequency range, it does have the effect of making her sound younger.
> That coupled with whatever your particular SDR or transceiver filtering
> adds creates the rather common misconception that the recordings were of
> a young child.
>
> Veronica Monteiro is the daughter of the late Tony Monteiro AA2TX, who
> as AMSAT Vice-President of Engineering brought the Fox-1 1U CubeSat
> concept and project to the Board of Directors and "sold" the Fox-1
> Program that has now produced 5 (OK 4 1/2 until Fox-1E is complete)
> Fox-1 CubeSats. The concept included a Morse Code ID for the beacon of
> the FM repeaters, as stated in the System Requirements:
>
> 3.9.6 If the downlink transmitter has been un-keyed for a period of 5
> minutes, the satellite shall send " HI THIS IS AMSAT FOX " in Morse code
> via a keyed audio tone on the downlink transmitter.
>
> When designing the software for the ID back in 2014 after I was
> appointed VPE, the Fox-1 Team thought it would be a nice idea to use a
> voice ID instead of Morse Code given the abilities of the IHU and
> available memory. In kicking around ideas about who would record the ID
> it came to us that it would be a nice tribute to Tony if Veronica were
> the voice ID. Fox-1 software engineer Burns Fisher, who lives near
> Tony's family, contacted them. Veronica graciously agreed, and Burns
> set out with his recorder to capture Veronica to become the voice of the
> Fox-1 FM satellites.
>
> From their many clips I was able to assemble the various Safe Mode and
> Transponder Mode IDs for each satellite/name, so I guess I'm to blame
> for the processing I did that makes her sound like a child...
>
> I listened to Veronica's IDs I'll bet hundreds if not a thousand times
> in testing the Fox-1 engineering model and Fox-1A through D, and I still
> get a kick and a smile from it every time I hear her - especially from
> orbit!
>
> Jerry Buxton, N?JY
>
>> On 11/19/2017 12:57, Paul Andrews wrote:
>> Satellite Fans,
>>
>> I pointed my 2 x XP28 moonbounce antenna at AO-91 today. The AO-91
>> pass was nearly directly overhead in FN20. The FM signal quality was
>> so high - you can hear the room acoustics in the recording of the
>> child's voice. Very cool.
>>
>> Here is a YouTube link - https://youtu.be/gepcNt2sW2g
>>
>> 73 - Paul - W2HRO
>> _______________________________________________
>> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
>> to all interested persons worldwide without requiring membership.
Opinions expressed
>> are solely those of the author, and do not reflect the official views of
AMSAT-NA.
>> Not an AMSAT-NA member? Join now to support the amateur satellite program!
>> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
>>
>>
>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
expressed
> are solely those of the author, and do not reflect the official views of
AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 11
Date: Mon, 20 Nov 2017 10:12:03 -0700
From: "Carlos Cardon" <cdcardon@xxxxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Thanks to KE4AL
Message-ID: <016e01d36222$b0530fc0$10f92f40$@xxxxxxx.xxx>
Content-Type: text/plain; charset="us-ascii"
Thanks to Robert, KE4AL, for the roving expedition to MS!
My only remaining state for satellite WAS is now Delaware. Anyone have a
recommendation for DE operators?
73,
Carlos
W7QL
------------------------------
Message: 12
Date: Sun, 19 Nov 2017 18:49:41 -0800
From: Jeremy Turner <jeremy@xxxxxxxxxxxxx.xxx>
To: vk4tec@xxxxxxxxxxxxx.xxxx amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] New Satellite ADIF Logging Tool
Message-ID:
<CAO4qtUfPnFCfJFiTw5damM=orS6CwsFHYRvPYL7sUKuqo90XOA@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"
The idea for this was simply to make log entry less painful for me. I don't
have the desire right now to write my own logging app. But good luck with
your programming.
--
Jeremy Turner
On November 19, 2017 at 19:20:30, vk4tec@xxxxxxxxxxxxx.xxx (
vk4tec@xxxxxxxxxxxxx.xxxx wrote:
Hi Jeremy
Nice work
I was thinking about a LINUX based MySQL database that does a SYNC to a
master dartabase when connected to the net
You see the data in front of you but then bang it populates with the master
server when you connect.
I would make an IOS app but I am too busy making satgates and the cube sats
are popping out faster than I can keep track of ?
Web browser interface locally using perl ( cgi ) web page to enter details
( can pre-populate )
Do you have experience with MySQL databases, web portals and Internet
scripts using python ?
Here is an example
http://59.167.159.165/satlogger/index2.html
Andrew VK4TEC
-----Original Message-----
From: AMSAT-BB [mailto:amsat-bb-bounces@xxxxx.xxxx On Behalf Of Jeremy
Turner
Sent: Monday, 20 November 2017 10:22 AM
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] New Satellite ADIF Logging Tool
Hello all,
One of the challenges that I've had since starting to work satellites is my
logging workflow. I don't always get back to my logging app to log QSOs
immediately, I have found it challenging to get all the right settings to
get LOTW to match, and some logging apps don't even allow me to type all
the right settings in. I hated having to fill in 10 fields per QSO, that
always seemed to reset to the wrong values with every QSO!
I wrote myself a little Python console app to improve my workflow, and I
want to share Python Satellite ADIF or pysatadif with you.
For instance, if there is an SO-50 pass where I make several QSOs, I would
type:
pysatadif --satname SO-50 --timeon 1450 --qsodate 20171119 --qso KO6RM,DN70
--qso N0CALL,EL99
I can add as many QSOs per pass as I need. I can leave off the date if the
QSO was on the current UTC day.
The software pulls my station defaults including rig, power, and my grid
square from a defaults file (automatically generated for you on first run),
and pulls frequency, band, and mode from a directory of satellite info.
These can be overridden for you rovers and special event ops out there.
The resulting ADIF output can be imported into your favorite logging app,
TQSL or whatever else you'd like.
If this sounds interesting, you can install pysatadif on Windows, Mac or
Linux using Python 2.7 or 3.6 by running 'pip install pysatadif'.
For more information, check out:
https://github.com/jeremymturner/pysatadif
https://pypi.python.org/pypi/pysatadif
If you have questions, feel free to contact me off-list.
73,
Jeremy / KO6RM
jeremy@xxxxxxxxxxxxx.xxx
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available to
all interested persons worldwide without requiring membership. Opinions
expressed are solely those of the author, and do not reflect the official
views of AMSAT-NA.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Subject: Digest Footer
_______________________________________________
Sent via amsat-bb@xxxxx.xxx.
AMSAT-NA makes this open forum available to all interested persons worldwide
without requiring membership. Opinions expressed
are solely those of the author, and do not reflect the official views of
AMSAT-NA.
Not an AMSAT member? Join now to support the amateur satellite program!
http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
End of AMSAT-BB Digest, Vol 12, Issue 303
*****************************************
Read previous mail | Read next mail
| |
