SDRSharp 1347 released

Posted on by

SDRSharp LogoTo my surprise I saw today (11-06-2015), that there was a new SDR# version released on there website. Below all the changes that have been done on the code since version 1337.

------------------------------------------------------------------------
r1347 | prog | 2015-06-09 18:22:46 +0200 (Tue, 09 Jun 2015) | 1 line

Added sticky tuning mode.
------------------------------------------------------------------------
r1346 | prog | 2015-06-09 17:27:06 +0200 (Tue, 09 Jun 2015) | 1 line

Fixed click to tune on non-tunable sources
------------------------------------------------------------------------
r1345 | prog | 2015-06-09 17:12:10 +0200 (Tue, 09 Jun 2015) | 1 line

Added additional modes: Center and Free tuning.
------------------------------------------------------------------------
r1344 | prog | 2015-06-09 00:35:23 +0200 (Tue, 09 Jun 2015) | 1 line

Fixed multi-device support
------------------------------------------------------------------------
r1343 | prog | 2015-06-08 23:52:56 +0200 (Mon, 08 Jun 2015) | 1 line

Added more checks for RTLSDR source.
------------------------------------------------------------------------
r1342 | prog | 2015-06-08 23:27:17 +0200 (Mon, 08 Jun 2015) | 3 lines

Revamped the RTLSDR controller to use the new API:
 - Added USB Enum;
 - Added Auto stop when the device is unplugged.
------------------------------------------------------------------------
r1341 | prog | 2015-06-08 19:46:11 +0200 (Mon, 08 Jun 2015) | 1 line

Ported Airspy plugin enhancements to RTLSDR plugin
------------------------------------------------------------------------
r1340 | prog | 2015-06-07 23:33:39 +0200 (Sun, 07 Jun 2015) | 3 lines

Enhanced the Airspy plugin;
Added a button center the current frequency on the spectrum;
A few GUI tweaks.
------------------------------------------------------------------------
r1339 | prog | 2015-06-07 21:07:08 +0200 (Sun, 07 Jun 2015) | 1 line

Enhanced the init behavior
------------------------------------------------------------------------
r1338 | prog | 2015-06-07 16:09:17 +0200 (Sun, 07 Jun 2015) | 5 lines

Added support for RFSPACE CloudIQ and CloudSDR sample rates;
Added new API to control the program from front-end plugins;
Changed the streaming from non-blocking to blocking I/O's.

PSAT Telemetry

Posted on by

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

PSAT Telemetry

Atlas V ULTRASat Objects identified

Posted on by

Ultrasat LauncherAtlas 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-A active again

Posted on by

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.

LghtSail-31052015-0958UTC

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

GRIFEX Update

Posted on by

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.

GRIFEX Battery Temparature

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

Posted on by

O/OREOS Telemetry 28-05-2015 16:53

OOREOS-28052015-1653UTC

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.