FYI, another ‘late deploy’ sat has gone active - I believe from the ION SCV-008 launcher.
Got a good decode from FUTURA-SM1 tonight on 436.700 LoRa. So, if anyone sees a quick 125 KHz burst in their waterfalls around 436.700, it may be the LoRa downlink from that satellite.
.
Dear all,
We have updated TLE of TAUSAT-2 from space-track:
1 55073U 23001BS 23018.80620439 .00014072 00000-0 77147-3 0 9995
2 55073 97.5036 80.6851 0017964 144.8551 215.3869 15.14154824 2455
I’ve updated TAUSAT-2 in DB to follow 55073. @dovelbas is this choice based on received data/observations or something else?
It is based on updates from the SSA sharing coordinator confirming they detected our satellite and followed it.
In Observation 7049342 we see that EPIC CHIMERA LEO 1, or whatever the object received in this observation is, is running early with respect to our TLE for EPIC CHIMERA LEO 1. Yesterday I created an updated TLE, see this post:
1 43835U 23014.20174576 .00000000 00000-0 64271-3 0 01
2 43835 97.4849 91.1717 0013590 170.1455 275.1811 15.14212796 06
# 20230118.44-20230118.44, 74 measurements, 0.026 kHz rms
Ikhnos confirms that this is a better match (although already a bit late now):
I suggest to use this TLE for EPIC CHIMERA LEO 1 until there is a better identification with a space-track object or an updated TLE from us, otherwise we risk loosing this object.
@kerel have you checked the newer TLE sets posted above against this waterfall?
Also it sounds not a good idea to follow an object that doesn’t belong to this launch as it seems to be a coincidence that the TLE fit.
if you have evidence that the object 43835 follows the orbit of the objects of this launch then we can try it, however we have TLE for almost all the objects so probably it would be better to follow one of them even if it doesn’t fit 100%.
TLE sets are still 95, reminder that the total of the payloads were 114, from which initially to be deployed were 82 and from them only 78 were confirmed. Here are the latest updates:
| Satellite Identifier | Satellite Name | NORAD ID to Follow | Other Possible NORAD IDs | Notes |
|---|---|---|---|---|
| DELH-6722-1461-1897-7938 | Sharjahsat-1 | 55032 | 55033 | Received and changed to follow OBJECT Z(51032), removed 55039, 55040, 55042, 55044 |
| NJFB-9884-9643-7739-4519 | BDSAT-2 | 55098 | 55103 | Received, removed 55038, 55094, 55095 |
| NJEX-6170-8600-1975-0468 | ION SCV-007 | 55051 | - | Received and for now only OBJECT AU(55051) fits |
| VPUU-7194-1121-2414-5647 | ION SCV-008 | 55060 | 55014-55021(unlikely) | Received and changed to follow OBJECT BD(55060), removed 55033 |
| RJCF-5779-9216-5641-4111 | BRO-8 | 55011 | - | Received and for now only OBJECT C(55011) fits |
| PDVW-9191-3063-9872-9368 | Vigoride-5 | 55036 | all the rest | No update |
| KCKF-9169-8304-1813-6974 | Platform-2 | 55067 | 55080, 55082(unlikely), 55083 | Received, removed 55077-55079, 55081 |
| TVZK-1463-5590-8994-0377 | Connecta T1.2 | 55012 | - | Received and for now only OBJECT D(55012) fits |
| LSZR-8461-9828-5431-6212 | Star Vibe | 55009 | all the rest | Not (recently) received, OBJECT A(55009) is chosen based on this tweet |
| JRGY-1674-7223-5551-1972 | TAUSAT-2 | 55073 | 55071, 55072(unlikely) | Received and set to follow OBJECT BS(55073) fits |
An update about Platform-2. We are not sure if the received signal belongs indeed to Platform-2 satellite or to something else. It needs further investigation and maybe some feedback from its team.
No, I haven’t (no automation for this here yet and 95 is just too many for a side task).
Agreed! From this other thread I took for granted that the transmission / the object fitted by the TLE I posted is EPIC CHIMERA, but as we still did not get a confirmation from the satellite team that this is a transmission by their satellite this assumption is to be rejected.
TAUSAT-2 55073
37502 0.760 kHz 436.398865 MHz
47461 0.282 kHz 436.400418 MHz
47617 0.439 kHz 436.399469 MHz
48297 0.869 kHz 436.398574 MHz
49233 0.307 kHz 436.400105 MHz
52484 0.723 kHz 436.399483 MHz
53428 0.601 kHz 436.399132 MHz
55073 0.180 kHz 436.400091 MHz
55075 0.651 kHz 436.401064 MHz
Identified 9 candidate(s), best fitting satellite is 55073
TLE sets are still 95, reminder that the total of the payloads were 114, from which initially to be deployed were 82 and from them only 78 were confirmed. Here are the latest updates:
| Satellite Identifier | Satellite Name | NORAD ID to Follow | Other Possible NORAD IDs | Notes |
|---|---|---|---|---|
| DELH-6722-1461-1897-7938 | Sharjahsat-1 | 51026 | 55022(unlikely), 55024, 55025(unlikely), 55027, 55029(unlikely) | Received and changed to follow OBJECT T(51026), removed 55032, 55033 |
| NJFB-9884-9643-7739-4519 | BDSAT-2 | 55098 | 55103(unlikely) | Received - no update |
| NJEX-6170-8600-1975-0468 | ION SCV-008 | 55051 | - | Received - no update* |
| VPUU-7194-1121-2414-5647 | ION SCV-007 | 55060 | - | Received and for now only 55060 fits, removed 55014-55021* |
| RJCF-5779-9216-5641-4111 | BRO-8 | 55011 | - | Received - no update |
| PDVW-9191-3063-9872-9368 | Vigoride-5 | 55056 | all the rest | Not (recently?) received, changed according to space-track.org |
| KCKF-9169-8304-1813-6974 | Platform-2 | 55067 | 55080, 55082(unlikely), 55083 | Not (recently?) received, not sure if the object we follow is the right until we confirm previous receptions were from the satellite |
| TVZK-1463-5590-8994-0377 | Connecta T1.2 | 55012 | - | Received - no update |
| LSZR-8461-9828-5431-6212 | Star Vibe | 55009 | all the rest | Not (recently) received, OBJECT A(55009) is chosen based on this tweet |
| JRGY-1674-7223-5551-1972 | TAUSAT-2 | 55073 | 55074(unlikely), 55075(unlikely) | Received, removed 55071, 55072 |
*According to space-track.org, it looks like that we thought that ION SCV-007 was ION SCV-008 and vice versa. So, I updated the names in DB and Network as well as in the table above.
Just to confirm… this was at the frequency we have in DB right?
Yes, frequency 437.025 MHz
SHARJAHSAT-1 Now looks like an object #55022 (OBJECT P)
https://twitter.com/EU1SAT/status/1617464303770304513
Indeed, I’ve re-checked one of our latest and it seems that this is the satellite as all the others don’t fit very well. So, I’ve changed in DB and Network, however let’s wait some more days before any final identification.
Here is the checked observation with ikhnos that show the 55022 fit:
EDIT: interesting that this object has been identified in space-track celestrak(in space-track is still unidentified) as one of the LEMURs, let’s see if it was a mis-identification or not.
Also we expect soon the team to increase the rate of the transmitted signals, this will make the identification easier.
After some checking by @PE0SAT on the current published TLE sets against the Sharjahsat-1 reception, we have ended up that we don’t have an object for that satellite published yet.
This is why we return back to generate our own TLE sets and use them instead of following any of the current objects. So, the latest TLE for Sharjahsat-1, generated by @PE0SAT is this:
1 99204U 23022.58575511 .00000000 00000-0 48289-3 0 07
2 99204 97.5005 84.3763 0012285 145.6443 211.7230 15.12572575 04
It is based on the 55022 objects fitted on the latest strf observation:
