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)

GRIFEX Update

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

GRIFEX Telemetry 15-02-2015

GRIFEX Telemetry 15-02-2015 14:46 – 18:04 UTC. It seems that the rotation over the Y axis is stabilizing.

grifex_grifex_pe0sat_15022015_1159

GRIFEX-axisIf you wonder how to project the axises on the satellite, have a look at the image on the right. This gives you an idea what the data collected is possibly telling us.

Elana-X Cubesats Active

All Elana-X Cubesats are received, only EXOCube is still not 100% sure because data is seen in the SDR spectrum but the signals are very weak.

I have made two IQ recordings, one from 31-01-2015 just after GRIFEX enabled its beacon and early morning 01-02-2015. The first one is the pass-band where Firebird-2 FU3 and GRIFEX are in and the second file is Firebird-2 FU4 and EXOCube.

FB-2 FU4 and EXOCube 01-02-2015 07:48 UTC

Firebird-II FU4 Telemetry 01-02-2015 07:48 UTC

1:Fm K7MSU To K7MSU
   1 > C0 00 96 6E 9A A6 AA 40 60 96 6E 9A A6 AA 40 E1 03 F0 DB DC 
  21 > 55 04 55 01 00 06 00 00 54 9F 03 41 00 02 00 00 2D 2C 00 01 
  41 > DE A8 03 3A 00 00 01 DE 15 00 00 2D 1E 03 39 03 39 00 00 00 
  61 > 00 00 00 00 03 01 D0 02 7F 02 87 02 15 02 0F 00 07 00 08 01 
  81 > 8D 01 8F 03 AC 02 6B 02 65 02 6E 02 69 01 C8 01 D4 02 69 00 
 101 > F9 00 0D 00 00 00 00 00 3E 00 2E 00 05 00 19 00 19 00 18 00 
 121 > 17 00 16 00 15 00 B6 00 17 1E A0 0E E8 00 00 00 00 00 00 00 
 141 > 00 00 8C 00 1C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
 161 > 00 03 1B 13 41 02 6D 02 67 02 6A 02 6C 02 64 02 65 7F D5 7F 
 181 > FA 80 26 80 26 80 1E 7F ED BB 94 DB DC C0

Firebird-II FU3 Telemetry 31-01-2015 17:13 UTC

from K7MSU to K7MSU
000 > C0 00 96 6E 9A A6 AA 40 60 96 6E 9A A6 AA 40 E1 03 F0 DB DC 
020 > AA 04 AA 01 00 0E 00 00 13 8C 0E 0B 05 00 0A 03 34 00 20 7B 
040 > 0A 00 83 00 00 72 6B 01 01 00 02 00 00 00 00 00 4E 02 37 02 
060 > 29 00 00 00 00 01 7A 00 6C 00 0F 00 00 00 02 AA 00 00 00 00 
080 > 00 00 00 00 03 52 00 01 00 00 00 01 06 06 00 00 10 9F 00 00 
100 > 00 06 2E 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 01 
120 > 1A 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
140 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
160 > 00 00 00 00 00 00 00 00 00 00 EF 12 DB DC C0

GRIFEX Telemetry 31-01-2015 17:49 UTC

from CQ to KD8SPS
   1 > C0 00 96 88 70 A6 A0 A6 60 86 A2 40 40 40 40 E1 03 F0 AB CD 
  21 > 00 00 00 42 03 F5 00 B4 75 16 10 00 00 00 00 1A 00 10 00 06 
  41 > 00 01 00 23 00 37 11 EE 7B C9 71 01 CA CB 00 00 7E 2A 00 00 
  61 > 12 00 1B 00 71 00 00 00 00 28 08 00 00 29 06 21 06 F9 0C 5D 
  81 > 00 27 00 F1 0C B8 0E 0C 00 A5 0E E3 05 47 06 B2 0E 0E 00 63 
 101 > 0D 1C 00 17 00 F9 0C 8B 00 54 00 14 06 63 0D 80 00 F6 0C AF 
 121 > 00 DB DD 00 0E 00 2F 02 0D 00 00 06 01 06 66 0A C4 00 03 0F 
 141 > 41 00 FB 05 FF 05 A8 00 02 00 2A 02 07 00 0D 06 0D 06 97 0A 
 161 > F3 00 2D 0F 53 00 05 06 09 06 01 FC 4E 06 4B 06 4F 06 00 DB 
 181 > DC 1E 00 5A 00 53 FF 65 00 C2 FF 12 00 99 00 AE FF 45 00 E8 
 201 > 00 F6 FF DB DD 00 4A 0B 40 0B 39 0A 27 0A 36 0A 41 0A BE 0A 
 221 > C4 0A 36 06 BE 09 03 00 00 00 88 33 88 33 4C 00 00 00 00 00 
 241 > 00 00 00 E3 03 00 00 01 00 FF FF FF FF FF FF FF FF FF FF FF 
 261 > 24 94 B0 15 1C 40 C0

