Burns,
I'm sorry to say that I don't believe AO-85 is showing any signs of recovery per my observations or what you've shown via the satnogs network. I looked through a number of other observations on the network and have not seen DUV telemetry from AO-85, which would have a much smaller BW than the telemetry pictured in the linked observation and look overall different. The pictured waterfall in the observation you linked is instead characteristic of GMSK telemetry from CAS-4A; you can even see the CW beacon for CAS-4A sitting above CAS-4A's 2 min reboot cycling telemetry link. See: https://imgur.com/a/EK56HxB
Zhuhai OVS-01 / CAS-4A (NORAD 42761) has been exhibiting this currently unique 2 min rebooting cycle behavior across many observations due to its loss of stabilization and now negative power budget (or so is current prevailing speculation by CAMSAT). I have made many observations of this phenomenon over the past few weeks for CAS-4A that you can see here: https://network.satnogs.org/observations/?norad=42761&observer=&stat...
Additionally, the most recent TLE from celestrak (space-track mirrored) I have for AO-85 (today) doesn't even have AO-85 over the observing satnogs station when the linked observation was captured when I backpropagate things by a week in GPredict, although I will grant you that CAS-4A doesn't downlink on a frequency near what should have been observed for the FOX-1A pass by 2220 - Mogielnica - VHF https://network.satnogs.org/stations/2220/ in KN09wx. I believe the satnogs station you linked was malfunctioning in some way, since no FOX - 1A observation should have been scheduled at that time for that observer as AO-85 wasn't there. The frequency difference could probably be explained by overloading the LNA used or other aliasing, or it could just be reported wrong by the satnogs station client. It is probably also worth noting that the TLE used came from Cal-Poly, which is an atypical source... So maybe that is part of the confusion and or issues with 2220.
My personal theory is that the client observed CAS-4A with the wrong doppler curve and reported its obs for AO-85.
-Robert, KB3WFQ
PS: FYI this is what DUV-200 TLM looks like https://network.satnogs.org/observations/5887019/
On Wed, May 4, 2022 at 11:07 AM Burns Fisher wb1fj-bb@fisher.cc wrote:
Certainly worth having more eyes on it, Robert. Here is the observation that I know of: https://network.satnogs.org/observations/5864936/
The suspect is the wide signal in the middle which is not absolutely perfectly doppler corrected, but the key to think it is AO-85 is the little "tail" when it turns on. That is very much like the Fox FM satellite behavior. If you listen to the audio, it sounds like the tx and rx are on with no uplink signal. Very similar to what Fox FM satellites sound like when they time out.
The other signal in that observation (higher frequency, more doppler, two frequency side-by-side) I have seen commonly on AO-85 observations and on my own rig. I expect that is another bird in a similar orbit. But I've only seen that wide signal once.
On Wed, May 4, 2022 at 10:59 AM Robert Meade rjm27trekkie@gmail.com wrote:
If we are citing satnogs as the point of origin for evidence of the renewed operating condition of AO-85, can we link to the observations where it was found working? Are we sure these weren't overlapping passes with other birds? Did the doppler correction match precisely to support it not being an overlap?
-Robert, KB3WFQ
On Wed, May 4, 2022 at 10:40 AM Burns Fisher wb1fj-bb@fisher.cc wrote:
Thank you for posting AO-85 again Ray.
Folks, I've seen a single pass of AO-85 on SatNogs that looked like the repeater was running. Purely from looking at the waterfall, I did not see any telemetry data, and it appeared that the repeater was on for roughly two minutes, then cut off briefly, and then restarted. I saw no obvious signals being repeated.
I also tried a pass or 2 from my QTH and did not see or hear 85 (although there are other things at a similar time whose dopplers were not matching). So don't get your hopes up too high, but please do report anything. Especially try FoxTelem to see if you get data, and try uplinks to see if you can hear yourself (or anyone else). Be sure to report it in https://www.amsat.org/status/ as well as here and/or the AMSAT Discord board.
Thanks!
Burns Fisher AMSAT Flight Software
On Tue, May 3, 2022 at 10:49 PM ray.hoad@mypbmail.com wrote:
AO-85 is back!!! Per Paul Stoetzer, N8HM "it seems to have woken up." Like AO-07, you just can't keep a good satellite down.
TLE for AO-85 will be included in this week's TLE distribution.
For now, here are current TLE for AO-85:
AO-85 1 40967U 15058D 22122.55538421 .00005037 00000-0 52331-3 0 3555 2 40967 64.7745 211.7318 0200720 214.8082 143.9700 14.77257778 53883
Ray Hoad WA5QGD AMSAT-NA Orbital Elements Manager
Sent via AMSAT-BB(a)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. Acceptable Use and Privacy Policies available at https://www.amsat.org/about-amsat/
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Sent via AMSAT-BB(a)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. Acceptable Use and Privacy Policies available at https://www.amsat.org/about-amsat/
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org