Serialport: Remote control

Hardware inputs

It is possible to connect a commercial remote control to the VEKTOR Core. We recommend using common serial protocols for this purpose.

The VEKTOR Core supports both PWM ports and serial protocols for remote control with a hardware sender.

These two methods, PWM and serial protocols, are not mutually exclusive and can be used concurrently.

Software inputs

In networked systems or beyond-line-of-sight, it may be preferable to send commands via the network stack.

The firmware includes multiple software input addresses that are writable via MODBUS. These software inputs can be combined with any function similar to the hardware inputs.

Both hardware and software input types are not mutually exclusive and can be used together.

Supported protocols

The VEKTOR Core listens on the configured port for incoming control packets. The activation order of sender and receiver is in most cases not import. The system will synchronize itself.

Radio control

USART4 and USART8 can be used at the same time for remote control packet reception.

The blue LED will light up once valid packets are detected.

Port	Protocol	Sub-protocol	Channels
USART4, USART8	FlySky AFHDS-2A	IBUS-PWM	Up to 16
USART4, USART8	FUTABA	S.BUS	Up to 16
USART4, USART8	HoTT	SUMD	Up to 32
USART4, USART8	ELRS	S.BUS, SUMD	Up to 32

Modbus virtual ports

Selected registers are dedicated as virtual PWM inputs. It is possible to write PWM duty cycle values, and assign them to other logic blocks. This way is especially convenient when using the VEKTOR Core togheter with single boards computers like the Raspberry Pi, or PLCs.

These 32 channels are identfied as INPUT_MBUS_CH1 to INPUT_MBUS_CH32.