Falcon Heavy Launch 2019-06-25 03:30 UTC


#41

ARMADILLO looks like it is either 44348 or more likely 44352, it’s definitely not 44347. Changed to 44352 in network.


#42

@jwc could this signal in the middle be one of TBExs? https://network.satnogs.org/observations/778884/ the one at the right 99% is CP9.

A similar situation there is at this obs https://network.satnogs.org/observations/778889/ but it’s not so clear.

Just to add that no other satellite near this frequency was visible during the two passes above.

Here is a CP9 observation for reference https://network.satnogs.org/observations/779172/

EDIT: and one more recent some minutes ago https://network.satnogs.org/observations/778861/


#43

The most recent, 778861, it looks like CP9 but the frequency is all over the place. Towards the end of the pass it looks like CP9 is on both sides of the spectrum?

A healthy TBEx should like GRIFEX and MC2 but with a transmission that is twice as long (two beacons at once).

(edit) @fredy This one si interesting. https://network.satnogs.org/observations/778912/ I’ve seen something around 520, looks like a 10s period.


#44

CP9 (LEO) is OBJECT X with NORAD ID 44360. Its NORAD ID is changed in Network and DB

from observation 779160 the theoretical signal (red line) and the signal follow the same path:


#45

According to this tweet:

LightSail-2 is going to be deployed from PROX-1 on Tuesday, unfortunately still no info if PROX-1 is alive and if there are any TLE for it, in order to use them for LightSail-2.


#46

On PSAT-2, there is an assignment of NORAD ID 44357, not sure what was the source of this identification. This is far from my calculations with ikhnos. I still think that PSAT-2 is one of OBJECT R or S, however all the three of these TLE are close to 1 day old, so this can affect my calculations, so let’s wait a little more on assigning a NORAD ID on PSAT-2.


#47

We just decoded TBEX-A on 437.485 tracking object 44356.


#48

Indeed some of the latest observations in SatNOGS have signal of TBEx-A.

I’ll agree on 44356, from my calculations there are a couple more objects that could be 44357 and 44359. I hope to get more good observations to make it sure!

What is its status? Anything worrying, like low voltage?


#49

The telemetry looks ok. Power is good. The clocks and resets are odd. Only 3 resets shown but the clock was low, had been running for only a few minutes. Not sure what to make of that.

Our beacon client is a little un stable and we think it’s crashing, hence the lack of regular beacons. Plan is to get some commands up if we can asap.


#50

A quick update:

TBEx-A: From the latest good observation it looks like that the right norad id is 44359. I have changed the satellite to follow this norad in network and waiting at least one more observation to confirm it in order to change the satellite’s norad id.

PSAT-2: From VHF observations it looks like that 44355 is the right one. But I think we need a couple more observations to be 100% sure and reject 44354. UFH SSTV transmissions drifting but still they confirm the norad ids.

ARMADILLO: It looks like that 44352 is the right one, but still I need a couple more observation to reject 44348. Also as the signal is drifted, I have added a drift of -2.3KHz in the transmitter, this will help us to decode more packets.

Still no news from BRICSat-2, Oculus-ASR.

Tomorrow UTC morning there will be LightSail-2 deployment, unfortunately no NORAD ID has been assigned to Prox-1. This will make difficult to observe it. I’m going to do some analysis and assign one NORAD ID/TLE. If anyone has any news or any suggestion, please let me know.

I remind you that for CP9 (LEO) we have ended up to 44360.


#51

@jwc
How much possible is it that TBEx-B transmits also at 437.485MHz? You said something about it before, but I want to make it sure.

I’m asking because we have this situation, there is this observation that matches OBJECT W (44359) while it is far from matching with OBJECT T (44356) which was used for this observation. Here are two calculations (the first for T and the second for W) with taking the closest in time of the observation TLE of the two objects:

There is also this CP9 observation, where at the left top we can see TBEx signal that again fits OBJECT W better.

