New DTMF mode on PSAT2

From ANS-122: PSAT2 (NO-104) VHF is alive and new DTMF mode:

Bob Bruninga writes: PSAT2 VHF awoke from an 8 month slumber on 26 Apr 2021. We have no idea why. Its telemetry looks fine. Volts between 6.2 and 7.0 volts (5 NiCds). Exterior temps between -18 and +22 C. See

PSAT2 will NOT be in APRS mode but a brand new experimental mode for DTMF uplink and VOICE downlink. So you preload your grid and callsign into a 16 digit DTMF memory in your radio and when the satellite hears this it will assign a QSO number and QSL the grid by voice and then also generate an APRS packet for collection by APRS operators. There is even a way to send back a DTMF QSL so you can make it a 2-way DTMF. contact. Successful DTMF grids and messages will appear on a special URL on the PSAT2 page (above). To QSL, you key in that stations 2 digit QSL number and then dump your pre-loaded QSL DTMF message.
Since this is the first time this transponder is on the air and because a
DTMF uplink takes maybe 4 seconds, we don’t want the uplink saturated by a bunch of newbees initially until we see if it actually works. So read the
docs and be sure you know what you are doing. There is a user operating manual available on the PSAT2 web page:

[ANS thanks Bob Bruninga, WB4APR for the above information]


Inactive satellites removed from TLE distribution

The following satellites, marked as inactive, have been removed from this AMSAT-NA TLE Distribution as of April 8 2021. The source is from ANS-101.
A note regarding GRIFEX: according to PE0SAT it is still active.

TISAT – NORAD Cat ID 36799
JUGNU – NORAD Cat ID 37839
AO-71 – NORAD Cat ID 37854
HORYU-2 – NORAD Cat ID 38340
BEESAT-3 – NORAD Cat ID 39135
BEESAT-2 – NORAD Cat ID 39136
TRITON-1 – NORAD Cat ID 39427
VELOX-1 – NORAD Cat ID 40057
DAURIA DX 1 – NORAD Cat ID 40071
LQSat – NORAD Cat ID 40958
OUFTI-1 – NORAD Cat ID 41458
Swayam – NORAD Cat ID 41607
AlSat 1N – NORAD Cat ID 41789
ScatSat – NORAD Cat ID 41790
Pegasus-1 – NORAD Cat ID 41846
UCLSat – NORAD Cat ID 42765
LituanicaSAT 2- NORAD Cat ID 42768

Satellitnyheter SDR och mjukvara

UVSQSAT tips från SM4JLX Inge

In Swedish only!
Några tips från SM4JLX runt mottagning av UVSQSat:

Just nu styr jag antennerna med en W7 dator och Gpredict tillsammans med rotcld (hamlib-w32-4.0), använder en Arduino Mega med L298N deivkrets. Rotorprogrammet i Arduino är från K3NG. Inte mycket till antenner ännu och ingen preamp.

IC-9700 är kopplad via USB till en W10 dator som även kör Gpredict för frekvens korrigering, där går även SoundModem för att koda ut BPSK, även UVSQsat Decoder – 0.5 för att sända in telemetrin.
Då man är pensionär numera så har jag kunna följa UVSQsat några dar och testat lite andra förslag på satellit än 2021-006AB.
Problemet är att justeringen av doppler frekvensen inte stämmer för mig och då måste man hela tiden justera i SoundModem vilket område datat kommer att hamna.

Nu har jag kommit fram till följande ordning på de olika satelliter som jag lyssnat på och jag skulle då vilja ha satelliter som kommer in tidigare än 6AB. Det gör följande om man ser på passage idag ca. kl. 15. 6AA 4 sek. före 6AB, 6Z 18 sek. före 6AB, 6Y 80 sek. före 6AB. Vid test så fick jag mot 6Y att radion ställde in sig hela passagen på för låg frekvens.
Mot 6Z så ställde radion in sig på för hög frekvens utom vid närmaste avstånd då det verkar stämma bra.

