Tianwen-1 post–TCM-1 state vectors

Yesterday I reported about Tianwen-1’s first trajectory correction manoeuvre, TCM-1. In that post I commented the possibility that the updated state vectors that we saw on the telemetry after TCM-1 might come from a prediction or planning rather than take into account the actual performance of the burn.

The figure below shows the error between the state vectors collected after TCM-1 over the last two days, and a trajectory propagated in GMAT, using the following state vector, which is one of the first received after TCM-1.

[0151059eb9ea] 2020-08-02 00:17:06.711400 100230220.21360767 -106145016.11787066 -45441035.07405791 25.581827920522485 18.240707152437626 8.567874276424218

We see that on the UTC night between August 1 and 2 the state vectors deviate very little from the GMAT trajectory. However, on the UTC night between August 2 and 3 we see a slightly different trajectory in the state vectors. We have no data in between, as the spacecraft is not visible in Europe, so we don’t know the precise moment of change. The gap in telemetry around 2020-08-03 00:45 UTC is due to a transmission of high-speed data.

It seems reasonable to think that after TCM-1 the Chinese DSN performed precise ranging of the spacecraft to determine the new orbit accurately and then uploaded a correction to the state vectors on-board Tianwen-1.

The state vectors from last night all describe the same trajectory, as shown in the plot below which uses

[0151322e67d0] 2020-08-02 21:03:08.078400 102132184.96868199 -104770375.00352533 -44795830.46284772 25.29849580646669 18.532513218789806 8.692135086385246

to propagate a trajectory in GMAT. There is a small jump of a few hundred meters at some point. We usually see one or two these jumps per day, but we don’t understand well why they happen.

The trajectory according to the state vectors from 00:17:06 and from 21:03:08 are very similar. For example, at the closest approach to Mars they only differ in 1197km. For comparison, the difference between the new trajectory and the pre–TCM-1 trajectory is 126529km (again, at the closest approach to Mars).

I have generated a new table of right-ascension, declination and distance coordinates based on the updated state vectors. Note that this table doesn’t include light-time delay to the spacecraft.

Thanks to AMSAT-DL‘s Bochum observatory team and to Paul Marsh M0EYT for their continuous effort in tracking Tianwen-1. The data used in this post has come from their observations.

Tianwen-1 TCM-1

On 2020-08-01 23:00 UTC, Tianwen-1 made its first correction manoeuvre, called TCM-1. The manoeuvre was observed by Amateur trackers, such as Edgar Kaiser DF2MZ, Paul Marsh M0EYT, and the 20m antenna at Bochum observatory, operated by AMSAT-DL. The news of the successful manoeuvre appeared in Chinese media, and in the German Wikipedia article for Tianwen-1 (thanks to Achim Vollhardt DH2VA for sharing this information).

Since Tianwen-1 transmits its own real time orbit state vectors in the telemetry, by comparing the vectors transmitted before and after TCM-1, and also by studying the Doppler observed by groundstations on Earth, we can learn more about the manoeuvre.

Continue reading “Tianwen-1 TCM-1”

Tianwen-1 manoeuvre and high-speed data

On the Beijing time morning of 2020-07-30, Tianwen-1 did something. Paul Marsh M0EYT reports that the probe first switched from the high gain antenna to the low gain antenna, then returned to the high gain antenna, and then switched to a high-speed data mode, finally coming back to the usual 16384baud telemetry.

r00t.cz has already analysed the telemetry data collected during this event. He reports that the high speed data was a replay of the telemetry produced during the period when the low gain antenna was used. He shows some interesting behaviour on APIDs 1280, 1281 and 1282 (see my previous post for a description of these during nominal operation). These seem to contain ADCS data.

This event was followed with some expectation by the Amateur deep space tracking community, since according to this paper Tianwen-1 would make the first correction manoeuvre (TCM-1) early on in the mission (day 9 is stated in the paper). However, by now it is clear that a true correction manoeuvre didn’t happen, since no significant change has been seen in the trajectory described by the state vectors transmitted in the spacecraft’s telemetry. However, this event might have been a very small thruster firing, in order to test the propulsion in preparation for the true TCM-1.

In this post, I look at the data during the high speed replay, following the same approach as in the previous post. With this data, I reach a definite conclusion of what happened during this event (I won’t spoil the mystery by stating it in advance). The description of the modulation and coding used by the high speed data will come in a later post.

The Jupyter notebook for the calculations in this post can be found here.

Continue reading “Tianwen-1 manoeuvre and high-speed data”

Tianwen-1 telemetry: framing and data

This is a follow-up to my previous post, where I explained the modulation and coding of Tianwen-1’s telemetry. In this post I will explain the framing structures and the data contained in the telemetry (though we only understand a few of the telemetry channels). Most of what I’m going to explain here was found first by r00t.cz and is already presented in his Tianwen-1 page. In this post I’ll try to give a bit more detail (especially for those not so familiar with the CCSDS protocols) and some Python code for those interested in digging into the data.

Continue reading “Tianwen-1 telemetry: framing and data”