Thank you for posting the link to your repository!
Have signals been received from any of the three satellites?
Thank you!
2 Likes
Best guess at this point, battery charging issue on all three sats. There is evidence that they are reaching beacon state at the end of sunlit portions of each orbit.
There is also a 30 minute timer for deployment that has not been turned off, so that has to time out before beaconing will start.
4 Likes
The passes over Argentina today may yield some results. Could we have some contacts scheduled there please? I would do 4800 GFSK for that.
2 Likes
Thanks for the information, can you share some information on the framing used by the satellites?
The team is working on it. There’s a few broken links on the website. Will let you know when it’s ready. In the meantime they pointed me towards the repo linked above.
3 Likes
Regarding AlbertaSat cubeSats (Ex-Alta-2, AuroraSat, Yukonsat), the AlbertaSat amateur radio webpage has been updated yesterday, please take a look!
Notably, the NORAD Catalog ID assignments have been updating but some are still incorrect. Our best guess of the correct ID’s are
Ex-Alta-2 is 56313
AuroraSat is 56315 (currently 56312 and very incorrect)
YukonSat is 56316
2 Likes
Thanks for the info.
I’ve also noticed that latest space-track.org TLE sets have the names of the satellites:
0 ARKSAT 1
1 56311U 98067VC 23119.18758196 .00052617 00000-0 87270-3 0 9995
2 56311 51.6393 211.3354 0007854 284.3881 75.6236 15.51574396 748
0 AURORASAT
1 56312U 98067VD 23119.18763609 .00055244 00000-0 91595-3 0 9995
2 56312 51.6392 211.3359 0007769 284.0966 75.9160 15.51563846 779
0 EX-ALTA-2
1 56313U 98067VE 23119.18769378 .00054682 00000-0 90751-3 0 9993
2 56313 51.6393 211.3362 0007715 283.6237 76.3893 15.51541663 762
0 LIGHTCUBE
1 56314U 98067VF 23119.12384466 .00059553 00000-0 99300-3 0 9990
2 56314 51.6390 211.6593 0007757 266.9261 93.0841 15.51373083 786
0 NEUDOSE
1 56315U 98067VG 23118.54419711 .00042131 00000-0 71098-3 0 9996
2 56315 51.6387 214.5374 0007973 263.1030 96.9053 15.51186325 648
0 YUKONSAT
1 56316U 98067VH 23118.54421730 .00048733 00000-0 82002-3 0 9992
2 56316 51.6387 214.5375 0007828 262.8353 97.1747 15.51203157 661
I’m really curious how the identification took place. @rjbarakat @lmberkhout @lskabelu @VE6IMU @VA6ISS @ve6cnk-Charles any idea?
2 Likes
I’m asking because with a quick analysis this identification doesn’t make any sense, these are the two deployment groups:
According to the above identification the groups are:
- Ex-Alta 2, ARKSat 1, AuroraSat
- LightCube, NEUDOSE, YukonSat
2 Likes
I am not sure how the identification took place, can only assume NORAD attempted to do so themselves and there was a mistake. They have made corrections each day though, so I expect AuroraSat (2nd in deployment group 2), Lightcube (3rd in deployment group 1), and Neudose (1st in deployment group 2) will be corrected soon.
Note that Ex-Alta-2, being significantly larger than Arksat and Lightcube should separate out significantly.
Additionally, YukonSat and AuroraSat are physically identical, so I expect them to stick together while Neudose moves away.
1 Like
Anyway, what would be really good is if someone here at SatNogs could (temporarily) manually change the TLEs assigned to each satellite. Then the ground stations would have the correct frequency for each satellite. Right now, if we look at any of Lightcube, Aurorasat, or Neudose, they are not going to show up because the ground stations are tracking the wrong center frequency (or conversely, correct frequency, but wrong time).
It’s likely space-track will have it all fixed in a couple days though
Tracking AuroraSat’s TLE right now has the chance of catching Ex-Alta 2, since they are on the same frequency. And tracking YukonSat’s TLE will probably catch both AuroraSat and YukonSat, since they are likely quite close together.
That’s assuming they have enough power to beacon.
1 Like
@ve6cnk-Charles could you please suggest selection for the TLE for each satellite?
However have in mind that all the satellites are pretty close so any pass we track even if it isn’t the correct one will catch the signal.
By the way, we did find some observations of all three Northern SPIRIT CubeSats earlier this week:
Ex-Alta 2:
(These next two are labelled AuroraSat but are more likely Ex-Alta 2)
(These next two are labelled Ex-Alta 2 but are likely YukonSat and/or AuroraSat):
Ex-Alta 2, AuroraSat, and YukonSat all together very interestingly in this plot:
@fredy I suspect this is the correct assignment of Name to NORAD catalogue ID.
ArkSat 1 : 56311
Lightcube : 56312
Ex-Alta 2 : 56313
Neudose : 56314
AuroraSat : 56315
YukonSat : 56316
I’ve just fixed it and now you can add many links.
Unfortunately all these signals in the observations are either terrestrial ones or other satellites. If you are interested we can find out which satellites are. Here are the results of ikhnos to observation 7470582 for each of the published TLE, with the red line you see the expected curve that the signals should have followed:
On the above images is also visible how close are the objects so even following the wrong TLE set for one of them you will be able to see the signal just a little curved.
I disagree with that. According to ikhnos analysis on observation 7462875, one of the last with transmissions from LightCube, the group of Objects 56314, 56315 and 56316 fits the signal better.
So, LightCube and the other two satellites deployed together (ARKSAT-1 and EX-ALTA-2) are Objects 56314, 56315 and 56316.
And the rest, AURORASAT, NEUDOSE and YUKONSAT are Objects 56311, 56312 and 56313.
1 Like
If someone was able to get beacons from Ex-Alta 2, AuroraSat or YukonSat and wanted to share the raw data with the team, we would really appreciate that. We would like to take a look at the data and try decoding the beacons.
2 Likes
Based on this and the slight separation of OBJECT VF(56314) from OBJECT VG(56315) and VH(56316), I’ve swapped the TLE we follow for LightCube and EX-ALTA-2.
So, now in DB and Network, we have LightCube to follow 56316 and EX-ALTA-2 to follow 56314.
Most of the signals in the waterfall are from:
47960 - Orbicraft-Zorkiy or 53386 - VIZARD
Here a Orbicraft-Zorkiy example SatNOGS Network - Observation 7484906 and a
VIZARD example SatNOGS Network - Observation 7225055
Jan - PE0SAT
1 Like
Looking at observation 7470582, this seems to be VIZARD, the freq from this station seems to be of by 5 kHz and I compensated ikhnos.
ikhnos -t T.tle -r 29 -f -5 7470582
T.tle:
Orbicraft-Zorkiy
1 47960U 21022AE 23119.49716611 .00012747 00000-0 71709-3 0 9992
2 47960 97.5038 18.1451 0019379 136.3324 348.7309 15.13234668115191
VIZARD
1 53386U 22096S 23119.37701051 .00044602 00000-0 11063-2 0 9993
2 53386 97.4166 26.0348 0003235 191.7737 275.3223 15.40234776 40266
3 Likes