TLE set by @PE0SAT for MRC-100:
MRC-100
1 99182U 23173.79400897 .00000000 00000-0 46840-3 0 07
2 99182 97.5127 290.8733 0014159 177.0273 180.4427 15.13242215 03
3 Likes
According to what was declared in the ITU, the DL frequency of Istanbul should be 402.075 Mhz
2 Likes
At the request of Rony (SATLLA Team), I have added a transmitter suggestion for SATLLA-2I
https://db.satnogs.org/satellite/XDTB-0414-1246-0782-0962#transmitters
… for the GFSK capability that’s included with their satellite’s radio.
These modules are most often used for LoRa, but absolutely support other modes. However, while we normally associate GFSK with FM modulation, previous testing (as well as the code shown below from SATLLA-2I’s programming) indicate that these signals decode when SSB demod is used:
… so, if this suggestion is added to the list of potential transmitters for SATLLA-2I, would it be possible to schedule some SatNogs observations to increase the odds of finding this new satellite?
Thanks!
3 Likes
Good catch, I’ve changed Istanbul transmitter, the future observations will be updated accordingly.
2 Likes
Thanks for adding it, I’m not sure if the coordination is valid for this satellite, as each satellite needs separate coordination with IARU.
I’ll try to schedule some observations and see if we can get anything.
2 Likes
May I ask how many satellites on the rocket have been successfully received so far?
Can list the confirmed satellites for future observations will appreciate…
Thanks
Currently the biggest challenge is identifying, we have multi signals and no idea to what satellite they belong.
Even on Ham radio UHF where this is mandatory, a signal on 436.630 no idea what satellite.
1 Like
New TLE set by @PE0SAT for MRC-100:
MRC-100
1 99182U 23175.10000000 .00000000 00000-0 00000-0 0 01
2 99182 97.5127 292.2526 0007844 177.2573 84.7931 15.13266641 02
EDIT: same TLE with updated epoch
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 | 56957 | - | NO | YES | Deployed, uses TLE set of its deployer when it was deployed |
| 99182 | MRC-100 | - | - | NO | YES | Deployed, uses TLE set generated by SatNOGS Community |
| 99115 | FOSSASAT-FEROX 14 - PlatziSat-1 | - | all | NO | YES | Received according to tinygs |
| 99100 | SpeiSat | 56957 | - | NO | YES | Deployed, uses TLE set of its deployer when it was deployed |
| 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 | |
| 99079 | Transporter 8 Satellite E | 56987 | 56986(unlikely) | NO | YES | No update |
| OBJECT 23084AJ (Transporter 8 Satellite D) | 56964 | - | YES | YES | Identified, here are the ikhnos results | |
| 99081 | Transporter 8 Satellite B | 56962 | 56961(unlikely) | NO | YES | Unknown satellite that seems to follow 56962, received, changed to follow 56962, other possible 56961 |
| RECEPTION STOPPED | ||||||
| 99078 | Transporter 8 Satellite F | 56939 | 56932-56938, 56940-56944 | NO | YES | No reception since 2023-06-15 11:31, changed to follow 56939, other possible 56932-56938, 56940-56944 |
| 99083 | Transporter 8 Satellite A | 56934 | 56932, 56933, 56935 | NO | YES | No reception since 2023-06-16 20:57, changed to follow 56934, other possible 56932, 56933, 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 | 56957 | - | NO | YES | Deployed, uses TLE set of its deployer when it was deployed |
| 99101 | Outpost Mission 0 | 56957 | - | NO | YES | Deployed, uses TLE set of its deployer when it was deployed |
| 99113 | FOSSASAT-FEROX 16 | - | - | NO | YES | |
| 99352 | URESAT-1 | 56957 | - | NO | YES | Deployed, uses TLE set of its deployer when it was deployed |
| 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 | 56957 | - | NO | YES | Deployed, uses TLE set of its deployer when it was deployed |
| 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 |
Can you update it in the scheduler as well? I just re-schedule a few for our station (2380, see e.g. SatNOGS Network - Observation 7759809), but still uses the previous one with a different mean motion (15.13242215 c/d instead of 15.13266641 c/d).
I did and also fix my copy paste error, so now you can see the updated TLE set in the post.
I see, thanks! So does it mean that the mean motion is not changed since yesterday?
Unfortunately the fit wasn’t done for mean motion, this usually needs more than one observations to have better accuracy and in this case the fit was done on one observation. Let’s see if the next hours space-track.org will publish TLE/objects from the ION deployment, if not we can try to fit more than one observations and get mean motion also updated.
EDIT: feel free to join the #satnogs matrix channel where we discuss all these matters
would it help if we make an i/q recording from this? SatNOGS Network - Observation 7760476. The previous high pass (SatNOGS Network - Observation 7752590) was rather good, but there is no i/q saved 
It may help but not sure if it will need some extra process, we perform the fit by using strf tools for observations and fit.
Based on latest @PE0SAT TLE set and some network observations I’ve managed to generate a little better TLE set with mean motion also fitted:
MRC-100
1 99182U 23175.20000000 .00000000 00000-0 00000-0 0 02
2 99182 97.5127 291.3583 0014340 171.7329 273.5804 15.11776647 09
sites.txt (2.6 KB)
mrc_175.dat (2.9 KB)
1 Like
it is interesting that the mean motion decreased quite prominently
1 Like
I think it is normal given that for the initial TLE set we used the one of the ION deployer which has different size and mass.
1 Like