Observations have been scheduled for GASPACS, FEES-2 and TARGISAT. DAILI transmits at 914 MHz and we don’t have any information about PATCOOL.
EDIT: I’ve scheduled for the first 12 hours using ISS TLE set.
Time schedule verified from nanoracks:
GASPACS has been received by “2107 - JH4XSY-pi” station in SatNOGS Network - Observation 5364832. You can hear the audio at 4:13, some notes from “The Scotsman”, the USU fight song.
2 Likes
There are also some first data by JA1GDE:
1 Like
TARGIT seems also to be alive in observation 5364879 by “500 - SWSU Omnidirectional” station.
Also there is this tweet by @EU1SAT:
1 Like
Heard the voice beacon over northern California and USU team seems to download telemetry or SSDV. See attached waterfall. Same during last pass. That does not seem like 9k6 FSK. Can anyone share what decoder SSDV uses / what modulation this is? Their website only provides a skript to go from binary to image, but its not clear what modulation type / baudrate is used.
I believe it’s still 9k6 packets, just a different payload. Do you have an audio or I/Q recording? I’d love to try to decode what they were streaming!
https://drive.google.com/drive/folders/1gW_dyKQaX9tf0FUXomMaugcc9PKIirXu?usp=sharing
Recorded with HDSDR. The earlier pass was fairly shallow here and the satellite disappeared half way through the transmission. The later one was overhead but there was strong QSB I guess from the satellite tumbling.
1 Like
Thanks very much for the GASPACS recording from that streaming download. I replayed the I/Q recording as well as some very strong audio from other SatNogs observations from Western U.S. passes and the downlink doesn’t resemble the standard 9k6 “Hello World” packets that we received earlier in the mission.
At this point I’m not sure what modulation was being used - or if the radio was functioning properly during that downlink. Will look forward to future passes so we can learn more!
1 Like
Thanks to @EelkeVisser we have a new TLE set for GASPACS. As it is based on few points it will not be perfect but it is much better the the current ones (ISS ones) we used. Also from the same analysis we confirmed the ~1KHz drift of the transmitter that is already added in DB and Network observations.
GASPACS
1 99430U 22027.09835009 .00000000 00000-0 15076-3 0 07
2 99430 51.6452 315.2942 0006921 65.2544 319.5495 15.50136108 06
It is the “EnduroSat Packet Protocol” described on their website! The AX.25 frames are also surrounded with that framing, but fortunately the native decoders like direwolf et al can detect the AX.25 packets inside the EnduroSat packets (located at Data Field 2) without any respect to the outer framing!
3 Likes
New TLE set for GASPACS by @EelkeVisser:
GASPACS
1 99430U 22027.51174303 .00000000 00000-0 14174-3 0 05
2 99430 51.6451 313.2440 0006867 67.2904 106.1030 15.50184441 05
1 Like
Unfortunately no signal from TARGIT since 2022-01-26 20:48:43, the end of the last good observation in Network SatNOGS Network - Observation 5364866. Using the TLE set from GASPACS I’ve updated the TLE of TARGIT in DB and Network as it fits quite well. So for now we follow the TLE set below for TARGIT:
TARGIT
1 99434U 22027.51174303 .00000000 00000-0 14174-3 0 09
2 99434 51.6451 313.2440 0006867 67.2904 106.1030 15.50184441 09
“To Be Assigned TLE” sets from spacetrack:
0 TBA - TO BE ASSIGNED
1 51439U 98067TB 22028.76998445 .00045454 00000-0 78960-3 0 9993
2 51439 51.6427 307.0071 0008871 78.6641 281.5524 15.50327452 385
0 TBA - TO BE ASSIGNED
1 51440U 98067TC 22028.76989760 .00063030 00000-0 10858-2 0 9996
2 51440 51.6427 307.0079 0008871 78.1482 282.0506 15.50422228 443
0 TBA - TO BE ASSIGNED
1 51441U 98067TD 22028.76989221 .00032739 00000-0 57125-3 0 9990
2 51441 51.6425 307.0061 0009159 80.7233 279.4052 15.50354688 435
0 TBA - TO BE ASSIGNED
1 51442U 98067TE 22028.76966943 .00019109 00000-0 33583-3 0 9995
2 51442 51.6415 307.0058 0008995 91.3672 268.8509 15.50482696 398
0 TBA - TO BE ASSIGNED
1 51443U 98067TF 22028.76950443 .00048764 00000-0 83522-3 0 9991
2 51443 51.6438 307.0044 0010530 75.0888 285.1266 15.50677483 353
Still satellites are close, but GASPACS seems to be OBJECT TB (51439). As it started transmitting again, after fixing an issue, we are going in the next hours/days to verify the fit above.
1 Like
GASPACS tracks very closely using object 51439. For some reason I can’t auto-schedule using either 51439 or 99430.
Am I doing something wrong or is not ready for the community to schedule?
Due to the orbit of GASPACS, most of the passes are under the limit of 30 degrees elevation use have set on your station (488). Those that are above 30 degrees are also filtered, as the pass that starts from 30 to XX degrees and ends back to 30 degrees are less than the minimum duration which is 2min for an observation.
Not sure if you can bypass this limit with the auto-scheduler, however you can check and schedule these observations in Sign In with Auth0 by choosing in advanced options custom station horizon. Alternatively if you lower the 30 degrees limit to 20 degrees you will be able to schedule some.
PS There is an issue to be implemented that will allow station owner to choose the start/end elevation of an observation/station, this will help the issue with the 30-XX-30 short duration observations as it will allow you to change the start/end limits, for example to set them to 0 or 20 and have 20-XX-20.
1 Like
Thanks Fredy. I’ll make some adjustments on my elevation limit. It’s frustrating to have passes obscured by trees and terrain to my east while having an unobstructed view to the west over the Pacific.
1 Like
Hey @agregoire3, could you post more information about how the T4RG1T callsign was decoded from the observation we linked? @PE0SAT processed the observation but it only returned packets from Ops-Sat.
By the way, GASPACS has been identified at 51439 and DAILI has been identified as 51443, so TARGIT, PATCOOL, and FEES2 are 51440-51442.
1 Like
When decoding this observation we get the following frame information:
And that is pointing to the satellite OPS-SAT and that is indeed also using 437.200 also.
-> Packet from 9k6 FSK downlink
Container:
header = Container:
addresses = ListContainer:
Container:
callsign = u'DP0ESA' (total 6)
ssid = Container:
ch = False
ssid = 0
extension = False
Container:
callsign = u'DP0OPS' (total 6)
ssid = Container:
ch = False
ssid = 0
extension = True
control = 0x03
pid = 0xF0
info = b"5\xef\xce\xc0\x9bQq\xe1q\x8eoZ\xa7\xb7\xd6\x8aZ\x97}\xd82\xeaOy\n\x10\xf1J\x96\xc9\x8c\xb1\xfe\x91\x1d\xbc\x8bc\x82\x86\x8fX&Q\xf9>\x8d\x9c\xe32N-3\x99~l\xcb\xa5\xe7R\x9f\xd8\xab\xdf\xf0\xdb,\xf8\xbf\xb7\xc0\xe2'\x94\xac\xd8\x9a_s\x8a\xf6\x97\xa5\x16\xfa\xbc\xe7\xbb\xfb\xbd\x8a8\x10\xa9" (total 94)
Maybe you can share some data to do further analyses.
2 Likes