Testat även 6AA och då ställde radion in sig för hög frekvens hela tiden.
Ska kolla 6AB på samma sätt också men jag tror nog att jag får samma värden som 6AA.

Jag kanske är ute och svamlar, men kul tycker jag det är ändå när man få allt att fungera rätt så bra.

Har även en Linux burk med en FunCube dongel som tar telemetri från Fox satelliterna (1 just nu).

73 de SM4JLX / Inge


RadFxSat-2 Signals Detected

Info from ANS-028:
RadFxSat-2 Signals Detected, AMSAT Engineering Continues to Assess

On January 27th, Brad Schumacher, W5SAT, reported copying his CW
signal weakly via the RadFxSat-2 transponder. On the morning of
January 28th, AMSAT Engineering and Operations confirmed these reports and determined that RadFxSat-2 is partially functioning, though
signals are extremely weak. AMSAT thanks W5SAT for his report.

We also appreciate those who joined in determining whether they could
detect their own or other signals in recent passes today.

At this time it is essential and we ask you: Please do not attempt to
transmit through the transponder until further notice. This is very
important to the next steps we are taking now.

The next crucial step in evaluating the condition of RadFxSat-2 is to
determine whether or not the 1200 bps BPSK telemetry beacon is
operating and, if possible, copy telemetry from the beacon. We ask
that everyone with 70cm receive capability listen to the beacon
frequency of 435.750 MHz (+/-) Doppler, upper sideband (USB). Use
FoxTelem with your receiver in order to tune and capture any telemetry
you can. Also make sure FoxTelem is set to “Upload to server” so that
we receive your telemetry data. If you capture a good IQ recording on
SDR, please send a detailed description of your recording to
foxtelem@amsat.us. We may respond with a request for your recording
and details on how to transfer it to the AMSAT Engineering team.
Please understand that keeping the transponder clear is essential to
putting all power and attention to the beacon telemetry.

Two-line elements (TLEs) are available in AMSAT’s nasabare.txt
distribution at https://www.amsat.org/tle/current/nasabare.txt.
Available data suggests that RadFxSat-2 is OBJECT M from the Virgin
Orbit LauncherOne launch, NORAD ID 47320, international designation

We thank the amateur satellite community for their perseverance and
assistance while the AMSAT Engineering and Operations teams work to
understand and resolve the situation with RadFxSat-2.

[ANS thanks the AMSAT Engineering and Operations teams for the above information]



UVSQ-SAT Launch Now January 24th

The launch of UVSQ-SAT, which carries an FM transponder for amateur radio use is now planned for January 24, 2021 at 15:00 UTC.
437,020 MHz

The project team is offering a gift to the first 5 people who receive
the satellite’s signal and the first 5 people who receive and decode
the signal and submit it to the AMSAT-F server and/or SatNOGS.

For more information on UVSQ-SAT, see the following links:



UVSQ-SAT Decoder


