Many thanks for the GRC file!
Here is the link without that trailing period → GitHub - ASU-cubesat/lightcube_telemetry: Repository for the downlink of the Amateur LightCube Satellite Telemetry
3 Likes
Could you kindly let me know if this is a valid LightCube decode? After adjusting your GRC flowgraph to input an audio file, I tested with an extremely strong & clear capture from SatNogs Observation → SatNOGS Network - Observation 7462188
Of course I’ll share the altered GRC if this is a valid decode.
Thank you!
2 Likes
On a really quick look, it looks reasonable to me! The call sign is KJ7TZG and it repeats twice in the header, preceded by a # for the hearbeat packet- in that .grc I use the first iteration of the call sign to sync which is why you only see it once at the start. I see the #callsign repeated a few times so looks like a few packets here? Hopefully we’ll have the packet definition up soon to interpret the other characters.
Thank you so much for the quick reply! I was looping through that ‘good’ packet repeatedly, so it’s no surprise that my output was not exactly correct. Here I replayed the entire .OGG audio file from SatNogs only -1- time through & I believe the decode looks to be formatted more correctly.
I’ll share my GRC file asap. Thank you!
1 Like
Obviously a LOT of room to improve on my modifications, but if anyone would like a GRC file that decodes LightCube with audio files as the input, you’re welcome to →
https://www.qsl.net/k/k4kdr//grc/lightcube/
4 Likes
Also trying to get some decodes after changing the .grc so it can use decoded audio as input.
I need to work on my HEX editor skills, puzzled how to get some human readable output 
This gave me the below result:
Packet number 12
***** VERBOSE PDU DEBUG PRINT ******
()
pdu length = 250 bytes
pdu vector contents =
0000: a4 e1 5e 26 e6 2e c4 e6 de 94 e1 ae 00 66 06 ae
0010: eb 0e bf e4 86 20 e0 06 00 68 0e 00 60 06 00 60
0020: 06 00 60 06 04 66 06 00 68 0e 14 6a f6 00 60 06
0030: bc e2 9e 00 6b fe c0 60 06 00 7f ff ff ff ff ff
0040: ff ff ff fd ff ef e7 f7 bf eb ce 60 7f b0 db e1
0050: f7 03 cc 9b 13 e3 a5 07 e3 86 93 1f 42 f2 40 a5
0060: 58 20 80 2f 2f 46 6e 20 58 6b 78 0a 30 e1 e1 ac
0070: 21 d7 19 7c c9 19 ff e5 5d 31 66 30 60 2e 11 0b
0080: f1 ac 95 18 8b 68 8c 5e c3 f8 03 d5 e2 65 9c d0
0090: 61 7a b0 f9 d0 ef 41 45 c3 90 08 52 a0 00 8f 89
00a0: 8b d3 3b 34 49 27 a4 a8 e2 9c 52 3f 69 e9 03 ef
00b0: 84 1e 87 37 0a 13 30 3d 1d b8 62 a3 b6 48 31 03
00c0: 07 4c 02 cb 31 96 02 c0 d8 e4 67 a1 ee 86 99 d3
00d0: 77 a5 00 b0 67 dd c8 18 07 48 80 17 74 ff 4c 25
00e0: 19 0c 67 a7 6a c6 28 4c 4f e2 56 4f 58 64 05 e9
00f0: 22 8d c2 4d e7 b5 87 42 45 e7
************************************
1 Like
Hi Jan!
I always output decodes to direwolf just because I like the formatting. Please note that the baud rate in my .CONF file is moot… we’re not decoding with direwolf in this case - only passing already decoded KSS data to it via /tmp/kisstnc (again, just because I like the output format). BEFORE running the GRC flowgraph, direwolf must be started with something like:
.
3 Likes
And, if anyone would like this flowgraph for -live- UDP audio input from something like GQRX + output to the SatNogs uploader, I’ve added that to another copy (NOT YET TESTED) in this same folder →
2 Likes
Hi Fredy!
I’m a member of the LightCube team that worked on calculating a TLE before deployment using data provided by Nanoracks. I’m pleased to say your TLE that you’ve calculated using observations perfectly matches our predicted TLE exactly when used to predict passes. This confirms that our predicted TLE is accurate. Thanks for the work you put in to calculate this!
4 Likes
note my flowgraph cuts bytes 0-6
I watched something similar to NEUDOSE for about 3 minutes after the ISS. Speed is like 4k8. Interval approximately 1.5 min. I could not demodulate, a weak signal.
2 Likes
Ok, ‘official’ TLEs for this deployment are out. All objects still very close to the ISS, of course.
https://celestrak.org/NORAD/elements/gp.php?GROUP=last-30-days&FORMAT=tle
3 Likes
Thanks I’m copy pasting here, the TLE from space-track.org, which still need to be assigned:
0 TBA - TO BE ASSIGNED
1 56311U 98067VC 23115.52746675 .00038698 00000-0 65378-3 0 9996
2 56311 51.6322 229.4829 0008999 274.9363 149.9593 15.51184527 179
0 TBA - TO BE ASSIGNED
1 56312U 98067VD 23115.52747286 .00038654 00000-0 65371-3 0 9991
2 56312 51.6423 229.5027 0007973 264.4535 160.4044 15.51165428 201
0 TBA - TO BE ASSIGNED
1 56313U 98067VE 23115.52747270 .00005488 00000-0 10000-3 0 9993
2 56313 51.6342 229.4847 0008176 268.6907 156.1076 15.51141343 191
0 TBA - TO BE ASSIGNED
1 56314U 98067VF 23115.52767954 .00005444 00000-0 10000-3 0 9997
2 56314 51.6391 229.4934 0008603 254.6104 170.5958 15.50923664 228
0 TBA - TO BE ASSIGNED
1 56315U 98067VG 23115.52768484 .00007716 00000-0 13837-3 0 9992
2 56315 51.6440 229.5096 0008255 245.6615 179.5552 15.50936649 174
0 TBA - TO BE ASSIGNED
1 56316U 98067VH 23115.52767938 -.00000465 00000-0 00000+0 0 9995
2 56316 51.6394 229.4995 0007901 238.4564 186.6871 15.50910570 190
1 Like
A status update after space-track.org TLE sets:
| Temporary NORAD ID | Satellite | NORAD ID to follow | Other NORAD IDs | Identified | Last Update |
|---|---|---|---|---|---|
| RECEIVED AND DEMODULATED | |||||
| 99172 | NEUDOSE | 56311 | 56312, 56313 | NO | Received but not heard since 2023-04-24 18:31 - random choice of NORAD ID to follow |
| RECEIVED | |||||
| 99165 | LIGHTCUBE | 56314 | 56315, 56316 | NO | Received - Set NORAD ID to follow by using best fit, other objects fit pretty good too |
| NOT RECEIVED | |||||
| 99166 | ARKSAT-1 | 56315 | 56314, 56316 | NO | Not received - random choice of NORAD ID to follow |
| 99169 | AURORASAT | 56312 | 56311, 56313 | NO | Not received - random choice of NORAD ID to follow |
| 99167 | EX-ALTA 2 | 56316 | 56314, 56315 | NO | Not received - random choice of NORAD ID to follow |
| 99168 | YUKONSAT | 56313 | 56311, 56312 | NO | Not received - random choice of NORAD ID to follow |
3 Likes
Is anyone currently receiving a LightCube beacon ? I have not received anything for several pass.
1 Like
No, nothing form LightCube nor NEUDOSE
Nothing here either FN41iq 
1 Like
Nothing here either KO33ru
1 Like
The AlbertaSat GitHub is here GitHub - AlbertaSat/ex2_ground_station_software: Ground station connection/data management software, the GNURadio flowgraph is in the repo.
3 Likes