Earlier today we had the launch of Vega VV19. There are 3 satellites that we are trying to observe, all of them have been added in DB and scheduled in Network with temporary NORAD ID and preliminary TLE sets:
99668 BRO 4
99669 RADCUBE
99670 LEDSAT
1 Like
Bellow are two TLE sets:
RADCUBE
1 69420U 21666AAA 21229.14653935 +.00000000 +00000+0 +00000+0 0 69695
2 69420 097.5470 302.7473 0015700 227.0950 156.8334 15.06633502000000
and from ESA - LEDSAT is launched
LEDSAT
1 00000U 21000ZZZ 21229.14658565 .00000000 00000-0 19534-3 0 18
2 00000 97.4520 302.6160 0009270 219.1400 164.8603 15.07356034000004
First reception of RADCUBE by @zr6aic’s ground station “1089 - ZR6AIC Ground Station”:
https://network.satnogs.org/observations/4588462/
1 Like
First reception of LEDSAT with decoded data by @W7KKE’s ground station 488 - W7KKE :
SatNOGS Network - Observation 4588495
1 Like
LEDSAT transmits now with 9600 baudrate, I’ve changed all the future scheduled observations.
I have received Ledsat using strf:
I have fitted it:
To give the following TLE:
1 99670U 21229.14658565 .00000000 00000-0 19534-3 0 05
2 99670 97.4520 303.4188 0009270 219.1400 165.2308 15.06661500 07
# 20210817.43-20210817.43, 61 measurements, 0.026 kHz rms
BUT, be careful, this is the first time I updated a TLE, so I hope all is well. But I am not sure 
2 Likes
Now also including the second pass:
Gives TLE:
1 99670U 21229.14658565 .00000000 00000-0 19534-3 0 05
2 99670 97.4520 303.6532 0009270 305.6972 76.2293 15.08751303 04
# 20210817.43-20210817.50, 84 measurements, 0.336 kHz rms
Again: no guarantees
3 Likes
@EelkeVisser thanks for the TLE sets, unfortunately we are not going to use them as we have spacetrack TLE sets published. But it would be nice if you can try them and let us know if there is any good match.
0 TBA - TO BE ASSIGNED
1 49066U 21073A 21229.49647919 -.00000065 00000-0 00000+0 0 9994
2 49066 97.5596 303.2465 0028458 243.9426 238.5954 15.08116307 51
0 TBA - TO BE ASSIGNED
1 49067U 21073B 21229.43443056 -.00000064 00000-0 00000+0 0 9994
2 49067 97.5573 303.1888 0026215 253.6711 251.1730 15.07123250 23
0 TBA - TO BE ASSIGNED
1 49068U 21073C 21229.43441899 -.00000064 00000-0 00000+0 0 9998
2 49068 97.5599 303.1892 0026363 253.7700 250.9821 15.07094523 28
0 TBA - TO BE ASSIGNED
1 49069U 21073D 21229.43437531 -.00000064 00000-0 00000+0 0 9997
2 49069 97.5687 303.1827 0028747 253.1229 251.3907 15.07124621 26
We have a decoder and a dashboard now!
Both are not yet validated but the values seem to be plausible. A few assumptions were made as the documentation is, unfortunately, lacking some important informations.
Find the dashboard here: Grafana
Thanks @kerel for jumping in on the work around the dashboard!
2 Likes
I’ve changed the TLE sets we follow in DB and Network for the satellites as stated bellow:
LEDSAT follows 49067
BRO 4 follows 49068
RADCUBE follows 49069
The difference, as expected, is too small to do any identifications and also TLE sets are still TBA(To Be Assigned) and they can change.
OBJECT A with 49066 NORAD ID doesn’t fit the signals we have received, as noted by @cgbsat in the #satnogs channel is leading some seconds and it is probably the main payload of the launch.
1 Like
On most of the RADCUBE observations there is a signal at -15KHz. It looks like it follow the TLE set of 49066 however the match is not accurate. Given that fact, it may be or not from this deployment.
I have created an unknown satellite and scheduled some observations to try track it and maybe find out which satellite is and if it belongs to this launch.
Hi @fredy, I have updated my tle’s and I got slightly newer ones. Then I made a search with rffit and got the expected 4 candidates:
rms limit (kHz): 1
49066 0.511 kHz 435.191058 MHz
49067 0.060 kHz 435.190294 MHz
49068 0.053 kHz 435.190270 MHz
49069 0.048 kHz 435.190248 MHz
Identified 4 candidate(s), best fitting satellite is 49069.
The 49066 is not Ledsat, because it is really different from the other 3. I checked that in the waterfall plot. The other 3 a very close together and have similar small doppler rms errors. It suggests that 49069 is Ledsat, but I think it is too close to call. Maybe @cgbsat has more experience in deciding what is right
Updated, because there was one bad measurement point.
4 Likes
A quick update, I’ll give a more descriptive post later:
BRO 4 is the unknown satellite, so both satellites are now merged to one in DB and Network and follows for now better 44066
RADCUBE seems to follow for now better 44067
LEDSAT seems to follow for now better 44069
As objects are still too close, we don’t have any identification yet. However BRO 4 seems to be more separated from the other objects.
PS As this is the first satellite we merge in DB after the landing of Satellite ID, please report any related issue in Network or DB.
4 Likes
Side note, congratulations to @fredy and other contributors for making the Satellite ID a reality with all those cool functionality for merging and managing satellite entries 
6 Likes
If the animation shown by Ariane Space during the launch is to be believed, the upper stage (AVUM) which deployed all the payloads was essentially non-rotating during deployment of the four CubeSats. The BRO-4 (6U CubeSat) dispenser was pointing in the opposite direction to the dispenser for LEDSAT (1U), SunStorm (2U) and RadCube (3U), so I’d expect OBJECT A 49066 2021-073A to be BRO-4, and OBJECT B, C and D to be the other three. On Celestrak they also have OBJECT E 49070 2021-073E which appears to have an orbit broadly compatible with that expected of the primary payload of VV19, Pléiades Neo 4.
(I have a professional interest, since we built one of the scientific instruments, MAGIC, carried by RadCube).
4 Likes
Your reasoning fits the TLE fitting we have gotten on BRO-4 at the moment.
2 Likes
Hello everyone,
I’ve read all the topic but, finally, could someone give me the working tle lines to track ledsat ?
Which one should we use from the list below ?
1 49066U 21073A 21232.65867489 -.00000065 00000-0 00000-0 0 9993
2 49066 97.5605 306.3570 0028557 231.9725 127.8950 15.08106768 531
2021-073B
1 49067U 21073B 21233.12568247 .00000664 00000-0 48095-4 0 9991
2 49067 97.5599 306.8112 0026682 239.0943 120.7734 15.07140957 583
2021-073C
1 49068U 21073C 21233.12577080 .00000452 00000-0 34118-4 0 9993
2 49068 97.5610 306.8103 0026618 239.1800 120.6869 15.07106415 589
2021-073D
1 49069U 21073D 21233.12585049 .00000481 00000-0 36054-4 0 9991
2 49069 97.5609 306.8096 0026553 239.9032 119.9619 15.07076307 582
PLEIADES NEO 4
1 49070U 21073E 21233.18745750 -.00000153 00000-0 -11987-4 0 9992
2 49070 97.9029 307.1828 0001372 49.8617 310.2747 14.84135027 600
2021-074A
1 49071U 21074A 21233.17994987 .02925193 00000-0 11463+0 0 9995
2 49071 97.4412 237.1406 0010339 250.6837 236.3743 15.22096109 340
2021-074B
1 49072U 21074B 21233.30865954 -.00067298 00000-0 -30212-2 0 9991
2 49072 97.4516 237.2711 0007452 263.6101 212.0158 15.21432995 354
2021-074C
1 49073U 21074C 21233.18875104 .00018437 00000-0 23385-3 0 9999
2 49073 97.4411 237.2517 0131174 4.6756 56.8354 15.49738192 340
2021-074D
1 49074U 21074D 21233.18164024 .00003162 00000-0 15802-3 0 9996
2 49074 97.4529 237.1422 0013314 250.6483 238.2049 15.18123906 322
It is 49069 currently. You can find this by looking up a successful observation and at the bottom of the page the tle is shown:
https://network.satnogs.org/observations/4602084/
1 Like
MANY THANKS for your answer and link !!!
2 Likes
Short update: we received a good documentation from the team around LEDSat and dashboard as well as the decoder are updated now and should show valid data!
2 Likes