The Altus Metrum System

Revision History

Revision 1.2.1

21 May 2013

+ Updated for software version 1.2. Version 1.2 adds support + for TeleBT and AltosDroid. It also adds a few minor features + and fixes bugs in AltosUI and the AltOS firmware. +

Revision 1.2

18 April 2013

+ Updated for software version 1.2. Version 1.2 adds support + for MicroPeak and the MicroPeak USB interface. +

Revision 1.1.1

16 September 2012

Updated for software version 1.1.1 Version 1.1.1 fixes a few bugs found in version 1.1.

Revision 1.1

13 September 2012

@@ -19,7 +26,7 @@ Updated for software version 0.9. Note that 0.9 represents a telemetry format change, meaning both ends of a link (TeleMetrum and TeleDongle) must be updated or communications will fail. -

Revision 0.8

24 November 2010

Updated for software version 0.8

AltOS Telemetry

Packet Definitions

Keith Packard

+AltOS Telemetry

AltOS Telemetry

Packet Definitions

Keith Packard

This document is released under the terms of the Creative Commons ShareAlike 3.0 license. -

Revision History
Revision 0.1	01 July 2011
Initial content

Table of Contents

1. Packet Format Design

2. Packet Formats

2.1. Packet Header
2.2. Sensor Data
2.3. Configuration Data
2.4. GPS Location
2.5. GPS Satellite Data

3. Data Transmission

3.1. Modulation Scheme
3.2. Error Correction

4. TeleDongle packet format

5. History and Motivation

1. Packet Format Design

Revision History
Revision 0.1	01 July 2011
Initial content

Table of Contents

1. Packet Format Design

2. Packet Formats

2.1. Packet Header
2.2. Sensor Data
2.3. Configuration Data
2.4. GPS Location
2.5. GPS Satellite Data

3. Data Transmission

3.1. Modulation Scheme
3.2. Error Correction

4. TeleDongle packet format

5. History and Motivation

1. Packet Format Design

AltOS telemetry data is split into multiple different packets, all the same size, but each includs an identifier so that the ground station can distinguish among different types. A single @@ -22,14 +22,14 @@ All packet types start with a five byte header which encodes the device serial number, device clock value and the packet type. The remaining 27 bytes encode type-specific data. -

2. Packet Formats

This section first defines the packet header common to all packets and then the per-packet data layout. -

2.1. Packet Header

Table 1. Telemetry Packet Header

Offset	Data Type	Name	Description
0	uint16_t	serial	Device serial Number
2	uint16_t	tick	Device time in 100ths of a second
4	uint8_t	type	Packet type
5

2.1. Packet Header

Table 1. Telemetry Packet Header

Offset	Data Type	Name	Description
0	uint16_t	serial	Device serial Number
2	uint16_t	tick	Device time in 100ths of a second
4	uint8_t	type	Packet type
5

Each packet starts with these five bytes which serve to identify which device has transmitted the packet, when it was transmitted and what the rest of the packet contains. -

2.2. Sensor Data

Type	Description
0x01	TeleMetrum Sensor Data
0x02	TeleMini Sensor Data
0x03	TeleNano Sensor Data

2.2. Sensor Data

Type	Description
0x01	TeleMetrum Sensor Data
0x02	TeleMini Sensor Data
0x03	TeleNano Sensor Data

TeleMetrum, TeleMini and TeleNano share this same packet format for sensor data. Each uses a distinct packet type so that the receiver knows which data values are valid and which @@ -38,63 +38,63 @@ Sensor Data packets are transmitted once per second on the ground, 10 times per second during ascent and once per second during descent and landing -

Table 2. Sensor Packet Contents

Offset	Data Type	Name	Description
5	uint8_t	state	Flight state
6	int16_t	accel	accelerometer (TM only)
8	int16_t	pres	pressure sensor
10	int16_t	temp	temperature sensor
12	int16_t	v_batt	battery voltage
14	int16_t	sense_d	drogue continuity sense (TM/Tm)
16	int16_t	sense_m	main continuity sense (TM/Tm)
18	int16_t	acceleration	m/s² * 16
20	int16_t	speed	m/s * 16
22	int16_t	height	m
24	int16_t	ground_pres	Average barometer reading on ground
26	int16_t	ground_accel	TM
28	int16_t	accel_plus_g	TM
30	int16_t	accel_minus_g	TM
32

2.3. Configuration Data

Type	Description
0x04	Configuration Data

Table 2. Sensor Packet Contents

