"fieldbus" block — the driver to auto-init at startup. An empty driver means "do not auto-init"; the fieldbus then waits for POST /api/init. More...

#include <config.h>

Collaboration diagram for FieldbusConfig:

[legend]

Public Attributes
std::string	driver
	"" \| "soem" \| "spoe".

std::string	adapter

std::vector< std::string >	ipAddresses
	SPoE only. One IP address per drive. The list order is the position order.

SpoeConfig	spoe

bool	mailboxStatusFmmu = false

Detailed Description

"fieldbus" block — the driver to auto-init at startup. An empty driver means "do not auto-init"; the fieldbus then waits for POST /api/init.

Member Data Documentation

◆ adapter

std::string FieldbusConfig::adapter

SOEM NIC: MAC or interface name. "" = none.

◆ driver

std::string FieldbusConfig::driver

"" | "soem" | "spoe".

◆ ipAddresses

std::vector<std::string> FieldbusConfig::ipAddresses

SPoE only. One IP address per drive. The list order is the position order.

◆ mailboxStatusFmmu

bool FieldbusConfig::mailboxStatusFmmu = false

SOEM only. Keep SOEM 2.0's mailbox-status FMMU active — the extra input FMMU it maps the SM1 mailbox-status register (0x080D) into the cyclic image on every mailbox slave, letting the master notice a waiting mailbox message without a separate read. Motion Master does not use that optimisation, and on TI PRU-ICSS ESCs a register-space FMMU inside an LRW is fatal (every cyclic frame is dropped, SAFE-OP → OP fails). Default false ⇒ the FMMU is deactivated after mapping. Set true only for hardware that both needs and supports it.

◆ spoe

SpoeConfig FieldbusConfig::spoe

SPoE only.

The documentation for this struct was generated from the following file:

apps/motion_master/config.h