SpaceX F9 Transporter-8 - 2023-06-12 21:35 UTC

will it be updated for the existing scheduled observations? like: SatNOGS Network - Observation 7823754

Yes it does after some time.

It does not seem really matched, there is a slight difference now: SatNOGS Network - Observation 7823754

Currently this is the best match. I can think two scenarios:

  1. There are more TLE to come
  2. As the TLE is still not assigned it may describe more than one satellites, also it is ~1 day old, which could make it inaccurate. To be honest, 1 day old TLE at this altitude shouldnā€™t make a significant difference.

I suggest we wait for 1-2 days to see and at the same time we can generate/use a more accurate TLE if you have one.

Indeed, one of the latest recording seems more accurate: SatNOGS Network - Observation 7828915

For ISTANBUL we were observing object M 56943ā€¦ Got signals with dopplerā€¦
When matched those to other TLEs using IKHNOS looks like ISTANBUL is 56942

I know this belongs to another identified object but that is what it is ā€¦ looks better than 56943

@fredy can I ask for one more change on ISTANBULā€™s TLE on satnogs network

here are the IKHNOS outputs for 2 observations

73ā€™s de
OH2UDS / TA7W
Baris

@oh2uds

None of the signal in both waterfalls you posted belongs to this launch. Iā€™ve re-vetted the observations as bad.

ISTANBUL is one of these OBJECTS:

0 OBJECT BR
1 56989U 23084BR  23188.41786933  .00017655  00000-0  10137-2 0  9995
2 56989  97.5070 304.6146 0018235 145.5028 214.7390 15.12444878  3716
0 OBJECT BS
1 56990U 23084BS  23188.74106830  .00012837  00000-0  72848-3 0  9990
2 56990  97.5116 304.9654 0015600 136.4964 223.7501 15.12978354  3767
0 OBJECT BT
1 56991U 23084BT  23188.40067440  .00011020  00000-0  60640-3 0  9997
2 56991  97.5113 304.6493 0014029 119.9045 240.3582 15.14138744  3715
0 OBJECT BK
1 56226U 23084BK  23188.72995128  .00007925  00000-0  43812-3 0  9997
2 56226  97.5135 304.9870 0012293 128.6309 231.6025 15.14089930  3765
0 OBJECT BL
1 56227U 23084BL  23189.07112612  .00015298  00000-0  85851-3 0  9997
2 56227  97.5150 305.3063 0013582 127.7234 232.5230 15.13362885  3817
0 OBJECT BM
1 56228U 23084BM  23188.41039393  .00009663  00000-0  54571-3 0  9993
2 56228  97.5151 304.6536 0013738 129.7571 230.4872 15.13249413  3714
0 OBJECT BN
1 56229U 23084BN  23188.74093898  .00007568  00000-0  42865-3 0  9995
2 56229  97.5149 304.9794 0013780 127.7055 232.5427 15.13219799  3761
0 OBJECT BP
1 56230U 23084BP  23188.61662199  .00034993  00000-0  19876-2 0  9996
2 56230  97.5137 304.8322 0017419 151.5329 208.6857 15.12696561  3742
0 OBJECT BQ
1 56231U 23084BQ  23188.61971878  .00010577  00000-0  61506-3 0  9994
2 56231  97.5133 304.8279 0018397 147.5038 212.7329 15.12106591  3747

It can not be 56942 as this object is tracked before its deployment from ION.

Iā€™ve went through all the vetted as good observations of ISTANBUL, Iā€™ve revetted all as bad, specifically:

SatNOGS Network - Observation 7822596 ā†’ Signals donā€™t belong to this launch, also the one at the right is too off for ISTANBUL frequency

SatNOGS Network - Observation 7822590 ā†’ Signal at the top doesnā€™t belong to this launch

SatNOGS Network - Observation 7822598 ā†’ Signals donā€™t belong to this launch

SatNOGS Network - Observation 7808999 ā†’ No signal at all

SatNOGS Network - Observation 7809003 ā†’ Signals too off from expected ISTANBUL frequency, also donā€™t much the expected FSK 600

SatNOGS Network - Observation 7808994 ā†’ Signal too off from expected ISTANBUL frequency, also doesnā€™t much the expected FSK 600

