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


#21

These are the TBEX TLEs corrected from the 03:30UTC to the 06:30UTC launch time.

TBEX-A
1 84001U 14900A   19176.27083333  .00000000  00000-0  00000-0 0    03
2 84001  28.5984 187.1642 0394051 105.4782 326.5543 14.97382750    03
TBEX-B
1 84002U 14900A   19176.27083333  .00000000  00000-0  00000-0 0    04
2 84002  28.5867 185.8955 0394590 105.0870 326.8044 14.98003902    07

#22

Thanks TLE for TBExs are updated on the scheduled observations.

With PSat-2 TLE maybe we have caught something in this observation, however need to confirm it with more.

@jwc maybe can you confirm if this was TBEx-A or not.


#23

Potentially, I can’t say for certain. They seem about 5 KHz high. Spacing should be every 10 s or so and that is close, but not exact.


#24

I’ve posted the latest TLEs from the rocket here: http://exploration.engin.umich.edu/tle/mxl.txt

See the 2019-36* objects. Space-track and Celestrak should have them online soon. Celestrak already has 5 of them.

Predictions put us close to H, J, K.

The predicted TLEs for TBEx and PSAT are close to these but distinctly off.

I’ll run new predictions shortly based on SpaceX data to see if they link up with H, J, K.


#25

Hmmm…PSAT-2 is beaconing that it is on 145.980 MHz.
“145.980MHz No Digi.”

PSAT-2 data

GL 73,

Guy W6MSU
Station 754


#26

Odd that PSat2 is active


#27

https://twitter.com/prstoetzer/status/1143576797189222401?s=21 Seems it’s some sort of uplink.


#28

If that is TBEX-A, on one hand, it’s a strong signal. On the other hand, we should be seeing 500 byte bursts at 10 s intervals. This continuous transmission would be bad.

The sats are scheduled to power cycle tonight or tomorrow depending on the clocks. We may see a change in behavior.


#29

From the latest observations and the latest space-track TLEs:

  • TBEx-A
    • one of 44354-44357 (chosen in network: 44354)
  • TBEx-B
    • no data (chosen in network: 44354)
  • ARMADILLO
    • no data (chosen in network: 44347)
  • PSat-2
    • no data in UHF from amsat list it transmits only SSTV when in Sun, now in southern hemisphere, some data in VHF not enough for TLE assignment, VHF is now closed until further notice (chosen in network from tweeter: 44348)
  • BRICSat-2
    • no data in UHF, from data in VHF one of 44354-44357 (chosen in network: 44356)
  • CP9 (LEO)
    • one of 44354-44357 (chosen in network: 44355)
  • Oculus-ASR
    • no data (chosen in network: 44348)

#30

I’ve scheduled observations for the next 48h.

We had one good PSat-2 observation so TLE should be one of 44354-44357 (chosen in network: 44357)

For the successful PSat-2 observation the signal is ~10KHz off. Not sure if it was the station or the satellite, we will need to wait for more observation to be sure.


#31

According to @vk5qi tweet:

I’ve changed TBEx-A to follow 44355 and CP9 to follow 44354.


#32

PSat-2 UHF Transmitters seems to be 4.4KHz off, I have added this change in db and updated scheduled observations. 44348 still seems to be the right object to follow for TLEs for PSat-2


#33

ARMADILLO is now alive and received!
CP9 (LEO) is closer to 44356-44357. Chosen for network: 44357


#34
  • TBEX-A:
    • No signal (still use 44355 in network)
  • TBEX-B:
    • No signal (still use 44354 in network)
  • ARMADILLO:
    • 44348, 44352, 44354-44357 (changed to 44355 in network)
  • PSAT-2:
    • 44354 or 44355 (changed to 44354 in network)
  • BRICSAT-2:
    • from this observation the only one that probably have its signal in UHF 44354 or 44355 (changed to follow 44355 in network)
  • CP9 (LEO)
    • 44360 or 44361 (changed to 44361 in network)
  • Oculus-ASR

#35

We decoded one of the TBEx satellites. We now think BOTH are on 437.485. So, we are looking for both A and B on 437.485. It seems we were in the first group of CubeSats, so objects R S or T.


#36

I’ve scheduled a couple extra observation on 437.485MHz for TBEx-B and also added it into db. Please if you fully confirm that indeed TBEx-B transmits also in 437.485MHz, let us know in order to fix future observations to watch the right frequency.


#37

By using ikhnos on 775500 from the current objects it looks like that only 44355 matches the PSAT-2 SSTV signal, as you can see in the image bellow:

The red line shows the signal we would get if TLE from 44355 were used. TLE from 44354 would be a straight line but as you can see there is a little curve at the start of the observation that is like the one coming from 44355 TLE.

PS I would like to thank again @cgbsat for helping me build this tool by writing the initial code!
So, I’ve just changed the norad id to 44355 for PSAT-2.


#38

Update for ARMADILLO it looks like that it is one of 44347, 44348 or 44352 (changed to follow 44348 in network)


#39

UPDATE for CP9 (LEO) it looks like it is 44360 (changed to follow in network), however this norad id isn’t assigned yet to an object from space-track, which means that could possibly change.


#40

Newer observations with decoded data show that indeed it is 44360, however still waiting for an object to be assigned on these TLE in space-track.