Thanks Devin for sharing your thoughts and I agree that 145.825 is the designated freq for APRS satellites but as per procedure we had some constraints on the API submission which is a prerequisite for submission to IARU for frequency co ordination. I have notified  IARU prior to the launch  that AISAT-1 will use 145.825 as this is a dedicated  APRS payload. We will ensure the process are followed in the future and to role model such submissions.  73 Nitin [VU3TYG]

On Thursday, 4 April, 2019, 12:48:52 am IST, Devin L. Ganger devin@thecabal.org wrote:

Regarding AlSat 1 and its APRS payload, I thought that 145.825 MHz was the accepted frequency for all APRS on satellites. So I'm curious how that qualifies as not coordinated if they're following established procedure?

Thanks in advance for any additional knowledge you can share,

-- Devin L. Ganger (WA7DLG) email: devin@thecabal.org web: Devin on Earth cell: +1 425.239.2575

-----Original Message----- From: AMSAT-BB amsat-bb-bounces@amsat.org On Behalf Of Nico Janssen Sent: Wednesday, April 3, 2019 5:43 AM To: amsat-bb@amsat.org; ray.hoad@mypbmail.com >> Ray Hoad ray.hoad@mypbmail.com Subject: [amsat-bb] Objects from PSLV C45 launch identified

All,

Doppler measurements show that AstroCast 0.2 is object 44083, 2019-018F. Downlink: 437.1729 MHz.

Doppler measurements show that AISTechSat 3 is object 44103, 2019-018AB. Downlink: 436.7302 MHz. Note that this frequency has NOT been coordinated with the IARU.

Doppler measurements show that the PS4 stage of PSLV C45, with the AIS, APRS and ARIS payloads attached, is object 44104, 2019-018AC. The APRS payload of AMSAT-India is called AISat 1 and has downlink frequency 145.825 MHz. Note that this frequency has NOT been coordinated with the IARU.

Doppler measurements show that the 6U Cubesat M6P is now about 50 s behind the PS4 stage. TLEs for M6P are not yet available. The downlink frequency of M6P is 437.265 MHz. Note that coordination of this frequency has been DECLINED by the IARU because there is no amateur radio involved in this mission.

73, Nico PA0DLO

---

Sent via AMSAT-BB@amsat.org. 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.org. 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

Congrats!!

I just got digipeated for the first time myself on the 1512utc pass here.

Using 50w to 2m X-Quad w/ AZ-EL tracking, I was only heard at closest approach (69° elevation). My iGate received the digipeats w/ no errors, but for some unknown reason the packets are not showing up on the greater APRS network (APRS.fi, for instance). I don't know the reason for that.

Here's a tweet w/ screen shots:

https://twitter.com/scott23192/status/1113827054892539905

-Scott, K4KDR

===============================

On Thu, Apr 4, 2019 at 10:44 AM christy hunter via AMSAT-BB < amsat-bb@amsat.org> wrote:

I was able to get 4 beacons digi thru AISAT-1 using ARISS path, and UISS. Obj /44104, 2019-018AC/

no other stations heard.

I wonder if the AMSAT status page will be listing this sat on the list?

73 Christy KB6LTY DM14