Used for SBUS?

[ikkemaniac]

can we use this component for SBUS communication?

https://github.com/uzh-rpg/rpg_quadrotor_control/wiki/SBUS-Protocol
For SBUS, a serial port has to be configured as follows:

    100'000 Baud rate (this is a non standard baud rate!)
    8E2 configuration, i.e.:
        1 start bit
        8 Data bits
        1 Even parity bit
        2 Stop bits



    1 Header byte 00001111b (0x0F)
    16 * 11 bit channels -> 22 bytes
    1 Byte with two digital channels (channel 17 and 18) and "frame lost" and "failsafe" flags
    1 Footer byte 00000000b (0x00)

[eigger]

Yes, it's possible.
You should be able to start communication with the SBUS protocol by configuring it like this.

uart:
  baud_rate: 100000
  data_bits: 8
  parity: EVEN
  stop_bits: 2

uartex:
  rx_timeout: 10ms
  tx_delay: 50ms
  tx_timeout: 500ms
  tx_retry_cnt: 3

  rx_header: [0x0F]
  rx_footer: [0x00]
  tx_header: [0x0F]
  tx_footer: [0x00]

  version:
    disabled: False
  error:
    disabled: False
  log:
    disabled: False

[ikkemaniac]

for documentation purposes: uart needs to be set to inverted for SBUS

[ikkemaniac]

that is freaking awesome 🔥

I'm going to start testing!

[ikkemaniac]

did some testing. Your setup works perfectly. One caveat is that SBUS is an inverted signal so we need set inverted in uart:, but that has really has nothing to do with the uartex implementation.

Working config:

uart:
  baud_rate: 100000
  data_bits: 8
  parity: EVEN
  stop_bits: 2
  rx_pin:
    number: GPIOxxx
    inverted: true
    mode:
      input: true


uartex:
  rx_timeout: 10ms
  tx_delay: 50ms
  tx_timeout: 500ms
  tx_retry_cnt: 3

  rx_header: [0x0F]
  rx_footer: [0x00]
  tx_header: [0x0F]
  tx_footer: [0x00]

  version:
    disabled: False
  error:
    disabled: False
  log:
    disabled: true

Next step i need to figure out is processing the data and extracting the info.

I guess the best way is to create a new component that 'depends' and basically extends yours/uartex. What do you think?

[eigger]

Thanks for the info — I actually wasn’t too familiar with the inverted setting, so that was really helpful!
I think creating a new component is a great idea. But rather than extending uartex using the depends method, I believe it's more appropriate to build a dedicated, standalone component specifically for handling SBUS.

When using uartex to add or manage new devices, I typically organize my configuration using YAML packages. This method has been flexible for testing and makes it easier to keep everything modular and maintainable.

ex)
https://github.com/eigger/espcomponents/blob/master/packages/count/botem/botem_csm505.yaml

packages:
  remote:
    refresh: always
    url: https://github.com/eigger/espcomponents/
    files:
      - packages/count/botem/botem_csm505.yaml