Rotator data structure. More...

#include <rotator.h>

Data Fields
rot_model_t	rot_model
const char *	model_name
const char *	mfg_name
const char *	version
const char *	copyright
enum rig_status_e	status
int	rot_type
enum rig_port_e	port_type
int	serial_rate_min
int	serial_rate_max
int	serial_data_bits
int	serial_stop_bits
enum serial_parity_e	serial_parity
enum serial_handshake_e	serial_handshake
int	write_delay
int	post_write_delay
int	timeout
int	retry
azimuth_t	min_az
azimuth_t	max_az
elevation_t	min_el
elevation_t	max_el
struct confparams *	cfgparams
const char *	priv
int(*	rot_init )(ROT *rot)
int(*	rot_cleanup )(ROT *rot)
int(*	rot_open )(ROT *rot)
int(*	rot_close )(ROT *rot)
int(*	set_conf )(ROT rot, token_t token, const char val)
int(*	get_conf )(ROT rot, token_t token, char val)
int(*	set_position )(ROT *rot, azimuth_t azimuth, elevation_t elevation)
int(*	get_position )(ROT rot, azimuth_t azimuth, elevation_t *elevation)
int(*	stop )(ROT *rot)
int(*	park )(ROT *rot)
int(*	reset )(ROT *rot, rot_reset_t reset)
int(*	move )(ROT *rot, int direction, int speed)
const char (	get_info )(ROT *rot)

Detailed Description

Rotator data structure.

Rotator Caps

The main idea of this struct is that it will be defined by the backend rotator driver, and will remain readonly for the application. Fields that need to be modifiable by the application are copied into the struct rot_state, which is a kind of private of the ROT instance. This way, you can have several rigs running within the same application, sharing the struct rot_caps of the backend, while keeping their own customized data. NB: don't move fields around, as backend depends on it when initializing their caps.