• AMSAT-BB-digest V14 273

    From CX2SA@21:5/101 to SATDIG on Wed Jul 31 04:22:14 2019
    R:190731/0307Z 12683@LU9FQR.2124.SFE.AR.SOAM BPQ6.0.17
    R:190715/2231Z 25403@LU3DVN.USH.TDF.ARG.SOAM LinBPQ6.0.17
    R:190715/2223Z 33112@N3HYM.MD.USA.NOAM BPQ6.0.18
    R:190715/2228Z 20599@OK2PEN.SP.BRA.SOAM [Sao Jose dos Campos] $:AMSATBB14273 R:190715/2228z @:OK0NBR.SP.BRA.SOAM $:AMSATBB14273
    R:190715/2228z @:IR2UBX.ILOM.ITA.EU $:AMSATBB14273
    R:190715/2228z @:IW2OHX.ILOM.ITA.EU $:AMSATBB14273
    R:190715/2228z @:IR1UAW.ILIG.ITA.EU $:AMSATBB14273
    R:190716/0026Z @:IK1NHL.ILIG.ITA.EU #:51012 [Ventimiglia JN33UU NHLNETWORK] R:190715/2225Z @:CX2SA.SAL.URY.SOAM #:10191 [Salto] FBB7.00e $:AMSATBB14273

    From: CX2SA@CX2SA.SAL.URY.SOAM
    To : SATDIG@WW

    Today's Topics:

    1. FO-29 quiet (Eli Caul)
    2. Re: SatPc32 AO-92 L Band Doppler.SQF with Icom-9700
    (Erich Eichmann)
    3. Re: APRS Satellite PATHs (KE6BLR Robert)
    4. Travelling Rig (Brad Smith)
    5. Re: Travelling Rig (John Brier)
    6. Re: Travelling Rig (Robert MacHale)
    7. Re: Travelling Rig (Robert Bankston)
    8. Re: APRS Satellite PATHs (Robert Bruninga)
    9. Re: FO-29 quiet (Mineo Wakita)
    10. Re: FO-29 quiet (Zach Metzinger)
    11. Re: APRS Satellite PATHs (Robert MacHale)


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

    Message: 1
    Date: Mon, 15 Jul 2019 17:12:07 +0000
    From: Eli Caul <eli.caul@?????.???>
    To: "amsat-bb@?????.???? <amsat-bb@?????.???>
    Subject: [amsat-bb] FO-29 quiet
    Message-ID: <MW2PR20MB2060F64A0E2DC99061B7818198CF0@?????????????.????????.????.???????.??


    Content-Type: text/plain; charset="us-ascii"

    Hi Folks -

    Has there been any news on what might have happened to FO-29?

    It's a wonderful resource, and I'm hoping it can be brought back into service.

    Fingers crossed,

    - Eli Caul KK6ZHZ

    Director of Customer Care
    Sonic



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

    Message: 2
    Date: Mon, 15 Jul 2019 20:29:45 +0200
    From: Erich Eichmann <erich.eichmann@????????.??>
    To: Cal Spreitzer <n3cal@??.?????????.???>, AMSAT-BB@?????.???
    Subject: Re: [amsat-bb] SatPc32 AO-92 L Band Doppler.SQF with
    Icom-9700
    Message-ID: <9c783611-ee22-578c-33f3-5ce108db3ad0@????????.??>
    Content-Type: text/plain; charset=utf-8; format=flowed

    Carl,
    The parameter REV / NOR in Doppler.SQF has only meaning for linear Sats:
    If the user tunes? the downlink frequency, the program changes the
    uplink frequency either in the opposite direction (REV)? pr in the same
    (NOR). The REV setting is correct for almost all linear satellites, only
    a few require NOR, e.g. AO-07, Mode A.

    With FM satellites which operate in fixed channels, the setting is
    irrelevant. Also, the REV/NOR paramater does not affect the Doppler
    shift correction. Uplink and Downlink must alway be corrected in the
    opposite direction The program also does not change the REV / NOR
    setting of the radio. But it overwrites the frequencies set with the
    VFO. If you change e.g. at AO-73 both frequencies with the VFO up by 10
    KHz, the uplink gets wrong by 20 KHz. Therefore, the program changes the
    uplink down by 20 KHz.


    Try Jeffs, KB2M, entry in Doppler.SQF. If you don't hear signals from
    other stations change the downlink using the 'Downlink' correction
    controls in menu 'CAT'- First click the control 'V' (which is 'V-' by
    default with FM sats) to V+. Then the controls will work also with FM
    sats.? If you hear other stations but not you own signal, correct the
    uplink using the 'Upl. Corr.' controls in menu 'CAT' (control V must be V+)

    If you know? the correct entries in Doppler.SQf? change the data line
    manually and save the file.


    73s, Erich, DK1TB

    Am 15.07.2019 um 14:44 schrieb Cal Spreitzer via AMSAT-BB:
    What should the Doppler.sqf values be for AO-92 L-Band be? I'm having
    issue with AO-92 L-Band uplink tracking on my IC-9700. I'm guessing it has something to do with the frequency trend (Nor/Rev) setting. I've tried it set to both Nor and Rev but for some odd reason the Nor/Rev setting does not make any difference and my uplink frequency keeps dropping during the pass when it should increase? I also noticed the IC-9700 display the NOR/REV never changes according to the what the .sqf is set. I'm not sure if this
    is a CAT issue with the rig or me? I'm using the current IC-9700 firmware 1.11. Here is what my current .sqf is set:



    AO-92,145880,1267350,FM,FM,NOR,0,0,Voice L/V



    I got it to work once but manually selecting the REV on the 9700 display.
    But then the very next pass it didn't work?? Any advice would be appreciated. Thanks.



    Cal/N3CAL

    _______________________________________________
    Sent via AMSAT-BB@?????.???. 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: https://www.amsat.org/mailman/listinfo/amsat-bb


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

    Message: 3
    Date: Mon, 15 Jul 2019 13:30:41 -0700
    From: KE6BLR Robert <ke6blr.robert@?????.???>
    To: Ryan Noguchi <ai6do@?????.???>
    Cc: AMSAT BB <amsat-bb@?????.???>
    Subject: Re: [amsat-bb] APRS Satellite PATHs
    Message-ID:

    <CABaTVVYyM=706DxPPvB=Kt1HYq01U9HG2Kqo9wbyQqgB=BWm_w@????.?????.???> Content-Type: text/plain; charset="UTF-8"

    Just a thought -- one of the benefits of using the actual call sign
    (RS0ISS, PSAT, PSAT2) rather than ARISS or APRSAT is for the record.

    For example, I am calculating the Az/El of each contact based on the
    digipeated (PSAT*) path. When the digipeated path is ARISS or APRSAT there
    is no good way to clarify which satellite participated in the packet.

    http://www.spacecommunicator.club/igates/

    See the Az/El columns for PSAT; I plan to add Az/El for others sometime
    soon.

    As a consumer of the data, I prefer seeing the individual call sign. As the user of the radio, I can see how using APRSAT for everything is more convenient.

    73

    On Wed, Jul 10, 2019 at 11:38 AM Ryan Noguchi via AMSAT-BB < amsat-bb@?????.???> wrote:

    Yes, that's correct. FalconSat-3 doesn't digipeat using the generic ARISS
    or APRSAT paths.

    Agreed, it's a pain to have to keep changing PATH, baud rate, and data
    band between FalconSat-3 and the other packet satellites. At least there
    are only two configurations to have to toggle between. Once you've done it
    a couple dozen times, it becomes second nature.

    Yes, PSAT2 (and apparently also AISAT) may need to use Narrow FM mode, but the mode can be easily programmed into memory channels. I just set up a different set of memory channels for PSAT2 and AISAT to set that mode and enable (crude) Doppler correction. I haven't used them yet so don't know if
    5 kHz steps will cut it.

    73, Ryan AI6DO

    On Wednesday, July 10, 2019, 10:14:18 AM PDT, Fred Hillhouse via
    AMSAT-BB <amsat-bb@?????.???> wrote:

    Regardless of the other operational requirements of FalconSAT-3, you are saying FalconSAT-3 will not digipeat using the generic paths. That means
    the text in the links provided is incorrect. Or is there some other
    qualifier I have missed?

    PSAT2 is also a different beast apparently. The text in the link imply
    APRS uplinks are narrowband. From the PSAT2 link:

    Uplinks: 145.825 MHz narroband [sic] FM packet and 29.4815 MHz SSB PSK31
    User Station Software Configuration:
    First bullet - Radios must be in Narrowband and track to 1 KHz Doppler on
    the uplink.

    The reason for asking is to be able to make as few changes to an HT (D72)
    as possible. And the main use is to achieve a digipeat. When a satellite is the only APRS network available it could be a useful way to get information out.

    Best regards,
    Fred N7FMH


    -----Original Message-----
    From: AMSAT-BB [mailto:amsat-bb-bounces@?????.???? On Behalf Of Ryan
    Noguchi via AMSAT-BB
    Sent: Wednesday, July 10, 2019 12:11 PM
    To: amsat-bb@?????.???
    Subject: Re: [amsat-bb] APRS Satellite PATHs

    FalconSat-3 is a different beast: 9600 bps vs. 1200 bps, and crossband at different frequencies than the 1200 bps packet satellites. If you want to
    be digipeated by FalconSat-3, you need to use the PFS3-1 PATH.

    73, Ryan AI6DO


    _______________________________________________
    Sent via AMSAT-BB@?????.???. 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: https://www.amsat.org/mailman/listinfo/amsat-bb



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

    Message: 4
    Date: Mon, 15 Jul 2019 20:40:36 +0000 (UTC)
    From: Brad Smith <corlissbs@???.???>
    To: amsat-bb@?????.???
    Subject: [amsat-bb] Travelling Rig
    Message-ID: <1033632090.953680.1563223236257@????.?????.???>
    Content-Type: text/plain; charset=UTF-8

    I have put together a rig for when I travel and have no room for an Arrow 2 antenna, which consists of a Kenwood TM-D710GA radio and a dual band, Comet, 5/8 wave whip antenna. This allows for a quick setup to work a bird from new grid squares, without disrupting the family. On our recent trip, this worked great for AO-91 and AO-92. However, I can't a signal from SO-50 with this
    rig, even with a preamp. Does anybody else use this radio on SO-50 and would you have any suggestions? I know it is not an ideal situation, but it may be the "only game in town" for some trips.? Brad Smith, KC9UQR


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

    Message: 5
    Date: Mon, 15 Jul 2019 16:51:22 -0400
    From: John Brier <johnbrier@?????.???>
    To: Brad Smith <corlissbs@???.???>
    Cc: AMSAT BB <amsat-bb@?????.???>
    Subject: Re: [amsat-bb] Travelling Rig
    Message-ID: <CALn0fKORe+oA7oA=xmC50+abfNcRnjM+oMbq_0cjFMjS5ucHrQ@????.?????.???> Content-Type: text/plain; charset="UTF-8"

    SO-50 has a lower power output than AO-91 and AO-92, and it has a 70cm downlink, so the path loss is higher. You're gonna need a beam or
    really high elevation passes to work SO-50. If you could get just a
    70cm beam and use the whip to transmit on 2m, you might be able to
    make it work. the 70cm elements might be small enough for travel too.

    Personally I have traveled with my backpacker Arrow II on planes
    without problems. Do you have the backpacker with split boom?

    73, John Brier KG4AKV

    On Mon, Jul 15, 2019 at 4:41 PM Brad Smith via AMSAT-BB
    <amsat-bb@?????.???> wrote:

    I have put together a rig for when I travel and have no room for an Arrow
    2 antenna, which consists of a Kenwood TM-D710GA radio and a dual band,
    Comet, 5/8 wave whip antenna. This allows for a quick setup to work a bird
    from new grid squares, without disrupting the family. On our recent trip,
    this worked great for AO-91 and AO-92. However, I can't a signal from SO-50 with this rig, even with a preamp. Does anybody else use this radio on SO-50 and would you have any suggestions? I know it is not an ideal situation, but
    it may be the "only game in town" for some trips. Brad Smith, KC9UQR
    _______________________________________________
    Sent via AMSAT-BB@?????.???. 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: https://www.amsat.org/mailman/listinfo/amsat-bb


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

    Message: 6
    Date: Mon, 15 Jul 2019 21:05:37 +0000 (UTC)
    From: Robert MacHale <robert.machale@?????.???>
    To: amsat-bb@?????.???? Brad Smith <corlissbs@???.???>
    Subject: Re: [amsat-bb] Travelling Rig
    Message-ID: <1222184995.2330389.1563224737647@????.?????.???>
    Content-Type: text/plain; charset=UTF-8

    I place my Arrow II into a 3" diameter PVC pipe with end caps. I think it's
    2 feet long. It stores well in the car trunk and the PVC is strong to
    protect from bends or punctures.
    73
    Robert MacHale. KE6BLR Ham Radio License.?http://spaceCommunicator.club/igates . Supporting Boy Scout Merit Badges in Radio, Robotics, and Space Exploration


    On Monday, July 15, 2019, 1:41:55 PM PDT, Brad Smith via AMSAT-BB <amsat-bb@?????.???> wrote:

    I have put together a rig for when I travel and have no room for an Arrow 2 antenna, which consists of a Kenwood TM-D710GA radio and a dual band, Comet, 5/8 wave whip antenna. This allows for a quick setup to work a bird from new grid squares, without disrupting the family. On our recent trip, this worked great for AO-91 and AO-92. However, I can't a signal from SO-50 with this
    rig, even with a preamp. Does anybody else use this radio on SO-50 and would you have any suggestions? I know it is not an ideal situation, but it may be the "only game in town" for some trips.? Brad Smith, KC9UQR _______________________________________________
    Sent via AMSAT-BB@?????.???. 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: https://www.amsat.org/mailman/listinfo/amsat-bb


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

    Message: 7
    Date: Mon, 15 Jul 2019 21:21:58 +0000 (UTC)
    From: Robert Bankston <ke4al@?????.???>
    To: Brad Smith <corlissbs@???.???>
    Cc: AMSAT BB <amsat-bb@?????.???>
    Subject: Re: [amsat-bb] Travelling Rig
    Message-ID: <706662902.2328109.1563225718177@????.?????.???>
    Content-Type: text/plain; charset=UTF-8

    Wyatt, AC0RA, has been know to operate with just a mobile on U/v

    satellites.? On V/u satellites (FO-29 and SO-50), he uses a shorty arrow (4
    UHF elements only) and a UHF preamplifier for downlink.?
    I have tried operating with a mobile whip, and, yes, I could get into the
    bird, but not consistently.? Having some form of directional antenna is
    always better.
    I have used both my shorty Arrow (2-elements on VHF and 4-elements on UHF)
    as well as my baby Arrow?(1-element on VHF and 3-elements on UHF) with my?Kenwood TM-D710GA.? Aiming/polarization matching is more critical than
    with a standard Arrow, but it still works a whole lot better than with just
    a mobile whip.? Note:? I bump my power up to mid-level.
    73,
    Robert Bankston, KE4ALAMSAT-NA VP of User Services
    Twitter:? @??????????????????? KE4AL.wordpress.com

    On Monday, July 15, 2019, 03:52:16 PM CDT, John Brier via AMSAT-BB <amsat-bb@?????.???> wrote:

    SO-50 has a lower power output than AO-91 and AO-92, and it has a 70cm downlink, so the path loss is higher. You're gonna need a beam or
    really high elevation passes to work SO-50. If you could get just a
    70cm beam and use the whip to transmit on 2m, you might be able to
    make it work. the 70cm elements might be small enough for travel too.

    Personally I have traveled with my backpacker Arrow II on planes
    without problems. Do you have the backpacker with split boom?

    73, John Brier KG4AKV

    On Mon, Jul 15, 2019 at 4:41 PM Brad Smith via AMSAT-BB
    <amsat-bb@?????.???> wrote:

    I have put together a rig for when I travel and have no room for an Arrow
    2 antenna, which consists of a Kenwood TM-D710GA radio and a dual band,
    Comet, 5/8 wave whip antenna. This allows for a quick setup to work a bird
    from new grid squares, without disrupting the family. On our recent trip,
    this worked great for AO-91 and AO-92. However, I can't a signal from SO-50 with this rig, even with a preamp. Does anybody else use this radio on SO-50 and would you have any suggestions? I know it is not an ideal situation, but
    it may be the "only game in town" for some trips.? Brad Smith, KC9UQR
    _______________________________________________
    Sent via AMSAT-BB@?????.???. 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: https://www.amsat.org/mailman/listinfo/amsat-bb
    _______________________________________________
    Sent via AMSAT-BB@?????.???. 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: https://www.amsat.org/mailman/listinfo/amsat-bb


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

    Message: 8
    Date: Sun, 14 Jul 2019 17:25:39 -0400
    From: Robert Bruninga <bruninga@????.???>
    To: KE6BLR Robert <ke6blr.robert@?????.???>, amsat bb
    <amsat-bb@?????.???>
    Subject: Re: [amsat-bb] APRS Satellite PATHs
    Message-ID: <CALdCfNK0nTV20ZVHmYJKY0yDE3vRd82O20MvipnVHEFc6MRZyg@????.?????.???> Content-Type: text/plain; charset="UTF-8"

    Actually, when you use ARISS or APRSAT then the signal comes down as
    RS0ISS* if it went via ISS, and comes down as PSAT,ARISS* or PSAT2,ARISS*
    if it went via one of those. Yes, it is a parsing pain, but a simple
    rule. If you see ARISS*, then simply find the actual satellite in the
    previous field.

    On Mon, Jul 15, 2019 at 4:31 PM KE6BLR Robert via AMSAT-BB < amsat-bb@?????.???> wrote:

    Just a thought -- one of the benefits of using the actual call sign
    (RS0ISS, PSAT, PSAT2) rather than ARISS or APRSAT is for the record.

    For example, I am calculating the Az/El of each contact based on the digipeated (PSAT*) path. When the digipeated path is ARISS or APRSAT there
    is no good way to clarify which satellite participated in the packet.

    http://www.spacecommunicator.club/igates/

    See the Az/El columns for PSAT; I plan to add Az/El for others sometime
    soon.


    As a consumer of the data, I prefer seeing the individual call sign. As the user of the radio, I can see how using APRSAT for everything is more convenient.

    73

    On Wed, Jul 10, 2019 at 11:38 AM Ryan Noguchi via AMSAT-BB < amsat-bb@?????.???> wrote:

    Yes, that's correct. FalconSat-3 doesn't digipeat using the generic
    ARISS
    or APRSAT paths.

    Agreed, it's a pain to have to keep changing PATH, baud rate, and data
    band between FalconSat-3 and the other packet satellites. At least there are only two configurations to have to toggle between. Once you've done
    it
    a couple dozen times, it becomes second nature.

    Yes, PSAT2 (and apparently also AISAT) may need to use Narrow FM mode,
    but
    the mode can be easily programmed into memory channels. I just set up a different set of memory channels for PSAT2 and AISAT to set that mode and enable (crude) Doppler correction. I haven't used them yet so don't know
    if
    5 kHz steps will cut it.

    73, Ryan AI6DO

    On Wednesday, July 10, 2019, 10:14:18 AM PDT, Fred Hillhouse via AMSAT-BB <amsat-bb@?????.???> wrote:

    Regardless of the other operational requirements of FalconSAT-3, you are saying FalconSAT-3 will not digipeat using the generic paths. That means the text in the links provided is incorrect. Or is there some other qualifier I have missed?

    PSAT2 is also a different beast apparently. The text in the link imply
    APRS uplinks are narrowband. From the PSAT2 link:

    Uplinks: 145.825 MHz narroband [sic] FM packet and 29.4815 MHz SSB PSK31 User Station Software Configuration:
    First bullet - Radios must be in Narrowband and track to 1 KHz Doppler on the uplink.

    The reason for asking is to be able to make as few changes to an HT (D72)

    as possible. And the main use is to achieve a digipeat. When a satellite
    is
    the only APRS network available it could be a useful way to get
    information
    out.

    Best regards,
    Fred N7FMH


    -----Original Message-----
    From: AMSAT-BB [mailto:amsat-bb-bounces@?????.???? On Behalf Of Ryan Noguchi via AMSAT-BB
    Sent: Wednesday, July 10, 2019 12:11 PM
    To: amsat-bb@?????.???
    Subject: Re: [amsat-bb] APRS Satellite PATHs

    FalconSat-3 is a different beast: 9600 bps vs. 1200 bps, and crossband
    at
    different frequencies than the 1200 bps packet satellites. If you want to be digipeated by FalconSat-3, you need to use the PFS3-1 PATH.

    73, Ryan AI6DO


    _______________________________________________
    Sent via AMSAT-BB@?????.???. 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: https://www.amsat.org/mailman/listinfo/amsat-bb

    _______________________________________________
    Sent via AMSAT-BB@?????.???. 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: https://www.amsat.org/mailman/listinfo/amsat-bb



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

    Message: 9
    Date: Tue, 16 Jul 2019 06:48:04 +0900
    From: "Mineo Wakita" <ei7m-wkt@?????????.??.??>
    To: <amsat-bb@?????.???>
    Subject: Re: [amsat-bb] FO-29 quiet
    Message-ID: <503892ED0BB84C7A9B73674F3C42FAB7@??????>
    Content-Type: text/plain; charset="UTF-8"

    FO-29 State:
    http://www.ne.jp/asahi/hamradio/je9pel/fo29siln.htm

    JE9PEL, Mineo Wakita



    ---
    ??E???????? ?????????????????????????
    https://www.avast.com/antivirus


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

    Message: 10
    Date: Mon, 15 Jul 2019 17:14:24 -0500
    From: Zach Metzinger <zmetzing@?????.???>
    To: amsat-bb@?????.???
    Subject: Re: [amsat-bb] FO-29 quiet
    Message-ID: <1e13a3d4-aec7-fb19-b26e-3704fe420ad6@?????.???>
    Content-Type: text/plain; charset=utf-8; format=flowed

    On 2019-07-15 16:48, Mineo Wakita via AMSAT-BB wrote:
    FO-29 State:
    http://www.ne.jp/asahi/hamradio/je9pel/fo29siln.htm


    Satnogs station 335 (ON4LS) heard it, or something that had a Doppler
    shift like a satellite, today:

    https://network.satnogs.org/observations/829247/

    --- Zach
    N0ZGO


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

    Message: 11
    Date: Mon, 15 Jul 2019 22:20:07 +0000 (UTC)
    From: Robert MacHale <robert.machale@?????.???>
    To: KE6BLR Robert <ke6blr.robert@?????.???>, amsat bb
    <amsat-bb@?????.???>, Robert Bruninga <bruninga@????.???>
    Subject: Re: [amsat-bb] APRS Satellite PATHs
    Message-ID: <1722217298