GREENCUBE
1 99382U 22194.64092593 .00000000 00000-0 00000-0 0 00
2 99382 70.1560 77.2934 0004386 6.3300 251.8144 6.42724700 04
# 20220713.71-20220713.76, 18 measurements, 0.025 kHz rms
These TLEs have been update for Mean Anomaly and are based on @cgbsat’s excellent pre-launch TLEs as shared in this thread. Thanks @fredy and all Satnogs members for all your help!
Doppler measurements from 5 passes of GREENCUBE over the Netherlands during the last 24h allow fitting a circular orbit from scratch.
The resulting TLE should also be valid for ASTROBIO, MTCUBE-2 and CELESTA and should be valid for the next few days.
1 99382U 22195.19609200 .00000000 00000-0 00000-0 0 00
2 99382 70.2449 77.4813 0001000 0.0000 102.0772 6.42625289 03
# 20220713.72-20220714.67, 79 measurements, 0.030 kHz rms
Based on the TLE above here are for all of them:
ASTROBIO
1 99385U 22195.19609200 .00000000 00000-0 00000-0 0 03
2 99385 70.2449 77.4813 0001000 0.0000 102.0772 6.42625289 06
MTCUBE 2
1 99384U 22195.19609200 .00000000 00000-0 00000-0 0 02
2 99384 70.2449 77.4813 0001000 0.0000 102.0772 6.42625289 05
CELESTA
1 99383U 22195.19609200 .00000000 00000-0 00000-0 0 01
2 99383 70.2449 77.4813 0001000 0.0000 102.0772 6.42625289 04
GREENCUBE
1 99382U 22195.19609200 .00000000 00000-0 00000-0 0 00
2 99382 70.2449 77.4813 0001000 0.0000 102.0772 6.42625289 03
TRISAT-R
1 99381U 22195.19609200 .00000000 00000-0 00000-0 0 09
2 99381 70.2449 77.4813 0001000 0.0000 102.0772 6.42625289 02
ALPHA
1 99380U 22195.19609200 .00000000 00000-0 00000-0 0 08
2 99380 70.2449 77.4813 0001000 0.0000 102.0772 6.42625289 01
DB and Network have been updated.
I followed the same approach as @cgbsat and measured the doppler on a few passes of CELESTA and MTCube 2. I have checked the previous TLEs based on GREENCUBE, but fitting the orbits from scratch gives some improvement.
For CELESTA the TCA changed to 25 seconds later and the rms from 52 to 24 Hz.
CELESTA
1 99383U 22195.19827300 .00000000 00000-0 50000-4 0 03
2 99383 69.8100 78.3165 0001000 0.0000 106.6194 6.42327089 07
# 20220713.72-20220714.68, 191 measurements, 0.024 kHz rms
For MTCube 2 the TCA changed to 13 seconds later and the rms from 43 to 21 Hz.
MTCube 2
1 99384U 22195.19800000 .00000000 00000-0 50000-4 0 02
2 99384 69.6195 78.4573 0001000 0.0000 106.0086 6.42458229 09
# 20220713.71-20220714.68, 316 measurements, 0.021 kHz rms
The differences with TLE of the previous message are small. But as the cubesats where deployed in 4 different directions, it can become meaningful to use separate orbits for them.
Edit: Changed the Epoch of MTCube-2 to a little later to make it the most recent.
An updated TLE set for GREENCUBE by @ve7til:
1 99382U 22196.10639840 .00000000 00000-0 00000-0 0 05
2 99382 70.1732 77.0216 0006127 290.9617 116.8621 6.42613335 04
By the way there are two new objects in space-track.org:
0 TBA - TO BE ASSIGNED
1 53105U 22080A 22196.10639840 -.00000006 00000-0 00000+0 0 9993
2 53105 70.1438 76.8159 0006030 290.9617 97.9334 6.38951669 95
0 TBA - TO BE ASSIGNED
1 53106U 22080B 22196.15422608 -.00000003 00000-0 00000+0 0 9998
2 53106 70.2286 76.7835 0090136 81.7947 75.5415 6.42090940 93
However it seems that they describe LARES 2 and the upper stage, so for now we are not going to use/following them for the cubesats.
Also an update by @ve7til for CELESTA:
CELESTA
1 99383U 22196.10639840 .00000000 00000-0 00000-0 0 06
2 99383 69.9954 77.1458 0006030 290.9617 116.5278 6.42846405 00
We have several To Be Assigned(TBA) TLE sets by space-track.org:
0 TBA - TO BE ASSIGNED
1 53105U 22080A 22196.71990961 -.00000008 00000-0 00000-0 0 9997
2 53105 70.1453 76.6157 0005732 284.2863 75.7348 6.38963337 145
0 TBA - TO BE ASSIGNED
1 53106U 22080B 22197.17516350 -.00000003 00000-0 00000+0 0 9999
2 53106 70.1484 76.4700 0008627 239.1254 120.8542 6.42580555 163
0 TBA - TO BE ASSIGNED
1 53107U 22080C 22196.31595537 -.00000003 00000-0 00000+0 0 9999
2 53107 70.1247 76.7799 0016951 257.6053 272.3612 6.42318967 14
0 TBA - TO BE ASSIGNED
1 53108U 22080D 22196.31309310 -.00000003 00000-0 00000+0 0 9992
2 53108 70.1286 76.7757 0020803 272.6022 251.0628 6.42729319 14
0 TBA - TO BE ASSIGNED
1 53109U 22080E 22197.17503805 -.00000003 00000-0 00000+0 0 9993
2 53109 70.1440 76.2786 0009039 242.7869 117.1894 6.42583738 53
0 TBA - TO BE ASSIGNED
1 53110U 22080F 22197.33090933 -.00000003 00000-0 00000+0 0 9996
2 53110 70.1431 76.4212 0007084 229.9832 129.9576 6.42470889 67
An analysis by @cgbsat discussed in the matrix channel, give us these results:
99381 TRISAT-R 435.613MHz 53107 0.075kHz
99382 GREENCUBE 435.310MHz 53106 0.044kHz or 53109 0.044kHz
99383 CELESTA 436.500MHz 53106 0.040kHz or 53109 0.041kHz
99384 MTCube 2 436.750MHz 53106 0.017kHz or 53109 0.018kHz
99385 ASTROBIO 435.600MHz 53107 by Scott Tilley
I’ve updated DB and Network and now we have:
| Satellite | Temporary NORAD ID | NORAD ID to follow |
|---|---|---|
| ALPHA | 99380 | 53106 |
| TRISAT-R | 99381 | 53107 |
| GREENCUBE | 99382 | 53109 |
| CELESTA | 99383 | 53106 |
| MTCUBE 2 | 99384 | 53109 |
| ASTROBIO | 99385 | 53107 |
Two new objects by space-track.org:
0 LARES-2
1 53105U 22080A 22197.03294509 -.00000008 00000-0 00000-0 0 9998
2 53105 70.1461 76.5110 0005710 284.0523 75.9683 6.38963682 168
0 OBJECT B
1 53106U 22080B 22197.48643973 -.00000003 00000-0 00000-0 0 9996
2 53106 70.1477 76.3613 0008586 238.9993 120.9805 6.42579192 188
0 OBJECT C
1 53107U 22080C 22197.08955110 -.00000003 00000-0 00000+0 0 9991
2 53107 70.1358 76.5048 0012995 252.5698 265.5901 6.42169517 59
0 OBJECT D
1 53108U 22080D 22197.24830797 -.00000003 00000-0 00000+0 0 9993
2 53108 70.1776 76.4391 0003402 295.4109 229.8368 6.42154517 76
0 OBJECT E
1 53109U 22080E 22197.64194511 -.00000003 00000-0 00000-0 0 9996
2 53109 70.1439 76.1165 0009048 242.9231 117.0509 6.42584369 82
0 OBJECT F
1 53110U 22080F 22197.40488051 -.00000003 00000-0 00000+0 0 9996
2 53110 70.1520 76.3932 0011469 204.8630 326.2382 6.42503395 60
0 TBA - TO BE ASSIGNED
1 53111U 22080G 22197.40488052 -.00000003 00000-0 00000+0 0 9998
2 53111 70.1452 76.3960 0009155 241.6267 289.4245 6.42528174 59
0 TBA - TO BE ASSIGNED
1 53112U 22080H 22197.22866146 -.00000003 00000-0 00000+0 0 9993
2 53112 70.1463 76.4508 0010840 259.7188 224.1212 6.42613720 58
An update for CELESTA, I’ve chosen to change it to follow 53111 for now, based on @PE0SAT analysis:
Hi, just a couple of points for anyone who might be trying to use the auto scheduler to capture these MEO Sats.
Firstly, there is a default MAX_NORAD_CAT_ID value in the auto scheduler settings of 90000. These Sats have (temporary) Norad CAT ID values in the 90000s, so the auto scheduler will ignore them unless you override the default in the auto scheduler .env file.
Secondly, the auto scheduler doesn’t have the rather useful facility via the network scheduler of being able to break up these very long passes into 12 min segments. Based on the TLEs, the pass might be at least 1hr 20 mins so is very likely to collide with another scheduled observation. The route we are using that gives most control is to manually schedule the MEOs, and then run the auto scheduler to work around them. Alternatively to go fully auto you can try limiting the max observation time selected by the auto scheduler to say 15 mins, and then it would appear the scheduler selects just the middle 15 mins of the pass. We are experimenting with this approach at the moment!
After a factory reset, ASTROBIO’s frequency has been changed. I’ve add a new transmitter to watch for it.
Regarding ASTROBIO, I have set up a 38el yagi with lna pointing straight up to look for it. There are a few observations with quite similar transmissions and I just wanted to report what I have seen.
6366828, 6372808 something is drifting back and forth with the average at about -15kHz.
6366827, 6366826, 6366825, 6366517 the same but at +10kHz.
There are also other satellites on the frequency, got demod of UniSat-7 on this obs 6365657. DB has more of them.
The one strange thing is the too consistent signal from it, I would expect a lot larger difference on the higher elevations. For example this GREENCUBE obs 6373242.
Just in case someone missed the other thread:
From recent observations of GREENCUBE and with suggestions from other observers, GREENCUBE fits better on 53106 object which was assigned to MTCUBE-2, for this reasons I’ve just swapped GREENCUBE and MTCUBE-2.
So,
MTCUBE-2 is now 53109 and GREENCUBE is now 53106.
GREENCUBE fit by @satcolintel5
53106 0.030 kHz 435.310304 MHz
53109 0.164 kHz 435.310825 MHz
Identified 2 candidate(s), best fitting satellite is 53106.
Update: NORAD 53106 still seems to be the best fit for GREENCUBE. I’m basing this on doppler curves from STRF observations from three different orbits at my station 2134, RF signal at 435.310 MHz in waterfalls and last date of decoded frame Obs 6623188 on Oct 17,2022.
rms limit (kHz): 0.5
53106 0.029 kHz 435.310322 MHz
53109 0.305 kHz 435.310997 MHz
Identified 2 candidate(s), best fitting satellite is 53106.
MTCube-2 @ 436.750MHz (53109) still has not been verified in over 500 SatNOGS observations since launch on July 13. There were several RF observations in waterfalls for the initial 24 hours after launch which appeared to be a beacon signal @ 15 second intervals, nothing decoded. Notable example from observation 6211825 that appears to have a valid beacon signal.
Source: Amsat-BB
Dear All,
the S5Lab research team of the University “La Sapienza”, Rome, Italy, the Italian Space Agency and AMSAT Italia are happy to inform the ham radio community that the GreenCube satellite will be switched in digipeater mode between 29-Oct-2022 00:01 UTC and 30-Oct-2022 23:59 UTC. Information on the setup required to access the satellite can be found on the team’s web site https://www.s5lab.space/index.php/digipeater/.
The S5lab team of Sapienza provides the software needed to communicate with the satellite along with a technical guide of the setup and the GUI features. The archive contains:
The user manual
The Graphical User Interface (GUI)
The Terminal Node Controller (TNC) software
The GNURadio script to receive and transmit
The software kit can be downloaded from the same web page. The satellite digipeater implements a store-and-forward message service and works at 435.310 Mhz (U/L and D/L).
The 3U cubesat was launched on the Vega-C maiden flight on 13-Jul-2022 in a MEO orbit. The GreenCube project is being carried out through a collaboration agreement between the Italian Space Agency and Sapienza University of Rome, with the participation of ENEA and University Federico II of Naples. As for the radio frequency communications, a strong and effective cooperation with AMSAT Italia has been established, whereby AMSAT Italia endorsed the frequency coordination request.
The team can be reached via their website at the URL https://www.s5lab.space/index.php/contact-us/.
73, Fabrizio IU5GEZ for AMSAT Italia
From this link I downloaded the zip,
https://www.s5lab.space/index.php/digipeater/
uncompressed on a win7. It started normaly the
DigipeaterTNC.exe
GreenCube…grc
But when I started the GUI, the Windows Defender sent an alert, found the Wacatac trojan malware.
After some little search it become clear, sometimes there are fals detections. At least, this situation not clear for me. But some descriptions propose another online virusscan. I started to download again to a linux machine, decompressed it, and try this online virus check:
put there the DigipeaterGUI.exe file. After the scan, it reported this:
5 security vendors and no sandboxes flagged this file as malicious
179729c7663e73dae5be80179ed12f62f048859b2de4baca59d64570e2c1376e
DigipeaterGUI.exe
It seems, it has malware. Or interpret I this an incorrect way?
My questions:
Contact the GreenCube team, the mail address is on the page where you found the zip file.
Thank you Jan!
Do you think, is it only my problem?
I don’t know, but the fact that Virustotal also detects some malicious content makes me wonder.