AO-27 update

Turned on low power during first pass. Had good tone, received a few TLM frames but then lost commanding of it as it came over the US. Seems to have major interference on uplink while over the US.
It faded mid pass and was not heard from for the rest of the pass. Sent off commands in the blind. Don’t know if the TX turned off or not.
The good news is it was at least heard from after last weekend’s problems.
– Michael, N3UC

AO-27 not yet been recovered

It has not yet been recovered. The command team turned the transmitter on to test it out on June 28th, but they still need to upload the secondary bootloader and then the high level code necessary to operate the satellite.
The issue in the past has been that the satellite crashes when they try to run high level code. We will see if they’ve managed to work around that problem (probably radiation damage to a section of the satellite’s memory).

Paul, N8HM

AO-27 status

We tried to do a restart of the high level code today which did not work out. We left the transmitter on to drain the batteries in hopes of clearing any latch ups.
On the next pass, we could turn the bird back on so it survived the battery draining. The modem problem was back and we got that cleared.
Its back up on the secondary bootloader.
Michael, N3UC

AO-27 status

The AFSK modem problem has come back. After Woking the night passes the last few nights we have recovered from that problem.AO-27 is running on its secondary bootloader, this is the one we can upload high level code with.
We had a great commanding night and begun to upload the kernal today.
We can report than the entire kernal is now uploaded. EOS uploading will start next pass.

Michael, N3UC and James N3UCC