PSAT Telemetry 03-06-2015 10:53 UTC
1:Fm PSAT To APRSON Via ARISS [12:52:23R] T#444,871,032,130,129,412,00000000 1:Fm PSAT To APRSON Via ARISS [12:52:56R] s#013306,0z200,FGeFGeEGeDGeBGd0GdaGdbGddGddGddGedFe 1:Fm PSAT To APRSON Via ARISS [12:53:24R] T#445,829,357,129,129,411,00000000 1:Fm PSAT To APRSON Via ARISS [12:54:24R] T#446,819,371,129,128,411,00000000 1:Fm PSAT To APRSON Via ARISS [12:59:08R] s#013310,0z200,IbEIaDI0CIABICAID0HE0HFaHFaGFaGF0FF0
Atlas V ULTRASat Objects identified
By using detailed Doppler shift measurements, PA0DLO informs that LightSail is object 90726, ULTRASat 7, without any doubt.
This means that LightSail is actually object 40658, 2015-025H in the JSpOC catalog.
The preliminary initial assignments in the JSpOC catalog for the objects in this launch will need to be corrected:
PSAT = 90720 = ULTRASat 1 = 40652 = 2015-025B
LightSail = 90726 = ULTRASat 7 = 40658 = 2015-025H
BRICSat = 90729 = ULTRASat 10 = 40661 = 2015-025L
Source: PA0DLO, Amsat-BB
LightSail was silent for eight days, but she is active again.
During this morning (31-05-2015 09:53 UTC) pass over The Netherlands I first received weak FSK signals and realized that the TLE I was using (ULTRASat2) didn’t match very well so I switched to ULTRASat8 and was able to decode 19 frames.
2015-05-31 10:03:12.770 UTC: from KK6HIT-1 to N6CP-X (UI, payload: 248 byte) 000 > 00 9C 6C 86 A0 5A B0 00 96 96 6C 90 92 A8 03 03 CC 45 00 00 020 > F8 00 00 40 00 40 11 11 2D 81 41 93 21 81 41 93 24 C3 50 C6 040 > 70 00 E4 D5 23 02 00 00 92 41 00 00 94 41 00 00 00 00 00 00 060 > 00 00 80 99 89 40 F9 0F 29 3D 81 EB 51 40 29 20 2D 3D C0 4F 080 > 9D 40 06 0E 90 3E A8 01 03 3C 00 00 00 00 A8 01 83 3B 9A 07 100 > B0 BA BB 34 00 00 74 89 00 00 00 00 00 00 F7 75 00 00 02 00 120 > 00 00 00 00 00 00 00 00 00 00 1D 39 10 0B 01 B2 07 00 DE 60 140 > DF 20 DE A0 E0 A0 00 00 00 03 00 03 00 03 00 03 00 03 00 03 160 > 00 03 00 03 09 8C 6D 30 0F 00 6D 60 08 58 6D 50 0F 30 6C F0 180 > 14 D0 6C 40 00 50 6D 70 10 B0 6D 00 1C F8 6D 00 1C 00 01 0B 200 > FB CF 01 15 00 15 00 1A 00 1A 00 20 00 25 00 1F 00 1C 00 18 220 > 3F 00 3F 00 01 96 00 1A 00 7F 01 18 00 35 00 07 01 8A 00 DB 240 > 00 25 00 E4 00 25 00 59 00 00 00 00 00 00 00 00 00 00 0F 00 260 > 40 00 00 80 40
TLE
ULTRASat7 (LIGHTSAIL-A) 1 90726U 15154.58498645 +.00012439 +00000-0 +33532-3 0 00213 2 90726 055.0069 279.7147 0249269 215.8824 234.0970 15.12547949002116>
ULTRASat8 1 90727U 15150.55115000 +.00017130 +00000-0 +45788-3 0 00150 2 90727 055.0112 297.1659 0249189 205.9605 230.4519 15.12499718001507
Download IQ recording
Download kiss file
MXL (The Michigan Exploration Laboratory) Grifex update: 28-06-2015
Our primary challenge in the past couple of weeks has been cold temperatures aboard the satellite. You may have noticed increased beacon frequency and higher transmit power – this was to keep the battery above the 0 deg. C minimum safe charge temperature.
We have completed several more MARINA runs with differing features, however, we are waiting on confirmation from JPL of a good image before we can release any images. Additionally, we have been able to pinpoint increased voltage drops during beacon transmissions as one source of MARINA aborts, so we have applied the appropriate mitigations (no beacons during MARINA runs) in order to reduce the overall number of aborts.
Source: MXL Ops
O/OREOS Telemetry 28-05-2015 16:53
O/OREOS, nanosatellite managed by NASA’s Ames Research Center, successfully launched at 5:25 p.m. PST on Friday, Nov. 19, 2010, from Alaska Aerospace Corporation’s Kodiak Launch Complex on Kodiak Island, Alaska.
PSAT Telemetry 21-05-2015 13:41 UTC PSK31
435.350 NFM – Decoded with DM780
W3ADO-5 beacon B ØØ7 8 44 785 247 +25 W3ADO-5 beacon B ØØ8 93 42 777 247 +25 W3ADO-5 beacon B ØØ9 87 34 784 247 +26 W3ADO-5 beacon B Ø1Ø 99 37 776 247 +26 W3ADO-5 beacon B Ø11 99 32 782 248 +26 W3ADO-5 beacon B ØØØ 34 45 796 245 +23 W3ADO-5 beacon B ØØ1 9Ø 37 784 249 +25 W3ADO-5 beacon B ØØ2 99 38 775 246 +25 W3ADO-5 beacon B ØØ3 87 47 779 247 +26 W3ADO-5 beacon B ØØ4 9Ø 48 772 247 +26 W3ADO-5 beacon B ØØ5 78 23 777 246 +26 W3ADO-5 beacon B ØØ6 99 38 774 246 +27 W3ADO-5 beacon B ØØ7 68 38 779 246 +27 W3ADO-5 beacon B ØØ8 99 4D 775 246 +27 W3ADO-5 beacon B ØØ9 68 37 772 246 +26
PSAT Beacon specification:
CALL beacon MODE NOF DET AGC VC IC TMP
Where:
| CALL | identification of the beacon (callsign) |
| beacon | keyword indicating beginning of data |
| MODE | A or B (A – transmitter always on, B – transmitter turns on, if BPSK31 signal is present) |
| NOF | number of frame (0 … 999) |
| DET | percentage of BPSK31 detection (0 … 99%) |
| AGC | percentage of AGC operation (0 … 99%) |
| VC | supply voltage (10 mVolts) |
| IC | power amplifier current (mAmps) |
| TMP | temperature of PA transistor (deg C) |
The AGC measured voltage is highly nonlinearly dependent on the input signal, morover the limiting values of measurement vary with temperature of the chip and its supply voltage. Indicative only conversion equation was computed as from 50Ohm generator to input of receiver Pin = 0.472xAGC-113.5 [dBm, %]
Example:
W3ADO-5 beacon B 044 03 24 540 198 +28
It means mode B active, frame number 044, BPSK31 03 %, AGC acting 24%, supply voltage 5.40V, PA current 198mA ant temperature of the PA transistor of +28°C.
Source: PSAT beacon specification