Offset	Data Type	Name	Description
5	uint8_t	state	Flight state
6	int16_t	accel	accelerometer (TM only)
8	int16_t	pres	pressure sensor
10	int16_t	temp	temperature sensor
12	int16_t	v_batt	battery voltage
14	int16_t	sense_d	drogue continuity sense (TM/Tm)
16	int16_t	sense_m	main continuity sense (TM/Tm)
18	int16_t	acceleration	m/s² * 16
20	int16_t	speed	m/s * 16
22	int16_t	height	m
24	int16_t	ground_pres	Average barometer reading on ground
26	int16_t	ground_accel	TM
28	int16_t	accel_plus_g	TM
30	int16_t	accel_minus_g	TM
32

2.3. Configuration Data

Type	Description
0x04	Configuration Data

This provides a description of the software installed on the flight computer as well as any user-specified configuration data.

Configuration data packets are transmitted once per second during all phases of the flight -

Table 3. Sensor Packet Contents

Offset	Data Type	Name	Description
5	uint8_t	type	Device type
6	uint16_t	flight	Flight number
8	uint8_t	config_major	Config major version
9	uint8_t	config_minor	Config minor version
10	uint16_t	apogee_delay	Apogee deploy delay in seconds
12	uint16_t	main_deploy	Main deploy alt in meters
14	uint16_t	flight_log_max	Maximum flight log size (kB)
16	char	callsign[8]	Radio operator identifier
24	char	version[8]	Software version identifier
32

2.4. GPS Location

Type	Description
0x05	GPS Location

Table 3. Sensor Packet Contents

Offset	Data Type	Name	Description
5	uint8_t	type	Device type
6	uint16_t	flight	Flight number
8	uint8_t	config_major	Config major version
9	uint8_t	config_minor	Config minor version
10	uint16_t	apogee_delay	Apogee deploy delay in seconds
12	uint16_t	main_deploy	Main deploy alt in meters
14	uint16_t	flight_log_max	Maximum flight log size (kB)
16	char	callsign[8]	Radio operator identifier
24	char	version[8]	Software version identifier
32

2.4. GPS Location

Type	Description
0x05	GPS Location

This packet provides all of the information available from the Venus SkyTraq GPS receiver—position, time, speed and precision estimates.

GPS Location packets are transmitted once per second during all phases of the flight -

Table 4. GPS Location Packet Contents

Offset	Data Type	Name	Description
5	uint8_t	flags	See GPS Flags table below
6	int16_t	altitude	m
8	int32_t	latitude	degrees * 10⁷
12	int32_t	longitude	degrees * 10⁷
16	uint8_t	year
17	uint8_t	month
18	uint8_t	day
19	uint8_t	hour
20	uint8_t	minute
21	uint8_t	second
22	uint8_t	pdop	* 5
23	uint8_t	hdop	* 5
24	uint8_t	vdop	* 5
25	uint8_t	mode	See GPS Mode table below
26	uint16_t	ground_speed	cm/s
28	int16_t	climb_rate	cm/s
30	uint8_t	course	/ 2
31	uint8_t	unused[1]
32

Table 4. GPS Location Packet Contents

Offset	Data Type	Name	Description
5	uint8_t	flags	See GPS Flags table below
6	int16_t	altitude	m
8	int32_t	latitude	degrees * 10⁷
12	int32_t	longitude	degrees * 10⁷
16	uint8_t	year
17	uint8_t	month
18	uint8_t	day
19	uint8_t	hour
20	uint8_t	minute
21	uint8_t	second
22	uint8_t	pdop	* 5
23	uint8_t	hdop	* 5
24	uint8_t	vdop	* 5
25	uint8_t	mode	See GPS Mode table below
26	uint16_t	ground_speed	cm/s
28	int16_t	climb_rate	cm/s
30	uint8_t	course	/ 2
31	uint8_t	unused[1]
32

Packed into a one byte field are status flags and the count of satellites used to compute the position fix. Note that this number may be lower than the number of satellites being tracked; the receiver will not use information from satellites with weak signals or which are close enough to the horizon to have significantly degraded position accuracy. -

Table 5. GPS Flags

Bits	Name	Description
0-3	nsats	Number of satellites in solution
4	valid	GPS solution is valid
5	running	GPS receiver is operational
6	date_valid	Reported date is valid
7	course_valid	ground speed, course and climb rates are valid

Table 5. GPS Flags

Bits	Name	Description
0-3	nsats	Number of satellites in solution
4	valid	GPS solution is valid
5	running	GPS receiver is operational
6	date_valid	Reported date is valid
7	course_valid	ground speed, course and climb rates are valid