Based on the launch sequence and the new TLE made available via Space-track I will be using the following Kepler data for the upcoming passes.

FIREBIRD-2-FU3
1 40377U 15003B   15032.23998870 -.00000111  00000-0  00000+0 0    47
2 40377 099.1229 040.8394 0160422 338.5296 020.9352 15.04145247    97
FIREBIRD-2-FU4
1 40378U 15003C   15032.23997153 -.00000113  00000-0  00000+0 0    43
2 40378 099.1283 040.8489 0167282 337.6984 021.7000 15.04199923    97
GRIFEX
1 40379U 15003D   15032.24001357 -.00000113  00000-0  00000+0 0    47
2 40379 099.1258 040.8456 0166294 338.7028 020.7326 15.04106125    99
EXOCUBE
1 40380U 15003E   15032.17351219 -.00000113  00000-0  00000+0 0    46
2 40380 099.1346 040.7708 0166270 338.5236 020.9052 15.04039583    81

EXOCube Beacon 3OXWith the help of the image from the IQ analysis on the top of this message, Logan Sisca found the following beacon message. Well done.

GRIFEX active and decoded

With the help of the recorded IQ file that can be downloaded at the following location, I was able to decode and send a couple of kiss packets to the GRIFEX telemetry server. Below you can see the data decoded by the MXL Ground Station Client.

GRIFEX-GS-client

2015-01-31 17:49:22.300 UTC: [267 Bytes KISS Frame (without CRC)]
   1 > C0 00 96 88 70 A6 A0 A6 60 86 A2 40 40 40 40 E1 03 F0 AB CD 
  21 > 00 00 00 42 03 F5 00 B4 75 16 10 00 00 00 00 1A 00 10 00 06 
  41 > 00 01 00 23 00 37 11 EE 7B C9 71 01 CA CB 00 00 7E 2A 00 00 
  61 > 12 00 1B 00 71 00 00 00 00 28 08 00 00 29 06 21 06 F9 0C 5D 
  81 > 00 27 00 F1 0C B8 0E 0C 00 A5 0E E3 05 47 06 B2 0E 0E 00 63 
 101 > 0D 1C 00 17 00 F9 0C 8B 00 54 00 14 06 63 0D 80 00 F6 0C AF 
 121 > 00 DB DD 00 0E 00 2F 02 0D 00 00 06 01 06 66 0A C4 00 03 0F 
 141 > 41 00 FB 05 FF 05 A8 00 02 00 2A 02 07 00 0D 06 0D 06 97 0A 
 161 > F3 00 2D 0F 53 00 05 06 09 06 01 FC 4E 06 4B 06 4F 06 00 DB 
 181 > DC 1E 00 5A 00 53 FF 65 00 C2 FF 12 00 99 00 AE FF 45 00 E8 
 201 > 00 F6 FF DB DD 00 4A 0B 40 0B 39 0A 27 0A 36 0A 41 0A BE 0A 
 221 > C4 0A 36 06 BE 09 03 00 00 00 88 33 88 33 4C 00 00 00 00 00 
 241 > 00 00 00 E3 03 00 00 01 00 FF FF FF FF FF FF FF FF FF FF FF 
 261 > 24 94 B0 15 1C 40 C0

UZ7HO-kiss-serverI used the UZ7HO G3RUH 1.7 beta sound modem software and enabled the Kiss server on port 9100. After that I configure the config.props file that is part of the MXL Ground Station Client software to use the kiss server port. Below the config.props I used.

Don’t use the tcp to serial option that comes with the GS client software. There is a direct connection between the GS client and UZ7HO via in my example port 9100.

radio.1.name=Radio
radio.1.address=localhost
radio.1.port=9100
radio.1.type=KISS
radio.1.tncport=1

client.callsign=PE0SAT
client.id=PE0SAT_GS
server.address=mxlab.engin.umich.edu
server.port=12805

librap.SID=50
librap.PID=0

api.crafts=https://mxl-ops.engin.umich.edu/api/craft?count=25
api.command=https://mxl-ops.engin.umich.edu/api/commands/
api.raps=https://mxl-ops.engin.umich.edu/api/raps

Good luck decoding GRIFEX with this setup.