Falconsat-10 (or Falconsat-X) identified and still a match 7 days after the first identification 
and
3 Likes
New TLE set for HADES-D:
HADES-D
1 98981U 23346.40000000 .00000000 00000-0 33474-3 0 04
2 98981 97.4806 58.8624 0001818 148.1468 97.3213 15.14360857 09
hadesd_346.dat (3.2 KB)
sites.txt (5.0 KB)
3 Likes
As we didnāt have any luck with ROM-3 following 58340 Object, Iāve changed its TLE to the one of the HADES-D above. They deployed together so maybe there is a better chance if ROM-3 is transmitting, to receive by using HADES-D TLE than other random objects from this launch.
ROM-3
1 98996U 23346.40000000 .00000000 00000-0 00000-0 0 06
2 98996 97.4806 58.9278 0002211 148.1468 97.1638 15.14405437 02
1 Like
New status update:
| Temporary NORAD ID | Satellite | NORAD ID to follow | Other NORAD IDs | Identified | Deployed | Last Update | Notes |
|---|---|---|---|---|---|---|---|
| RECEIVED AND DEMODULATED | |||||||
| - | Connecta T3.1 | 58256 | - | YES | YES | Identified, here are the ikhnos results | |
| - | Connecta T3.2 | 58268 | - | YES | YES | Identified, here are the ikhnos results | |
| - | Barry-1 | 58338 | - | YES | YES | Identified, here are the ikhnos results | |
| - | IRIS-C2 | 58269 | - | YES | YES | Identified, here are the ikhnos results | |
| - | PEARL-1C | 58342 | - | YES | YES | Identified, here are the ikhnos results | |
| - | Veronika | 58261 | - | YES | YES | Identified, here are the ikhnos results | |
| - | KAFASAT | 58317 | - | YES | YES | Identified, here are the ikhnos results | |
| - | BRO-11 | 58264 | - | YES | YES | Identified, here are the ikhnos results | |
| - | BRO-10 | 58331 | - | YES | YES | Identified, here are the ikhnos results | |
| - | DJIBOUTI-1A | 58266 | - | YES | YES | Identified, here are the ikhnos results | Demodulated by 3rd party tools |
| - | ION SCV-013 | 58300 | - | YES | YES | Identified, here are the ikhnos results | |
| - | Platform-5 | 58339 | - | YES | YES | Identified, here are the ikhnos results | |
| 98993 | Intuition-1 | 58284 | 58291 | NO | YES | Received, changed to follow 58284, other possible 58291 removed 58283, 58286 | From the latest status updates it looks like that none of the current published objects is this satellite |
| 98981 | HADES-D | - | - | NO | YES | Received, changed to follow generated TLE from SatNOGS | Demodulated by 3rd party tools, none of the current published objects is this satellite |
| 98980 | PEARL-1H | 58265 | - | NO | YES | Received, continue to follow 58265 | Not received since 2023-12-03 14:04:19 |
| 99006 | NinjaSat | 58341 | 58335(unlikely), 58339(unlikely) | NO | YES | Received, continue to follow 58341 other possible 58335(unlikely), 58339(unlikely) | Demodulated by 3rd party tools, not received since 2023-12-01 21:51:48 |
| RECEIVED | |||||||
| - | Outpost Mission 2 | 58334 | - | YES | YES | Identified, here are the ikhnos results | Without decoding it may not be Outpost Mission 2, identification is based on the fcc.gov granted frequency |
| - | Impulse-1 (LEO Express-1) | 58301 | - | YES | YES | Identified, here are the ikhnos results | |
| 99008 | Lemur 2 - Mango 2B | 58337 | 58335(unlikely, maybe other Lemur satellite?) | NO | YES | Received, continue to follow 58337 | This could be also Lemur 2 - Mango 2A |
| 99007 | Lemur 2 - Mango 2A | 58336 | - | NO | YES | Received, continue to follow 58336, removed 58331 | This could be also Lemur 2 - Mango 2B |
| 98996 | ROM-3 | - | - | NO | YES | Randomly changed to follow HADES-D TLE, removed 58340 | None of the current published objects is this satellite, we choose to follow HADES-D TLE |
| 99004 | ProtoMƩthƩe-1 | 58305 | all(non-identified) | NO | YES | Maybe received, randomly changed to follow 58305, removed 58321 | we choose 58305 per some indications in this observation |
| NOT RECEIVED | |||||||
| 99060 | HERON Mk. II | NO | YES | ||||
| 98995 | SPACEANT-D | NO | YES | ||||
| NOT DEPLOYED | |||||||
| 99026 | JINJUSat-1 | NO | NO | Probably not deployed | |||
| 99000 | AMAN-1 | NO | NO | Probably not deployed | |||
| 98997 | Picacho | NO | NO | Probably not deployed |
The 1k2 downlink from ION_SCV-013 is extremely strong on 401.415 MHz, but the pass over the U.S. East Coast around 0316utc on 13-Dec-2023 was around 3-minutes ahead of the TLE in Celestrak. So, I donāt know if the TLE is bad or 58300 is not this satellite.
1 Like
Can you check if the signal could be on of the rest ION deployers? Where they in your field of view at that time?
Iāve seen several in SCV-013 observations from time to time. Also I donāt expect any important change on TLE sets, however it wouldnāt be the first time weāve seen one. Finally in the latest observations in Network I havenāt seen any SCV-013 signal, so we need to check.
There are 13 new TBA TLE sets from space-track.org, so now we have 100 from the 113 expected ones:
0 TBA - TO BE ASSIGNED
1 58343U 23174CR 23346.72039625 .00028896 00000-0 14420-2 0 9998
2 58343 97.4801 59.2082 0007811 141.0445 219.1353 15.17437673 5290
0 TBA - TO BE ASSIGNED
1 58344U 23174CS 23346.72256340 .00025458 00000-0 12812-2 0 9998
2 58344 97.4803 59.2056 0008127 140.9083 219.2739 15.17166019 5293
0 TBA - TO BE ASSIGNED
1 58345U 23174CT 23347.18220880 .00037090 00000-0 18474-2 0 9995
2 58345 97.4799 59.6640 0007844 139.1095 221.0728 15.17447187 5364
0 TBA - TO BE ASSIGNED
1 58563U 23174CU 23346.45677985 .00028266 00000-0 14125-2 0 9992
2 58563 97.4806 58.9480 0007735 141.5004 218.6783 15.17395179 5259
0 TBA - TO BE ASSIGNED
1 58564U 23174CV 23346.78717940 .00029592 00000-0 14798-2 0 9994
2 58564 97.4802 59.2728 0007873 139.8411 220.3405 15.17359646 5306
0 TBA - TO BE ASSIGNED
1 58565U 23174CW 23346.75258955 .00007445 00000-0 40886-3 0 9999
2 58565 97.4788 59.1585 0014748 155.6119 204.5814 15.14320840 5297
0 TBA - TO BE ASSIGNED
1 58566U 23174CX 23346.07730115 .00016703 00000-0 86870-3 0 9998
2 58566 97.4810 58.5322 0013520 141.2026 219.0180 15.16047051 5199
0 TBA - TO BE ASSIGNED
1 58567U 23174CY 23346.61928789 .00016060 00000-0 87351-3 0 9996
2 58567 97.4811 59.0368 0015846 162.1812 197.9979 15.14437972 5277
0 TBA - TO BE ASSIGNED
1 58568U 23174CZ 23347.14815047 .00016459 00000-0 89630-3 0 9992
2 58568 97.4808 59.5555 0016113 159.2143 200.9747 15.14385991 5348
0 TBA - TO BE ASSIGNED
1 58569U 23174DA 23346.74917641 .00026046 00000-0 13969-2 0 9995
2 58569 97.4809 59.1682 0015268 162.6718 197.5038 15.14842507 5292
0 TBA - TO BE ASSIGNED
1 58570U 23174DB 23346.34118288 .00005162 00000-0 27550-3 0 9991
2 58570 97.4781 58.7802 0010203 143.6196 216.5732 15.15530797 5227
0 TBA - TO BE ASSIGNED
1 58571U 23174DC 23347.13589408 .00006113 00000-0 32368-3 0 9996
2 58571 97.4828 59.5820 0016155 161.1508 199.0326 15.15674279 5344
0 TBA - TO BE ASSIGNED
1 58572U 23174DD 23347.13724577 .00016655 00000-0 87857-3 0 9990
2 58572 97.4809 59.5660 0013650 141.1346 219.0870 15.15545861 5342
Great idea!
My decodes were from 03:13:58 to 03:17:02. Here are all the IONās in Celestrak at those two times.
.
ION_SCV-013 (if it was the transmitter heard) was well past me by that 03:17:02 point in contast with the position shown hereā¦ not even at the point of closest approach yet.
None of the other IONās appear to have been in position to deliver the packets observed.
Reviewing a few of the recent āObservationsā for ION_SCV-013, there are very strong signals in the waterfalls but with wild, non-linear plots which I suppose means they were not utilizing an accurate TLE for the transmitted signals being heard.
1 Like
A quick status update with the new TLE sets for the satellites that couldnāt fit to any of the existent ones. Note that as TLE are still in TBA status we will need to wait for identification:
| Temporary NORAD ID | Satellite | NORAD ID to follow | Other NORAD IDs | Identified | Deployed | Last Update | Notes |
|---|---|---|---|---|---|---|---|
| RECEIVED AND DEMODULATED | |||||||
| 98993 | Intuition-1 | 57565 | 58284(unlikely), 58291(unlikely) | NO | YES | Received, changed to follow 57565, other possible 58284(unlikely), 58291(unlikely) | |
| 98981 | HADES-D | 58567 | 57568(unlikely) | NO | YES | Received, changed to 58567, other possible 57568(unlikely) | Demodulated by 3rd party tools |
| RECEIVED | |||||||
| 98996 | ROM-3 | 57568 | all | NO | YES | Randomly changed to follow 57568 | we choose to follow 57568 as it is the nearest to object 58567 which is probably HADES-D, other objects near 58567 are objects 57569, 57565 |
@K4KDR It is very confusing on the ION observations, Iām not sure what happens:
Iāve checked two of them with ikhnos:
The only objects that are close to the signal on both of them are objects 58317 and 58330, however both are far from saying that are fits.
Iāve also checked them against known objects in DB near this frequency (other ION deployers and satellites) and none of them fits.
My assumption/guess for now, if nothing goes wrong with the TLE from space-track.org for SCV-013 and if it hasnāt changed orbit (I think it has thrusters and can change its orbit), then we may have at least two different satellites that we donāt track in DB near IONās frequency.
If I find some free time, Iāll try to do a couple more checks.
I suppose that itās going to be some other satellite on or near 401.415 MHz that happens to be using 1k2 AX.100.
On the pass just ended here around 1630utc (13-Dec-2023), those strong packets were several minutes BEHIND ION_SCV-013:
ā¦ in fact, I was still getting decodes when ION_SCV-013 was LOS here. The āIONā that was most closely centered on the capture of these packets was ION-MK01 which is listed on a different frequency and I see from a couple of recent observations that the HEX decode of its packets is quite different than I am getting here.
ā¦ so, Iāll stop uploading these decodes as ION_SCV-013 and will try to make time to run these I/Q files through STRF to see if they match up with something else that happens to match this downlink freq and mode.
By chance is the SatNogs catalog of tracked objects searchable by frequency, frequency-range, mode, raw hex decode patterns, etc?
2 Likes
You can search in the transmitters page, adding frequency in the search field will filter the entries. Just have in mind that if this signal is the same with the one we have in Networkās observations then probably isnāt in the DB.
Thank you so much - what a great resource!!
Sorted by baud rate, there are a limited number in the area of 401.4xx MHz using 1k2 baud. Very interesting!
1 Like
High pass of HADES-D over the U.S. East Coast just now; downlink clearly visible but no indication that it was hearing me on the FM Voice uplink.
Does anyone know if the voice repeater is enabled all the time at this point?
2 Likes
Hi,
the repeater is still being tested so it is not enabled all the time. When the tests are finished iIt will be. It will be announced in Twitter @AmsatSpain
FĆ©lix EA4GQS
3 Likes
With the new TLE assigned, we have this new status update with a couple new identifications:
| Temporary NORAD ID | Satellite | NORAD ID to follow | Other NORAD IDs | Identified | Deployed | Last Update | Notes |
|---|---|---|---|---|---|---|---|
| RECEIVED AND DEMODULATED | |||||||
| - | Connecta T3.1 | 58256 | - | YES | YES | Identified, here are the ikhnos results | |
| - | Connecta T3.2 | 58268 | - | YES | YES | Identified, here are the ikhnos results | |
| - | Barry-1 | 58338 | - | YES | YES | Identified, here are the ikhnos results | |
| - | IRIS-C2 | 58269 | - | YES | YES | Identified, here are the ikhnos results | |
| - | PEARL-1C | 58342 | - | YES | YES | Identified, here are the ikhnos results | |
| - | Veronika | 58261 | - | YES | YES | Identified, here are the ikhnos results | |
| - | KAFASAT | 58317 | - | YES | YES | Identified, here are the ikhnos results | |
| - | BRO-11 | 58264 | - | YES | YES | Identified, here are the ikhnos results | |
| - | BRO-10 | 58331 | - | YES | YES | Identified, here are the ikhnos results | |
| - | DJIBOUTI-1A | 58266 | - | YES | YES | Identified, here are the ikhnos results | Demodulated by 3rd party tools |
| - | ION SCV-013 | 58300 | - | YES | YES | Identified, here are the ikhnos results | |
| - | Platform-5 | 58339 | - | YES | YES | Identified, here are the ikhnos results | |
| - | Intuition-1 | 58565 | - | YES | YES | Identified, here are the ikhnos results | |
| - | HADES-D | 58567 | - | YES | YES | Identified, here are the ikhnos results | |
| - | PEARL-1H | 58265 | - | YES | YES | Identified, here are the ikhnos results | |
| 99006 | NinjaSat | 58341 | 58335(unlikely), 58339(unlikely) | NO | YES | Received, continue to follow 58341 other possible 58335(unlikely), 58339(unlikely) | Demodulated by 3rd party tools, not received since 2023-12-01 21:51:48 |
| 58297, 58300, 58308, | |||||||
| RECEIVED | |||||||
| - | Outpost Mission 2 | 58334 | - | YES | YES | Identified, here are the ikhnos results | Without decoding it may not be Outpost Mission 2, identification is based on the fcc.gov granted frequency |
| - | Impulse-1 (LEO Express-1) | 58301 | - | YES | YES | Identified, here are the ikhnos results | |
| 99008 | Lemur 2 - Mango 2B | 58337 | - | NO | YES | Received, changed to follow 58337, identified in space-track.org | |
| 99007 | Lemur 2 - Mango 2A | 58335 | - | NO | YES | Received, changed to follow 58335, identified in space-track.org | |
| 99007 | Lemur 2 - JK0903EM1407 | 58336 | - | NO | YES | Received, changed to follow 58336, identified in space-track.org | |
| 98996 | ROM-3 | 58568 | all | NO | YES | Randomly changed to follow 58568 | we choose to follow 58568 as it is the nearest to object 58567 which is probably HADES-D, other objects near 58567 are objects 58569, 58565 |
| 99004 | ProtoMƩthƩe-1 | 58305 | all(non-identified) | NO | YES | Maybe received, randomly changed to follow 58305, removed 58321 | we choose 58305 per some indications in this observation |
| NOT RECEIVED | |||||||
| 99060 | HERON Mk. II | NO | YES | ||||
| 98995 | SPACEANT-D | NO | YES | ||||
| NOT DEPLOYED | |||||||
| 99026 | JINJUSat-1 | NO | NO | Probably not deployed | |||
| 99000 | AMAN-1 | NO | NO | Probably not deployed | |||
| 98997 | Picacho | NO | NO | Probably not deployed |
1 Like
It gets confusingā¦
Does the āLemur 2 NANAZā satellite referenced in todayās announcement refer to one that weāre already tracking, or some additional object? Thanks!
1 Like
I donāt think is one of these we track, by maybe Iām wrong. We need to check again the names the quantity.
To be honest, my impression was that LEMUR 2 NANAZ was already deployed. Wondering if this wasnāt the case or if the announcement is delayed. Anyway, Iāll check the next days, letās keep an eye.
1 Like
