Fox Telemetry Decoder

Fox Telemetry Decoder Software Version 1.0 is Available for Download.

I downloaded the software to see if everything is working. I did some testing an debugging on my side. Except of the audio monitor function I got everything working with the help of the available AF and IQ recordings. The software is looking great and I am ready to received and decode the FOX satellites.

FoxTelem

Version 1.0 of the FoxTelem software, the Fox Telemetry Decoder is being
released to enable setup, testing, and debugging of your Fox-1A ground
station prior to the launch of the satellite. FoxTelem is used to
demodulate, store and analyze telemetry data from AMSAT’s Fox series of
Cube Sats.

Fox-1 satellites include two telemetry formats:

  • Slow Speed, also called Data Under Voice (DUV) is 200 bps FSK data
    sent at the same time as the transponder audio. Whenever the trans-
    mitter is on, data is being sent. This happens during beacons and
    during live QSOs.
  • High Speed is 9600 bps FSK sent instead of the transponder. This is
    used for data intensive experiments such as the Virginia Tech Camera.
    This is only active when commanded from the ground. You can recognize
    High Speed because it sounds like an old school computer modem.

FoxTelem will receive and store both formats assuming you can feed it audio
that does not have the frequencies below 200 Hz filtered. For High Speed,
the audio must also extend to include the full 9600bps bandwidth of the FM
signal. For both modes this is best achieved from a Software Defined Radio
or from the 9600 bps packet port of some radios. The FoxTelem User Guide
provides more details.

Source: FoxTelem Software for Windows, Mac, & Linux

XW-2 (CAS3) launched and active

XW2-2 (CAS3) Satellites launched and active.

I was able to decode FSK signals after analyzing the recorded IQ data, real-time CW and heard some signals on the transponders.

from BJ1SG to CQ: 
   1 > EB 90 6A 5E B9 8F 57 54 54 21 2D 65 80 CF B4 5B 70 56 56 4E 
  21 > 4E 4C 4D 00 38 00 00 00 05 00 00 00 5C 00 00 00 06 00 03 0C 
  41 > 03 18 03 25 03 34 03 20 03 0C 02 FD 02 EE 02 94 02 26 01 F4 
  61 > 03 E8 03 20 03 20 03 0C 00 67 4C 00 60 95 AA AA AA AA AA AA 
  81 > AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA 
 101 > AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA 
 121 > AA AA AA AA AA AA AA AA

from BJ1SF to CQ: 
   1 > EB 90 69 62 B7 96 58 57 57 21 16 65 40 E5 AB 5D 78 58 58 4D 
  21 > 50 4C 4D 00 38 00 00 00 00 00 00 00 5C 00 00 00 01 00 03 0C 
  41 > 03 18 03 25 03 34 03 20 03 0C 02 FD 02 EE 02 94 02 26 01 F4 
  61 > 03 E8 03 20 03 20 03 0C 00 57 7B 00 49 A0 AA AA AA AA AA AA 
  81 > AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA 
 101 > AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA 
 121 > AA AA AA AA AA AA AA AA
BJ1SG DFH XW2 XW2 AAAA IVBI KF6I AIN4 ITDU URVU 6ICK ANIM 6UI6 I64E 4E4E 4ETT TTTT TTTT TFN4 TTTT 4CT4 6KKM 6EEH DDDD DDDD DDDD DDDD DDDD CAMSAT CAMSAT

BJ1SG DFH XW2 XW2 AAAA IUAF KF6M AIN4 4FEI URNC .... IA4D RAI6 I6IC ..UA VBTT TTTT TTTT TKN4 TTTT 4CT4 6KKM DDDD DDDD DDDD DDDD DDDD DDDD CAMSAT CAMSAT 
BJ1SG DFH XW2 XW2 AAAA ..BI KFKT AIN4 ITET URAU 6ITK NK4E RUI6 I64C 4F4B 4CTT TTTT TTTT TTN4 TTTT 4CT4 6K4M DDDD DDDD DDDD DDDD DDDD DDDD CAMSAT CAMSAT
BJ1SG DFH XW2 XW2 AAAA IRBC KBKI AINK IUE4 URN6 64CK BM6V UVIM IM4E IT4C 4ETT TTTT TTTT TMN4 TTTT KBT4 IK4M DDDD DDDD DDDD DDDD DDDD DDDD CAMSAI CAMSAT
BJ1SF DFH XW2 XW2 AAAA IUBC KBKI AINK IUEI URUM 6IMK AMIA KVIM IM4F 4E4E 4FTT TTTT TTTT TUN4 TTTT KBT4 IKIT DDDD DDDD DDDD DDDD DDDD DDDD CAMSAT CAMSAT

BJ1SE DFH XW2 XW2 AAA RTT RUR RUR RUV TMT R6I RNT RUR TTT RKM TIU FAR TTT TTT FET TTT TTI TTT TTT K4K VTT CAMSAT CAMSAT
BJ1SD DFH XW2 XW2 AAA RTT RUT RUT RUI TNV R6V RMN RUR TTT RKI TIT EUR TTT TTT EDT TET TTT TTT TTT 6VK VTT CAMSAT CAMSAT

XW-2-CAR-CW-TRSP

XW-2(CAS-3) Launch information

XW-2 (CAS-3)

Update: The launch is postponed by one day due to technical reasons, next launch window will be at 19-09-2015 23:00:00 UTC.

Launch time: 18-09-2015 on 23:00:00 UTC
Satellite rocket separation: 18-09-2015 at 23:15:14 UTC

XW-2
1 99999U          15262.96885748  .00004985  00000-0  28395-3 0 00005
2 99999 097.4712 270.8252 0010383 266.0522 270.6644 15.12847565000015

