# Home
## About Avionics Anonymous
Avionics Anonymous is dedicated to providing high-quality electronics to the hobby robotics community. Many of our offerings were born out of needs we had on our own projects and found a surprising lack of good options on the market. We built these devices to meet our own needs and are excited to share with the world!
> **Note** This guide is still a work in progress! Please contact us if you have questions not addressed here.
## Getting Started
### Check out the pages below for specifics on each of our devices:
* [Laser Interface](/devices/laser_interface)
* [MiniMag](/devices/minimag)
* [MaxiMag](/devices/maximag)
* [GNSSMag](/devices/gnssmag)
* [MicroADC](/devices/microadc)
* [Voltage Monitor](/devices/power_monitor)
* [Engine Monitor](/devices/engine_monitor)
* [Light Controller](/devices/lightcontroller)
### Check out these pages for general tips that apply to most devices:
* [Firmware Update](/general/firmware_update) for how to update firmware on AvAnon CAN nodes
* [Parameter Adjustment](/general/parameters) for how to adjust parameters on AvAnon CAN nodes
# Parameters
All AvAnon nodes have some internal parameters which can be adjusted via the UAVCAN interface. Consult the page for each AvAnon device for details on each parameter.
## Changing parameters using UAVCAN GUI and SLCAN tool
1. Install the [UAVCAN GUI](https://github.com/UAVCAN/gui_tool)
2. Connect your [SLCAN tool](https://zubax.com/products/babel) to your computer
3. Open the UAVCAN GUI and select your SLCAN tool
4. Set your local Node ID and click the "check" button
5. Connect your AvAnon node to your SLCAN tool
* The node should appear in the GUI "Online Nodes" list
6. Double-click on the AvAnon node
* A window like this should appear
7. Under "Configuration Parameters, click on "Fetch All"
8. The parameters will appear in the list below
9. Double-click on a parameter to open the param editor dialog
10. Change the parameter as desired, noting the displayed min and max values. Consult the page for each AvAnon device for details on each parameter.
11. Click on "Send" to send the new value to the node, then close the editor dialog
12. Repeat steps 9-11 for any other parameter changes
13. When done with all changes, select "Store All" to write the parameter changes to the device's nonvolatile memory
14. You're done!
# Firmware Update
The firmware on all AvAnon UAVCAN nodes can be updated via their UAVCAN interface. Make sure to keep your devices updated for the best performance! Firmware download links and release notes can be found near the bottom of each device page.
## Updating using UAVCAN GUI and SLCAN tool
1. Download the latest firmware for your AvAnon node, save it somewhere accessible on your computer, and unzip the folder.
2. Install the [UAVCAN GUI](https://github.com/UAVCAN/gui_tool)
3. Connect your [SLCAN tool](https://zubax.com/products/babel) to your computer
4. Open the UAVCAN GUI and select your SLCAN tool
5. Set your local Node ID and click the "check" button
6. Connect your AvAnon node to your SLCAN tool
* The node should appear in the GUI "Online Nodes" list
7. Double-click on the AvAnon node you want to update
* A window like this should appear
8. Click on "Update Firmware"
9. You may get a warning that no dynamic ID server is running that asks if you want to continue. Select "yes".
10. Navigate to the AvAnon firmware file you downloaded earlier and select "open"
**Warning** Make sure you select the correct firmware file for this node! Using this method, there is no protection against flashing firmware for the wrong node.
11. Sit back and wait!
* You should see the node "Mode" switch to "SOFTWARE UPDATE"
* The LED's on your AvAnon node should flash yellow/red alternately
* Periodically, updates will appear in the GUI "Log Messages" box showing download progress
12. When the firmware update is successful, the node will restart
* The displayed "Mode" will return to operational
* The node's LED will flash green
**Note** Some devices (like the GNSS) may not restart cleanly and the LED may flash red. If this happens, disconnect and reconnect the node. It should start up normally.
13. Verify the expected version is displayed next to "Software Version"
* If the version does not match what you tried to load, the upload may have failed. Certain CAN tools seem to provide more reliable transfers than others, and the firmware loader in early firmware versions is not very robust to dropped data. If it fails, disconnect your node and start again at step 6. With some tools, this may take several attempts. Upcoming firmware will improve the robustness of this update system.
## Updating automatically using PX4-based autopilots
**Note** Not ready yet - check back soon!
# Laser Interface
## Overview
The [Avionics Anonymous Laser Altimeter Interface](https://www.avionicsanonymous.com/product-page/uavcan-laser-interface) is a tiny interface for [several common laser rangefinders](/devices/laser_interface#currently-supported-lasers) that allows connection to Pixhawk and other similar autopilots via UAVCAN - A nice robust interface, no sketchy long-distance I2C wiring and no hogged serial ports! These lasers are great for use as laser altimeters which help with nice auto landings. Comes fully assembled, ready to use!
### Currently supported Lasers
At time of writing the following rangefinders are supported:
* Lightware SF02
* Lightware SF10/a
* Lightware SF10/b
* Lightware SF10/c
* Lightware SF11/b
* Lightware SF11/c
* Lightware SF(LW)20/b
* Lightware SF(LW)20/c
* Lightware SF30/D
Coming soon:
* Lidar Lite
* Others - contact us with your needs!
### What makes it special?
* Robust UAVCAN interface is compatible with most Pixhawks and similar autopilots and makes it safe to install your laser far away from the autopilot, wherever is convenient!
* Onboard power filtering for connected laser
* Mount with screws through mounting ears or snip them off and foam tape it straight to your laser
* Update firmware via CAN interface
### Specifications
* Weight: 3.2 grams
* Size: 1.25in x 0.75in x 0.25in
* Power: 4.0V to 5.5V, XXmA
### Required Accessories
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
### Where to Buy
* [Avionics Anonymous Store](https://www.avionicsanonymous.com/product-page/uavcan-laser-interface)
* [Tindie](https://www.tindie.com/products/avionicsanonymous/uavcan-laser-altimeter-interface/)
## User Guide
### Wiring
The rangefinder (laser) is connected to the AvAnon Laser Interface board, which is connected to one of the CAN ports on your autopilot. The wiring is per the pinout below, or the necessary cables can be purchased to connect to your system right out of the box:
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
The interface board provides a filtered power output for the laser, but does not provide its own regulation. Therefore, the laser must be compatible with whatever voltage is supplied to the Laser Interface.
#### Pinouts
**CAN Connector**
| Pin | Name | Description |
| --- | --------- | ----------------------------------------------------------------------------------- |
| 1 | POWER\_IN | Power Supply. 4.0-5.5V supported, but must also be compatible with connected laser. |
| 2 | CAN\_H | CAN high |
| 3 | CAN\_L | CAN low |
| 4 | GND | Signal/power ground. |
**Laser Connector**
| Pin | Name | Description |
| --- | ---------- | -------------------------------------- |
| 1 | POWER\_OUT | Filtered power at the supply voltage. |
| 2 | TX/SCL | TX for serial mode, Clock for I2C mode |
| 3 | RX/SDA | RX for serial mode, Data for I2C mode |
| 4 | GND | Signal/power ground. |
### Configuration
#### Autopilot Configuration
**PX4**
Several autopilot parameters must be set using QGC or similar:
* UAVCAN must be enabled by setting *UAVCAN\_ENABLE* non zero. Set this to 1 for basic functionality or 2 to allow the device's UAVCAN parameters to be accessed via QGC.
* The minimum and maximum valid range for the laser must be set in the parameters *UAVCAN\_RNG\_MIN* and *UAVCAN\_RNG\_MAX*. These should be set according to the rangefinder manufacturer's datasheet.
#### Rangefinder Configuration
Certain parameters must be configured in your rangefinder per the manufacturer's guidance
| Rangefinder Model | Notes |
| -------------------- | ----------------------------------------------------- |
| Lightware SF02 | Must be set to 115200 baud |
| Lightware SF10/a | Must be set to 115200 baud |
| Lightware SF10/b | Must be set to 115200 baud |
| Lightware SF10/c | Must be set to 115200 baud |
| Lightware SF11/c | Must be set to 115200 baud |
| Lightware SF11/b | Must be set to 115200 baud |
| Lightware SF(LW)20/b | Must be set to 115200 baud. Returns default distance. |
| Lightware SF11/b | Must be set to 115200 baud. Returns default distance. |
| Lightware SF30/D | Must be set to 115200 baud. Returns default distance. |
#### Node Configuration
The Laser Interface node has a number of parameters accessible via the UAVCAN interface. These may be set following the steps outlined [here](/general/parameters)
**Parameters**
| Parameter Name | Description | Default Value | Allowable Values |
| --------------- | --------------------------------------------------------------- | ----------------- | --------------------------------- |
| node\_id | Node ID for this device | 103 | 1-125 |
| rangefinder\_hw | Rangefinder type specifier - see list below | 5 (or as ordered) | 1-10 (see below) |
| first\_return | Use "first" or "last" return range, if supported by rangefinder | 0 | 0 = last return, 1 = first return |
**Rangefinder Hardware Options**
| Rangefinder Model | rangefinder\_hw Value | Wiring Type |
| -------------------- | --------------------- | ----------- |
| Lightware SF02 | 1 | Serial |
| Lightware SF10/a | 2 | Serial |
| Lightware SF10/b | 3 | Serial |
| Lightware SF10/c | 4 | Serial |
| Lightware SF11/c | 5 | Serial |
| Lightware SF11/b | 6 | Serial |
| Lightware SF(LW)20/b | 7 | Serial |
| Lightware SF11/b | 8 | Serial |
| Lightware SF30/D | 10 | Serial |
## Firmware
{% file src="/files/-MItc2dFbuHcshp1pQ-t" %}
Firmware v1.2
{% endfile %}
### Release Notes
#### v1.2
* Improve SF0X timeout recovery
#### v1.0
* Initial Release
# MiniMag
## Overview
The [Avionics Anonymous MiniMag Magnetometer](https://www.avionicsanonymous.com/product-page/uavcan-magnetometer) is a high-precision magnetometer for small unmanned aircraft. It includes a high-quality Memsic MMC5983MA magnetometer enabling sub-1-degree heading accuracy. This interfaces to your autopilot via robust UAVCAN interface - no sketchy I2C wiring for your magnetometer!
### What makes it special?
* Extremely high-quality Memsic magnetometer IC allows better than 1-degree heading accuracy in low-interference installations
* Robust UAVCAN interface is compatible with most Pixhawks and similar autopilots and makes it safe to install your laser far away from the autopilot, wherever is convenient!
* Mount with screws through mounting ears or snip them off and foam tape it to your airframe
* Update firmware via CAN interface
### Specifications
* Weight: 3.2 grams
* Size: 1.25in x 0.75in x 0.25in
* Power: 4.0V to 5.5V, XXmA
### Required Accessories
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
#### Where to Buy
* [Avionics Anonymous Store](https://www.avionicsanonymous.com/product-page/uavcan-magnetometer)
* [Tindie](https://www.tindie.com/products/avionicsanonymous/uavcan-magnetometer/)
## User Guide
### Wiring
The MiniMag is connected to your autopilot via CAN bus. The wiring is per the pinout below, or the necessary cables can be purchased to connect to your system right out of the box:
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
#### Pinouts
**CAN Connector**
| Pin | Name | Description |
| --- | --------- | --------------------------------- |
| 1 | POWER\_IN | Power Supply. 4.0-5.5V supported. |
| 2 | CAN\_H | CAN high |
| 3 | CAN\_L | CAN low |
| 4 | GND | Signal/power ground. |
### Mounting
#### Attachment
The MiniMag can be mounted several ways. It includes 4x screw holes for 4-40/M3 screws. If using screws, make sure to use aluminum or otherwise non-ferrous screws! You can also simply adhere it to your vehicle with double-sided tape, and if doing so, you can cut off the mounting ears to save some weight and space.
#### Orientation
The MiniMag is normally mounted with the "flat" side down (components on the board pointed up) and the connector-end of the board pointed toward the back of your vehicle.
It can, however, be mounted in any orientation. If mounted flat-side-down and only rotated in yaw, you can use the built-in rotation parameter to adjust for this. Enter the value (in degrees) that the board is rotated in yaw. For example, if the connector-end of the board points toward the left side of your vehicle, enter "90" for rotation.
For mounting orientations other than simple yaw, please use the external mag rotation settings in your autopilot to match your mounting.
### Configuration
#### Autopilot Configuration
**PX4**
Several autopilot parameters must be set using QGC or similar:
* UAVCAN must be enabled by setting *UAVCAN\_ENABLE* non zero. Set this to 1 for basic functionality or 2 to allow the device's UAVCAN parameters to be accessed via QGC.
#### Node Configuration
The MiniMag node has a number of parameters accessible via the UAVCAN interface. These may be set following the steps outlined [here](/general/parameters)
**Parameters**
| Parameter Name | Description | Default Value | Allowable Values |
| ---------------- | ------------------------------------------------------------------------------------------- | ------------- | ---------------- |
| node\_id | Node ID for this device | 102 | 1-125 |
| rotation | Board rotation in degrees | 0 | 0-360 |
| update\_rate\_hz | Rate at which magnetic field data is published in Hz | 30 | 1-30 |
| auto\_mag\_set | Enable [auto temperature compensation](/devices/minimag#automatic-temperature-compensation) | 0 | 0-1 |
**Automatic Temperature Compensation**
Setting the "auto\_mag\_set" parameter to 1 enables an experimental automatic temperature compensation. When enabled, every 10 seconds, the unit evaluates its internal temperature. if it has changed too much, the unit performs an automatic reset and set of the polarity of the sensing film and uses this to update thermal correction offsets. If the sensor undergoes significant changes in ambient temperature, this can dramatically improve stability and accuracy of its output, but also leads to small step changes in the magnetic field output when the offsets are updated. This will pose no issue for PX4 autopilots which fuse magnetic data into a Kalman filter, but you should ensure this behavior is safe in your application. Please contact us for more information.
**Warning** This feature has not been thoroughly vetted and is considered experimental! Use at your own risk.
## Firmware
{% file src="/files/-MItc2hg2lZssUSPM\_Au" %}
Firmware v1.3
{% endfile %}
### Release Notes
#### v1.3
* Reset sensor magnetization on boot
#### v1.2
* Improved firmware version reporting via CAN to support PX4-based firmware update
* Fix timer rollover issue which could cause a failed mag sample every \~72 minutes
#### v1.0
* Initial Release
# MaxiMag
## Overview
The [Avionics Anonymous MaxiMag Magnetometer](https://www.avionicsanonymous.com/product-page/uavcan-high-quality-magnetometer) is a high-precision magnetometer for small unmanned aircraft. It includes a high-quality PNI RM3100 magnetometer enabling sub-1-degree heading accuracy and no variation with temperature. This interfaces to your autopilot via robust UAVCAN interface - no sketchy I2C wiring for your magnetometer!
### What makes it special?
* Extremely high-quality RM3100 magnetometer IC allows better than 1-degree heading accuracy in low-interference installations
* Coil sensors are inherently insensitive to temperature, displaying no offset drift unlike typical IC magnetometers
* Robust UAVCAN interface is compatible with most Pixhawks and similar autopilots and makes it safe to install your laser far away from the autopilot, wherever is convenient!
* Mount with screws through mounting ears or snip them off and foam tape it to your airframe
* Update firmware via CAN interface
### Specifications
* Weight: <4 grams
* Size: 1.50in x 0.75in x 0.25in
* Power: 4.0V to 5.5V, XXmA
### Required Accessories
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
#### Where to Buy
* [Avionics Anonymous Store](https://www.avionicsanonymous.com/product-page/uavcan-high-quality-magnetometer)
## User Guide
### Wiring
The MaxiMag is connected to your autopilot via CAN bus. The wiring is per the pinout below, or the necessary cables can be purchased to connect to your system right out of the box:
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
#### Pinouts
**CAN Connector**
| Pin | Name | Description |
| --- | --------- | --------------------------------- |
| 1 | POWER\_IN | Power Supply. 4.0-5.5V supported. |
| 2 | CAN\_H | CAN high |
| 3 | CAN\_L | CAN low |
| 4 | GND | Signal/power ground. |
### Mounting
#### Attachment
The MaxiMag can be mounted several ways. It includes 4x screw holes for 4-40/M3 screws. If using screws, make sure to use aluminum or otherwise non-ferrous screws! You can also simply adhere it to your vehicle with double-sided tape, and if doing so, you can cut off the mounting ears to save some weight and space.
#### Orientation
The MaxiMag is normally mounted with the "flat" side down (components on the board pointed up) and the connector-end of the board pointed toward the back of your vehicle.
It can, however, be mounted in any orientation. If mounted flat-side-down and only rotated in yaw, you can use the built-in rotation parameter to adjust for this. Enter the value (in degrees) that the board is rotated in yaw. For example, if the connector-end of the board points toward the left side of your vehicle, enter "90" for rotation.
For mounting orientations other than simple yaw, please use the external mag rotation settings in your autopilot to match your mounting.
### Configuration
#### Autopilot Configuration
**PX4**
Several autopilot parameters must be set using QGC or similar:
* UAVCAN must be enabled by setting *UAVCAN\_ENABLE* non zero. Set this to 1 for basic functionality or 2 to allow the device's UAVCAN parameters to be accessed via QGC.
#### Node Configuration
The MaxiMag node has a number of parameters accessible via the UAVCAN interface. These may be set following the steps outlined [here](/general/parameters)
**Parameters**
| Parameter Name | Description | Default Value | Allowable Values |
| -------------- | ------------------------- | ------------- | ---------------- |
| node\_id | Node ID for this device | 102 | 1-125 |
| rotation | Board rotation in degrees | 0 | 0-360 |
## Firmware
### Release Notes
#### v1.4
* Initial Release
# GNSSMag
## Overview
The [Avionics Anonymous GNSSMag GPS and Magnetometer](https://www.avionicsanonymous.com/product-page/uavcan-gnss-mag) is a combination GPS and magnetometer for small unmanned aircraft. Includes a uBlox SAM-M8Q integrated multi-constellation GNSS unit and a high-quality Memsic MMC5983MA magnetometer enabling sub-1-degree heading accuracy. All of this interfaces to your autopilot via robust UAVCAN interface - no sketchy I2C wiring for your magnetometer! Comes fully assembled, ready to plug in and use! Also available without a magnetometer for applications using remote mags.
### What makes it special?
* Extremely high-quality Memsic magnetometer IC allows \~0.5deg heading accuracy in low-interference installations
* uBlox multi-constellation GPS provides excellent performance in any flying scenario
* Robust UAVCAN interface is compatible with most Pixhawks and similar autopilots and makes it safe to install your laser far away from the autopilot, wherever is convenient!
* Broken-out GPS interrupt pin for special timing applications
* Drop-in replacement for competitive UAVCAN GPS/magnetometer unit
* Update firmware via CAN interface
### Specifications
* Weight: 16.9 grams
* Size: 55m x 55mm x 10mm
* Power: 4.0V to 5.5V, XXmA
### Required Accessories
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
#### Where to Buy
* [Avionics Anonymous Store](https://www.avionicsanonymous.com/product-page/uavcan-gnss-mag)
* [Tindie](https://www.tindie.com/products/avionicsanonymous/uavcan-gps-magnetometer/)
## User Guide
### Wiring
The GNSSMag is connected to your autopilot via CAN bus. The wiring is per the pinout below, or the necessary cables can be purchased to connect to your system right out of the box:
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
#### Pinouts
**CAN Connector**
| Pin | Name | Description |
| --- | --------- | --------------------------------- |
| 1 | POWER\_IN | Power Supply. 4.0-5.5V supported. |
| 2 | CAN\_H | CAN high |
| 3 | CAN\_L | CAN low |
| 4 | GND | Signal/power ground. |
**AUX Connector**
| Pin | Name | Description |
| --- | -------- | ---------------------------------------------- |
| 1 | EXTINT | GPS external interrupt input. Normally unused. |
| 2 | Reserved | Reserved for future use |
| 3 | PPS | GPS Pulse-Per-Second output |
### Configuration
#### Autopilot Configuration
**PX4**
Several autopilot parameters must be set using QGC or similar:
* UAVCAN must be enabled by setting *UAVCAN\_ENABLE* non zero. Set this to 1 for basic functionality or 2 to allow the device's UAVCAN parameters to be accessed via QGC.
#### Node Configuration
The GNSSMag node has a number of parameters accessible via the UAVCAN interface. These may be set following the steps outlined [here](/general/parameters)
**Parameters**
| Parameter Name | Description | Default Value | Allowable Values |
| ---------------- | ------------------------------------------------------------------------------------------- | ------------- | ---------------- |
| node\_id | Node ID for this device | 120 | 1-125 |
| rotation | Board rotation in degrees | 0 | 0-360 |
| update\_rate\_hz | Rate at which magnetic field data is published in Hz | 30 | 0-30 |
| auto\_mag\_set | Enable [auto temperature compensation](/devices/gnssmag#automatic-temperature-compensation) | 0 | 0-1 |
**Automatic Temperature Compensation**
Setting the "auto\_mag\_set" parameter to 1 enables an experimental automatic temperature compensation. When enabled, every 10 seconds, the unit evaluates its internal temperature. if it has changed too much, the unit performs an automatic reset and set of the polarity of the sensing film and uses this to update thermal correction offsets. If the sensor undergoes significant changes in ambient temperature, this can dramatically improve stability and accuracy of its output, but also leads to small step changes in the magnetic field output when the offsets are updated. This will pose no issue for PX4 autopilots which fuse magnetic data into a Kalman filter, but you should ensure this behavior is safe in your application. Please contact us for more information.
**Warning** This feature has not been thoroughly vetted and is considered experimental! Use at your own risk.
# MicroADC
## Overview
The [Avionics Anonymous MicroADC Air Data Computer](https://www.avionicsanonymous.com/product-page/microadc) is a tiny, richly-featured Air Data Computer (ADC) for small unmanned airplanes. Includes an MS5611 barometric pressure sensor for 10cm-resolution altitude, a Honeywell RSC-series differential pressure transducer for extremely accurate airspeed, and a thermistor interface with high-resolution convertor for air temperature measurement with less than 1 degree precision. All of this interfaces to your autopilot via robust UAVCAN interface - no sketchy I2C wiring! Comes fully assembled, ready to use!
### What makes it special?
* High-resolution, temperature-compensated airspeed sensor - low-range models are accurate to fractions of a knot!
* Sealed barometer case with port for plumbing to proper static source
* Onboard heaters keep barometer in accurate sensing range, even when it's below freezing outside!
* True air temperature measurement via included OAT probe
* Onboard computer calculates air density and true airspeed
* Robust UAVCAN interface is compatible with most Pixhawks and similar autopilots and makes it safe to install this out in a wing or wherever is convenient!
* Update firmware via CAN interface
### Specifications
* Weight: 6.1 grams
* Size: 1.5in x 1.15in x 0.47in
* Power: 4.0V to 5.5V, XXmA
### Required Accessories
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
#### Where to Buy
* [Avionics Anonymous Store](https://www.avionicsanonymous.com/product-page/microadc)
* [Tindie](https://www.tindie.com/products/avionicsanonymous/uavcan-air-data-computer-airspeed-sensor/)
## User Guide
### Wiring
The MicroADC is connected to your autopilot via CAN bus. The wiring is per the pinout below, or the necessary cables can be purchased to connect to your system right out of the box:
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
#### Pinouts
**CAN Connector**
| Pin | Name | Description |
| --- | --------- | --------------------------------- |
| 1 | POWER\_IN | Power Supply. 4.0-5.5V supported. |
| 2 | CAN\_H | CAN high |
| 3 | CAN\_L | CAN low |
| 4 | GND | Signal/power ground. |
**OAT Connector**
| Pin | Name | Description |
| --- | ---------- | ----------------------- |
| 1 | Thermistor | Included OAT thermistor |
| 2 | Thermistor | Included OAT thermistor |
### Plumbing
The MicroADC must be plumbed to a clean source of both pitot and static pressure. Typically, this is accomplished via a pitot/static probe, but a static source can also be installed in a carefully-chosen location on the fuselage.
Two barbed fittings are provided to connect to 1/16" ID tubing. The upper barb, which connects only to the differential pressure transducer, is for pitot pressure. The lower barb, which connects to both the differential pressure transducer and barometer, is for static pressure.
### Configuration
#### Autopilot Configuration
**PX4**
Several autopilot parameters must be set using QGC or similar:
* UAVCAN must be enabled by setting *UAVCAN\_ENABLE* non zero. Set this to 1 for basic functionality or 2 to allow the device's UAVCAN parameters to be accessed via QGC.
#### Node Configuration
The MicroADC node has a number of parameters accessible via the UAVCAN interface. These may be set following the steps outlined [here](/general/parameters)
**Parameters**
| Parameter Name | Description | Default Value | Allowable Values |
| --------------- | ---------------------------------------------------------------- | ------------- | ---------------- |
| node\_id | Node ID for this device | 101 | 1-125 |
| autozero\_time | Time in seconds from boot at which airspeed sensor is zeroed | 5 | 0-360 |
| pub\_airspeed | Enable/Disable publish of calculated indicated and true airspeed | 0 | 0-1 |
| pub\_raw\_press | Enable/Disable publish of raw differential pressure | 1 | 0-1 |
***Notes on airspeed vs raw pressure***
The MicroADC is capable of publishing calculated indicated and true airspeed based on its sensors. This is valuable for systems which don't have other means to compute these values. However, the PX4 autopilot system is build on an old assumption that only raw pressure is provided, so their existing data flow and sensor validation works better if only raw pressure is provided. The autopilot will still use the highly-accurate pressure and air temperature measurements from the microADC to calculate indicated and true airspeed at identical accuracy to that computed within the air data computer. For this reason, when using PX4, we suggest leaving the default settings - "pub\_airspeed" set to 0 and "pub\_raw\_press" set to 1.
## Firmware
{% file src="/files/-MPFdnzlDGOJE2g0UVx6" %}
Firmware v1.2
{% endfile %}
### Release Notes
#### v1.2
* Fix timing bug that could cause intermittent CAN bus lockups
* Support new thermistor type
#### v1.0
* Initial Release
# Voltage Monitor
## Overview
The Avionics Anonymous Voltage Monitor is a small 8-channel analog input unit. It allows measurement of analog sensors or monitoring of multiple batteries, voltage regulators, solar cells, etc - any 8 voltage sources that share a common ground. Connects to Pixhawk and other similar autopilots via UAVCAN. Comes fully assembled, ready to use!
**Note:** This device currently requires custom development to integrate with most autopilot software. Please contact us if you need assistance.
### What makes it special?
* 8 separate voltage inputs (common ground)
* Inputs are protected against under- and over-voltage
* Units are built to order with your preferred voltage range for each channel
* Publishes 8x standard UAVCAN "CircuitStatus" messages
* Robust UAVCAN interface is compatible with most Pixhawks and similar autopilots
* Update firmware via CAN interface
**Note:** Because the inputs share a common ground, this unit cannot be used to monitor series cell voltages in a battery.
### Specifications
* Weight: x.x grams
* Size: 1.15in x 1.35in x 0.25in
* Input Power: 4.0V to 5.5V, XXmA
### Required Accessories
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
### Where to Buy
* Coming soon! Contact us to order now.
## User Guide
### Wiring
The Voltage Monitor is connected to your autopilot via CAN bus. The wiring is per the pinout below, or the necessary cables can be purchased to connect to your system right out of the box:
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
Analog inputs are connected to channels 1-8 on the 8x2 header. The 8 ground pins, closest to the edge of the board, are tied to a common ground.
#### Pinouts
**CAN Connector**
| Pin | Name | Description |
| --- | --------- | --------------------------------- |
| 1 | POWER\_IN | Power Supply. 4.0-5.5V supported. |
| 2 | CAN\_H | CAN high |
| 3 | CAN\_L | CAN low |
| 4 | GND | Signal/power ground. |
**Input Connectors (8x)**
| Pin | Name | Description |
| --- | ---- | -------------- |
| 1 | S | Voltage signal |
| 2 | G | Ground |
### Configuration
#### Autopilot Configuration
Currently, this device is not natively supported by common autopilots. Add your own support for UAVCAN devices publishing "CircuitStatus" messages, or get in touch with us to ask about developing this support for you.
#### Node Configuration
The Voltage Monitor node has a number of parameters accessible via the UAVCAN interface. These may be set following the steps outlined [here](/general/parameters)
**Parameters**
| Parameter Name | Description | Default Value | Allowable Values |
| -------------- | ----------------------- | ------------- | ---------------- |
| node\_id | Node ID for this device | XXX | 1-125 |
## Firmware
### Release Notes
#### v1.0
* Initial Release
# Engine Monitor
## Overview
The \[Avionics Anonymous Engine Monitor] interfaces with common engine sensors. It provides 4x 0-5V analog inputs, 4x thermocouple inputs, and an RPM input. Connects to Pixhawk and other similar autopilots via UAVCAN. Comes fully assembled, ready to use!
**Note:** This device currently requires custom development to integrate with most autopilot software. Please contact us if you need assistance.
### What makes it special?
* 4x 0-5V analog inputs (with under- and over-voltage protection)
* 4x thermocouple inputs (K-type by default)
* 1x RPM input for connection to hall-effect sensors or output from electronic ignition systems
* Customized software configuration for your application
* Robust UAVCAN interface is compatible with most Pixhawks and similar autopilots
* Update firmware via CAN interface
### Specifications
* Weight: x.x grams
* Size: 1.65in x 1.59in x 0.5in
* Input Power: 4.0V to 5.5V, XXmA
### Required Accessories
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
### Where to Buy
* Coming soon! Contact us to order now.
## User Guide
### Wiring
The Engine Monitor is connected to your autopilot via CAN bus. The wiring is per the pinout below, or the necessary cables can be purchased to connect to your system right out of the box:
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
Analog inputs are connected to each of 4x Molex SL 2-pin locking headers. Polarity is marked on the board.
Thermocouples are connected to each of 4x screw-terminal blocks. Polarity is marked on the board.
The RPM signal is connected to a Molex SL 2-pin locking header. Polarity is marked on the board.
#### Pinouts
**CAN Connector**
| Pin | Name | Description |
| --- | --------- | --------------------------------- |
| 1 | POWER\_IN | Power Supply. 4.0-5.5V supported. |
| 2 | CAN\_H | CAN high |
| 3 | CAN\_L | CAN low |
| 4 | GND | Signal/power ground. |
**Analog Input Connectors (4x)**
| Pin | Name | Description |
| --- | ---- | -------------- |
| 1 | S | Voltage signal |
| 2 | G | Ground |
**Thermocouple Input Connectors (4x)**
| Pin | Name | Description |
| --- | ---- | --------------- |
| 1 | Y | Yellow (K-type) |
| 2 | R | Red (K-type) |
**RPM Input Connector**
| Pin | Name | Description |
| --- | ---- | ----------- |
| 1 | S | Signal |
| 2 | G | Ground |
### Configuration
#### Autopilot Configuration
Currently, this device is not natively supported by common autopilots, and the firmware of this device itself is customized to your needs. We can set it up to publish CircuitStatus, FuelStatus, Temperature, RPM, or any other default UAVCAN messages, or define your own DSDL and we'll integrate it. Add your own support for processing these UAVCAN messages in your autopilot, or get in touch with us to ask about developing this support for you.
#### Node Configuration
The Engine Monitor node has a number of parameters accessible via the UAVCAN interface. These may be set following the steps outlined [here](/general/parameters)
**Parameters**
| Parameter Name | Description | Default Value | Allowable Values |
| -------------- | ----------------------- | ------------- | ---------------- |
| node\_id | Node ID for this device | XXX | 1-125 |
## Firmware
### Release Notes
#### v1.0
* Initial Release
# Light Controller
## Overview
The [Avionics Anonymous Light Controller](https://www.avionicsanonymous.com/product-page/uavcan-light-controller) is a 4-channel light controller for unmanned vehicles. Each channel can be configured as a nav, strobe, beacon or landing light and can be programmed for various patterns. When connected to an autopilot running PX4, lights are automatically controlled based on the state of the autopilot! For example, beacons can be set to turn on when the system is prearmed and strobes to turn on when the system is armed, while nav lights may always be on. All of this is configurable via PX4 and UAVCAN parameters. The device interfaces to your autopilot via robust UAVCAN interface - much easier than trying to tune a PWM signal to give you the desired patterns using typical R/C light controllers.
### What makes it special?
* Designed for drop-in use with uniLight LED products
* Supports up to 30V lighting voltage
* Supports common-anode lights (combined lights that use the same power pin for multiple LED's)
* 4 separately-controllable channels supporting 3A each with a total limit of 10A.
* 3x connectors for 2 channels, 2x connectors for the other 2 channels means you can plug in multiple lights without having to splice
* Robust UAVCAN interface is compatible with most Pixhawks and similar autopilots
* Mount with screws through mounting holes
* Update firmware via CAN interface
### Specifications
* Weight: XX grams
* Size: XXin x XXin x XXin
* Power: 4.0V to 5.5V, XXmA
### Required Accessories
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
#### Where to Buy
* [Avionics Anonymous Store](https://www.avionicsanonymous.com/product-page/uavcan-light-controller)
## User Guide
### Wiring
The Light Controller is connected to your autopilot via CAN bus. The wiring is per the pinout below, or the necessary cables can be purchased to connect to your system right out of the box:
* [CAN Harness](https://www.avionicsanonymous.com/product-page/uavcan-interconnect-cable) - connects between the autopilot and a CAN node and between each CAN node on the bus
* [CAN Terminator](https://www.avionicsanonymous.com/product-page/uavcan-terminator) - connects to the last device on the CAN bus
#### Pinouts
**CAN Connector**
| Pin | Name | Description |
| --- | --------- | --------------------------------- |
| 1 | POWER\_IN | Power supply. 4.0-5.5V supported. |
| 2 | CAN\_H | CAN high |
| 3 | CAN\_L | CAN low |
| 4 | GND | Signal/power ground. |
**Power Input Connector**
| Pin | Name | Description |
| --- | --------- | ------------------------------------ |
| 1 | POWER\_IN | Light power supply. 5-30V supported. |
| 2 | GND | Light power ground. |
**Light Output Connector**
| Pin | Name | Description |
| --- | --------- | ------------------- |
| 1 | POWER\_IN | Light power output. |
| 2 | GND | Light power ground. |
### Mounting
#### Attachment
The Light Controller includes 4x screw holes for 4-40/M3 screws. Consider using standoffs or otherwise spacing the board off of flat surfaces to protect the pins which protrude through the bottom side.
### Configuration
#### Autopilot Configuration
**PX4 (Support coming soon)**
Several autopilot parameters must be set using QGC or similar:
* UAVCAN must be enabled by setting *UAVCAN\_ENABLE* non zero. Set this to 1 for basic functionality or 2 to allow the device's UAVCAN parameters to be accessed via QGC.
* Set the operating mode for each light using the parameters *UAVCAN\_LGT\_ANTCL*, *UAVCAN\_LGT\_STROB*, *UAVCAN\_LGT\_NAV*, and *UAVCAN\_LGT\_LAND*, as follows:
| Param Value | Description |
| ----------- | ---------------------------------------------------------- |
| 0 | Lights never on |
| 1 | Lights on when system is armed |
| 2 | Lights on when system is prearmed (safety switch "unsafe") |
| 3 | Lights always on |
#### Node Configuration
The Light Controller node has a number of parameters accessible via the UAVCAN interface. These may be set following the steps outlined [here](/general/parameters)
**Parameters**
| Parameter Name | Description | Default Value | Allowable Values |
| ---------------- | ----------------------------------------------------------- | -------------------------------------- | ---------------- |
| node\_id | Node ID for this device | 111 | 1-125 |
| chan\_1\_id | UAVCAN "SingleLightCommand" "light\_id" value for channel 1 | LIGHT\_ID\_RIGHT\_OF\_WAY (nav lights) | 0-255 |
| chan\_2\_id | UAVCAN "SingleLightCommand" "light\_id" value for channel 2 | LIGHT\_ID\_STROBE | 0-255 |
| chan\_3\_id | UAVCAN "SingleLightCommand" "light\_id" value for channel 3 | LIGHT\_ID\_LANDING | 0-255 |
| chan\_4\_id | UAVCAN "SingleLightCommand" "light\_id" value for channel 4 | LIGHT\_ID\_ANTI\_COLLISION (beacon) | 0-255 |
| chan\_1\_pattern | Pattern for channel 1. See "Patterns" table below. | 5 (always on) | 0-255 |
| chan\_2\_pattern | Pattern for channel 2. See "Patterns" table below. | 1 (strobe, double flash) | 0-255 |
| chan\_3\_pattern | Pattern for channel 3. See "Patterns" table below. | 5 (always on) | 0-255 |
| chan\_4\_pattern | Pattern for channel 4. See "Patterns" table below. | 3 (beacon, single-flash) | 0-255 |
***Patterns***
| Pattern Value | Pattern Name | Description |
| ------------- | -------------------- | ------------------------------------------------------------------------ |
| 0 | ALWAYS\_OFF | Lights off, regardless of command signal from autopilot |
| 1 | STROBE\_DOUBLE | Double flash at 1Hz |
| 2 | STROBE\_GLOW\_DOUBLE | Strobe, double flash, but low-intensity constant light when not strobing |
| 3 | BEACON | Single flash at 1Hz, opposite phase to strobe |
| 4 | BEACON\_SOFT | Soft 0.5Hz flash |
| 5 | ALWAYS\_ON | Constantly on when commanded on |
## Firmware
### Release Notes
#### v1.0
* Initial Release