dfti::Settings Class Reference
#include <settings.hh>
Inheritance diagram for dfti::Settings:
Collaboration diagram for dfti::Settings:
Public Member Functions | |
| Settings (QString _rcfile, DebugMode _debug) | |
| Ctor. | |
| bool | debugRC () const |
| Returns true if settings debug messages are enabled. | |
| bool | debugData () const |
| Returns true if sensor data debug messages are enabled. | |
| bool | debugSerial () const |
| Returns true if serial i/o debug messages are enabled. | |
| void | loadRCFile (QString _fn) |
| Load a settings file. More... | |
| float | logRateMs (void) const |
| Return the log sampling time in ms. | |
| float | flushRateMs (void) const |
| Return the log flush timer period in ms. | |
| float | sendRateMs (void) const |
| Return the server sampling time in ms. | |
| bool | serverEnabled (void) const |
| Return the server status. | |
| QHostAddress | serverAddress (void) const |
| Return the server address. | |
| quint16 | serverPort (void) const |
| Return the server port. | |
| bool | useMessageInterval (void) const |
| Should we prefer the MESSAGE_INTERVAL interface? More... | |
| quint32 | streamRate (void) const |
| Return the desired MAVLink stream rate in Hz. | |
| bool | setSystemTime (void) const |
| Should we set the system time from GPS? | |
| bool | useRIO (void) const |
| Do we have RIO logging? | |
| bool | useMavlink (void) const |
| Do we have a MAVLink-based autopilot? | |
| bool | useUADC (void) const |
| Do we have a Micro Air Data Computer? | |
| bool | useVN200 (void) const |
| Do we have a VN-200 INS? | |
| bool | waitForRIO (void) const |
| Should we wait for the RIO values before logging? | |
| bool | waitForMavInit (void) const |
| Should we wait for the MAVLink init message before logging? | |
| bool | waitForVN200GPS (void) const |
| Should we wait for VN200 GPS before logging? | |
| bool | waitForAllSensors (void) const |
| Should we wait for all sensors to get data before writing? | |
| bool | waitForUpdate (void) const |
| Should we wait for a data update to write to the log? | |
| QString | autopilotSerialPort (void) const |
| Overridden Autopilot serial port. | |
| QString | rioSerialPort (void) const |
| Overridden RIO serial port. | |
| QString | uADCSerialPort (void) const |
| Overridden uADC serial port. | |
| QString | vn200SerialPort (void) const |
| Overridden VN-200 serial port. | |
| quint32 | autopilotBaudRate (void) const |
| Overridden Autopilot baud rate. | |
| quint32 | rioBaudRate (void) const |
| Overridden RIO baud rate. | |
| quint32 | uADCBaudRate (void) const |
| Overridden uADC baud rate. | |
| quint32 | vn200BaudRate (void) const |
| Overridden VN-200 baud rate. | |
Detailed Description
Settings manager.
Member Function Documentation
| void dfti::Settings::loadRCFile | ( | QString | _fn | ) |
Load a settings file.
- Parameters
-
_fn Filename for settings file.
|
inline |
Should we prefer the MESSAGE_INTERVAL interface?
- Remarks
- MAVLink has deprecated the REQUEST_DATA_STREAM interface in favor of the new MESSAGE_INTERVAL interface, however APM does not yet (~Nov 2016) support this.
The documentation for this class was generated from the following files:
