FIRSTMOVE – end of mission

First-MOVE On-Board Computer Damaged

As we posted on December 21st 2013, we are not receiving data beacons from First-MOVE anymore. In contrast to the nominal mode in which CW beacons and AX.25 beacons alternate every 60 seconds, we are now hearing only CW beacons every 60 seconds. After trying many different approaches to reset our on-board computer via telecommands we re-analyzed our current options again last week. This analysis resulted in the conclusion, that the on-board software has sustained irreparable damage. The fact that we are receiving CW beacons every 60 seconds indicates, that both the transceiver and the power supply are functioning properly. For the transceiver to return to the 60 second CW beacon mode, it has to be power cycled, since this mode cannot be activated by the on-board software. This means that there was definitively an interruption in the power supply. In case of an interruption, the computer should deactivate the 60 second CW beacon mode as the first task during the boot sequence. As this has obviously not happened, the only conclusion is, that the computer is not getting through the entire boot sequence, probably because it was damaged due to an erroneous write process on the memory chip. Since there is no way to upload new software to First-MOVE we see no possibility to continue the mission and perform the planned experiments. It seems that First-MOVE has become inactive after a very short lifetime. We will still receive the CW beacons, but we will not hear anything but his name.

We would like to take this opportunity to thank all the people who went on this long journey and helped us. Especially the experience of strangers all around the world trying and often succeeding in tracking our satellite has made us very happy. Thank you for your efforts and help!

We will now try to compile all of the experience we have gained, write it down and pass it on to the next generation so a longer and more successful mission can be performed in the future.

Claas Olthoff

FIRSTMOVE beacon

09:15 UTC
MV1b 0x6C 0xE7 0x34 0x01 0xF7 0x48 0x44 0x01 0xD5 0x04 0xC0 0x09 0x21 0x03 0x48 0x03 0x37 0x03 0x02 0x00 0x07 0x00 0x22 0xE7 0x07 0x00 0xC1 0x24 0x41 0x62 0x60 0x60 0xA1 0x00 0x00 0x00 0x00 0x00 0x00 0x20 0x66 0x60 0xA2 0x62 0x20 0x60 0x20 0x12 0x73 0x06 0x40 0x00 0x02 0x02 0x00 0x04 0x21 0x12 0x10 0x05 0x40 0x31 0x71 0x22 0x36 0x30 0x02 0x02 0x00 0x06 0x00 0x00

Battery Temp: 6.5C
Battery Voltage: 8.3V

FIRSTMOVE beacons

MixW decoded 4 packets, ISIS software 3 packets (but only 2 in the log file)

Battery Voltage: 8.11 V
Battery Temp: 11.1 C

21:39:46 MV1b 0x9D 0x46 0xD6 0xC1 0x55 0x48 0x64 0x61 0x44 0x64 0x80 0x69 0x01 0x03 0x0A 0x01 0xF6 0x01 0x00 0x00 0x05 0x00 0x82 0xC5 0x45 0x02 0xA3 0x64 0x43 0x62 0x20 0x20 0x40 0x00 0x00 0x00 0x00 0x00 0x00 0x22 0x26 0x62 0x60 0x22 0x20 0x60 0x60 0x50 0x71 0x46 0x40 0x02 0x00 0x00 0x00 0x76 0x72 0x73 0x51 0x17 0x51 0x53 0x70 0x22 0x36 0x30 0x02 0x02 0x00 0x06 0x00 0x00
21:44:16 MV1b 0x3F 0xC6 0x16 0x01 0x17 0x08 0x24 0x41 0x04 0x44 0xE0 0x69 0x01 0x01 0x08 0x03 0xF6 0x01 0x00 0x00 0x05 0x00 0xE0 0xA5 0x45 0x42 0xE1 0x26 0x43 0x62 0x20 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x62 0x66 0x62 0x20 0x22 0x20 0x20 0x60 0x52 0x71 0x46 0x40 0x02 0x00 0x00 0x00 0x34 0x72 0x13 0x51 0x55 0x73 0x53 0x70 0x22 0x36 0x30 0x02 0x02 0x00 0x06 0x00 0x00

DNEPR launch – TLE lottery update

It seems we have now all 3 objects from the ISIPOD-1 :-)
HINCube, FUNCube and ZACube are very close together

