SpaceX F9 Transporter-9 - Vandenberg - 2023-11-11 18:47 UTC

Done, is there any way we can credit you and the SatNOGS community for all your help? Who is a good contact for that sort of discussion?

would you like to share this decoder?

1 Like

HADES-D
soundmodem FSK 50 - http://uz7.ho.ua/uresat1.zip
decoder - https://www.amsat-ea.org/app/download/13648764/HADES-D_telemetry_decoder_Windows_v1.21.zip
info - AMSAT EA - Proyecto Sat

6 Likes

For social media, you can mention SatNOGS and/or LSF accounts, we have presence in several platforms. For anything more get in contact through this form and you will be forwarded to the right persons.

By the way suggestion reviewed and accepted, and spoiler alert (a status table with more details for all the satellites is coming) Barry seems to fit one of 58335, 58338, 58339 objects of the list above, for now we are going to follow 58335 until we have a better fit. Reminder that these TLE sets aren’t fully assigned to Objects and maybe change/swap which object they track.

2 Likes

Hi, could we have the deployment update and prelaunch TLE for Albapod-1 deployment plan 09:14UTC today of SpaceANT-D satellite? Thankyou in advance

Danny, SpaceIn

@danny1 you can use the one from this post SpaceX F9 Transporter-9 - Vandenberg - 2023-11-11 18:47 UTC - #188 by fredy or the TLE from space-track or celestrak for the OBJECT 23174AW(58300) at the time of the deployment, as this seems to fit better for the ION SCV-013 deployer. Either case, the TLE will need soon after the deployment an update.

Here are the current fits of the satellites we have received from this launch. Notice that the published TLE sets are still in “TO BE ASSIGNED” status, which means that it is not safe to identify any of them as they may change, or additional objects show up for this launch.

Temporary NORAD ID Satellite NORAD ID to follow Other NORAD IDs Identified Deployed Last Update Notes
RECEIVED AND DEMODULATED
99025 ION SCV-013 58300 58292(unlikely), 58298(unlikely) NO YES Received, changed to follow 58300
99031 Connecta T3.1 58256 NO YES Received, changed to follow 58256
99030 Connecta T3.2 58268 NO YES Received, changed to follow 58268
99010 Barry-1 58335 58337(unlikely), 58338, 58339, 58341(unlikely) NO YES Received, changed to follow 58335, other possible 58337(unlikely), 58338, 58339, 58341(unlikely)
98979 Platform-5 58339 58335, 58337(unlikely), 58338(unlikely), 58341(unlikely) NO YES Received, changed to follow 58339, other possible 58335, 58337(unlikely), 58338(unlikely), 58341(unlikely)
98978 IRIS-C2 58269 NO YES Received, changed to follow 58269
98980 PEARL-1H 58260 58263(unlikely), 58265 NO YES Received, changed to follow 58260, other possible 58263(unlikely), 58265
99009 PEARL-1C 58342 NO YES Received, changed to follow 58342
99052 Veronika 58264 58259(unlikely), 58261 NO YES Received, changed to follow 58264, other possible 58259(unlikely), 58261
99002 BRO-11 58261 58258, 58259, 58260, 58262, 58263, 58264, 58265 NO YES Received(in data contains 03 F3 hex), changed to follow 58261, other possible 58258, 58259, 58260, 58262, 58263, 58264, 58265 Fit check happened on observations 13 days old, so they can be inaccurate
99003 BRO-10 58331 58330(unlikely), 58333, 58334 NO YES Received(in data contains 03 EB hex), changed to follow 58331, other possible 58330(unlikely), 58333, 58334
99028 KAFASAT 58317 58325 NO YES Received, changed to follow 58317
99006 NinjaSat 58341 58337 NO YES Received, changed to follow 58341 other possible 58341 Demodulated by 3rd party tools
98993 Intuition-1 58295 58288 NO YES Received, changed to follow 58295, other possible 58288
98981 HADES-D 58298, 58292(unlikely) NO YES Received, other possible 58298, 58292(unlikely) Demodulated by 3rd party tools, there is a chance none of the current published objects to be this satellite
RECEIVED
99005 Outpost Mission 2 58334 58331(unlikely) NO YES Received, changed to follow 58334 other possible 58331(unlikely) Without decoding it may not be Outpost Mission 2
99027 DJIBOUTI-1A 58266 NO YES Received, changed to follow 58266
99008 Lemur 2 - Mango 2B 58337 58335(unlikely), 58338(unlikely), 58339(unlikely), 58341 NO YES Received, changed to follow 58337, other possible 58335(unlikely), 58338(unlikely), 58339(unlikely), 58341 This could be also Lemur 2 - Mango 2A
99007 Lemur 2 - Mango 2A 58336 58331(unlikely), 58332(unlikely), 58333(unlikely), 58334 NO YES Received, changed to follow 58336 other possible 58331(unlikely), 58332(unlikely), 58333(unlikely), 58334 This could be also Lemur 2 - Mango 2B
98977 Impulse-1 (LEO Express-1) 58301 NO YES Received, changed to follow 58301
98996 ROM-3 58298, 58292(unlikely) NO YES Received, other possible 58298, 58292(unlikely) There is a chance none of the current published objects to be this satellite
3 Likes