SatNOGS Network - Observation 7799662 ā†’ Signal too off from expected ISTANBUL frequency

SatNOGS Network - Observation 7769809 ā†’ Signal too off from expected ISTANBUL frequency

SatNOGS Network - Observation 7769053 ā†’ Singal doesnā€™t much the expected FSK 600

Let me know if I miss something.

3 Likes

Latest Status Update:

Temporary NORAD ID Satellite NORAD ID to follow Other NORAD IDs Identified Deployed Last Update
RECEIVED AND DEMODULATED
ION SCV-011 56957 - YES YES Identified, here are the ikhnos results
99187 ROM-2 56230 56226-56229,56231,56989-56991 NO YES Randomly change to follow 56230, other possible 56226-56229,56231, 56989-56991
99182 MRC-100 56231 - NO YES Changed to follow 56231, waiting for a couple more observations for identification
99115 FOSSASAT-FEROX 14 - PlatziSat-1 - all NO YES Received according to tinygs
99100 SpeiSat 56991 - NO YES Changed to follow 56991, waiting for a couple more observations for identification
99114 FOSSASAT-FEROX 15 - all NO YES Received according to tinygs
99112 FOSSASAT-FEROX 17 - all NO YES Received according to tinygs
99097 MDQSAT-1C - all NO YES Received according to tinygs
99096 MDQSAT-1D - all NO YES Received according to tinygs
RECEIVED
99258 Tomorrow-R2 56959 56958, 56960(unlikely) NO YES No update
Otter Pup 56933 - YES YES Identified, here are the ikhnos results
OBJECT 23084BH (Transporter 8 Satellite E) 56987 - YES YES Identified, here are the ikhnos results
OBJECT 23084AJ (Transporter 8 Satellite D) 56964 - YES YES Identified, here are the ikhnos results
OBJECT 23084AG (Transporter 8 Satellite B) 56962 - YES YES Identified, here are the ikhnos results
OBJECT 23084C (Transporter 8 Satellite A) 56934 - YES YES Received again and Identified, here are the ikhnos results
RECEPTION STOPPED
99078 Transporter 8 Satellite F 56938 56932-56937, 56939-56944 NO YES No reception since 2023-06-15 11:31, changed to follow 56938, other possible 56932-56937, 56939-56944
NOT RECEIVED
99082 Transporter 8 Satellite C - - NO YES Not currently observing, trying to figure out if they are known or unknown satellites
99192 Istanbul 56228 56226,56227,56229-56231,56989-56991 NO YES Randomly change to follow 56228, other possible 56226,56227,56229-56231,56989-56991
99101 Outpost Mission 0 56991 56226-56231,56989,56990 NO YES Randomly change to follow 56991, other possible 56226-56231,56989,56990
99113 FOSSASAT-FEROX 16 - - NO YES
99352 URESAT-1 56989 56226-56231,56990,56991 NO YES Randomly change to follow 56989, other possible 56226-56231,56990,56991
99095 Pleiades-Squared - - NO YES
99104 QPS-SAR-6 - - NO YES
99106 GREGOIRE - - NO YES
99109 XVI - - NO YES
99110 Droid.001 - - NO YES
99107 AFR-1 - - NO YES
99105 Orbiter SN3 - - NO YES
99111 EIVE - - NO YES
99102 Winnebago-1 - - NO YES
99106 GREGOIRE - - NO YES
99108 MuSat-1 - - NO YES
99260 Blackjack Aces-2 - - NO YES
99262 Blackjack Aces-4 - - NO YES
99259 Blackjack Aces-1 - - NO YES
99261 Blackjack Aces-3 - - NO YES
99099 SATLLA-2I 56227 56226,56228-56231,56989-56991 NO YES Randomly change to follow 56227, other possible 56226,56228-56231,56989-56991
NOT IN DB
- AII-DELTA - - NO YES
- GEISAT - - NO YES
- Ayris-1 - - NO YES
- Ayris-2 - - NO YES
- LEMUR 2 EMBRIONOVIS - - NO YES
- MISR-A - - NO YES
- LEMUR 2 NAZIYAH - - NO YES
- LEMUR 2 AADAM-ALIYAH - - NO YES
- Swarm Spacebees - - NO YES
- MISR-B - - NO YES
- Tiger-4 - - NO YES
- NewSat 40 - - NO YES
- NewSat 41 - - NO YES
- NewSat 43 - - NO YES
- NewSat 42 - - NO YES
- 1st ICEYE satellite - - NO YES
- 2nd ICEYE satellite - - NO YES
- 3rd ICEYE satellite - - NO YES
- HotSat-1 - - NO YES
- 4th ICEYE satellite - - NO YES
- Skykraft-3 - - NO YES
- GHOSt-3 - - NO YES
- Runner-1 - - NO YES
- EpicHyper2/Dragonette 2 - - NO YES Waiting deployment from ION SCV-011