However there is this observation that shows a better fit for OBJECT T in calculations (the first for T and the second for W):

There are also this and this observations that showing that ~40min earlier there was signal, unfortunately they don’t have a clear path of the signal in order to match with one of the two norad ids, but OBJECT T shows a little better matching than W.

For those two there are also two more observations that confirm that there is a match for T and W for this signal, the one is of TBEx-B (that follows a random norad id) and the other of CP9.

For all the above observations, I have cross-checked that no other satellite (at least from the known ones), that transmits near 437.485MHz, was receivable by the stations. Also the matches with the objects are too good to be a satellite from other launches.

So, the question is, do we see two different satellites or we miss something?

@jwc you said that you have managed to decode TBEx-A, is it possible to share the exact datetime of these receivings/decodings? Even if there wasn’t a TBEx observation scheduled, it could be possible to extract some info from other observations and at least make sure which OBJECT is TBEx-A.

PS I’m going again to change TBEx-A to 44356 and TBEx-B to 44359.


#52

LightSail-2 deployment was successful! And SatNOGS Network was the first (at least in twitter :P) to get a signal https://twitter.com/alanbjohnston/status/1145980536760020992

The signal fits better the OBJECT A (44339), so I’m going to change this to both LightSail-2 and Prox-1. Now we are waiting for a new object to follow.


#53

B is definitely on 485. We decoded both in 485. We will check time stamps and get back to you on the timing. We seem to be beaconing for a little while every two days. That ours watchdog reboot period.


#54

Quick update:

ARMADILLO:
We changed its temporary NORAD ID to 44352!
44348 is now fully rejected, check the red line (expected signal path) in the images below (1st is 44352, 2nd is 44348):

For PSAT-2 still on the same status, 44355 looks to be the right one, but still waiting for newer TLE for 44354 to be fully sure.

Thanks!


#55

After a sort period of no sigal, LightSail-2 is back. Also we have a dashboard thanks to @DL4PD.


#56

There are two new OBJECTS, Z (44375) and AA (44376). AA has been recognized as OCULUS-ASR SPHERE. Also 44356 has been recognized to be OCULUS-ASR and it is now changed in both DB and Network. The other one it’s unknown (maybe the other SPHERE of OCULUS?), but for sure it is not LightSail-2.

LightSail-2 has started not to fit in 44339, but still this object is the best for scheduling observation of LightSail-2. Check the light curve of the signal in the next image compared with the straight red line of 44339:

Thanks to @cgbsat for let us know this post by planetary society about LightSail-2, there is a reference to SatNOGS there, and a big thanks to everyone helping keeping this Network alive and able to receive signal from satellites around the world:


#57

Lightsail 2 have released a lot of info to help decode the telemetry data here:

https://planetary.s3.amazonaws.com/projects/lightsail/manuals/ls2-beacon-info-v01.txt

There is a Lightsail 2 Mission Control Dashboard using the data they are collecting too.


#58

TBEx-A or TBEx-B was heard in this observation and fits OBJECT W (44359):
https://network.satnogs.org/observations/795372/

I vetted also as good these two observations as they have signals and not other satellite around, however not 100% if they are indeed on of the them:
https://network.satnogs.org/observations/795436/ between 200s - 300s
https://network.satnogs.org/observations/789038/ at ~480s


#59

One more observation at TBEx frequency that fits 44359 OBJECT:
https://network.satnogs.org/observations/800859/

On PSAT-2:
Still OBJECT S (44355) looks to fit perfectly on VHF signals. However OBJECTS R (44354) and the new Z (44375) are in too close orbits. Before fully identify, let’s wait for a couple of days to have a clear result.

On LightSail-2:
Still missing an object that fits, still Prox-1 TLE are the best to follow.


#60

Lightsail-2 has finally its own NORAD ID and it is 44420, we are going to watch it for a couple of days until we fully move it to this NORAD ID.