Hello once again,
we have just received a confirmation of deployment of VZLUSAT-2! In about 15 minutes, it should start transmitting beacon!
4 Likes
Very nice signals from VZLUSAT-2 over the U.S. Many decodes even though max elevation was only 26Ā° (which is not great from my location).
3 Likes
No Scott, they are using a GOMSpace AX.100 TRX and Mode 5 is AX100 ASM+Golay framing.
gr_satellites has a yml file and you can try the UZ7HO 1KUNS-PF decoder.
3 Likes
Some FOSSASAT-2Eās have updated TLEās. Still uncertainty on FOSSASAT-2E2 and FOSSASAT-2E3
FOSSASAT2E4 ā 50987 Norad
2022-002D
1 50987U 22002D 22026.90572233 .00008036 00000+0 44823-3 0 9998
2 50987 97.5089 96.3918 0014998 182.9131 177.2015 15.13737523 2014
FOSSASAT2E5 ā 51001 Norad
2022-002T
1 51001U 22002T 22026.90732326 .00007277 00000+0 40855-3 0 9994
2 51001 97.5106 96.3935 0014470 185.3313 174.7766 15.13543473 2019
FOSSASAT2E6 ā 50991 Norad
2022-002H
1 50991U 22002H 22026.90696389 .00006996 00000+0 39249-3 0 9991
2 50991 97.5102 96.3932 0014637 184.5794 175.5306 15.13579900 2011
FOSSASAT2E1 - 50985 Norad or 50990 Norad
2022-002B
1 50985U 22002B 22026.90556357 .00006602 00000+0 36887-3 0 9993
2 50985 97.5089 96.3923 0015146 182.6856 177.4296 15.13741503 2011
1 Like
Iāve changed them in DB and will be updated soon in Network too. Any suggestion for FOSSASAT-2E2 and FOSSASAT-2E3 or we should keep the same we follow now, 51028 and 51079?
VZLUSAT-2 has significantly drifted from ION TLE. I guess, this is the reason for unsuccessful decoding of frames in the past day.
Could anyone fit better TLE, or more time needed for good results?
Anyway, if it helps for fitting, we are saving I/Q dumps of observations at station 2380, feel free to use if it can be useful: Index of /share/satnogs/2380/vzlusat2/
New TLE set for VZLUSAT-2 by @EelkeVisser:
VZLUSAT-2
1 99768U 22027.90854915 .00000000 00000-0 47968-4 0 04
2 99768 97.5058 97.3462 0010792 182.2078 173.1343 15.11408347 09
3 Likes
@EelkeVisser thank you very much for the TLE, it looks like a very good match for now!
We used the generated TLE to estimate a new target for our ground station during this evening pass - it seems very closely aligned with object 51047 (FLOCK 4X-7) or 51049 (FLOCK 4X-9). We think one of these objects was misidentified, and itās actually VZLUSAT-2.
Unfortunately we canāt tell those two apart yet. @fredy would it be possible to use Celestrak TLE of object 51047 for VZLUSAT-2 in SatNOGS? If it starts to drift, then we know VZLUSAT-2 is 51049. If it doesnāt, then we know VZLUSAT-2 is 51047.
No thanks, I am glad I can help a bit!
Tomorrow, I can fit my obs to the two Flock objects, and see if they fit. But are you sure these objects are new? Werenāt they published before your satellite got deployed? Might be worth a check! Space track has published 96 TLEs and there were 105 satellites on the ride. For sure we are missing a few TLEs.
From what Iāve seen, the best match for the calculated TLE at the moment is 51047, followed by 51049. Celestrak has no unidentified objects close to these two. But I guess it is still possible itās missing completely (especially since we were deployed so late).
In the last pass we have been tracking 51047, and observed almost no Doppler shift, with both uplink and downlink working flawlessly. So either weāre that object, or close to it. Weāll see how the Doppler changes over the next couple of days.
@vzlu_team unfortunately none of them is VZLUSAT-2, those TLE sets were published days before VZLUSAT-2 deployment. As @EelkeVisser said, in space-track there are 96 objects for this launch for several days, so letās start checking the new ones that will be published.
I suggest we continue use the TLE set @EelkeVisser has produced and update it with tomorrow fits. Connecting the satellite with one of the current TLE sets which will be updated once or twice per day may create more issues on reception than using the generated one. However I donāt expect big changes in orbit for OBJECTS 51047 and 51049, so itās your call.
Youāre right, I didnāt realize those were deployed so early. In that case letās stick the the generated TLEs and see if space-track publishes anything new.
1 Like
hi, LabSat was released yesterday from the ION according to D-Orbit tweet - https://twitter.com/D_Orbit/status/1487099560069672962. No TLE is available but maybe there is one that you suppose can be connected to this ION deployer (and maybe they would be similar enough)?
3 Likes
@vzlu_team The 51047 is a bad fit, the doppler residu is high 2.7kHz:
The 51049 is even worse, 4.3kHz:
I have updated my previous TLE, but the difference is minor:
New TLE:
VZLUSAT-2
1 99768U 22027.90854915 .00000000 00000-0 47968-4 0 04
2 99768 97.5058 97.3462 0010792 182.2078 173.1300 15.11408564 03
# 20220126.79-20220128.92, 233 measurements, 0.026 kHz rms
1 Like
Thanks for checking, maybe we were using outdated TLE for the 51047 observation yesterday.
Or maybe it fits well on one pass, but not on multiple passes over a couple of days.
Update from Dave @ USCās DODONA team for relay to SatNOGS
we got late word yesterday that NORAD has updated our object, but still not listed it as an official number. It appears we are now way outside the ION traveling pack.
Here are the two TLEās that we are tracking, with the one called DODONA-EST as the one that we just got from NORAD. WE thought Object Q was us, but they donāt exactly match. However I am uncertain if the one called DODONA-EST is up to dateā¦
OBJECT Q
1 50998U 22002Q 22031.87326981 .00007301 00000-0 41743-3 0 9992
2 50998 97.4995 101.2409 0012142 164.3956 195.7652 15.12912791 2765
DODONA EST
1 88353U 22031.67584411 +.00007873 +00000+0 +44582-3 0 0093
2 88353 97.5062 101.0612 0007930 162.0940 198.0572 15.13268839 0273I am not sure how to communicate to Fredy to get either of these to the SatNOGS operatorsā¦
Thanks so much!
Dave
1 Like