Here are all of the valid GPS operational modes. Altus Metrum products will only ever report 'N' (not valid), 'A' (Autonomous) modes or 'E' (Estimated). The remaining modes are either testing modes or require additional data. -

Table 6. GPS Mode

Mode

Name

Decsription

Not Valid

All data are invalid

Autonomous mode

Data are derived from satellite data

Differential Mode

Table 6. GPS Mode

Mode	Name	Decsription
N	Not Valid	All data are invalid
A	Autonomous mode	Data are derived from satellite data
D	Differential Mode	Data are augmented with differential data from a known ground station. The SkyTraq unit in TeleMetrum does not support this mode
E	Estimated	Data are estimated using dead reckoning from the last known data -
M	Manual	Data were entered manually
S	Simulated	GPS receiver testing mode

2.5. GPS Satellite Data

Type	Description
0x06	GPS Satellite Data

Manual

Data were entered manually

Simulated

GPS receiver testing mode

2.5. GPS Satellite Data

Type	Description
0x06	GPS Satellite Data

This packet provides space vehicle identifiers and signal quality information in the form of a C/N1 number for up to 12 satellites. The order of the svids is not specified.

GPS Satellite data are transmitted once per second during all phases of the flight. -

Table 7. GPS Satellite Data Contents

Offset	Data Type	Name	Description
5	uint8_t	channels	Number of reported satellite information
6	sat_info_t	sats[12]	See Per-Satellite data table below
30	uint8_t	unused[2]
32

Table 8. GPS Per-Satellite data (sat_info_t)

Offset	Data Type	Name	Description
0	uint8_t	svid	Space Vehicle Identifier
1	uint8_t	c_n_1	C/N1 signal quality indicator
2

3. Data Transmission

Table 7. GPS Satellite Data Contents

Offset	Data Type	Name	Description
5	uint8_t	channels	Number of reported satellite information
6	sat_info_t	sats[12]	See Per-Satellite data table below
30	uint8_t	unused[2]
32

Table 8. GPS Per-Satellite data (sat_info_t)

Offset	Data Type	Name	Description
0	uint8_t	svid	Space Vehicle Identifier
1	uint8_t	c_n_1	C/N1 signal quality indicator
2

3. Data Transmission

Altus Metrum devices use the Texas Instruments CC1111 microcontroller which includes an integrated sub-GHz digital transceiver. This transceiver is used to both transmit and receive the telemetry packets. This section discusses what modulation scheme is used and how this device is configured. -

3.1. Modulation Scheme

Texas Instruments provides a tool for computing modulation parameters given a desired modulation format and basic bit rate. For AltOS, the basic bit rate was specified as 38 kBaud, resulting in the following signal parmeters: -

Table 9.

Parameter	Value	Description
Modulation	GFSK	Gaussian Frequency Shift Keying
Deviation	20.507812 kHz	Frequency modulation
Data rate	38.360596 kBaud	Raw bit rate
RX Filter Bandwidth	93.75 kHz	Receiver Band pass filter bandwidth
IF Frequency	140.62 kHz	Receiver intermediate frequency

3.2. Error Correction

Table 9.

Parameter	Value	Description
Modulation	GFSK	Gaussian Frequency Shift Keying
Deviation	20.507812 kHz	Frequency modulation
Data rate	38.360596 kBaud	Raw bit rate
RX Filter Bandwidth	93.75 kHz	Receiver Band pass filter bandwidth
IF Frequency	140.62 kHz	Receiver intermediate frequency

3.2. Error Correction

The cc1111 provides forward error correction in hardware, which AltOS uses to improve reception of weak signals. The overall effect of this is to halve the available bandwidth for data from 38 kBaud to 19 kBaud. -

Table 10.

Parameter	Value	Description
Error Correction	Convolutional coding FEC	1/2 code, constraint length m=4
Interleaving	4 x 4	Reduce effect of noise burst
Data Whitening	XOR with 9-bit PNR	Rotate right with bit 8 = bit 0 xor bit 5, initial - value 111111111

4. TeleDongle packet format

Table 10.

Parameter	Value	Description
Error Correction	Convolutional coding FEC	1/2 code, constraint length m=4
Interleaving	4 x 4	Reduce effect of noise burst
Data Whitening	XOR with 9-bit PNR	Rotate right with bit 8 = bit 0 xor bit 5, initial + value 111111111

4. TeleDongle packet format

TeleDongle does not do any interpretation of the packet data, instead it is configured to receive packets of a specified length (32 bytes in this case). For each received packet, @@ -106,9 +106,9 @@ the packet data, two bytes added by the cc1111 radio receiver hardware and finally a checksum so that the host software can validate that the line was transmitted without any errors. -

Table 11.

Offset

Name

Example

Description

length

Total length of data bytes in the line. Note that +

Table 11.

Offset	Name	Example	Description
0	length	22	Total length of data bytes in the line. Note that this includes the added RSSI and status bytes
1 ·· length-3	packet	4f ·· 00	Bytes of actual packet data
length-2	rssi	3f	Received signal strength. dBm = rssi / 2 - 74
length-1	lqi	a9	Link Quality Indicator and CRC status. Bit 7 - is set when the CRC is correct
length	checksum	88	(0x5a + sum(bytes 1 ·· length-1)) % 256

5. History and Motivation

+ is set when the CRC is correct

length

checksum

(0x5a + sum(bytes 1 ·· length-1)) % 256

5. History and Motivation

The original AltoOS telemetry mechanism encoded everything available piece of information on the TeleMetrum hardware into a single unified packet. Initially, the packets contained very diff --git a/AltOS/doc/telemetry.pdf b/AltOS/doc/telemetry.pdf index 1556094..987f01d 100644 Binary files a/AltOS/doc/telemetry.pdf and b/AltOS/doc/telemetry.pdf differ diff --git a/AltOS/launch-sites.txt b/AltOS/launch-sites.txt index 4082a2e..48a1c8c 100644 --- a/AltOS/launch-sites.txt +++ b/AltOS/launch-sites.txt @@ -1,3 +1,4 @@ +4 Corners Rocketry Association:36.50965:-107.830711: Advanced Rocketry Queensland:-27.82533:151.48001:http://advrocketry.com AARC South Australia:-35.092063:140.014786:http://www.australianrocketryclub.com.au/forum/index.php/board,28.0.html AHPRA BALLS:40.808:-119.15:http://www.ahpra.org diff --git a/EasyMini.mdwn b/EasyMini.mdwn new file mode 100644 index 0000000..2092a44 --- /dev/null +++ b/EasyMini.mdwn @@ -0,0 +1 @@ +[[!map pages="EasyMini/* and ! EasyMini/*/*"]] diff --git a/EasyMini/index.mdwn b/EasyMini/index.mdwn new file mode 100644 index 0000000..41b1c61 --- /dev/null +++ b/EasyMini/index.mdwn @@ -0,0 +1,61 @@ +# EasyMini + +This is a small, baro-only recording dual-deploy altimeter for +model rocketry + +EasyMini is currently in development, with a handful of prototype +boards built and flown. Production units will eventually be available from the +[Garbee and Garbee](http://auric.gag.com) web +store. + +For the latest EasyMini firmware and related ground station software, please +visit the [AltOS](../AltOS) page on this site. + +These are photos of our current prototype version: + + + + +## Features ## + +### User View ### + +* Recording altimeter for model rocketry +* Supports dual deployment (can fire 2 ejection charges) +* Barometric pressure sensor good to 100k feet MSL +* Designed to use a battery supplying 3.7V-12V. +* 1.5 x 0.8 inch board designed to fit inside 24mm airframe coupler tube +* 2MB on-board data logging flash + +### Developer View ### + +* Hardware Features + * [NXP LPC11U14](http://www.nxp.com/products/microcontrollers/cortex_m0_m0/LPC11U14FHI33.html) System-on-Chip + * ARM Cortex-M0 MCU + * 32k Flash + * 6k RAM + * USB 2.0 + * 8 12-bit analog inputs + * I2C, SPI, async serial + * digital I/O + * [Measurement Specialties MS5607](http://www.meas-spec.com/product/pressure/MS5607-02BA03.aspx) pressure sensor + * 1MB SPI flash +* Software Features + * Written mostly in C with some ARM assembler + * Runs from on-chip flash, uses on-chip RAM, stores flight data to + flash memory part +* Tools Used + * [gEDA](http://www.gpleda.org/) for schematic capture and PCB layout + * [GCC](http://gcc.gnu.org/) compiler and source debugger +* Licenses + * The hardware is licensed under the [TAPR](http://www.tapr.org) [Open Hardware License](http://www.tapr.org/ohl.html) + * The software is licensed [GPL version 2](http://www.gnu.org/licenses/old-licenses/gpl-2.0.html) + +## Artifacts ## + +There is a single manual for EasyMini and all other Altus Metrum products, +which is available in [html](../AltOS/doc/altusmetrum.html) and +[pdf](../AltOS/doc/altusmetrum.pdf) formats. + +The hardware design files can be found on [git.gag.com](http://git.gag.com) +in the project [hw/easymini](http://git.gag.com/?p=hw/easymini;a=summary). diff --git a/EasyMini/v0.2.mdwn b/EasyMini/v0.2.mdwn new file mode 100644 index 0000000..453e346 --- /dev/null +++ b/EasyMini/v0.2.mdwn @@ -0,0 +1 @@ +[[!map pages="EasyMini/v0.2/* and ! EasyMini/v0.2/*/*"]] diff --git a/EasyMini/v0.2/easymini-parts-thumb.jpg b/EasyMini/v0.2/easymini-parts-thumb.jpg new file mode 100644 index 0000000..ec79fc0 Binary files /dev/null and b/EasyMini/v0.2/easymini-parts-thumb.jpg differ diff --git a/EasyMini/v0.2/easymini-parts.jpg b/EasyMini/v0.2/easymini-parts.jpg new file mode 100644 index 0000000..724d4ea Binary files /dev/null and b/EasyMini/v0.2/easymini-parts.jpg differ diff --git a/EasyMini/v0.2/easymini-top-thumb.jpg b/EasyMini/v0.2/easymini-top-thumb.jpg new file mode 100644 index 0000000..f018f15 Binary files /dev/null and b/EasyMini/v0.2/easymini-top-thumb.jpg differ diff --git a/EasyMini/v0.2/easymini-top.jpg b/EasyMini/v0.2/easymini-top.jpg new file mode 100644 index 0000000..2b9e0a3 Binary files /dev/null and b/EasyMini/v0.2/easymini-top.jpg differ diff --git a/TeleGPS.mdwn b/TeleGPS.mdwn new file mode 100644 index 0000000..b91aeb8 --- /dev/null +++ b/TeleGPS.mdwn @@ -0,0 +1 @@ +[[!map pages="TeleGPS/* and ! TeleGPS/*/*"]] diff --git a/TeleGPS/index.mdwn b/TeleGPS/index.mdwn new file mode 100644 index 0000000..7d4a163 --- /dev/null +++ b/TeleGPS/index.mdwn @@ -0,0 +1,61 @@ +# TeleGPS + +This is a GPS-based position tracker and logger. + +TeleGPS is currently in development, with a handful of prototype +boards built. Production units will eventually be available from the +[Garbee and Garbee](http://auric.gag.com) web +store. + +For the latest TeleGPS firmware and related ground station software, please +visit the [AltOS](../AltOS) page on this site. + +These are photos of our current prototype version: + + + + +## Features ## + +### User View ### + +* GPS tracker and logger +* Offers custom digital telemetry, APRS and direction beacons +* High-dynamics GPS receiver for accurate tracking +* Uses 3.7V Lithium Polymer battery. +* 1.5 x 0.8 inch board designed to fit inside 24mm airframe coupler tube +* 2MB on-board data logging flash +* Built-in USB connection for configuration, data download and battery charging + +### Developer View ### + +* Hardware Features + * [NXP LPC11U14](http://www.nxp.com/products/microcontrollers/cortex_m0_m0/LPC11U14FHI33.html) System-on-Chip + * ARM Cortex-M0 MCU + * 32k Flash + * 6k RAM + * USB 2.0 + * 8 12-bit analog inputs + * I2C, SPI, async serial + * digital I/O + * [uBlox Max 7Q](http://www.u-blox.com/en/gps-modules/pvt-modules/max-7.html) GPS receiver + * 2MB SPI flash +* Software Features + * Written mostly in C with some ARM assembler + * Runs from on-chip flash, uses on-chip RAM, stores tracking data to + flash memory part +* Tools Used + * [gEDA](http://www.gpleda.org/) for schematic capture and PCB layout + * [GCC](http://gcc.gnu.org/) compiler and source debugger +* Licenses + * The hardware is licensed under the [TAPR](http://www.tapr.org) [Open Hardware License](http://www.tapr.org/ohl.html) + * The software is licensed [GPL version 2](http://www.gnu.org/licenses/old-licenses/gpl-2.0.html) + +## Artifacts ## + +There is a single manual for TeleGPS and all other Altus Metrum products, +which is available in [html](../AltOS/doc/altusmetrum.html) and +[pdf](../AltOS/doc/altusmetrum.pdf) formats. + +The hardware design files can be found on [git.gag.com](http://git.gag.com) +in the project [hw/telegps](http://git.gag.com/?p=hw/telegps;a=summary). diff --git a/TeleGPS/v0.3.mdwn b/TeleGPS/v0.3.mdwn new file mode 100644 index 0000000..9c149a6 --- /dev/null +++ b/TeleGPS/v0.3.mdwn @@ -0,0 +1 @@ +[[!map pages="TeleGPS/v0.3/* and ! TeleGPS/v0.3/*/*"]] diff --git a/TeleGPS/v0.3/telegps-parts-thumb.jpg b/TeleGPS/v0.3/telegps-parts-thumb.jpg new file mode 100644 index 0000000..f89bb1d Binary files /dev/null and b/TeleGPS/v0.3/telegps-parts-thumb.jpg differ diff --git a/TeleGPS/v0.3/telegps-parts.jpg b/TeleGPS/v0.3/telegps-parts.jpg new file mode 100644 index 0000000..088e9eb Binary files /dev/null and b/TeleGPS/v0.3/telegps-parts.jpg differ diff --git a/TeleGPS/v0.3/telegps-top-thumb.jpg b/TeleGPS/v0.3/telegps-top-thumb.jpg new file mode 100644 index 0000000..4b5f858 Binary files /dev/null and b/TeleGPS/v0.3/telegps-top-thumb.jpg differ diff --git a/TeleGPS/v0.3/telegps-top.jpg b/TeleGPS/v0.3/telegps-top.jpg new file mode 100644 index 0000000..fdeb0d4 Binary files /dev/null and b/TeleGPS/v0.3/telegps-top.jpg differ diff --git a/TeleMini/history.mdwn b/TeleMini/history.mdwn new file mode 100644 index 0000000..8074dd4 --- /dev/null +++ b/TeleMini/history.mdwn @@ -0,0 +1,62 @@ +# TeleMini History + +# TeleMini Version 1.0 # + +The very first TeleMini design became 1.0. It was a very small, +baro-only recording dual-deploy altimeter for model rocketry with +integrated telemetry link. + + + + +## Features ## + +### User View ### + +* Recording altimeter for model rocketry +* Supports dual deployment (can fire 2 ejection charges) +* 70cm ham-band transceiver for telemetry downlink +* Barometric pressure sensor good to 45k feet MSL +* Designed to use a single LiPo rechargeable battery +* 1.5 x 0.5 inch board designed to fit inside 18mm airframe coupler tube + +### Developer View ### + +* Hardware Features + * [TI CC1111F32](http://focus.ti.com/docs/prod/folders/print/cc1111f32.html) Low Power RF System-on-Chip + * Sub-1Ghz transceiver + * 8051 MCU + * 32k Flash + * 4k RAM + * USB 2.0 + * 6 12-bit analog inputs (11 bits with single-ended sensors) + * 2 channels of serial I/O + * digital I/O + * [Freescale MP3H6115A](http://www.freescale.com/webapp/search.partparamdetail.framework?PART_NUMBER=MP3H6115A6U) pressure sensor +* Software Features + * Written mostly in C with some 8051 assembler + * Runs from on-chip flash, uses on-chip RAM, stores flight data to + upper blocks of on-chip flash +* Tools Used + * [gEDA](http://www.gpleda.org/) for schematic capture and PCB layout + * [SDCC](http://sdcc.sourceforge.net/) compiler and source debugger +* Licenses + * The hardware is licensed under the [TAPR](http://www.tapr.org) [Open Hardware License](http://www.tapr.org/ohl.html) + * The software is licensed [GPL version 2](http://www.gnu.org/licenses/old-licenses/gpl-2.0.html) + +## Artifacts ## + +There is a single manual for TeleMini and all other Altus Metrum products, +which is available in [html](../AltOS/doc/altusmetrum.html) and +[pdf](../AltOS/doc/altusmetrum.pdf) formats. + +The hardware design files can be found on [git.gag.com](http://git.gag.com) +in the project [hw/telemini](http://git.gag.com/?p=hw/telemini;a=summary). + +For those who don't have ready access to the gEDA suite, here are pdf snapshots +of the files for Production PCB version 1.0 in more easily readable form. + +* [schematic](v1.0/telemini.pdf) +* [pcb artwork](v1.0/telemini.pcb.pdf) +* [bill of materials](v1.0/partslist.csv) + diff --git a/TeleMini/index.mdwn b/TeleMini/index.mdwn index 5a783cb..ee861c3 100644 --- a/TeleMini/index.mdwn +++ b/TeleMini/index.mdwn @@ -1,31 +1,30 @@ -# TeleMini +# TeleMini # -This is a very small, baro-only recording dual-deploy altimeter for -model rocketry with integrated telemetry link. - -Production units are available from the -[Garbee and Garbee](http://auric.gag.com) web -store. TeleMini starter kits are also available from -[Apogee Components](http://www.apogeerockets.com/Altus_Metrum_telemini.asp). +TeleMini version 2.0 is a small, baro-only recording dual-deploy +altimeter for model rocketry with integrated telemetry link. It's +currently in development, with production planned to start in the fall +of 2013. For the latest TeleMini firmware and related ground station software, please visit the [AltOS](../AltOS) page on this site. -These are photos of our current production version: +These are photos of our current prototype version: - - + + ## Features ## ### User View ### -* Recording altimeter for model rocketry -* Supports dual deployment (can fire 2 ejection charges) -* 70cm ham-band transceiver for telemetry downlink -* Barometric pressure sensor good to 45k feet MSL -* Designed to use a single LiPo rechargeable battery -* 1.5 x 0.5 inch board designed to fit inside 18mm airframe coupler tube + * Recording altimeter for model rocketry + * Supports dual deployment (can fire 2 ejection charges) + * 70cm ham-band transceiver for telemetry downlink + * Barometric pressure sensor good to 100k' feet MSL + * Designed to use any battery from 3.7 - 12V + * Screw terminals for pyro connectors, switch and external battery + * Built-in USB connector for configuration and data download + * 1.5 x 0.8 inch board designed to fit inside 24mm airframe coupler tube ### Developer View ### @@ -39,11 +38,12 @@ These are photos of our current production version: * 6 12-bit analog inputs (11 bits with single-ended sensors) * 2 channels of serial I/O * digital I/O - * [Freescale MP3H6115A](http://www.freescale.com/webapp/search.partparamdetail.framework?PART_NUMBER=MP3H6115A6U) pressure sensor + * [Measurement Specialties MS5607](http://www.meas-spec.com/product/pressure/MS5607-02BA03.aspx) pressure sensor + * 1MB SPI flash * Software Features * Written mostly in C with some 8051 assembler * Runs from on-chip flash, uses on-chip RAM, stores flight data to - upper blocks of on-chip flash + on-board flash memory * Tools Used * [gEDA](http://www.gpleda.org/) for schematic capture and PCB layout * [SDCC](http://sdcc.sourceforge.net/) compiler and source debugger @@ -60,10 +60,4 @@ which is available in [html](../AltOS/doc/altusmetrum.html) and The hardware design files can be found on [git.gag.com](http://git.gag.com) in the project [hw/telemini](http://git.gag.com/?p=hw/telemini;a=summary). -For those who don't have ready access to the gEDA suite, here are pdf snapshots -of the files for Production PCB version 1.0 in more easily readable form. - -* [schematic](v1.0/telemini.pdf) -* [pcb artwork](v1.0/telemini.pcb.pdf) -* [bill of materials](v1.0/partslist.csv) - +## [History of TeleMini](history) ## diff --git a/TeleMini/v1.2.mdwn b/TeleMini/v1.2.mdwn new file mode 100644 index 0000000..b1b4a5a --- /dev/null +++ b/TeleMini/v1.2.mdwn @@ -0,0 +1 @@ +[[!map pages="TeleMini/v1.2/* and ! TeleMini/v1.2/*/*"]] diff --git a/TeleMini/v2.0.mdwn b/TeleMini/v2.0.mdwn new file mode 100644 index 0000000..bc7a228 --- /dev/null +++ b/TeleMini/v2.0.mdwn @@ -0,0 +1 @@ +[[!map pages="TeleMini/v2.0/* and ! TeleMini/v2.0/*/*"]] diff --git a/TeleMini/v2.0/telemini-parts-thumb.jpg b/TeleMini/v2.0/telemini-parts-thumb.jpg new file mode 100644 index 0000000..cc56555 Binary files /dev/null and b/TeleMini/v2.0/telemini-parts-thumb.jpg differ diff --git a/TeleMini/v2.0/telemini-parts.jpg b/TeleMini/v2.0/telemini-parts.jpg new file mode 100644 index 0000000..08adf3b Binary files /dev/null and b/TeleMini/v2.0/telemini-parts.jpg differ diff --git a/TeleMini/v2.0/telemini-top-thumb.jpg b/TeleMini/v2.0/telemini-top-thumb.jpg new file mode 100644 index 0000000..aa47526 Binary files /dev/null and b/TeleMini/v2.0/telemini-top-thumb.jpg differ diff --git a/TeleMini/v2.0/telemini-top.jpg b/TeleMini/v2.0/telemini-top.jpg new file mode 100644 index 0000000..bc8ae45 Binary files /dev/null and b/TeleMini/v2.0/telemini-top.jpg differ diff --git a/index.mdwn b/index.mdwn index 9c4866a..1a2ec6e 100644 --- a/index.mdwn +++ b/index.mdwn @@ -82,17 +82,25 @@ These are projects we're working on that may become products someday: is the name of the firmware and related utilities that Keith maintains for the set of hardware projects here. +* [EasyMini](EasyMini/) +is a small dual-deploy rocketry altimeter using the MS5607 barometry +pressure sensor. + * [MegaDongle](MegaDongle/) is a higher-performance alternative to [TeleDongle](TeleDongle/). -* [TeleMega](TeleMega/) -is a high-end flight computer with 6 pyro channels, more and better sensors, -GPS, and a high performance bidirectional RF telemetry link. - * [OpenAlt](OpenAlt/) was Bdale's original project here, a dual-deploy rocketry altimeter. One prototype was built, but never flown. This project is now indefinitely on hold. +* [TeleGPS](TeleGPS/) +is a GPS tracker and logger using the uBlox Max 7Q GPS receiver for +high dynamic performance and a combination digital/APRS transmitter. + +* [TeleMega](TeleMega/) +is a high-end flight computer with 6 pyro channels, more and better sensors, +GPS, and a high performance bidirectional RF telemetry link. + * [TeleNano](TeleNano/) is a tiny rocketry altimeter with telemetry using only a barometric pressure sensor diff --git a/production.mdwn b/production.mdwn index f5930a3..aa12bcc 100644 --- a/production.mdwn +++ b/production.mdwn @@ -303,6 +303,10 @@ TeleMetrum v1.9 2013.08.27 TeleMega v0.4 P 2013.08.28 +## sn 96 ## + +TeleMini v1.1 2013.08.25. From Phoenix panel. + ## sn 100-207 ## First production run of 108 pieces of TeleDongle v0.2 by