Unless I’m mistaken, it appears from testing w/ tonight’s I/Q recording of the first high-elevation HADES-D pass here that this ‘50 baud FSK’ needs to be demodulated as USB. (normally we think of FSK as an FM demod)

This of course means that there is ZERO error for doppler-tracking; not easy until the TLE is confirmed.

But, on the plus side, the downlink was very strong and if/when you get a packet centered perfectly, it does decode w/ that UZ7HO SoundModem for URESAT-1 linked to above.

I’m still trying to work out how to get decodes in GNU Radio, though. Any tips on that appreciated.

4 Likes

Confirmed. Demodulated as USB.
In addition, with the longer data packet I had to do the “AFC” manually in soundmodem because the TLE are not yet accurate.

3 Likes

We identified Veronika as 58621

58261 0.038 kHz 436.679850 MHz
58264 0.142 kHz 436.679718 MHz


3 Likes

@fredy need help to update SpaceANT-D data. We have deployed on 29th at 9.14 UTC. We tried to track tonight in Malaysia but no luck.

3 Likes

The ~30-second interval downlink packets from DJIBOUTI-1A tracked extremely well using Object #58266

2 Likes

You can login in DB site and at the satellite page to hit the edit button at the top right corner to suggest a change. I’ll create one later today if there isn’t one :wink:

1 Like

For anyone w/ LoRa RX capability, I saw the following post that indicates that the -9- Pico-IoT sats were deployed:

https://twitter.com/D_Orbit/status/1729905591508779093

Screenshot from 2023-11-29 20-04-06

… I don’t have all the parameters needed to decode these signals, but if anyone captures an I/Q or audio recording from any of these objects, I would very much appreciate a copy. Thanks!

https://db.satnogs.org/search/?q=pico-1a

-Scott, K4KDR

2 Likes

Hi all, can you guys help track spaceANT-D (98995) deployed 29.11.23 09:14UTC on amatuer UHF 437.425MHz. The signal is in CW Morse Code OOK form.
By the way what is the meaning of “100%overlap” when about to schedule the observation?

1 Like

No sign of anything on a high-elevation pass over the Eastern U.S. around 0315utc tonight; will keep trying!

2 Likes

Hi all, I try to change my launch and deploy date in SatNOGS DB, but it say that I need to fill in the citation. What is citation means? Also, what does it mean when I try to schedule it and it cannot be scheduled as it already overlap?

By the way, does anyone have the updated TLE because we only received this TLE only:
First TLE:

1 99999U 23000XX  23333.38472222  .00000000  00000-0 -29891-4 0  9998
2 99999  97.4824  46.0541 0011000 182.7228  83.4074 15.15203911    07

Second TLE:

1 99999U 23000XX  23333.71458333  .00000000  00000-0 -36394-4 0  9998
2 99999  97.4830  46.3783 0010945 181.7779  81.6299 15.15207030    07

Citation field is the way to track from where the information comes from. Usually is a link to a page that contains the information, for example a tweet from a radio amateur, or the page of a launch provider or a satellite team.

About scheduling, this means that other satellites with similar orbit have already been scheduled on a station. If this is your station you can delete these observations and re-schedule. Usually this happens often when new satellites are deployed from the same launch as they share for the first days/weeks similar orbits. For that reason we are trying (manually for now, automatically in the future) to keep a balance when scheduling new deployments.

For this launch, until we identify (connect satellites with their NORAD ID) the received satellites, I make sure that all satellites get their share on the network and the opportunity to be received. So, you can either leave the scheduling on me, or schedule but make sure you will leave several passes for other satellites. In case of excessive scheduling, I’m going to remove some observations, to allow others to be scheduled.

One last note, my manual handling of this balance isn’t perfect, as it is happened manually and massively but I try to be as fair as possible.

The TLE that was assigned to the satellite, SPACEANT-D, is the one that we had for ION SCV-013 deployer and it works fine even if it is old. To give you an overview here is depicted the FOV of 4 TLE sets:

  1. The one we used for ION-SCV013 and passed to SPACEANT-D
  2. The one that space-track.org has published and fits better ION-SCV013 deployer
  3. and 4. The ones you shared in your post above:

image

Discard the names as this is an issue of the software, as you see all the TLE cover the same area with the difference of some seconds. This means that if satellite is transmitting on the expected frequency, whichever TLE we use station will receive the satellite.

2 Likes

I had described in this post how I perform scheduling.

By the way especially for member from satellite teams, for more quick and active coordination, feel free to join our #satnogs matrix channel, more info can be found in this wiki page.