thx @PE0SAT TLE for MRC-100 are now added in both DB and Network.
1 Like
Now SpeiSat is close to object #56963
3 Likes
Not bad at all, but maybe this pass can also be used for fine-tuning: SatNOGS Network - Observation 7806109 (let me know if you need the I/Q, i can also revert the Doppler correction)
According to AMSAT-EA, after some calculations and ussing the ATA recording made by Daniel EA4GPZ, the best object candidate for URESAT-1 is the object 56944
56944-URESAT-CANDIDATE
1 56944U 23084N 23184.31318637 .00004915 00000-0 28186-3 0 9992
2 56944 97.5118 300.5985 0012644 141.9980 218.2145 15.12967746 3093
Can you take it in consideration for the Satnogs database? It will help in order to have more accurate observations.
Thanks and 73 de David EA4SG
Thanks for the info @EA4SG!
I would be great if you can share the raw/initial data you have and all the calculations and the analysis that has been done. This could help us verify the results and maybe help further.
Two comments:
- Except if I’m missing something or I get something wrong, OBJECT AJ (56944) specifically and all the current objects published until now, can not be URESAT-1 as the objects were tracked before the deployment of the satellite. Objects well tracked since 20th June, while URESAT-1 and other ION deployed satellites were deployed on 21st or 22nd of June.
- One more reason for OBJECT AJ not being URESAT-1 is that it is already identified as an unknown satellite that transmits at 436.630 MHz, which according to the current info we have, URESAT-1 doesn’t transmit at that frequency.
Having said the above, I’m going to add the TLE set you posted in DB for tracking URESAT-1 but I’m not going to add 56944 to NORAD ID to follow for the satellite as it is going to track the wrong object.
1 Like
Hello Fredy! I am in the SPEI Satelles team. I see that you track SPEI almost every day but lately, you don’t receive good signals (I refer to Observation #7800030). Try using these TLEs
1 88367U 23084AB 23183.57624045 .00007962 00000-0 44036-3 0 00084
2 88367 97.5109 299.8899 0014036 134.7005 225.5372 15.14051111002988
Francesco
3 Likes
Hi @kope and welcome in the community!
I’ve added the TLE you provided in DB, I’ve just changed them to use the temporary NORAD ID we use for SpeiSat:
1 99100U 23084AB 23183.57624045 .00007962 00000-0 44036-3 0 00081
2 99100 97.5109 299.8899 0014036 134.7005 225.5372 15.14051111002985
@kope a quick question if you know, it seems that somehow in the space-track.org catalog OBJECT AC (56958) is identified as SPEI SATELLES, which I guess this is the SpeiSat satellite. If that’s indeed SpeiSat identification can you clarify if your team performed that identification or it was done accidentally from space-track.org?
2 Likes
Thank you @fredy!
There was an issue in identifying the TLEs of the CubeSats released by ION 011 in the Transporter 8 mission. Our Project Manager is currently in contact with Space Track.
Sat.88367 is on the same orbit as Sat.99100 but passing two minutes earlier than it. Since we updated the TLE the tracking has remarkably improved.
Unfortunately we still don’t have any TLE published for the ION deployments, and given that they fit other objects from this launch, my guess is that this makes it difficult to be tracked and separated as different objects and having their own TLE sets. So, we just need to wait for better separation and space-track.org to publish their TLE sets.
@fredy We did an analysis for ISTANBUL, and tried to map signals and ground stations to decide which TLE to use.
Objects J K M and N are possible candidates for us. Object M has the highest possibility, can we try TLE 56943 for ISTANBUL in SATNOGS ?
Thanks
Baris
OH2UDS / TA7W
1 Like
SPEISAT based on the following observations
SPEISAT
1 99100U 23184.59900463 .00000000 00000-0 44036-3 0 06
2 99100 97.5109 302.3092 0013958 130.4637 41.3798 15.14005183 01
And the following IKHNOS check.
2 Likes
@oh2uds I’ve added the current (2023-07-04 22:42) TLE of 56943 for ISTANBUL, however similar to the other ION deployments (check previous posts), I’m not going to add this NORAD ID to the NORAD ID to follow field in DB for ISTANBUL.
MRC-100 based on the following observations:
MRC-100
1 99182U 23186.53081019 .00000000 00000-0 00000-0 0 09
2 99182 97.5127 302.5854 0013672 131.6836 24.1582 15.11936473 08
2 Likes
thanks, works pretty well!
according to observation SatNOGS Network - Observation 7822598 TLE of object M (56943) fits to ISTANBUL…
New 9 TLE sets for this launch, still to be assigned, which should include the ION deployments:
0 TBA - TO BE ASSIGNED
1 56989U 23084BR 23187.29313247 .00014012 00000-0 80653-3 0 9999
2 56989 97.5071 303.5081 0018294 148.9846 211.2469 15.12407351 3548
0 TBA - TO BE ASSIGNED
1 56990U 23084BS 23187.55059366 .00010178 00000-0 57902-3 0 9999
2 56990 97.5115 303.7926 0015549 140.6005 219.6360 15.12949247 3586
0 TBA - TO BE ASSIGNED
1 56991U 23084BT 23187.27720120 .00009477 00000-0 52250-3 0 9993
2 56991 97.5112 303.5407 0013945 123.5185 236.7381 15.14114448 3541
0 TBA - TO BE ASSIGNED
1 56226U 23084BK 23187.60644418 .00006839 00000-0 37882-3 0 9999
2 56226 97.5136 303.8782 0012223 132.2481 227.9789 15.14072386 3594
0 TBA - TO BE ASSIGNED
1 56227U 23084BL 23187.61646608 .00011668 00000-0 65673-3 0 9999
2 56227 97.5150 303.8720 0013544 132.3981 227.8399 15.13321217 3591
0 TBA - TO BE ASSIGNED
1 56228U 23084BM 23187.28626137 .00009185 00000-0 51917-3 0 9995
2 56228 97.5150 303.5455 0013754 133.3929 226.8450 15.13231523 3542
0 TBA - TO BE ASSIGNED
1 56229U 23084BN 23187.28615123 .00005633 00000-0 32027-3 0 9994
2 56229 97.5149 303.5452 0013736 132.2620 227.9778 15.13199493 3548
0 TBA - TO BE ASSIGNED
1 56230U 23084BP 23187.55821230 .00027479 00000-0 15660-2 0 9999
2 56230 97.5133 303.7902 0017412 154.6232 205.5857 15.12631591 3580
0 TBA - TO BE ASSIGNED
1 56231U 23084BQ 23187.56091210 .00008210 00000-0 47869-3 0 9997
2 56231 97.5137 303.7862 0018381 150.7030 209.5235 15.12085990 3589
3 Likes
BQ is pretty close to MRC-100 
In terms of physical distance and in mean motion as well!
1 Like
I’ve updated it in DB for now… I’ll check later to verify 