INNOCUBE RAW Telemetry
308 Frames I uploaded to SatNOGS DB
Huge thanks UZ7HO for new SoundModem!!!
http://uz7.ho.ua/ax100nocrc32.zip
9 Likes
Hi there!
I’m also from the InnoCube team, thanks everybody for the interest in our project and your support! It’s great to see so many TM frames being decoded already by some of you and the SatNogs network!
Tracking using the currently used TLE from SatNogs looks good to us. We hope we will be able to provide a telemetry decoder soon (see INNOCUBE decoder (!427) · Merge requests · librespacefoundation / SatNOGS / satnogs-decoders · GitLab)
InnoCube is doing fine and the batteries are fully recharged after the LEOP operations.
Cheers
Tom
7 Likes
7 Likes
Isn’t the “no CRC32” version of AX100 Modem from UZ7HO intended for INNOCube?
At least the 1KUNS-PF version(s) will also work for ION SVC-016.
Yes it is, I thought id try it as it looked similar, so although it has decoded data I’m not sure if its correct
The AX.100 deframer in GNU Radio appears to work also
… and the final layout w/ all my standard input & output options:
3 Likes
And speaking of ION_SVC-16, does anyone know if there will be any announcement before, during, or after it deploys its satellites?
1 Like
Tried APRS Digipeating on PARUS-T1 but no luck. Did not hear the beacon during the 18:05 UTC pass over MK83sd, Bengaluru India.
2 Likes
Unfortunately D-Orbit doesn’t share that info. Our only chance to know that in time is through a satellite team, otherwise we will find out later through NORAD when there are new TLE sets or a tweet if it happens.
4 Likes
@K4KDR
I’ve asked me that, too.
However, the valuable cargo, the PocketQubes Prometheus-1, HYPE, Hades-R and POCQUITO are additionally inclosed into one or two Albapods. So we additionally would need to know when Alba Orbital will release its payload.
Seven PocketQube satellites were packed into the two Albapod deployers on the flight.
5 Likes
I have a question regarding the Yaml file. Can I expect an improvement in the decoding, or what is the advantage or purpose / use when I apply this file ?
I mean, my GS is providing good results as you can see here SatNOGS Network - Observation 10926782
What change I can expect ?
Thanks, Manuel
Good evening Manuel,
For INNOCube there is a native SatNOGS GOMspace AX.100 decoder part of the install and that works pretty good, and therefor you don’t need the gr-satellites integration for this specific satellite.
I have seen more frames being decoded with gr-satellites when Yaml is optimized, the biggest parameter that needs investigation is --deviation and that is when decoding real time using the IQ stream from your SDR.
I had a quick look at your observation, and even when I replay the audio recording (ogg file) (then deviation is done by the satnogs fsk flowgraph) I get 266 frames decoded compared to your 58, when using the gr-satellites satnogs integration.
Replay:
gr_satellites INNOCUBE.yml --wavfile 10926782.ogg --samp_rate 48e3
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 9k6 FSK downlink))
pdu length = 221 bytes
pdu vector contents =
0000: 01 55 03 00 0a 44 57 00 00 6f 3e 8d 01 dd 1d e1
0010: 0a 32 08 af cd 4c 14 00 00 20 09 a6 01 4f 00 00
0020: 0b 91 4e 00 f2 00 00 f0 00 00 01 00 00 00 01 00
0030: 00 00 00 00 80 00 00 00 05 00 00 00 63 00 00 00
0040: 00 00 00 00 00 14 49 61 74 85 53 57 2f 47 5e 29
0050: 11 88 00 00 4c a1 00 00 00 00 4b e7 00 08 00 63
0060: 06 94 00 00 00 00 00 00 00 00 00 00 0b 05 00 00
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00
************************************
gr_satellites INNOCUBE.yml --wavfile 10926782.ogg --samp_rate 48e3 | grep "VERBOSE PDU DEBUG PRINT" | wc -l
266
So you can consider if you also want to activate the gr-satellites integration on your SatNOGS station.
All the best,
Jan - PE0SAT
Generic gr-satellites documentation.
The old pre docker way to integrate with SatNOGS.
3 Likes
Hello Jan,
many thanks for your comprehensive explanation, that sounds very interesting. I am curious and intend to try it - with your recoemmended deviation value of 3200.
Thank you for sharing the link to gr-satellites documentation as well.
Best 73, Manuel
1 Like
Great decoding @EU1SAT !
During our pass (and also in some satnogs recordings) we noticed degrading celestrack tle performance. We currently struggle with the use of strf since our team is fully occupied in preparing the passes. Did anybody already check for an improved TLE? Maybe @PE0SAT ? We’d appreciate your help 
We also got some ADCS data, InnoCube is slowly tumbling as expected with a rate of approx. 3 dps.
Cheers
Tom
1 Like
Besides Centauri 7 and Centauri 8 there were two satellites launched on Tyvak platform - OTTER and SATGUS (Not yet in DB).
After we changed frequencies of Centauri 7 to 400.220 MHz, I noticed that there are two satellites which are working on this frequency (they are very close on orbit yet) - it is clearly visible here. And at least one of them have callsign FLEF5N - see here.
This type of callsign FLEF*N is usually belongs to Centauri satellite. For example, Centauri 4 had FLEF2N (see here) and Centauri 6 FLEF4N (see here). So FLEF5N should be Centauri 7 and FLEF6N should be Centauri 8.
My guess right now is that both Centauri 7 and Centauri 8 have same frequency 400.220 MHz. And satellite on 400.200 MHz is one of other Tyvak satellites - either OTTER or SATGUS. Because it have different callsign GRAF1N (see here).
Also because we have almost no info about OTTER, i suppose we have Sat Gus on 400.200 MHz
3 Likes
VERY strong downlink from ION_SVC-16 tonight & the AX.100 deframer in GNU Radio worked as well w/ a live signal as it did w/ the audio recording from SatNogs!
2 Likes
Great analysis @geoscan!
From this observation’s data we can also see the FLEF6N call sign.
I’ve updated the transmitter frequency of Centauri 8 to 400.220 MHz and I’ve also updated the callsigns of both in their DB entries.
I’ve added a new unknown satellite for now for this signal at 400.200 MHz, let’s watch it and see if we can find which one is it.
3 Likes