[ANS thanks Christophe Mercier, AMSAT-F President, for the above


Update on the Status of RadFxSat-2 / Fox-1E

From ANS-024:
RadFxSat-2 was launched Sunday, January 17, on Virgin Orbit
LauncherOne launch vehicle. Reports from the launch provider stated
that telemetry confirmed that the deploy commands had been sent and
that all of the doors opened successfully, resulting in payload orbits
that were all within the ICD limits.

Nominally, we expected to see “First (digital) Veronica” from the
RadFxSat-2 telemetry beacon commencing 54 minutes after our deployment
from the launch vehicle. That did not occur as expected.

For each of our launches, we follow a number of steps documented in
the “In Orbit Checklist” (IOC) spreadsheet. Confirmation of launch
and deployment are the first steps and then, confirmation of beacon
reception. All other steps follow that but there are steps in case of
anomaly, beginning with the detection of the beacon.

As always, from the moment we are deployed we look for signs of the
beacon through the ears of amateur radio operators and other means,
SatNOGS and webSDR to name a few. The antenna deployment and full
start of the IHU to bring up the beacon can occur anywhere around the
globe. AMSAT greatly appreciates the ongoing and reliable help we
receive from you and it is by far the best satellite ground network
even beyond that of many commercial players, for LEO orbits.

Command coverage is limited to the United States for various reasons
including regulatory requirements, so the opportunity to exercise the
steps of the IOC occurs a few times per day as the orbit passes over

With no sign of the beacon after a few orbits offering good footprints
for reception, we proceeded with the contingency steps to verify the
presence of or activate the beacon. This past week our Engineering
and Operations Team members have been at work literally 20 hours per
day exercising all of the contingencies outlined in the IOC steps.
These steps have grown and matured with each launch of a Fox-1 program
CubeSat and are tailored to the specific satellite. RadFxSat-2, while
she may seem to be much the same as the others with the exception of
the transponder vs. FM radio, does present a number of variations to
be included in the IOC. As the results of those steps were exhausted
with no beacon detected, we added meetings and increased emails
including all of our engineers to discuss possible causes by any of
the systems and to develop further steps.

From those we drew new steps of command sequences that might overcome
whatever anomaly existed and make the beacon heard. As the week drew
on, we continued brainstorming and steps to activate other functions
that would provide proof of life. We continue to do so today and for
whatever time until we exhaust all possibilities that we are able to
draw from the expertise and satellite experience of our Engineering
Team and Operations Team drawing from the design of RadFxSat-2 and
lessons learned in the Fox-1 program as well as any from missions
prior to AMSAT’s first CubeSats.

AMSAT still needs your help as always, to help detect any sign of
activity from RadFxSat-2. This includes ability to listen for local
oscillators or transponder driver output in the case of a failed PA.

I personally ask that those of you who are and have been interested in
the entire process of bringing a new amateur radio satellite to orbit
and through end of life to continue to contribute your curiosity and
enthusiasm in exploring from your own station, to pursue the
possibilities of a successful RadFxSat-2 mission along with us. I
have received reports and queries from some of you, and I greatly
appreciate your contributions. You are in fact volunteers in the
AMSAT Engineering Team through your contribution.

If you are interested, I ask that you do due diligence in your
procedure if you think you have identified a signal by re-creating (if
possible) and verifying to yourself that what you have is credible, as
we do, before contacting us. That “standard” procedure is what adds
value by making the information actionable rather than placing the
onus of determining if it is even real upon us, because we are of
course quite busy with that already. Please email your findings to
foxtelem@amsat.us and allow us a day or two to acknowledge and/or

While we tend to talk about our involvement with RadFxSat-2 above all,
a real effect reaches outside our mutual desire for amateur radio
satellite fun. RadFxSat-2 is sponsored by Vanderbilt University as
part of our long partnership going back to Fox-1A. RadFxSat-2’s
mission belongs to Vanderbilt University as part of their RadFX series
of missions seeking to verify and explore radiation effects on COTS
components. Their mission coincides well with AMSAT’s desire to fly
lower cost satellite missions using COTS components, in the unfriendly
radiation environment of Earth orbit and beyond. Vanderbilt also
sponsored the CSLI for RadFxSat (one) in our Fox-1B spacecraft back in

  1. Their proposal was selected by NASA, flown on the ELaNa XIV
    mission in November of 2017.

RadFxSat’s mission was very successful in the information provided
through the combined telemetry-gathering of all of those who pursue
our missions through FoxTelem. Vanderbilt University published their
results giving praise to AMSAT and our Fox-1 CubeSats. The experiments
we host are built by students and Vanderbilt shares the experiences
with the educational community in their area. That is a success for
AMSAT as well in our goal to provide STEM and other educational

While the RadFxSat-2 mission is problematic at this time, we will
pursue every possibility to make her work for the amateur community
and for our partner. I certainly hope to continue our partnership
with Vanderbilt, the mutual benefit is a wonderful and fun undertaking
that adds to the value of our satellites.