Full manual: The Altus Metrum System: An Owner’s Manual for Altus Metrum Rocketry Electronics

RF Link

To interact with the telmega you will need to use the TeleBT to connect over rf link. There is also a way to do it directly through micro-usb but for some reason this never works. Connect the teleBT to a laptop and launch AltOS. If it can’t find the teleBT as a device, the battery is probably just very dead and it might need to charge for a little while.

When using the RF link it is important to know which mode the flight computer is in. The Telemetrum and Telemega have two starup modes: Idle and Pad.

Idle Mode

The computer enters this mode if it is powered on while turned sideways. When in this mode the computer is only receiving signals so you can use Configure Altimeter , Save Flight Data, Monitor Idle, and Fire Igniter. While in this mode the board will only beep on startup. To connect to the computer you will need to use the correct channel and callsign. If you don't know what channel or callsign the computer is set to, you can find out by powering it on in Flight Mode, then using Scan Channels. The ground station callsign can be changed in Configure Altos UI, and the channel can be changed in Configure Ground Station. The factory default should be using channel 0 (434.550 Mhz) and callsign N0CALL.

Configure Altimeter

Can change callsign and channel from here, along with other settings.

Use the Reboot button on the Configure Flight Computer menu to restart the board. If the orientation is correct this can allow switching from Idle to Pad mode from a distance.

Extra Event Pyro Configuration

For triggering pyros for other events, such as staging.

Pad Mode

The computer enters this mode if it is powered on while pointing up. When in this mode the computer will only transmit signals, not receive them. While is this mode you can use Scan Channels to find the right computer and Monitor Flight to view the data. While in the mode the board will beep frequently (a series of beeps over five seconds).

Data table

Beeping

In the description of the beeping pattern, “dit” means a short beep while "dah" means a long beep (three times as long). “Brap” means a long dissonant tone.

Mode Indicator Beeps

Mode Name	Abbreviation	Beeps	Description
Startup	S	battery voltage in decivolts	Calibrating sensors, detecting orientation.
Idle	I	dit dit	Ready to accept commands over USB or radio link.
Pad	P	dit dah dah dit	Waiting for launch. Not listening for commands.
Boost	B	dah dit dit dit	Accelerating upwards.
Fast	F	dit dit dah dit	Decelerating, but moving faster than 200m/s.
Coast	C	dah dit dah dit	Decelerating, moving slower than 200m/s
Drogue	D	dah dit dit	Descending after apogee. Above main height.
Main	M	dah dah	Descending. Below main height.
Landed	L	dit dah dit dit	Stable altitude for at least ten seconds.
Sensor error	X	dah dit dit dah	Error detected during sensor calibration.

Here’s a summary of all of the Pad and Idle mode indications. In Idle mode, you’ll hear one of these just once after the two short dits indicating idle mode. In Pad mode, after the dit dah dah dit indicating Pad mode, you’ll hear these once every five seconds.

Idle and Pad Mode Beeps

Name	Beeps	Description

Name	Beeps	Description
Neither	brap	No continuity detected on either apogee or main igniters.
Apogee	dit	Continuity detected only on apogee igniter.
Main	dit dit	Continuity detected only on main igniter.
Both	dit dit dit	Continuity detected on both igniters.
Storage Full	warble	On-board data logging storage is full. This will not prevent the flight computer from safely controlling the flight or transmitting telemetry signals, but no record of the flight will be stored in on-board flash.
Additional Igniters	four very short beeps	Continuity indication for the additional pyro channels on TeleMega, EasyMega and EasyTimer. One high tone for no continuity, one low tone for continuity. On TeleMega and EasyMegay, these are produced after the continuity indicators for the two primary igniter channels.