CSSWE Telemetry 08-10-2013

CSSWE Telemetry 08-10-2013 18:45 UTC

CSSWE TLM 08-10-2013 184:5UTC

CSSWE Telemetry 08-10-2013 17:09 UTC

CSSWE Telemetry Decoder   (c) Mike Rupprecht, DK3WN
=====================================================

Satellite Mode         SAFE            |  Cmds Since Boot        17740             
Time Since Boot        111.9991  days  |  EPS                    OK                
Batt Voltage           7.88      V     |  Batt Temp              18      dec C   
Batt Discharge Current 62.75     mA    |  Batt Charge Current    0.00    mA      
5V Bus Voltage         5.00      V     |  5V Bus Current         31.37   mA      
3.3V Bus Voltage       3.31      V     |  3.3V Bus Current       54.90   mA      
Solar Panel Volt/Curr  OK              |  PVX1 Voltage           0.00    V       
PVX1 Current           0.00      mA    |  PVX2 Voltage           10.61   V       
PVX2 Current           0.00      mA    |  PVY1 Voltage           0.34    V       
PVY1 Current           0.00      mA    |  PVY2 Voltage           8.40    V       
PVY2 Current           0.00      mA    |  Solar Panel Temp       OK              
PVX1 Temp              -11       deg C |  PVX2 Temp              29      deg C   
PVY1 Temp              13        deg C |  PVY2 Temp              57      deg C   
Radio                  OK              |  Radio Temp             19      deg C   
CDH Temp               19        deg C |  GPIO: Battery Heater   OFF     V       
GPIO: ADM Resistor     OFF       V     |  GPIO: REPTile 3.3V     ON      A

DANDE Telemetry 04-10-2013

DANDE Telemetry 04-10-2013 19:28 – 19:35 UTC using object 2013-055U

Sorry for all the possible confusion. I have to go back to the drawing board because what seemed to be a good fit last night, isn’t working anymore. It is still not clear what TLE to be used with CUSat and DANDE.

2013-055U
1 39273U 13055U   13277.46126644  .06799826  16859-1  11664+0 0   109
2 39273  80.9080 310.2662 0517474 146.5534 210.4066 14.72121854   685

In total 37 frames decoded and object U fitted perfect at the end of the pass.
Below, one of the frames received.

from DANDE-2 to DANDE-1: 
   1 > 64 61 6E 64 65 63 6F 73 67 63 00 06 C1 60 00 04 00 06 7F C1 
  21 > 00 00 00 00 05 F7 04 F7 02 00 D0 02 00 01 02 00 00 FF 02 02 
  41 > 3B 01 90 00 00 02 36 01 08 01 7E 01 8F 01 8B 01 A9 01 9F 28 
  61 > 00 00 01 0F E7 00 19 0D 50 0B DB 0E DD 06 89 05 FC 05 F7 05 
  81 > ED 00 02 05 C7 09 B2 3D 0B 3D 28 0E 1C 0F 25 00 00 64 61 6E 
 101 > 64 65 2E 63 6F 6C 6F 72 61 64 6F 2E 65 64 75 4A 44 