DNEPR OBJECT B
1 39417U 13066B   13338.21518120  .00001612  00000-0  22756-3 0   455
2 39417 097.7994 050.4415 0063837 154.2629 206.1807 14.77139597  1903
DNEPR OBJECT AE
1 39444U 13066AE  13337.74092910  .00002054  00000-0  28807-3 0    12
2 39444 097.7987 049.9810 0063406 155.8156 204.6075 14.77151634   603
DNEPR OBJECT AF -> FUNCube
1 39445U 13066AF  13337.87645984  .00001886  00000-0  26491-3 0    11
2 39445 097.7977 050.1127 0064533 155.6233 204.7939 14.77146225   198

objects Y, Z and AG belong to ISIPOD-2

VELOX
1 39438U 13066Y   13337.76278889  .00001521  00000-0  22571-3 0    52
2 39438 097.7980 049.9526 0075643 154.2108 206.2925 14.74550218  1824
FIRSTMOVE
1 39439U 13066Z   13337.49100478  .00003111  00000-0  45313-3 0    68
2 39439 097.7980 049.6900 0075518 155.2728 205.2142 14.74611850  1749
UWE-3
1 39446U 13066AG  13337.76274885  .00001854  00000-0  27334-3 0    10
2 39446 097.7975 049.9510 0075536 154.3318 206.1661 14.74558905   607

MOVE-1 telemetry

20:15 UTC could decode 4 PSK beacons

[Mon Dec 02 22:18:30 CET 2013]
FM: MOVE1 -0 TO: LRT1 -0
MV1b 0x9D 0x24 0x55 0x21 0x97 0xC8 0x24 0x41 0x64 0x64 0x80 0x69 0x01 0x01 0x0A 0x03 0xB5 0x01 0x00 0x00 0x05 0x00 0xC2 0xE7 0x65 0x60 0xC1 0x24 0x01 0x62 0x20 0x20 0x42 0x00 0x00 0x00 0x00 0x00 0x00 0x62 0x66 0x62 0x22 0x60 0x60 0x60 0x20 0x51 0x70 0x44 0x42 0x02 0x02 0x00 0x00 0x35 0x53 0x11 0x50 0x14 0x51 0x52 0x73 0x22 0x36 0x30 0x02 0x02 0x00 0x06 0x00 0x00

[Mon Dec 02 22:23:34 CET 2013]
FM: MOVE1 -0 TO: LRT1 -0
MV1b 0x5F 0xC6 0x75 0x41 0x14 0x68 0x04 0x01 0x27 0x44 0xE0 0x69 0x01 0x43 0x08 0x01 0x95 0x01 0x00 0x00 0x05 0x00 0xC0 0xC7 0x47 0x42 0xE1 0x26 0x01 0x20 0x20 0x20 0x62 0x00 0x00 0x00 0x00 0x00 0x00 0x22 0x26 0x62 0x62 0x20 0x20 0x20 0x60 0x53 0x70 0x44 0x42 0x02 0x02 0x00 0x00 0x74 0x50 0x10 0x11 0x56 0x73 0x52 0x73 0x22 0x36 0x30 0x02 0x02 0x00 0x06 0x00 0x00

move_velox_02122013
tracked with Object Y – so it seems FIRSTMOVE is not Y, VELOX-PII fits better

FIRSTMOVE-1 telemetry

01:15 UTC over Japan
fm MOVE1 -0  to LRT1  -0  ctl UI pid f0 4D 56 31 62 DD 25 05 C1 E5 88 E4 81 F7 C4 40 09 21 01 4A 01 25 01 00 00 05 00 A0 25 25 20 A1 44 43 62 20 60 A0 00 00 00 00 00 00 62 E6 60 A2 60 A0 20 60 43 72 06 42 02 02 02 00 66 20 10 11 75 11 70 60 22 36 30 02 02 00 06 00 00

fm MOVE1 -0  to LRT1  -0  ctl UI pid f0 4D 56 31 62 6D 57 15 E1 45 28 C5 E1 A7 C4 00 09 21 03 4A 01 45 01 00 00 05 00 A0 67 47 20 A3 44 43 60 20 60 70 00 00 00 00 00 00 E2 A6 A0 62 20 A0 60 60 13 72 06 42 02 02 02 00 46 32 32 31 57 41 70 62 22 36 30 02 02 00 06 00 00