SatPC32 doppler.sqf

XW-2A,145640,0,FM,FM,NOR,0,0,XW-2A Telemetry FSK
XW-2A,145660.08,0,CW,CW,NOR,0,0,XW-2A Telemetry CW
XW-2A,145675,435040,USB,LSB,REV,0,0,XW-2A Transponder
;
XW-2B,145705,0,FM,FM,NOR,0,0,XW-2B Telemetry FSK
XW-2B,145725,0,CW,CW,NOR,0,0,XW-2B Telemetry CW
XW-2B,145740,435100,USB,LSB,REV,0,0,XW-2B Transponder
;
XW-2C,145770,0,FM,FM,NOR,0,0,XW-2C Telemetry FSK
XW-2C,145790,0,CW,CW,NOR,0,0,XW-2C Telemetry CW
XW-2C,145805,435160,USB,LSB,REV,0,0,XW-2C Transponder
;
XW-2D,145835,0,FM,FM,NOR,0,0,XW-2D Telemetry FSK
XW-2D,145855,0,CW,CW,NOR,0,0,XW-2D Telemetry CW
XW-2D,145870,435220,USB,LSB,REV,0,0,XW-2D Transponder
;
XW-2E,145890,0,FM,FM,NOR,0,0,XW-2E Telemetry FSK
XW-2E,145910,0,CW,CW,NOR,0,0,XW-2E Telemetry CW
XW-2E,145925,435280,USB,LSB,REV,0,0,XW-2E Transponder
;
XW-2F,145955,0,FM,FM,NOR,0,0,XW-2F Telemetry FSK
XW-2F,145975,0,CW,CW,NOR,0,0,XW-2F Telemetry CW
XW-2F,145990,435340,USB,LSB,REV,0,0,XW-2F Transponder

Source: Alan Kung, BA1DU (Amsat-BB)

XW-2 Rocket separation 18-09-2015 23:15 UTC (19-09-2015 01:15:00 CEST)

XW-2-separation

XW-2 First pass over my ground-station 19-09-2015 07:17:59 CEST

XW-2-NLD

Major SDRSharp update

SDRSharp LogoSDR# is moving to .NET 4.6

We have been relying on the .NET Framework 3.5 for quite some time until it’s no longer installed by default into the new operating systems. Microsoft also provides minimalist support of this version of the Framework on Windows 10 which handicapped the core and plugin developers in many ways. This also resulted in obscure bugs in the user base. So we moved recently the entire code base to the .NET 4.6 in order to refresh the software and make it compatible with modern operating systems like Windows 10.

This has many implications:

  • Better performance
  • Better programming API
  • Support of Windows 10
  • Support of Linux and Mac with Mono 4.0 and up
  • End of support of Windows XP and Vista
  • End of support of the ExtIO interface (not portable)

We coordinated this migration with all the plugins and front-ends developers so no body misses the boat.

The installation procedure has also changed and now the main package contains a batch file to download the dependencies required to run RTL-SDR.

This might be disturbing for a few, but the overall impact was judged positive and a better investment for the future, especially with the new API offered by .NET 4.6.

Source: Yahoo SDR# Team

Posted in SDR

Update GRIFEX operations

Update: 12-08-2015

The GRIFEX operations team just wanted to give you a quick update on operations and thank you for your continued support of the mission.

First off, we’ve now had 30 successful MARINA run completions at various locations across the US and Canada. Many of these images have unfortunately been saturated, but we did downlink a few images with interesting features. We are still waiting on confirmation from JPL of a good image before we release these images, but it appears as though the most interesting ones come from mid-latitudes in the continental US (Arizona or Virginia latitudes).

In addition to MARINA data, we’ve also been downlinking telemetry to ensure the continued health of the satellite, as per usual.

On the Ann Arbor passes during which we are not downlinking, we’ve been experimenting with the magnetorquers on GRIFEX. GRIFEX has three coils of wires, each aligned with one axis of the spacecraft (X, Y, or Z). When we run current through these wires, a magnetic dipole is generated that interacts with Earth’s magnetic field to alter GRIFEX’s attitude. Thus far, we have just been “pulsing” the coils, i.e. running current through them for only 10 seconds at a time, to make sure they are functioning properly and that the magnetometers record an appropriate change in magnetic field. You can see the results of our experiments in the three graphs below:

12082015-01

12082015-02

12082015-03

You’ll note that the X and Y coils draw much less current than the Z coil does and generate a much weaker change in magnetic field – this is because the Z coil needs to be strong enough to overcome the permanent magnet on GRIFEX (which is aligned with the Z axis of the spacecraft) if necessary. Thus far, we have only experimented with running current in one direction through the magnetorquer coils, but we plan on completing “pulse” tests with current running the opposite direction before we attempt full attitude control of the spacecraft.

Another event to note is that GRIFEX stopped beaconing sometime between 7/30/2015 23:45:00 UTC and 7/31/2015 00:51:00 UTC. At the 00:51:00 UTC pass over Ann Arbor, we attempted to reset the spacecraft, but to no avail; GRIFEX was neither beaconing nor responding to any commands we sent. GRIFEX remained silent throughout 7/31/2015, but luckily a watchdog timeout reset the spacecraft and we started picking up beacons again on 8/1/2015 13:55:00 UTC. We are still unsure of what caused this anomalous behavior, but we have been downlinking telemetry from the time period during which GRIFEX was silent (beacons were still being created and saved on the spacecraft) to debug the problem and ensure it does not happen again. A big shout out to the hams that were tracking GRIFEX during this worrisome time and alerting us to the fact that it was silent! We are all very glad that the GRIFEX mission can continue now that the spacecraft is beaconing again.

Thanks again for all your support.

Valerie Chen (KG7RGV)