dandecosgc..Á`....Á.....÷.÷..Ð......ÿ..;....6...~..‹.©.Ÿ(....ç...P.Û.\
Ý.‰.ü.÷.í...Ç.²=.=(...%..dande.colorado.eduJD

I do have a lot of frames decoded from the late passes from 04-10-2013 and they can be found at the following location.

DANDE Telemetry download: location

OOREOS Telemetry

O/OREOS Telemetry 04-10-2013 09:36 UTC

O/OREOS SDR 04-10-2013 09:36 UTC

1:Fm KF6JBP To UNDEF Via TELEM  [11:35:46R]
OOREOS.org    F8C799025D009901C90000A301C20A9A000D5F094300204B46
1:Fm KF6JBP To UNDEF Via TELEM  [11:35:51R]
OOREOS.org    FCC7990300008D0100030032022D0054050D5F094300204B46
1:Fm KF6JBP To UNDEF Via TELEM  [11:35:56R]
OOREOS.org    02C899000000AB011AB9015D03020286010D5F094300204B46
1:Fm KF6JBP To UNDEF Via TELEM  [11:36:01R]
OOREOS.org    07C8990193019B01DA7C01A3010000CF090D5F094300204B46
1:Fm KF6JBP To UNDEF Via TELEM  [11:36:11R]
OOREOS.org    11C899034F008D0100A30131022D0054050D5F094300204B46
1:Fm KF6JBP To UNDEF Via TELEM  [11:36:16R]
OOREOS.org    16C89900AE00AC011BBA010803020286010D5F094300204B46
1:Fm KF6JBP To UNDEF Via TELEM  [11:36:21R]
OOREOS.org    1BC8990100009C01DA7D01A3010000CF090D5F094300204B46
1:Fm KF6JBP To UNDEF Via TELEM  [11:36:26R]
OOREOS.org    20C8990257009D01C95400A301C20A9A000D5F094300204B46
1:Fm KF6JBP To UNDEF Via TELEM  [11:36:31R]
OOREOS.org    25C89903DD008E0100A30132022D0054050D5F094300204B46
1:Fm KF6JBP To UNDEF Via TELEM  [11:36:41R]
OOREOS.org    2FC899015C009D01DA7E01A3010000CF090D5F094300204B46
1:Fm KF6JBP To UNDEF Via TELEM  [11:36:46R]
OOREOS.org    34C89902E2009F01C95400A301C30A9A000D5F094300204B46
1:Fm KF6JBP To UNDEF Via TELEM  [11:36:51R]
OOREOS.org    39C899030000900100A30132022D0054050D5F094300204B46

O/OREOS TLM 04-10-2013 09:36 UTC

DANDE Heard 02-10-2013 17:32 UTC

DANDE heard during the pass of 02-10-2013 at 17:32 UTC. In total 10 frames received.

[136 Bytes KISS Frame (without CRC)]
from DANDE-2 to DANDE-1: 
   1 > 64 61 6E 64 65 63 6F 73 67 63 00 04 05 7C 00 03 00 00 00 00 
  21 > 00 00 00 00 05 F7 00 04 00 00 D0 02 00 01 02 00 00 FF 02 01 
  41 > B9 01 50 00 00 01 AC 00 B0 01 42 01 4F 01 48 01 63 01 56 28 
  61 > 00 00 01 0F EE 00 22 0C CC 0B EA 0E DE 05 D8 05 99 05 9B 05 
  81 > F0 00 01 05 C8 09 42 3B 58 3B 52 0D 8A 0E 8D 00 00 64 61 6E 
 101 > 64 65 2E 63 6F 6C 6F 72 61 64 6F 2E 65 64 75 D6 3C 
dandecosgc...|...........÷....Ð......ÿ..¹.P...¬.°.B.O.H.c.\
V(....î.".Ì.ê.Þ.Ø.™.›.ð...È.B;X;R.Š...dande.colorado.eduÖ<

DANDE received data Download: location

Large number of objects after Falcon Launch

After being confronted with a large number of objects via celestrak.com I saw T.S. Kelso his ‏tweet on twitter where he is also trying to find out why there are so many object after the Falcon 9 v1.1 launch. “Trying to make sense of today’s Falcon 9 launch. There were supposed to be 6 payloads, but we have 20 objects (so far). TLEs are online.” Via Spacenews I found the following possible explanation for this.

Falcon launchU.S. Space Surveillance Network is tracking a large number of objects after Falcon 9 v1.1 Launch.

SpaceX issued a statement Oct. 1 denying speculation that the upper stage of its Falcon 9 v1.1. rocket exploded on orbit following the rocket’s successful demonstration launch Sept. 29 from the Vandenberg Air Force Base in California.

The speculation was spawned in part by the fact that the U.S. Space Surveillance Network is currently tracking more orbital objects associated with the launch than expected.

“Regarding the rumors you may have heard about the Falcon 9 second stage, in short, our data confirms there was no rupture of any kind on the second stage,” SpaceX spokeswoman Emily Shanklin wrote in an Oct. 1 email. “Following separation of the satellites to their correct orbit, the Falcon 9 second stage underwent a controlled venting of propellants … and the stage was successfully safed. During this process, it is possible insulation came off the fuel dome on the second stage and is the source of what some observers incorrectly interpreted as a rupture in the second stage.”

SpaceX attempted to reignite the upper stage after payload separation in a demonstration of a capability it will need to place satellites into the proper geostationary transfer orbit. However, the re-ignition sequence was aborted after a problem was detected, SpaceX Chief Executive Elon Musk told reporters in a post-launch teleconference.

Falcon Second Stage Space ImageFollowing the launch, an eyewitness in Reunion Island off the eastern coast of Madagascar posted a photograph on the website Reddit of what amateur astronomers later determined was a cloud of rocket propellent surrounding the spent Falcon 9 1.1 upper stage. By Sept. 30, the U.S Air Force-run Space Surveillance System was tracking 20 objects associated with the launch in low Earth orbit. Experts were expecting to see 11 objects, including Cassiope; the three secondary payloads, one of which released seven independently flying objects; and the upper stage.

SpaceX’s explanation of events is copied below:

Following separation of the satellites to their correct orbit, the Falcon 9 second stage underwent a controlled venting of propellants (fuel and pressure were released from the tank) and the stage was successfully safed. During this process, it is possible insulation came off the fuel dome on the second stage and is the source of what some observers incorrectly interpreted as a rupture in the second stage. This material would be in several pieces and be reflective in the Space Track radar. It is also possible the debris came from the student satellite separation mechanisms onboard. SpaceX will continue to review to help identify the source of the extra debris, but our data confirms there was no rupture of any kind on the second stage.

Source: Spacenews