Hi fredy! This is Arturo from México. I made the request on IRC #cubesat channel. Now we are still trying to make contact with the satellite with no success. I have been reading that you have some observations regarding PAINANI issue. Could be possible for you to help me with this, please? Sorry about this questions but is the first nanosat from Mexico and all communication channels related to this are totally new for us
Can you please supply more information about PAINANI so we can see how we can help?
This is the information we have so far based on your IARU application and frequency coordination:
We will also need the encoding/framing and any other information you can supply on what the satellite transmission would look like.
You can see on our Network observations of PAINANI here:
Unfortunately we don’t seem to have any successful captures of the satellite so far (?).
Thanks for your reply.
Based on your request, i can share this available information of the PAINANI transmission:
Modulation: GMSK@9600 bps; AFSK@1200 bps
Data link: AX.25
Encoding: CCSDS (1/2 Rate, K=7)
Configuration mode: Full-duplex operation (Mode 1 DL: GMSK 9600 bps; Mode 2 DL: AFSK 1200 bps; Mode 3 DL: GMSK 9600 bps)
Frequency range: 430-440 MHz
Spurious responses: 10 MHz reference oscillator, 25 kHz comparison frequency; <-65 dBc
Harmonic outputs: <-40 dBc
Frequency deviation: 3 kHz
Channel spacing: 25 kHz
Is it enough this information? Do you need some other specific parameters? Please, just tell me and i will try to give you precise data.
Thanks for your help.
@art if you have any information that can help us decoding these frames, would be more than welcome!
The telemetry description provided in the link above describes a totally different type of telemetry.
The headers indicate a source callsign
SPACE and a destination callsign
EARTH. Probably PAINANI-1. Most of the frames in the latest observations are from
TBEX-B as identified in the AX.25 headers showing a source of
KF6RFX, and also the very prominent
0xABCD just after the header indicates this (maybe cross-travelling among the PAINANI-1 orbit).
It could indeed be TBEX-A and -B, as they share the same callsign. The payload includes a spacecraft identifier, where
0x52 identifies TBEX-A, and
0x53 identifies TBEX-B. See
mxl.ksy in satnogs-decoders.