CubeBug-1 status

Hi All, I can confirm that last night here (morning likely over there) we sucessfuly changed it to 9600 bps, so maybe you thought you missed it, but it was there beaconing at 9600bps.

This will only last until it resets itself (either 16hrs timer or powerdown). I will continue to try to switch it to 9600, as we want to verify whether this is a better configuration or not, so please, if you happen to see it, let me know.

Uptime: 3h59m29s, Mode: SURVIVAL
FreeHeapSize: 13320 bytes [0x00003408]
Power: I2C Error
Thermal: I2C Error
Last Seen Seq: 3, Next Beacon Enable: 0
Antenna count: 16, deploy: false [0x10]
Magnetometer (X, Y, Z): (323,600, -323,400, -294,400) [milligauss] Payload length: 0

As I said, the commands from the GS are at 17s intervals, a few each time. The satellite is beaconing at 1200 bps when it starts, around the middle it changes to 9600 bps, it immediately sends around 10 packets at 9600 and then beacons at the regular 10s-30s intervals.

Date and Time: 18-07-2013 20:36 - 20:47 UTC
Object       : 2013-018D
Max elevation: 31 degree
Azimuth      : 134 - 353 degree
Polarization : LHCP Strongest
Signal       : max 10 db above noise
Frequency    : 437.438300 MHz FM +/- doppler
Status       : Active
Remark       : Very strange TX ritme and very weak

Excellent to know it’s back on! again, we’ll try to switch to 9600 in the next passes, I think there are some chances we can make it at 04:15 UTC, if it’s on…

Until I can see the IQ file I can’t comment on the “Very strange TX ritme and very weak”, but it sounds a lot like the satellite is in low power mode, we’ve only seen it once, and it’s consistent with the fact that it has just come back from sleeping. If this is the case, it’s, at this point, excellent news. It means the I2C bus is working :) and if we manage to get some telemetry we can see some real info

Leave a Reply