Silverware Wiki

User Tools

Site Tools

Trace:
sbus

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
sbus [2017/10/04 07:39]
silverxxx created 		sbus [2017/10/04 07:52] (current)
silverxxx
Line 1: Line 1:
-Sbus input+ 
 + 
 +**Sbus input**
  
 Sbus is an additional input type currently added to the bwhoop code only ( stm32 ). The pin used is one of the programming pins, SWCLK. That means the programming can only be done at powerup, during gyro calibration, or first 2 seconds, whichever is longer Sbus is an additional input type currently added to the bwhoop code only ( stm32 ). The pin used is one of the programming pins, SWCLK. That means the programming can only be done at powerup, during gyro calibration, or first 2 seconds, whichever is longer
Line 5: Line 7:
 The input pin supports both 3.3v and 5v, which should work with most SBUS receivers available. After signal is detected, the firmware waits for zero throttle for approximately 1 second before accepting the signal. Failsafe is set at 1 second of no signal, internal failsafe of the quad is used, which sets throttle to zero. The input pin supports both 3.3v and 5v, which should work with most SBUS receivers available. After signal is detected, the firmware waits for zero throttle for approximately 1 second before accepting the signal. Failsafe is set at 1 second of no signal, internal failsafe of the quad is used, which sets throttle to zero.
  
-To activate sbus input, enable the line " +To activate sbus input, enable the line " #define RX_SBUS" in the protocol section of config.h 
-#define RX_SBUS" in the protocol section of config.h+ 
 +**Rates** 
 + 
 +The current scaling is calculated to correspond with taranis settings on 100% limits. Higher limits will also be recognized, but the throttle active range will shrink as well. For other radios the range is 988 - 2012 uS, 1500 center. 
 + 
 +**Safety** 
 + 
 +Although some checks are made, the SBUS input could possible be decoded incorrectly; it's recommended to test the quad first in a safe manner, to make sure the channel order is correct ( especially throttle ). The correct order is AETR. One may also check the failsafe function at this point, by turning the tx off, while throttle is up.
  
  
sbus.1507095550.txt.gz · Last modified: 2017/10/04 07:39 by silverxxx

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki