Thanks @satcolintel5, I’m going to use the DODONA EST for DB and Network as the OBJECT Q was there before DODONA deployment.
Do you know if there are any news from the satellite, any reception or communication with it?
1 Like
@satcolintel5 I’m going to remove and re-schedule some of the observations you have scheduled for DODONA as they are too off with the new TLE, feel free to add more.
@satcolintel5 two more requests/suggestions:
- If you can pass to Dave this page Get In Touch - SatNOGS Wiki for being able to join the community and have a more direct communication.
- When you schedule a satellite that isn’t yet identified please use in the advanced options the
Customoption inStation Horizonwith the value0. This will make the station to track from 0 to max to 0 degrees the satellite giving more chances (as we don’t have the right TLE set) to receive the satellite and if receives it to allow us analyze better its orbit and its identification.
EDIT:
The TLE we use now in DB and Network are the ones bellow:
DODONA EST
1 99456U 22032.93673372 .00000000 00000-0 44582-3 0 01
2 99456 97.5062 102.3027 0006687 155.0439 229.8335 15.13288508 06
They are based on the DODONA EST from the previous post but I have used the temporary NORAD ID that we use in DB and also propagate them to 22032.93673372 in order to use these in Network.
1 Like
Nothing definitive communications wise. The DODONA team suspects the bus is power cycling due to a low battery condition from 10 days in cold saturation. Last I heard is they were commanding the satellite into idle mode to conserve/load the battery, assuming that is the problem.
3 New TLE sets for transporter 3 launch from spacetrack, still in TO BE ASSIGNED status:
0 TBA - TO BE ASSIGNED
1 51080U 22002BA 22035.68674627 .00006552 00000-0 35852-3 0 9992
2 51080 97.5245 105.1241 0014003 187.9596 172.1416 15.14509865 3341
0 TBA - TO BE ASSIGNED
1 51085U 22002BF 22035.72158483 .00003427 00000-0 20598-3 0 9998
2 51085 97.5040 105.0144 0015277 167.0277 193.1349 15.11448014 3342
0 TBA - TO BE ASSIGNED
1 51088U 22002BJ 22035.71473689 .00006945 00000-0 39691-3 0 9990
2 51088 97.4983 105.0121 0011026 145.2259 214.9695 15.12956714 3349
It seems that OBJECT BF (51085) describes for now better VZLUSAT-2 signals. cc @vzlu_team
Have in mind that still we are waiting TLE sets for other objects deployed by ION deployer, this means that OBJECT BF may describe more than one satellites.
Thanks to @PE0SAT for helping finding the VZLUSAT-2 fit.
3 Likes
That’s brilliant, @fredy, @PE0SAT thank you very much. So far we’ve been using SatNOGS TLE for LEOP, which seems to still matching OK for most passes (though it is starting to show some drift in high elevations).
2 Likes
One more update according to D-Orbit tweets STORK-2 and SW1FT have been deployed on Feb 2nd and 3rd respectively. They will be available for scheduling in a couple of minutes following ION deployer TLE set.
1 Like
New TO BE ASSIGNED TLE sets by spacetrack, with these we have in total 105 TLE sets, which means that we have TLE sets for all the satellites of this launch:
0 TBA - TO BE ASSIGNED
1 51080U 22002BA 22035.68674627 .00006552 00000-0 35852-3 0 9992
2 51080 97.5245 105.1241 0014003 187.9596 172.1416 15.14509865 3341
0 TBA - TO BE ASSIGNED
1 51081U 22002BB 22035.68703883 .00006692 00000-0 36622-3 0 9991
2 51081 97.5237 105.1214 0014364 187.9504 172.1502 15.14491161 3347
0 TBA - TO BE ASSIGNED
1 51082U 22002BC 22035.70268989 .00010415 00000-0 58427-3 0 9993
2 51082 97.4933 105.0087 0012815 143.7172 216.4931 15.13477948 3341
0 TBA - TO BE ASSIGNED
1 51083U 22002BD 22035.45515426 .00004630 00000-0 27159-3 0 9997
2 51083 97.5018 104.7500 0009913 165.1843 194.9680 15.12203219 3305
0 TBA - TO BE ASSIGNED
1 51084U 22002BE 22035.70936306 .00006494 00000-0 36795-3 0 9996
2 51084 97.5048 105.0321 0008330 148.4454 211.7278 15.13313398 3344
0 TBA - TO BE ASSIGNED
1 51085U 22002BF 22035.72158483 .00003427 00000-0 20598-3 0 9998
2 51085 97.5040 105.0144 0015277 167.0277 193.1349 15.11448014 3342
0 TBA - TO BE ASSIGNED
1 51086U 22002BG 22035.71122306 .00005540 00000-0 31418-3 0 9994
2 51086 97.4976 105.0181 0008329 144.5605 215.6182 15.13349187 3344
0 TBA - TO BE ASSIGNED
1 51087U 22002BH 22035.71767494 .00007130 00000-0 42125-3 0 9992
2 51087 97.5098 105.0267 0014402 164.2040 195.9643 15.11713533 3347
0 TBA - TO BE ASSIGNED
1 51088U 22002BJ 22035.71473689 .00006945 00000-0 39691-3 0 9990
2 51088 97.4983 105.0121 0011026 145.2259 214.9695 15.12956714 3349
Still VZLUSAT-2 fits 51085 better. For the rest satellites there will be updates soon.
4 Likes
Hi,
GRIZU-263 is being monitor by only a few stations according to dashboard (Grafana)
I have 2 questions :
- How can I make all satnogs ground stations to decode packets for Grizu-263 ?
- Why I don’t see any decoded packets beside the waterfall and sound recordings of Grizu-263 observations in network page ?
Thanks
Baris Dinc
OH2UDS/TA7W
Simple really - the packet framing is not one supported by the SatNOGS demodulators.
Nobody has put in the effort to add support to the demodulators. Because this appears to be a custom packet framing format used by a single satellite, it’s unlikely it will ever be added.
So… the packets you are seeing are coming from other sources, such as SIDS forwarders.
1 Like
@fredy it looks like VZLUSAT-2 is now recognized as NORAD 51085 (https://celestrak.com/NORAD/elements/tle-new.txt). So maybe it’s time to drop the temporary ID in SatNOGS DB? Thanks!
@oh2uds as @vk5qi unfortunately the custom framing isn’t currently supported so there are two solutions:
-
To create a new flowgraph in librespacefoundation / SatNOGS / satnogs-flowgraphs · GitLab. However have in mind that this may take some time to be reviewed and tested before hit the production and also it may take some time for all station to be updated to the version that will supported.
-
Another solution is that there are some discussions of integrating gr-satellites in SatNOGS Client and use it for some satellites that gr-satnogs and gr-flowgraphs don’t support. Currently there is support for gr-satellites by adding a pre-observation script but this is a really manual process for the average user to setup, so the next step that you can probably help is to create a better integration of gr-satellites, that will also help future missions too.
@fredy sorry to bother, but would it be possible to change VZLUSAT-2 to the official NORAD ID? I noticed I am able to edit the entry in DB, but I’m not sure if that’s the proper way to do this change, since I would expect it can interfere with scheduling. Thanks!
Piling on with @vzlu_team’s request here … 
can someone add a link to VZLUSAT-2 's telemetry dashboard on DB?
The way it is now, only the link to Network Observations is showing
Thanks much to the SatNOGS team for all you do! Thanks!
This is the way to do it. Remove the NORAD ID to follow, and replace the temporary NORAD ID with the identified one. In citation field add a link to public evidence for this identification, for example an ikhnos or an strf tools observation showing the fit.
1 Like
@satcolintel5 this follow the same process, create a suggestion for adding the dashboard link, you will find the related field by clicking edit at the top right of the satellite page, note that you need to be logged in in DB site first.
2 Likes
OK, will do - thanks for the pointer!
2 Likes
Please @fredy change the NORAD ID of delfi-pq to 51074, some hams
are trying to upload tlm frames to DB using DK3WN tlm fwd without sucess
due this mistake.
1 Like
@LW2DTZ please add a suggestion for it and I’ll review it as soon as possible.
Check here how to do it: