</para>
</legalnotice>
<revhistory>
+ <revision>
+ <revnumber>1.5</revnumber>
+ <date>6 September 2014</date>
+ <revremark>
+ Major release adding EasyMega support.
+ </revremark>
+ </revision>
<revision>
<revnumber>1.4.1</revnumber>
<date>20 June 2014</date>
EasyMini is a dual-deploy altimeter with logging and built-in
USB data download.
</para>
+ <para>
+ EasyMega is essentially a TeleMega board with the GPS receiver
+ and telemetry transmitter removed. It offers the same 6 pyro
+ channels and integrated gyroscopes for staging/air-start inhibit.
+ </para>
<para>
TeleDongle was our first ground station, providing a USB to RF
interfaces for communicating with the altimeters. Combined with
“starter kit” is to charge the battery.
</para>
<para>
- For TeleMetrum and TeleMega, the battery can be charged by plugging it into the
+ For TeleMetrum, TeleMega and EasyMega, the battery can be charged by plugging it into the
corresponding socket of the device and then using the USB
cable to plug the flight computer into your computer's USB socket. The
on-board circuitry will charge the battery whenever it is plugged
deeply discharged battery.
</para>
<para>
- TeleMetrum v2.0 and TeleMega use a higher power battery charger,
+ TeleMetrum v2.0, TeleMega and EasyMega use a higher power battery charger,
allowing them to charge the battery while running the board at
maximum power. When the battery is charging, or when the board
is consuming a lot of power, the red LED will be lit. When the
EasyMini and TeleMini v2 are designed to use either a
lithium polymer battery or any other battery producing
between 4 and 12 volts, such as a rectangular 9V
- battery. TeleMega and TeleMetrum are not designed for this,
+ battery. TeleMega, EasyMega and TeleMetrum are not designed for this,
and must only be powered by a lithium polymer battery. Find
instructions on how to use other batteries in the EasyMini
and TeleMini sections below.
<entry>40mW</entry>
<entry>3.7V</entry>
</row>
+ <row>
+ <entry>EasyMega <?linebreak?>v1.0</entry>
+ <entry><para>MS5607 30km (100k')</para></entry>
+ <entry><para>MMA6555 102g</para></entry>
+ <entry>-</entry>
+ <entry><para>MPU6000 HMC5883</para></entry>
+ <entry>8MB</entry>
+ <entry>-</entry>
+ <entry>3.7V</entry>
+ </row>
</tbody>
</tgroup>
</table>
<entry>3¼ inch (8.26cm)</entry>
<entry>38mm coupler</entry>
</row>
+ <row>
+ <entry>EasyMega</entry>
+ <entry><para>
+ Debug<?linebreak?>
+ Companion<?linebreak?>
+ USB<?linebreak?>
+ Battery
+ </para></entry>
+ <entry><para>
+ Apogee pyro <?linebreak?>
+ Main pyro<?linebreak?>
+ Pyro A-D<?linebreak?>
+ Switch<?linebreak?>
+ Pyro battery
+ </para></entry>
+ <entry>1¼ inch (3.18cm)</entry>
+ <entry>2¼ inch (5.62cm)</entry>
+ <entry>38mm coupler</entry>
+ </row>
</tbody>
</tgroup>
</table>
</para>
</section>
</section>
+ <section>
+ <title>EasyMega</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="easymega-v1.0-top.jpg" width="4.5in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
+ <para>
+ EasyMega is a 1¼ inch by 2¼ inch circuit board. It was
+ designed to easily fit in a 38mm coupler. Like TeleMetrum,
+ EasyMega has an accelerometer and so it must be mounted so that
+ the board is aligned with the flight axis. It can be mounted
+ either antenna up or down.
+ </para>
+ <section>
+ <title>EasyMega Screw Terminals</title>
+ <para>
+ EasyMega has two sets of nine screw terminals on the end of
+ the board opposite the telemetry antenna. They are as follows:
+ </para>
+ <table frame='all'>
+ <title>EasyMega Screw Terminals</title>
+ <?dbfo keep-together="always"?>
+ <tgroup cols='3' align='center' colsep='1' rowsep='1'>
+ <colspec align='center' colwidth='*' colname='Pin #'/>
+ <colspec align='center' colwidth='2*' colname='Pin Name'/>
+ <colspec align='left' colwidth='5*' colname='Description'/>
+ <thead>
+ <row>
+ <entry align='center'>Terminal #</entry>
+ <entry align='center'>Terminal Name</entry>
+ <entry align='center'>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Top 1</entry>
+ <entry>Switch Input</entry>
+ <entry>Switch connection to positive battery terminal</entry>
+ </row>
+ <row>
+ <entry>Top 2</entry>
+ <entry>Switch Output</entry>
+ <entry>Switch connection to flight computer</entry>
+ </row>
+ <row>
+ <entry>Top 3</entry>
+ <entry>GND</entry>
+ <entry>Ground connection for use with external active switch</entry>
+ </row>
+ <row>
+ <entry>Top 4</entry>
+ <entry>Main -</entry>
+ <entry>Main pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Top 5</entry>
+ <entry>Main +</entry>
+ <entry>Main pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>Top 6</entry>
+ <entry>Apogee -</entry>
+ <entry>Apogee pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Top 7</entry>
+ <entry>Apogee +</entry>
+ <entry>Apogee pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>Top 8</entry>
+ <entry>D -</entry>
+ <entry>D pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Top 9</entry>
+ <entry>D +</entry>
+ <entry>D pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>Bottom 1</entry>
+ <entry>GND</entry>
+ <entry>Ground connection for negative pyro battery terminal</entry>
+ </row>
+ <row>
+ <entry>Bottom 2</entry>
+ <entry>Pyro</entry>
+ <entry>Positive pyro battery terminal</entry>
+ </row>
+ <row>
+ <entry>Bottom 3</entry>
+ <entry>Lipo</entry>
+ <entry>
+ Power switch output. Use to connect main battery to
+ pyro battery input
+ </entry>
+ </row>
+ <row>
+ <entry>Bottom 4</entry>
+ <entry>A -</entry>
+ <entry>A pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Bottom 5</entry>
+ <entry>A +</entry>
+ <entry>A pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>Bottom 6</entry>
+ <entry>B -</entry>
+ <entry>B pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Bottom 7</entry>
+ <entry>B +</entry>
+ <entry>B pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>Bottom 8</entry>
+ <entry>C -</entry>
+ <entry>C pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Bottom 9</entry>
+ <entry>C +</entry>
+ <entry>C pyro channel common connection to battery +</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+ <section>
+ <title>Using a Separate Pyro Battery with EasyMega</title>
+ <para>
+ EasyMega provides explicit support for an external pyro
+ battery. All that is required is to remove the jumper
+ between the lipo terminal (Bottom 3) and the pyro terminal
+ (Bottom 2). Then hook the negative pyro battery terminal to ground
+ (Bottom 1) and the positive pyro battery to the pyro battery
+ input (Bottom 2). You can then use the existing pyro screw
+ terminals to hook up all of the pyro charges.
+ </para>
+ </section>
+ <section>
+ <title>Using Only One Battery With EasyMega</title>
+ <para>
+ Because EasyMega has built-in support for a separate pyro
+ battery, if you want to fly with just one battery running
+ both the computer and firing the charges, you need to
+ connect the flight computer battery to the pyro
+ circuit. EasyMega has two screw terminals for this—hook a
+ wire from the Lipo terminal (Bottom 3) to the Pyro terminal
+ (Bottom 2).
+ </para>
+ </section>
+ <section>
+ <title>Using an Active Switch with EasyMega</title>
+ <para>
+ As explained above, an external active switch requires three
+ connections, one to the positive battery terminal, one to
+ the flight computer positive input and one to ground.
+ </para>
+ <para>
+ The positive battery terminal is available on Top terminal
+ 1, the positive flight computer input is on Top terminal
+ 2. Ground is on Top terminal 3.
+ </para>
+ </section>
+ </section>
<section>
<title>Flight Data Recording</title>
<para>
<entry>8MB</entry>
<entry>40</entry>
</row>
+ <row>
+ <entry>EasyMega</entry>
+ <entry>32</entry>
+ <entry>8MB</entry>
+ <entry>40</entry>
+ </row>
</tbody>
</tgroup>
</table>
Configuration data is also stored in the flash memory on
TeleMetrum v1.x, TeleMini and EasyMini. This consumes 64kB
of flash space. This configuration space is not available
- for storing flight log data. TeleMetrum v2.0 and TeleMega
+ for storing flight log data. TeleMetrum v2.0, TeleMega and EasyMega
store configuration data in a bit of eeprom available within
the processor chip, leaving that space available in flash for
more flight data.
The AltOS firmware build for the altimeters has two
fundamental modes, “idle” and “flight”. Which of these modes
the firmware operates in is determined at start up time. For
- TeleMetrum and TeleMega, which have accelerometers, the mode is
+ TeleMetrum, TeleMega and EasyMega, which have accelerometers, the mode is
controlled by the orientation of the
rocket (well, actually the board, of course...) at the time
power is switched on. If the rocket is “nose up”, then
and beep out the maximum height until turned off.
</para>
<para>
- One “neat trick” of particular value when TeleMetrum or TeleMega are used with
+ One “neat trick” of particular value when TeleMetrum, TeleMega
+ or EasyMega are used with
very large air-frames, is that you can power the board up while the
rocket is horizontal, such that it comes up in idle mode. Then you can
raise the air-frame to launch position, and issue a 'reset' command
isn't displaying position information, it's possible that this
is the cause.
</para>
+ <para>
+ APRS packets include an SSID (Secondary Station Identifier)
+ field that allows one operator to have multiple
+ transmitters. AltOS allows you to set this to a single digit
+ from 0 to 9, allowing you to fly multiple transmitters at the
+ same time while keeping the identify of each one separate in
+ the receiver. By default, the SSID is set to the last digit of
+ the device serial number.
+ </para>
<para>
The APRS packet format includes a comment field that can have
arbitrary text in it. AltOS uses this to send status
<entry>M3.7</entry>
<entry>Main Igniter Voltage</entry>
</row>
+ <row>
+ <entry>6</entry>
+ <entry>1286</entry>
+ <entry>Device Serial Number</entry>
+ </row>
</tbody>
</tgroup>
</table>
<para>
Here's an example of an APRS comment showing GPS lock with 6
satellites in view, a primary battery at 4.0V, and
- apogee and main igniters both at 3.7V.
+ apogee and main igniters both at 3.7V from device 1286.
<screen>
- L6 B4.0 A3.7 M3.7
+ L6 B4.0 A3.7 M3.7 1286
</screen>
</para>
<para>
mode.
</para>
</section>
+ <section>
+ <title>Telemetry baud rate</title>
+ <para>
+ This sets the modulation bit rate for data transmission for
+ both telemetry and packet link mode. Lower bit
+ rates will increase range while reducing the amount of data
+ that can be sent and increasing battery consumption. All
+ telemetry is done using a rate 1/2 constraint 4 convolution
+ code, so the actual data transmission rate is 1/2 of the
+ modulation bit rate specified here.
+ </para>
+ </section>
<section>
<title>APRS Interval</title>
<para>
recommend sending packets no more than once every 5 seconds.
</para>
</section>
+ <section>
+ <title>APRS SSID</title>
+ <para>
+ This selects the SSID reported in APRS packets. By default,
+ it is set to the last digit of the serial number, but you
+ can change this to any value from 0 to 9.
+ </para>
+ </section>
<section>
<title>Apogee Delay</title>
<para>
<section>
<title>Pad Orientation</title>
<para>
- TeleMetrum and TeleMega measure acceleration along the axis
+ TeleMetrum, TeleMega and EasyMega measure acceleration along the axis
of the board. Which way the board is oriented affects the
sign of the acceleration value. Instead of trying to guess
which way the board is mounted in the air frame, the
<title>Configurable Pyro Channels</title>
<para>
In addition to the usual Apogee and Main pyro channels,
- TeleMega has four additional channels that can be configured
+ TeleMega and EasyMega have four additional channels that can be configured
to activate when various flight conditions are
satisfied. You can select as many conditions as necessary;
all of them must be met in order to activate the
</listitem>
<listitem>
<para>
- Orientation. TeleMega contains a 3-axis gyroscope and
+ Orientation. TeleMega and EasyMega contain a 3-axis gyroscope and
accelerometer which is used to measure the current
angle. Note that this angle is not the change in angle
from the launch pad, but rather absolute relative to
at all.
</para>
</section>
+ <section>
+ <title>Telemetry baud rate</title>
+ <para>
+ This sets the modulation bit rate for data transmission for
+ both telemetry and packet link mode. Lower bit
+ rates will increase range while reducing the amount of data
+ that can be sent and increasing battery consumption. All
+ telemetry is done using a rate 1/2 constraint 4 convolution
+ code, so the actual data transmission rate is 1/2 of the
+ modulation bit rate specified here.
+ </para>
+ </section>
<section>
<title>APRS Interval</title>
<para>
sending any other telemetry during that time.
</para>
</section>
+ <section>
+ <title>APRS SSID</title>
+ <para>
+ Which SSID to report in APRS packets. By default, this is
+ set to the last digit of the serial number, but can be
+ configured to any value from 0 to 9.
+ </para>
+ </section>
<section>
<title>Callsign</title>
<para>
<section>
<title>Pad Orientation</title>
<para>
- Because they include accelerometers, TeleMetrum and
- TeleMega are sensitive to the orientation of the board. By
+ Because they include accelerometers, TeleMetrum,
+ TeleMega and EasyMega are sensitive to the orientation of the board. By
default, they expect the antenna end to point forward. This
parameter allows that default to be changed, permitting the
board to be mounted with the antenna pointing aft instead.
</informalfigure>
<para>
This opens a separate window to configure the additional
- pyro channels available on TeleMega. One column is
+ pyro channels available on TeleMega and EasyMega. One column is
presented for each channel. Each row represents a single
parameter, if enabled the parameter must meet the specified
test for the pyro channel to be fired. See the Pyro Channels
</mediaobject>
</informalfigure>
<para>
- Select this button and then select a TeleDongle Device from the list provided.
+ Select this button and then select a TeleDongle or TeleBT Device from the list provided.
</para>
<para>
The first few lines of the dialog provide information about the
individual configuration entries.
</para>
<para>
- Note that the TeleDongle itself doesn't save any configuration
+ Note that TeleDongle and TeleBT don't save any configuration
data, the settings here are recorded on the local machine in
- the Java preferences database. Moving the TeleDongle to
+ the Java preferences database. Moving the device to
another machine, or using a different user account on the same
machine will cause settings made here to have no effect.
</para>
</para>
</section>
<section>
- <title>Radio Calibration</title>
+ <title>RF Calibration</title>
<para>
The radios in every Altus Metrum device are calibrated at the
factory to ensure that they transmit and receive on the
- specified frequency. To change a TeleDongle's calibration,
+ specified frequency. To change a TeleDongle or TeleBT's calibration,
you must reprogram the unit completely, so this entry simply
shows the current value and doesn't allow any changes.
</para>
</section>
+ <section>
+ <title>Telemetry Rate</title>
+ <para>
+ This lets you match the telemetry and packet link rate from
+ the transmitter. If they don't match, the device won't
+ receive any data.
+ </para>
+ </section>
</section>
<section>
<title>Flash Image</title>
This reprograms Altus Metrum devices with new
firmware. TeleMetrum v1.x, TeleDongle, TeleMini and TeleBT are
all reprogrammed by using another similar unit as a
- programming dongle (pair programming). TeleMega, TeleMetrum v2
+ programming dongle (pair programming). TeleMega, EasyMega, TeleMetrum v2
and EasyMini are all programmed directly over their USB ports
(self programming). Please read the directions for flashing
devices in the Updating Device Firmware chapter below.
<para>
This listens for telemetry packets on all of the configured
frequencies, displaying information about each device it
- receives a packet from. You can select which of the three
- telemetry formats should be tried; by default, it only listens
- for the standard telemetry packets used in v1.0 and later
+ receives a packet from. You can select which of the baud rates
+ and telemetry formats should be tried; by default, it only listens
+ at 38400 baud with the standard telemetry format used in v1.0 and later
firmware.
</para>
</section>
In the rocket itself, you just need a flight computer and
a single-cell, 3.7 volt nominal Li-Po rechargeable battery. An
850mAh battery weighs less than a 9V alkaline battery, and will
- run a TeleMetrum or TeleMega for hours.
+ run a TeleMetrum, TeleMega or EasyMega for hours.
A 110mAh battery weighs less than a triple A battery and is a good
- choice for use with TeleMini.
+ choice for use with TeleMini or EasyMini.
</para>
<para>
- By default, we ship flight computers with a simple wire antenna.
+ By default, we ship TeleMini, TeleMetrum and TeleMega flight computers with a simple wire antenna.
If your electronics bay or the air-frame it resides within is made
of carbon fiber, which is opaque to RF signals, you may prefer to
install an SMA connector so that you can run a coaxial cable to an
if the rocket is hiding in sage brush or a tree, or if the last GPS position
doesn't get you close enough because the rocket dropped into a canyon, or
the wind is blowing it across a dry lake bed, or something like that... Keith
- currently uses a Yaesu VX-7R, Bdale has a Baofung UV-5R
- which isn't as nice, but was a whole lot cheaper.
+ currently uses a Yaesu FT1D, Bdale has a Yaesu VX-7R, which
+ is a nicer radio in most ways but doesn't support APRS.
</para>
<para>
So, to recap, on the ground the hardware you'll need includes:
</section>
<section>
<title>Future Plans</title>
- <para>
- We've designed a simple GPS based radio tracker called TeleGPS.
- If all goes well, we hope to introduce this in the first
- half of 2014.
- </para>
<para>
We have designed and prototyped several “companion boards” that
- can attach to the companion connector on TeleMetrum and TeleMega
+ can attach to the companion connector on TeleMetrum,
+ TeleMega and EasyMega
flight computers to collect more data, provide more pyro channels,
and so forth. We do not yet know if or when any of these boards
will be produced in enough quantity to sell. If you have specific
<orderedlist inheritnum='inherit' numeration='arabic'>
<listitem>
<para>
- Make sure accelerometer-equipped products like TeleMetrum and
- TeleMega are aligned precisely along the axis of
+ Make sure accelerometer-equipped products like TeleMetrum,
+ TeleMega and EasyMega are aligned precisely along the axis of
acceleration so that the accelerometer can accurately
capture data during the flight.
</para>
<chapter>
<title>Updating Device Firmware</title>
<para>
- TeleMega, TeleMetrum v2 and EasyMini are all programmed directly
+ TeleMega, TeleMetrum v2, EasyMega and EasyMini are all programmed directly
over their USB connectors (self programming). TeleMetrum v1, TeleMini and
TeleDongle are all programmed by using another device as a
programmer (pair programming). It's important to recognize which
performance slightly.
</para>
<para>
- Self-programmable devices (TeleMega, TeleMetrum v2 and EasyMini)
+ Self-programmable devices (TeleMega, TeleMetrum v2, EasyMega and EasyMini)
are reprogrammed by connecting them to your computer over USB
</para>
<section>
<title>
- Updating TeleMega, TeleMetrum v2 or EasyMini Firmware
+ Updating TeleMega, TeleMetrum v2, EasyMega or EasyMini Firmware
</title>
<orderedlist inheritnum='inherit' numeration='arabic'>
<listitem>
</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term>EasyMega</term>
+ <listitem>
+ <para>
+ Connect pin 6 and pin 1 of the companion connector. Pin 1
+ can be identified by the square pad around it, and then
+ the pins could sequentially across the board. Be very
+ careful to <emphasis>not</emphasis> short pin 8 to
+ anything as that is connected directly to the battery. Pin
+ 7 carries 3.3V and the board will crash if that is
+ connected to pin 1, but shouldn't damage the board.
+ </para>
+ </listitem>
+ </varlistentry>
<varlistentry>
<term>TeleMetrum v2</term>
<listitem>
</listitem>
</itemizedlist>
</section>
+ <section>
+ <title>
+ EasyMega Specifications
+ </title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Recording altimeter for model rocketry.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Supports dual deployment and four auxiliary pyro channels
+ (a total of 6 events).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Barometric pressure sensor good to 100k feet MSL.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 1-axis high-g accelerometer for motor characterization, capable of
+ +/- 102g.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 9-axis IMU including integrated 3-axis accelerometer,
+ 3-axis gyroscope and 3-axis magnetometer.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ On-board 8 Megabyte non-volatile memory for flight data storage.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ USB interface for battery charging, configuration, and data recovery.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Fully integrated support for Li-Po rechargeable batteries.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Can use either main system Li-Po or optional separate pyro battery
+ to fire e-matches.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 1.25 x 1.25 inch board designed to fit inside 38mm air-frame coupler tube.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
<section>
<title>
TeleMetrum v2 Specifications
</mediaobject>
</informalfigure>
</section>
+ <section>
+ <title>EasyMega template</title>
+ <para>
+ EasyMega has overall dimensions of 1.250 x 2.250 inches, and
+ the mounting holes are sized for use with 4-40 or M3 screws.
+ </para>
+ <informalfigure>
+ <mediaobject id="EasyMegaTemplate">
+ <imageobject>
+ <imagedata format="SVG" fileref="easymega.svg"
+ scalefit="0" scale="100" align="center" />
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
+ </section>
<section>
<title>TeleMetrum template</title>
<para>
<title>Calibration</title>
<para>
There are only two calibrations required for TeleMetrum and
- TeleMega, and only one for TeleDongle, TeleMini and EasyMini.
+ TeleMega, and only one for EasyMega, TeleDongle, TeleMini and EasyMini.
All boards are shipped from the factory pre-calibrated, but
the procedures are documented here in case they are ever
needed. Re-calibration is not supported by AltosUI, you must
</para>
</section>
<section>
- <title>TeleMetrum and TeleMega Accelerometers</title>
+ <title>TeleMetrum, TeleMega and EasyMega Accelerometers</title>
<para>
While barometric sensors are factory-calibrated,
accelerometers are not, and so each must be calibrated once
</para>
<para>
In the unlikely event an accel cal goes badly, it is possible
- that TeleMetrum or TeleMega may always come up in 'pad mode'
+ that TeleMetrum, TeleMega or EasyMega may always come up in 'pad mode'
and as such not be listening to either the USB or radio link.
If that happens, there is a special hook in the firmware to
force the board back in to 'idle mode' so you can re-do the
<appendix>
<title>Release Notes</title>
<simplesect>
- <title>Version 1.41</title>
+ <title>Version 1.4.1</title>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="release-notes-1.4.1.xsl"
xpointer="xpointer(/article/*)"/>
</simplesect>
+ <simplesect>
+ <title>Version 1.5</title>
+ <xi:include
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="release-notes-1.5.xsl"
+ xpointer="xpointer(/article/*)"/>
+ </simplesect>
<simplesect>
<title>Version 1.4</title>
<xi:include
*
* M = 1, E = 3, bw = 75kHz
*
- * 20.5 kHz deviation, 9.6kbps signal
+ * 5.125 kHz deviation, 9.6kbps signal
*
- * m = 41 / 9.6, which is < 5.5:
+ * m = 10.25 / 9.6, which is < 5.5:
*
- * bw = 2.6 * 20.5 + 0.55 * 9.6 = 58.58kHz
+ * bw = 2.6 * 5.125 + 0.55 * 9.6 = 18.6kHz
*
- * M = 2, E = 3, bw = 62.5kHz
+ * M = 2, E = 3, bw = 53.6kHz
*
- * 20.5kHz deviation, 2.4kbps signal
+ * 1.28125kHz deviation, 2.4kbps signal
*
- * m = 41 / 2.4, which is > 5.5:
+ * m = 2.565 / 2.4, which is < 5.5:
*
- * bw = 2.1 * 20.5 + 1.9 * 2.4 = 47.61kHz
+ * bw = 2.6 * 20.5 + 1.9 * 2.4 = 47.61kHz
*
* M = 3, E = 3, bw = 53.6kHz
*
*/
#define CHANBW_M_384 1
-#define CHANBW_M_96 2
+#define CHANBW_M_96 3
#define CHANBW_M_24 3
#define CHANBW_E 3
*
* F = 24e6/2**17 * (8 + DEVIATION_M) * 2**DEVIATION_E
*
- * So M is 6 and E is 3
+ * For 20.5kHz deviation, M is 6 and E is 3
+ * For 5.125kHz deviation, M is 6 and E is 1
+ * For 1.28125kHz deviation, M is 0 and E is 0
*/
-#define DEVIATION_M 6
-#define DEVIATION_E 3
+#define DEVIATION_M_384 6
+#define DEVIATION_E_384 3
+
+#define DEVIATION_M_96 6
+#define DEVIATION_E_96 1
+
+#define DEVIATION_M_24 0
+#define DEVIATION_E_24 0
/*
* For our RDF beacon, set the symbol rate to 2kBaud (for a 1kHz tone),
RF_CHANNR_OFF, 0,
- RF_DEVIATN_OFF, ((DEVIATION_E << RF_DEVIATN_DEVIATION_E_SHIFT) |
- (DEVIATION_M << RF_DEVIATN_DEVIATION_M_SHIFT)),
-
/* SmartRF says set LODIV_BUF_CURRENT_TX to 0
* And, we're not using power ramping, so use PA_POWER 0
*/
RF_MDMCFG1_NUM_PREAMBLE_4 |
(2 << RF_MDMCFG1_CHANSPC_E_SHIFT)),
- RF_DEVIATN_OFF, ((DEVIATION_E << RF_DEVIATN_DEVIATION_E_SHIFT) |
- (DEVIATION_M << RF_DEVIATN_DEVIATION_M_SHIFT)),
+#if !HAS_RADIO_RATE
+ RF_DEVIATN_OFF, ((DEVIATION_E_384 << RF_DEVIATN_DEVIATION_E_SHIFT) |
+ (DEVIATION_M_384 << RF_DEVIATN_DEVIATION_M_SHIFT)),
+#endif
/* max packet length -- now set inline */
RF_PKTCTRL1_OFF, ((1 << PKTCTRL1_PQT_SHIFT)|
};
#if HAS_RADIO_RATE
-static __code uint8_t packet_rate_setup[] = {
+static __code struct {
+ uint8_t mdmcfg4;
+ uint8_t deviatn;
+} packet_rate_setup[] = {
/* 38400 */
- ((CHANBW_E << RF_MDMCFG4_CHANBW_E_SHIFT) |
- (CHANBW_M_384 << RF_MDMCFG4_CHANBW_M_SHIFT) |
- (DRATE_E_384 << RF_MDMCFG4_DRATE_E_SHIFT)),
+ {
+ ((CHANBW_E << RF_MDMCFG4_CHANBW_E_SHIFT) |
+ (CHANBW_M_384 << RF_MDMCFG4_CHANBW_M_SHIFT) |
+ (DRATE_E_384 << RF_MDMCFG4_DRATE_E_SHIFT)),
+ ((DEVIATION_E_384 << RF_DEVIATN_DEVIATION_E_SHIFT) |
+ (DEVIATION_M_384 << RF_DEVIATN_DEVIATION_M_SHIFT)),
+ },
/* 9600 */
- ((CHANBW_E << RF_MDMCFG4_CHANBW_E_SHIFT) |
- (CHANBW_M_96 << RF_MDMCFG4_CHANBW_M_SHIFT) |
- (DRATE_E_96 << RF_MDMCFG4_DRATE_E_SHIFT)),
+ {
+ ((CHANBW_E << RF_MDMCFG4_CHANBW_E_SHIFT) |
+ (CHANBW_M_96 << RF_MDMCFG4_CHANBW_M_SHIFT) |
+ (DRATE_E_96 << RF_MDMCFG4_DRATE_E_SHIFT)),
+ ((DEVIATION_E_96 << RF_DEVIATN_DEVIATION_E_SHIFT) |
+ (DEVIATION_M_96 << RF_DEVIATN_DEVIATION_M_SHIFT)),
+ },
/* 2400 */
- ((CHANBW_E << RF_MDMCFG4_CHANBW_E_SHIFT) |
- (CHANBW_M_24 << RF_MDMCFG4_CHANBW_M_SHIFT) |
- (DRATE_E_24 << RF_MDMCFG4_DRATE_E_SHIFT)),
+ {
+ ((CHANBW_E << RF_MDMCFG4_CHANBW_E_SHIFT) |
+ (CHANBW_M_24 << RF_MDMCFG4_CHANBW_M_SHIFT) |
+ (DRATE_E_24 << RF_MDMCFG4_DRATE_E_SHIFT)),
+ ((DEVIATION_E_24 << RF_DEVIATN_DEVIATION_E_SHIFT) |
+ (DEVIATION_M_24 << RF_DEVIATN_DEVIATION_M_SHIFT)),
+ },
};
#endif
RF_FREQ0 = (uint8_t) (ao_config.radio_setting);
RF_PKTLEN = len;
#if HAS_RADIO_RATE
- RF_MDMCFG4 = packet_rate_setup[ao_config.radio_rate];
+ RF_MDMCFG4 = packet_rate_setup[ao_config.radio_rate].mdmcfg4;
+ RF_DEVIATN = packet_rate_setup[ao_config.radio_rate].deviatn;
#endif
}
}
/*
- * Packet deviation is 20.5kHz
+ * Packet deviation
*
* fdev = fosc >> 24 * (256 + dev_m) << dev_e
*
+ * Deviation for 38400 baud should be 20.5kHz:
+ *
* 32e6Hz / (2 ** 24) * (256 + 80) * (2 ** 5) = 20508Hz
+ *
+ * Deviation for 9600 baud should be 5.125kHz:
+ *
+ * 32e6Hz / (2 ** 24) * (256 + 80) * (2 ** 3) = 5127Hz
+ *
+ * Deviation for 2400 baud should be 1.28125kHz, but cc1111 and
+ * cc115l can't do that, so we'll use 1.5kHz instead:
+ *
+ * 32e6Hz / (2 ** 24) * (256 + 137) * (2 ** 1) = 1499Hz
*/
-#define PACKET_DEV_E 5
-#define PACKET_DEV_M 80
+#define PACKET_DEV_M_384 80
+#define PACKET_DEV_E_384 5
+
+#define PACKET_DEV_M_96 80
+#define PACKET_DEV_E_96 3
+
+#define PACKET_DEV_M_24 137
+#define PACKET_DEV_E_24 1
/*
* For our packet data
* Rdata = -------------------------------------- * fosc
* 2 ** 39
*
+ * Given the bit period of the baseband, T, the bandwidth of the
+ * baseband signal is B = 1/(2T). The overall bandwidth of the
+ * modulated signal is then Channel bandwidth = 2Δf + 2B.
+ *
+ * 38400 -- 2 * 20500 + 38400 = 79.4 kHz
+ * 9600 -- 2 * 5.125 + 9600 = 19.9 kHz
+ * 2400 -- 2 * 1.5 + 2400 = 5.4 khz
+ *
* Symbol rate 38400 Baud:
*
* DATARATE_M = 239914
* DATARATE_E = 9
- * CHANBW = 74.42 (round to 100)
+ * CHANBW = 79.4 (round to 100)
*
* Symbol rate 9600 Baud:
*
* DATARATE_M = 239914
* DATARATE_E = 7
- * CHANBW = 58.58 (round to 62.5)
+ * CHANBW = 19.9 (round to 20)
*
* Symbol rate 2400 Baud:
*
* DATARATE_M = 239914
* DATARATE_E = 5
- * CHANBW = 47.61 (round to 50)
+ * CHANBW = 5.0 (round to 8.0)
*/
#define PACKET_DRATE_M 239914
#define PACKET_DRATE_E_384 9
-#define PACKET_CHAN_BW_384 0x02 /* 200 / 2 = 100 */
+
+/* 200 / 2 = 100 */
+#define PACKET_CHAN_BW_384 ((0 << CC1120_CHAN_BW_CHFILT_BYPASS) | \
+ (CC1120_CHAN_BW_ADC_CIC_DECFACT_20 << CC1120_CHAN_BW_ADC_CIC_DECFACT) | \
+ (2 << CC1120_CHAN_BW_BB_CIC_DECFACT))
#define PACKET_DRATE_E_96 7
-#define PACKET_CHAN_BW_96 0x42 /* 125 / 2 = 62.5 */
+/* 200 / 10 = 20 */
+#define PACKET_CHAN_BW_96 ((0 << CC1120_CHAN_BW_CHFILT_BYPASS) | \
+ (CC1120_CHAN_BW_ADC_CIC_DECFACT_20 << CC1120_CHAN_BW_ADC_CIC_DECFACT) | \
+ (10 << CC1120_CHAN_BW_BB_CIC_DECFACT))
#define PACKET_DRATE_E_24 5
-#define PACKET_CHAN_BW_24 0x04 /* 200 / 4 = 50 */
+/* 200 / 25 = 8 */
+#define PACKET_CHAN_BW_24 ((0 << CC1120_CHAN_BW_CHFILT_BYPASS) | \
+ (CC1120_CHAN_BW_ADC_CIC_DECFACT_20 << CC1120_CHAN_BW_ADC_CIC_DECFACT) | \
+ (25 << CC1120_CHAN_BW_BB_CIC_DECFACT))
static const uint16_t packet_setup[] = {
- CC1120_DEVIATION_M, PACKET_DEV_M,
- CC1120_MODCFG_DEV_E, ((CC1120_MODCFG_DEV_E_MODEM_MODE_NORMAL << CC1120_MODCFG_DEV_E_MODEM_MODE) |
- (CC1120_MODCFG_DEV_E_MOD_FORMAT_2_GFSK << CC1120_MODCFG_DEV_E_MOD_FORMAT) |
- (PACKET_DEV_E << CC1120_MODCFG_DEV_E_DEV_E)),
CC1120_DRATE1, ((PACKET_DRATE_M >> 8) & 0xff),
CC1120_DRATE0, ((PACKET_DRATE_M >> 0) & 0xff),
CC1120_PKT_CFG2, ((CC1120_PKT_CFG2_CCA_MODE_ALWAYS_CLEAR << CC1120_PKT_CFG2_CCA_MODE) |
};
static const uint16_t packet_setup_384[] = {
+ CC1120_DEVIATION_M, PACKET_DEV_M_384,
+ CC1120_MODCFG_DEV_E, ((CC1120_MODCFG_DEV_E_MODEM_MODE_NORMAL << CC1120_MODCFG_DEV_E_MODEM_MODE) |
+ (CC1120_MODCFG_DEV_E_MOD_FORMAT_2_GFSK << CC1120_MODCFG_DEV_E_MOD_FORMAT) |
+ (PACKET_DEV_E_384 << CC1120_MODCFG_DEV_E_DEV_E)),
CC1120_DRATE2, ((PACKET_DRATE_E_384 << CC1120_DRATE2_DATARATE_E) |
(((PACKET_DRATE_M >> 16) & CC1120_DRATE2_DATARATE_M_19_16_MASK) << CC1120_DRATE2_DATARATE_M_19_16)),
CC1120_CHAN_BW, PACKET_CHAN_BW_384,
};
static const uint16_t packet_setup_96[] = {
+ CC1120_DEVIATION_M, PACKET_DEV_M_96,
+ CC1120_MODCFG_DEV_E, ((CC1120_MODCFG_DEV_E_MODEM_MODE_NORMAL << CC1120_MODCFG_DEV_E_MODEM_MODE) |
+ (CC1120_MODCFG_DEV_E_MOD_FORMAT_2_GFSK << CC1120_MODCFG_DEV_E_MOD_FORMAT) |
+ (PACKET_DEV_E_96 << CC1120_MODCFG_DEV_E_DEV_E)),
CC1120_DRATE2, ((PACKET_DRATE_E_96 << CC1120_DRATE2_DATARATE_E) |
(((PACKET_DRATE_M >> 16) & CC1120_DRATE2_DATARATE_M_19_16_MASK) << CC1120_DRATE2_DATARATE_M_19_16)),
CC1120_CHAN_BW, PACKET_CHAN_BW_96,
};
static const uint16_t packet_setup_24[] = {
+ CC1120_DEVIATION_M, PACKET_DEV_M_24,
+ CC1120_MODCFG_DEV_E, ((CC1120_MODCFG_DEV_E_MODEM_MODE_NORMAL << CC1120_MODCFG_DEV_E_MODEM_MODE) |
+ (CC1120_MODCFG_DEV_E_MOD_FORMAT_2_GFSK << CC1120_MODCFG_DEV_E_MOD_FORMAT) |
+ (PACKET_DEV_E_24 << CC1120_MODCFG_DEV_E_DEV_E)),
CC1120_DRATE2, ((PACKET_DRATE_E_24 << CC1120_DRATE2_DATARATE_E) |
(((PACKET_DRATE_M >> 16) & CC1120_DRATE2_DATARATE_M_19_16_MASK) << CC1120_DRATE2_DATARATE_M_19_16)),
CC1120_CHAN_BW, PACKET_CHAN_BW_24,
projects / fw / altos / commitdiff
