rusefi
/
atbetaflight
mirror of https://github.com/rusefi/atbetaflight.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Documentation updates and spelling fixes

This commit is contained in:
Michael Jakob 2014-11-30 12:03:49 +01:00
parent 17d1c6e610
commit 4b2f35ccef
2 changed files with 13 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/Board - AlienWii32.md
View File

@ -1,8 +1,8 @@
# Board - AlienWii32
The AlienWii32 is actually in prototype stage only a few sample exist. There is some more field testing ongoing. The information below is preliminary an will be updated as needed.
The AlienWii32 is actually in prototype stage only a few samples exist. There is some more field testing ongoing. The information below is preliminary an will be updated as needed.
Here are the Hardware specifications:
Here are the hardware specifications:
- STM32F103CBT6 MCU
- MPU6050 accelerometer/gyro sensor unit
@ -17,8 +17,6 @@ Here are the Hardware specifications:
- dimensions: 30x32mm
- direct operation from an single cell lipoly battery
* Spektrum Compatible DSM2 satellites are supported out of the box. DSMX sat will work with DSM2 protocol wit default settings. Changes can be done as usual via CLI or the Cleanflight configurator.
* Spektrum Compatible DSM2 satellites are supported out of the box. DSMX sat will work with DSM2 protocol with default settings. Changes can be done as usual via CLI or the Cleanflight configurator.
The pin layout is similar as the NAZE32 or the related clones. The hardware bind pin is connected to pin 41 (PB5). The AlienWii32 firmware will be build with TARGET=NAZE and OTIONS="AlienWii32".
The firmware image will come with alternative default settings which will give a plug and play experience. There is no computer need to get this into the air with an smAL quadcopter.
anyhow to use this in an Hexa- or Octocopter or to do some more tuning additional CLI changes are required as usual.
The pin layout is very similar as the NAZE32 or the related clones (MW32, Flip32 etc). The hardware bind pin is connected to pin 41 (PB5). The AlienWii32 firmware will be build with TARGET=NAZE and OPTIONS="AlienWii32". The firmware image will come with alternative default settings which will give the user an plug and play experience. There is no computer need to get this into the air with an smal quadcopter. Anyhow to use this in an Hexa- or Octocopter or to do some more tuning additional CLI changes are required as usual.

26
docs/Spektrum bind.md
View File

@ -4,32 +4,24 @@ Spektrum bind with hardware bind plug support.
## Hardware
The hardware bind plug will be enabled via defining HARDWARE_BIND_PLUG during building of the firmware.
This is done automatically if the AlienWii32 firmware is build. The bind plug is expected between pin 41
(PB5 STM32F103CBT6) and ground. The bind code will actually work for USART2 (PA3 STM32F103CBT6).
The hardware bind plug will be enabled via defining HARDWARE_BIND_PLUG during building of the firmware. This is done automatically if the AlienWii32 firmware is build. The bind plug is expected between pin 41 (PB5 STM32F103CBT6) and ground. The bind code will actually work for USART2 (PA3 STM32F103CBT6).
## Function
If the bind plug is set the bind mode will be permanently activated during the firmware start-up. The
spektrum_sat_bind CLI parameter is defining the number of bind impulses (1-10) send to the satellite receiver.
If there is no hardware bind plug present the bind code will be executed ones after the next start (hardware
reset or power on) of the firmware and the spektrum_sat_bind parameter will be reset to 0 when done. The bind
code will not be executed during an soft rest of the MCU. Please refer to your receiver documentation for more
details of the specific receiver in bind mode. Usually the bind mode will be indicated with some flashing LED’s.
The Bind plug should be always removed for normal flying.
If the bind plug is set the bind mode will be permanently activated during the firmware start-up. The spektrum_sat_bind CLI parameter is defining the number of bind impulses (1-10) send to the satellite receiver. Please refer to the table below. If there is no hardware bind plug present and the spektrum_sat_bind paremeter is set the bind code will be executed one time only after the next start of the firmware (hardware reset or power on). The spektrum_sat_bind parameter will be reset to 0 when done. The bind code will not be executed during an soft rest of the MCU. Please refer to the sattelite receiver documentation for more details of the specific receiver in bind mode. Usually the bind mode will be indicated with some flashing LED’s. The Bind plug should be always removed for normal flying.
## Table with spektrum_sat_bind parameter Value
| Value | Receiver mode |
| ----- | ---------------|
| 3 | DSM2 1024/22ms |
| 5 | DSM2 2048/11ms |
| 7 | DSMX 22ms |
| 9 | DSMX 11ms |
| Value | Receiver mode | Notes |
| ----- | ---------------| --------|
| 3 | DSM2 1024/22ms | |
| 5 | DSM2 2048/11ms | default |
| 7 | DSMX 22ms | |
| 9 | DSMX 11ms | |
More detailed information regarding the sattelite binding process can be found here:
http://wiki.openpilot.org/display/Doc/Spektrum+Satellite
### Supported Hardware
all NAZE Targets (NAZE32, Flip32, AlienWii32 with hardware bind pin)
all NAZE targets (NAZE32, MW32, Flip32, AlienWii32 with hardware bind pin)