The Altus Metrum System

An Owner's Manual for TeleMetrum, TeleMini and TeleDongle Devices

Bdale Garbee

Keith Packard

Bob Finch

Anthony Towns

The Altus Metrum System

An Owner's Manual for TeleMetrum, TeleMini, TeleDongle and TeleBT Devices

Bdale Garbee

Keith Packard

Bob Finch

Anthony Towns

Acknowledgements

Acknowledgements

Chapter 1. Introduction and Overview

Chapter 1. Introduction and Overview

Chapter 2. Getting Started

Chapter 2. Getting Started

Chapter 3. Handling Precautions

Chapter 3. Handling Precautions

Chapter 4. Hardware Overview

Chapter 4. Hardware Overview

Chapter 5. System Operation

1. Firmware Modes

Chapter 5. System Operation

1. Firmware Modes

2. GPS

2. GPS

3. Controlling An Altimeter Over The Radio Link

3. Controlling An Altimeter Over The Radio Link

4. Ground Testing

4. Ground Testing

5. Radio Link

5. Radio Link

6. Configurable Parameters

6. Configurable Parameters

6.1. Radio Frequency

6.1. Radio Frequency

6.2. Apogee Delay

6.2. Apogee Delay

6.3. Main Deployment Altitude

6.3. Main Deployment Altitude

6.4. Maximum Flight Log

6.4. Maximum Flight Log

6.5. Ignite Mode

6.5. Ignite Mode

6.6. Pad Orientation

6.6. Pad Orientation

Chapter 6. AltosUI

Chapter 6. AltosUI

1. Monitor Flight

Receive, Record and Display Telemetry Data

1. Monitor Flight

Receive, Record and Display Telemetry Data

1.1. Launch Pad

1.1. Launch Pad

1.2. Ascent

1.2. Ascent

1.3. Descent

1.3. Descent

1.4. Landed

1.4. Landed

1.5. Site Map

1.5. Site Map

2. Save Flight Data

2. Save Flight Data

3. Replay Flight

3. Replay Flight

4. Graph Data

4. Graph Data

5. Export Data

5. Export Data

5.1. Comma Separated Value Format

5.1. Comma Separated Value Format

5.2. Keyhole Markup Language (for Google Earth)

5.2. Keyhole Markup Language (for Google Earth)

6. Configure Altimeter

6. Configure Altimeter

6.1. Main Deploy Altitude

6.1. Main Deploy Altitude