[quote=ā€œfredy, post:129, topic:10499ā€]
Latest Status Update:
99192 Istanbul 56228 56226,56227,56229-56231,56989-56991 NO YES

ISTANBUL observation with 56228 has some signals in the first 100 seconds without dopller.
Any comments ?

https://network.satnogs.org/observations/7835394/

Baris
OH2UDS / TA7W

Given that it isnā€™t visible in other observations at the same time, Iā€™m not sure if this is ISTANBUL or other satellite or local noise. Also there isnā€™t any signal in observations after 1.5h. Letā€™s keep observing though to verify it.

A few basic info on ISTANBUL;

  • normal period of 401 MHz beacon is 180 seconds
  • if it has some data to relay this information re-transmissions might be more frequent
  • Baudrate is 600 bps but RF BW if 5 KHz
    - The team figured out a bug in BEACON that may randomly stop/start beaconing (or the beacons might be 1 byte long or 255 bytes longā€¦

We will be monitoring 56228 observationsā€¦thanks

Baris
OH2UDS / TA7W

1 Like

Latest Status Update, highlights, SpeiSat identification and reception of the unknown ā€œTransporter 8 Satellite Fā€ which limited the possible objects to two:

Temporary NORAD ID Satellite NORAD ID to follow Other NORAD IDs Identified Deployed Last Update
RECEIVED AND DEMODULATED
ION SCV-011 56957 - YES YES Identified, here are the ikhnos results
99187 ROM-2 56230 56226-56229,56231,56989-56991 NO YES Randomly change to follow 56230, other possible 56226-56229,56231, 56989-56991
99182 MRC-100 56231 - NO YES Changed to follow 56231, waiting for a couple more observations for identification
99115 FOSSASAT-FEROX 14 - PlatziSat-1 - all NO YES Received according to tinygs
SpeiSat 56991 - YES YES Identified, here are the ikhnos results
99114 FOSSASAT-FEROX 15 - all NO YES Received according to tinygs
99112 FOSSASAT-FEROX 17 - all NO YES Received according to tinygs
99097 MDQSAT-1C - all NO YES Received according to tinygs
99096 MDQSAT-1D - all NO YES Received according to tinygs
RECEIVED
99258 Tomorrow-R2 56959 56958, 56960(unlikely) NO YES No update
Otter Pup 56933 - YES YES Identified, here are the ikhnos results
OBJECT 23084BH (Transporter 8 Satellite E) 56987 - YES YES Identified, here are the ikhnos results
OBJECT 23084AJ (Transporter 8 Satellite D) 56964 - YES YES Identified, here are the ikhnos results
OBJECT 23084AG (Transporter 8 Satellite B) 56962 - YES YES Identified, here are the ikhnos results
OBJECT 23084C (Transporter 8 Satellite A) 56934 - YES YES Received again and Identified, here are the ikhnos results
99078 Transporter 8 Satellite F 56936 56935 NO YES Received again, changed to follow 56936, removed other possible 56932-56934, 56937, 56939-56944, other possible 56935
NOT RECEIVED
99082 Transporter 8 Satellite C - - NO YES Not currently observing, trying to figure out if they are known or unknown satellites
99192 Istanbul 56228 56226,56227,56229-56231,56989-56991 NO YES Randomly change to follow 56228, other possible 56226,56227,56229-56231,56989-56991
99101 Outpost Mission 0 56991 56226-56231,56989,56990 NO YES Randomly change to follow 56991, other possible 56226-56231,56989,56990
99113 FOSSASAT-FEROX 16 - - NO YES
99352 URESAT-1 56989 56226-56231,56990,56991 NO YES Randomly change to follow 56989, other possible 56226-56231,56990,56991
99095 Pleiades-Squared - - NO YES
99104 QPS-SAR-6 - - NO YES
99106 GREGOIRE - - NO YES
99109 XVI - - NO YES
99110 Droid.001 - - NO YES
99107 AFR-1 - - NO YES
99105 Orbiter SN3 - - NO YES
99111 EIVE - - NO YES
99102 Winnebago-1 - - NO YES
99106 GREGOIRE - - NO YES
99108 MuSat-1 - - NO YES
99260 Blackjack Aces-2 - - NO YES
99262 Blackjack Aces-4 - - NO YES
99259 Blackjack Aces-1 - - NO YES
99261 Blackjack Aces-3 - - NO YES
99099 SATLLA-2I 56227 56226,56228-56231,56989-56991 NO YES Randomly change to follow 56227, other possible 56226,56228-56231,56989-56991
NOT IN DB
- AII-DELTA - - NO YES
- GEISAT - - NO YES
- Ayris-1 - - NO YES
- Ayris-2 - - NO YES
- LEMUR 2 EMBRIONOVIS - - NO YES
- MISR-A - - NO YES
- LEMUR 2 NAZIYAH - - NO YES
- LEMUR 2 AADAM-ALIYAH - - NO YES
- Swarm Spacebees - - NO YES
- MISR-B - - NO YES
- Tiger-4 - - NO YES
- NewSat 40 - - NO YES
- NewSat 41 - - NO YES
- NewSat 43 - - NO YES
- NewSat 42 - - NO YES
- 1st ICEYE satellite - - NO YES
- 2nd ICEYE satellite - - NO YES
- 3rd ICEYE satellite - - NO YES
- HotSat-1 - - NO YES
- 4th ICEYE satellite - - NO YES
- Skykraft-3 - - NO YES
- GHOSt-3 - - NO YES
- Runner-1 - - NO YES
- EpicHyper2/Dragonette 2 - - NO YES Waiting deployment from ION SCV-011

There are 3 new satellites in this batch: 2023-084BU, BV and BW (56992, 56993 and 56994). BV is a good candidate for MRC-100 since it is ~30-35 seconds behind BQ and this is in accordance with the slight +frequency offset in the waterfalls we received just recently in the last few days. I did a BQ ā†’ BV correction on the waterfalls based on the I/Q recordings of 7848601 and 7848602 - and matches pretty well. BW is ahead of BQ.

Can someone reassign the TLEs for a quick test? :slight_smile:

1 Like

The corrected waterfall looks like this:

1 Like

We worked on received signals (out of satnogs network) from ISTANBUL.
in SATNOGS, now we are following TLE 56228 (object BM)


These are some observations (signals captured on ground stations using Vertical antennas)

INFO : The RED dot with date time stamp is the ground station observing.




According the observations (except the last one) Object BQ looks like a better candidate.

Any commentsā€¦

Baris
OH2UDS / TA7W

Unfortunately I can not check in detail, so Iā€™ll change to follow BQ for ISTANBUL

I have been searching without success for any clear observation of the satellite,(Hello Space, Istanbul).
Can you point me some?

Thanks.

Hello Fredy!

I am a member of the AMSAT-EA association.
After conducting several analyses, we have come to the following conclusion: since satellite 56993 appears to be MRC-100, we believe that URESAT-1 could be object 56992. Both were deployed simultaneously, along with ROM-2, which could be object 56994. Based on the initial positions of these objects and their current positions, it seems that they are following the expected trajectory for satellites of these characteristics.

Would it be possible to update the Satnogs database accordingly?

Thank you!
Maria del Mar

2 Likes

@maria welcome in the community!

Thank you for the information!

Iā€™ve changed accordingly in DB for ROM-2 and URESAT-1. MRC-100 is already following the right object and as soon as Iā€™m back in a good internet connection (on Monday) Iā€™ll move to identify it fully in DB. Unfortunately I need to do this as Iā€™m currently the bottleneck on this process, hopefully this will change soon.

Iā€™m not saying that this is the case but letā€™s have in mind the deployment order, especially days after the deployment, can be changed drastically and we have seen this in many cases.

By the way if you can share any of the calculations you made or more details would be great! It is very useful for the community to understand how we analyze the data we have and also to verify and give feedback.

2 Likes