| |
CX2SA > SATDIG 23.06.17 03:31l 867 Lines 28828 Bytes #999 (0) @ WW
BID : AMSATBB12156
Read: GUEST
Subj: AMSAT-BB-digest V12 156
Path: IW8PGT<CX2SA
Sent: 170623/0119Z @:CX2SA.SAL.URY.SOAM #:11409 [Salto] FBB7.00e $:AMSATBB12156
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. IC-910H tuning (KC2TN)
2. Decoding CAS4A and CAS4B telemetry? (Douglas Quagliana)
3. Satellite frequency coordination (rsoifer1@xxx.xxxx
4. Re: Satellite frequency coordination (Paul Stoetzer)
5. QBITO is coordinated! Sorry for error. (rsoifer1@xxx.xxxx
6. Re: SatPC32 Doppler Correction/Calibration? (David Rush)
7. FD sat contacts (Jeff Griffin)
8. Re: FD sat contacts (Paul Stoetzer)
9. Re: FD sat contacts (Jeff Griffin)
10. Re: FD sat contacts (Bruce)
11. Re: V31CI (David Swanson)
12. Re: FD sat contacts (Scott)
13. CORRECTION- NIUSAT Tele-metry Reception Support for the
Initial Orbits (Mani [VU2WMY/KJ6LRS])
----------------------------------------------------------------------
Message: 1
Date: Thu, 22 Jun 2017 13:36:41 -0400
From: KC2TN <kc2tn@xxxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] IC-910H tuning
Message-ID: <C412764B-11CF-42C6-85B3-D84CE7A7BBD4@xxxxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
After years of non-use, I've got my IC-910H CIV fixed and antennas back in
service.
I've noticed when trying to calibrate my uplink frequency by hitting the
"Swap 0" button, it sometimes does not stay ON, but rather reverts back to
the frequency display rather than the -------'s it normally displays while
I'm tuning. Sometimes this happens as soon as I start tuning or after a few
seconds.
Shouldn't the display stay blanked until I hit the Swap 0 button again?
Well, as I'm typing this question I had a thought. Maybe I should turn off
the CAT tuning while zero beating. Maybe CAT is what's turning the display
back on.
I'll have to wait for Field Day to try it out as I've got the truck packed
with all my equipment now.
Joe - KC2TN
------------------------------
Message: 2
Date: Thu, 22 Jun 2017 14:54:09 -0500
From: Douglas Quagliana <dquagliana@xxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Decoding CAS4A and CAS4B telemetry?
Message-ID:
<CALaYSmmJRwtuH5rhaMvxhxcwe+rETa8iAjihjJn8nkQLcaACAQ@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"
Hi,
Does anyone have the equations for decoding the telemetry values
from CAS4A and CAS4B? I'm curious and wondering about the
CW and 4800 baud telemetry, but I couldn't find any details on what the
telemetry
means.
73,
Douglas KA2UPW/5
------------------------------
Message: 3
Date: Thu, 22 Jun 2017 16:30:51 -0400
From: rsoifer1@xxx.xxx
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Satellite frequency coordination
Message-ID: <15cd1801729-2729-bc0e@xxxxxxxxxxx.xxxx.xxx.xxx>
Content-Type: text/plain; charset=utf-8
>From what I can see, QBITO does not appear to have been coordinated by IARU
either. Some countries, such as the USA, require IARU coordination in order
to use frequencies allocated to the amateur-satellite service. Even if
licensed by a country which does not require it, IARU coordination is very
helpful in giving your satellite project the greatest chance of success.
For best results, it should be done as early in the design and construction
process as possible. For further information, please see
www.iaru.org/satellite.
73 Ray W2RS
------------------------------
Message: 4
Date: Thu, 22 Jun 2017 16:36:31 -0400
From: Paul Stoetzer <n8hm@xxxx.xxx>
To: rsoifer1@xxx.xxx
Cc: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Satellite frequency coordination
Message-ID:
<CABzOSOpM1XFhiQ49fSC0kHYdD3ywusCGv4kiaeA8DdsYNZgq9g@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"
Ray,
QBITO was coordinated on 9/22/2014:
http://www.amsatuk.me.uk/iaru/finished_detail.php?serialnum=344
73,
Paul, N8HM
On Thu, Jun 22, 2017 at 4:30 PM, rsoifer1--- via AMSAT-BB
<amsat-bb@xxxxx.xxx> wrote:
> From what I can see, QBITO does not appear to have been coordinated by
IARU either. Some countries, such as the USA, require IARU coordination in
order to use frequencies allocated to the amateur-satellite service. Even
if licensed by a country which does not require it, IARU coordination is
very helpful in giving your satellite project the greatest chance of
success. For best results, it should be done as early in the design and
construction process as possible. For further information, please see
www.iaru.org/satellite.
>
>
> 73 Ray W2RS
> _______________________________________________
> 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: Thu, 22 Jun 2017 16:59:18 -0400
From: rsoifer1@xxx.xxx
To: amsat-bb@xxxxx.xxxx n8hm@xxxx.xxx
Subject: [amsat-bb] QBITO is coordinated! Sorry for error.
Message-ID: <15cd19a1f4f-2729-bdfb@xxxxxxxxxxx.xxxx.xxx.xxx>
Content-Type: text/plain; charset=utf-8
You're right, Paul. I see it on the IARU/AMSAT-UK website now. My old eyes
couldn't find it the first time. Apologies to the QBITO project team and I
hope it can be found soon.
73 Ray W2RS
------------------------------
Message: 6
Date: Thu, 22 Jun 2017 18:34:11 -0400
From: David Rush <david@xxxxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] SatPC32 Doppler Correction/Calibration?
Message-ID: <49db98f7-f3f7-6ab9-4084-9c2c77d02adc@xxxxxxxx.xxx>
Content-Type: text/plain; charset=windows-1252; format=flowed
I just gave this a shot at an XW-2C pass this evening here in EM72.
I reset the uplink and downlink in Doppler.SQF to 145805.0 and 435160.0
(center of the passband).
Once the bird popped far enough off the horizon to hear its beacon, I
tuned back to a clear spot on the pass band.
I opened the CAT menu, and intermittently poked the uplink correction
buttons and transmitted, until I found myself. I saved the uplink
correction.
Closed the CAT menu but was never able to find myself again. I had a
few minutes before LOS, and tweaked the D/L correction a bit on either
side, but nothing before LOS.
Looking at Dopper.SQF, it now shows 145805.0 and 435159.53. So the save
worked, but still can't hear myself right where I should be, nor find
myself tweaking the D/L correction before LOS.
Bah.
David, ky7dr
On /20170622/ 08:02, David Rush wrote:
> George:
>
> Okay, I'll give that a shot this evening. Thanks.
>
> David, ky7dr
>
>
> On /20170622/ 00:10, George Henry wrote:
>> Go into your Doppler.sqf file and edit the up- and downlink
>> frequencies back to the original values. Then use the uplink
>> calibration buttons to find yourself on the downlink. Then click the
>> Change/Store data file button and store the uplink calibration. I've
>> never touched the downlink correction on a sat with a linear
>> transponder...
>>
>> George, KA3HSW
>>
>>
>> ----- Original Message ----- From: "David Rush" <david@xxxxxxxx.xxx>
>> To: <amsat-bb@xxxxx.xxx>
>> Sent: Wednesday, June 21, 2017 7:53 PM
>> Subject: Re: [amsat-bb] SatPC32 Doppler Correction/Calibration?
>>
>>
>>> Okay, I followed the instructions (as I described below). I found
>>> myself on a couple of the XW-2* birds, and kept adjusting my
>>> downlink correction until I was at about peak elevation in the pass
>>> (I even made one contact while one of the birds was still on its way
>>> up). Then zeroed out the downlink correction and entered the
>>> opposite in uplink correction, and saved it.
>>>
>>> Once I did that I did not hear myself on the downlink, and failed to
>>> find myself, even trying a few 10s of hz of d/l correction either
>>> side, before the birds got too low on the horizon.
>>>
>>> What am I doing wrong?
>>>
>>> David, ky7dr
>>>
>>>
>>> On /20170621/ 07:44, David Rush wrote:
>>>> George:
>>>>
>>>> Thanks for the reply. So by repeatedly trying the same thing, have
>>>> I shifted the uplink frequency by a bit more every time? Sounds
>>>> like I may need to set those back. Or else just find a new value
>>>> in the opposite direction (starting a few multiples of the 160),
>>>> set it once, and leave it.
>>>>
>>>> 73, David, KY7DR
>>>>
>>>>
>>>> On /20170621/ 00:55, George Henry wrote:
>>>>> You're doing it right... once you store the uplink calibration,
>>>>> the calibration values WILL return to zero, but if you look at the
>>>>> uplink frequency displayed in the right-hand panel of the CAT
>>>>> window, it will have a new value which is offset from the original
>>>>> frequency by whatever calibration value you stored.
>>>>>
>>>>> 73,
>>>>> George, KA3HSW
>>>>>
>>>>>
>>>>> ----- Original Message ----- From: "David Rush" <david@xxxxxxxx.xxx>
>>>>> To: "Amsat BB" <amsat-bb@xxxxx.xxx>
>>>>> Sent: Tuesday, June 20, 2017 7:59 PM
>>>>> Subject: [amsat-bb] SatPC32 Doppler Correction/Calibration?
>>>>>
>>>>>
>>>>>> I'm trying to get the doppler correction/calibration set up for
>>>>>> the various birds before Field Day, but I'm just not making any
>>>>>> tangible progress.
>>>>>>
>>>>>> I've got a pair of Yaesu FT-817ND rigs, and can successfully tune
>>>>>> both of them with SatPC32's CAT controls.
>>>>>>
>>>>>> Following the directions for a two-rig calibration process, I've
>>>>>> been catching the XW-2* birds and can occasionally get the
>>>>>> downlink correction set to where I can hear myself on the downlink.
>>>>>>
>>>>>> In a couple of cases I've made note of where that downlink
>>>>>> calibration was near mid-pass (the necessary correction changed
>>>>>> constantly across the pass).
>>>>>>
>>>>>> Then I go into the CAT menu, set the downlink correction to zero
>>>>>> and the uplink calibration to the opposite sign of the previously
>>>>>> found downlink correction at mid-pass.
>>>>>>
>>>>>> For example on a recent pass of XW-2C I found a downlink
>>>>>> correction of -160 Hz was working well near mid-pass (I could
>>>>>> hear myself) so I set the uplink calibration to 160 Hz.
>>>>>>
>>>>>> The "Upl. Calibr." window in the CAT pop-up says "160", and the
>>>>>> grey box above the uplink frequency in the main window also says
>>>>>> "160".
>>>>>>
>>>>>> I click on the "Change/Store Dataf File" button, then click on
>>>>>> the "Store" "Uplink Calibration" button on the next pop-up.
>>>>>>
>>>>>> It says "The changings have been stored!" but the uplink
>>>>>> calibration in both the first popup and the main window are back
>>>>>> to zero.
>>>>>>
>>>>>> I click the X to close both pop-ups, and uplink correction in the
>>>>>> main window is still 0. I exit the program, restart it, select
>>>>>> XW-2C, enable CAT (C+) and the uplink calibration is still on zero.
>>>>>>
>>>>>> What am I missing?
>>>>>>
>>>>>> David, ky7dr
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>
>>>>>
>>>>> ---
>>>>> This email has been checked for viruses by Avast antivirus software.
>>>>> https://www.avast.com/antivirus
>>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>
>
> _______________________________________________
> 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: Thu, 22 Jun 2017 19:46:39 -0400
From: "Jeff Griffin" <kb2m@xxxx.xxx>
To: "'AMSAT-BB'" <AMSAT-BB@xxxxx.xxx>
Subject: [amsat-bb] FD sat contacts
Message-ID: <014501d2ebb1$cb8a1a50$629e4ef0$@xxx>
Content-Type: text/plain; charset="us-ascii"
Does anyone have any comments on the current ARRL FD satellite contact
rules?
73 Jeff kb2m
------------------------------
Message: 8
Date: Fri, 23 Jun 2017 00:02:34 +0000
From: Paul Stoetzer <n8hm@xxxx.xxx>
To: AMSAT-BB <AMSAT-BB@xxxxx.xxx>, Jeff Griffin <kb2m@xxxx.xxx>
Subject: Re: [amsat-bb] FD sat contacts
Message-ID:
<CABzOSOrdNFXpbCkwEuDxawjz-e-SHnaOYksB0JEDVkDrmUGKyw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"
They are fine, though confusing about the meaning of contacting "different
satellites." Does that mean that "satellite" is a band and working a
station on more than one satellite would be a dupe? I'm not sure. AMSAT
rules allow you to work the same station on multiple satellites.
73,
Paul, N8HM
On Thu, Jun 22, 2017 at 19:47 Jeff Griffin <kb2m@xxxx.xxx> wrote:
> Does anyone have any comments on the current ARRL FD satellite contact
> rules?
>
>
>
> 73 Jeff kb2m
>
>
>
> _______________________________________________
> 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: 9
Date: Thu, 22 Jun 2017 20:20:19 -0400
From: "Jeff Griffin" <jeff_griffin@xxxxxxx.xxx>
To: "'Paul Stoetzer'" <n8hm@xxxx.xxx>, "'AMSAT-BB'"
<AMSAT-BB@xxxxx.xxx>
Subject: Re: [amsat-bb] FD sat contacts
Message-ID: <016001d2ebb6$80021100$80063300$@xxx>
Content-Type: text/plain; charset="utf-8"
HI Paul, yes I know the rules well after 20 years. What I?m talking about is
a total restructure of the sat contact thing. I would like a way to make sat
operations a contest, like the rest of the bands. I?m looking for ideas?
73 Jeff kb2m
From: Paul Stoetzer [mailto:n8hm@xxxx.xxxx
Sent: Thursday, June 22, 2017 8:03 PM
To: AMSAT-BB; Jeff Griffin
Subject: Re: [amsat-bb] FD sat contacts
They are fine, though confusing about the meaning of contacting "different
satellites." Does that mean that "satellite" is a band and working a station
on more than one satellite would be a dupe? I'm not sure. AMSAT rules allow
you to work the same station on multiple satellites.
73,
Paul, N8HM
On Thu, Jun 22, 2017 at 19:47 Jeff Griffin <kb2m@xxxx.xxx> wrote:
Does anyone have any comments on the current ARRL FD satellite contact
rules?
73 Jeff kb2m
_______________________________________________
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: Thu, 22 Jun 2017 19:24:53 -0500
From: Bruce <kk5do@xxxxx.xxx>
To: Paul Stoetzer <n8hm@xxxx.xxx>
Cc: AMSAT-BB <AMSAT-BB@xxxxx.xxx>
Subject: Re: [amsat-bb] FD sat contacts
Message-ID: <19FF9DCC-BDA7-44A9-92D4-3960B83F21AC@xxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
ARRL has tried to adopt our rules the best they can.
73...bruce
Sent from my iPhone
On Jun 22, 2017, at 7:02 PM, Paul Stoetzer <n8hm@xxxx.xxx> wrote:
They are fine, though confusing about the meaning of contacting "different
satellites." Does that mean that "satellite" is a band and working a
station on more than one satellite would be a dupe? I'm not sure. AMSAT
rules allow you to work the same station on multiple satellites.
73,
Paul, N8HM
> On Thu, Jun 22, 2017 at 19:47 Jeff Griffin <kb2m@xxxx.xxx> wrote:
>
> Does anyone have any comments on the current ARRL FD satellite contact
> rules?
>
>
>
> 73 Jeff kb2m
>
>
>
> _______________________________________________
> 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: Thu, 22 Jun 2017 19:31:44 -0500
From: David Swanson <dave@xxxxxxxxxxxxx.xxx>
To: John KI4RO <johnki4ro@xxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] V31CI
Message-ID:
<CANq+eyWQGFDgG3bnuLbGRTWwGH3iu8+sJjgcDiikhCodm80=Jw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset="UTF-8"
Hey John, I've got the issues mostly sorted out with my equipment.. we are
now fighting gale force winds though (waves were 15' today, all the boats
stayed in!) which is making operating difficult. I'll try to be on ao85 and
fo29 this evening.
Dave, KG5CCI / V31CI
On Jun 21, 2017 9:39 PM, "John KI4RO" <johnki4ro@xxxxx.xxx> wrote:
> Dave is having gamma match problems on 70cm...says travel is hell on the
> equipment at times. hi hi Hopes to be back on later today (22 June)
>
> 73
> John KI4RO
>
>
>
>
> <https://mailtrack.io/> Sent with Mailtrack
> <https://mailtrack.io/install?source=signature&lang=en&
> referral=johnki4ro@xxxxx.xxxxxxxxxxxxxxxxxx>
> _______________________________________________
> 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: 12
Date: Thu, 22 Jun 2017 18:05:34 -0700
From: Scott <ka7fvv@xxxxx.xxx>
To: Bruce <kk5do@xxxxx.xxx>
Cc: AMSAT-BB <AMSAT-BB@xxxxx.xxx>, Paul Stoetzer <n8hm@xxxx.xxx>
Subject: Re: [amsat-bb] FD sat contacts
Message-ID: <FF009F48-3079-4854-A3DA-2C47A038666D@xxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
I was a little confused when I read the rules in the latest Journal. I need
to reread them again but they are way to restrictive.
73, Scott, KA7FVV
President - KBARA www.kbara.org
Co-Owner 443.525 System Fusion Repeater
ka7fvv.net
> On Jun 22, 2017, at 17:24, Bruce <kk5do@xxxxx.xxx> wrote:
>
> ARRL has tried to adopt our rules the best they can.
>
> 73...bruce
>
> Sent from my iPhone
>
> On Jun 22, 2017, at 7:02 PM, Paul Stoetzer <n8hm@xxxx.xxx> wrote:
>
> They are fine, though confusing about the meaning of contacting "different
> satellites." Does that mean that "satellite" is a band and working a
> station on more than one satellite would be a dupe? I'm not sure. AMSAT
> rules allow you to work the same station on multiple satellites.
>
> 73,
>
> Paul, N8HM
>
>> On Thu, Jun 22, 2017 at 19:47 Jeff Griffin <kb2m@xxxx.xxx> wrote:
>>
>> Does anyone have any comments on the current ARRL FD satellite contact
>> rules?
>>
>>
>>
>> 73 Jeff kb2m
>>
>>
>>
>> _______________________________________________
>> 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
>
> _______________________________________________
> 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: 13
Date: Fri, 23 Jun 2017 06:42:24 +0530
From: "Mani [VU2WMY/KJ6LRS]" <wmy@xxxx.xxx.xx>
To: "BB, AMSAT" <amsat-bb@xxxxx.xxx>, AMSAT-INDIA
<amsatindia@xxxxxxxxxxx.xxx>, VUHAMS <vuhams@xxxxxxxxxxx.xxx>, "HAMS,
ISRO" <isrohams@xxxxxxxxxxx.xxx>
Cc: kmswam@xxxxx.xxxx ijrohith1992@xxxxx.xxx
Subject: [amsat-bb] CORRECTION- NIUSAT Tele-metry Reception Support
for the Initial Orbits
Message-ID: <20170623011238.3F7DB8C7F@xxxxxxxxxx.xxxxx.xxx>
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
Sorry Friends,
Typo Error....
The telemetry down link signals are FSK, not AFSK
with regards
Quoting "'Mani [VU2WMY/KJ6LRS]' wmy@xxxx.xxx.xx [vuhams]"
<vuhams@xxxxxxxxxxx.xxx>:
> ?
> ?
>
> Dear Friends,
>
> NIUSAT- a nano-satellite designed & developed by Noorul Islam
> University will be launched tomorrow from India by PSLV C38 along
> with Cartosat 2 series and 29 other foreign satellites. The lift off
> is scheduled at 03:59 UT / 09:29 IST.
>
> On behalf of the NIUSAT team, the amateur radio fraternity around
> the World is kindly requested to listen to the AFSK telemetry down
> link signals on 436.000 Mhz and to provide the Reception Support for
> the initial orbits.
>
> The pre-launch TLE's are as follows:
>
> NIUSAT
> 1 12345U ?9072A ? 17174.17768773 ?.00007885 ?00000-0 ?35993-3 0 ?1238
> 2 12345 ?97.4411 233.9415 0008945 248.8440 320.4492 15.20418213 ? ?18
>
> The signal reports can be sent directly to the below mail ID:
>
> ijrohith1992@xxxxx.xxx
>
> Thanks in advance.
> with regards
> ?
> Mani [VU2WMY/KJ6LRS]
> Secretary & Station Director
> Upagrah Amateur Radio Club VU2URC
> ISRO Satellite Centre
> HAL Airport Road, Bangalore-560 017.
> Phone:(Office)91-80-25082598/25082054/25082192
> Mobile:? 91-9880 341 456
> E-mail ID: wmy@xxxx.xxx.xx
> ? ? ? ? ? ?vu2wmy.mani@xxxxx.xxx
> ? ? ? ? ? ?isrohams@xxxxx.xxx
>
> ?
>
> -------------------------
>
> ???????? ?????? ?? ?-??? ?????, ???? ?? ??????? ?? ???,
> ???????? ??????????(???) ?? ??????? ????? ?? ??? ?? ?? ?????
> ???????? ?? ??????????? ????? ????? ???? ?????? ?? ? 2346;
> 381;??????? ?????????, ?????, ?????? ?? ??????? ????? ??? ??? ??
> ???????? ?????????? ???? ??? ??, ????? ????? ???? ?? ????? ?-???
> ?????? ?????? ???? ?? ??? ????? ?? ??? ???? ?& #2351;?? ?? ???? ??
> ????
>
> -------------------------
>
> Confidentiality Notice: This e-mail message, including any
> attachments, is for the sole use of the intended recipient(s) and
> may contain confidential and privileged information. Any
> unauthorized review, use, disclosure or distribution is prohibited.
> If you are not the intended recipient, please contact the sender by
> reply e-mail and destroy all copies of the original message.
>
> -------------------------
>
> __._,_.___
> ?
>
> -------------------------
> Posted by: "Mani [VU2WMY/KJ6LRS]" <wmy@xxxx.xxx.xx>
> -------------------------
>
> ?
>
>
> Reply via web post[1] ? Reply to sender [2]
> ? Reply to group [3] ? Start a New Topic[4]
> ? Messages in this topic[5] (1)
>
>
> -------------------------
>
> Have you tried the highest rated email app?[6]
> With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated
> email app on the market. What are you waiting for? Now you can
> access all your inboxes (Gmail, Outlook, AOL and more) in one place.
> Never delete an email again with 1000GB of free cloud storage.
>
> -------------------------
>
> One World, One Language, Amateur Radio...
>
> To Unsubscribe, send a mail to vuhams-unsubscribe@xxxxxxxxxxx.xxx
> Visit Your Group[7]
>
>
> [8] ? Privacy[9] ? Unsubscribe[10] ? Terms of Use[11]
>
> ?
>
> .
>
> __,_._,___
Links:
------
[1]
https://groups.yahoo.com/neo/groups/vuhams/conversations/messages/34274;_ylc=X
3oDMTJxMGppNjltBF9TAzk3MzU5NzE0BGdycElkAzEwOTE1NDEEZ3Jwc3BJZAMxNzA1MDYzMTA4BG1
zZ0lkAzM0Mjc0BHNlYwNmdHIEc2xrA3JwbHkEc3RpbWUDMTQ5ODEyNjY2NA--?act=reply&messag
eNum=34274
[2]
mailto:wmy@xxxx.xxx.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[3]
mailto:vuhams@xxxxxxxxxxx.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[4]
https://groups.yahoo.com/neo/groups/vuhams/conversations/newtopic;_ylc=X3oDMTJ
ldWZoM2Z0BF9TAzk3MzU5NzE0BGdycElkAzEwOTE1NDEEZ3Jwc3BJZAMxNzA1MDYzMTA4BHNlYwNmd
HIEc2xrA250cGMEc3RpbWUDMTQ5ODEyNjY2NA--
[5]
https://groups.yahoo.com/neo/groups/vuhams/conversations/topics/34274;_ylc=X3o
DMTM2YTQxbDFkBF9TAzk3MzU5NzE0BGdycElkAzEwOTE1NDEEZ3Jwc3BJZAMxNzA1MDYzMTA4BG1zZ
0lkAzM0Mjc0BHNlYwNmdHIEc2xrA3Z0cGMEc3RpbWUDMTQ5ODEyNjY2NAR0cGNJZAMzNDI3NA--
[6] https://yho.com/1wwmgg
[7]
https://groups.yahoo.com/neo/groups/vuhams/info;_ylc=X3oDMTJlcm43ZmJzBF9TAzk3M
zU5NzE0BGdycElkAzEwOTE1NDEEZ3Jwc3BJZAMxNzA1MDYzMTA4BHNlYwN2dGwEc2xrA3ZnaHAEc3R
pbWUDMTQ5ODEyNjY2NA--
[8]
https://groups.yahoo.com/neo;_ylc=X3oDMTJkaXE2MDdnBF9TAzk3NDc2NTkwBGdycElkAzEw
OTE1NDEEZ3Jwc3BJZAMxNzA1MDYzMTA4BHNlYwNmdHIEc2xrA2dmcARzdGltZQMxNDk4MTI2NjY0
[9] https://info.yahoo.com/privacy/us/yahoo/groups/details.html
[10] mailto:vuhams-unsubscribe@xxxxxxxxxxx.xxxxxxxxxxxxxxxxxxxxxxx
[11] https://info.yahoo.com/legal/us/yahoo/utos/terms/
Mani [VU2WMY/KJ6LRS]
Secretary & Station Director
Upagrah Amateur Radio Club VU2URC
ISRO Satellite Centre
HAL Airport Road, Bangalore-560 017.
Phone:(Office)91-80-25082598/25082054/25082192
Mobile:? 91-9880 341 456
E-mail ID: wmy@xxxx.xxx.xx
? ? ? ? ? ?vu2wmy.mani@xxxxx.xxx
? ? ? ? ? ?isrohams@xxxxx.xxx
------------------------------------------------------------------------------
Confidentiality Notice: This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.
------------------------------------------------------------------------------
------------------------------
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 156
*****************************************
Read previous mail | Read next mail
| |
