RadFxSat-2 Identified, Testing Continues

Testing and characterization of RadFxSat-2/Fox-1E continues.  After user reports and additional verification that the linear transponder is at least partially functioning with a low level downlink signal, the Engineering and Operations teams worked to identify which satellite, or Object, orbited from the Virgin Orbit Launch Demo 2 is actually RadFxSat-2/Fox-1E.   Several objects have been suspected (D, C, and M), with Object C being suggested recently by Drew Glasbrenner, KO4MA.  Recently, these satellites have sufficiently spread apart to allow testing to determine which object is RadFxSat-2/Fox-1E.

During the 2 Feb 2021 0240 UTC passes, command station Mark Hammond, N8MH, compared Objects D, C, and M for the “best fit” for received signals with Doppler correction on both the uplink and downlink frequencies for each of the candidate objects.  Objects D and M were quickly eliminated from further consideration, due to poor frequency predictions of Doppler correction compared to observed signals. The clear best fit is Object C, which is known OBJECT C, INTELDES 2021-002C, and NORAD CAT ID 47311.   Therefore, AMSAT is happy to identify Object C/2021-002C/47311U as RadFxSat-2/Fox-1E.    Thank to Alan Biddle, WA4SCA, for support during the identification.

It should be noted that 18 SPS has not yet approved the identification for cataloguing.  Final determination of the object assignment comes from the squadron.

The Engineering and Operations teams appreciate the community’s cooperation thus far and affirm the request that users do not attempt to use the transponder until further notice.  The proper identification will allow further characterization of the satellite’s condition through additional testing.

On behalf of the Engineering and Operations Team,

Mark Hammond N8MH

RadFxSat-2 Update – January 29, 2021

From AMSAT Vice President – Engineering Jerry Buxton, N0JY:

Thanks go to W5SAT, who applied the amateur radio spirit of exploration and innovation to helping find out “what’s up?” with RadFxSat-2.

We appreciate his work and immediately applied it to our processes as we discover/recover RadFxSat-2.

Why was it not heard or found week ago?  There could be an unexplained behavior such that it could not and was not able to occur until the other day.  Our stations attempted transponder use under various conjectured and commanded states throughout this period as part of the exploration of the anomaly, but did not detect any signals.  They were able to confirm their signals the night of the 27th.

Following that we turned attention to the beacon, as you know.  We have not discovered the beacon yet and we have contacted some top class “big gun” stations, asking for their help.  The signal will obviously be pipsqueak and may not even be there.  The drive to find it, or if it is not detected then to take possible actions to activate it, is the information in the telemetry that is paramount to knowing through satellite data exactly what is going on.  We asked you that the transponder not be used because any power to signals in the transponder downlink is power stolen from the beacon strength.  We have asked everybody to listen, as from the beginning, to help find it and find status and solutions faster.  It may sound boring or useless but it is at the heart of every satellite launch and commissioning phase and perhaps the biggest part the general satellite community can play in the lifetime of the satellite.  The payoff is important to all of us, and I invite anyone to join the hunt and share in the enjoyment of – whatever happens.

I can’t say what we will be doing tomorrow for sure, we will be looking for any reports and telemetry as more and larger stations join and because we have seen behavior that is not clearly understood.  Procedures and conclusions that are not carefully thought out could result in losing what we have now.  It is comparable to NASA taking careful time in dealing with anomalies (barring safety-related issues).  Very importantly, we will be watching to see if anyone captured anything at all from the telemetry in the beacon.  All you have to do is hunt and catch one frame and you are a hero in this game.  Your help is greatly appreciated.

Unless there is some big news over the weekend, I expect that Monday evening would be the next opportunity for a short update, time permitting.

RadFxSat-2 Signals Detected, AMSAT Engineering Continues to Assess Status

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 at 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 21-002M.

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.

FoxTelem Version 1.07 Released

I’m officially releasing version 1.07 of FoxTelem. A test version has been out for a while, but it had several issues, including a lower decode rate than 1.06. That prevented release for a while. Those issues (and something like 65 other defects) are now all fixed and this decoder performs better than 1.06. Feel free to test them side by side and report back if that is not the case for you. We are always interested in any comparative results.

In addition to defects in FoxTelem 1.06 and earlier versions of 1.07, this also introduces Doppler calculation with automatic adjustment of the decoder frequency. This is especially useful for decoding beacons and has been helpful in testing for Fox-1A / AO-85 and Fox-1Cliff / AO-95 which are both in SAFE mode. Decoding from Doppler takes a bit of configuration to get right. Have a read of the new sections in the manual or ask for help if you want to give it a try. There are pros and cons vs “Find Signal” for sure.

Version 1.07 changes the core SDR within FoxTelem to use a Numerically Controlled Oscillator (NCO) rather than an FFT Filter for the conversion to base-band. This produces better decodes and will allow the support of wider bandwidth SDRs in the future. The old decoder is available still if needed from the settings screen. Read the manual for details.

Version 1.07 also introduces two new BPSK decoders in advance of the Fox-1E launch. (I have no inside information about when that will be, but I have the decoder ready 🙂 I also wrote some notes on the comparison between the two decoders, which you can read if you are interested in BPSK decoding performance, or just wonder what I do with my time in the evenings: http://www.g0kla.com/workbench/2019-03-09.php

The releases are here:

* Ability to add a new spacecraft from the menu. You can also remove them.
* Doppler calculation and tracking as an option instead of “Find Signal”
* A better SDR based on a Numerically Controlled Oscillator, ready for wider SDRs
* Two new PSK decoders – Costas Loop and Dotproduct
* RTL dongle implemented for testing, though more work to do
* Stops downloading keps when position calc is off
* Allows toggling of high speed / DUV display when in auto mode
* Fixed plotting issues for Earth plots
* Fixes several crashes and bugs
* Fixes copy paste issues with tables
* Respects left/right audio preference when processing wav files
* Implements formats for later spacecraft – Fox-1E and HuskySat
* Linux and Mac launch script updated to locate the JVM (especially on Mac). Please report if when this works/does not work
* MEMS gyro calibration updated
* Fixed a bug where AO-85 data from the server could not be stepped through

And many other bug fixes. Full list of changes here: https://github.com/ac2cz/FoxTelem/milestone/12?closed=1

Let me know any feedback.