<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<AmsatList>
    <Satellites>
        <Name>First-MOVE</Name>
        <NasaID>39439</NasaID>
        <InternationalID>2013-066Z</InternationalID>
        <Status>Operational</Status>
        <IARUCoordination>
            <Coordinated>true</Coordinated>
        </IARUCoordination>
        <LaunchData>
            <LaunchDate>2013-11-21</LaunchDate>
            <LaunchingSite>Orenburg, Russia</LaunchingSite>
        </LaunchData>
        <SatelliteInformationStatus>Verified</SatelliteInformationStatus>
        <UpdateDate>2020-05-24+02:00</UpdateDate>
        <Information>
			<Title> IARU Coordination   </Title>
			<Value>http://www.amsatuk.me.uk/iaru/finished_detail.php?serialnum=125</Value>
		<Description> 	</Description>
			</Information>
        <Information>
			<Title> Mission information</Title>
			<Value>https://www.pe0sat.vgnet.nl/satellite/cube-nano-picosats/first-move/</Value>
		<Description> 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.	</Description>
			
			</Information>
        <RadioData>
            <Beacons>
                <Name>Main</Name>
                <Frequency>145970000</Frequency>
                <Modes>
                    <Mode>BPSK</Mode>
                    <Speed>1200</Speed>
                </Modes>
                <Modes>
                    <Mode>CW</Mode>
                </Modes>
                <CallSign>MOVE1</CallSign>
            </Beacons>
            <Transponders>
                <Name>Repeater</Name>
                <FrequencyUplink>
                    <FrequencyBegin>435520000</FrequencyBegin>
                </FrequencyUplink>
                <FrequencyDownlink>
                    <FrequencyBegin>145970000</FrequencyBegin>
                </FrequencyDownlink>
                <Mode></Mode>
            </Transponders>
        </RadioData>
    </Satellites>
</AmsatList>
