AESP-14 Deployment

AESP-14-CubesatFirst Cubesat Developed in Brazil.

PY2SDR has confirmed the deployment of AESP-14 from the International Space Station at 14:30 UTC on Thursday, February 5.

The AESP-14 team would like to ask the help of the AMSAT community to forward any received telemetry frames back to the team. For this, please save the AX.25 frames in KISS format and forward the file to aesp14 (at) ita.br. Telemetry format can be found at this location: AESP14-Telemetry Format.

AESP-14 CubeSat
Frequency: 437.600 MHz 9k6 AX25

After launch we can use the TLE data from ISS.

Source: Amsat-BB

Delta-2 SMAP launch sequence

Delta-2 SMAP LaunchNew Delta-2 Cubsat ppod launch sequence.

Based on todays schedule and the fact the launch is delayed for 24 hours, then the below schedule should be the correct sequence for tomorrow 01/30/15 14:20:42 UTC. Latest news on the SMAP launch: Spaceflight101.

Below the Cubsat deploy and activation details for Exocube (CP10), Firebird-2 and Grifex.

Event Elapsed (min) Time (UTC)
Launch 0 1/31/15 14:20:42
Firebird-2 deploy 105 1/31/15 16:05:49
Grifex deploy 107 1/31/15 16:07:29
Exocube (CP10) deploy 108 1/31/15 16:09:09
Firebird-2 Beacon start 165 1/31/15 17:05:49
Grifex Beacon start 172 1/31/15 17:12:59
Exocube (CP10) Beacon start 308 1/31/15 19:29:09

Source: Amsat-BB

UKube-1 BPSK Telemetry

UKube-1 BPSK Telemetry 26-01-2015 20:13 UTC

For me a first to hear Ukube-1 send BPSK on 145.805 +/- doppler

2015-01-26 20:23:18.190 UTC: from UKUBE to MIDORI (UI, payload: 125 byte)
000 > 00 9A 92 88 9E A4 92 00 AA 96 AA 84 8A 40 01 03 F0 08 02 C0 
020 > 47 00 76 10 03 19 F1 00 00 B3 9F 00 00 06 2A 08 00 21 05 00 
040 > 17 40 3D 00 00 00 41 58 33 D8 30 C0 00 00 00 02 00 00 00 00 
060 > 0A 1D 00 15 54 00 FC 01 7E 00 00 0B FB CF 00 A0 10 54 A3 00 
080 > 00 00 00 00 00 00 8B 00 7B 00 84 80 8A 00 78 00 85 80 82 00 
100 > 87 80 00 00 00 02 80 00 00 00 00 00 00 00 3D E0 00 00 00 00 
120 > 6B 58 37 C0 03 04 01 30 00 00 00 00 00 00 00 00 00 04 00 00 
140 > E0 B4

ukube1_dk3wn_2017_utc_2014-07-11

CubeSAT launch 29-01-2015

Exocube CP-10CubeSat launch scheduled for Jan 29, 2015 14:20 UTC from Vandenberg Air Force Base Space Launch Complex with a Delta-2 rocket.

Primary payload: Soil Moisture Active Passive (SMAP) secondary payload: ELaNa-X (3 POD)

Firebird-II FU3         437.405 MHz 19k2 FSK
Firebird-II FU4	        437.230 MHz 19k2 FSK
GRIFEX                  437.485 MHz 9k6 FSK
Exocube (CP-10)         437.270 MHz 9k6 FSK

Preliminary TLE

EXOCUBE
1 99993U 00000    15029.59770833 -.00001134  00000-0 -64350-4 0 00004
2 99993 099.0736 036.6690 0163275 344.1705 144.7582 15.02264856000014
FIREBIRD-2
1 99991U 00000    15029.59770833 -.00001191  00000-0 -74412-4 0 00005
2 99991 099.0666 036.7936 0148155 343.1200 146.2345 15.00731451000019
GRIFEX
1 99992U 00000    15029.59770833 -.00000939  00000-0 -53803-4 0 00006
2 99992 099.0410 036.6726 0153788 343.4726 145.2471 15.03079548000011

Source: SatBLOG DK3WN

New UZ7HO Sound modem version

UZ7HO has released a new version of his great Sound modem software.

UZ7HO Soundmodem

Here is part of the version history file, take a look at this file to get to know al the options.

SCM v0.71b changes:
- Fixed "Frame Collector" operation with MAXFRAME greater than 4 and IPOLL
  frames. By default it supports up to 6 frames into collector's buffer now.
- Added "TXFrmMode" option (that was available in 9k6/19k2 version). It allows
  to select the transmission mode of the frames.

  If set "TXFrmMode=1" then it will repeat only one frame on each of REJ acks.
  It can be useful in poor condition jointly with MAXFRAME up to 4. If another
  station uses a TNC which can operate with "Frame Collector" this option can
  improve a performance, especially on HF.

  If set "TXFrmMode=0" then it will always repeat the block of the frames, of
  which the number is limited by MAXFRAME. It can improve the efficiency in
  good condition. Especially with TNCs without "Frame Collector" function.

  By default this value is "1".